User guide

C-47

Cisco Media Gateway Manager 5.0 User Guide

OL-5461-02

Appendix C Troubleshooting

Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems

<NewAlarmDescrSuffix>Sync-Up has not started yet</NewAlarmDescrSuffix>

</CorrelatedRule>

This alarm will occur if the southbound processes (EMs) send a node message with EM syncup status

as 1 or -1. If that does occur, then the node should be unreachable severity (value 7) in the tree view.

Note there is no 'unreachable' severity in the alarm list. This is why we have two severities for each

alarm. There is no such alarm severity as 'unreachable' in the alarm list. Unreachable alarms have

'Critical' (value 6) severity in the alarm list.

Another instance when 'Alarm' and 'Object' severity do not match is for 'Aggregate Port' alarms.

Aggregate port alarms are alarms that summarize the condition of the connections on the port. Since

these alarms should not effect the severity of the port, the object severity of these is alarms is 'Clear'

(value 3). Following is the XML for an aggregate port alarm:

<NewAlarmDescrSuffix>Aggregate Port alarm, One or more connections on this port are in

primary failure</NewAlarmDescrSuffix>

</CorrelatedBmRule>

Note the alarm severity ('NewAlarmSev' tag) is 'Major' (value 5).

C.6.5.4 Severity Shown on Tree View Does Not Match Severity Shown on Platform

Severity of network element in tree view does not match the severity the switch is showing for the same

network element.

Step 1 Verify customer is comparing the correct severity icon

a. There are two severities associated with every object in the tree view, the Aggregate severity and

the Self severity. The aggregate severity is on the left, the Self severity is on the right. Since the

switch does aggregation of many faults, the customer should compare the aggregate severity of the

object in tree view with the severity of the switch.

b. If the customer is looking at the correct severity icon and there is still a discrepancy between the

severities, continue to Step 2.

Step 2 Verify whether Cisco MGM has synced up with the node.

a. Login to Cisco MGM server and type 'selnd'

b. Verify the mode of the node in question is 3

Step 3 If the mode is 3, continue to Step 4.