Frame relay command directory
encapsulation of frame-relay. No
to diable.
encapsulation frame-relay
no encapsulation
frame-relay
parameter:
none
default:
none
command mode:
Interface
configuration mode
explanation:
Use no to
diable encapsulation, which means, back to the encapsulation HDLC mode
Example:
The
following example, configure frame relay encapsulation mode in serial s1/1:
interface s1/1
encapsulation frame-relay
Specify committed
information speed for frame relay virtual circuit.
frame-relay cir bps
parameter:
bps |
Submit information rate, number of bits every
second, default value 64000. |
the value is
one between 1 to 2048000.
default:
64000
command mode:
Interface
configuration mode
explanation:
The
submission rate is confirmed when applying for DLCI.
Example:
Configure
s1/1 port as frame relay, and configure cir as 2048000.
interface s1/1
encapsulation frame-relay
frame-relay cir 2048000
relevant command:
none
Configure
the exchange type of the frame relay.
frame-relay intf-type [dce | dte
| nni]
parameter:
dce |
(optional) connect to the router of the
router or access the server and works under the mode of exchanger. |
dte |
(optional) router or access the server to
work under the mode of connecting into the terminal device of the frame relay
network. This is the default configuration. |
nni |
(optional)
router or access the server to connect to the network under the mode of
exchanger, which means that it supports NNI network connection. |
default:
dte
command mode:
Interface
configuration mode
explanation:
When the
frame relay port connects with the network, normally it will be configured as
DTE, if the router is connected back on back, then one is configured as DTE,
the other will be DCE. If you require double direction LMI process, it should
be configured as NNI. Frame relay standard describes an interface between a
terminal user and a frame relay network, which is named UNI, and the interface
between the neighboring frame relay networks, which are named NNI. The
following chart describes the concept of UNI and NNI.
A PVC
link from port to port consists of many PVC sections. Each PVC section is
separated by one UNI and one NNI or two NNIs. If you want to activate one PVC,
you should activate all PVC sections. The network can be link-shaped. A network
terminal user station connected is called save and draw network, the network
between is called the transfer network. Every network conducts local
allocation, this means that every section of PVC has its dependent DLCI number.
But the DLCI number used on the link of the two neighboring networks should be
the same. NNI and UNI are based on the same standards. In order to provide a
balanced interface, it should provide simultaneously the network and client
process on both sides.
Example:
Configure
s1/1 port as frame-relay, configure the interface as dce
interface s1/1
enca frame-relay
frame-relay intf-type dce
On the
router or access server configured frame relay, if inverse address resolution
protocol is not activated, then use this command to reactivate it.
[no] frame-relay inverse-arp
parameter:
default:
Enable
inverse address resolution protocol (IARP)
command mode:
Interface
configuration mode
explanation:
IARP is the
protocol used to inquire the protocol address on frame relay network. Please
refer to RFC1293 for the implementation of it. It enables the router or access
server which are configured frame relay to discover protocol address related to
virtual circuit.
In frame
relay network, the DLCI of pvc can be regarded as hardware address. The network
establishes a virtual circuit by signal information, it can find out the
protocol address on the other side of the circuit by IARP.
Example:
Configure
the s1/1 port as frame relay and prohibit IARP
interface s1/1
enca frame-relay
no fr inverse-arp
relevant command:
Configure
LMI type. Use command “no frame-relay lmi-type” to
reset to default type value:
[no] frame-relay
lmi-type { q933a | bcisco | ansi}
parameter:
q933a |
ITU-T Q.933 attachment A |
ansi |
The interface type defined by attachment ANSI
T1.617 |
bcisco |
Rev 1 of Group of Four, compatible with Cisco |
default:
Autosense
command mode:
Interface
configuration mode
explanation:
LMI defines the
operation between the user’s device and
frame relay network, it provides the mode or overtime notice of permanent
virtual circuit(PVC). Q933a used the defined process and information in
attachment A of ITU-T Q.933. ansi used the defined process and information in
attachment D of ANSI T1.617. bcisco uses the defined process and information in
Group of Four Rev.#1. The configuration of LMI type is based on the interface
and can be checked by command “show interface”.
Example:
The
following example configures the LMI interface as ANSI attachment D:
interface S1/1
encapsulation frame-relay
frame-relay lmi-type ansi
Configure
local DLCI. Use command no to diable.
frame-relay local-dlci number [cir speed]
no frame-relay local-dlci number
parameter:
number |
Local DLCI |
speed |
CIR rate |
default:
no local DLCI
Default
speed of CIR is 64000
command mode:
Interface
configuration mode
explanation:
Use to
configure usable DLCI when LMI is not configured or has been back-to-back
connected and served as DCE. In other stances, it can be obtained though LMI.
No to delete this DLCI.
Example:
The
following example, configure a no.100 local DLCI:
interface s1/1
frame-relay local-dlci 100
Configure
the status query times before the query of all status information.
frame-relay n391 keep-exchanges
parameter:
keep-exchanges |
Configure the query interval of all mode
information. Range: 1-255. |
default:
Exchange for
six times
command mode:
Interface
configuration mode
explanation:
The interface must be DTE device or NNI
interface to use this command. Send a request for complete PVC mode in every
n391 enquiry packet.
Example:
In the
following example, there is one complete mode information query every four mode
queries. For the rest of the queries, the exchanger only returns with the mode
information of the change.
interface s1/0
frame-relay intf-type dte
frame-relay n391 4
Configure
error threshold counter
frame-relay n392 threshold
parameter:
threshold |
The threshold value of the errors. Range from
1 to 10. default value is 3. |
default:
3
command mode:
Interface
configuration mode
explanation:
If there
are consecutively n392 failures in every n393 query packets, then the link mode
is abnormal. Before the N393 event counter to judge the closure of the link
arrives, there should be error times defined by N392. so, this value must be
smaller than the defined value in frame-relay n393.
Example:
下The
following example, configure the LMI error threshold value as 4. this router is
frame relay DCE device or NNI exchanger:
interface s1/0
frame-relay intf-type dce
frame-relay n392 4
relevant command:
Configure
the supervising event counter
frame-relay n393 events
parameter:
events |
Supervising event counter. Range from 1 to 10
and default value is 4. |
default:
4
command mode:
Interface
configuration mode
explanation:
This command
and the parameters configured by frame-relay n392 are the conditions of link
closure. During the execution, in the n393 event timer to judge the link
closure, the error times defined by N392 must emerge.
Example:
The
following example, configure the LMI supervising event counter value as 3. The
router works under the mode of DCE of frame relay or NNI exchanger:
interface s1/0
frame-relay interface dce
frame-relay n393 3
relevant command:
List:
LMI system parameter counter
Counter |
Description |
Range |
Default |
Usage |
User or network |
N391 |
Mode (full) enquiry counter |
1-255 |
6 |
Enquiry loop |
User |
N392 |
Error threshold |
1-10 |
3 |
error |
Both |
N393 |
Supervised event counting |
1-10 |
4 |
event |
Both |
Note: N392 should be smaller or equal to N393. N391 always
allies to user process.
Configure
link integrity authentication enquiry timer.
frame-relay t391 seconds
parameter:
seconds |
The value of authentication enquiry timer, second as the unit,
range from 5 to 30, default value is 10 seconds. |
default:
10 seconds
command mode:
Interface
configuration mode
explanation:
Used on DTE.
Send mode request information every t391 seconds, if the mode information is
not received, log the error.
Example:
The
following command, configure the value of link integrity authentication enquiry
timer as 20 seconds:
interface s1/1
frame-relay intf-type dce
frame-relay t391 20
relevant command:
Configure
authentication enquiry timer
frame-relay t392 seconds
parameter:
seconds |
Value of authentication
enquiry timer, second as the unit, range from 5 to 30, default value is 15
seconds. |
default:
15 seconds
command mode:
Interface
configuration mode
explanation:
Used on DCE.
Expect a mode request information every t392 seconds. If not received , log the
error. T392>t391.
Example:
The following command, configure the value of authentication enquiry timer as 20 seconds:
interface s1/1
frame-relay intf-type dce
frame-relay t392 20
relevant command:
List:
LMI system parameter timer
Timer |
Description |
Range |
Default (second) |
Enable |
Stop |
Activity of overtime system |
T391 |
Link
integrity authentication enquiry timer |
5-30 |
10 |
Send mode enquiry information |
|
If it does not receive mode information, log
the error. |
T392 |
authentication enquiry timer |
5-30 |
15 |
Send mode information |
Receive mode enquiry information |
Add N392 to log the errors, and restart the
timer |
Note: T392 must be greater than T391, T391 is always used
in user process, T392 is always used in the network process
frswitch
This
global configuration command activates PVC exchange on DEC of frame relay or
NNI. No to diable.
frswitch in-port in-dlci
out-port out-dlci
no frswitch in-port in-dlci
out-port out-dlci
parameter:
in_port |
First port exchanged |
in_dlci |
DLCI of the first port |
out_port |
Second port exchanged |
out_dlci |
DLCI of the second port |
default:
none
command mode:
全局配置态
explanation:
When you are configuring the exchange list, the two ports connected
must be encapsulated as frame relay, and there exists effective PVC.
Example:
The following
example narrates, the router enables PVC exchange between interface s1/1 and
interface s1/2. The DLCI 100 frame receives on interface 1 will be forwarded on
DLCI 200 of serial 2.
frswitch s1/1 100 s1/2 200
Configure the
destination protocol address by DLCI connection. Use command “no” to
diable the configuration.
[no] frame-relay map ipaddress pvc dlci [broadcast]
parameter:
ipaddress |
Destination IP address |
dlci |
The DLCI of connected destination protocol address
(16-1007) |
broadcast |
(Optional
parameter) when Multicast is not activated, forwarding the broadcast packet
from this interface. |
default:
none
command mode:
Interface
configuration mode
explanation:
The router
and the access server may have several DLCIs to send data. But they can be
reused on a physical link. Frame relay map command defines the logical
connection among specific protocol and address pair and DLCI. Broadcast activates
two functions: if multicast is not activated, it forwards broadcast and
simplifies the OSPF configuration in frame relay non-broadcast network.
Example:
The
following example maps the IP address 172.16.123.1 to DLCI 100:
interface s1/0
frame-relay map
172.16.123.1 pvc 100 broadcast
OSPF will use DLCI 100 broadcast route update.
This
command is used to clear the remote address list got via Inverse ARP protocl by
designated frame relay port (or all ports).
命令格式:
clear frame-relay-inarp [Serial]
parameter:
Serial is the name of interface to encapsulate frame relay
command mode:
supervisor
mode
Show the current mapping entry and
information of the connection
show frame-relay
parameter:
none
command mode:
All
configuration modes
explanation:
Check all
frame relay ports and active DLCI state. First, show the protocol state on all
ports configured frame relay protocol, can be either “UP” or “DOWN”, you must
guarantee that the protocol state is “UP” before carrying out upstream protocol
data transfer. State table is sorted by port and DLCI, each occupies one line,
each line is divided into 5 lines, from left to right, in order: port name, DLCI
value, DLCI state, remote IP address, local IP address and type. DLCI state can
be ACTIVE, INACTIVE or DELETED, class area is mainly used to distinguish static
or dynamic mapping mode. M means static, I means dynamic(InverseARP)。
样本输出
Here is a
sample output
Router#show frame-relay
Frame
Relay/Ip state
Serial1/0 UP
interface |
DLCI |
state |
remote IP address |
Local IP address |
Type |
======================================================================= |
|||||
Serial1/0 |
32 |
ACTIVE |
130.130.0.2 |
|
M |
Serial1/1 |
33 |
ACTIVE |
133.133.0.3 |
|
M |
relevant command:
Show the
information of frame relay switch list
show frswitch
parameter:
none
command mode:
All
configuration modes
explanation:
When frame relay is experimenting back on
back, the DLCI on the two sides must be the same, if they are connected through
the exchanger, the DLCIs may be different.
样本输出:
Here is a
sample output
Router#show frswitch
Frame relay PVC connection routing table
source interface pvc destination
interface pvc
Serial1/0 32 <---> Serial1/1 35
relevant command:
This command
is used to show serial port information and protocol statistics. If the serial
port uses frame relay encapsulation, then you can use it to show the statistics
of frame relay protocol.
show interface type number
parameter:
Type |
Interface type |
number |
Interface number |
command mode:
All
configuration modes
explanation:
This command
shows the state and statistical information of frame relay link.
样本显示:
Here we are
going to run the sample output of the serial port:
router#show int s1/0
Serial1/0 is up, line
protocol is up
Hardware is SCC Mode=Sync,Speed=64000
DTR=UP,DSR=UP,RTS=UP,CTS=UP,DCD=UP
Interface address is 96.0.0.2/8
MTU 1500 bytes, BW 64 kbit, DLY 2000 usec
Encapsulation frame-relay, loopback not set
Keepalive set(10 sec)
frame-relay DCE, LMI type is Q933A, LMI DLCI 1023
LMI DCE Link Errors 1, Protocol Errors 2, Inactives 0
Recvd Octets 2640, Recvd Frames 203, Recvd Discards 0
Sent Octets 2802, Sent Frames 202, Sent Discards 0
Recvd Errors 1, Send Errors 0, Recvd Unknowns 1
1 minute input rate 11
bits/sec, 0 packets/sec
1 minute output rate 11 bits/sec, 0 packets/sec
203 packets input, 3046 bytes, 0 no buffer
0 input errors, 0 CRC, 0 frame, 0 overrun,
0 ignored, 0 abort
202 packets output, 3206 bytes, 0 underruns
PowerQUICC SCC specific
errors:
0 recv allocb mblk fail 0 recv no buffer
0 transmitter queue full 0 transmitter hwqueue_full
relevant command:
The
statistical information frame relay may display are listed in the following
table:
English |
Meaning |
Recvd Octets |
Bits received on this interface since it is
configured as frame relay protocol |
Recvd Frames |
Frames received on this interface since it is
configured as frame relay protocol |
Recvd Discards |
Frames correctly received yet discarded on
this interface since it is configured as frame relay protocol |
Recvd Errors |
Error frames received on this interface since
it is configured as frame relay protocol |
Recvd Unknown Protocols |
Frames received correct but encapsulate
unknown protocol on this interface since it is configured as frame relay
protocol |
Sent Octets |
Bits sent successfully on this interface since
it is configured as frame relay protocol |
Sent Frames |
Frames sent on this interface since it is
configured as frame relay protocol |
Sent Discards |
Frames to be sent yet discarded on this interface
since it is configured as frame relay protocol |
Sent Errors |
Error frames sent on this interface since it
is configured as frame relay protocol |
LMI DTE Link Errors |
Link errors discovered through LMI DTE process
since it is configured as frame relay protocol |
LMI DTE Inactives |
Protocol states invalids discovered through
LMI DTE process since it is configured as frame relay protocol |
LMI DTE Protocol Errors |
Information content errors discovered through
LMI DTE process since it is configured as frame relay protocol |
LMI DCE Link Errors |
Link errors discovered through LMI DCE process
since it is configured as frame relay protocol |
LMI DCE Inactives |
Protocol states invalid discovered through LMI
DCE process since it is configured as frame relay protocol |
LMI DCE Protocol Errors |
Information content errors discovered through
LMI DCE process since it is configured as frame relay protocol |
Show frame
relay interactive information. Use no debug frame-relay to stop
showing.
[no] debug frame-relay
[raw | event | lmi | packet] Serial
parameter:
Serial |
The interface name require\ed to open debug
information. This interface can either be physical or E1 mapped one. |
Raw |
Show raw frame relay |
event |
Show all frame relay events |
Lmi |
Show all LMI information. |
packet |
Show all data backets. |
command
mode:
supervisor
mode
Example:
Router#debug frame-relay
lmi s1/0
Router#debug frame-relay
event s1/0
Router#debug frame-relay
packet s1/0
FR Serial1/0: TX -> LMI
STATUS ENQUIRY(full) message, send seq 5, expect seq 7
FR Serial1/0: RX <- LMI
STATUS(full) message, send seq 8, expect seq 5 200 A
FR Serial1/0: Active DLCI
200 according LMI message
FR Serial1/0: TX ->
InARP request on DLCI 200, src(0,192.168.75.4),dst(200,0.0.0.0)
FR Serial1/0: RX <-
InARP reply on DLCI 200, src(200,192.168.75.1),dst(200,192.168.75.4)
FR Serial1/0: Add map DLCI
200 to IP 8.0.0.1 according InARP message
FR Serial1/0: TX -> LMI
STATUS ENQUIRY(link) message, send seq 7, expect seq 9
FR Serial1/0: RX <- LMI
STATUS(link) message, send seq 10, expect seq 7
FR Serial1/0: Receive
packet from upper on DLCI 200:Len = 84
FR Serial1/0: TX -> IP
packet on DLCI 200:Len = 88
FR Serial1/0: RX <- IP
Packet on DLCI 200:Len = 84
45 00 00 54 00 07 00 00 FF
01 AB 9F 08 00 00 01 E..T............
08 00 00 02 00 00 E2 70 00
0D 00 00 03 05 25 6E .......p......%n
FR Serial1/0: Forward
packet to upper on DLCI 200:Len = 84
The
first line means the port sends the complete state query information of LMI.
The
second line means the port receives complete state response information of LMI,
DLCI 200 is valid among them.
The
third line means the port activates DLCI 200 according to the complete state
response information of LMI.
The
fourth line means the port sends InverseARP request, and carries the local IP
address 192.168.75.4.
The
fifth line means the interface receives InverseARP response. The recipient
address is 192.168.75.1, corresponds DLCI 200.
The
sixth line means the port sets up dynamic mapping relation between DLCI 200 and
192.168.75.1.
The
seventh line means the port sends LMI state request information.
The
eighth line means the port receives state response information of LMI.
The
ninth line means the port receives upstream data packet, DLCI 200. The length
of the packet is 86 bits
The
tenth line means the port sends the packet through DLCI 200 and the length of
the packet is 88 bits.
The
eleventh line means the port receives data packet on DLCI 200, and the length
of the packet is 88 bits. The following two lines are the detailed information
about data packets.
The fourteenth line means the port will hand in this packet to the network later (IP).