User guide

C-43
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems
Step 5 If element is not in the database, check the NMServer cache.
This can be done by using the command nmControl (Option 4) on the Cisco MGM CLI. Check the
nmControl.<pid>.dump
Step 6 Use nmClient and verify whether getChildren for FDN, returns the element in the nmClient.<pid>.dump
file.
Step 7 If element is not present in NMServer cache, Open a New GUI and verify whether the extra element is
shown in the new GUI.
Defect Information—Collect the following information for further analysis:
• Collect topod.log, ILMITopoc.log, NMServer.log
• Collect nmControl.dump for option 4.
• Collect CMSCclient.log
Possible alternative workarounds
1. Open a new GUI and a new Configuration Center, Chassis View, Diagnostic Center or Statistics
Report GUI.
2. Use nmControl and perform "Resync Node" specifying the node id.
C.6.5 Configuration Center, Chassis View, Diagnostic Center or Statistics
Report GUI Alarm Issues
This section includes the following information:
• C.6.5.1 Alarm Processing Basics
• C.6.5.2 XML Schema for Alarm Rules
• C.6.5.3 Alarm Severity and Object Severity
• C.6.5.4 Severity Shown on Tree View Does Not Match Severity Shown on Platform
• C.6.5.5 Alarm List Shows Alarm That Does not Exist on Platform
• C.6.5.6 Transient Event Has Disappeared Unexpectedly
• C.6.5.7 Port in Tree View Displays an Aggregate Alarm, However No Children Exist Under Port
C.6.5.1 Alarm Processing Basics
Alarm processing is done within the NMServer processes. Following are some vital points with regard
to alarm processing:
1. Alarm rules are defined in an XML file (/opt/svplus/xml/ruledata.xml). For details on 'XML schema
on alarm rules, see Figure C-2.
2. GUI clients register for alarms by providing the parent FDN
3. GUI clients pull initial alarms from NMServer. After initial pull of alarms, all alarms are pushed to
registered clients by NMServer when alarms occur
4. Object severity for any and all network elements is determined by the XML alarm rule
5. Administrative states of network element states are not displayed in alarm list, only alarm states.