H3C Technologies H3C SR8800 - Manual (Page 71)

63
[RouterA] interface Serial 2/1/8:0
[RouterA-Serial2/1/8:0] link-protocol fr
[RouterA-Serial2/1/8:0] fr interface-type dce
[RouterA-Serial2/1/8:0] quit
# Configure the IP address of the subinterface and local virtual circuit.
[RouterA] interface Serial 2/1/8:0.1 p2p
[RouterA-Serial2/1/8:0.1] ip address 202.38.13.251 255.255.255.0
[RouterA-Serial2/1/8:0.1] fr dlci 100
2. Configure Router B:
# Set the link layer protocol on the interface to frame relay and interface type to DTE.
system-view
[RouterB] interface Serial 2/1/8:0
[RouterB-Serial2/1/8:0] link-protocol fr
[RouterB-Serial2/1/8:0] quit
# Configure IP address of the subinterface and local virtual circuit.
[RouterB] interface Serial 2/1/8:0.1 p2p
[RouterB-Serial2/1/8:0.1] ip address 202.38.13.252 255.255.255.0
[RouterB-Serial2/1/8:0.1] fr dlci 100
Troubleshooting frame relay
Symptom 1:
The physical layer is in down status.
Solution:
• Check whether the physical line is normal.
• Check whether the remote router runs properly.
Symptom 2:
The physical layer is already up, but the link layer protocol is down.
Solution:
• Make sure that both local router and remote router have been encapsulated with frame relay
protocol.
• If two routers are directly connected, check the local router and remote router to make sure that one
end is configured as frame relay DTE interface and the other end as frame relay DCE interface.
• Make sure that the LMI protocol type configuration at the two ends is the same.
• If the conditions are satisfied, use the debugging lmi command to enable the monitoring function
for the frame relay LMI messages to see whether one Status Request message corresponds to one
Status Response message. If not, it indicates the physical layer data is not received/sent correctly.
Check the physical layer.
Symptom 3:
The link layer protocol is up, but the remote party cannot be pinged.