Information Technology Reference
In-Depth Information
Table10-11 SDLC: Sessions Fail over Router Running STUN (continued)
Possible Problem
Solution
No reply to
SNRMs or XIDs
1.
Use the
show stun
command to see whether the peers are
open. If the peers are not open, see the first problem in this
table.
2.
If the peers are open, use the
debug stun packet
privileged
exec command on the remote end. Check for SNRMS or
XIDs from the primary arriving as NDI packets.
3.
If SNRMs or XIDs are not arriving, refer to the preceding
problem in this table.
4.
If SNRMs or XIDs are arriving, make sure that the core
router is sending UA or XID responses as SDI packets.
5.
If the router is not sending responses, there might be a link
problem. Refer to the problem “SDLC physical or link layer
problem,” later in this table.
6.
If the router is sending responses, use the
debug stun packet
command to see whether the UA or XID responses are
getting back to the primary as SDI packets.
7.
If the responses are not getting back to the primary, use the
show running-config
privileged exec command to make
sure that the stun route and other STUN configuration
commands are properly configured on the remote router. The
following is the syntax for the
stun route
command:
stun route
address
address-number tcp ip-address
[
local-ack
]
[
priority
] [
tcp-queue-max
]
Syntax description:
address-number
—Is a number that conforms to TCP
addressing conventions
•
ip-address
—Gives the IP address by which this STUN peer
is known to other STUN peers that are using the TCP as the
STUN encapsulation
•
