Failed To Ping The Other Side With X.25 On Both Sides Being Up; Troubleshooting X.25 Configuration; Of Two Sides Always Being Down With Lapb Of Two Sides Being Up - 3Com MSR 50 Series Configuration Manual

Failed to Ping the Other
Side with X.25 on Both
Sides Being Up
Troubleshooting X.25
Configuration
X.25 of Two Sides
Always Being Down
with LAPB of two sides
Being Up
Failed to Ping the Other
Side with X.25 on Both
Sides Being Up
Troubleshooting
Enable the debugging on both sides. If one side sends SABM frames and the other
sends FRMR frames cyclically, the two sides are working in the same mode (DTE or
DCE). Change the working mode of one side to solve it.
Symptom
Despite X.25 is up on both sides, the other side can not be pinged.
Analysis
The maximum length of frames set at one side is too small.
Troubleshooting
Enable the debugging on both sides. If one side discards incoming frames without
delivering them to the upper layer, it indicates the maximum length of frames set
for this side is too small. Change the frame length configuration of this side.
Assume that the layer 2 LAPB of X.25 is up.
Symptom
X.25 of two sides is always down although LAPB of two sides is up.
Analysis
A possible reason is that the two sides are working in the same mode (DTE or
DCE).
Troubleshooting
Change the working mode of one side.
Symptom
Despite X.25 is up on both sides, the other side can not be pinged.
Analysis
The following are possible causes:
The local X.121 address is not configured.
■
The address mapping of the two sides is not configured on the local end.
■
The peer's X.121 address is not configured.
■
The address mapping of the two sides is not configured on the remote end.
■
The channel range is not correct.
■
Some wrong user facilities are carried.
■
Troubleshooting
If addresses are not correct, change them to the correct ones.
■
For the last two causes, you need contact the network administration to get
■
the correct channel range and user facilities.

Troubleshooting X.25 Configuration

341