Cisco PXM Version 1.1 User's Guide Page 730

  • Download
  • Add to my manuals
  • Print
  • Page
    / 972
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 729
C-116
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Miscellaneous Problems
In normal case, you see the following cluster for each trap in NTS log.
( 21359: 46) 01:46:49 WARNING: N15 Trap(6, 60303, #25278)
( 21359: 46) 01:46:49 WARNING: N15 Trap #25278 buffered
( 21359: 48) 01:46:49 WARNING: N15 Trap(6, 60303, #25278) to CSA
( 21359: 50) 01:46:49 WARNING: N15 Trap(6, 60303, #25278) to RtmProxy
( 21359: 60) 01:46:49 WARNING: N15 Trap(6, 60303, #25278) to ooemc-24610
( 21359: 58) 01:46:49 WARNING: N15 Trap(6, 60303, #25278) to EMD
( 21359: 49) 01:46:49 WARNING: N15 Trap(6, 60303, #25278) to HPOV
line 1 means "Trap(6, 60303, #25278)" is received by NTS.
line 2 means it is successfully buffered by NTS.
line 3 ~ 7 means it is delivered to the clients who registered to receive it in their XML filter setting.
Step 2 If you cannot find the particular trap, verify if the switch is sending traps with a wrong trap IP address.
If the switch trap IP is wrong, traps from it is declared as coming from unmanaged node and dropped.
The Trap IP address has to be the primary IP address of the switch. Otherwise, NTS cannot correlate the
trap with the Cisco MGM node information and has to discard that trap. See C.15.1.2 Config Change or
Provisioning Activity Not Reflected on Cisco MGM.
The NTS prints a different message when a trap comes from a node it does not yet manage (unknown
node_id), for example:
nts.7275.log.old.2:( 7275: 45) 03:32:39 WARNING: Trap unmanaged 172.28.140.16
In that case, it prints the IP address only and throw it away.
Defect Information—None
Possible alternative workarounds—None
Related key index entries: nts, log
C.15.2 Data Inconsistency
This section includes the following information:
C.15.2.1 Connection Inconsistency Between the Switch and GUI
C.15.2.2 Inconsistent Connection Status
C.15.2.3 Inconsistent Connection Secondary Status
C.15.2.4 Incomplete Connections
C.15.2.1 Connection Inconsistency Between the Switch and GUI
This section discusses strategies for debugging inconsistencies between the switch and the Cisco MGM
GUI. The inconsistency in this section are not directly related to provisioning. The problems may be
caused by coldstart, warmstart or provisioning, but they are noticed sometime after the fact. (i.e. You
look at the system and suddenly realize there is an inconsistency).
Page view 729
1 ... 729 730 731 ... 972

Comments to this Manuals

No comments