Information Technology Reference
In-Depth Information
Table10-11 SDLC: Sessions Fail over Router Running STUN (continued)
Possible Problem
Solution
SNRMs or XIDs
not sent
Use the
show stun
command to see whether the peers are
open. If the peers are not open, see the preceding problem in
this table.
1.
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.
2.
If SNRMs or XIDs are arriving, proceed to the next problem
in this table.
3.
If SNRMS or XIDs are not arriving, use the
debug stun
packet
command on the core router to see whether SNRMs
or XIDs are being sent.
4.
continues
SNRMs or XIDs
not sent
(continued)
5.
If the core router is not sending SNRMs or XIDs, make sure
that the physical and link layers are operating properly. See
the problem “SDLC physical or link layer problem,” later in
this table.
6.
If the core router is sending SNRMs or XIDs, use the
show
running-config
privileged exec command to make sure that
the
stun route
command is properly configured on the
router.
7.
Check to make sure that no other network problems are
occurring, such as interface drops, buffer misses, overloaded
Frame Relay switches, and IP routing problems.
