User Manual -Configuration Guide (Volume 1)

Versatile Routing Platform Table of Contents

i
Table of Contents
Chapter 1 Configuring PPP and MP .................................................................................... 1-1
1.1 PPP and MP Overview.............................................................................................. 1-1
1.1.1 PPP Overview................................................................................................. 1-1
1.1.2 MP Overview .................................................................................................. 1-2
1.2 Configuring PPP....................................................................................................... 1-3
1.2.1 PPP Configuration Task List ............................................................................ 1-3
1.2.2 Configuring the Link Layer Protocol for Interface Encapsulation as PPP............. 1-3
1.2.3 Configuring PPP Authentication Mode, Username and User Password............... 1-3
1.2.4 Configuring AAA Authentication and Accounting Parameter of PPP.................... 1-5
1.2.5 Configuring PPP Negotiation Parameter........................................................... 1-5
1.2.6 Configuring PPP Compression......................................................................... 1-6
1.3 Configuring MP......................................................................................................... 1-6
1.3.1 MP Configuration Task List.............................................................................. 1-6
1.3.2 Configuring MP on Virtual Interface Template................................................... 1-7
1.4 Monitoring and Maintenance of PPP .......................................................................... 1-7
1.5 Typical PPP Configuration Example........................................................................... 1-8
1.5.1 PAP Authentication Example........................................................................... 1-8
1.5.2 CHAP Authentication Example......................................................................... 1-9
1.6 Typical MP Configuration Example........................................................................... 1-10
1.7 Fault Diagnosis and Troubleshooting of PPP............................................................ 1-12
Chapter 2 Configuring SLIP................................................................................................. 2-1
2.1 SLIP Overview.......................................................................................................... 2-1
2.2 Configuring SLIP....................................................................................................... 2-1
2.2.1 SLIP Configuration Task List............................................................................ 2-1
2.2.2 Configuring the Sync/Async Serial Interface to Work in Async Mode................... 2-1
2.2.3 Configuring Encapsulation Protocol SLIP.......................................................... 2-2
2.3 Monitoring and Maintenance of SLIP.......................................................................... 2-2
2.4 Typical SLIP Configuration Example........................................................................... 2-2
Chapter 3 Configuring ISDN Protocol .................................................................................. 3-1
3.1 ISDN Protocol Overview............................................................................................ 3-1
3.2 Configuring ISDN...................................................................................................... 3-1
3.2.1 ISDN Configuration Task List........................................................................... 3-1
3.2.2 Setting the Called Number or Sub-Address to be Checked................................ 3-1
3.3 Monitoring and Maintenance of ISDN Configuration.................................................... 3-2
3.4 Typical ISDN Configuration Example.......................................................................... 3-4
3.5 Fault Diagnosis and Troubleshooting of ISDN............................................................. 3-5
User Manual -Configuration Guide (Volume 1)
Versatile Routing Platform Table of Contents
ii
Chapter 4 Configuring LAPB, X.25 and X.25 Switching....................................................... 4-1
4.1 X.25 and LAPB Protocols Overview........................................................................... 4-1
4.2 Configuring LAPB ..................................................................................................... 4-3
4.2.1 LAPB Configuration Task List .......................................................................... 4-3
4.2.2 Configuring Encapsulation LAPB Protocol......................................................... 4-3
4.2.3 Configuring LAPB Protocol Parameter.............................................................. 4-4
4.3 Configuring X.25....................................................................................................... 4-5
4.3.1 X.25 Configuration Task List ............................................................................ 4-5
4.3.2 Configuring X.25 Interface............................................................................... 4-6
4.3.3 Configuring X.25 Interface Supplementary Parameter...................................... 4-11
4.3.4 Configuring X.25 Datagram Transmission....................................................... 4-15
4.3.5 Configuring Additional Parameters of X.25 Datagram Transmission ................. 4-16
4.3.6 Configuring X.25 Sub-Interface...................................................................... 4-21
4.3.7 Configuring X.25 Switching............................................................................ 4-21
4.3.8 Configuring XOT........................................................................................... 4-24
4.4 Monitoring and Maintenance of LAPB, X.25 and X.25 Switching................................ 4-28
4.4.1 Displaying the Information of Interface Encapsulated LAPB ............................. 4-29
4.4.2 Displaying the Information of Interface Encapsulated X.25............................... 4-30
4.4.3 Displaying X.25 Alias Table............................................................................ 4-31
4.4.4 Displaying X.25 Address Mapping Table......................................................... 4-32
4.4.5 Displaying X.25 Switching Route Table........................................................... 4-32
4.4.6 Displaying X.25 Virtual Circuit Table............................................................... 4-32
4.5 Typical LAPB Configuration Example....................................................................... 4-34
4.6 Typical X.25 Configuration Example......................................................................... 4-35
4.6.1 Back to Back Direct Connection of Two Routers via Serial Ports ...................... 4-35
4.6.2 Connecting the Router to X.25 Public Packet Network ..................................... 4-36
4.6.3 Configuring Virtual Circuit Range.................................................................... 4-38
4.6.4 Transmitting IP Datagram via X.25 PVC......................................................... 4-39
4.6.5 Typical X.25 Sub-Interface Configuration Example.......................................... 4-41
4.6.6 SVC Application of XOT................................................................................. 4-42
4.6.7 PVC Application of XOT................................................................................. 4-44
4.7 Fault Diagnosis and Troubleshooting of LAPB .......................................................... 4-46
4.8 Fault Diagnosis and Troubleshooting of X.25............................................................ 4-46
Chapter 5 Configuring Frame Relay.................................................................................... 5-1
5.1 Frame Relay Protocol Overview................................................................................. 5-1
5.2 Configuring Frame Relay........................................................................................... 5-2
5.2.1 Frame Relay Configuration Task List................................................................ 5-2
5.2.2 Configuring Interface Encapsulation as Frame Relay......................................... 5-2
5.2.3 Configuring Frame Relay Terminal Type........................................................... 5-3
5.2.4 Configuring Frame Relay LMI Type.................................................................. 5-3
5.2.5 Configuring Frame Relay LMI Protocol Parameters ........................................... 5-4
5.2.6 Configuring Frame Relay Address Mapping...................................................... 5-6
User Manual -Configuration Guide (Volume 1)
Versatile Routing Platform Table of Contents
iii
5.2.7 Configuring Frame Relay Local Virtual Circuit ................................................... 5-7
5.2.8 Configuring Frame Relay Sub-Interface............................................................ 5-7
5.2.9 Configuring Frame Relay PVC Switching.......................................................... 5-9
5.2.10 Enable/Disable TCP/IP Header Compression on Interfaces ............................. 5-9
5.3 Monitoring and Maintenance of Frame Relay ............................................................ 5-10
5.4 Typical Frame Relay Configuration Example............................................................. 5-13
5.4.1 Interconnecting LANs via Frame Relay Network .............................................. 5-13
5.4.2 Interconnecting LANs via Private Line............................................................ 5-14
5.5 Fault Diagnosis and Troubleshooting of Frame Relay ................................................ 5-15
Chapter 6 Configuring HDLC............................................................................................... 6-1
6.1 Configuring HDLC..................................................................................................... 6-1
6.1.1 HDLC Configuration Task List.......................................................................... 6-1
6.1.2 Encapsulating Interface with HDLC Protocol ..................................................... 6-1
6.1.3 Setting Keepalive Time Delay .......................................................................... 6-2
6.2 Monitoring and Maintenance of HDLC........................................................................ 6-2
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-1
Chapter 1 Configuring PPP and MP
1.1 PPP and MP Overview
1.1.1 PPP Overview
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-
protocol datagrams over point-to-point links. It has found wide application since it can
provide user authentication, support synchronous/asynchronous operations and can
be expanded easily.
PPP defines a whole set of protocols, including link control protocol (LCP), network
control protocol (NCP) and authentication protocols (PAP and CHAP). Of them:
l Link Control Protocol is used to negotiate some parameters of the link and is
responsible for creating and maintaining the link.
l Network Control Protocol is used to negotiate the parameters of network layer
protocol.
PPP authentication mode includes the following:
1) PAP authentication
PAP (Password Authentication Protocol) is a 2-way handshake authentication protocol
and it sends the password in plaintext. The process of PAP authentication is as follows:
The requester repeatedly sends its username/password combination across the link
until the authenticator responds with an acknowledgment or until the link is broken. The
authenticator may disconnect the link if it determines that the username/password
combination is not valid.
2) CHAP authentication
CHAP (Challenge-Handshake Authentication Protocol) is a 3-way handshake
authentication protocol and it only sends its username but not the password across the
link. The process of CHAP is as follows:
The authenticator sends some randomly generated messages to the requester
(challenge), and at the same time it sends its own hostname to the requester.
When the requester receives the challenge, it will look for the user password according
to the authenticator s hostname and its own user list. If it finds the user in the user list
with the same name as the authenticator s hostname, the requester builds the
response with its own password, serial number of message using MD5 algorithm, and
sends the generated response and its own hostname to the authenticator (response).
After receiving the response from the requester, the authenticator does the same
encryption as the requester with the saved password, serial number of message using
MD5 algorithm. Then it compares the encryption result with the response from
requester, and returns the response according to the comparison result (Acknowledge
or Not Acknowledge).
Phases of PPP negotiation:
3) When the physical layer is unavailable, the link is in Dead phase. A link shall starts
from and end at the Dead phase. When the physical layer becomes available,
PPP link enters the Establish phase.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-2
4) In Establish phase, PPP link carries out LCP negotiation, including negotiation of
working mode (SP or MP), authentication mode and maximum transmission unit
etc. After the successful LCP negotiation, the status of LCP is Open, indicating
that the link has been established.
5) If the authentication is not configured, it begins NCP negotiation. At this time, the
status of LCP is still Open, while the status of NCP is changed from Initial to
Request-sent. Then it enters the flow of step 5. If the authentication is configured
(the remote verifies the local or the local verifies the remote), it enters Authenticate
phase to start CHAP or PAP authentication, and then enters the flow of step 4.
6) If the authentication fails, it enters Terminate phase, the link is removed and LCP
turns to Down. After successful authentication, the NCP negotiation begins. At this
time, the status of LCP is still Open, while the status of NCP is changed from Initial
to Request-sent.
7) NCP negotiation supports the negotiations of IPCP and IPXCP, of which IPCP
negotiation mainly includes the IP addresses of two partners. One or more
network layer protocols is selected and configured through NCP negotiation. The
selected network layer protocol must be configured successfully before this
network layer protocol sends messages through this link.
8) PPP link will remain in communication status until a specific LCP or NCP frame
closes this link or some external events take place (for example, the intervention of
user).
Phases of PPP negotiation are shown in the following diagram.
Dead Establish Authenticate
Terminate
Network
UP OPENED
FAIL FAIL
DOWN CLOSING
SUCCESS/NONE
Figure LLC-1-1 Diagram of PPP negotiation phases
For detailed description of PPP, refer to RFC1661.
1.1.2 MP Overview
MP (MultiLink PPP) provides load balancing functionality over multiple WAN links. At
the same time it provides multi-vendor interoperability, packet fragmentation and
proper sequencing, and load calculation on both inbound and outbound traffic. Multilink
PPP allows packets to be fragmented. These fragments can be sent at the same time
over multiple point-to-point links to the same remote address. Multilink PPP works over
the following interface types (single or multiple) which can be configured to support
PPP encapsulation:
l Asynchronous/Synchronous serial interfaces
l BRI interfaces
l PRI interfaces
l Dialer interfaces
l Virtual interface template
The interface working process in MP mode is as follows (taking MP in the virtual
interface template as example):
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-3
First, begin LCP negotiation with the peer, negotiating about ordinary LCP parameters
and verify whether the interface of the peer works in MP mode. If the peer does not
work in MP mode, begin NCP negotiation and do not bundle MP.
Then begin PPP authentication, and get the username of the peer. If the peer also
works in MP mode, locate the virtual interface template specified for the peer according
to its username, and then begin NCP negotiation with the NCP parameters of this
virtual template (such as IP address). The NCP parameters configured at the physical
interface are not functional. If NCP negotiation is successful, MP link can be
established, to transport data with wider bandwidth.
1.2 Configuring PPP
1.2.1 PPP Configuration Task List
PPP configuration task list is as follows:
l Configure the link layer protocol for interface encapsulation as PPP
l Configure PPP authentication mode, username and user password
l Configure AAA authentication and accounting parameter of PPP
l Configure PPP negotiation parameter
l Configure PPP compression algorithm
1.2.2 Configuring the Link Layer Protocol for Interface Encapsulation as PPP
Perform the following configuration in the interface configuration mode.
Table LLC-1-1 Configure the link layer protocol for interface encapsulation as PPP
Operation Command
Configure the link layer protocol for interface encapsulation as PPP encapsulation ppp
The default link layer protocol for interface encapsulation is PPP.
1.2.3 Configuring PPP Authentication Mode, Username and User Password
PPP has two authentication modes:
l PAP mode
l CHAP mode
Generally speaking, CHAP authentication is securer.
The respective configuration steps of PAP authentication and CHAP authentication are
as follows.
& Note:
In the PPP authentication commands introduced in this section, only user series commands are used in
the global configuration mode, all other commands are used in the interface configuration mode.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-4
I. Configuring the local authenticates the opposite router in PAP mode
Perform the following configuration in the interface configuration mode.
Table LLC-1-2 Configure the local authenticates the peer in PAP mode
Operation Command
Configure the local authenticates the peer (in PAP mode) ppp authentication pap [ callin ]
[ default | name-list ]
Cancel the configured PPP authentication, i.e. do not perform PPP
authentication
no ppp authentication
Add the username and password of the peer into the local user list user user password { 0 | 7 } password
II. Configuring the local authenticates the peer in CHAP mode
Perform the following configuration in the interface configuration mode.
Table LLC-1-3 Configure the local authenticates the peer in CHAP mode
Operation Command
Configure the local authenticates the peer (in CHAP
mode)
ppp authentication chap [ callin ] [ default | name-list ]
Cancel the configured PPP authentication, i.e. do not
perform PPP authentication
no ppp authentication
Configure the name of the local ppp chap host hostname
Delete the configured name of the local no ppp chap host
Add the username and password of the peer into the
local user list
user user password { 0 | 7 } password
III. Configuring the peer authenticates the local in PAP mode
Perform the following configuration in the interface configuration mode.
Table LLC-1-4 Configure the peer authenticates the local in PAP mode
Operation Command
Configure PAP username and password when the peer
authenticates the local in PAP mode
ppp pap sent-username sent-username
password { 0 | 7 } password
Delete the above configured username and password sent
during authentication in PAP mode
no ppp pap sent-username
IV. Configuring the peer authenticates the local in CHAP mode
Perform the following task in the interface configuration mode.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-5
Table LLC-1-5 Configure as the peer authenticates the local in CHAP mode
Operation Command
Configure the name of the local ppp chap host hostname
Delete the configured name of the local no ppp chap host
Configure the password of the local for authentication in
CHAP mode
ppp chap password { 0 | 7 } password
Delete the password of the local during authentication in
CHAP mode
no ppp chap password
Add the username and password of the peer into the local
user list
user user password { 0 | 7 } password
Generally speaking, in the situation that the router has configured user list, it configure
the command ppp chap host hostname and user user password { 0 | 7 } password, to
perform CHAP authentication. When configuring CHAP authentication, user of one end
is the hostname of the other, and the password must be the same.
In some situation, the router cannot configure user list, then it need to configure the
command ppp chap password { 0 | 7 } password to perform CHAP authentication.
1.2.4 Configuring AAA Authentication and Accounting Parameter of PPP
Whether the PPP user passes the authentication will be finally decided by AAA, which
can authenticate PPP user at local or at RADIUS server.
Local authentication is to authenticate using the local user configured with the user
user password { 0 | 7 } password command, and RADIUS server authentication is to
authenticate with the user database on RADIUS server. The specific configuration
commands are shown in the following table.
Table LLC-1-6 Configure AAA authentication and accounting of PPP
Operation Command
Enable AAA aaa-enable
Configure PPP authentication method of AAA aaa authentication ppp { default | list-name }
[ method1 | method2| ...... ]
Configure the local first authentication of AAA aaa authentication local-first
Configure PPP authentication method of AAA at the
interface
ppp authentication { chap | pap } [ default
|list-name]
Configure accounting method list of PPP user of AAA at the
interface. At present the RADIUS authentication is
supported.
ppp accounting { default | list-name }
For PPP authentication method of AAA, refer to the Security Configuration part. If
PPP authentication method of AAA is not specified on the interface, please use the
default authentication method.
1.2.5 Configuring PPP Negotiation Parameter
The following PPP negotiation parameters can be configured:
l Time interval between negotiation timeout
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-6
During PPP negotiation, if the response message of the peer is not received within this
time interval, PPP will redirect the message. The default time interval of timeout is 10s,
and the value range is 1~10s.
l Some negotiation parameters of NCP
For the configuration of local IP address and the IP address assigned to the peer, refer
to the Network Protocol Configuration part in this manual. For example, the ip
address negotiate command can be used to require the peer to assign IP address for
the local, while the peer default ip address command can be used to designate the
local to assign IP address for the peer.
Table LLC-1-7 Configure the time interval of PPP negotiation timeout
Operation Command
Configure the time interval of negotiation timeout ppp negotiate timeout seconds
Restore the default of time interval of negotiation timeout no ppp negotiate timeout
1.2.6 Configuring PPP Compression
The current VRP version supports the Stac compression method.
Perform the following task in the interface configuration mode.
Table LLC-1-8 Configure PPP compression
Operation Command
Configure as Stac compression permitted on the interface ppp compress stac
Cancel the Stac compression used by the interface no ppp compress stac
& Note:
In MP working mode, it is not recommended to use PPP compression. To configure PPP compression
negotiation on the virtual interface, PPP compression must be configured on Virtual-template interface
before the subordinate physical interface can accept the PPP compression negotiation.
1.3 Configuring MP
1.3.1 MP Configuration Task List
MP configuration tasks on the virtual interface template is shown as follow, the MP
configuration in the DDR mode (including MP on the ISDN BRI/PRI interface) refers to
the DDR Configuration part of this manual.
l Create and configure MP virtual interface template
l Establish the corresponding relation between PPP user and MP virtual interface
template
l Configure the interface bound under the virtual interface template to work in MP
mode
l Configure the authentication mode of virtual interface
l Configure maximum numbers of links and fragments that MP permits
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-7
1.3.2 Configuring MP on Virtual Interface Template
Perform the following task to configure MP on virtual interface template.
Table LLC-1-9 Configure MP under MP virtual interface template
Operation Command
In global configuration mode, create and enter the MP virtual
interface template
interface virtual-template number
In virtual interface configuration mode, configure the working
parameter of the virtual interface template
Omitted
In global configuration mode, establish the corresponding relation
between virtual interface template and PPP user
multilink-user user-name bind virtual-
template number
In global configuration mode, configure MP parameter multilink { max-binds binds | max-frags
frags }
Note that before configuring MP, the virtual interface template must be configured and
please refer to "Virtual-Template and Virtual Interface" for specific configuration method.
The interface bound under the virtual interface template shall perform two-way
authentication with the remote end (CHAP or PAP). For configuring the working
parameters of the virtual interface template in the above table, please refer to Virtual-
Template and Virtual Interface .
1.4 Monitoring and Maintenance of PPP
Perform the following task in the privileged mode to monitor and maintain PPP.
Table LLC-1-10 Monitoring and maintenance of PPP
Operation Command
Show local user of PPP authentication show user
Show PPP configuration and running state of the interface show interface interface-type interface-number
1) Show the local user of PPP authentication.
Quidway# show user
No. username logintimes failedtimes
-------------------------------------------------------------------
1 RTB_A 0 0
2 RTB_B 0 0
2) Show the PPP configuration and running state of the interface.
Quidway# show interface serial 0
Serial0 is up, line protocol is up
physical layer is synchronous
interface is DTE, clock is DTECLK1, cable type is V35
Internet address is 10.3.0.158 255.255.255.252
Encapsulation is PPP
LCP opened, IPCP opened
5 minutes input rate 1023.79 bytes/sec, 5.50 packets/sec
5 minutes output rate 4836.88 bytes/sec, 5.92 packets/sec
1005453 packets input, 488212969 bytes, 0 no buffers
1833530 packets output, 547917333 bytes, 0 no buffers
1172162 input errors, 437770 CRC, 504267 frame errors
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-8
0 overrunners, 230125 aborted sequences, 0 input no buffers
The above information includes the current states of LCP and IPCP, by which the user
can estimate PPP running status.
1.5 Typical PPP Configuration Example
1.5.1 PAP Authentication Example
I. Configuration requirement
As shown in Figure LLC-1-2, routers Quidway1 and Quidway2 are interconnected
through interface Serial0, and router Quidway1 (authenticator) is required to
authenticate router Quidway2 (requester) in PAP mode.
II. Networking diagram
Quidway 2
Quidway 1
Figure LLC-1-2 Networking diagram of PAP and CHAP authentication example
III. Configuration procedure
1) Configure router Quidway1 (authenticator):
! Add a user with name quidway2 and password hello to the local database
Quidway(config)# user quidway2 password 0 hello
! Configure to start PAP authentication at this side
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# ppp authentication pap
2) Configure router Quidway2 (requester):
! Configure this side to be authenticated by the opposite side with username quidway2
and password hello
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# ppp pap sent-username quidway2 password 0 hello
While configuring PAP authentication, note following things:
1) If one side originates the PAP, it (authenticator) should add username and
password for the requester in the local database ( user...). The requester should
send its username and password to the authenticator ( ppp pap sent-
username....).
2) If one side originates the PAP, it (authenticator) only needs to start PAP
authentication itself ( ppp authentication pap) . The requester does not need to
configure the command.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-9
3) If both sides originate PAP simultaneously, then each side is both authenticator
and requester. At this time, both sides need to configure all the commands
supporting the PAP authentication.
1.5.2 CHAP Authentication Example
I. Configuration requirement
In Figure LLC-1-2, router Quidway1 is required to authenticate router Quidway2 in
CHAP mode.
II. Configuration procedure
1) Configure router Quidway1:
! Add a user with name quidway2 and password hello to the local database
Quidway(config)# user quidway2 password 0 hello
! Set local username as quidway1
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# ppp chap host quidway1
! Configure to start CHAP authentication at this side
Quidway(config-if-Serial0)# ppp authentication chap
2) Configure router Quidway2:
! Add a user with name quidway1 and password hello to the local database
Quidway(config)# user quidway1 password 0 hello
! Set local username as quidway2
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# ppp chap host quidway2
While configuring CHAP authentication, note following things:
1) If one side originates the CHAP, it (authenticator) should add username and
password for the requester in the local database ( user...), and should send its
username to the requester (ppp chap host...). The requester should also add
username and password for the authenticator in its database (user...), and send
its username and password to the authenticator (ppp chap host...).
2) If one side originates the CHAP, it (authenticator) only needs to start CHAP
authentication itself ( ppp authentication chap) . The requester does not need to
configure the command.
3) If both sides originate CHAP simultaneously, then each side is both authenticator
and requester. At this time, both sides need to configure all the commands
supporting the CHAP authentication.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-10
1.6 Typical MP Configuration Example
I. Configuration requirement
In Figure LLC-1-3, two B channels of E1 interface of router-a are bound to the B
channel of router-b, and the other two B channels are bound to router-c. Supposing that
four B channels on router-a are serial2:1, serial2:2, serial2:3 and serial2:4, the names
of interfaces of two B channels on router-b are serial2:1 and serial2:2, and the names
of interfaces of two B channels on router-c are serial2:1 and serial2:2.
II. Networking diagram
router-a
router-b
router-c
DDN
Tower System
Desktop System
Tower System
Desktop System
Tower System
Desktop System
Figure LLC-1-3 Networking diagram of MP configuration example
III. Configuration procedure
1) Configure router-a:
! Add a user for router-b and router-c respectively
Quidway(config)# user router-b password 0 router-b
Quidway(config)# user router-c password 0 router-c
! Specify the virtual interface templates for the two users and begin PPP negotiation for
the NCP information using this template
Quidway(config)# multilink-user router-b bind virtual-template 1
Quidway(config)# multilink-user router-c bind virtual-template 2
! Configure virtual interface template
Quidway(config)# interface virtual-template 1
Quidway(config-if-vitual-template1)# ip address 202.38.166.1 255.255.255.0
Quidway(config)# interface virtual-template 2
Quidway(config-if-vitual-template2)# ip address 202.38.168.1 255.255.255.0
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-11
! Add the interfaces serial2:1, serial2:2, serial2:3 and serial2:4 into MP channel. Here,
take serial2:1 as an example, and other interfaces are configured similarly.
Quidway(config)# interface serial 2:1
Quidway(config-if-Serial2: 1)# encapsulation ppp
Quidway(config-if-Serial2: 1)# ppp multilink
Quidway(config-if-Serial2:1)# ppp authentication pap
Quidway(config-if-serial2:1)# ppp pap sent-username router-a password 0 router-a
2) Configure router-b:
! Add a user for router-a
Quidway(config)# user router-a password 0 router-a
! Specify the virtual interface template for this user and begin PPP negotiation for the
NCP information using this template
Quidway(config)# multilink-user router-a bind virtual-template 1
! Configure working parameters of the virtual interface template
Quidway(config)# interface virtual-template 1
Quidway(config-if-virtual-template1)# ip address 202.38.166.2 255.255. 255.0
! Add the interfaces serial2:1 and serial2:2 into MP channel. Here, take serial2:1 as an
example, and configure other interfaces similarly
Quidway(config)# interface serial2: 1
Quidway(config-if-serial2: 1)# ppp multilink
Quidway(config-if-serial2: 1)# ppp authentication pap
Quidway(config-if-serial2: 1)# ppp pap sent-username router-b password 0 router-b
3) Configure router-c:
! Add a user for router-a
Quidway(config)# user router-a password 0 router-a
! Specify the virtual interface template for this user and begin PPP negotiation for the
NCP information using this template
Quidway(config)# multilink-user router-a bind virtual-template 1
! Configure working parameters of the virtual interface template
Quidway(config)# interface virtual-template 1
Quidway(config-if-virtual-template1)# ip address 202.38.168.2 255.255. 255.0
! Add the interfaces serial2:1 and serial2:2 into MP channel. Here, take serial2: 1 as an
example, and other interfaces are configured similarly.
Quidway(config)# interface serial2: 1
Quidway(config-if-serial2: 1)# ppp multilink
Quidway(config-if-serial2: 1)# ppp authentication pap
Quidway(config-if-serial2: 1)# ppp pap sent-username router-c password 0 router-c
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 1
Configuring PPP and MP
1-12
1.7 Fault Diagnosis and Troubleshooting of PPP
I. Fault 1: Link always fails to turn to up status.
Troubleshooting: It's possible that PPP authentication parameter is not configured
correctly, resulting in the failure of PPP authentication.
Turn on the debugging switch of PPP, and it is shown that LCP negotiation is successful
and turns to Up status, then begin PAP or CHAP negotiation and LCP turns to Down
status.
II. Fault 2: Physical link fails to turn to up status.
Troubleshooting: Execute show interface serial interface-number command to view
the current interface status, including five statuses:
serial number is administratively down, line protocol is down
It indicates that the interface is shut down.
serial number is down, line protocol is down
It indicates that the interface is not activated or the physical layer does not turn to Up
status.
serial number is up, line protocol is up(spoofing)
It indicates that this interface is a dialup interface and the call is not connected
successfully.
serial number is up, line protocol is up
It indicates that data can be transmitted through this interface.
serial number is up, line protocol is down
It indicates that this interface is activated, but link negotiation is not successful.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 2
Configuring SLIP
2-1
Chapter 2 Configuring SLIP
2.1 SLIP Overview
SLIP (Serial Line Internet Protocol) defines a method of sending packets over standard
RS-232 asynchronous serial lines.
SLIP is an inexpensive way of connecting PCs to a network. SLIP can be used over
asynchronous dial-up modems, allowing computers in people's homes to be connected
to a network without the cost of a leased line. Besides, SLIP is easy to realize because
it does not provide address, error detection, correction and compression algorithm.
& Note:
SLIP does not distinguish between different types of messages, so it supports only one type of network
protocol at one time.
For details about SLIP, users can refer to RFC1055.
2.2 Configuring SLIP
2.2.1 SLIP Configuration Task List
Because SLIP protocol does not negotiate name of the remote end, SLIP dialer can
only be used with the standard DDR; meanwhile, SLIP can be encapsulated only on the
physical port, and can not be encapsulated on Dialer port.
Configure SLIP dialer on the physical port:
l Configure the synchronous/asynchronous serial interface to asynchronous mode
l Configure the incoming and outgoing call authorities of Modem
l Enable DDR
l Configure encapsulation protocol SLIP
l Configure Dialer Group and Dialer List of activated calls
l Configure the dial string of interface
For the specific configuration methods of DDR, Modem and Dialer, please refer to
related chapters of DDR, Modem.
2.2.2 Configuring the Sync/Async Serial Interface to Work in Async Mode
Perform the following task in the interface configuration mode.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 2
Configuring SLIP
2-2
Table LLC-2-1 Configure the synchronous/async serial interface to work in async mode
Operation Command
Configure the synchronous/asynchronous serial interface to work in asynchronous
mode
physical-layer async
By default, the synchronous/asynchronous serial interface operates in synchronous
mode
2.2.3 Configuring Encapsulation Protocol SLIP
Perform the following task in the asynchronous interface configuration mode.
Table LLC-2-2 Configure the link layer protocol for interface encapsulation as SLIP
Operation Command
Configure the link layer protocol for interface encapsulation as SLIP encapsulation slip
By default, the link layer protocol encapsulated on the interface is PPP.
Note the following points:
1) The interface can be encapsulated with SLIP only when it operates in the
asynchronous mode.
2) When LAPB, X.25, HDLC or Frame Relay is operating on the interface, the
physical attributes of the interface cannot be modified to asynchronous mode. At
this time, you should first modify the link layer encapsulation of the interface to
PPP and then you may change the interface attribute to asynchronous mode.
3) After the interface is encapsulated with SLIP, its upper layer still can carry IP
protocol.
2.3 Monitoring and Maintenance of SLIP
Perform the following task in privileged mode to monitor the current state of SLIP in real
time.
Table LLC-2-3 Enable/Disable the information debugging of SLIP
Operation Command
Enable the information debugging of SLIP packet debug slip packet
Disable the information debugging of SLIP packet no debug slip packet
2.4 Typical SLIP Configuration Example
I. Networking requirement
Interconnect two Quidway routers via PSTN and run IP.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 2
Configuring SLIP
2-3
II. Networking diagram
PSTN
E
t
h
e
r
n
e
t
E
t
h
e
r
n
e
t
Router A
Router B
IP10.110.0.1
8810003
IP10.110.0.2
8810026
IP129.102.0.1
IP129.103.0.1
Modem Modem
Figure LLC-2-1 Networking diagram of SLIP dialer
III. Configuration procedure
l Configure Quidway router A:
! Configure Dialer List
Quidway(config)# dialer-list 1 protocol ip permit
! Configure the synchronous/asynchronous interface to asynchronous mode
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# physical-layer async
! Configure IP address of synchronous/asynchronous interface
Quidway(config-if-Serial0)# ip address 10.110.0.1 255.0.0.0
! Configure the incoming and outgoing call authorities of Modem
Quidway(config-if-Serial0)# modem
! Enable DDR
Quidway(config-if-Serial0)# dialer in-band
! Configure the Dialer String to router B
Quidway(config-if-Serial0)# dialer string 8810026
! Encapsulate SLIP protocol
Quidway(config-if-Serial0)# encapsulation slip
! Specify Dialer Group
Quidway(config-if-Serial0)# dialer-group 1
! Configure the default route to Route B
Quidway(config)# ip route 0.0.0.0 0.0.0.0 10.110.0.2
l Configure Quidway router B:
! Configure Dialer List
Quidway(config)# dialer-list 1 protocol ip permit
! Configure the synchronous/asynchronous interface to asynchronous mode
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 2
Configuring SLIP
2-4
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# physical-layer async
! Configure IP address of synchronous/asynchronous interface
Quidway(config-if-Serial0)# ip address 10.110.0.2 255.0.0.0
! Configure the incoming and outgoing call authorities of Modem
Quidway(config-if-Serial0)# modem
! Enable DDR
Quidway(config-if-Serial0)# dialer in-band
! Configure the Dialer String to router A
Quidway(config-if-Serial0)# dialer string 8810003
! Encapsulate SLIP protocol
Quidway(config-if-Serial0)# encapsulation slip
! Specify Dialer Group
Quidway(config-if-Serial0)# dialer-group 1
! Configure the default route to Route A
Quidway(config)# ip route 0.0.0.0 0.0.0.0 10.110.0.1
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 3
Configuring ISDN Protocol
3-1
Chapter 3 Configuring ISDN Protocol
3.1 ISDN Protocol Overview
ISDN (Integrated Services Digital Network), developed from telephone integrated
digital network (IDN), provides end-to-end digital connection, so as to support wide
range of services (including voice and non-voice services).
ISDN provides the user with a group of standard multifunctional user-network
interfaces. In ITU-T I.412 recommendations, two types of user-network interfaces are
specified: basic rate interface (BRI) and primary rate interface. The bandwidth of BRI is
2B+D, and that of PRI is 30B+D or 23B+D. Here:
l B channel is a user channel, used to transmit the voice, data and other user
information with the transmission rate 64kbit/s.
l D channel is a control channel and used to transmit the common channel signaling,
controlling the calls on B channels of the same interface. The rate of D channel is
64kbit/s (PRI) or 16kbit/s (BRI). ITU-T Q.921, the data link layer protocol of D
channel, defines the rules by which the information is exchanged between layer-
2 entities on the user-network interface through D channel. Meanwhile, it supports
the access of layer-3 entity. ITU-T Q.931, the network layer protocol of D channel,
provides methods to establish, maintain and terminate the network connection
between communication application entities.
3.2 Configuring ISDN
3.2.1 ISDN Configuration Task List
ISDN protocol configuration task includes:
l Set the called number or sub-address to be checked in digital incoming call.
3.2.2 Setting the Called Number or Sub-Address to be Checked
Table LLC-3-1 Set the called number or sub-address to be checked in digital incoming call
Operation Command
Set the called number or sub-address to be checked in digital incoming call
isdn answer1 [called-party]
[:subaddress]
Cancel the called number or sub-address to be checked in digital incoming call no isdn answer1
Set the additional called number or sub-address to be checked in digital
incoming call
isdn answer2 [called-party]
[:subaddress]
Cancel the additional called number or sub-address to be checked in digital
incoming call
no isdn answer2
By default, no called number or sub-address is configured.
The two commands are used to set the items to be checked in the digital incoming call.
If the sub-address is set, call of the opposite will be rejected when the sub-address is
not sent or is sent incorrectly. The above two commands are independent commands
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 3
Configuring ISDN Protocol
3-2
and function separately. An incoming call will be accepted as long as it satisfies one of
the items.
3.3 Monitoring and Maintenance of ISDN Configuration
In privileged mode, execute the following command to monitor the current state of
ISDN in real time.
Table LLC-3-2 Maintain and monitor ISDN
Operation Command
Show the current activated call information of ISDN
interface
Show all the information or the information of specified
interface
show isdn active [ interface interface-type
interface-number ]
Show the called number and sub-address to be checked on
ISDN interface
Show all the information or the information of specified
interface
show isdn answers [ interface interface-type
interface-number ]
Show the current state of ISDN interface
Show all the information or the information of specified
interface
show isdn status [ interface interface- type
interface-number ]
Show the value of ISDN timer show isdn timer
Enable the debugging of ISDN CC
debug isdn cc [ interface interface-type
interface-number ]
Disable the debugging of ISDN CC
no debug isdn cc [ interface interface-type
interface-number ]
Enable the debugging of ISDN q921 protocol
debug isdn q921 [ interface interface-type
interface-number ]
Disable the debugging of ISDN q921 protocol
no debug isdn q921 [ interface interface-type
interface-number ]
Turn on the debugging of ISDN q931 protocol
debug isdn q931 [ interface interface-type
interface-number ]
Disable the debugging of ISDN q931 protocol
no debug isdn q931 [ interface interface-type
interface-number ]
! Show the current activated call information of ISDN interface
Quidway# show isdn active interface bri 0
Bri0 ___________________________________________________________________
Channel Call Call Calling Calling Called called
Info Property Type Number Subaddress Number subaddress
__________________________________________________________________
B1 Digital Out 8810124
B2 Analog In 8810118 380 8810150 2201
The information shown above indicates that currently there are two activated calls on
the ISDN Bri0 interface:
l The outgoing digital call from B1 channel to 8810124.
l The incoming analog calls from the terminal with the number 8810118 and sub-
address 380 to B2 channel.
! Show the called number and sub-address to be checked on ISDN interface
Quidway# show isdn answers interface bri 0
Bri0:
ISDN Answer1 66668888
ISDN Answer2 :sub2000
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 3
Configuring ISDN Protocol
3-3
The information shown above indicates that in the case of incoming digital call on the
interface Bri0, the called number to be checked is 66668888, the sub-address to be
checked additionally is sub2000.
! Show the current status of ISDN interface
Quidway# show isdn status interface bri 0
Bri0:
Layer 2 Status:
TEI = 64, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
2 Active Layer 3 Call(s)
CCIndex = 0x0001 , State = Setup , CES = 1 , Channel =0x00000002
Calling_Num=661003,Calling_Sub=,Called_Num = 660066,Called_Sub =
CCIndex = 0x0000,State = Active , CES = 1 , Channel = 0x00000001
Calling_Num=661004,Calling_Sub=,Called_Num=660066 , Called_Sub =
The information shown above indicates that layer-2 link TEI of ISDN interface Bri0 is 64,
and the status is that multiple frames are established. The number of active calls of
layer 3 is 2, the call with the index number 0x0001 is being set up, CES is 1, the channel
is 0x00000002, the calling and called numbers are respectively 661003 and 660066,
and both the calling and called sub-addresses are empty. The call with the index
number 0x0000 is active, CES is 1, the channel is 0x00000001, the calling and called
numbers are respectively 661004 and 660066, and both the calling and called sub-
addresses are empty.
! Show the value of ISDN timer
Quidway# show isdn timer
ISDN Layer 2 values
K = 1 Outstanding I-frames on BRI port
N200 = 3 Max number of retransmits
T200 = 1 Seconds
T202 = 2 Seconds
T203 = 10 Seconds
ISDN Layer 3 values
T301 = 240 Seconds
T302 = 15 Seconds
T303 = 4 Seconds
T304 = 30 Seconds
T305 = 30 Seconds
T308 = 4 Seconds
T309 = 90 Seconds
T310 = 10 Seconds
T313 = 4 Seconds
T314 = 4 Seconds
T316 = 120 Seconds
T317 = 10 Seconds
T318 = 4 Seconds
T319 = 4 Seconds
T321 = 30 Seconds
T322 = 4 Seconds
& Note:
If there is only one type of ISDN interface (BRI or PRI) in the router, only the K value of corresponding
interface is shown.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 3
Configuring ISDN Protocol
3-4
3.4 Typical ISDN Configuration Example
I. Networking requirement
Router A is connected with router B via WAN, as shown in the following diagram.
II. Networking diagram
Router A
ISDN switching
network
8810154
cE1/PRI
202.38.154.2
202.38.154.1
8810152
cE1/PRI
Router B
Figure LLC-3-1 Networking diagram of ISDN protocol configuration example
III. Configuration procedure
l Configure Router A:
! Configure the timeslot binding of B channel of PRI interface
Quidway(config)# controller e1 0
Quidway(config-if-e1-0)# pri-group timeslots 1-31
Quidway(config-if-e1-0)# exit
! Configure D channel of PRI interface
Quidway(config)# interface serial 2:15
! Configure IP address
Quidway(config-if-Serial2: 15)# ip address 202.38.154.1 255.255.0.0
! Configure dialer
Quidway(config-if-Serial2: 15)# dialer map ip 202.38.154.2 8810154
Quidway(config-if-Serial2: 15)# dialer-group 1
Quidway(config-if-Serial2: 15)# exit
Quidway(config)# dialer-list 1 protocol ip permit
l Configure Router B:
! Configure the timeslot binding of B channel of PRI interface
Quidway(config)# controller e1 0
Quidway(config-if-e1-0)# pri-group timeslots 1-31
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 3
Configuring ISDN Protocol
3-5
Quidway(config-if-e1-0)# exit
! Configure D channel of PRI interface
Quidway(config)# interface serial 2:15
! Configure IP address
Quidway(config-if-Serial2: 15)# ip address 202.38.154.2 255.255.0.0
! Configure dialer
Quidway(config-if-Serial2: 15)# dialer map ip 202.38.154.1 8810152
Quidway(config-if-Serial2: 15)# dialer-group 1
Quidway(config-if-Serial2: 15)# exit
Quidway(config)# dialer-list 1 protocol ip permit
Either ping 202.38.154.2 on Router A or ping 202.38.154.1 on Router B can be
successful.
3.5 Fault Diagnosis and Troubleshooting of ISDN
Fault: In the typical configuration example, cannot ping through the two routers.
Troubleshooting:
l Execute the command show isdn status and there is no isdn port is displayed, it
indicates that ISDN BRI or PRI port is not configured. Configure with the method in
the configuration example.
l If the information debugging of Q.921 is enabled and ISDN-D send data error is
displayed, it indicates that the physical layer is not activated. Try the following
methods to shut down and reopen the related interface:
Quidway(config)# interface serial 2:15
Quidway(config-if-Serial2:15)# shutdown
Quidway(config-if-Serial2:15)# no shutdown
l For BRI interface, the corresponding process is as follows:
Quidway(config)# interface bri 0
Quidway(config-if-Bri0)# shutdown
Quidway(config-if-Bri0)# no shutdown
l Check whether the dialer is configured correctly
l If the dialer is configured correctly and no ISDN-D send data error is displayed,
then it's possible the ISDN line is not connected well.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-1
Chapter 4 Configuring LAPB, X.25 and X.25
Switching
4.1 X.25 and LAPB Protocols Overview
X.25 protocol is the interface procedure between the data terminal equipment (DTE)
and data circuit-terminating equipment (DCE). In 1974, CCITT issued the first draft of
X.25, whose initial files were based on the experiences and recommendations of
Telenet and Tymnet of USA and Datapac packet-switched networks of Canada. It was
revised in 1976, 1978, 1980 and 1984, added many optional service functions and
facilities.
With X.25, two DTE can communicate with each other via the existing telephone
network. X.25 sessions are established when one DTE device contacts another to
request a communication session. The DTE device that receives the request can either
accept or refuse the connection. If the request is accepted, the two systems begin
full-duplex information transfer. Either DTE device can terminate the connection. After
the session is terminated, any further communication requires the establishment of a
new session.
X.25 is the protocol of point-to-point interaction between DTE and DCE. DTE usually
refers to the host or terminal at the user side, and DCE usually refers to the
synchronous modem. DTE is connected with DCE directly, DCE is connected to a port
of packet switching exchange, and some connections are established between the
packet switching exchanges, thus forming the paths between different DTE. In an X.25
network, the relation between entities is shown in the following diagram:
DCE DTE
DCE
DCE
DTE
DTE
PSE
PSE
PSE
PSN
Figure LLC-4-1 X.25 network model
In the above figure, DTE stands for Data Terminal Equipment, DCE for Data Circuit-
terminating Equipment, PSE for Packet Switching Equipment, and PSN for Packet
Switched Network.
The X.25 protocol suite maps to the lowest three layers of the OSI (Open System
Interconnection) reference model. The following protocols are typically used in X.25
implementations: Packet-Layer Protocol (PLP), Link Access Procedure Balanced
(LAPB), and those among other physical-layer serial interfaces. X.25 layer 3 (packet-
layer protocol) describes the format of packet used by the packet layer and the
procedure of packet switching between two 3-layer entities. X.25 layer 2 (link-layer
protocol), also called LAPB (Link Access Procedure Balanced), defines the format and
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-2
procedure of interactive frames between DTE and DCE. X.25 layer 1 (physical-layer
protocol) defines some physical and electrical characteristics in the connection
between DTE and DCE. The above relation is shown in the following diagram.
OSI reference model
7
6
5
4
3
2
1
X.25
Packet layer
interface
Link layer
interface
Physical layer
interface
DTE
DCE
X.25
Physical layer
X.25
Link layer
X.25
Packet layer
X.25
Physical layer
X.25
Link layer
X.25
Packet layer
Figure LLC-4-2 DTE/DCE interface
A virtual circuit is a logical connection created to ensure reliable communication
between two network devices. A virtual circuit denotes the existence of a logical, bi-
directional path from one DTE device to another across an X.25 network. Two types of
X.25 virtual circuits exist: permanent virtual circuit (PVC) and switched virtual circuit
(SVC). PVCs are permanently established connections used for frequent and
consistent data transfers, whereas SVCs are temporary connections used for sporadic
data transfers.
Once a virtual circuit is established between a pair of DTEs, it is assigned with a unique
virtual circuit number. When one DTE is to send a packet to the other, it numbers this
packet (with virtual circuit number) and sends it to DCE. According to the number on
the packet, DCE determines the method to switch this packet within the switching
network, so that this packet can reach the destination. A link established between DTE
and DCE by X.25 layer X.25 layer 3 multiplexes 2 (LAPB), and those finally presented
to users are several usable virtual circuits.
The relation between packets and frames in various X.25 layers is shown in the
following diagram.
Packet
header
User data
Data
Frame
header
FCS
Frame
delimiter
Bit stream
X.25 layer 3 Packet
X.25 layer 2 Frame
X.25 layer 1
Frame
delimiter
Figure LLC-4-3 X.25 packet and LAPB frame
X.25 link layer specifies the frame switching process between DTE and DCE. In terms
of hierarchy, the link layer seems to bridge the packet layer interface of DTE and that of
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-3
DCE. Through this bridge, the packets can be transmitted continuously between the
packet layer of DTE and that of DCE. The link layer has such main functions as follows:
l Transmit the data effectively between DTE and DCE
l Ensure the synchronization of information between the receiver and transmitter
l Detect and correct the error in the transmission
l Identify and report the procedure error to the higher layer protocol
l Inform the packet layer of the link layer state
As specified in international standards, X.25 link layer protocol LAPB adopts the frame
structure of high-level data link control (HDLC) and the frame structure is a subset of
LAPB. The bi-directional link will be established when either site sends an SABM (Set
Asynchronous Balanced mode) command and the other replies with UA.
Defined as X.25 layer-2 protocol, LAPB is actually a separate link layer protocol, which
can transmit the data with LAPB bearing non-X.25 upper layer protocol. Quidway

series
router can directly employ LAPB protocol to encapsulate the serial port and perform
simple local data transmission. Meanwhile, X.25 of Quidway

series router has
switching function, that is to say, the router can be used as a small X.25 packet switch.
The following diagram shows the relations among LAPB, X.25 and X.25 switching.
Inter-network protocol
X.25
switching
X.25
LAPB
Figure LLC-4-4 Relations among LAPB, X.25 and X.25 switching
4.2 Configuring LAPB
4.2.1 LAPB Configuration Task List
To directly encapsulate the synchronous serial port as LAPB protocol, perform the
following configuration tasks:
l Configure encapsulation LAPB protocol
l Configure LAPB protocol parameters
4.2.2 Configuring Encapsulation LAPB Protocol
In the interface configuration mode, perform the following task to configure the link
layer protocol encapsulated for interface as lapb.
Table LLC-4-1 Configure encapsulation LAPB protocol
Operation Command
Configure encapsulation LAPB protocol encapsulation lapb [ dte | dce ] [ ip ]
If not specified, the working mode of LAPB is DTE by default. Besides, when LAPB
protocol is directly encapsulated, the upper layer protocol can be specified (IP is
supported currently).
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-4
4.2.3 Configuring LAPB Protocol Parameter
After specifying the encapsulation mode of LAPB, configure LAPB protocol parameter.
LAPB corresponds to the data link layer of OSI reference mode. LAPB specifies
methods for exchanging data (frames), detecting out-of-sequence or missing frames,
redirecting frames, and acknowledging frames. Several protocol parameters can be
modified to change LAPB protocol performance on a particular link. Modifying
parameters is mainly according to the indexes such as the reliability and delay of the
connection.
I. Configuring LAPB operating mode (also called modulo)
There are two LAPB modulos: Modulo 8 and Modulo128. Each data frame (I frame) is
numbered by sequence, the number can be any from 0 to modulo minus 1, and the
sequence number is selected cyclically within the range of the modulo.
Modulo 8 (basic mode) is widely available because it is required for all standard LAPB
implementations and is sufficient for most links. Modulo128 (extended mode) can
achieve greater throughput on high-speed links that have a low error rate by increasing
the number of frames that can be sent before the sending device must wait for
acknowledgment (as configured by LAPB parameter K). The maximum value of LAPB
window parameter K is modulo minus 1
In the interface configuration mode, configure as follows:
Table LLC-4-2 Configure LAPB frame numbering mode
Operation Command
Configure LAPB frame numbering mode (also called modulo) lapb modulo { 128 | 8 }
By default, the LAPB modulos is Modulo 8.
II. Configuring LAPB parameter K
LAPB parameter K must be at most one less than the operating modulo. Modulo 8 links
can send seven frames before an acknowledgment must be received by the sending
device; modulo 128 links can send as many as 127 frames. By default, LAPB links use
the basic mode with a window of 7.
In the interface configuration mode, configure as follows:
Table LLC-4-3 Configure LAPB window parameter K
Operation Command
Configure LAPB window parameter K lapb k k-value
Restore the default value of LAPB window parameter K no lapb k
By default, k is 7.
III. Configuring LAPB N1, N2
LAPB N1 is the maximum number of bits in a LAPB frame, which determines the
maximum size of an X.25 packet. When you use LAPB over leased lines, the N1
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-5
parameter should be eight times the hardware MTU size plus lapb protocol head
length.
The transmitting counter (N2) is the number of unsuccessful transmitting attempts that
are made before the link is declared down.
Table LLC-4-4 Configure LAPB N1, N2
Operation Command
Configure LAPB parameter N1 lapb n1 n1-value
Restore the default value of LAPB parameter N1 no lapb n1
Configure LAPB parameter N2 lapb n2 n2-value
Restore the default value of LAPB parameter N2 no lapb n2
By default, n1 is 12032, and n2 is 10.
IV. Configuring LAPB T1, T2, T3
LAPB T1, the retransmission timer (T1) determines how long a sent frame can remain
unacknowledged before retransmission. The timer setting must be large enough to
permit a maximum-sized frame to complete one round trip on the link.
LAPB T2, the receiving timer (T1) determines when to send a confirmation frame to the
opposite DCE (or DTE) before T1 runs out (T2<T1).
LAPB T3, the idle channel timer, determines when to report the long-time idle channel
state to the packet layer. The timer setting must be larger than T1 in DCE (T3>T1). If T3
is 0, it indicates that the timer is not in function.
Table LLC-4-5 Configure LAPB system timer T1, T2, T3
Operation Command
Configure LAPB system timer T1 lapb t1 t1-value
Restore the default value of LAPB system timer T1 no lapb t1
Configure LAPB system timer T2 lapb t2 t2-value
Restore the default value of LAPB system timer T2 no lapb t2
Configure LAPB system timer T3 lapb t3 t3-value
Restore the default value of LAPB system timer T3 no lapb t3
By default, T1 is 2000ms; T2 is 1000ms and T3 is 0ms.
4.3 Configuring X.25
4.3.1 X.25 Configuration Task List
To transmit data between two routers, you only need to perform simple serial interface
encapsulation using LAPB. If the router is to transmit the data through X.25 public
network, X.25 protocol must be used to encapsulate the serial interface, and X.25
protocol should be configured according to the parameters provided by the network
service provider. Here, we will introduce each of X.25 configuration tasks in detail.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-6
I. Configuring X.25 interface
l Configure X.25 working mode
l Configure virtual circuit range
l Configure packet numbering modulo
l Configure X.121 address
l Configure default flow control parameter (including the setting of window size and
packet length)
II. Configuring X.25 interface supplementary parameter
1) Configure the time delay of X.25 layer 3 timer
2) Configure the attributes related to X.25 address, including the following
configuration items:
l Configure the alias of interface address
l Configure to skip the calling or called address
l Configure whether to check the address code block in call accepting packet.
l Configure whether to carry the address code block in call accept packet
l Configure default upper layer protocol
l Prohibit the restart of X.25 layer 3
III. Configuring X.25 datagram transmission
1) Create the mapping from the protocol address to X.121 address, including the
following configuration items:
l About the encapsulation of protocol datagram
l About the protocol identifier
l Create the address mapping
2) Create the permanent virtual circuit
IV. Configuring the supplementary parameters of X.25 datagram transmission
1) Specify the maximum idle time of SVC
2) Specify the maximum number of SVCs that is associated with the same address
mapping
3) Specify the pre-acknowledgement of packet
4) Configure X.25 user facility
5) Set the length of virtual circuit queue
6) Broadcast via X.25
7) Restrict the use of address mapping
8) Configure the interface with the backup center
Transmit the data with X.25. Choose one task or any task combination according to
specific condition of the employed X.25 public network. Before performing any
configuration task, the X.25 protocol parameter corresponding to this task is default
value. Contact the service provider for the parameter values. The X.25 supported by
Quidway series router also provides other configuration methods. Besides, appropriate
modification to some LAPB parameters in certain cases can also optimize the
performance of X.25.
4.3.2 Configuring X.25 Interface
Only when configured as an X.25 interface, can an interface transmit data with X.25
protocol.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-7
& Note:
In the following configuration commands, only Configure X.25 working mode is obligatory, and other
configuration items are optional, depending on the specific condition of X.25 network that is accessed.
I. Configuring X.25 working mode
To configure X.25 working mode, perform the following task in the interface
configuration mode.
Table LLC-4-6 Set X.25 working mode
Operation Command
Set the working mode and encapsulation format of X.25 interface
encapsulation x25 [ [ dte | dce ] | [ bfe |
cisco-compatible | ddn | ietf ] ]
Layer 3 of X.25 supported by Quidway series router can work in both DTE mode and
DCE mode. It can also specify the datagram encapsulation format among the four
optional encapsulation formats: BFE, Cisco-compatible, DDN and IETF.
Note that generally speaking, public X.25 packet switching network requires the router
to access at DTE side and requires the IETF encapsulation format. Therefore, the
working mode of X.25 should be DTE and the encapsulation format should be IETF. If a
pair of serial interfaces of two routers is directly connected for data transmission, make
sure the two transmission ends are DTE and DCE and the encapsulation formats are
the same.
For X.25 supported by Quidway series router, default working mode is DTE and default
encapsulation format is IETF.
II. Configuring X.25 virtual circuit range
X.25 protocol can multiplex multiple virtual connection over a real physical link between
DTE and DCE, also called virtual circuit (VC) or logic channel (LC). X.25 can establish
up to 4095 virtual connections numbered from 1 to 4095. The number that can be
employed to identify each virtual circuit (or logic channel) is called logic channel
identifier (LCI) or virtual circuit number (VCN).
& Note:
Strictly speaking, virtual circuit and logic channel are two different concepts. However, they are not
differentiated so strictly at the user side.
An important part of X.25 operation is the virtual circuit channel sequence. This
sequence is a range of virtual circuit channel numbers broken into four ranges (listed
here in numerically increasing order):
l Permanent virtual circuits (PVCs)
l Incoming-only circuits
l Two-way circuits
l Outgoing-only circuits
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-8
The incoming-only, two-way, and outgoing-only ranges define the VC numbers over
which a switched virtual circuit (SVC) can be established by the placement of an X.25
call. The permanent virtual circuits must be set in the PVCs range.
According to ITU-T Recommendation X.25, the rules about DCE and DTE devices
initiating calls are as follows:
l Only the DCE device can initiate a call in the incoming-only range.
l Only the DTE device can initiate a call in the outgoing-only range.
l Both the DCE device and the DTE device can initiate a call in the two-way range.
l DCE always uses the lowest available logic channel.
l DTE always uses the highest available logic channel.
Thus, we can avoid the case that one side of the communication occupies all the
channels, and minimize the possibility of call collision.
In X.25 protocol, six parameters are employed to delimit the four sections, as shown in
the diagram below.
1
LTC
LIC
HTC
HIC
LOC
HOC
4095
Permanent virtual circuit
Incoming-only channel
Unused
Two-way channel
Unused
Outgoing-only channel
Unused
Figure LLC-4-5 X.25 channel delimitation
For the meanings of these six parameters, please refer to Table 4-4.
Table LLC-4-7 X.25 channel delimitation parameters
Parameter Meaning
LIC Lowest Incoming-only Channel
HIC Highest Incoming-only Channel
LTC Lowest Two-way Channel
HTC Highest Two-way Channel
LOC Lowest Outgoing-only Channel
HOC Highest Outgoing-only Channel
Perform the following task in the interface configuration mode:
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-9
Table LLC-4-8 Set/cancel X.25 virtual circuit range
Operation Command
Set the lowest incoming-only channel number
Default value: 0
x25 lic circuit-number
Cancel the set lowest incoming-only channel number no x25 lic
Set the highest incoming-only channel number
Default value: 0
x25 hic circuit-number
Cancel the set highest incoming-only channel number no x25 hic
Set the lowest two-way channel number
Default value: 1
x25 ltc circuit-number
Cancel the set lowest two-way channel number no x25 ltc
Set the highest two-way channel number
Default value: 1024
x25 htc circuit-number
Cancel the set highest two-way channel number no x25 htc
Set the lowest outgoing-only channel number
Default value: 0
x25 loc circuit-number
Cancel the set lowest outgoing-only channel number no x25 loc
Set the highest outgoing-only channel number
Default value: 0
x25 hoc circuit-number
Cancel the set highest outgoing-only channel number no x25 hoc
The above shows that each section (except the permanent virtual circuit section) is
defined by two parameters: upper limit and lower limit, the value of which ranges
between 1 and 4095 (including 1 and 4095). Correct configuration must satisfy the
following conditions:
l In strict numerically increasing order, i.e. 1 lic hic<ltc htc<loc hoc 4095.
l If the upper limit (or lower limit) of a section is 0, then the lower limit (or upper limit)
shall also be 0, (which indicates this section is prohibited to use).
Finally, the following should be noted:
l At the two sides (i.e. DTE and DCE) of a physical connection, the six parameters
of X.25 must be equal correspondingly, otherwise, the procedure will possibly to
operate abnormally, resulting in data transmission failure.
l During the configuration, after ensuring the numerically increasing order, pay
attention to the default values of various parameters, and set the parameters
according to actual condition.
l Because X.25 protocol requires DTE and DCE to have the same virtual circuit
range parameters, the new configuration can not take effect immediately after
successful X.25 protocol negotiation. It is necessary to first execute shutdown
and no shutdown commands.
III. Configure X.25 packet sequence numbering modulo
The implementation of X.25 in Quidway series router supports both modulo 8 and
modulo 128 packet sequence numbering. Module 8 is the default.
To set/cancel the packet sequence numbering, perform the following task in the
interface configuration mode:
Table LLC-4-9 Set/Cancel X.25 packet numbering modulo
Operation Command
Set the packet sequence numbering mode x25 modulo { 8 | 128 }
Cancel the set packet sequence numbering mode no x25 modulo
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-10
& Note:
Please note that X.25 procedure requires DTE and DCE to have the same packet numbering mode,
therefore the configuration will take effect by executing the shutdown and no shutdown commands.
Besides, the packet sequence numbering mode of X.25 layer 3 is different from the frame sequence
numbering mode of LAPB (X.25 layer 2). When modulo 128 numbering mode is employed in the DTE/DCE
interface with high throughput rate, for LAPB, only the efficiency of local DTE/DCE interface is affected,
that is point-to-point efficiency increases. While for X.25 layer 3, the efficiency of end-to-end is affected,
that is, the efficiency between two sets of communicating DTE increases.
IV. Configuring X.121 address
If the Quidway

series router does not originate or terminate calls but only participates in
X.25 switching, this task is optional. However, if the Quidway series router is attached
to a PDN, you must set the interface X.121 address assigned by the X.25 network
service provider. Interfaces that use the DDN or BFE mode will have an X.121 address
generated from the interface IP address; for correct DDN or BFE operation, any such
X.121 address must not be modified! You only need to specify an X.121 address for the
X.25 interface encapsulated in IETF format.
To set/cancel the X.121 address, perform the following task in interface configuration
mode.
Table LLC-4-10 Set/Cancel the X.121 address of the interface
Operation Command
Set the X.121 address of the interface x25 address x.121-address
Cancel the set X.121 address of the interface no x25 address
V. Configuring the default flow control parameter
Setting correct default flow control parameters (window size and packet size) is
essential for correct operation of the link because X.25 is a strongly flow controlled
protocol. Mismatched default flow control values will cause X.25 local procedure errors,
evidenced by CLEAR and RESET events. However, most public X.25 packet networks
use the default window size and maximum packet size specified in ITU-T X.25
Recommendation, which is also true for Quidway series router. Therefore, this task
may be optional without special requirements of service provider.
After setting default window size and default maximum packet size, the SVCs that can
be established only with call process will use these default values if related parameters
are not negotiated in the call process. The PVCs that can be established without call
process will also use these default values if no window size or packet size option is
assigned when specifying PVC.
X.25 transmitting end will fragment the too long data message of upper layer according
to the maximum packet size and mark in the last fragment packet (M bit is not set).
When the message reaches the receiving end, X.25 regroups all these fragment
packets, and judges whether a complete message is received according to M bit
marker. Therefore, too small value of the maximum packet size will consume too much
router resources on message fragmenting and repacket, thus lowering efficiency.
Finally, the following two points should be noted:
l Maximum packet size < MTU*8 < LAPB N1.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-11
l New configuration will take effect only after executing shutdown and no shutdown
commands
To set/cancel the default flow control parameter, perform the following tasks.
Table LLC-4-11 Set the default flow control parameter
Operation Command
Set the default receiving window size of virtual circuit
Default value: 2
x25 win packets
Cancel the set default receiving window size of virtual circuit no x25 win
Set the default sending window size of virtual circuit
Default value: 2
x25 wout packets
Cancel the set default sending window size of virtual circuit no x25 wout
Set the default receiving maximum packet length
Default value: 128
x25 ips bytes
Cancel the set default receiving maximum packet length no x25 ips
Set the default sending maximum packet length
Default value: 128
x25 ops bytes
Cancel the set default sending maximum packet length no x25 ops
4.3.3 Configuring X.25 Interface Supplementary Parameter
It's necessary to configure certain supplementary X.25 parameters in some special
network environments.
I. Configuring the delay of X.25 layer 3 timer
X.25 protocol defines a series of timers to facilitate its procedure. After X.25 sends a
control message, if it does not receive the response before the timeout of the
corresponding timer, X.25 protocol will take corresponding measure to handle this
abnormal event. The names and corresponding procedures of these timers are shown
in the following table.
Table LLC-4-12 X.25 layer 3 timer
Timer name
Procedure name
DTE side DCE side
Restart T20 T10
Call T21 T11
Restore T22 T12
Clear T23 T13
Register T28
In the table, T28 is the timer of sending register request , and is only defined at the
DTE side. It is used to dynamically apply for or stop the selective services in the
network. Its reference value is 300 seconds, and cannot be modified. Perform the
following tasks in the interface configuration mode.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-12
Table LLC-4-13 Set X.25 layer 3 timer delay
Operation Command
Set the timer delay value of restart procedure
Default value (second):DTE 180 DCE 60
x25 tx0 seconds
Cancel the set timer delay value of restart procedure no x25 tx0
Set the timer delay value of call procedure
Default value (second):DTE: 200 DCE: 180
x25 tx1 seconds
Cancel the set timer delay value of call procedure no x25 tx1
Set the timer delay value of restore procedure
Default value (second):DTE: 180 DCE: 60
x25 tx2 seconds
Cancel the set timer delay value of restore procedure no x25 tx2
Set the timer delay value of clearing procedure
Default value (second):DTE: 180 DCE: 60
x25 tx3 seconds
Cancel the set timer delay value of clearing procedure no x25 tx3
II. Configuring the attribute related to X.25 address
To establish a SVC with a call, X.25 address is needed, which adopts the address
format specified in ITU-T Recommendation X.121. X.121 address consists of a string of
Arabic numerals from 0 to 15.
1) Configure an alias for the interface
When an X.25 call is forwarded across the network, different networks will likely to
make some modifications on the called address according to their own needs, such as
adding or deleting the prefix. In such cases, the destination address of a call that
reaches X.25 interface may be inconsistent with X.121 address of the destination
interface (because the destination address of this call is modified within the network),
still the interface will accept this call. At this time, one or multiple aliases should be
specified for this interface by performing the following tasks in the interface
configuration mode:
Table LLC-4-14 Specify/Cancel an alias for the interface
Task Command
Specify an alias for the interface x25 alias match-type alias-string
Cancel the specification of an alias for the interface no x25 alias match-type alias-string
To satisfy the requirements of different networks, nine matching modes and the formats
of corresponding alias strings are defined for X.25 in Quidway series router, as shown
in the following table.
Table LLC-4-15 Alias match modes and meanings
Matching mode Meaning Example
Free
Free matching, the alias string is in the
form of 1234
1234 will match with 561234, 1234567 and
956123478, but will not match with 12354.
free-ext
Extended free matching, the alias string
is in the formof 0.1234..
1234.. will match with 678123459, but will
not match with 68123459, 67812345 and
6781234591.
Left
Left-justified matching mode, the alias
string is in the form of $1234
$1234 will match with 1234567 and 12346790,
but will not match with 3123478 and 123784.
left-ext
Extended left-justified matching mode,
the alias string is in the form of $1234
$1234will match with 1234679 and
1234872, but will not match with 123468 and
12346890.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-13
Matching mode Meaning Example
Right
Right-justified match mode, the alias
string is in the form of 1234$
1234$ will match with 791234 and 6901234,
but will not match with 7912345 and 6212534.
right-ext
Extended right-justified matching mode,
the alias string is in the form of .1234$
.1234$ will match with 79001234 and
86901234, but will not match with 7912345 and
506212534.
Strict
Strict matching mode, the alias string is
in the formof $1234$
$1234$ can only match with 1234
Whole
Whole matching mode, the alias string is
in the form of ........
........ will match with all the valid X.121
addresses with the length of 8
whole-ext
Extended whole matching mode, the
alias string can only be *
* will match with all the valid X.121 addresses
2) Configure the attributes related to the address code block in the call packet or call
accept packet
As specified in X.25 protocol, the call packet must carry the information set of both the
calling DTE address (source address) and the called DTE address (destination
address). This address information set is called the address code block. While in call
accept packet, some networks require that both (the calling DTE address and the
called DTE address) be carried, some networks require that only one of the two be
carried, while some others require that neither should be carried. X.25 in Quidway
series router enables users to make choices according to the requirement of specific
network. Perform the following task in interface configuration mode.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-14
Table LLC-4-16 Configure/Cancel the attributes related to the address code block in the call packet or call
accept packet
Operation Command
Not carrying the called DTE address information when a call is originated
Default: carry
x25 suppress-called-address (by
default)
Cancel not carrying the called DTE address information when a call is
originated
no x25 suppress-called-address
Not carrying the calling DTE address information when a call is originated
Default: carry
x25 suppress-calling-address (by
default)
Cancel not carrying of the calling DTE address information in a call no x25 suppress-calling-address
Not carrying the called DTE address information when the originated call is
accepted
Default: not carry
x25 response-called-address
Cancel not carrying of the called DTE address information when the
originated call is accepted
no x25 response-called-address
(by default)
Not carrying the calling DTE address information when the originated call is
accepted
Default: not carry
x25 response-calling-address
Cancel not carrying the calling DTE address information when the
originated call is accepted
no x25 response-calling-address
(by default)
Check the address code block after the response of the call is received
Default: not check
x25 check-response-address
Cancel check the address code block after the response of the call is
received
no x25 check-response-address
(by default)
By default, the upper protocol carried by X.25 is IP protocol.
3) Configure default upper layer protocol
In the X.25 call request packet, there is a field called Call User Data (CUD). The first
few bytes of this domain differentiate the message type of upper layer protocol this call
is bearing. When the router is the destination host, it will refuse to receive a call with
unrecognizable CUD. But an upper layer protocol can be specified as the default
protocol borne on the X.25 of the Quidway series router. When the X.25 of the Quidway
series router receives a call with an unrecognizable CUD, it will treat it as the default
upper layer protocol specified by user.
In the interface configuration mode, perform the following task to set/cancel the default
upper layer protocol borne on X.25.
Table LLC-4-17 Set/Cancel the default upper layer protocol borne on X.25
Operation Command
Specify the default upper layer protocol borne on X.25
Default: IP
x25 default [ ip | ipx ]
Cancel the specifying of the default upper layer protocol
borne on X.25
no x25 default [ ip | ipx ]
4) Prohibit the restart of X.25 layer 3
Generally, when the X.25 layer 2 (LAPB) is restarted, the X.25 layer 3 will also be
restarted. This is essential for the correct running of the protocol procedure. However,
user can also disable this function so that the X.25 layer 3 does not restart even after
the X.25 layer 2 is restarted. In the interface configuration mode, perform the following
task to prohibit the restart of X.25 layer 3.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-15
Table LLC-4-18 Permit/Prohibit the restart of X.25 layer 3
Operation Command
Enable the restart of X.25 layer 3 x25 linkrestart
Disable the restart of X.25 layer 3 no x25 linkrestart
By default, enable the restart of X.25 layer 3.
& Note:
Do not run this command unless absolutely necessary. It is recommended to enable the restart of X.25
layer 3.
4.3.4 Configuring X.25 Datagram Transmission
In the most frequently used X.25 service, data is transmitted remotely between two
hosts using the X.25 protocol via X.25 public packet network. As shown in the figure
below, LAN A and LAN B are far apart, and X.25 packet switching network can be used
to realize information exchange between them.
X.25
LAN A
LAN B
Router A
Router B
Figure LLC-4-6 LAN interconnection via X.25
The datagram uses IP address to communicate data and information between LAN A
and LAN B, whereas X.121 address is used inside X.25. Therefore, we setup correct
mapping between the IP address and X.121 address.
I. Creating the mapping from the protocol address to X.121 address
An X.25 interface has its own X.121 address and inter-network protocol (such as IP
protocol) address. When X.25 initiates a call through this interface, the source address
(calling DTE address) it carries in the call request packet is the X.121 address of this
interface.
For a datagram with a definite destination IP address, its corresponding X.121
destination address is located by the configured address mapping. The call destination,
just like a calling source, also has its own protocol address and X.121 address.
Establish the mapping between the destination protocol address and the X.121
address at the calling source, you can find the destination X.121 address according to
the destination protocol address, and successfully initiate a call.
In the interface configuration mode, perform the following commands to create/delete
an address mapping.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-16
Table LLC-4-19 Create/Delete the mapping from the protocol address to X.121 address
Operation Command
Create the mapping from the destination protocol
address to X.121 address
x25 map protocol protocol-address x.121-address
[ option ]
Delete the mapping from the destination protocol
address to X.121 address
no x25 map protocol protocol-address
& Note:
The protocol-address and x.121-address in the command line refer to the protocol address and X.121
address of the destination, not those of the source.
An address mapping should be created for every destination.
While creating an address mapping, specify its attributes with the option items. The meanings and specific
content of these options will be described in subsequent sections.
For the address mapping configuration example, refer to subsequent sections.
II. Creating the permanent virtual circuit (PVC)
A permanent virtual circuit can be created for large-traffic and stable data transmission
on leased line. Permanent virtual circuits (PVCs) do not need any call process and it
always exists. An address mapping will be created implicitly while a permanent virtual
circuit is created.
To create/delete a permanent virtual circuit, perform the following tasks in interface
configuration mode.
Table LLC-4-20 Create/Delete permanent virtual circuit
Operation Command
Create a permanent virtual circuit
x25 pvc pvc-number protocol protocol-address x.121-address
[ option ]
Delete a permanent virtual circuit no x25 pvc pvc-number
The format of this command shows that while a permanent virtual circuit is created, an
address mapping is also created for it. Similarly, the protocol-address and x.121-
address in the command also refer to the destination address. While creating a
permanent virtual circuit, some attributes of the PVC can also be selected via the option.
This [option] is a subset of [option] in the command "x25 map...... [ option]".
For configuration example of permanent virtual circuit, refer to subsequent sections.
4.3.5 Configuring Additional Parameters of X.25 Datagram Transmission
The X.25 of Quidway series router allows adding some additional characteristics,
including a series of optional user facilities stipulated in ITU-T Recommendation X.25.
This section shows how to configure such additional characteristics, including the
options in the two commands of "x25 map ......" and "x25 pvc......". Please select and
configure these additional characteristics according to the actual needs, X.25 network
structure and the services provided by service provider.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-17
I. Configuring SVC maximum idle time
Specify a time period, and if SVC is idle within this period (no packet interaction), then
X.25 of the Quidway series router will automatically clear this SVC to avoid
unnecessary expenses. Before the data packet is sent next time, this SVC will be
reestablished. So the activation of this characteristic will not affect data transmission.
In the interface configuration mode, this task can be accomplished in two different ways.
For details, refer to the table as follows.
Table LLC-4-21 Specify/Cancel SVC maximum idle time
Operation Command
Specify maximum idle time for all the SVCs on an interface x25 idle minutes
Specify maximum idle time for SVC associated with an
address mapping
x25 map protocol protocol-address x.121-
address idle minutes
Cancel specify maximum idle time for all the SVCs on an
interface
no x25 idle
II. Configuring the maximum number of SVCs that are associated with the
same address mapping
The maximum number of virtual circuits to be set up on the same address mapping can
be specified. The X.25 of Quidway series router can establish up to 8 virtual circuits on
one address mapping. In case of large traffic and low line rate, this parameter can be
increased properly to reduce data loss. By default, one address mapping is associated
with only one virtual circuit.
In the interface configuration mode, perform the following commands.
Table LLC-4-22 Specify/Cancel the maximum number of SVCs associated with the same address
mapping
Operation Command
Specify the maximum number of SVCs associated with all address
mappings on an X.25 interface
x25 nvc count
Specify the maximum number of SVCs associated with an address
mapping
x25 map protocol protocol-address
x.121-address nvc count
Cancel the maximum number of SVCs associated with all address
mappings on an X.25 interface
no x25 nvc
III. Configuring the pre-acknowledgment of packets
According to X.25 protocol, the receiving party will send an acknowledgment only after
the receiving window is full (the number of received packets equals the win value).
However, in some X.25 networks, the delays may be long, resulting in low efficiency of
sending and receiving. Therefore, we specify a value. Each time the number of
received packets reach the value, the acknowledgment will be sent to the peer, thus
improving receiving and sending efficiency. This value, called a "threshold", ranges
between 0 and win. If it is set to 1, every packet will be acknowledged. If it is set to win,
the acknowledgment will be sent only after the receiving window is full. In applications
requiring a high response speed, this function is especially important.
In the interface configuration mode, perform the following task.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-18
Table LLC-4-23 Specify/Cancel packet pre-acknowledgement
Operation Command
Set packet acknowledgment value x25 threshold packet-count
Cancel packet acknowledgment value no x25 threshold
IV. Configuring X.25 user facility
The X.25 in the Quidway series router supports the user facility options defined in
ITU-T Recommendation X.25, such as reverse charging negotiation and flow control
parameter negotiation. These configurations can be modified in two ways:
Configuration based on X.25 interface (use "x25 facility....." command); configuration
based on address mapping (use "x25 map......" command).
The configuration based on X.25 interface will be effective in every call originated from
this X.25 interface, while the configuration based on address mapping will be effective
only in the calls originated from this address mapping.
In the interface configuration mode, perform the following task.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-19
Table LLC-4-24 Configure X.25 user facility
Operation Command
Specify CUG (Closed User Group)
x25 facility cug group-number
Or
x25 map protocol protocol-address x.121-address cug
group_number
Cancel CUG number no x25 facility cug
Perform flow control parameter negotiation while
initiating a call
x25 facility packetsize in-size out-size
1
Or
x25 map protocol protocol-address x.121-address
packetsize in-size out-size
1
x25 facility windowsize in-size out-size
1
Or
x25 map protocol protocol-address x.121-address
windowsize in-size out-size
1
Cancel flow control parameter negotiation while
initiating a call
no x25 facility packetsize
Or
no x25 facility windowsize
Request reverse charging while initiating a call
x25 facility reverse
Or
x25 map protocol protocol-address x.121-address reverse
Cancel the request of reverse charging while
initiating a call
no x25 facility reverse
Receive calls with reverse charging requests
x25 accept-reverse
Or
x25 map protocol protocol-address x.121-address accept-
reverse
Request throughput-level negotiation while
initiating a call
x25 facility throughput in out
Or
x25 map protocol protocol-address x.121-address
throughput in out
Cancel the request of throughput-level negotiation
while initiating a call
no x25 facility throughput
Carry transmission delay request while initiating a
call
x25 facility transit-delay milliseconds
Or
x25 map protocol protocol-address x.121-address transit-
delay milliseconds
Cancel the carrying of transmission delay request
while initiating a call
no x25 facility transit-delay
Specify the use of ROA (Recognized operating
Agency)
x25 facility roa name
2
Or
x25 map protocol protocol-address x.121-address roa name
2
Cancel the use of ROA no x25 facility roa
Here:
windowsize and packetsize options are also supported in x25 pvc command.
However, in x25 pvc command, these two options specify the window size and
maximum packet length of the set PVC. If these two options are not selected in the x25
pvc command, the set PVC will choose the default value of X.25 interface.
name is the name of the ROA ID list configured by the command x25 roa in the global
configuration mode, for example:
Quidway(config)# x25 roa list1 12 34 567
In the serial port configuration mode, list1 can be quoted:
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-20
Quidway(config-if-Serial0)# x25 facility roa list1
V. Configuring the sending queue length of virtual circuit
The sending and receiving queue lengths of the virtual circuit can be specified for the
X.25 of the Quidway series router to adapt to different network environments. The
default queue length can contain 500 packets, but if data flow is very large, or the
transmission rate of the X.25 network is low, the queue length can be increased to
avoid unexpected data packet loss.
In the interface configuration mode, perform the following tasks to specify the length of
virtual circuit queue.
Table LLC-4-25 Configure the sending queue length of virtual circuit
Operation Command
Set the length of X.25 virtual circuit queue x25 hold-queue queue-size
Cancel set the length of X.25 virtual circuit queue no x25 hold-queue
VI. Broadcasting via X.25
Generally, inter-network protocols will need to send some broadcast datagrams for
specific purposes. On the broadcasting physical networks (such as Ethernet), such
requirements are naturally supported. But for non-broadcasting networks like X.25,
how to realize the broadcasting?
The X.25 of the Quidway series router enables decision of whether to duplicate and
send a broadcasting data packet to a destination. This is very important. For instance,
the broadcast-based application layer routing protocol will request broadcasting
datagram sent by X.25 to exchange routing information on the X.25 network.
It can be specified whether to send broadcasting data packets on the related virtual
circuits of both SVC and PVC.
Table LLC-4-26 Set broadcasting via X.25
Operation Command
Enable to send broadcasting data packets to the peer of the
SVC associated with this address mapping
x25 map protocol protocol-address
x.121-address broadcast
Enable to send broadcasting data packets to the peer of this
PVC
x25 pvc pvc-number protocol protocol-address
x.121-address broadcast
VII. Restricting the use of address mapping
X.25 calls are closely related to address mapping: before a destination is called, this
destination must be found in the address mapping table. Before a call is received, the
source of this call must also be found in the address mapping table. But in some cases,
some address mappings are used for calling out only, while others are used for calling
in only.
The X.25 of the Quidway series router allows restricting the use of this address
mapping addition by adding some option items, as shown in the following table.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-21
Table LLC-4-27 Restrict the use of address mapping
Operation Command
Inhibit outgoing call through this address mapping
x25 map protocol protocol-address
X.121-address no-outgoing
Inhibit incoming call through this address mapping
x25 map protocol protocol-address
X.121-address no-incoming
VIII. Configuring interface with backup center
The powerful backup function of Quidway series router is provided by the "backup
center". To add an X.25 interface into the backup center, perform the following task in
the interface configuration mode (for details of the "backup center", refer to the chapter
about Backup Center ).
Table LLC-4-28 Set interface with backup center
Operation Command
Set the logic interface number of this address mapping in the
backup center
X25 map protocol protocol-address x.121-
address lin logical-interface-number
4.3.6 Configuring X.25 Sub-Interface
X.25 sub-interface is a virtual interface with its own protocol address and virtual circuit.
Multiple sub-interfaces can be created on a physical interface, so the networks can be
interconnected via one physical interface. The sub-interface of X.25 falls into two types:
point-to-point sub-interface, used to connect a single remote end and point-to-
multipoint sub-interface, used to connect multiple remote ends in the same network
segment.
In the interface configuration mode, perform the following task to configure X.25 sub-
interface.
Table LLC-4-29 Configure X.25 sub-Interface
Operation Command
Create X.25 sub-interface
interface serial number.subinterface-
number{multipoint|point-to-point}
Configure address mapping
Or
Configure permanent virtual circuit
x25 map protocol protocol-address x.121-address [option]
or
x25 pvc pvc-number protocol protocol-address
x.121-address [option]
4.3.7 Configuring X.25 Switching
I. X.25 switching function
A packet network consists of many nodes interconnected in a certain topological
structure. From the source to its destination, a packet will pass through many nodes,
each of which must have packet switching capability.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-22
To put it simply, X.25 packet switching means to receive packets from one X.25 port,
and send them out from the X.25 port selected according to related destination address
information contained in the packets. X.25 switching enables the Quidway series router
to perform packet switching function in the packet layer, and to be used as a small
packet switching exchange.
Quidway series router provides such X.25 switching functions as follows:
l SVC switching function
l Support parameter negotiation on window size and packet size
l PVC switching
The following describes how to configure X.25 switching tables for PVC and SVC.
PC
PC
Quidway Router
X.25 host
X.25 host
Figure LLC-4-7 X.25 switching networking diagram
II. Enabling or disabling X.25 switching
In the global configuration mode, perform the following task to enable or disable X.25
switching.
Table LLC-4-30 Enable or disable X.25 switching
Operation Command
Enable X.25 switching x25 routing
Disable X.25 switching no x25 routing
III. Adding or deleting a PVC route
Table LLC-4-31 Add or delete a PVC route
Operation Command
Add a PVC route x25 pvc number interface serial port-number pvc number
Delete a PVC route no x25 pvc number interface serial port-number pvc number
Example: Set to encapsulate X.25 on a router's serial port 0 and serial port 1, add PVC
virtual circuit route into the virtual circuit route table, so that packets can be switched
between the 1st PVC of serial port 0 and the 1st PVC of serial port 1.
Quidway(config)# x25 routing
Quidway(config)# interface serial 0
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-23
Quidway(config-if-Serial0)# encapsulation x25 dce
Quidway(config-if-Serial0)# x25 lic 10
Quidway(config-if-Serial0)# x25 hic 20
Quidway(config-if-Serial0)# x25 ltc 30
Quidway(config-if-Serial0)# exit
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# encapsulation x25 dce
Quidway(config-if-Serial1)# x25 lic 10
Quidway(config-if-Serial1)# x25 hic 20
Quidway(config-if-Serial1)# x25 ltc 30
Quidway(config-if-Serial1)# x25 pvc 1 interface serial 0 pvc 1
In the configuration of PVC switching, the two connected ports must be encapsulated
into X.25, and there should be valid Permanent virtual circuits (PVCs). After
configuration, the show x25 vc command can be used to show the virtual circuit route
table. For this command, refer to the section about X.25 configuration.
IV. Adding/Deleting an SVC route
In the global configuration mode, the commands in the following table can be used to
add or delete an SVC route.
Table LLC-4-32 Add or delete an SVC route
Operation Command
Add an SVC route x25 route x.121-addr interface serial interface-number
Delete an SVC route no x25 route x.121-addr interface serial interface -number
Example: Set to encapsulate serial port 0 and serial port 1 as X.25, add into the X.25
switching route table SVC switching routes: 1 S0, 2 S1.
Then the two hosts connected to this router can directly communicate with each other
on X.25 by calling 1 and 2.
Quidway(config)# x25 routing
Quidway(config-if-Serial0)# encapsulation x25 dce ietf
Quidway(config-if-Serial0)# exit
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# encapsulation x25 dce ietf
Quidway(config)# x25 route 1 interface serial 0
Quidway(config)# x25 route 2 interface serial 1
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-24
& Note:
The window size and packet size of the two hosts switched via the Quidway series router can be different.
The smaller value of the two can be negotiated via the switching module.
In the configuration of SVC switching, the two connected ports do not have to be
encapsulated as X.25, but during communication they must be encapsulated. After the
configuration, use show x25 route command to show the switching route table.
4.3.8 Configuring XOT
I. Introduction to XOT Protocol
XOT (X.25 Over TCP) is a protocol that is supported by TCP, and implements the
connection of two X.25 networks through IP network. The practical application
environment is shown in the following figure.
X.25 IP X.25
Quidway A Quidway B Quidway C Quidway D
Figure LLC-4-8 XOT typical application diagram
Since the application of IP network is broader and broader, the practical applications of
supporting X.25 data through IP net and connecting X.25 networks are becoming more
and more. The conventional X.25 protocol is the third layer of the OSI seven-layer
model, i.e., the network layer, for which the LAPB protocol provides reliable data
transmission link. Because TCP has the mechanism of error redirection and window
flow controlling to guarantee the reliability of links, it can be applied by X.25. XOT builds
a TCP tunnel connection between the two X.25 networks, and the X.25 packets are
supported by TCP as data of application layer, i.e., TCP serves as the link layer of
X.25. You can regard the middle QuidwayB, QuidwayC and IP net as a big X.25
switch , and data is directly switched from QuidwayA to QuidwayD through this
switch .
The XOT features implemented in VRP accords with RFC1613 recommendation, and it
possess the following features:
l Supporting SVC application. The two routers can dynamically set up a SVC by
sending call packet, and the VC will automatically be cleared when no data is
transmitted.
l Supporting PVC application. After the two routers configure a PVC, they directly
enter the data transmission status without the process of call establishing. If no
data is transmitted, this VC will not be cleared dynamically.
l Supporting the Keepalive attribute of TCP. If Keepalive is not configured, TCP
connection will not be cleared or be cleared after a long period of time when the
line is disconnected. If Keepalive is configured, TCP check the usability of the links
in time, and it will automatically clear the TCP connection if it does not receive the
answer of the opposite side for many times.
Implementing theory of XOT (taking SVC as an example):
As shown in the former figure, when it has data to transmit, QuidwayA first send a
request packet to set up a VC. After QuidwayB receive the call packet and know that it
is XOT application through judging, it first set up a TCP connection with QuidwayC, and
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-25
then stick the XOT packet header to X.25 call packet packet which is encapsulated in
TCP to send to QuidwayC. QuidwayC takes off the TCP and XOT packet headers and
send the call request packet to QuidwayD through X.25 local switch. After QuidwayD
receives the call request packet, it answers the call to confirm until the link is completely
set up and enters the data transmission status. To QuidwayA and QuidwayD, the whole
process of setting up and applying TCP connection is transparent, and they do not and
cannot care whether the data is forwarded through IP net or X.25 net.
II. Configuring XOT
1) XOT configuration task list
XOT configuration task list is as follows:
l Start X.25 switching
l Configure IP side interface
l Configure local switching (SVC)
l Configure XOT route
l Configure Keepalive and xot-source attributes (optional)
2) Start X.25 switching
Because the XOT is the extension of X.25 switch, first you have to start X.25 switch.
Perform the following tasks in global configuration mode.
Table LLC-4-33 Start X.25 switching
Operation Command
Start X.25 switching x25 routing
By default, do not start X.25 switch.
3) Configure IP side interface
Because the XOT implements the connection of two X.25 nets through IP net, first you
should ensure that the IP net is expedite. For the specific configuration, refer to
chapters of Network protocol configuration in this manual.
4) Configure local switching (SVC)
For SVC, when it receives the packets from the remote side, it must send out the
packets through local switch interface, so you have to configure local switching.
The following commands determine: In SVC, through which switch interface the
packets getting to local side will be sent out.
Perform the following tasks in global configuration mode.
Table LLC-4-34 Configure local switching
Operation Command
Configure X.25 local switching x25 route X.121-address interface serial interface-number
Delete X.25 local switching no x25 route X.121-address interface serial interface-number
5) Configure XOT route
The following configuration determines how the X.25 side packets received are
forwarded through IP net. There are different configuration modes for SVC and PVC.
For SVC, perform the following tasks in global configuration mode.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-26
Table LLC-4-35 Configure SVC XOT switching
Operation Command
Add a SVC XOT route x25 route dest-address xot ip-address
Delete a SVC XOT route no x25 route dest-address xot ip-address
& Note
The local X.25 route must be configured in the SVC mode.
For PVC, perform the following tasks in interface configuration mode.
Table LLC-4-36 Configure PVC XOT switching
Operation Command
Add a PVC XOT route x25 pvc vc number xot ip address interface type number
Delete a PVC XOT route no x25 pvc vc number
6) Configure Keepalive and xot-source attributes (optional)
After the TCP link is established, TCP will not be easily cleared even if the link is
disconnected. But after configuring Keepalive, the router will send checking packets in
time to check the usability of the link. If it cannot get confirmation after sending out
packets several times, it will consider the link failure and clear it automatically.
Table LLC-4-37 Configure Keepalive and xot-source attributes
Operation Command
Configure SVC Keepalive and xot-
source attributes
x25 route x.121 address xot ip address xot-keepalive-period period
xot-keepalive-tries times xot-source interface type number
Configure PVC Keepalive and xot-
source attributes
x25 pvc vc number xot ip address interface serial number xot-
keepalive-period period xot-keepalive-tries times xot-source interface
type number
III. Monitoring and Maintenance of XOT
In privileged user mode, the system provides XOT debugging commands to show the
establishment of TCP and the status of X25 VC.
Table LLC-4-38 Monitoring and Maintenance of XOT
Operation Command
Show the establishment of TCP show tcp brief
Show the status of X25 VC show x25 vc
Enable X25 information debugging
(transceiving packets, timer, event,
limited state machine)
debug x25 xot
1) Check X.25 VC table
The command show x25 vc is used to show all the virtual circuits in effect on all the
X.25 interfaces.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-27
Quidway# show x25 vc
SVC 1024, State: TRANSFER, Interface: Serial11/0/2
Started: 2001-9-30 13:48:29, Last input: 0:0:18, Last output: 0:0:18
Connects: X.121 <--> ietf
10.1.1.2 vc 1024 cud pid, no Tx data PID
Window size: input 2 output 2
Packet Size: input 128 output 128
PS: 0 PR: 0 ACK: 0 Remote PR: 0 RCNT: 0
RNR: FALSE Reset times: 0
input/output: DATA 5/5 INTERRUPT 0/0 Bytes 420/420
RR 0/0 RNR 0/0 REJs 0/0
Snd Queue: Current length 0 Max length 500 Drops 0
Rcv Queue: Current length 0 Max length 500 Drops 0
SVC 1024, State: TRANSFER, Interface: 10.1.1.2
Started: 2001-9-30 13:48:29, Last input: 0:0:18, Last output: 0:0:18
Connects: X.121 <--> ietf
Serial11/0/2 vc 1024 cud pid, no Tx data PID
Window size: input 2 output 2
Packet Size: input 128 output 128
PS: 0 PR: 0 ACK: 0 Remote PR: 0 RCNT: 0
RNR: FALSE Reset times: 0
input/output: DATA 5/5 INTERRUPT 0/0 Bytes 420/420
RR 0/0 RNR 0/0 REJs 0/0
Snd Queue: Current length 0 Max length 500 Drops 0
Rcv Queue: Current length 0 Max length 500 Drops 0
The upper information indicates: On X.25 interface Serial11/0/2, there is a temporary
VC in effect with the serial number 1024.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-28
Table LLC-4-39 Information about X.25 virtual circuit
Field Meaning
SVC 1
The type and number of the virtual circuit. SVC stands for the switched virtual circuit, and
PVC for the permanent virtual circuit
State Current state of the virtual circuit
Interface Name of the interface on which the virtual circuit is established
Started Time elapsed since the VC was created. Format: : year-month-day hour: minute: second
Last input
Time of last input (when the show x25 vc is executed) on the virtual circuit. Format: hour:
minute: second
Last output
Shows time of the last output (when the show x25 vc is executed) on the virtual circuit.
Format: hour: minute: second
Connects
If the router is the start / end point (that is, the router does not work in X.25 switched
mode), this field indicates the address map attached to this virtual circuit. If the virtual
circuit is set up for switching (that is, the router works in switched mode), this field
describes the type and number of the VC on another X.25 interface attached to this VC.
For example, Serial1 SVC 1024 indicates that this VC is attached to SVC1024 on the
X.25 interface Serial1
Window size The incoming window size and outgoing window size of this VC
Packet size The maximum packet size of this VC
Vs Variable currently sent on this VC
Vr Variable current received on this VC
ACK Current acknowledgement variable on this VC
Remote Vr Last acknowledgement from the far end on this VC
RCNT Count of unacknowledged output packets
RNR
If this VC is in the Receiver Not Ready status. TRUE indicate that it is in this status, and
FALSE indicates that it is not in this status
Reset times Number of VC reset times
input/output:
DATA...REJ 0/0
Statistics about this VC, including the input and output packets, and the total bytes of all
the data packets
Snd Queue
Current status of the output queue of this VC: maximum hold size, current queue length,
and packets dropped due to a full queue
Rcv Queue
Current status of the input queue of this VC: maximum hold size, current queue length,
and packets dropped due to a full queue
2) In privileged user mode, the command show tcp brief is used to show the
establishment of TCP.
Quidway# show tcp brief
LocalAddress LocalPort ForeignAddress ForeignPort State
010.001.001.002 1998 010.001.001.001 1034 ESTABLISHED
000.000.000.000 23 000.000.000.000 0 LISTEN
000.000.000.000 1998 000.000.000.000 0 LISTEN
The upper information indicates: local 10.1.1.2 and the opposite 10.1.1.1 establish TCP
connection. This side uses port 1998 and the opposite side uses port 1034.
4.4 Monitoring and Maintenance of LAPB, X.25 and X.25
Switching
In the privileged mode, perform the following tasks to enable real-time monitoring of the
current status of LAPB, X.25 and X.25 switching.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-29
Table LLC-4-40 Maintenance and monitoring of LAPB, X.25 and X.25 switching
Operation Command
Show interface information show interface [ type number ]
Show X.25 alias table show x25 alias
Show X.25 address mapping table show x25 map
Show X.25 switching route table show x25 route
Show X.25 switching virtual circuit table show x25 switch-vc-table
Show X.25 virtual circuit show x25 vc lci-number
Enable X.25 information debugging debug x25 all [interface interface-type interface-number ]
Disable X.25 information debugging no debug x25 all [interface interface-type interface-number ]
Enable X.25 event debugging debug x25 event [interface interface-type interface-number ]
Disable X.25 event debugging no debug x25 event [interface interface-type interface-number ]
Enable X.25 packet debugging debug x25 packet [interface interface-type interface-number ]
Disable X.25 packet debugging no debug x25 packet [interface interface-type interface-number ]
4.4.1 Displaying the Information of Interface Encapsulated LAPB
The following tasks can encapsulate interface Serial0 as LAPB protocol, and display
interface information after encapsulation:
Quidway# configure
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# encapsulation lapb
Quidway(config-if-Serial0)# show interface serial 0
Serial0 is down, line protocol is down
physical layer is synchronous, baudrate is 64000 bps
interface is DCE, clock is DCECLK, no cable
Encapsulation LAPB
LAPB DTE, module 8, k 7, N1 12032, N2 5
timer: T1 2000, T2 1000, T3 0 (milliseconds)
state DISCONNECT, VS 0, VR 0, Remote VR 0
IFRAME 0/0, RR 0/0, RNR 0/0, REJ 0/0
FRMR 0/0, SABM 0/0, DM 0/0, UA 0/0
DISC 0/0, Invalid Ns 0, Invalid Nr 0, Link Resets 0
0 packets input, 0 bytes, 0 no buffers
0 packets output, 0 bytes, 0 no buffers
0 input errors, 0 CRC, 0 frame errors
0 overrunners, 0 aborted sequences, 0 input no buffers
After inputting the command serial, the above information will display. The parts in bold
are related to the LAPB protocol, and the meaning of each field is as follows.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-30
Table LLC-4-41 LAPB information shown by show interface command
Field Meaning
Encapsulation LAPB Current encapsulation protocol of this interface is LAPB protocol
LAPB DTE LAPB of this interface works in DTE mode
module 8
Information frame and monitoring frame sent by this interface LAPB are
numbered in the modulo 8 mode
k 7 Window size of this interface LAPB is 7
N1 12032 The maximum length of frame sent by the interface LAPB is 12032 bits
N2 5 Maximum re-sending times of information frame of this interface LAPB is 5
timer: Delay value of timers of this interface LAPB, in unit of millisecond
state Current status of this interface LAPB
VS Sending variable of this interface LAPB
VR Receiving variable of this interface LAPB
Remote VR
Peer s last acknowledgment on information frame received by this interface
LAPB
IFRAME 0/0 ... DISC 0/0
Statistics information of frames sent and received by this interface LAPB,
format: received quantity/sent quantity
Invalid Ns
Error statistics of this interface LAPB: total of received information frames
carrying erroneous sequence numbers
Invalid Nr
Error statistics of this interface LAPB: total of received information frames
and monitoring frames carrying erroneous acknowledgment numbers
Link Resets Restarting times of this interface LAPB link
4.4.2 Displaying the Information of Interface Encapsulated X.25
The following command series encapsulates interface Serial1 with X.25 protocol, and
exits to the privileged user mode to show the interface information after encapsulation:
Quidway# configure
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# encapsulation x25
Quidway(config-if-Serial1)# exit
Quidway(config)# exit
Quidway# show interface serial 1
Serial1 is down, line protocol is down
physical layer is synchronous, baudrate is 9600 bps
interface is DCE, clock is DCECLK, no cable
Encapsulation X.25 DTE IETF, address is , state Ready, modulo 8
input/output: window sizes 2/2, packet sizes 128/128
Channels: Incoming-only 0-0, Two-way 1-1024, Outgoing-only 0-0
Timers: T20 180, T21 200, T22 180, T23 180, T28 300, Idle_Timer 0
New configuration (will be effective after restart): modulo 8
input/output: window sizes 2/2, packet sizes 128/128
Channels: Incoming-only 0-0, Two-way 1-1024, Outgoing-only 0-0
Statistic: Restarts 0 (Restart Collisions 0)
Refused Incoming Call 0, Failing Outgoing Call 0
input/output: RESTART 0/0 CALL 0/0 DIAGNOSE 0/0
DATA 0/0 INTERRUPT 0/0 Bytes 0/0
RR 0/0 RNR 0/0 REJ 0/0
Invalid Pr: 0 Invalid Ps: 0 Unknown: 0
LAPB DTE, module 8, k 7, N1 2104, N2 5
timer: T1 2000, T2 1000, T3 0 (milliseconds)
state DISCONNECT, VS 0, VR 0, Remote VR 0
IFRAME 0/0, RR 0/0, RNR 0/0, REJ 0/0
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-31
FRMR 0/0, SABM 0/0, DM 0/0, UA 0/0
DISC 0/0, invalid ns 0, invalid nr 0, link resets 0
5 minutes input rate 0.00 bytes/sec,0.00 packets/sec
5 minutes output rate 0.00 bytes/sec,0.00 packets/sec
Input queue:(size/max/drops)
0/1000/0
Queueing strategy:FIFO
Output queue:(size/max/drops
0/1000/0
0 packets input, 0 bytes, 0 no buffers
0 packets output, 0 bytes, 0 no buffers
0 input errors, 0 CRC, 0 frame errors
0 overrunners, 0 aborted sequences, 0 input no buffers
DCD=UP DTR=DOWN DSR=UP RTS=DOWN CTS=UP
After inputting the command serial, the above information will be displayed. The bold
parts are related to LAPB and X.25 protocol. LAPB has already been introduced in the
previous section. For meanings of various fields related to X.25 protocol, refer to the
following table.
Table LLC-4-42 X.25 information shown by show interface command
Field Meaning
Encapsulation X.25 DTE IETF
Current encapsulation protocol of this interface is X.25 protocol. X.25 works in
DTE mode, and the data packet encapsulation format is IETF
address is
X.121 address of this X.25 interface; this field will be empty if there is no
address
state Current status of this X.25 interface
modulo
Data packets and flow control packets sent by this X.25 interface are
numbered in modulo 8 mode
input/output : window sizes ...
Flow control parameters of this X.25 interface, including receiving window
size, sending window size, maximum received packet length (in bytes), and
maximum sent packet length (in bytes)
Channels :
Channel range division of this X.25 interface, sequentially as incoming-only
channel section, two-way channel section, outgoing-only channel section; if
both demarcating values of an section are 0, this section is disabled
Timers : Delay values of various timers of this X.25 interface, in unit of second
New Configuration
New configuration of this X.25 interface taking effect after next restart; if this
configuration is wrong, the default value will be restored
Restarts 0 ( Restart Collision 0)
Statistics information of this X.25 interface: times of restart (including restart
collision)
Refused Incoming Call Statistics information of this X.25 interface: times of call refusals
Failing Outgoing Call Statistics information of this X.25 interface: times of call failures
input/output : RESTART 0/0 ...
REJ 0/0
Statistics information of this X.25 interface: quantities of received and sent
packets, format: received quantity/sent quantity
Invalid Ps
Error statistics information of this X.25 interface: total of received data packets
carrying erroneous sequence numbers
Invalid Pr
Error statistics information of this X.25 interface: total of received data packets
and flow control packets carrying erroneous acknowledgement numbers
Unknown
Error statistics information of this X.25 interface: total of received non-
analyzable packets
4.4.3 Displaying X.25 Alias Table
Perform the following task to display all aliases of all X.25 interfaces:
Quidway# show x25 alias
Alias for Serial0:
Alias for Serial1:
Alias- 1: $20112405$ strict
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-32
Alias- 2: $20112450 left
Alias- 3: 20112450$ right
The information shown above indicates: X.25 interface Serial0 is not set with an alias;
X.25 interface Serial1 is set with 3 aliases: $20112405$ (matching mode is strict
matching), $20112405 (matching mode is left-justified matching), and 20112405$
(matching mode is right-justified matching).
4.4.4 Displaying X.25 Address Mapping Table
Perform the following task to display all address mappings of all X.25 interfaces:
Quidway# show x25 map
Serial0: X.121 20112450 <--> ip 202.38.165.19 SVC_MAP
No VC attached
Facility:
ACCEPT_REVERSE;
BROADCAST;
PACKET_SIZE: I 512 O 512;
Serial1: X.121 20112451 <--> ip 202.38.166.20 PVC_MAP
1 VC: 3*
Facility:
BROADCAST;
WINDOW_SIZE: I 5 O 5
The table below describes the detailed meanings of various fields of the above address
mapping information:
Table LLC-4-43 X.25 address mapping information
Field Meaning
Serial0 Name of the X.25 interface in which this address mapping is located
X.121 20112451 Destination X.121 address of this address mapping
ip 202.38.165.19 Destination protocol type and protocol address of this address mapping
SVC_MAP
Type of this address mapping, SVC_MAP means temporary virtual circuit address
mapping, PVC_MAP means permanent virtual circuit address mapping
1 VC: 3*
There is one virtual circuit associated with this address mapping, numbered 3; if no virtual
circuit is associated with this address mapping, this field will be "No VC attached"
Facility
Option of this address mapping, for example, "Broadcast" indicates to "permit to
broadcast through this address mapping"
4.4.5 Displaying X.25 Switching Route Table
Quidway(config)# Show X25 route
Number X.121 CUD FowardTo
# 1 1 Serial0
# 2 2 Serial1
The information above means that the call with a destination X.121 address of 1 will be
switched to interface Serial0 for output; and the call with a destination X.121 address of
2 will be switched to interface Serial1 for output.
4.4.6 Displaying X.25 Virtual Circuit Table
Perform the following task to display all the current virtual circuits of all X.25 interfaces:
Quidway# show x25 vc
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-33
SVC 1, State: TRANSFER, Interface: Serial0
Started: 1998-1-1 1:48:11, Last input: 0:45:57, Last output: 0:45:59
Connects: X.121 20112450 <--> ip 202.38.165.19
Window size: input 5 output 5
Packet Size: input 128 output 128
PS: 0 PR: 0 ACK: 0 Remote PR: 0 RCNT: 0
RNR: FALSE Reset times: 0
input/output: DATA 1154/1022 INTERRUPT 0/0 Bytes 1569732/1435638
RR 143/165 RNR 0/0 REJ 0/0
Snd Queue: Current length 0 Max length 50 Drops 0
Rcv Queue: Current length 0 Max length 50 Drops 0
PVC 3, State: TRANSFER, Interface: Serial1
Started: 1998-1-1 1:48:11, Last input: 0:30:09, Last output: 0:30:17
Connects: X.121 20112451 <--> ip 202.38.166.20
Window size: input 5 output 5
Packet Size: input 128 output 128
PS: 0 PR: 0 ACK: 0 Remote PR: 0 RCNT: 0
RNR: FALSE Reset times: 0
input/output:DATA 0/0 INTERRUPT 0/0 Bytes 0/0
RR 0/0 RNR 0/0 REJ 0/0
Snd Queue: Current length 0 Max length 50 Drops 0
Rcv Queue: Current length 0 Max length 50 Drops 0
The information above indicates that on the X.25 interface Serial0, there is one
temporary virtual circuit numbered 1; on the X.25 interface Serial1, there is one
permanent virtual circuit numbered 3. The following table shows the detailed meaning
of each field of the above information.
Table LLC-4-44 X.25 virtual circuit information
Field Meaning
SVC 1
Type and number of this virtual circuit; SVC means temporary virtual circuit, and PVC
means permanent virtual circuit
State Current status of this virtual circuit
Interface Name of interface where this virtual circuit is located
Started Time when this virtual circuit is set up, format: year-month-day h: m: s
Last input
Time interval from last receipt of data packet on this virtual circuit till now (executing the
show x25 vc command), format: hh:mm:ss
Last output
Time interval from last sending of data packet on this virtual circuit till now (executing the
show x25 vc command), format: hh:mm:ss
Connects
If the router is the start or end point for a data transmission (i.e., the router does not work in
X.25 switching mode), this field refers to the address mapping associated with this virtual
circuit. If this virtual circuit is set up for switching (i.e., the router works in the switching
mode), this field indicates the type and number of virtual circuit on another X.25 interface
associated with this virtual circuit. For example, "Serial1 SVC 1024" indicates this virtual
circuit is associated with the temporary virtual circuit 1024 on the X.25 interface Serial1
Window size Receiving window size and sending window size of this virtual circuit
Packet size Maximum lengths of receiving packet and sending packet of this virtual circuit
Vs Current sending variable of this virtual circuit
Vr Current receiving variable of this virtual circuit
ACK Current acknowledgement variable of this virtual circuit
Remote Vr Last acknowledgment received from the peer by this virtual circuit
RCNT Quantity of data packets sent by this virtual circuit but not yet acknowledged by the peer
RNR
Whether this virtual circuit currently is in the status "receiving not ready"; TRUE means it is
in this status, while FALSE means not
Reset times Times of resetting of this virtual circuit
input/output:
DATA ... REJ 0/0
Statistics information of this virtual circuit, including quantities of received and sent packets
and total bytes of all data packets
Snd Queue
Current status of the sending queue of this virtual circuit: maximum holding length, current
queue length, quantity of data packets lost due to full queue
Rcv Queue
Current status of the receiving queue of this virtual circuit: maximum holding length, current
queue length, quantity of data packets lost due to full queue
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-34
4.5 Typical LAPB Configuration Example
I. Networking requirement
Two routers are directly connected via serial ports with LABP protocol encapsulated to
transmit IP data packets directly.
II. Networking diagram
V.35 cable
Serial 0 Serial 1
Router Router
Figure LLC-4-9 Direct connection between two routers via serial ports
III. Configuration procedure
As shown in the diagram above, perform the following configuration tasks:
l Configure Router A:
! Select interface
Quidway# configure
Quidway(config)# interface serial 0
! Specify IP address for this interface
Quidway(config-if-Serial0)# ip address 202.38.160.1 255.255.255.0
! Encapsulate this interface as LAPB interface and specify its working mode as DTE
Quidway(config-if-Serial0)# encapsulation lapb dte
! Configure other Lapb parameters (if the link is of good quality, and a higher rate is
required, the flow control parameter modulo can be increased to 128, k to 127, but they
must be the same for both ends in the direct connection)
Quidway(config-if-Serial0)# lapb module 128
Quidway(config-if-Serial0)# lapb k 127
l Configure Router B:
! Select interface
Quidway# configure
Quidway(config)# interface serial 1
! Specify IP address for this interface
Quidway(config-if-Serial1)# ip address 202.38.160.2 255.255.255.0
! Encapsulate this interface as LAPB interface and specify its working mode as DCE
Quidway(config-if-Serial1)# encapsulation lapb dce
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-35
! Configure other LAPB parameters (if the link quality is good, and a higher rate is
required, the flow control parameter modulo can be increased to 128, k to 127, but they
must be the same for both ends in the direct connection)
Quidway(config-if-Serial1)# lapb modulo 128
Quidway(config-if-Serial1)# lapb k 127
4.6 Typical X.25 Configuration Example
This section describes some typical X.25 configuration examples.
4.6.1 Back to Back Direct Connection of Two Routers via Serial Ports
I. Networking requirement
As shown in the diagram below, if two routers are to be directly connected back to back,
the X.25 protocol is encapsulated between the serial ports for IP data packet
transmission, configure the two routers as follows.
II. Networking diagram
V.24/V.35 cable
Router
Serial 1 Serial 0
Router
Figure LLC-4-10 Direct connection of two routers via serial ports
III. Configuration procedure
l Configure Router A:
! Select interface
Quidway# configure
Quidway(config)# interface serial 0
! Specify IP address for this interface
Quidway(config-if-Serial0)# ip address 202.38.160.1 255.255.255.0
! Encapsulate this interface as X.25 interface and specify its working mode as DTE
Quidway(config-if-Serial0)# encapsulation x25 dte
! Specify X.121 address of this interface
Quidway(config-if-Serial0)# x25 address 20112451
! Specify address mapping to the peer
Quidway(config-if-Serial0)# x25 map ip 202.38.160.2 20112452
! As this is a direct connection, the flow control parameters can be increased slightly
Quidway(config-if-Serial0)# x25 ips 1024
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-36
Quidway(config-if-Serial0)# x25 ops 1024
Quidway(config-if-Serial0)# x25 win 5
Quidway(config-if-Serial0)# x25 wout 5
l Configure Router B:
! Select interface
Quidway# configure
Quidway(config)# interface serial 1
! Specify IP address for this interface
Quidway(config-if-Serial1)# ip address 202.38.160.2 255.255.255.0
! Encapsulate this interface as X.25 interface and specify its working mode as DCE
Quidway(config-if-Serial1)# encapsulation x25 dce
! Specify X.121 address of this interface
Quidway(config-if-Serial1)# x25 address 20112452
! Specify address mapping to the peer
Quidway(config-if-Serial1)# x25 map ip 202.38.160.1 20112451
! As this is a direct connection, the flow control parameters can be increased slightly
Quidway(config-if-Serial1)# x25 ips 1024
Quidway(config-if-Serial1)# x25 ops 1024
Quidway(config-if-Serial1)# x25 win 5
Quidway(config-if-Serial1)# x25 wout 5
4.6.2 Connecting the Router to X.25 Public Packet Network
I. Networking requirement
As shown in the diagram below, three routers A, B and C are connected to the same
X.25 network for mutual communication. The requirements are:
l IP addresses of the interfaces Serial0 of three routers are 168.173.24.1,
168.173.24.2 and 168.173.24.3 respectively.
l X.121 addresses assigned to the three routers by the network are 30561001,
30561002 and 30561003 respectively.
l Standard window size supported by the packet network: both receiving window
and sending window are 5.
l Standard maximum packet length: both maximum receiving packet length and
maximum sending packet length are 512.
l Channel range: permanent virtual circuit section, incoming-only channel section
and outgoing-only channel section are disabled, two-way channel section is [1,
31].
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-37
II. Networking diagram
RouterA
RouterB
RouterC
Serial0
Serial0
Serial0
IP: 168.173.24.1
X.121: 30561001
IP: 168.173.24.2
X.121: 30561002
X.25
windowsize: 5 5
packetsize: 512 512
Figure LLC-4-11 Connect the router to X.25 public packet network
III. Configuration procedure
l Configure Router A:
! Configure interface IP address
Quidway# configure
Quidway(config)# interface Serial 0
Quidway(config-if-Serial0)# ip address 168.173.24.1 255.255.255.0
! Connect to public packet network, make the router as DTE side
Quidway(config-if-Serial0)# encapsulation x25 dte
Quidway(config-if-Serial0)# x25 address 30561001
Quidway(config-if-Serial0)# x25 win 5
Quidway(config-if-Serial0)# x25 wout 5
Quidway(config-if-Serial0)# x25 ips 512
Quidway(config-if-Serial0)# x25 ops 512
Quidway(config-if-Serial0)# x25 htc 32
Quidway(config-if-Serial0)# x25 map ip 168.173.24.2 30561002
Quidway(config-if-Serial0)# x25 map ip 168.173.24.3 30561003
l Configure Router B:
! Configure interface IP address
Quidway# configure
Quidway(config)# interface Serial 0
Quidway(config-if-Serial0)# ip address 168.173.24.2 255.255.255.0
! Connect to public packet network, make the router as DTE side
Quidway(config-if-Serial0)# encapsulation x25 dte
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-38
Quidway(config-if-Serial0)# x25 address 30561002
Quidway(config-if-Serial0)# x25 win 5
Quidway(config-if-Serial0)# x25 wout 5
Quidway(config-if-Serial0)# x25 ips 512
Quidway(config-if-Serial0)# x25 ops 512
Quidway(config-if-Serial0)# x25 htc 32
Quidway(config-if-Serial0)# x25 map ip 168.173.24.1 30561001
Quidway(config-if-Serial0)# x25 map ip 168.173.24.3 30561003
l Configure Router C:
! Configure interface IP address
Quidway# configure
Quidway(config)# interface Serial 0
Quidway(config-if-Serial0)# ip address 168.173.24.3 255.255.255.0
! Connect to public packet network, make the router as DTE side
Quidway(config-if-Serial0)# encapsulation x25 dte
Quidway(config-if-Serial0)# x25 address 30561003
Quidway(config-if-Serial0)# x25 win 5
Quidway(config-if-Serial0)# x25 wout 5
Quidway(config-if-Serial0)# x25 ips 512
Quidway(config-if-Serial0)# x25 ops 512
Quidway(config-if-Serial0)# x25 htc 32
Quidway(config-if-Serial0)# x25 map ip 168.173.24.1 30561001
Quidway(config-if-Serial0)# x25 map ip 168.173.24.2 30561002
4.6.3 Configuring Virtual Circuit Range
I. Networking requirement
The router's interface Serial0 is encapsulated into X.25 protocol, with the virtual circuit
range: permanent virtual circuit section [1, 8], incoming-only channel section [9, 16],
two-way channel section [17, 1024], and the outgoing-only channel section is disabled.
II. Configuration procedure
Quidway# configure
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# encapsulation x25
Quidway(config-if-Serial0)# x25 lic 9
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-39
Quidway(config-if-Serial0)# x25 hic 16
Quidway(config-if-Serial0)# x25 ltc 17
4.6.4 Transmitting IP Datagram via X.25 PVC
I. Networking requirement
In the following diagram, the permanent virtual circuit section allowed by the packet
network is [1,8], the PVC numbers assigned to Router A and Router B are 3 and 4
respectively. The IP network addresses of Ethernets A and B are 202.38.165.0 and
196.25.231.0 respectively. It is required to exchange routing information between
Ethernets A and B with RIP routing protocol, so that PC A and PC B can exchange
information without adding static route.
II. Networking diagram
X.25
windowsize: 5 5
packetsize: 512 512
RouterA RouterB
IP: 192.149.13.1
X.121: 1004358901
IP: 192.149.13.2
X.121: 1004358902
PVC 3 PVC 4
EtherNet A
EtherNet B
PC B PC A
Serial 0 Serial 0
Figure LLC-4-12 X.25 PVC bearing IP data packet
III. Configuration procedure
l Configure Router A:
Quidway# configure
Quidway(config)# interface ethernet 0
Quidway(config-if-Ethernet0)# ip address 202.38.165.1 255.255.255.0
Quidway(config-if-Ethernet0)# interface serial 0
Quidway(config-if-Serial0)# ip address 192.149.13.1 255.255.255.0
Quidway(config-if-Serial0)# encapsulation x25
Quidway(config-if-Serial0)# x25 address 1004358901
Quidway(config-if-Serial0)# x25 ltc 9
Quidway(config-if-Serial0)# x25 pvc 3 ip 192.149.13.2 1004358902 broadcast
packetsize 512 512 windowsize 5 5
Quidway(config-if-Serial0)# exit
Quidway(config)# router rip
l Configure Router B:
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-40
Quidway# configure
Quidway(config)# interface ethernet 0
Quidway(config-if-Ethernet0)# ip address 196.25.231.1 255.255.255.0
Quidway(config-if-Ethernet0)# interface serial 0
Quidway(config-if-Serial0)# ip address 192.149.13.2 255.255.255.0
Quidway(config-if-Serial0)# encapsulation x25
Quidway(config-if-Serial0)# x25 address 1004358902
Quidway(config-if-Serial0)# x25 ltc 9
Quidway(config-if-Serial0)# x25 pvc 4 ip 192.149.13.1 1004358901 broadcast
packetsize 512 512 windowsize 5 5
Quidway(config-if-Serial0)# exit
Quidway(config)# router rip
In above configuration, the permanent virtual circuit numbers of routers A and B are
different: 3 and 4 respectively. Virtual circuit refers to the end-to-end logic link between
the calling DTE and the called DTE, while logic channel refers to the logic link between
two directly connected devices (either between DTE and DCE, or between the ports of
two packet switching exchanges). A virtual circuit consists of several logic channels,
and each logic channel has a separate number. The virtual circuit between routers A
and B is shown in Figure 4-12 (suppose this virtual circuit passes four packet switching
exchanges in the network).
RouterA
RouterB
PBX
PBX
PBX
LC 3
LC 4
LC 243
LC 24
LC 3
PBX
Figure LLC-4-13 A virtual circuit consisting of several logic channels
Therefore, the PVC 3 and PVC 4 mentioned above actually refer to the numbers of the
logic channels between the router and the switch directly connected to it. However, on
one side of this virtual circuit, the logic channel number can be used to identify this
virtual circuit without causing misunderstanding. This is why no strict distinction is
made between "virtual circuit" and "logic channel".
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-41
4.6.5 Typical X.25 Sub-Interface Configuration Example
I. Networking requirement
Multiple sub-interfaces are configured on a physical interface to connect with multiple
peers of different network sections. In the following diagram, Router A is configured
with two sub-interfaces, respectively interconnected with Router B and Router C.
II. Networking diagram
S0
S0
S0
S0
S2
RouterB RouterC
RouterD
RouterA
S1
Figure LLC-4-14 Diagram of X.25 sub-interface configuration
III. Configuration procedure
l Configure Router A:
Quidway# configure
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# encapsulation x25 dte
Quidway(config-if-Serial0)# x25 address 100
Quidway(config-if-Serial0)# interface serial 0.1
! Create sub-interface serial 0.1
Quidway(config-if-Serial0.1)# ip address 10.1.1.2 255.255.0.0
Quidway(config-if-Serial0.1)# x25 map ip 10.1.1.1 200
! Create sub-interface serial 0.2
Quidway(config-if-Serial0.1)# interface serial 0.2
Quidway(config-if-Serial0.2)# ip address 20.1.1.2 255.255.0.0
Quidway(config-if-Serial0.2)# x25 map ip 20.1.1.1 300
l Configure Router B:
Quidway# configure
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# encapsulation x25 dte
Quidway(config-if-Serial0)# x25 address 200
Quidway(config-if-Serial0)# x25 map ip 10.1.1.2 100
l Configure Router C:
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-42
Quidway# configure
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# encapsulation x25 dte
Quidway(config-if-Serial0)# x25 address 300
Quidway(config-if-Serial0)# x25 map ip 20.1.1.2 100
l Configure Router D:
Quidway# configure
Quidway(config)# interface serial 0
Quidway(config-if-Serial0)# encapsulation x25 dce
Quidway(config-if-Serial0)# interface serial 1
Quidway(config-if-Serial1)# encapsulation x25 dce
Quidway(config-if-Serial1)# interface serial 2
Quidway(config-if-Serial2)# encapsulation x25 dce
Quidway(config-if-Serial2)# exit
Quidway(config)# x25 routing
Quidway(config)# x25 route 100 interface serial 0
Quidway(config)# x25 route 200 interface serial 1
Quidway(config)# x25 route 300 interface serial 2
4.6.6 SVC Application of XOT
I. Networking requirement
Router B and C connect through Ethernet interface, and build TCP connection between
them. X.25 packets forward through TCP, and configure SVC to implement the SVC
function.
II. Networking diagram
PC1
S0
S0
S0
S0
E0
E0
PC2
E0 E0
Router B
Router A
Router C
Router D
Figure LLC-4-15 SVC application networking diagram of XOT
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-43
III. Configuration procedure
l Configure Quidway A router
! Basic X.25 Configuration
QuidwayA# config
QuidwayA(config)# interface serial 0
QuidwayA(config-if-Serial0)# encapsulation x25 dte ietf
QuidwayA(config-if-Serial0)# x25 address 1
QuidwayA(config-if-Serial0)# x25 map ip 1.1.1.2 2
QuidwayA(config-if-Serial0)# ip address 1.1.1.1 255.0.0.0
l Configure Quidway D router
! Basic X.25 Configuration
QuidwayD# config
QuidwayD(config)# interface serial 0
QuidwayD(config-if-Serial0)# encapsulation x25 dte ietf
QuidwayD(config-if-Serial0)# x25 address 2
QuidwayD(config-if-Serial0)# x25 map ip 1.1.1.1 1
QuidwayD(config-if-Serial0)# ip address 1.1.1.2 255.0.0.0
l Configure Quidway B router
! Start X.25 switching
QuidwayB# config
QuidwayB(config)# x25 routing
! Configure X.25 local switching
QuidwayB(config)# x25 route 1 interface serial 0
! Configure XOT switching
QuidwayB(config)# x25 route 2 xot 10.1.1.2
! Configure ethernet 0.
QuidwayB(config)# interface ethernet 0
QuidwayB(config-if-Ethernet0)# ip address 10.1.1.1 255.0.0.0
! Configure Serial 0
QuidwayB(config)# interface serial 0
QuidwayB(config-if-Serial0)# encapsulation x25 dce ietf
l Configure Quidway C router
! Start X.25 switching
QuidwayC# config
QuidwayC(config)# x25 routing
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-44
! Configure X.25 local switching
QuidwayC(config)# x25 route 2 interface serial 0
! Configure XOT switching
QuidwayC(config)# x25 route 1 xot 10.1.1.1
! Configure Ethernet 0
QuidwayC(config)# interface ethernet 0
QuidwayC(config-if-Ethernet0)# ip address 10.1.1.2 255.0.0.0
! Configure Serial 0
QuidwayC(config)# interface serial 0
QuidwayC(config-if-Serial 0)# encapsulation x25 dce ietf
4.6.7 PVC Application of XOT
I. Networking requirement
Router B and C connect through Ethernet interface, and build TCP connection between
them. X.25 packets forward through TCP, and configure PVC to implement the PVC
function.
II. Networking diagram
PC1
S0
S0
S0
S0
E0
E0
PC2
E0
E0
Router B
Router A Router D
Router C
Figure LLC-4-16 PVC application networking diagram of XOT
III.Configuration procedure
l Configure Quidway A router
! Basic X.25 Configuration
QuidwayA# config
QuidwayA(config)# interface serial 0
QuidwayA(config-if-Serial0)# encapsulation x25 dte ietf
QuidwayA(config-if-Serial0)# x25 address 1
QuidwayA(config-if-Serial0)# x25 lic 10
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-45
QuidwayA(config-if-Serial0)# x25 hic 20
QuidwayA(config-if-Serial0)# x25 ltc 30
QuidwayA(config-if-Serial0)# x25 pvc 1 ip 1.1.1.2 2
QuidwayA(config-if-Serial0)# ip address 1.1.1.1 255.0.0.0
l Configure Quidway RouterD
! Basic X.25 configuration
QuidwayD# config
QuidwayD(config)# interface serial 0
QuidwayD(config-if-Serial0)# encapsulation x25 dte ietf
QuidwayD(config-if-Serial0)# x25 address 2
QuidwayD(config-if-Serial0)# x25 lic 10
QuidwayD(config-if-Serial0)# x25 hic 20
QuidwayD(config-if-Serial0)# x25 ltc 30
QuidwayD(config-if-Serial0)# x25 pvc 1 ip 1.1.1.1 1
QuidwayD(config-if-Serial0)# ip address 1.1.1.2 255.0.0.0
l Configure Quidway B router
! Start X.25 switching
QuidwayB# config
QuidwayB(config)# x25 routing
! Configure Ethernet 0.
QuidwayB(config)# interface ethernet 0
QuidwayB(config-if-Ethernet 0)# ip address 10.1.1.1 255.0.0.0
! Configure Serial 0.
QuidwayB(config)# interface serial 0
QuidwayB(config-if-Serial0)# encapsulation x25 dce ietf
QuidwayB(config-if-Serial0)# x25 lic 10
QuidwayB(config-if-Serial0)# x25 hic 20
QuidwayB(config-if-Serial0)# x25 ltc 30
QuidwayB(config-if-Serial0)# x25 pvc 1 xot 10.1.1.2 interface serial 0 pvc 1
l Configure Quidway C router
! Start X.25 switching
QuidwayC# config
QuidwayC(config)# x25 routing
! Configure Ethernet 0.
QuidwayC(config)# interface ethernet 0
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-46
QuidwayC(config-if-Ethernet 0)# ip address 10.1.1.2 255.0.0.0
! Configure Serial 0.
QuidwayC(config)# interface serial 0
QuidwayC(config-if-Serial 0)# en x25 DCE IETF
QuidwayC(config-if-Serial 0)# x25 lic 10
QuidwayC(config-if-Serial 0)# x25 hic 20
QuidwayC(config-if-Serial 0)# x25 ltc 30
QuidwayC(config-if-Serial 0)# x25 pvc 1 xot 10.1.1.1 interface serial 0 pvc 1
4.7 Fault Diagnosis and Troubleshooting of LAPB
Fault 1: Two connected sides are encapsulated with X.25 (or directly encapsulated with
LAPB), but the protocol is always disconnected. Turn on the debugging switch, it is
found that one end sends SABM frame, while the other end sends FRMR frame
circularly.
Troubleshooting: this is because both sides are encapsulated in the same working
mode (DTE or DCE). Change the working mode of one side to solve the problem.
Fault 2: Two connected sides are encapsulated with X.25, and the protocol is already in
UP status, but cannot ping through the peer. Turn on the debugging switch and it is
found that the received frames are discarded on one end instead of being forwarded up
to the packet layer.
Troubleshooting: The maximum frame bits of this end may be too small. Change the
configuration.
4.8 Fault Diagnosis and Troubleshooting of X.25
This section describes some common faults and the troubleshooting methods.
Assuming that the connection of the X.25 layer 2 (LAPB) is completely correct.
Fault 1: LAPB is already in "Connect" status, but the X.25 protocol can not enter "UP"
status.
Troubleshooting: It is possible that the local working mode has been configured wrong,
for example, both sides of a connection are DTE or DCE. Try again after changing the
encapsulation working mode.
Fault 2: X.25 protocol is "UP", but virtual circuit can not be established, i.e., unable to
ping through.
This may be caused by one of the following:
l Local X.121 address not configured
l Address mapping to the peer not configured
l Opposite X.121 address not configured
l Address mapping from peer to local not configured
l Channel range not correct
l Facility options inhibited by network have been carried.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 4
Configuring LAPB, X.25 and X.25 Switching
4-47
Troubleshooting: if the address is configured incorrectly, change the configuration. For
the last two causes, please consult the network management department for correct
channel range and permissible facility options.
Fault 3: the virtual circuit can be set up, but is frequently reset or cleared during data
transmission.
Troubleshooting: It is very likely that the flow control parameters are set incorrectly. For
the back to back direct connection, check the sending window and receiving window of
the local and peer to see whether they match each other. In case it is connected to
public packet networks, consult the network management department. about correct
flow control parameters.
Fault 4: the request to set Permanent virtual circuits (PVCs) is rejected.
Troubleshooting: if the channel section of the permanent virtual circuit is disabled, the
X.25 will reject the request to set a permanent virtual circuit. In this case, simply enable
the permanent virtual circuit channel section.
Fault 5: after configuring SVC application of XOT, you cannot ping through
Troubleshooting: there are various reasons. You may first check if the physical and
protocol statuses of the interface are UP. If the interface status is DOWN, check if the
physical connection and bottom configuration are correct. If the interface is properly
configured, then check the SVC configuration. If SVC is also properly configured, check
the XOT configuration.
Fault 6: after configuring PVC application of XOT, you cannot ping through
Troubleshooting: there are various reasons. You may first check if the physical and
protocol statuses of the interface are UP. If the interface status is DOWN, check if the
physical connection and bottom configuration are correct. If the interface is properly
configured, then check the PVC configuration. If PVC is also properly configured, check
the XOT configuration.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-1
Chapter 5 Configuring Frame Relay
5.1 Frame Relay Protocol Overview
Frame-Relay protocol is a fast-packaging switching technology, which develops on the
basis of X.25 technology. Compared with X.25 protocol, Frame-Relay only implements
the core function of the link layer, easily and efficiently.
A frame relay network provides capacity of data communication between user
equipment (such as routers and hosts), also called data terminal equipment (DTE). The
equipment that provides access for DTE is data circuit-terminating equipment (DCE). A
frame relay network can be a public network, a private enterprise network, or a network
formed by direct connection between data equipment.
The frame relay protocol is a statistics multiplexing protocol, providing multiple virtual
circuits on a single physical transmission line. Each virtual circuit is identified by a DLCI
(Data Link Connection Identifier), which is valid only on the local interface and the
corresponding opposite interface. This means that in the same frame relay network, the
same DLCI on different physical interfaces does not indicate the same virtual
connection. A user interface in the frame relay network supports up to 1024 virtual
circuits, among which the DLCI range available to the user is 16~1007. As a frame
relay virtual circuit is connection oriented, different local DLCIs are connected to
different opposite equipment. Therefore, the local DLCI can be considered as the
"frame relay address" of the opposite equipment.
Frame relay address mapping associates the opposite equipment s protocol address
with its frame relay address (local DLCI), so that the upper layer protocol can locate the
opposite equipment by using its protocol address. Frame relay mainly bears IP. In
sending IP message, only the next hop address of the message can be obtained from
the route table, so this IP address must be used to determine the corresponding DLCI
before sending. This process can be performed by searching for the frame relay
address mapping table, because the mapping relation between the opposite IP
address and the next hop DLCI is stored in the address mapping table. The address
mapping table can be manually configured, or maintained dynamically by the Inverse
ARP protocol.
Virtual circuits can be divided into permanent virtual circuit and switching virtual circuit,
according to their different configuration method. Virtual circuits configured manually
are called Permanent virtual circuits (PVCs), and those created by protocol negotiation
are called switching virtual circuits, which are automatically created and deleted by
Inverse ARP protocol. At present, the most frequently used in frame relay is the
permanent virtual circuit mode, i.e., manual configured virtual circuit.
In the permanent virtual circuit mode, test the availability of the virtual circuit, which is
accomplished by the local management interface (LMI) protocol. VRP supports three
LMI protocols: LMI complying with ITU-T Q.933 Appendix A, LMI complying with ANSI
T1.617 Appendix D and Gang of Four LMI (also called Cisco LMI). Their basic working
mode is: DTE sends one Status Enquiry message to query the virtual circuit status at
certain interval, after the DCE receives the message, it will immediately use the Status
message to inform DTE the status of all the virtual circuits on current interface.
The status of Permanent virtual circuits (PVCs) on DTE is completely determined by
DCE. And the network determines the status of Permanent virtual circuits (PVCs) of
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-2
DCE. In case that the two network devices are directly connected, the equipment
administrator sets the virtual circuit status of DCE. In VRP, the quantity and status of
the virtual circuits are set at the same time when address mapping is set (with the
frame-relay map command). They can also be configured with the frame relay local
virtual circuit configuration command (frame-relay local-dlci) or inter-frame relay sub-
interface virtual command (frame-relay interface-dlci).
5.2 Configuring Frame Relay
5.2.1 Frame Relay Configuration Task List
The frame relay configuration task list is as follows:
l Configuring Interface Encapsulation as Frame Relay
l Configuring Frame Relay Terminal Type
l Configuring Frame Relay LMI Type
l Configuring Frame Relay Protocol Parameters
l Configuring Frame Relay Address Mapping
l Configuring Frame Relay Local Virtual Circuit
l Configuring Frame Relay Sub-Interface
l Configuring Frame Relay PVC Switching
l Enable/Disable TCP/IP Header Compression on Interfaces
5.2.2 Configuring Interface Encapsulation as Frame Relay
In the interface configuration mode, perform the following task to configure the interface
encapsulation as frame relay.
Table LLC-5-1 Configure interface encapsulation as frame relay
Operation Command
Configure interface encapsulation as frame relay encapsulation frame-relay [ cisco-compatible | ietf ]
By default, the interface is encapsulated with link layer protocol PPP and the default
encapsulating format is ietf.
Note the following points:
1) The interface can be encapsulated with Frame-Relay only when it operates in the
synchronous mode.
2) When SLIP is encapsulated on the interface, the physical attributes of the
interface cannot be modified to synchronous mode. At this time, you should first
modify the link layer encapsulation of the interface to PPP and then you may
change the interface attribute to synchronous mode.
3) After the interface is encapsulated with Frame-Relay its upper layer still can carry
IP and IPX protocols.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-3
& Note:
1) In VRP, the IETF standard can be selected to encapsulate the frame relay protocol in the format
stipulated in RFC1490. The format compatible with CISCO router dedicated encapsulation format can also
be selected.
2) The default encapsulation format is ietf encapsulation.
3) The frame relay interface can send the message in either of the encapsulation formats, while it can
recognize and receive messages in both formats. That is, even if the encapsulation format of frame relay
of opposite equipment is different from that of the local, the equipment at the two ends can communicate
with each other as long as the opposite equipment can recognize the two formats automatically. But when
the opposite equipment can not recognize the two formats automatically, the frame relays of equipment at
the two ends must be set to the same format.
5.2.3 Configuring Frame Relay Terminal Type
In frame relay, the two sides in communication are classified into user side and network
side. The user side is called DTE, and the network side is called DCE. The equipment
response interface should be configured as DTE or DCE format according to its
location in the network. In frame relay networks, Network-to-Network Interface (NNI) is
used between the frame relay switches.
In the interface configuration mode, perform the following task to configure the type of
frame relay interface as DTE, DCE or NNI.
Table LLC-5-2 Configure frame relay interface type
Operation Command
Configure frame relay interface type frame-relay intf-type { dce | dte | nni }
Restore the frame relay interface type to the default value,
i.e. DTE mode
no frame-relay intf-type
The default type of frame relay interface is DTE.
Note the following point: If the terminal type of Frame-Relay interface is changed to
DCE or NNI, frame-relay switching should be enabled in the global configuration
mode.
5.2.4 Configuring Frame Relay LMI Type
The LMI protocol is used to maintain the PVC lists of frame relay protocol, including
adding PVC records, deleting the records about disconnected PVCs, monitoring the
change of PVC status, and verifying the link integrity. VRP supports three standard LMI
protocols: LMI complying with ITU-T Q.933 Appendix A, LMI complying with ANSI
T1.617 Appendix D and Gang of Four LMI (also called Cisco LMI)
In the interface configuration mode, perform the following task to configure the type of
LMI protocol of frame relay interface.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-4
Table LLC-5-3 Configure frame relay LMI protocol type
Operation Command
Configure frame relay LMI protocol type
frame-relay lmi-type { ansi | cisco-
compatible | q933a }
When the frame relay interface type is DCE or NNI, this command will
restore the frame relay interface LMI protocol type to the default q933a;
when the frame relay interface type is DTE, this command will set the
interface and the LMI protocol type for peer negotiation.
no frame-relay lmi-type
When the frame relay interface type is DCE or NNI, the default type of LMI protocol of
interface is Q933a.
When the frame relay interface type is DTE, the default LMI protocol of interface is null.
5.2.5 Configuring Frame Relay LMI Protocol Parameters
LMI protocol specification is as follows:
l DTE sends a Status-Enquiry message at certain interval (determined by T391).
There are two types of Status-Enquiry messages: link integrity verification
message and link status enquiry message. Parameter N391 defines the ratio of
the two types of messages sent, i.e. number of link integrity verification messages :
number of link status enquiry packet messages = N391-1: 1. DTE sends a
Status-Enquiry message to query the link integrity and all the PVC status or Full
Satus Message Polling.
l DCE immediately sends a Status response after receiving the message. If the
DTE does not receive any response within a specified time, it will record this error.
l If the error number exceeds the threshold, DTE will regard the physical channel
and all virtual circuits as unavailable. N392 and N393 together define "error
threshold".
l N392 and N393 together define "error threshold". In other words, if errors reach
N392 among the N393 Status-Enquiry messages sent by DTE, DTE will consider
that error number has reached the threshold and the physical channel and all
virtual circuits are unavailable.
l The meanings of N392 and N393 of DCE are similar to those of N392 and N393
of DTE. The difference is: the fixed time interval at which DCE requires DTE to
send the Status-Enquiry message is determined by T392, while that in DTE is
determined by T391.
Frame relay protocol parameters and their configurations are respectively shown in
Table LLC-5-4 and LLC-5-5.
Table LLC-5-4 Meanings of frame relay protocol parameters
Working mode Meaning of parameter Value range Default value
Request PVC status counter (N391) 1~255 6
Error threshold (N392) 1~10 3
Event counter (N393) 1~10 4 DTE
User side polling timer (T391), the value 0
indicates that LMI protocol is disabled
0~32767
(Unit: second)
10
(Unit: second)
Error threshold (N392) 1~10 3
Event counter (N393) 1~10 4
DCE
Network side polling timer (T392)
5~30
(Unit: second)
15
(Unit: second)
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-5
These parameters are stipulated by Q.933 Appendix A, with the meanings as follows:
Meanings of parameters related to DTE working mode:
l T391DTE: the interval of link full status message polling of the devices at the DTE
side
l N391: DTE sends a Status-Enquiry message at certain interval (determined by
T391). There are two types of Status-Enquiry messages: link integrity verification
message and link status enquiry message. Parameter N391 defines the ratio of
the two types of messages sent, i.e. number of link integrity verification messages :
number of link status enquiry packet messages = N391-1: 1
l N392DTE: it indicates the threshold for errors among the observed events.
l N393DTE: it indicates the total of observed events.
DTE sends a Status-Enquiry message at certain interval (determined by T391) to query
the link status. DCE immediately sends a Status response after receiving the message.
If the DTE does not receive any response within a specified time, it will record this error.
If the error number exceeds the threshold, DTE will regard the physical channel and all
virtual circuits as unavailable. N392 and N393 together define "error threshold". In
other words, if errors reach N392 among the N393 Status-Enquiry messages sent by
DTE, DTE will consider that error number has reached the threshold and the physical
channel and all virtual circuits are unavailable.
Meanings of parameters related to DCE working mode:
l T392DCE: a time variable, which defines the maximum time for DCE to wait for
one Status-Enquiry message and should be larger than T391.
l N392DCE: it indicates the threshold for errors among the observed events.
l N393DCE: it indicates the total of observed events.
Note the following points: N392 should be less than or equal to N393 and T391DTE
should be less than the peer T392DCE.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-6
Table LLC-5-5 Configure frame relay protocol parameters
Operation Command
Configure user side N391 frame-relay lmi-n391dte n391-value
Restore user side N391 to the default value no frame-relay lmi-n391dte
Configure user side N392 frame-relay lmi-n392dte n392-value
Restore user side N392 to the default value no frame-relay lmi-n392dte
Configure user side N393 frame-relay lmi-n393dte n393-value
Restore user side N393 to the default value no frame-relay lmi-n393dte
Configure user side T391 keepalive t391-value
Disable LMI protocol no keepalive
Configure network side N392 frame-relay lmi-n392dce n392-value
Restore network side N392 to the default value no frame-relay lmi-n392dce
Configure network side N393 frame-relay lmi-n393dce n393-value
Restore network side N393 to the default value no frame-relay lmi-n393dce
Configure network side T392 frame-relay lmi-t392dce t392-value
Restore network side T392 to the default value no frame-relay lmi-t392dce
& Note:
N392 should be less than or equal to N393, and T391 should be less than T392 of the peer.
5.2.6 Configuring Frame Relay Address Mapping
Frame-Relay address mapping means to establish the mapping between the peer
protocol address and the local DLCI. Address mapping of frame relay can either be
configured statically or set up dynamically.
I. Configure frame relay static address mapping
Static configuration means the manual setup of the mapping relation between the peer
protocol address and local DLCI, and is usually applied when there are few peer hosts
or there is a default route.
In interface configuration mode, perform the following task to configure the frame relay
static address mapping.
Table LLC-5-6 Configure frame relay static address mapping
Operation Command
Add a static address mapping
frame-relay map { ip | ipx } protocol-address dlci [ broadcast ]
[ cisco-compatible | ietf ] [ lin logical-number ] [ nocompress |
tcp header-compress [active | passive ] ]
Delete a static address mapping no frame-relay map [IP|IPX] protocol-address dlci
By default, the dynamic inverse arp is enabled on all the interfaces.
After the frame relay static address mapping is configured, the dynamic inverse arp will
be disabled automatically on the specified DLCI.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-7
II. Configure frame relay dynamic inverse arp
Dynamic setup means the dynamic setup of mapping relation between peer protocol
address and local DLCI after running the inverse address resolution protocol (Inverse
ARP), which is applied when the peer router also supports the "inverse address
resolution protocol" and network is complex.
In interface configuration mode, perform the following task to configure the dynamic
inverse arp of frame relay.
Table LLC-5-7 Configure frame relay dynamic address mapping
Operation Command
Enable dynamic address mapping frame-relay inverse-arp [ ip | ipx ] [ dlci ]
Disable dynamic address mapping no frame-relay inverse-arp [ ip | ipx ] [ dlci ]
By default, the dynamic inverse arp is enabled on the interface.
5.2.7 Configuring Frame Relay Local Virtual Circuit
In the interface configuration mode, perform the following task to configure the frame
relay local virtual circuit.
Table LLC-5-8 Configure frame relay local virtual circuit
Operation Command
Specify a virtual circuit for main interface frame-relay local-dlci dlci
Cancel the virtual circuit specified for main interface no frame-relay local-dlci dlci
Assign virtual circuit to interface frame-relay interface-dlci dlci
Cancel virtual circuit assigned to interface no frame-relay interface-dlci dlci
& Note:
1) The command frame-relay interface-dlci dlci can be used to specify virtual circuits for main interface and
sub-interface, while the command frame-relay local-dlci dlci can only be used to specify virtual circuits for
main interface.
2) The number of virtual circuit specified using any of the above commands should be unique, with the
value range between 16 and 1007, i.e. the virtual circuit number is unique on a physical interface.
3) When the frame relay interface type is DCE or NNI, the interface (either main interface or sub-interface)
should be configured manually with virtual circuits. When the frame relay interface type is DTE, for the
main interface, the system will determine the virtual circuit automatically according to the opposite
equipment; the sub-interface must be configured with virtual circuits manually.
5.2.8 Configuring Frame Relay Sub-Interface
The Frame-Relay interface is a kind of NBMA (Non-Broadcast Muti-Access) interface,
which supports sub-interfaces. The frame relay module has two types of interfaces:
main interface and sub-interface. The sub-interface is of logical structure and can be
used to configure protocol address and virtual circuit PVC. One physical interface can
include multiple sub-interfaces, which do not exist physically. However, for the network
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-8
layer, both the sub-interface and main interface can be used to configure the PVC to
connect to remote equipment.
The sub-interface of frame relay falls into two types: point-to-point sub-interface, used
to connect a single remote object and point-to-multipoint sub-interface, used to connect
multiple remote objects in the same network segment. Multiple PVCs can be
configured on one point-to-multipoint sub-interface, and a MAP (address mapping) is
set up between each PVC and the connected remote protocol address. In this way,
different PVCs can reach different remotes without confusion. MAP can be set up with
manual configuration or set up dynamically using inverse address resolution protocol.
Point-to-point sub-interface is applied similarly, where one sub-interface is connected
to one opposite equipment only, and the opposite equipment can be determined
uniquely by configuring a PVC on the sub-interface, without configuring a MAP.
1) Creating Sub-Interface
In the interface configuration mode, perform the following task to create a sub-
interface.
Table LLC-5-9 Create frame relay sub-interface
Operation Command
Enter interface configuration mode (global
configuration mode or interface configuration mode)
interface type number
Configure interface encapsulation as frame relay encapsulation frame-relay
Clear IP address configuration of main interface
interface type number.subinterface-number [multipoint |
point-to-point ]
Create sub-interface no interface type number.subinterface-number
2) Configuring virtual circuit of frame relay sub-interface
In interface configuration mode, perform the following task to configure the virtual
circuit of frame relay sub-interface.
Table LLC-5-10 Configure virtual circuit of frame relay sub-interface
Operation Command
Configure a virtual circuit frame-relay interface-dlci dlci
Remove a virtual circuit no frame-relay interface-dlci
3) Configuring Sub-Interface PVC and Establish Address Mapping
Since there is only one peer address for point-to-point sub-interface, the peer address
is determined when a PVC is configured for the sub-interface. For point-to-multipoint
sub-interface, the peer address and local DLCI can be determined by configuring static
address mapping or using inverse address resolution protocol.
l Establishing static address mapping of frame relay sub-interface
Table LLC-5-11 Establish static address mapping
Operation Command
Establish address mapping frame-relay map [ip|ipx] protocol-address dlci [ option ]
Delete an address mapping
no frame-relay map [ip|ipx] protocol-address dlci
[option]
l Applying dynamic address mapping to the sub-interface
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-9
Table LLC-5-12 Configure frame relay dynamic address mapping
Operation Command
Enable dynamic address mapping frame-relay inverse-arp [ip|ipx] [ dlci ]
Disable dynamic address mapping no frame-relay inverse-arp [ip|ipx] [dlci ]
By default, all the sub-interfaces are enabled to use dynamic inverse-arp.
5.2.9 Configuring Frame Relay PVC Switching
Perform the following task to configure frame relay PVC switching. Enable/disable
frame relay PVC switching is executed in global configuration mode, while all the other
commands are executed in interface configuration mode.
Table LLC-5-13 Configure frame relay PVC switching
Operation Command
Enable frame relay PVC switching frame-relay switching
Disable frame relay PVC switching no frame-relay switching
Set the interface type of frame relay performing frame
relay switching to NNI or DCE. If set to DTE, the frame
relay switching will be disabled
frame-relay intf-type { dce| dte | nni}
Add frame relay PVC switching
frame-relay route in-dlci interface out-interface
out-dlci
Delete frame relay PVC switching no frame-relay route in-dlci
& Note:
1) PVC switching will be enabled only when the type of frame relay interface configured with PVC
switching is NNI or DCE.
2) PVC switching will be enabled only when two or more interfaces of the equipment for the frame relay
switching are configured.
3) A PVC switching route should be configured after the PVC switching is enabled on the Frame-Relay
DCE or NNI interface.
5.2.10 Enable/Disable TCP/IP Header Compression on Interfaces
Frame relay supports TCP/IP header compression. Only when the encapsulation form
of interface frame relay is cisco-compatible, can TCP/IP header compression be
executed. TCP/IP header compression can be designated both on the interface and on
configuring static address mapping.
Perform the following task in synchronous interface configuration mode.
Table LLC-5-14 Enable/Disable TCP/IP Header Compression on Interfaces
Operation Command
Enable TCP/IP Header Compression on Interfaces frame-relay ip tcp head-compress [ passive ]
Disable TCP/IP Header Compression on Interfaces no frame-relay ip tcp head-compress
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-10
By default, interfaces use initiative compression.
5.3 Monitoring and Maintenance of Frame Relay
In privileged mode, perform the following tasks to monitor the status of frame relay in
real time.
Table LLC-5-15 Frame relay monitoring and maintenance
Operation Command
Show frame relay protocol status of each interface show frame-relay status
Show protocol address and frame relay address mapping
table
show frame-relay map
Show receiving/sending statistics information of frame relay
LMI type messages
Either all the information or the information of specified
interface can be shown. Only the main interface can be
specified.
show frame-relay lmi [ interface interface-type
nterface-number ]
Show frame relay data receiving/sending statistics
information.
Either all the information or the information of specified
interface can be shown. Only the main interface can be
specified.
show frame-relay packet [ interface
interface-type interface-number ]
Show frame relay permanent virtual circuit table show frame-relay pvc
Show frame relay PVC switching table show frame-relay route
Show statistics information of frame relay inverse address
resolution protocol messages
show frame-relay traffic
Clear all the automatically established frame relay address
mappings
clear frame-relay-inarp
Enable all the debugging of Frame-relay
debug frame-relay all [ interface interface-
type nterface-number ]
Disable all the debugging of Frame-relay
no debug frame-relay all [ interface interface-
type nterface-number ]
Enable the debugging of Frame-relay arp
debug frame-relay arp [ interface interface-
type nterface-number ]
Disable the debugging of Frame-relay arp
no debug frame-relay arp [ interface
interface-type nterface-number ]
Enable the debugging of Frame-relay event
debug frame-relay event [ interface interface-
type nterface-number ]
Disable the debugging of Frame-relay event
no debug frame-relay event [ interface
interface-type nterface-number ]
Enable the debugging of Frame-relay lmi
debug frame-relay lmi [ interface interface-
type nterface-number ]
Disable the debugging of Frame-relay lmi
no debug frame-relay lmi [ interface
interface-type nterface-number ]
Enable the debugging of Frame-relay packet
debug frame-relay packet [ interface
interface-type nterface-number ]
Disable the debugging of Frame-relay packet
no debug frame-relay packet [ interface
interface-type nterface-number ]
I. Displaying frame relay protocol status of each interface
Quidway# show frame-relay status
Serial0, DTE, physical up, protocol up
Serial0.1, multi-point, protocol up
Serial0.2, point-to-point, protocol down
Serial1, DCE, physical down, protocol down
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-11
The above information indicates that the type of frame relay interface of serial port S0 is
DTE, and both the physical layer and link layer of S0 have been activated.
II. Displaying network protocol address and frame relay address mapping
table
Quidway# show frame-relay map
Map Statistics for interface Serial0 (DTE)
IP 2.2.2.2, DLCI = 33, INTERFACE = Serial0
created time = 2000/04/02 00:01:58, type = static, status = inactive broadcast,
vlink
IP 20.20.20.1, DLCI = 100, INTERFACE = Serial0
created time = 2000/04/01 23:57:00, type = dynamic, status = active broadcast,
vlink
Point-to-Point DLCI, DLCI = 200, INTERFACE = Serial0.2
created time = 2000/04/02 00:04:36, status = inactive
IP 100.100.0.1, DLCI = 280, INTERFACE = Serial0
created time = 2000/04/02 00:00:57, type = static, status = inactive vlink
It can be indicated that the first address mapping is created between the PVC with
DLCI=33 on the serial port S0 and the peer IP address 2.2.2.2 at 2000/04/02 00:01:58.
Its type is static, i.e. it is created manually (if the type is dynamic, it indicates that it is
created dynamically with inverse address resolution); the status is inactive, which
indicates that it is not activated and the message broadcast is permitted.
III. Displaying configuration information and statistics information of LMI
protocol
LMI protocol is used to maintain the current frame relay link status and the related
messages include Status Enquiry message and status message.
Quidway# show frame-relay lmi
Frame relay LMI statistics for interface Serial0 (DTE, CISCO)
T391DTE = 10 (keepalive 10) N391DTE = 6, N392DTE = 3, N393DTE = 4 out status
enquiry = 96, in status = 85 status timeout = 3, discarded messages = 3
Frame relay LMI statistics for interface Serial1 (DCE, ANSI)
T391DTE = 0 (no keepalive)
T392DCE = 15, N392DCE = 3, N393DCE = 4 in status enquiry = 0, out status = 0
status enquiry timeout = 0, discarded messages = 0
The above information indicates that the type of frame relay interface of serial port S0 is
DTE, LMI protocol is CISCO compatibility protocol. At DTE side, T391 is set to 10,
N391 set to 6, N392 set to 3, and N393 set to 4. 96 Status Enquiry messages have
been sent and S0, 3 status messages timeout, and 3 discarded messages have
received 85 status messages.
IV. Displaying frame relay receiving/sending statistics information
Quidway# show frame-relay packet
Frame relay packet statistics for interface Serial0 (DTE)
in packets = 84, in bytes = 1333
out packets = 92, out bytes = 1217
discarded in packets = 13, discarded out packets = 0
Frame relay packet statistics for interface Serial1 (DCE)
in packets = 0, in bytes = 0
out packets = 0, out bytes = 0
discarded in packets = 0, discarded out packets = 0
The above information indicates that the type of frame relay interface of serial port S0 is
DTE; S0 has received 84 messages with 1333 bytes, and sent 92 messages with 1217
bytes; 13 received messages are discarded and no sent message is discarded.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-12
V. Displaying frame relay permanent virtual circuit table
Quidway# show frame-relay pvc
PVC statistics for interface Serial0 (DTE, physical UP)
DLCI = 100, USAGE = UNUSED (0000), INTERFACE = Serial0
create time = 2000/04/01 23:55:39, status = active
in BECN = 0, in FECN = 0
in packets = 0, in bytes = 0
out packets = 0, out bytes = 0
DLCI = 102, USAGE = LOCAL (0010), INTERFACE = Serial0.1
create time = 2000/04/01 23:56:14, status = active
in BECN = 0, in FECN = 0
in packets = 0, in bytes = 0
out packets = 0, out bytes = 0
The above information indicates that the PVC with DLCI=100 is unavailable and it is
configured on serial port S0. The creation time is 2000/04/01 23:55:39 and PVC is
active. No in FECN message or in BECN message is received; no frame is received
or sent; and no byte is received or sent.
VI. Displaying frame relay PVC switching table
Quidway# show frame-relay route
% Frame-relay switching is on
Frame relay switch statistics
In Interface In DLCI Out Interface Out DLCI Status
Serial1 100 Serial0 100 Inactive
Meanings of fields in PVC switching table:
In Interface: input interface unit
In DLCI: input DLCI
Out Interface: output interface unit
Out DLCI: output DLCI
Status: connection status
VII. Displaying inverse address resolution protocol message statistics
information
Quidway# show frame-relay traffic
Frame relay InverseARP statistics for interface Serial0 (DTE)
in ARP request = 0, out ARP reply = 0
out ARP request = 1, in ARP reply = 1
Frame relay InverseARP statistics for interface Serial1 (DCE)
in ARP request = 0, out ARP reply = 0
out ARP request = 0, in ARP reply = 0
The above information shows the statistics information of inverse address resolution
protocol message.
The above information indicates that on the serial port S0, no ARP request is received,
no ARP response is sent, 1 ARP request is sent, and 1 ARP response is received.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-13
5.4 Typical Frame Relay Configuration Example
5.4.1 Interconnecting LANs via Frame Relay Network
I. Networking requirement
Interconnect LANs via the public frame relay network. In this mode, the router can only
work as user equipment in the frame relay DTE mode.
II. Networking diagram
FR
Router C
Router B
DLCI=50
DLCI=60
DLCI=80
DLCI=70
Quidway Router A
IP:202.38.163.253
IP:202.38.163.251
IP:202.38.163.252
Figure LLC-5-1 Interconnect LANs via frame relay network
III. Configuration procedure
l Configure Router A:
! Configure interface IP address
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# ip address 202.38.163.251 255.255.255.0
! Configure interface encapsulation as frame relay
Quidway(config-if-Serial1)# encapsulation frame-relay
Quidway(config-if-Serial1)# frame-relay intf-type dte
! If the opposite router supports inverse address resolution function, configure dynamic
address mapping
Quidway(config-if-Serial1)# frame-relay inverse-arp
! Otherwise configure static address mapping
Quidway(config-if-Serial1)# frame-relay map ip 202.38.163.252 50
Quidway(config-if-Serial1)# frame-relay map ip 202.38.163.253 60
l Configure Router B:
! Configure interface IP address
Quidway(config)# interface serial 1
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-14
Quidway(config-if-Serial1)# ip address 202.38.163.252 255.255.255.0
! Configure interface encapsulation as frame relay
Quidway(config-if-Serial1)# encapsulation frame-relay
Quidway(config-if-Serial1)# frame-relay intf-type dte
! If the opposite router supports inverse address resolution function, configure dynamic
address mapping
Quidway(config-if-Serial1)# frame-relay inverse-arp
! Otherwise configure static address mapping
Quidway(config-if-Serial1)# frame-relay map ip 202.38.163.251 70
l Configure Router C:
! Configure interface IP address
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# ip address 202.38.163.253 255.255.255.0
! Configure interface encapsulation as frame relay
Quidway(config-if-Serial1)# encapsulation frame-relay
Quidway(config-if-Serial1)# frame-relay intf-type dte
! If the opposite router supports inverse address resolution function, configure dynamic
address mapping
Quidway(config-if-Serial1)# frame-relay inverse-arp
! Otherwise, configure static address mapping
Quidway(config-if-Serial1)# frame-relay map ip 202.38.163.251 80
5.4.2 Interconnecting LANs via Private Line
I. Networking requirement
Two Quidway routers are directly connected via a serial port. Router A works in the
frame relay DCE mode, and Router B works in the frame relay DTE mode.
II. Networking diagram
Quidway Router A Quidway Router B
IP:202.38.163.251 IP:202.38.163.252
DLCI=100
Figure LLC-5-2 Interconnect LANs via private line
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-15
III. Configuration procedure
l Configure Router A:
! Configure interface IP address
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# ip address 202.38.163.251 255.255.255.0
! Configure interface encapsulation as frame relay
Quidway(config-if-Serial1)# encapsulation frame-relay
Quidway(config-if-Serial1)# frame-relay intf-type dce
! Configure local virtual circuit
Quidway(config-if-serial1) # frame-relay local-dlci 100
! If the opposite router supports inverse address resolution function, configure dynamic
address mapping
Quidway(config-if-Serial1)# frame-relay inverse-arp
! Otherwise configure static address mapping
Quidway(config-if-Serial1)# frame-relay map ip 202.38.163.252 100
l Configure Router B:
! Configure interface IP address
Quidway(config)# interface serial 1
Quidway(config-if-Serial1)# ip address 202.38.163.252 255.255.255.0
! Configure interface encapsulation as frame relay
Quidway(config-if-Serial1)# encapsulation frame-relay
Quidway(config-if-Serial1)# frame-relay intf-type dte
! If the opposite router supports inverse address resolution function, configure dynamic
address mapping
Quidway(config-if-Serial1)# frame-relay inverse-arp
! Otherwise configure static address mapping
Quidway(config-if-Serial1)# frame-relay map ip 202.38.163.251 100
5.5 Fault Diagnosis and Troubleshooting of Frame Relay
1) Fault 1: the physical layer in DOWN status.
Troubleshooting:
Check whether the physical line is normal.
Check whether the opposite equipment runs normally.
2) Fault 2: the physical layer is already UP, but the link layer protocol is DOWN.
Troubleshooting:
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 5
Configuring Frame Relay
5-16
Check whether both local equipment and opposite equipment have been encapsulated
with frame relay protocol.
If two sets of equipment are directly connected, check the local equipment and
opposite equipment to see whether one end is configured as frame relay DTE interface
and the other end as frame relay DCE interface.
If everything is OK, turn on the monitoring switch for the frame relay LMI message to
see whether the Status Enquiry messages correspond to the Status message. If not, it
indicates the physical layer data is not received/sent correctly. Check the physical layer.
Command debug frame-relay lmi is used to turn on the monitoring switch for frame
relay LMI information.
3) Fault 3: link layer protocol is UP, but cannot Ping through the peer.
Troubleshooting:
Check whether the link layer protocols of the equipment at both ends are UP.
Check whether the equipment at both ends have configured (or created) correct
address mapping for the peer.
Check the route table to see whether there is a route to the peer.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 6
Configuring HDLC
6-1
Chapter 6 Configuring HDLC
HDLC (High Data Link Control), is a kind of bit-oriented link layer protocol. Its most
prominent feature is that it can transparently transmit any kind of bit flow without the
restriction that the data must be character set. Protocols of standard HDLC protocol
group all operate upon the synchronous serial lines, e.g., DDN. The address field of
HDLC is 8 bytes and its control field is 8 bits, which is used to implement all kinds of
control information of HDLC protocol and to mark whether they are data. VRP supports
the HDLC protocol encapsulation and can interconnect with HDLC protocol of other
popular devices.
6.1 Configuring HDLC
6.1.1 HDLC Configuration Task List
HDLC protocol can be configured with two commands:
l Encapsulate interface with HDLC protocol
l Set keepalive time delay
6.1.2 Encapsulating Interface with HDLC Protocol
In interface configuration mode, perform the following task to encapsulate the interface
with HDLC protocol.
Table LLC-6-1 Configure interface with HDLC protocol
Operation Command
Encapsulate interface with HDLC protocol encapsulation hdlc
By default, the link layer protocol encapsulated on the interface is PPP.
Things should be noted:
Only when the interface operates in the synchronous mode, can it be encapsulated
with HDLC.
When the interface is encapsulated with SLIP, its physical property cannot be changed
to synchronous mode. At this time, you should first change the link layer encapsulation
of the interface to PPP, and then you may change the interface property to synchronous
mode.
After the interface is encapsulated with HDLC, the upper layer can still support IP and
IPX.
User Manual - Configuration Guide (Volume 1)
Versatile Routing Platform
Chapter 6
Configuring HDLC
6-2
6.1.3 Setting Keepalive Time Delay
The keepalive parameter of HDLC protocol is used to set the polling interval of status
polling timer. keepalive of the equipment at both ends should be set to the same value.
Perform the following task to set the parameter keepalive.
Table LLC-6-2 Set parameter keepalive
Operation Command
Set keepalive, with value range 0~32767 and in the unit of second;
the default value is 10 seconds
keepalive value
Set keepalive to 0, i.e. to disable the link detection function no keepalive
By default, the delay of keepalive is 10 seconds.
Note the following point: the delay of keepalive set for the devices of the two ends must
be the same.
6.2 Monitoring and Maintenance of HDLC
In privileged mode, perform the following task to monitor the current status of HDLC in
real time and carry out maintenance efficiently.
Table LLC-6-3 Monitoring and Maintenance of HDLC
Operation Command
Enable all the information debugging of
HDLC protocol
debug hdlc all [ interface type number ]
Enable HDLC event debugging debug hdlc event [ interface type number ]
Enable HDLC packet debugging debug hdlc packet [ interface type number ]