Advertisement
Check for clocking problems. Enter the privileged EXEC command show controllers t1
Step 5
or show controllers e1 command to check for slip errors, as shown in the following
excerpt from the command output:
.
.
.
Data in current interval (819 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 1:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 2:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 3:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
.
.
.
A few slip errors may not indicate a problem with clocking. However, if there are
numerous errors, especially incrementing numbers of errors, you should check the
following possibilities:
— The network clocks are not set to the same clock rate. Enter the show
network-clocks command on the devices to ensure that these clock rates match.
— The Cisco MC3810 multiservice access concentrators may not be using the same
clock source. For example, if there are two back-to-back Cisco MC3810
multiservice access concentrators and one is using an internal clock source, the
other must use the line clock source in order to obtain clocking from the same
device. Enter the privileged EXEC commands show network-clocks and show
controllers t1 or show controllers e1 to see the clock source settings. For
additional guidance, see Chapter 4, "Configuring Synchronized Clocking," in
Cisco MC3810 Multiservice Access Concentrator Software Configuration Guide.
Check the functionality of the Service-Specific Connection-Oriented Protocol (SSCOP).
Step 6
Enter the privileged EXEC show sscop command. See the following excerpt from the
command output:
router# show sscop
SSCOP details for interface ATM0
Current State = Data Transfer Ready
Interpretation of the command output requires familiarity with SSCOP, so unless you
understand the protocol, just use the command to ensure that the protocol is in a state of
readiness, as shown above. If you need to make changes, see the Cisco IOS Release 12.0
documents, Wide-Area Networking Configuration Guide and Wide-Area Networking
Command Reference.
If you plan to adjust SSCOP parameters, you may wish to complete the rest of the
Note
troubleshooting steps before taking this route.
Verifying Voice Ports and Voice Dial Peers
Voice over ATM Switched Virtual Circuits on the Cisco MC3810 17
Advertisement
