Novell Home

AppNote: Centralized Management of NetWare Traps via ZENworks 7 MMS Console

Novell Cool Solutions: AppNote
By Narasimha Galeleo

Digg This - Slashdot This

Posted: 18 Oct 2005
 

This AppNote explains the effective usage of "Trap Configuration" available in ZENworks 7 Management and Monitoring services. This can be leveraged to manage NetWare Server, eDirectory / Novell Directory Services (NDS) Traps sent from the Managed Servers to a designated Site Server.

  1. Introduction
  2. Understanding Trap Configuration
  3. Configuring and applying settings
  4. Conclusion

1. Introduction

In many corporate networks there are multiple NetWare servers running different services and/or applications. As these services and apps are used daily, problems and variations in behavior can occur, and traps are a useful way for administrators to keep an eye on things. NetWare Server and NDS Traps can be configured to be sent to the Management Site Server to highlight changes in normally defined behavior or variations in the parameter being monitored. As an administrator, you may wish to control the traps sent from the servers to the Management Server, and with ZENworks 7 it's easier than ever.

With previous versions of ZENworks, you had to type in some commands on the server Console. Alternatively, you could manage the traps through ndstrap.cfg and nwtrap.cfg and reload the agents to read the configuration, or execute "nwtrap read_cfg" commands to apply the configuration. However, Novell ZENworks 7 Management and Monitoring Services (MMS) now allows you to configure the NetWare and NDS traps easily via ConsoleOne Snapins.

Using ZENworks 7 MMS Trap Configuration Console you can centrally enable/disable traps and change the Trap Interval for the traps defined in NetWare Server Alarm MIB and NDS Alarm MIB.

2. Understanding Trap Configuration

The Configuration Agents

NetWare Server Alarm MIB Trap Configuration is managed by the nwtrpagt.nlm agent, which implements the NWTRAPCONFIGURATION MIB module.

The NDS MIB Trap Configuration is managed by the dstrpagt.nlm agent, which implements the NDSTRAPCONFIGURATION MIB module.

MIB Name MIB Module Implemented By
NetWare Server Alarm NWTRAPCONFIGURATION NWTRPAGT.NLM
Novell Directory Services NDSTRAPCONFIGURATION DSTRPAGT.NLM

The nwtrpagt and dstrpagt NLMs implement tables for NetWare Server Alarm MIB Traps and Novell Directory Services MIB Traps. These tables are defined by NWTRAPCONFIGURATION MIB and NDSTRAPCONFIGURATION MIB. This table has editable objects for "Trap Status" and "Interval."

Here is the Object ID for the NetWare Server MIB:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).novell(23).mibDoc(2).nwServer(28)

Trap Configuration Console

You can use the Trap Configuration management console to enable/disable and configure the Interval field for NetWare Server Traps and Novell Directory Service Traps.

The Trap Configuration console can be launched at Atlas / Segment / Page / NW Server Node level.

When launched from the node level, it displays the existing configuration on the respective NetWare Server. Otherwise, Default Profile, Traps with Critical and Major severity are enabled and "Interval = -1" for all traps.



Figure 1: Trap Configuration main window

3. Configuring and applying settings

Here are some typical usage scenarios which illustrate how you could centrally configure trap behaviors with the Trap Configuration console of ZENworks 7 Management and Monitoring Services.

Scenario 1: Configuring settings for a chosen set of traps and applying them to a server

An administrator wants to enable critical NetWare Server Traps and assign a five-minute interval. He also wants to enable major NDS Traps with a twenty-minute interval. Here's how to do that.

  1. Invoke Trap Configuration



    Figure 2: Invoking Trap Configuration from Page/Segment/Container

    "Trap Configuration" window (as shown in "Figure 1") comes up in ConsoleOne.


  2. On the "Trap Configuration" window, click on "Filters" and configure a filter as follows:



    Figure 3 : Filter to view NetWare Server traps of 'Critical' Severity and NDS traps of 'Major' Severity

    Click "OK" to apply the filter. The filtered View as seen on Figure 4 is displayed.


  3. Configure Interval using the "Trap Command" Text box on the "Trap Configuration" window.
    Trap intervals can be set individually on the console or by using the Trap Command to configure intervals for multiple traps.

    To configure the interval of an individual trap, select the row corresponding to the trap and double-click on the cell corresponding to the Interval column to edit the value.

    Note: All the modifications done in the Trap Configuration window are applied to the view only. Click Select Agents and Apply to make the settings effective on target NetWare Servers.



    Figure 4: View after filter is applied as in Step 3 & "Trap Command" to set interval of NetWare Server Traps in the view to 300 seconds (5 Minutes).

    Note: Similarly, type "ndstrap all interval 1200" and click on Set to configure the interval for NDS Traps in the view to 20 Minutes (1200 seconds).


  4. Select the NetWare Servers on which the configuration is to be applied.



    Figure 5: Select servers to apply Trap Configurations and click Apply.

    "Select Node View" adds nodes selected from the "Select Objects" window based on the following criterion: "Nodes which are discovered to implement NetWare Server MIB", as this feature can be used only for configuring NetWare Servers.

    Selected nodes are displayed as IP Addresses in the "Select Node View".


  5. To view the status of the configuration click "Show Status."



    Figure 6: Trap configuration status window

    Note: Configuration Status is displayed per Server. Configuration Status logs would provide the details of succeeded and failed configurations.

Scenario 2 : Replication of configuration done on a server to multiple servers in the network

An administrator has completed Trap configuration on a NetWare server and wishes to replicate the same configuration across multiple servers in the network. For the purpose of future usage, he also wishes to save the configuration as a profile in the database. Here's how to do that.

  1. Browse to the node for which you want to read the Trap Configuration and invoke Trap Configuration.



    Figure 7: Viewing the current configuration from a server

    The Trap Configuration window as shown in Figure 1 comes up on the ConsoleOne, but now with a difference: Window Title is "Server Name."


  2. Select "Manage Profile" and save a copy of the current configuration.



    Figure 8: View of "Manage Profile", Save the profile


  3. Select NetWare servers where this configuration is to be replicated (as explained in Step 4 of Scenario 1).


  4. Apply the configuration. Verify the Status logs to see the result (as explained in Step 5 of Scenario 1).

Conclusion

This AppNote has discussed the effective usage of "Trap Configuration" available in ZENworks 7 Management and Monitoring services. This can be leveraged to manage NetWare Server and / or NDS Traps sent from the Managed Servers to designated Site Server.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell