Cisco Systems 78-16845-01 appendix Appendix J Troubleshooting Equipment Management Problems

Page 48

Appendix J Troubleshooting

J.10.4 Equipment Management Problems

•EMC_DBProperty_Card_c::ComposeNMSMsg

•EMC_DBProperty_Line_c::ComposeNMSMsg

•EMC_DBProperty_AusmPort_c::ComposeNMSMsg

•EMC_DBProperty_CesmPort_c::ComposeNMSMsg

•EMC_DBProperty_FrPort_c::ComposeNMSMsg

•EMC_DBProperty_RpmPort_c::ComposeNMSMsg

•EMC_DBProperty_SvcPort_c::ComposeNMSMsg

•EMC_DBProperty_VtPort_c::ComposeNMSMsg

•EMC_DBProperty_Aps_c::ComposeNMSMsg

•EMC_DBProperty_ImaGroup_c::ComposeNMSMsg

•EMC_DBProperty_ImaLink_c::ComposeNMSMsg

•EMC_DBProperty_LineDist_c::ComposeNMSMsg

•EMC_DBProperty_AU4TUG3_c::ComposeNMSMsg

•EMC_DBProperty_Ctrlr_c::ComposeNMSMsg

•EMC_DBProperty_LicenseInUse_c::ComposeNMSMsg

•EMC_DBProperty_MfrBundle_c::ComposeNMSMsg

•EMC_DBProperty_MfrLink_c::ComposeNMSMsg

•EMC_DBProperty_Peripheral_c::ComposeNMSMsg

•EMC_DBProperty_RedCard_c::ComposeNMSMsg

•EMC_DBProperty_Sensor_c::ComposeNMSMsg

Note Database data will not be sent to NMServer during the initial node resync. It is after the initial resync that ooemc starts sending updated or newly provisioned database data to NMServer. Each ooemc log message from grep contains detailed information on the identity of the NE object and the required fields from the corresponding database table. The following is an example of NMServer message for line tables:

ooemc10.24370.log.old.5:( 24370: 4) 23:15:17 INFO: N0:C7:B2:L2

<EMC_DBProperty_Line_c::ComposeNMSMsg> (MODIFY::LINE) aNMSEvent.node:0 type:4 subType:1 lpbkType:1 alarmState:1 adminState:1 sectStatus:6 pathState:2

In this example, the identity of the NE object is N0:C7:B2:L2, which is the line with node ID=0, slot=7, bay=2, and line#=2. The database operation is update. The rest of the message shows the values of the required fields from the line table.

Step 4 If grep returns log messages that indicate matched data, then you need to continue investigation on the NM server. See J.10.5.1 CTM Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Basics, page J-53for information on nmController.

Defect information—Collect ooemc and NMServer log files from the /opt/svplus/log directory.

Possible alternative workaround—Manually resync the node. If the problem persists, perform a coldstart. If the problem is still not resolved, collect the log files and report the problem.

Cisco Transport Manager Release 6.0 User Guide

 

J-48

78-16845-01

 

 

 

Page 47 Page 49
Image 48
Page 47 Page 49
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 Launching Tables Results in Database Errors Snmp Traps Are Not Forwarded from NEsTrap Port Is Unavailable Problems with ONS 15530 and ONS 15540 Configuration Performance Monitoring Data Is Not DisplayedCTC-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 Using the get nestate Command Database Is Not AvailableDatabase Timeout Occurs Are the CTM Client and the CTM Server Connected?Cannot Log In as Provisioner or Operator Cannot Authenticate User Message Appears Model Index Is UnknownCannot 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 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 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 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 Issues at Startup Discovery MechanismNo 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 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 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 Diagnostics Center Does Not Respond GUI Is Grayed Out Drop Target Displays Incorrect Object or Object Data111 Diagnostics Center Server-Specific Issues 112XML Parser Error Snmpcommtimeout Error While Polling MIB Objects113 Node Sync-Up Status Are Not Shown in the Diagnostics Center Node Resync FailsPolling 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 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 123Registration with RtmProxy Failed Not Receiving Any Traps124 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 128Connection Inconsistency Between the Switch and GUI Data Inconsistency129 Each output line is similar to this 130Process ID of the sdbroker will be returned 131Inconsistent Connection Status Inconsistent Connection Secondary Status132 Incomplete Connections 133Generic Troubleshooting FTP Username and PasswordCTM 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 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