System information

Troubleshooting IBM
Book Title
10-242
No reply to SNRMs or
XIDs
Step 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.
Step 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.
Step 3 If SNRMs or XIDs are not arriving, refer to the preceding problem in this table.
Step 4 If SNRMs or XIDs are arriving, make sure that the core router is sending UA or
XID responses as SDI packets.
Step 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.
No reply to SNRMs or
XIDs
Step 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.
Step 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—Number that conforms to TCP addressing conventions.
• ip-address—IP address by which this STUN peer is known to other STUN peers
that are using the TCP as the STUN encapsulation.
• local-ack—(Optional) Enables local acknowledgment for STUN.
• priority—(Optional) Establishes the four levels used in priority queuing: low,
medium, normal, and high.
• tcp-queue-max—(Optional) Sets the maximum size of the outbound TCP queue
for the SDLC link.
Example:
In the following example, a frame with a source-route address of 10 is propagated
using TCP encapsulation to a device with an IP address of 131.108.8.1:
stun route address 10 tcp 131.108.8.1
Step 8
Check to make sure that there are not other network problems occurring, such as
interface drops, buffer misses, overloaded Frame Relay switches, and IP routing
problems.
Step 9 If packets are passed end-to-end in both directions, check end station
configurations, duplex settings, configurations, and so forth.
Possible Problem Solution