Information Technology Reference
In-Depth Information
Table10-10 SDLC: Client Cannot Connect to Host over Router Running SDLLC (continued)
Possible Problem
Solution
XID
2
not sent by
router
1.
With the
debug sdllc
and
debug llc2 packet
privileged exec
commands enabled on the router, check whether the router is
sending XID frames to the FEP.
Caution:
Because debugging output is assigned high priority in
the CPU process, it can render the system unusable. For this
reason, use
debug
commands only to troubleshoot specific
problems or during troubleshooting sessions with Cisco
technical support staff. Moreover, it is best to use
debug
commands during periods of lower network traffic and fewer
users. Debugging during these periods decreases the likelihood
that increased
debug
command processing overhead will affect
system use.
2.
If the router is sending XID frames to the FEP, proceed to the
next problem in this table.
3.
If the router is not sending XID frames, use the
show
running-config
privileged exec command to view the router
configuration. Make sure that there is an
sdllc xid
interface
configuration command entry present.
4.
If the
sdllc xid
command is not configured on the router, add
it to the configuration. The following is the syntax for the
sdlc xid
command:
sdlc xid
address xid
Syntax description:
•
address
—Address of the SDLC station associated with this
interface.
•
xid
—XID that the Cisco IOS software will use to respond to
XID requests that the router receives. This value must be 4
bytes (8 digits) in length and is specified with hexadecimal
digits.
Example:
The following example specifies an XID value of 01720002 at
address C2:
interface serial 0
sdlc xid c2 01720002
