Information Technology Reference
In-Depth Information
Table10-11 SDLC: Sessions Fail over Router Running STUN (continued)
Possible Problem
Solution
SDLC physical or
link layer problem
1.
Use the
show interfaces
exec command on the link
connecting to the primary device. Make sure that the
interface and the line protocol are both up.
2.
If the interface or line protocol is not up, make sure that the
devices are powered up and connected correctly. Check the
line to make sure that it is active. Check for clocking,
address misconfigurations, correct NRZ or NRZI
specifications, and so forth.
3.
Try slowing the clock rate of the connection. Use the
clock
rate
interface configuration command to configure the clock
rate for the hardware connections on serial interfaces such as
NIMs and interface processors to an acceptable bit rate.
The following is the syntax of the
clock rate
command:
clock rate
bps
Syntax description:
bps
—Desired clock rate in bits per second: 1200, 2400,
4800, 9600, 19200, 38400, 56000, 64000, 72000, 125000,
148000, 250000, 500000, 800000, 1000000, 1300000,
2000000, 4000000, or 8000000
•
SDLC physical or
link layer problem
(continued)
Example:
The following example sets the clock rate on the first serial
interface to 64000 bits per second:
interface serial 0
clock rate 64000
For more information about troubleshooting SDLC physical and
link-layer problems, see the section “SDLC: Router Cannot
Communicate with SDLC Device,” earlier in this chapter.
CIP: CLAW Connection Does Not Come Up
Symptom:
Common Link Access for Workstations (CLAW) connections do not come up properly over
a Channel Interface Processor (CIP). The output of the
show extended channel slot/port statistics
exec
command shows N for CLAW connections, indicating that they are down.
