Cisco Systems 78-16845-01 J.10.4.9 CTM Database and Switch Data Inconsistency Issues After Node Provisioning for MGX

J-49
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.4 Equipmen t 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