Fault description, Fault analysis, Troubleshooting procedure – Nortel Networks 8000 User Manual
Page 364
Attention! The text in this document has been recognized automatically. To view the original document, you can use the "Original mode".
8 Frame relay configuration
Nortel Secure Router 8000 Series
Configuration -WAN Access
8.15.2 Failure of pinging the peer after configuring the frame relay
Fault description
Failed to ping the peer after the frame relay switch is configured.
Fault analysis
The possible causes are:
•
The exchange of the DLCI fails.
•
The two ends cannot learn the host route to the peer in time.
Troubleshooting procedure
Do as follows on the routers:
Step 1
Check the FR switching information by using the
display fr dlci-switch
command. If FR
switch is not Active, run the
fr dlci-switch
command to reset the DLCI switch.
Step 2
Check whether the DLCI values are the same at both sides by using the
display fr dlci-switch
command. If the values are different, run the
fr dlci
command to reset the DLCI value and the
fr dlci-switch
command to reset the DLCI switch.
Step 3
Check whether the incoming interface and the outgoing interface are the same one by using
the
display current-configuration interface
command if the routed switch is used. If they
are the same, run the
fr dlci-switch
command to configure them to be different.
Step 4
Check the address mapping on the FR interfaces of both ends by using the
display fr
map-info
command. If no mapping appears, run the
shutdown
and the
undo shutdown
commands to restart the interfaces, or run the
reset fr inarp
command to clear the original
mappings of dynamic addresses. Then, the interfaces can dynamically learn the address
mapping.
--- End
8.15.3 Failure of pinging the peer after configuring the frame relay
switch over IP
Fault description
Failed to ping the peer after the frame relay switch over IP is configured.
Fault analysis
The possible causes are:
•
The network fails to work.
•
The tunnel is not configured correctly.
•
In the configured FR PVC, DLCI values of the tunnel interfaces are di^erent.
8-74
Nortel Networks Inc.
Issue 5.3 (30 March 2009)