Cisco Systems 78-16845-01 appendix Database Table Population Through Traps and Snmp Upload

Page 49

Appendix J Troubleshooting

J.10.4 Equipment Management Problems

J.10.4.9 CTM Database and Switch Data Inconsistency Issues After Node Provisioning for MGX

This section includes the following information:

•J.10.4.9.1 Database Table Population Through Traps and SNMP Upload, page J-49

•J.10.4.9.2 Switch Data Does Not Match CTM Database Table After Node Provisioning, page J-49

J.10.4.9.1 Database Table Population Through Traps and SNMP Upload

Except for node and/or card resync, another mechanism that CTM ooemc uses to populate the database table entries is through trap processing followed by SNMP upload, if necessary. You can provision the switch through switch CLI, CTM GUI, or CTM service agents. All three cases will involve trap processing and SNMP upload on ooemc. Only connections can be provisioned by the CTM CM GUI. Other provisioning, such as line and port, have to go to CTM service agents. The MGX switch CLI can do all.

J.10.4.9.2 Switch Data Does Not Match CTM Database Table After Node Provisioning

After switch provisioning through the switch CLI, CTM GUI, or CTM service agents, the switch data does not match the CTM database.

Step 1 If the issue is caused by a trap (for example, if you provision a connection on a switch or through CTM GUI or service agent, and CTM does not populate the database entry or the information in the database entry does not match the switch data), it is possible that CTM did not receive the trap, or that it received the trap but the trap is buffered in the ooemc trap queue, and trap processing has been delayed. On the other hand, if the data in the CTM database is not correct, it is also possible that the SNMP upload failed to upload correct data. Study the log files to understand the root cause of the inconsistency problem.

Step 2 To determine whether or not a trap has been received and processed, there are key words in the ooemc log files that you can grep. For example, to find out the channel traps from node_id=4, slot=6, vpi=1, and vci=326, you can grep "TRAPLIST" as shown in the following:

cwmult60% grep "TRAPLIST: N4:" ooemc* grep

"Channel Trap" grep

"C6" grep "vpi

1

vci

326"

 

 

 

 

 

 

 

 

 

ooemc10.5760.log.old.55:(

5760: 10)

23:21:12

INFO: TRAPLIST: N4: Channel Trap 60310

from

C6 B2

L1 P20 Ch299 ifIndex 17176597

vpi 1 vci 326 upCntr

0

vpcFlag

2 operS 1 alarm 67

 

ooemc10.5760.log.old.55:(

5760: 10)

23:21:12

INFO: TRAPLIST: N4: Channel Trap 60310

<

 

PROCESSED > from C6 B2 L1

P20 Ch299

ifIndex 17176597 vpi

1

vci 326

upCntr 0 vpcFlag

2

 

operS

1 alarm 67

 

 

 

 

 

 

 

 

ooemc10.5760.log.old.73:(

5760: 10)

23:23:48

INFO: TRAPLIST: N4: Channel Trap 60310

from

C6 B2

L1 P20 Ch299 ifIndex 17176597

vpi 1 vci 326 upCntr

0

vpcFlag

2 operS 1 alarm 66

 

For other kinds of traps, you can use the following key words to supplement "TRAPLIST" in your grep statement:

•Port Trap

•RscPart Trap

•Svc Trap

•SonetLn Trap

•SctCard Trap

•SonetPath Trap

•FunMod Trap

•LineMod Trap

Cisco Transport Manager Release 6.0 User Guide

 

78-16845-01

J-49

 

Page 48 Page 50
Image 49
Page 48 Page 50
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 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 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 Node Resync Fails Node Sync-Up Status Are Not Shown in the Diagnostics CenterPolling 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 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 123Not Receiving Any Traps Registration with RtmProxy Failed124 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 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 Username and Password Generic TroubleshootingCTM 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 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