Cisco PXM Version 1.1 User's Guide Page 634

  • Download
  • Add to my manuals
  • Print
  • Page
    / 972
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 633
C-20
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
Defect Information—Collect the following information for further analysis:
Collect the ILMITopoc.log, topod.log, NMServer.*.log, nts.*.log
Collect the dump outputs of ILMITopoc, topod and NMServer. The dump can be captured by issuing
a kill -USR1 signal to the process.
Collect the output of the switch CLI, selnd and dbnds.
Possible alternative workaround—None
C.5 Equipment Management Problems
This section includes the following information:
C.5.1 Sync Up Issues
C.5.2 Cisco MGM DB and Switch Data Inconsistency Issues After Node Provisioning for MGX
C.5.1 Sync Up Issues
This section includes the following information:
C.5.1.1 EM Declares Successful Node Re-sync When Node Mode Is 3
C.5.1.2 Network Setup and Configuration Required for OOEMC Sync Up Process
C.5.1.3 Node Mode Remains in 1
C.5.1.4 Node Mode Remains in 2
C.5.1.5 Node Resync Mode is 5
C.5.1.6 Cisco MGM DB Inconsistent With Switch Data After Successful Coldstart (Cisco MGM
Server stop/start) or Periodic Resync
C.5.1.7 Cisco MGM CM GUI Shows Incomplete Connections After Successful Node Resync and
Dbroker Sync Up
C.5.1.8 Cisco MGM GUI Shows Mismatched Information Between GUI Views and DB Data
C.5.1.1 EM Declares Successful Node Re-sync When Node Mode Is 3
MGX nodes are managed by OOEMC component in Cisco MGM. Equipment Management (EM) uses
coldstart, warm start, and periodic resync to sync up network data. Each of these resync methods will
involve configuration file upload, parsing, and DB population. Node mode in node table indicates the
state of the sync up process. The possible node modes are 1, 2, 3 and 5. Expected mode for a successful
node resync is 3. If the node mode stays in other mode for a long period of time, it indicates some kind
of resync problem. Keep in mind that any sync up problem could be caused by switch, SNMP, FTP, and
OOEMC itself. User needs to branch out to different areas for identifying the root cause of any sync up
problem.
Page view 633
1 ... 633 634 635 ... 972

Comments to this Manuals

No comments