User guide

C-48
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 4 Verify whether discrepancy is caused by aggregated connection alarms
a. NMServer does more aggregation of alarms then the platform. For instance, NMServer aggregates
connection alarms up the port and the switch does not. Therefore, if the tree view displays a higher
severity then the switch, it maybe caused by one or more aggregated port alarms.
b. Right click the NE (network element) in the tree view and choose 'show alarms'. All of the alarms
for this NE and its children should display in the alarm list.
c. Filter on the alarms that are greater severity then what the platform is showing
d. Are these alarms 'Aggregate Port' alarms? If so, this is expected behavior and there is no defect. If
there are alarms that are greater severity then what is shown on the platform, and they are not
'Aggregate Port' alarms, continue to next step to troubleshoot whether the alarm is in DB.
Step 5 Verify whether DB has correct alarm state. Refer to the DB schema document for information on what
table to lookup for this particular entity type.
Defect Information—Collect the following information for further analysis:
• Collect NMServer.log
• Collect nmControl.dump for option 3.
• Collect CMSCclient.log on client machine.
Possible alternative workaround—Open a new GUI and a new Cisco MGM MGXNE Specific GUI
(CC,DC,CV,SRT)
C.6.5.5 Alarm List Shows Alarm That Does not Exist on Platform
There are several alarms that are correlated by NMServer and are not handled by the switch. This is the
case because the NMS keeps track of alarm conditions that may not be relevant to the switch alone, but
are relevant to the switch + the NMS. One example of such an alarm is the node syncup state. The switch
itself is not interested in the fact that the NMS may not be synced up with it, but the NMS is interested
in this information. Therefore if the node is still syncing up with the NMS, an alarm will be displayed
for this node in Alarm List, but there will not be such an alarm on the platform. Below is a summary of
alarms that may be seen in the Alarm List, but not seen on the platform.
Step 1 If there exists an alarm in the alarm list, and not on the platform, check if the suspect alarm is included
in the following list:
1. Node Syncup status alarms
2. Node DB Syncup status alarms
3. Node Management State status alarms
4. Node Aggregate alarm status
5. Link0/Link1 Node alarms
6. Card Syncup status alarms
7. Aggregate Port (Connection) alarms