System information

Troubleshooting IBM 10-243
CIP: CLAW Connection Does Not Come Up
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.
Table 10-13 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table 10-13 CIP: CLAW Connection Does Not Come Up
SDLC physical or
link-layer problem
Step 1 Use the show interfaces exec command on the link connecting to the primary
device. Make sure that the interface and line protocol are both up.
Step 2 If the interface or line protocol is not up, make sure the devices are powered up and
connected correctly. Check the line to make sure it is active. Check for clocking,
address misconfigurations, correct NRZ or NRZI specifications, and so forth.
Step 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.
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.
Possible Problem Solution
TCP/IP not running
on host
Step 1 Check whether TCP/IP is running on the host.
Step 2 If TCP/IP is not running, start it.
Possible Problem Solution