Cisco Systems 78-16845-01 Data Inconsistency, Connection Inconsistency Between the Switch and GUI

Page 129

Appendix J Troubleshooting

J.10.13 Miscellaneous Problems

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

J.10.13.2 Data Inconsistency

This section includes the following information:

•J.10.13.2.1 Connection Inconsistency Between the Switch and GUI, page J-129

•J.10.13.2.2 Inconsistent Connection Status, page J-132

•J.10.13.2.3 Inconsistent Connection Secondary Status, page J-132

•J.10.13.2.4 Incomplete Connections, page J-133

J.10.13.2.1 Connection Inconsistency Between the Switch and GUI

This section discusses strategies for debugging inconsistencies between the switch and the CTM GUI. The inconsistencies discussed 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; for example, you might look at the system and suddenly realize there is an inconsistency.

This section gives a list of steps to try to determine more precisely the cause of the inconsistency. These steps should be performed in order:

1.Verify the node's sync states

2.Isolate the connection inconsistency by using a database query

3.Isolate the connection inconsistency by using a message flow

Step 1 Check the node’s state after startup. If the node is in an abnormal state, it can result in incorrect counts or the presence of incomplete connections.

a.Determine if sync-up has been completed.

b.If the system has declared sync-up, use the CTM CLI command selnd to verify that the nodes on which you see the inconsistency are in mode 3. The second-to-last column identifies the mode for a given node.

Step 2 Check the user_connection table and the segment tables for problems. The information displayed on the Connection Manager GUI is taken directly from the user_connection table. The Connection Manager is rarely the problem. This procedure uses database access queries to help isolate the problem. If the problem is found in the user_connection table and the segment tables are incorrect, the problem is usually in the EM. If the user_connection table is wrong but the segment tables are correct, you will need to continue with the investigation before you can determine a root cause.

 

 

Cisco Transport Manager Release 6.0 User Guide

 

 

 

 

 

 

 

78-16845-01

 

 

J-129

 

 

 

 

 

Page 128 Page 130
Image 129
Page 128 Page 130
Contents Troubleshooting Conditions that Affect CTM Server Performance Server ProblemsCTM Server Does Not Respond Cannot Connect to the CTM Server NE Connection State Is Listed as Unavailable Launching Tables Results in Database Errors Snmp Traps Are Not Forwarded from NEsTrap Port Is Unavailable Performance Monitoring Data Is Not Displayed Problems with ONS 15530 and ONS 15540 ConfigurationCTC-Based NE Is Not Discovered CTC-Based NE Is Not ReachableONS 15501, ONS 15540, or ONS 15530 Is Not Reachable Circuits Are Not Displayed Circuit State for Monitor Circuits Reads Duplicate IDNE Model Type Appears as Unknown Memory Backup, Memory Restore, or Software Download Fails Cannot Copy CTC Binary to the CTM ServerGetinfo.sh Script Fails Database Is Not Available Using the get nestate CommandDatabase Timeout Occurs Are the CTM Client and the CTM Server Connected?Cannot Log In as Provisioner or Operator Model Index Is Unknown Cannot Authenticate User Message AppearsCannot Delete an NE CTC Fails to StartAdded a New Software Version to the Wrong NE Cannot Delete a Subnetwork Cannot Move an NE Between SubnetworksCannot Schedule Jobs Bandwidth-Intensive Operations Are Blocked NE Displays Incorrect Configuration Management DataCannot Customize the Network Map Snmptrap How Do I Collect Thread Dumps?Click OK Client Debug Messages How Do I Replace the Alarm Interface Panel?CTM GateWay/TL1 Problems Cisco CRS-1 and Catalyst 6509 Problems CTM Does Not Receive Traps from the Catalyst Cat6509 enable# set snmp trap enable allSyslog CTM Does Not Receive syslog Events from the CatalystCTM Does Not Collect Historical PM Data for the CRS-1 Memory Backup or Restore Fails for the CRS-1 Click NE Service Cannot Delete an Out-of-Service NE from CTM How Do I Configure Telnet on the CRS-1?How Do I Configure SSH on the CRS-1? How Do I Load a Software Image on the Catalyst 6509? How Do I View the Snmp Configuration on the Catalyst 6509?Output is similar to the following example CTM Cannot Discover an XR 12000 Node Reporting XR 12000 Issues5 XR 12000 PM Collection Issues 4 XR 12000 Alarm and Event Reporting Issues7 XR 12000 NE Explorer Applications Are Disabled 6 XR 12000 BGP and CDP Neighbor Discovery IssuesDiscovery Issues at Startup Discovery MechanismNo Nodes Are Discovered Node Name Is Incorrect in the Database Output of the switch CLI, selnd, and dbndsNode IP Is Incorrect in the Database Node Alarm Is Shown Incorrectly in the DatabaseCTM State Is Incorrect Reachable Node Is Shown as UnreachableDiscovery Issues at Runtime Collect the output of the switch CLI, selnd, and dbnds Equipment Management Problems Node Mode Remains Ls -ltr *.9 SMCARD01SRM.CF SMCARD01RPM.CF Node Resync Mode IsEMCSnmpFunccProcFuncGenNodeBulkFile1 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 All the Cards Under a Node Are Missing Network Element Discovery IssuesCisco Transport Manager Release 6.0 User Guide 78-16845-01 Appendix J Troubleshooting Alarm Processing Basics Figure J-2 Client/Server Architecture for Alarm Components XML Schema for Alarm RulesFigure J-3 Correlated Alarm Rule Diagram Figure J-5 Transient Alarm Rule Diagram Alarm Severity and Object SeverityCisco 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 Basics Chassis View ProblemsCard Not Displayed in the Chassis View Lines Not Displayed in the Chassis ViewHIST, CBRX, and Cbtx Status Not Updated in MGX Nodes Ethernet Status Not Updated on PXM CardsRPM Card Status Not Updated 10.6.4 DCA/DCB Status Not Displayed on PXM CardsConfiguration Center Framework Configuration Center ManagementLines Not Selectable Wrong Tooltip Is DisplayedChoose Tools Configuration Center from any application Cannot Launch the Configuration CenterAppendix J Troubleshooting Configuration Center Management Element Tab-Internal Frame Does Not Launch Element Management-Drag and Drop Within Configuration CenterCross Application-Configuration Center as Drag Source Appendix J Troubleshooting Configuration Center Management XML Parsing Error Configuration Center-Element ManagementDetails, Create, Delete, and Refresh Buttons Are Not Enabled Snmp No Data ErrorSnmp Set Error Snmp Timeout ErrorObject Not Found In Tree View Error Element Data Inconsistent with Switch Connection Management Problems Configuration Center GUI-Framework IssuesConfig Server Reports Error Messages Appendix J Troubleshooting Connection Management Problems Appendix J Troubleshooting Connection Management Problems Cross Application-Connection List as Drag Source Configuration Centers Connection Tab Does Not Respond Configuration Center GUI-CM Server-Reported ErrorsDATABASEERRORDatabase error %s Appendix J Troubleshooting Connection Management Problems Cmsvr Errors Cannot Create One-Segment Hybrid Unsupported Service Type-General node-slot-port-version TestConn or TestDelay Failed with Switch Error Cmsvr-Connection Diagnostic IssuesConnection Trace Failures Connection Up/Down/Reroute FailedCmgrd Figure J-6 Connection Management Subsystem High-Level Connection Management Subsystem ArchitectureCmgrd-Sdbroker Errors Related key index entries cmgrd, sdbroker, vpi/vci Appendix J Troubleshooting Connection Management Problems 100 Cmgrd Errors101 102 103 Cmgrd-Switch Errors104 105 106 107 Diagnostics Center Problems108 Diagnostics Center Framework109 Cannot Launch Diagnostics Center110 Diagnostics Center Does Not Respond GUI Is Grayed Out Drop Target Displays Incorrect Object or Object Data111 112 Diagnostics Center Server-Specific IssuesXML Parser Error Snmpcommtimeout Error While Polling MIB Objects113 Node Resync Fails Node Sync-Up Status Are Not Shown in the Diagnostics CenterPolling of Real-Time Counters Fails 114Some Real-Time Counters Are Not Shown Unable to Start, Stop, or Modify Bert Operations115 Cannot Perform Connection Diagnostics Unable to Start/Stop IMA Link Test Patterns116 PM Collection Issues Performance Management Collection and Parsing ProblemsMiscellaneous Issues or Problems in Diagnostics Center Pmcollector-Generic Troubleshooting118 119 PM Collection Fails for the Node-Log File Shows Snmp failed120 PM Collection Fails for the Node-Log File Shows Ftp failedPM Parsing Issues Statistics Report ProblemsStatsParser-Generic Troubleshooting 121Statistics Report You See FDNs for Other Entities when You Generate a ReportYou Collected Data but You See No Data Available You Generated a Report but Do Not See Data for a Long TimeUtilization Report Value Is Greater than 100% Service Agent ProblemsRtmProxy 123Registration with RtmProxy Failed Not Receiving Any Traps124 Manager Gets Deregistered Audit Trail Logging Mechanism ProblemsNodal Community Strings Do Not Work 125AuditLogger.conf Usage Miscellaneous ProblemsAudit Trail Log File Naming Convention 126Config Change or Provisioning Activity Not Reflected on CTM Nodes Stay in Mode 1 After ColdStart10.13.1 NTS 127128 How To Interpret NTS LogConnection Inconsistency Between the Switch and GUI Data Inconsistency129 130 Each output line is similar to this131 Process ID of the sdbroker will be returnedInconsistent Connection Status Inconsistent Connection Secondary Status132 133 Incomplete ConnectionsFTP Username and Password Generic TroubleshootingCTM FTP Daemon FTP Daemon OverviewCwmftpd-File Not Available On Switch FTP Sessions in Switch135 10.13.3.7 421 Session Limit Reached 10.13.3.8 499 Session Limit Reached136 Failed to Acquire Session After All Retries Failed to Acquire a Session with a SwitchGeneral Log Information 137138
Related manuals
Manual 68 pages 52.71 Kb
Top Page Image Contents