J-67
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.5 Configuration Center, Chassis View, Diagn ostics Center, and Statistics Report Problems
c. Verify whether or not the alarms are aggregate port alarms. If so, this is expected behavior and there
is no defect. If there are alarms that have greater severity then what is shown on the platform, and
they are not aggregate port alarms, continue to the next step to see whether the alarm is in the
database.
Step 4 Verify whether the database has the correct alarm state. Refer to the Cisco Transport Manager Release
6.0 Database Schema for information on what table to look up for this particular entity type.
Defect Information—Collect the following information for further analysis:
•NMServer.log
•nmControl.dump
•CMSCclient.log on client machine
Possible alternative workaround—Open a new GUI and a new Configuration Center, Chassis View,
Diagnostics Center, or Statistics Report.
J.10.5.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 and the NMS. One example of such an alarm is the node sync-up 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 the alarm list, but there will not be such an alarm on the platform. The
following is a summary of alarms that may be seen in the alarm list, but not on the platform.
Step 1 If there is an alarm in the alarm list, and not on the platform, see if the suspect alarm is included in the
following list:
•Node sync-up status alarms
•Node database sync-up status alarms
•Node Management State status alarms
•Node Aggregate alarm status
•Link0/Link1 Node alarms
•Card sync-up status alarms
•Aggregate Port (Connection) alarms
Step 2 If the suspect alarm is not included in any of the alarm list mentioned in step 1, it may be a defect.
Perform the following:
a. Verify whether the database has the correct alarm state. See the Cisco Transport Manager Release
6.0 Database Schema for information on what table to look up for this particular entity type.
b. Collect the following information:
–
topod.log, linktopoc.log, ILMITopoc.log, NMServer.log, and fileTopoc.log
–
nmControl.dump
–
CMSCclient.log