7.3 Troubleshooting the Alarm Manager

No alarm is displayed in the Alarms view of ConsoleOne even though the alarms are in the database

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The Alarm Manager might not have started properly.
Action: Perform the following tasks:

  1. Open the sloader.log file in the ZENworks_installation_directory\zfs\mms\logfiles directory and search for the following string: Alarm Manager started successfully.

    If you are unable to find this string, the Alarm Manager has not been started successfully.

  2. Start SLOADER again.

    To start, enter sloader at the Management server prompt.

Alarm is not displayed in the Alarms view

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The archiving and the ticker bar options are disabled in the rule triggered by the Alarm.
Action: Do the following:

  1. Check the disposition settings of similar rules for the type of alarm you are viewing.

  2. Enable the archiving option and the ticker bar option.

Possible Cause: The system is unable to recognize the alarm type and the IgnoreUnknownTrap flag is set to YES in ZENworks_installation_directory\zenworks\mms\ mwserver\properties\alarmmanager.properties.
Action: Perform the following tasks:

  1. In the left frame of Novell ConsoleOne, right-click the Novell ZENworks Server Management site object, click Properties, and then open the alarm templates.

  2. Search for the alarm type in the templates. If the alarm type does not exist, the Alarm Manager does not recognize the alarm type you have specified.

  3. In ZENworks_installation_directory\zenworks\mms\ mwserver\properties\alarmmanager.properties, select the value of IgnoreUnknownTrap to NO.

  4. Add the MIB into the MIB Pool that defines this trap type and compile the MIB.

    For more information, see Configuring MIBs and Setting Up MIB Tools in Understanding Alarm Management in the Novell ZENworks 7 Server Management Administration Guide.

Alarms from a NetWare machine are not displayed in the Alarms view

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The sys:\etc\traptarg.cfg does not contain the IP address of the ZENworks Server Management site server.
Action: Ensure that the sys:\etc\traptarg.cfg file contains an entry for the IP address of the ZENworks Server Management site server.

Incomplete parameter is displayed while an application is being launched

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The arguments are incorrect because they contain spaces.
Action: Open the Launch Application disposition for the template for which the launching application disposition has been set. In the argument field, enclose the arguments within double quotes.

Unable to receive the SMTP mail notification

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The SMTP mail notification is disabled in the rule triggered by the alarm.
Action: Do the following:

  1. Check the SMTP Notification Settings of the rule for which the SMTP mail notification is required.

  2. Click Test in the Actions tab of the Rule Configuration page to verify that the IP address or DNS name of the SMTP mail server is correct and the SMTP service is up and running on the SMTP mail server.

Possible Cause: The SMTP mail server is not running on the designated server.
Action: On the server, start the SMTP mail service with the designated IP address.

Unable to forward alarms or traps

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The ZENworks Server Management site server is not running.
Possible Cause: The Alarm Manager is not running at the destination IP address or server name.
Action: Run the Alarm Manager component at the destination ZENworks Server Management site server.

Unable to launch the application

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The application mentioned in the rule Action is not found at the site server or the application does not exist in the path you have specified in the Launching Application page.
Action: Verify that the application name and the path are correct.

I recompiled the MIBs after changing the severity of a trap definition. The new severity status is reflected in the Alarm template but not in the Active Alarms and Alarm History. The incoming alarms still display the previous severity status

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Action: Restart the ZENworks Server Management server.

I do not see alarm in the active alarm view of ConsoleOne

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The snmplog.nlm version has changed.
Action: Do the following:

  1. Restart the Site server.

  2. On the NetWare server console, check whether snmplog.nlm is loaded.

Alarms from a SUSE(R) Linux Enterprise Server (SLES) machine are not displayed in the Alarms view

Severity: ZENworks 7 Server Management; Management and Monitoring Services; Alarm Manager
Possible Cause: The application firewall on the SLES10 Server blocks the traps from reaching the MMS server.
Action: Perform the following steps to allow the traps to reach the MMS server:

  1. Open the /etc/apparmor.d/sbin.syslogd file by using an editor.

  2. (Conditional) If the following line does not exist in the file, then add the line to the file:

    /opt/novell/** rw

  3. At the command prompt, execute the following commands:

    1. To restart the apparmor: rcappamor restart

    2. To restart the syslog: /etc/init.d/syslog restart

    3. To restart the log2trapd: /var/opt/novell/zenworks/zfs/mms/suse/novell-trapd restart