Cisco Systems 78-16845-01 appendix 10.13.1 NTS, Nodes Stay in Mode 1 After ColdStart, 127

Page 127

Appendix J Troubleshooting

J.10.13 Miscellaneous Problems

•J.10.13.2 Data Inconsistency, page J-129

•J.10.13.3 CTM FTP Daemon, page J-134

J.10.13.1 NTS

This section includes the following information:

•J.10.13.1.1 Nodes Stay in Mode 1 After ColdStart, page J-127

•J.10.13.1.2 Config Change or Provisioning Activity Not Reflected on CTM, page J-127

•J.10.13.1.3 How To Interpret NTS Log, page J-128

J.10.13.1.1 Nodes Stay in Mode 1 After ColdStart

The nts cannot manage a particular switch successfully. In other words, nts declared the switch to be in the Unreachable or Unregistered state. As a result, nts notified its clients with a LINK_DOWN message. The nts declares a node to be in OK state if it is in the Trap Manager List of the node and can successfully perform SNMP operations on the node.

Step 1 Check the PING reachability. Run ntsControl and enter ni at the prompt. Then, enter q to exit ntsControl. This shows the nts node information. A node has to be in OK state so that CTM can start syncing it up. If the node is not in OK state, first thing to check is PING. Run ping <ip_address>. If the PING succeeded, go to step 2. Otherwise, fix the network reachability between the switch and the CTM station.

Step 2 Check the CTM IP address configuration This only applies to CTM workstation with multiple IP interfaces. The NMS_IP_ADDRESS setting in /opt/svplus/config/svplus.conf has to match the interface users chose for CTM. To check the IP interfaces, run ifconfig -a. CTM stations with only one IP interface does not need to have the NMS_IP_ADDRESS setting.

Step 3 Check the Trap Manager List on the switch. SSH or Telnet to the switch. Run dsptrapmgr command to show the Trap Manager List. Check whether the CTM is in the table. If so, go to step 4. Otherwise, if the table is already full, remove unwanted entries with deltrapmgr command. The nts should be able to register the CTM into the table within a few minutes. If not, go to step 4.

Step 4 Check the SNMP community strings. In case the SNMP community string on the switch has been changed from the default setting, the SNMP community string on the CTM have to match the new ones on the switch. The SNMP community string on the switch can be viewed with dspsnmp command. The setting on the CTM can be viewed in Domain Explorer.

Defect Information—Collect the following information for further analysis:

•Selnd and dbnds command output

•Nts log and EM log of the node in question.

Possible alternative workaround—If community strings do not match, run the CTM Configurator GUI to correct them. (/opt/svplus/java/bin/runConfigurator)

Related key index entries: nts, traps

J.10.13.1.2 Config Change or Provisioning Activity Not Reflected on CTM

The nts does not receive any traps from a particular switch when it actually had generated traps.

 

 

Cisco Transport Manager Release 6.0 User Guide

 

 

 

 

 

 

 

78-16845-01

 

 

J-127

 

 

 

 

 

Page 126 Page 128
Image 127
Page 126 Page 128
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 Snmp Traps Are Not Forwarded from NEs Launching Tables Results in Database ErrorsTrap Port Is Unavailable Performance Monitoring Data Is Not Displayed Problems with ONS 15530 and ONS 15540 ConfigurationCTC-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 Database Is Not Available Using the get nestate CommandAre the CTM Client and the CTM Server Connected? Database Timeout OccursCannot Log In as Provisioner or Operator Model Index Is Unknown Cannot Authenticate User Message AppearsCTC 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 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 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 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 Mechanism Discovery Issues at StartupNo 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 View10.6.4 DCA/DCB Status Not Displayed on PXM Cards Ethernet Status Not Updated on PXM CardsHIST, CBRX, and Cbtx Status Not Updated in MGX Nodes RPM Card Status Not UpdatedWrong Tooltip Is Displayed Configuration Center ManagementConfiguration Center Framework Lines Not SelectableChoose 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 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 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 Drop Target Displays Incorrect Object or Object Data Diagnostics Center Does Not Respond GUI Is Grayed Out111 112 Diagnostics Center Server-Specific IssuesSnmpcommtimeout Error While Polling MIB Objects XML Parser Error113 114 Node Sync-Up Status Are Not Shown in the Diagnostics CenterNode Resync Fails Polling of Real-Time Counters FailsUnable 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 Pmcollector-Generic Troubleshooting Performance Management Collection and Parsing ProblemsPM Collection Issues Miscellaneous Issues or Problems in Diagnostics Center118 119 PM Collection Fails for the Node-Log File Shows Snmp failed120 PM Collection Fails for the Node-Log File Shows Ftp failed121 Statistics Report ProblemsPM Parsing Issues StatsParser-Generic TroubleshootingYou Generated a Report but Do Not See Data for a Long Time You See FDNs for Other Entities when You Generate a ReportStatistics Report You Collected Data but You See No Data Available123 Service Agent ProblemsUtilization Report Value Is Greater than 100% RtmProxyNot Receiving Any Traps Registration with RtmProxy Failed124 125 Audit Trail Logging Mechanism ProblemsManager Gets Deregistered Nodal Community Strings Do Not Work126 Miscellaneous ProblemsAuditLogger.conf Usage Audit Trail Log File Naming Convention127 Nodes Stay in Mode 1 After ColdStartConfig Change or Provisioning Activity Not Reflected on CTM 10.13.1 NTS128 How To Interpret NTS LogData Inconsistency Connection Inconsistency Between the Switch and GUI129 130 Each output line is similar to this131 Process ID of the sdbroker will be returnedInconsistent Connection Secondary Status Inconsistent Connection Status132 133 Incomplete ConnectionsFTP Daemon Overview Generic TroubleshootingFTP Username and Password CTM FTP DaemonFTP 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 137 Failed to Acquire a Session with a SwitchFailed to Acquire Session After All Retries General Log Information138
Related manuals
Manual 68 pages 52.71 Kb
Top Page Image Contents