Cisco BTS 10200 Troubleshooting Manual page 184

Hide thumbs Also See for BTS 10200:

Table of Contents

Troubleshooting Call Processing Alarms

Check statistics for ethernet interface(s) on the call agent side while looking for any abnormal

queue/input/output errors/collisions. For example, to check stats on bge0 interface:

# netstat -i -I bge0

Ipkts Ierrs Opkts Oerrs Collis Queue

The packets queued (Queue) that cannot be transmitted should be 0. If not, it is possible that a cable or

ethernet interface is defective.

The input errors (Ierrs) and the output errors (Oerrs) should be close to 0. High input errors could

indicate that the network is saturated, host overload, or physical network problem. High output errors

could indicate a saturated local network or a bad physical connection.

Check statistics for ethernet interface(s) on the switch side. Look for abnormal input/output errors,

cyclic redundancy check (CRC), frame errors. For a description of the output of "show interface fast

ethernet", refer to:

http://www.cisco.com/en/US/customer/docs/ios/12_2/interface/command/reference/irfshoin.html

Paste the output of "show interfaces" to the Cisco output interpreter for further analysis of the interfaces.

https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl

Check the physical cable, the cable connectors, and the cable connections.

Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x

Call Processing Troubleshooting

Chapters

Table of Contents