user manual

J-48

Cisco Transport Manager Release 6.0 User Guide

78-16845-01

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-53 for 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.