Cisco Systems 78-16845-01 appendix Equipment Management Problems

Page 40

Appendix J Troubleshooting

J.10.4 Equipment Management Problems

Step 2 If the node table does not have an entry for the node with the correct IP address, complete the following substeps:

a.Check the ILMItopoc log and verify whether it received a 60007 and 70202 trap.

b.If you see the trap in the log, verify that ILMITopoc updates its cache based on the trap.

c.If you do not see the traps in the ILMITopoc.log, see J.10.13.1 NTS, page J-127.

Defect information—Collect the following information for further analysis:

•ILMITopoc.log, topod.log, NMServer.log, and nts.*.log.

•Dump outputs of ILMITopoc, topod, and NMServer. Enter the following command:

kill -USR1 signal <process>

•Collect the output of the switch CLI, selnd, and dbnds.

J.10.4 Equipment Management Problems

This section describes troubleshooting procedures for equipment management problems on the Cisco MGX devices.

J.10.4.1 Equipment Management Declares Successful Node Resync when Node Mode Is 3

MGX nodes are managed by the ooemc component in CTM. Equipment management (EM) uses coldstart, warmstart, and periodic resync to synchronize network data. Each of these resync methods involves configuration file upload, parsing, and database population. The node mode in the node table indicates the state of the synchronization process. The possible node modes are 1, 2, 3, and 5. The expected mode for a successful node resync is 3. If the node mode stays in other modes for a long time, it indicates a resync problem. Any synchronization problem could be caused by the switch, SNMP, FTP, or ooemc. You must investigate different areas to identify the root cause of any synchronization problem.

The following is the flow of events in the ooemc coldstart synchronization process:

1.The topo process discovers a node in the network. The process changes the node mode in the node database table to –1. It then notifies the ooemc component for the discovery. The ooemc changes the node mode from –1 to 1 after the component begins managing the node.

2.When the nts component is able to register with the node, it sends a link up message to the ooemc that manages the node. The ooemc component changes the node mode from 1 to 2 to signify the start of the node synchronization.

3.The ooemc component sends an SNMP bulk file creation request to the switch. If the request is allowed, the switch sends a trap 60901 to CTM to signify the start of bulk file creation. When bulk file creation is complete on the switch, the switch sends a trap 60902 to CTM. After CTM receives the trap, it begins to FTP the config upload files.

4.If the upload and parsing of all config files completes without errors, the ooemc changes the node mode from 2 to 3. If the upload or parsing encounters errors for any service module on the switch, the node synchronizes partially and the ooemc changes the node mode from 2 to 4 at the end of the node synchronization process. If the error occurs on the shelf generic card file (CARD_01_CC.CF) or pnni file (PNNI_01_CC_CF), the ooemc changes the node mode from 2 to 5 to signify node sync-up failure.

Cisco Transport Manager Release 6.0 User Guide

 

J-40

78-16845-01

 

 

 

Page 39 Page 41
Image 40
Page 39 Page 41
Contents Troubleshooting Server Problems Conditions that Affect CTM Server PerformanceCTM Server Does Not Respond Cannot Connect to the CTM Server NE Connection State Is Listed as Unavailable Snmp Traps Are Not Forwarded from NEs Launching Tables Results in Database ErrorsTrap Port Is Unavailable Problems with ONS 15530 and ONS 15540 Configuration Performance Monitoring Data Is Not DisplayedCTC-Based NE Is Not Reachable CTC-Based NE Is Not DiscoveredONS 15501, ONS 15540, or ONS 15530 Is Not Reachable Circuit State for Monitor Circuits Reads Duplicate ID Circuits Are Not DisplayedNE Model Type Appears as Unknown Cannot Copy CTC Binary to the CTM Server Memory Backup, Memory Restore, or Software Download FailsGetinfo.sh Script Fails Using the get nestate Command Database Is Not AvailableAre the CTM Client and the CTM Server Connected? Database Timeout OccursCannot Log In as Provisioner or Operator Cannot Authenticate User Message Appears Model Index Is UnknownCTC Fails to Start Cannot Delete an NEAdded a New Software Version to the Wrong NE Cannot Move an NE Between Subnetworks Cannot Delete a SubnetworkCannot Schedule Jobs NE Displays Incorrect Configuration Management Data Bandwidth-Intensive Operations Are BlockedCannot Customize the Network Map How Do I Collect Thread Dumps? SnmptrapClick OK How Do I Replace the Alarm Interface Panel? Client Debug MessagesCTM GateWay/TL1 Problems Cisco CRS-1 and Catalyst 6509 Problems Cat6509 enable# set snmp trap enable all CTM Does Not Receive Traps from the CatalystCTM Does Not Receive syslog Events from the Catalyst SyslogCTM Does Not Collect Historical PM Data for the CRS-1 Memory Backup or Restore Fails for the CRS-1 Click NE Service How Do I Configure Telnet on the CRS-1? Cannot Delete an Out-of-Service NE from CTMHow Do I Configure SSH on the CRS-1? How Do I View the Snmp Configuration on the Catalyst 6509? How Do I Load a Software Image on the Catalyst 6509?Output is similar to the following example Reporting XR 12000 Issues CTM Cannot Discover an XR 12000 Node4 XR 12000 Alarm and Event Reporting Issues 5 XR 12000 PM Collection Issues6 XR 12000 BGP and CDP Neighbor Discovery Issues 7 XR 12000 NE Explorer Applications Are DisabledDiscovery Mechanism Discovery Issues at StartupNo Nodes Are Discovered Output of the switch CLI, selnd, and dbnds Node Name Is Incorrect in the DatabaseNode Alarm Is Shown Incorrectly in the Database Node IP Is Incorrect in the DatabaseReachable Node Is Shown as Unreachable CTM State Is IncorrectDiscovery Issues at Runtime Collect the output of the switch CLI, selnd, and dbnds Equipment Management Problems Node Mode Remains Ls -ltr *.9 SMCARD01SRM.CF Node Resync Mode Is SMCARD01RPM.CFEMCSnmpFunccProcFuncGenNodeBulkFile1 entering Appendix J Troubleshooting Equipment Management Problems Appendix J Troubleshooting Equipment Management Problems Appendix J Troubleshooting Equipment Management Problems Database Table Population Through Traps and Snmp Upload Appendix J Troubleshooting Equipment Management Problems Appendix J Troubleshooting Equipment Management Problems You should see something like the following Figure J-1shows the end-to-end architecture Figure J-1 CTM End-to-End Architecture Basic Issues Topology Discovery Issues Appendix J Troubleshooting CTM CLI Network Element Discovery Issues All the Cards Under a Node Are MissingCisco Transport Manager Release 6.0 User Guide 78-16845-01 Appendix J Troubleshooting Alarm Processing Basics XML Schema for Alarm Rules Figure J-2 Client/Server Architecture for Alarm ComponentsFigure J-3 Correlated Alarm Rule Diagram Alarm Severity and Object Severity Figure J-5 Transient Alarm Rule DiagramCisco Transport Manager Release 6.0 User Guide 78-16845-01 Alarm List Shows Alarm that Does Not Exist on Platform Transient Event Has Disappeared Unexpectedly Chassis View Problems Chassis View BasicsLines Not Displayed in the Chassis View Card Not Displayed in the Chassis ViewEthernet Status Not Updated on PXM Cards HIST, CBRX, and Cbtx Status Not Updated in MGX NodesRPM Card Status Not Updated 10.6.4 DCA/DCB Status Not Displayed on PXM CardsConfiguration Center Management Configuration Center FrameworkLines Not Selectable Wrong Tooltip Is DisplayedCannot Launch the Configuration Center Choose Tools Configuration Center from any applicationAppendix J Troubleshooting Configuration Center Management Element Management-Drag and Drop Within Configuration Center Element Tab-Internal Frame Does Not LaunchCross Application-Configuration Center as Drag Source Appendix J Troubleshooting Configuration Center Management Configuration Center-Element Management XML Parsing ErrorSnmp No Data Error Details, Create, Delete, and Refresh Buttons Are Not EnabledSnmp Timeout Error Snmp Set ErrorObject Not Found In Tree View Error Element Data Inconsistent with Switch Configuration Center GUI-Framework Issues Connection Management ProblemsConfig Server Reports Error Messages Appendix J Troubleshooting Connection Management Problems Appendix J Troubleshooting Connection Management Problems Cross Application-Connection List as Drag Source Configuration Center GUI-CM Server-Reported Errors Configuration Centers Connection Tab Does Not RespondDATABASEERRORDatabase error %s Appendix J Troubleshooting Connection Management Problems Cmsvr Errors Cannot Create One-Segment Hybrid Unsupported Service Type-General node-slot-port-version Cmsvr-Connection Diagnostic Issues TestConn or TestDelay Failed with Switch ErrorConnection Up/Down/Reroute Failed Connection Trace FailuresCmgrd High-Level Connection Management Subsystem Architecture Figure J-6 Connection Management SubsystemCmgrd-Sdbroker Errors Related key index entries cmgrd, sdbroker, vpi/vci Appendix J Troubleshooting Connection Management Problems Cmgrd Errors 100101 102 Cmgrd-Switch Errors 103104 105 106 Diagnostics Center Problems 107Diagnostics Center Framework 108Cannot Launch Diagnostics Center 109110 Drop Target Displays Incorrect Object or Object Data Diagnostics Center Does Not Respond GUI Is Grayed Out111 Diagnostics Center Server-Specific Issues 112Snmpcommtimeout Error While Polling MIB Objects XML Parser Error113 Node Sync-Up Status Are Not Shown in the Diagnostics Center Node Resync FailsPolling of Real-Time Counters Fails 114Unable to Start, Stop, or Modify Bert Operations Some Real-Time Counters Are Not Shown115 Unable to Start/Stop IMA Link Test Patterns Cannot Perform Connection Diagnostics116 Performance Management Collection and Parsing Problems PM Collection IssuesMiscellaneous Issues or Problems in Diagnostics Center Pmcollector-Generic Troubleshooting118 PM Collection Fails for the Node-Log File Shows Snmp failed 119PM Collection Fails for the Node-Log File Shows Ftp failed 120Statistics Report Problems PM Parsing IssuesStatsParser-Generic Troubleshooting 121You See FDNs for Other Entities when You Generate a Report Statistics ReportYou Collected Data but You See No Data Available You Generated a Report but Do Not See Data for a Long TimeService Agent Problems Utilization Report Value Is Greater than 100%RtmProxy 123Not Receiving Any Traps Registration with RtmProxy Failed124 Audit Trail Logging Mechanism Problems Manager Gets DeregisteredNodal Community Strings Do Not Work 125Miscellaneous Problems AuditLogger.conf UsageAudit Trail Log File Naming Convention 126Nodes Stay in Mode 1 After ColdStart Config Change or Provisioning Activity Not Reflected on CTM10.13.1 NTS 127How To Interpret NTS Log 128Data Inconsistency Connection Inconsistency Between the Switch and GUI129 Each output line is similar to this 130Process ID of the sdbroker will be returned 131Inconsistent Connection Secondary Status Inconsistent Connection Status132 Incomplete Connections 133Generic Troubleshooting FTP Username and PasswordCTM FTP Daemon FTP Daemon OverviewFTP Sessions in Switch Cwmftpd-File Not Available On Switch135 10.13.3.8 499 Session Limit Reached 10.13.3.7 421 Session Limit Reached136 Failed to Acquire a Session with a Switch Failed to Acquire Session After All RetriesGeneral Log Information 137138
Related manuals
Manual 68 pages 52.71 Kb
Top Page Image Contents