01-05 ATM Configuration
01-05 ATM Configuration
5 ATM Configuration
Definition
ATM was designated as the transmission and switching mode for Broadband
Integrated Services Digital Networks (B-ISDN) by the ITU-T in June 1992. Due to
its high flexibility and support to the multi-media service, ATM is considered as
the key for realizing broadband communications.
An ATM cell has a fixed length of 53 bytes. As defined by the ITU-T, ATM
transmits, multiplexes, and switches data based on cells. For example, the
messages of voice, video, and data are all transmitted in the cells of the fixed
length. This ensures the fast data transmission.
ATM is connection-oriented. Each VC is identified by a Virtual Path Identifier (VPI)
and a Virtual Channel Identifier (VCI). One pair of VPI/VCI values is useful only on
a link segment between ATM nodes. If a connection is broken, the relevant
VPI/VCI values are released.
Purpose
ATM provides the network with a versatile and connection-oriented transfer mode
that applies to different services.
Before the Gigabit Ethernet technology, ATM backbone switches were mostly used
on backbone networks to ensure high bandwidth. ATM dominated among
network technologies because it can provide good QoS and transmit voice, data,
and video with high bandwidth.
Nevertheless, the initial roadmap for ATM, that is, coping with all the network
communication issues, was too ambitious and idealistic. As a result, the ATM
implementation became so complicated. The aim of the ATM technology is too
ideal. The realization of ATM is complex. The perfection of the ATM technology
and complexity of its architecture result in the difficulties of developing,
configuring, managing, and troubleshooting the ATM system.
ATM network devices are quite expensive. The ATM network cannot be affordable
for people and its excellent performance is unknown from the origin of ATM.
In the late 1990's, Internet and IP technology overshadowed ATM for their
simplicity and flexibility. They developed at a fast rate in the application field. This
made a severe impact on the B-ISDN plan.
ATM is, however, still regarded as the best transmission technology of B-ISDN
because it has advantages in transporting integrated services. Thus, the IP
technology integrated with ATM. This brought about the new era of constructing
broadband networks through the integration of the IP and ATM technologies.
Control User
plane plane
ATM adaptation
layer
ATM layer
Physical
layer
● Control plane: This plane generates and manages signaling requests. It sets
up, monitors, and removes connections by using signaling protocols.
● User plane: This plane manages data transmission.
● Management plane: This plane is divided into layer management and plane
management.
– Layer management: It is responsible for the management of every layer
in each plane. It has a layered structure corresponding to other planes.
– Plane management: It is responsible for the system management and the
communications between different planes.
Figure 5-2 Comparison between the ATM protocol architecture and the OSI
reference model
ATM Model OSI Reference Model
Table 5-1 Functions of layers and sub-layers in the ATM reference model
The detailed functions of layers and sub-layers in the ATM reference model are
described in the following sections.
The device supports the following transmission standards for G.SHDSL interfaces:
The device supports the following transmission standards for ADSL interfaces:
● G.DMT(G.992.1)
● ADSL2(G.992.3)
● ADSL2+(G.992.5)
● T1.413
● AnnexL
● AnnexM
● AnnexJ
NOTE
The device provides ADSL-A/M and ADSL-B/J boards. Only ADSL-A/M boards support
T1.413, AnnexL and AnnexM standards, and only ADSL-B/J boards support AnnexJ standard.
The 48-byte payload that is input into the ATM layer is called the Segmentation
and Reassembly-Protocol Data Unit (SAR-PDU). The 53-byte cell is output from
the ATM layer. Thus, this cell is forwarded to the physical layer for transmission.
Private UNIs are connected to two switches on the same private ATM network
and used inside the private ATM network. Public UNIs are connected to ATM
peripheral devices or private ATM switches to public ATM switches.
● Network-to-Network Interface
The NNI refers to the interfaces between ATM switches.
Depending on whether the switches are owned by clients or operators, NNI
can be divided into two types: public NNIs and private NNIs.
Connected to two switches on the same private ATM network, the private
NNI is used inside the private ATM network. Connected to two ATM switches
of the same public network carrier, the public NNI is used by one ATM service
provider.
● B-ISDN Inter Carrier Interface
A B-ISDN Inter Carrier Interface (B-ICI) is connected to the public switches of
different network carriers and provides internal connections to multiple ATM
network carriers. B-ICIs are directly connected to NNIs.
Figure 5-3 shows the connections between various ATM network interfaces.
Figure 5-3 ATM network interfaces of the private and public networks
Public ATM
Dedicated Public Public ATM B-ICI networkB
ATM network UNI networkA
Public
Dedicated NNI Dedicated
NNI Dedicated UNI
UNI
Dedicated
UNI
NOTE
On the device, only user-to-network interfaces are used as ATM network interfaces.
VP VC
VP VC
Physical VP VC
channel VCC
VP VC
VP VC
VP VC
ATM Network
PVC PVC
SVC
Soft VC
The NNI cell header is used for communication between two switching nodes.
Figure 5-7 shows the NNI cell header format.
● GFC: indicates the general flow control with a length of 4 bits. It applies to
the UNI interfaces only. It performs flow control, and identifies different
accesses on a shared media network.
● VPI: indicates the virtual path identifier. In the UNI, it can identify 256 VPs
and its length is 8 bits. In the NNI, it can identify 4096 VPs and its length is 12
bits.
● VCI: indicates the virtual channel identifier. It can identify 65536 VCs and its
length is 16 bits.
● CLP: indicates the cell loss priority. It is used for congestion control and its
length is 1 bit. When congestion occurs, cells with the CLP as 1 are discarded
first.
● PTI: indicates the payload type indicator. It identifies the payload type and its
length is 3 bits.
● HEC: indicates the header error control. It is used for error control and cell
delimitation in a cell header and its length is 8 bits. HEC can correct 1-bit
error, find multi-bit error, and perform HEC on the physical layer.
Some specified VPI/VCI values are reserved for special cells. These special cells are
described as follows:
● Idle cell: Its VPI is 0, VCI is 0, PTI is 0, and CLP is 1. It is used for rate
adaptation.
● Unassigned cell: Its VPI is 0, VCI is 0, PTI can be any value, and CLP is 1.
● OAM cell: For the VP sub-layer, its VCI is 3 and it is used for the VP link. When
VCI is 4, it is used for the VP connection. For the VC sub-layer, it is used for
the VC link when PTI is 4. When PTI is 5, it is used for the VC connection.
● Signaling cell: It is divided into the following types:
– Component signaling cell: Its VPI can be any value, and VCI is 1.
– General broadcast signaling cell: Its VPI can be any value, and VCI is 2.
– Point-to-point (P2P) signaling cell: Its VPI can be any value, and VCI is 5.
● Payload type: Its length is 3 bits. It is used to identify the information field,
that is, the payload type. The following lists the PT values and corresponding
meanings defined by the ITU-T I.361.
– PT = 000: indicates that the service data cell does not experience
congestion and ATM user to user (AUU) is 0.
– PT = 001: indicates that the service data cell does not experience
congestion and AUU is 1.
– PT = 010: indicates that the service data cell experiences congestion and
AUU is 0.
– PT = 011: indicates that the service data cell experiences congestion and
AUU is 1.
– PT = 100: indicates the cells related to the OAM F5 segment.
– PT = 101: indicates the OAM F5 end-to-end cells.
– PT = 110: indicates the resource management cells.
– PT = 111: This PT is for future use.
ATM OAM
ATM Operation, Administration and Maintenance (OAM) provides a mechanism to
detect and locate faults and verify network performance without interrupting
services. Broadband-Integrated Services Digital Network (ITU-T B-ISDN) I.610
defines the OAM function on the ATM network and classifies the OAM function
into the following five layers in Table 5-2.
Layer Description
F1: Regenerator section layer Physical layer OAM: The OAM flow
depends on the concrete mechanism
F2: Digit section layer of the transmission system. The ATM
F3: Transmission channel layer network includes the following three
types of transmission systems:
● Transmission system based on SDH
(defined in G.707 and G.783)
● Transmission system based on cell
(defined in I.432.1, I.432.2, and I.
432.4)
● Transmission system based on PDH
(defined in G.702, G.804 and G.832)
F4: Virtual path layer ATM layer OAM: based on VP/VC and
does not depend on the transmission
F5: Virtual channel layer system.
The two types of operation flows are defined in the ATM layer: F4 and F5.
● F4 flow is the OAM cell flow in the Virtual Path Connect (VPC) and provides
the operation management and maintenance of the VP layer.
● F5 flow is the Virtual Channel Connect (VCC) and provides the operation
management and maintenance of the VC layer.
After the OAM is activated in the F4 and F5 flows, the specified OAM cells are
inserted into the user cells to occupy certain bandwidth and to be transmitted in
the same physical channel with the cells of the other users.
The F4 and F5 flows support four types of OAM cells: FM OAM cell, PM OAM cell,
active/deactive OAM cell, and SM OAM cell, as shown in Table 5-3.
FM (Fault Management) AIS (reports the errors to The FM OAM cell is uses
downstream) to detect and locate the
faults of in-service which
RDI (reports the errors to is real-time and
upstream) consecutive.
LoopBack (detects the
connectivity and locates
the faults)
CC (continuity detection)
Deactive PM (deactive
performance monitoring)
Deactive CC (deactive
continuity detection)
On the ATM network, three types of the OAM functional nodes are as follows:
● End point
The end point is defined as the point connecting the ATM network in I.610
and usually refers to the border of the ATM network. The end points are the
termination points of all the OAM cells and cannot send the OAM cells
backwards. If the end points detect that the link is faulty, they do not insert
the OAM cells into the downstream node but insert the end Remote Defect
Indication (RDI) cells into the upstream nodes and notify the upstream nodes
that the upstream link is faulty.
● Segment point
The segment point is defined in I.610. One ATM link may consist of many
segments. The segment points can terminate all the segment cells but not the
end cells. If the segment points detect that the link is faulty, they insert the
end Alarm Indication Signal (AIS) cells into the downstream nodes and the
segment RDI cells into the upstream nodes.
● Middle point
The middle point is in between the two segment points or the two end points,
so it can be classified into two types: end middle point and segment middle
point. The middle points do not terminate any cells, and the segment cells
and end cells can be transmitted transparently. If the middle points detect
that the link is faulty, they send the segment AIS cells and end AIS cells to the
downstream nodes.
The device supports F5 OAM and FM OAM cells. When the device implements
OAM, it functions only as an end point.
AAL Type
Currently, four types of AAL are available: AAL1, AAL2, AAL3/4, and AAL5. Each
type supports certain specified services on the ATM network. Products produced
by most ATM equipment manufacturers widely adopt AAL5 to support data
communication service.
NOTE
The device supports only AAL5.
● AAL1
AAL1 is used for constant bit rate (CBR), sending data at a fixed interval.
AAL1 uses one part of the 48-byte payload to bear additional information,
such as sequence number (SN) and sequence number protection (SNP). SN
contains 1-bit convergence sub-layer identifier and 3-bit sequence counting
(SC). CSI is also used for timing.
● AAL2
Compared with AAL1, AAL2 can transmit compressed voice and realize
common channel signaling (CCS) inside ISDN.
Details on AAL2 are defined in ITU-T 363.2.
AAL2 supports the processing of compressed voice at the upper limit rate of
5.3 Kbit/s. This realizes silence detection, suppression, elimination, and CCS. In
addition, higher bandwidth utilization is available. Segments can be
encapsulated into one or multiple ATM cells.
CS of AAL2 can be divided into CPCS and SSCS. SSCS is on top of CPCS. The
basic structure of AAL2 users can be recognized through CPCS. Error check,
data encapsulation, and payload breakdown can be performed.
AAL2 allows payloads of variable length to exist in one or multiple ATM cells.
● AAL3/4
As the first technology trying to realize cell delay, AAL3/4 stipulates the
connection-oriented and connectionless data transmission.
CPCS is used to detect and process errors, identify the CPCS-service data unit
(SDU) to be transmitted, and determine the length of the CPCS-packet data
unit (PDU).
● AAL5
AAL5 can also process connection-oriented and connectionless data. AAL5 is
called the simple and valid adaptation layer. It uses 48 bytes to load the
payload information. AAL5 does not use the additional information bit. It
contains no sequence number and cannot detect errors.
AAL5 SAR sub-layer is simple. It divides CPCS-PDUs into 48-byte SAR-PDUs
without any overhead and realizes the reverse function when receiving data.
The CPCS-PDU format of AAL5 CPCS is shown in Figure 5-8.
The length of the CPCS-PDU payload is variable and ranges from 1 to 65535
bytes.
As shown in Figure 5-8, no CPCS-PDU header exists. A CPCS-PDU tail,
however, occupies eight bytes. The meaning of each field in Figure 5-8 is as
follows:
– PAD: indicates the stuffing bit, making the CPCS-PDU length as the
integer multiple of 48-byte payload.
In addition, the RFC also defines the following two multiprotocol encapsulations,
both of which carry the PDU in the payload field of the AAL5 frame. The format of
the AAL5 CPCS-PDU is shown in Figure 5-9.
LLC/SNAP Encapsulation
LLC encapsulation is needed when several protocols are carried over the same VC.
To ensure that the receiver properly processes the received AAL5 CPCS-PDU
packets, the payload field must contain information necessary to identify the
protocol of the routed or bridged PDU. In LLC encapsulation, this information is
encoded in an LLC header placed in front of the carried PDU.
Unless otherwise specified, LLC in this document refers to LLC type 1. The
application of LLC type 2 is similar to that of LLC type 1.
In the detailed format of an IPv4 PDU, the Ethernet type value is 0x08-00.
Figure 5-14 shows the format of the IP PDU.
- 0x00-0D Fragments
- 0x00-0E BPDUs
The AAL5 CPCS-PDU Payload field carrying a bridged PDU must have one of
the following formats.
It is required to add padding after the PID field to align the user information
field of the Ethernet and 802.3.
The sequence of a MAC address must be the same as that in the LAN or
MAN.
VC Multiplexing
In the multiplexing technologies based on the VC, the VC between two ATM sites
is used to differentiate the protocols that carry network interconnection. That is,
each protocol must be carried over each VC.
Thus, no additional multiplexing information is contained on the payload of each
AAL5 CPCS-PDU. This can save bandwidth and reduce the processing cost.
● VC Multiplexing for Routed Protocols
In VC multiplexing for routed protocols, the Payload field of an AAL5 CPCS-
PDU contains only the routed PDU packet. The format of the PDU packet is
shown in Figure 5-16.
...
Carried PDU
(up to 2^16 - 1 octets)
...
Since the PID field is not contained in a bridged Ethernet/802.3 PDU packet,
the VC determines the LAN FCS. PDUs in the same bridged medium can carry
different protocols regardless of whether the PDUs contain the LAN FCS.
CBR
The CBR service class is designed for connections requiring a static amount of
bandwidth that is continuously available during the lifetime of the connections.
The amount of bandwidth is determined by the peak cell rate (PCR). The source
end configured with the CBR service class can send cells at the PCR at any time.
The CBR service class is usually used to support real-time services requiring low
delay, such as voice and video services.
VBR-RT
The VBR-RT service class is used for real-time applications requiring low delay and
jitter, such as voice and video services.
The VBR-RT is determined by the PCR, sustainable cell rate (SCR), and maximum
burst size (MBS). When the average cell rate is the SCR, the source end can
transmit burst traffic of the maximum length of the MBS at the PCR without
packet loss.
VBR-NRT
The VBR-NRT service class supports burst and non-real-time applications. The
VBR-NRT service class does not require low delay and has the same parameters as
the VBR-RT service class.
UBR
The UBR service class is used for applications that tolerate the cell delay and cell
loss on the network. The UBR service class does not provide QoS guarantee, and
the cell loss ratio and cell delay are variable. If congestion occurs, UBR cells are
discarded first.
Licensing Requirements
ATM features is a basic capability of an AR router and is not under license control.
Feature Limitations
An E1-IMA interface, ADSL interface, VDSL interface working in ATM mode or
G.SHDSL interface working in ATM mode on the device provides ATM features. For
details on how to configure E1-IMA, ADSL, VDSL and G.SHDSL interfaces, see IMA
Configuration, ADSL Interface Configuration, VDSL Interface Configuration and
G.SHDSL Interface Configuration in the Huawei AR Series Access Routers
Configuration Guide - Interface Management. For details on how to configure E1-
IMA, ADSL, VDSL and G.SHDSL interfaces, see IMA (Licensing Requirements and
Limitations for IMA), ADSL (Licensing Requirements and Limitations for ADSL
Interfaces), VDSL (Licensing Requirements and Limitations for VDSL Interfaces),
and G.SHDSL (Licensing Requirements and Limitations for G.SHDSL Interfaces).
If PPPoE packets or MP packets are transmitted over an ATM link, only the
PPPoEoA client and MPoEoA client are supported.
5.4.1 IPoA
IP over AAL5 (IPoA) means that AAL5 bears IP packets. That is, IP packets are
encapsulated in ATM cells and transmitted on the ATM network.
ATM1/0/0
To A:0/40
RouterA To C:0/51
ATM1/0/0 ATM
Network
To B:0/40 RouterC
To C:0/41
ATM1/0/0
To A:0/41
To B:0/51
Realization
As shown in Figure 5-18, on RouterA, PVC 0/40 can reach RouterB, and PVC 0/41
can reach RouterC. If IP packets sent to RouterB need to be sent from PVC 0/40,
the IP address of RouterB must be mapped on PVC 0/40. After address mapping is
set up, RouterA sets up a route that reaches the IP address of RouterB. The
outgoing interface is the interface where ATM PVC 0/40 resides.
5.4.2 IPoEoA
IP over Ethernet over AAL5 (IPoEoA) has a three-layer architecture. The high layer
is IP encapsulation, the middle layer is IPoE, and the low layer is IPoE over AAL5.
IPoE packets are transmitted after being encapsulated on the ATM.
When devices are connected to the remote access server through a high rate link,
the access to the external network can be realized through the Ethernet packets
over ATM.
● PVCs that are associated with the same VE interface communicate through
Layer 2.
ADSL
Router A
Ethernet
Server
202.38.160.1
PC
Router C
DSLAM To ADSL Router A: 0/60
To ADSL Router B: 0/61
Virtual Ethernet1/0/0
Ethernet
Server
ADSL
Router B
PC
Implementation
As shown in Figure 5-19, IP packets must be encapsulated into Ethernet frames
and transmitted as ATM cells. Thus, the interfaces with the IP address and
Ethernet address information must exist between routers. Setting up a VE
interface and mapping it to the PVC of ATM can realize IPoEoA. That is, all the
packets sent from the local router to the VE interface are transmitted as ATM cells
after being encapsulated through the mapped ATM interface.
5.4.3 PPPoA
PPP over AAL5 (PPPoA) means that AAL5 carries PPP packets. It means that ATM
cells are used to encapsulate PPP packets. IP or other packets are encapsulated in
PPP packets. In this manner, AAL5 can be regarded as the bearer layer of PPP
packets.
PPPoA can make use of the flexibility and extensive applications of PPP because
the PPPoA communication process is managed by PPP.
Users must create a Virtual-Template (VT) before transmitting PPP packets over
AAL5. Figure 5-20 shows typical networking of PPPoA.
RouterC
PC 1 DSLAM
ATM1/0/0
Realization
In PPPoA mode, PPP packets are encapsulated as ATM cells and transmitted on an
ATM network. The PPPoA mode is similar to the IPoEoA mode.
A VT interface is required because the establishment of PPP needs to be
authenticated.
When authentication is performed on RouterC, the authenticated user name,
password, and assigned IP address pool need to be created on RouterC. Set
parameters such as the local IP address, authentication mode (PAP or CHAP) of
remote users, and address pool that allocates addresses to the authenticated users
on the VT interface. The VT is mapped to the PVC, which associates PPP and ATM.
On the ADSL Router A at the client end, a VT must be created and mapped onto
the corresponding ATM interface. The user name, password, authentication mode,
and IP address acquisition mode that are authenticated on RouterC must be
configured on a VT interface.
5.4.4 PPPoEoA
PPPoE over AAL5 (PPPoEoA) means that AAL5 bears the PPPoE (PPP over
Ethernet) packets. ATM cells are used to encapsulate Ethernet packets. In this
manner, a PVC simulates all the functions of the Ethernet.
The router implements the Ethernet packets over AAL5 through a VE interface.
This VE interface has the feature of the Ethernet and can be dynamically created
by using the configuration commands.
The protocol stack of this interface is as follows:
● The bottom layer is the PVC of ATM, through which packets can be
transmitted and received.
● The link layer is an Ethernet protocol.
● The network layer and upper layer protocols are the same as the protocols of
common Ethernet interfaces.
PPP packets are encapsulated in the Ethernet packets that are encapsulated and
transmitted in the ATM network.
ADSL
Router A
Ethernet
Server
VT10: 202.38.160.1/24
VT11: 202.38.161.1/24
PC
Router C
DSLAM To ADSL Router A: 0/60
To ADSL Router B: 0/61
ATM1/0/0.1
Ethernet
Server
ADSL
Router B
PC
Realization Method
PPP encapsulation is implemented on a VT, PPPoE is used to encapsulate PPP
packets on a VE, and an ATM interface uses PPPoEoA to encapsulate PPPoE
packets. PPPoEoA implementation is similar to PPPoA implementation.
Configure parameters such as users and address pool on the authenticating router.
External remote authentication dial-in user service (RADIUS) can also be used. The
local authentication is described here. Configuration on the VT interface is the
same as that described in PPPoA. A VE interface is set up again. The VT is mapped
on the VE interface to realize the encapsulation or decapsulation of PPPoE
packets. Then, the VE interface is mapped onto the ATM interface.
Pre-configuration Tasks
Before creating a PVC group and configuring PVC service mapping, complete the
following tasks:
● Configuring physical attributes for ATM interfaces on the device
● Configuring IP addresses and masks for ATM interfaces and sub-interfaces
● Creating PVCs and configuring their application mode
NOTE
If the interface type is an ATM sub-interface, you can run atm-link check command to enable
the connection of a link on an ATM sub-interface. When all the PVCs or PVPs go Down, the
protocol status on the ATM sub-interface is set to Down.
NOTE
If the status of a PVC is unstable, and the local end of the PVC needs to know the status
change of the remote end, the OAM F5 loopback function must be enabled on the local
end.
The virtual path identifier (VPI)/virtual channel identifier (VCI) values configured for the
primary and secondary ATM PVCs in an ATM PVC group must be the same on the local and
remote ends. The IP precedence value or the DSCP value carried by the IP packet on each
ATM PVC must also be the same on the local and remote ends. If the IP packets on ATM
PVCs on the local and remote ends are configured with different IP precedence values or
DSCP values, services provided by the ATM PVC group will be interrupted.
The PVC name or VPI/VCI values must be available for creating a PVC group or
entering the view of a PVC group.
The protection for member permanent virtual channels (PVCs) in a PVC group is
configured.
After the protection for member PVCs in a PVC group is configured, the PVC group
will become unavailable so that traffic cannot be forwarded if the link goes faulty
on a protected member PVC. This way helps detect the link fault promptly and
locate the cause.
----End
Prerequisites
PVCs with specified precedence values have been configured.
Context
PVCs in a group can be configured to transmit IP packets with different
precedence values. PVCs transmitting IP packets with high precedence values
preferentially use bandwidth resources.
After IP precedence values or DiffServ Code Point (DSCP) values are mapped to
PVCs, IP packets with different precedence values are transmitted along different
PVCs. In this manner, IP packets with different precedence values are transmitted
separately.
Procedure
Step 1 Run system-view
NOTE
PVC service mapping does not change the precedence values of IP packets transmitted
along PVCs in a PVC group. To change precedence values for IP packets, configure certain
tags carried in IP packets. For details, see the Huawei AR Series Access Routers
Configuration Guide - QoS.
----End
Prerequisites
The configurations of a PVC group and PVC service mapping are complete.
Procedure
● Run the display atm pvc-info [ interface atm interface-number [ pvc { pvc-
name [ vpi/vci ] | vpi/vci } ] ] command to check information about PVCs.
● Run the display atm pvc-info statistics [ interface interface-type interface-
number ] command to check statistics information about PVCs.
● Run the display atm pvc-group [ interface atm interface-number [ pvc
{ pvc-name [ vpi/vci ] | vpi/vci } ] ] command to check information about a
PVC group.
----End
Pre-configuration Tasks
Before configuring ATM links to transmit different protocol packets, complete the
following tasks:
● Powering on the device and ensuring that the device detects no error during
self-check
● Creating PVCs
● Performing basic configuration of transparent bridging
Prerequisites
Before creating PVCs and configuring IPoA mapping on PVCs, complete the
following configurations:
Context
By configuring IPoA mapping on PVCs, you can enable a device to encapsulate IP
packets into ATM cells and transmit them over ATM networks. This allows AAL5 to
transmit IP protocol packets.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface atm interface-number[.subinterface ]
The ATM interface or sub-interface view is displayed.
Step 3 Run pvc { pvc-name [ vpi/vci ] | vpi/vci }
A PVC is created and the PVC view is displayed.
NOTE
NOTE
NOTICE
The IP address specified in this command must be the IP address of the peer
interface. Otherwise, data cannot be correctly forwarded.
----End
Prerequisites
Before creating PVCs and configuring IPoEoA mapping on PVCs, complete the
following configurations:
Context
By configuring IPoEoA mapping on PVCs, you can enable PVCs associated with the
same Virtual Ethernet (VE) interface to communicate at Layer 2. This allows AAL5
to transmit IPoE protocol packets.
Procedure
Step 1 Run system-view
Before assigning an IPv6 address to an interface, run the ipv6 command in the system
view to enable IPv6 packet forwarding and run the ipv6 enable command on the
interface to enable IPv6.
The AAL5 encapsulation type can be aal5snap or aal5mux. The default value is
aal5snap.
----End
Procedure
Step 1 Run system-view
The AAL5 encapsulation type can be aal5snap or aal5mux. The default value is
aal5snap.
----End
Context
PPPoA mapping on a PVC enables the device to encapsulate PPP packets into ATM
cells and transmit them over an ATM network. To reduce traffic, configure PPPoA
mapping using on-demand dialing.
In on-demand dialing mode, a PVC is terminated after it becomes idle for a period
of time and is re-established when traffic needs to be transmitted. In permanent
online mode, a PVC is always functioning after it is configured. Using a PVC in on-
demand rather than permanent online dialing mode reduces traffic.
Procedure
Step 1 Run system-view
The configured link idle time determines the maximum idle time of a PPPoA
connection established in on-demand dialing mode. A PPPoA connection is
terminated when the maximum link idle time expires.
This command affects only new calls but not the established calls.
----End
Procedure
Step 1 Run system-view
A PPPoE session is created and the dialer bundle is specified for the session.
----End
Context
Users connect to a digital subscriber line access multiplexer (DSLAM) through
G.SHDSL interfaces or inverse multiplexing over ATM (IMA) interfaces to
communicate with the Point-to-Point Protocol over Ethernet over ATM (PPPoEoA)
server. When users require high bandwidth, a single PPPoEoA link cannot provide
sufficient bandwidth. You need to bundle multiple PPPoEoA links into a Multilink
PPP over Ethernet over ATM (MPoEoA) link to increase link bandwidth and
improve link reliability.
Procedure
Step 1 Create PPPoEoA mapping on PVCs of an ATM interface.
NOTE
Repeat this step to create PPPoEoA mapping on PVCs of multiple ATM interfaces.
You can repeat this step to bind multiple dialer interfaces to the same VT by
specifying the same vt-number in the ppp mp virtual-template vt-number
command.
----End
Context
ATM transparent bridging allows devices on two Ethernet networks to
communicate with each other through ATM links.
Procedure
Step 1 Run system-view
NOTE
NOTE
The bridge must be enabled before map bridge broadcast command.
----End
Prerequisites
The configurations of ATM links to transmit different protocol packets are
complete.
Procedure
● Run the display atm pvc-info [ interface atm interface-number [ pvc { pvc-
name [ vpi/vci ] | vpi/vci } ] ] command to check information about PVCs.
● Run the display atm pvc-info statistics [ interface interface-type interface-
number ] command to check statistics information about PVCs.
● Run the display atm map-info [ interface atm interface-number [ pvc { pvc-
name [ vpi/vci ] | vpi/vci } ] ] command to check information about PVC
mapping.
● Run the display interface virtual-ethernet [ interface-number ] command to
check status and statistics of VE interfaces.
----End
Pre-configuration Tasks
Before configuring the service types or OAM parameters of a PVC, complete the
following tasks:
● Configuring physical attributes for the ATM interface
● Configuring an IP address and mask for the ATM interface or sub-interface
● Creating a PVC and configuring application modes
Before configuring the parameters of VP policing of ATM interface, complete the
following tasks:
● Configuring the physical attributes for the ATM interface
● Configuring the IP address and mask of the sub-interface
● Run the service cbr output-pcr command to set the service type to Constant
Bit Rate (CBR).
● Run the service ubr [ output-pcr ] command to set the service type to
Unspecified Bit Rate (UBR).
● Run the service vbr-rt output-pcr output-scr output-mbs command to set the
service type to Variable Bit Rate-Real Time (VBR-RT).
----End
Procedure
Step 1 Run system-view
NOTE
If an ATM interface that has sub-interfaces is configured with VP policing, the VP policing is
valid for all the PVCs with the same VPI.
----End
Prerequisites
The configurations of the service type of PVC and the OAM and VP parameters are
complete.
Procedure
● Run the display atm pvc-info [ interface atm interface-number [ pvc { pvc-
name [ vpi/vci ] | vpi/vci } ] ] command to check information about the PVC.
Pre-configuration Tasks
NOTE
A maximum of eight OAM commands can be configured for PVCs on ATM interfaces of the
same card.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface atm interface-number [.subinterface-number ]
The ATM interface or sub-interface view is displayed.
Step 3 Run pvc { pvc-name [ vpi/vci ] | vpi/vci }
The PVC view is displayed.
Step 4 Run oam loopback [ up up-count down down-count retry-frequency retry-
frequency ]
OAM F5 loopback cell transmission and retransmission detection are enabled.
By default, the device does not send OAM F5 loopback cells, but the device must
respond to the received OAM F5 loopback cells.
After OAM F5 loopback cell transmission and retransmission detection are
enabled, the PVC status changes only when a certain number of OAM F5 loopback
cells are received. For example, when the device receives consecutive OAM F5
loopback cells of a number specified by up-count, the PVC becomes Up. When the
device does not receive consecutive OAM F5 loopback cells of a number specified
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface atm interface-number [.subinterface-number ]
The ATM interface or sub-interface view is displayed.
Step 3 Run pvc { pvc-name [ vpi/vci ] | vpi/vci }
The PVC view is displayed.
Step 4 Run oam cc end-to-end { both | sink | source }
OAM CC is enabled.
By default, OAM CC is disabled.
NOTE
When you configure CC, if source or both is configured on one end, sink or both must be
configured on the other end.
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface atm interface-number [.subinterface-number ]
The ATM interface or sub-interface view is displayed.
Step 3 Run pvc { pvc-name [ vpi/vci ] | vpi/vci }
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface atm interface-number [.subinterface-number ]
The ATM interface or sub-interface view is displayed.
Step 3 Run oamping pvc { pvc-name | vpi/vci } [ number timeout ]
Connectivity of an ATM link on a specified ATM interface is detected.
----End
----End
NOTICE
The statistics data cannot be restored after you run the reset command to clear it.
Confirm the action before you use the command.
NOTE
For more information about the display of interface statistics in the NMS, see related NMS
manuals.
Procedure
Step 1 Run the reset counters interface [ atm [ interface-number ] ] command to clear
the interface statistics displayed by running the display interface command.
Step 2 Run the reset counters if-mib interface [ atm [ interface-number ] ] command
to clear the interface statistics in the NMS.
Step 3 Run the reset atm interface [ atm interface-number ] command to clear the
ATM interface statistics.
----End
network. A DSLAM connects the ADSL interface of RouterA to the Internet. IPoA
application needs to be implemented.
ATM1/0/0
Internet
Ethernet4/0/0 RouterA
DSLAM
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the LAN side so that users on the enterprise network can connect
to RouterA through the Layer 2 Ethernet interface.
2. Configure the WAN side so that RouterA can use the ADSL interface to
communicate with the DSLAM.
Data Preparation
To complete the configuration, you need the following data:
● On the LAN side:
– VLAN ID allowed by the Ethernet interface: 200
– IP address of the VLANIF interface corresponding to the allowed VLAN ID:
10.0.0.1/24
● On the WAN side:
– IP address of the ADSL interface: 192.168.0.1/24
– PVC name: ipoa
– PVC number: 0/35
– IPoA mapping on the PVC (remote IP address 192.168.0.2/24)
Procedure
Step 1 Configure RouterA.
# Configure the LAN side.
<Huawei> system-view
[Huawei] sysname RouterA
[RouterA] interface ethernet 4/0/0
# After the configuration is complete, RouterA can ping the remote IP address
192.168.0.2/24.
[RouterA] ping 192.168.0.2
PING 192.168.0.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.0.2: bytes=56 Sequence=1 ttl=255 time=2 ms
Reply from 192.168.0.2: bytes=56 Sequence=2 ttl=255 time=1 ms
Reply from 192.168.0.2: bytes=56 Sequence=3 ttl=255 time=1 ms
Reply from 192.168.0.2: bytes=56 Sequence=4 ttl=255 time=1 ms
Reply from 192.168.0.2: bytes=56 Sequence=5 ttl=255 time=1 ms
--- 192.168.0.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/1/2 ms
----End
Configuration Files
● Configuration file of RouterA
#
sysname RouterA
#
interface Atm1/0/0
ip address 192.168.0.1 255.255.255.0
pvc ipoa 0/35
map ip 192.168.0.2
#
interface Ethernet4/0/0
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 200
#
vlan batch 200
#
interface Vlanif200
ip address 10.0.0.1 255.255.255.0
#
return
Networking Requirements
IP over Ethernet over ATM (IPoEoA) is a triple-layer protocol. In IPoEoA
application, IP packets are encapsulated in Ethernet frames, and Ethernet frames
are encapsulated in ATM cells.
ATM1/0/0
VE 0/0/2
Internet
Ethernet4/0/0 RouterA
DSLAM
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the LAN side so that users on the enterprise network can connect
to RouterA through the Layer 2 Ethernet interface.
2. Configure the WAN side so that RouterA can use the ADSL interface to
communicate with the DSLAM.
Data Preparation
To complete the configuration, you need the following data:
Procedure
Step 1 Configure RouterA.
# Configure the LAN side.
<Huawei> system-view
[Huawei] sysname RouterA
[RouterA] interface ethernet 4/0/0
[RouterA-Ethernet4/0/0] port link-type trunk
[RouterA-Ethernet4/0/0] port trunk allow-pass vlan 200
[RouterA-Ethernet4/0/0] undo port trunk allow-pass vlan 1
[RouterA-Ethernet4/0/0] quit
[RouterA] vlan 200
[RouterA-vlan200] quit
[RouterA] interface vlanif 200
[RouterA-Vlanif200] ip address 10.0.0.1 255.255.255.0
[RouterA-Vlanif200] quit
----End
Configuration Files
● Configuration file of RouterA
#
sysname RouterA
#
interface Virtual-Ethernet0/0/2
ip address 1.1.0.1 255.255.255.0
#
interface Atm1/0/0
pvc ipoeoa 25/45
map bridge Virtual-Ethernet 0/0/2
#
interface Ethernet4/0/0
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 200
#
vlan batch 200
#
interface Vlanif200
ip address 10.0.0.1 255.255.255.0
#
return
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the LAN side so that users on the enterprise network can connect
to RouterA through the Layer 3 Ethernet interface.
2. Configure the WAN side so that IP packets sent from the enterprise network
are encapsulated in PPP packets and RouterA can use the ADSL interface to
communicate with the DSLAM.
Data Preparation
To complete the configuration, you need the following data:
Procedure
Step 1 Configure RouterA.
# The following information indicates that the VT interface has been assigned the
correct IP address.
Internet Address is negotiated, 1.1.0.1/32
# Run the display virtual-access command to view the PPP negotiation status of
the virtual access interface created using the VT.
[RouterA] display virtual-access
----End
Configuration Files
● Configuration file of RouterA
#
sysname RouterA
#
interface Virtual-Template10
ppp chap user pppoa
ppp chap password cipher %^%#dX<{WvY1rRC4A]JD7!}$-)k>8<1}S951Ue+g:!_P%^%#
ip address ppp-negotiate
#
interface Atm1/0/0
pvc pppoa 35/53
map ppp Virtual-Template10
#
interface Ethernet2/0/0
ip address 10.0.0.1 255.255.255.0
#
return
the PPPoA client is automatically disconnected and then connected again when
traffic needs to be transmitted.
Configuration Roadmap
The configuration roadmap is as follows:
● Configure a dialer interface.
● Configure an ATM interface.
● Configure a static route from the local end to the PPPoA server.
Data Preparation
To complete the configuration, you need the following data:
● Dialer interface: dial rule number 10 (allowing all IP packets to pass through),
dialer interface number 1, dial user name u1, dialer access group number 10,
dialer interface IP address to be allocated by the server, CHAP user name
usera, CHAP password huawei@123 in plain text, maximum link idle time 90
seconds, and interface buffer queue length 8
● ATM interface: ATM interface number, PVC name pppoa, PVC number 2/40,
and on-demand PPPoA mapping on the PVC
● Static route: destination address 1.1.0.2, 24-bit mask length, and outbound
interface Dialer 1
Procedure
Step 1 Configure RouterA.
# Configure a dialer interface.
<Huawei> system-view
[Huawei] sysname RouterA
[RouterA] dialer-rule
[RouterA-dialer-rule] dialer-rule 10 ip permit
[RouterA-dialer-rule] quit
[RouterA] interface dialer 1
# Configure a static route from the local end to the PPPoA server.
[RouterA] ip route-static 0.0.0.0 0 dialer 1
# The following information indicates that the dialer interface has been assigned a
correct IP address.
Internet Address is negotiated, 1.1.0.1/32
----End
Configuration Files
● Configuration file of RouterA
#
sysname RouterA
#
dialer-rule
dialer-rule 10 ip permit
#
interface Dialer1
link-protocol ppp
ppp chap user usera
ppp chap password cipher %^%#dX<{WvY1rRC4A]JD7!}$-)k>8<1}S951Ue+g:!_P%^%#
ip address ppp-negotiate
dialer user u1
dialer bundle 12
dialer timer idle 90
dialer queue-length 8
dialer-group 10
#
interface Atm1/0/0
pvc pppoa 2/40
map ppp Dialer1
#
ip route-static 0.0.0.0 0.0.0.0 Dialer1
#
return
ATM1/0/0
Internet
RouterA PPPoEoA
DSLAM
Server
Configuration Roadmap
The configuration roadmap is as follows:
● Configure a dialer interface.
● Configure a VE interface.
● Configure an ATM interface and configure PPPoEoA mapping on the ATM
interface.
● Configure a static route from the local end to the PPPoEoA server.
Data Preparation
To complete the configuration, you need the following data:
● Dialer interface: interface number, IP address, dialer ACL number, and dialer
group number
● VE interface: interface number and dialer bundle number
● ATM interface: PVC name, PVC number, and PPPoEoA mapping on the PVC
● Static route: destination address, mask, and outbound interface
Procedure
Step 1 Configure RouterA.
# Configure a VE interface.
[RouterA] interface virtual-ethernet 0/0/0
[RouterA-Virtual-Ethernet0/0/0] pppoe-client dial-bundle-number 12
[RouterA-Virtual-Ethernet0/0/0] quit
# Run the display interface dialer command to check whether the dialer
interface on RouterA has been assigned the correct IP address.
[RouterA] display interface dialer 1
# The following information indicates that the dialer interface has been assigned
the correct IP address.
Internet Address is negotiated, 10.0.0.1/32
# Run the display virtual-access command to view the PPP negotiation status of
the virtual access interface created using the dialer interface.
[RouterA] display virtual-access
----End
Configuration Files
● Configuration file of RouterA
#
sysname RouterA
#
dialer-rule
dialer-rule 10 ip permit
#
interface Dialer1
link-protocol ppp
ppp chap user usera
ppp chap password cipher %@%@|[~(wMqA(@*[r$246i%@%@
dialer user u1
dialer-group 10
dialer bundle 12
ip address ppp-negotiate
#
interface Virtual-Ethernet0/0/0
pppoe-client dial-bundle-number 12
#
interface Atm1/0/0
pvc pppoeoa 2/45
map bridge Virtual-Ethernet0/0/0
#
ip route-static 0.0.0.0 0.0.0.0 Dialer1
#
return
VLAN 20 VLAN 30
Configuration Roadmap
The configuration roadmap is as follows:
● Configure the device to add VLAN IDs to PPPoE packets so that users in VLAN
30 can access the Internet using dialing.
● Configure CHAP authentication on RouterB to authenticate clients.
Procedure
Step 1 Configure RouterA.
# Configure a dialer interface.
<Huawei> system-view
[Huawei] sysname RouterA
[RouterA] dialer-rule
[RouterA-dialer-rule] dialer-rule 10 ip permit
[RouterA-dialer-rule] quit
# Configure a VE sub-interface.
[RouterA] interface virtual-ethernet 0/0/0
[RouterA-Virtual-Ethernet0/0/0] quit
[RouterA] interface virtual-ethernet 0/0/0.1
[RouterA-Virtual-Ethernet0/0/0.1] pppoe-client dial-bundle-number 12
[RouterA-Virtual-Ethernet0/0/0.1] dot1q termination vid 30
[RouterA-Virtual-Ethernet0/0/0.1] quit
# Configure RouterB to remove original tags from packets passing through the
DSLAM and add outer VLAN 60 to the packets.
[RouterB] interface gigabitethernet 1/0/0.1
[RouterB-GigabitEthernet1/0/0.1] pppoe-server bind virtual-template 1
[RouterB-GigabitEthernet1/0/0.1] dot1q termination vid 60
[RouterB-GigabitEthernet1/0/0.1] quit
# Configure RouterB to remove original tags from packets passing through the
DSLAM.
[RouterB] interface gigabitethernet 1/0/0
[RouterB-GigabitEthernet1/0/0] pppoe-server bind virtual-template 1
[RouterB-GigabitEthernet1/0/0] quit
# Run the display interface dialer command to check whether the dialer
interface on RouterA has been assigned a correct IP address.
[RouterA] display interface dialer 1
# The following information indicates that the dialer interface has been assigned a
correct IP address.
Internet Address is negotiated, 192.168.10.254/32
# Run the display virtual-access command to view the PPP negotiation status of
the virtual access interface created on the dialer interface.
[RouterA] display virtual-access
----End
Configuration Files
● Configuration file of RouterA
#
sysname RouterA
#
dialer-rule
dialer-rule 10 ip permit
#
interface Dialer1
link-protocol ppp
ppp chap user user1@system
ppp chap password cipher %#%#9T`|L}K(4#J3k=+I8SiJrsM:RO[iy@Uuc:LTQJ,1%#%#
dialer user u1
dialer-group 10
dialer bundle 12
ip address ppp-negotiate
#
interface Virtual-Ethernet0/0/0.1
pppoe-client dial-bundle-number 12
dot1q termination vid 30
#
interface Atm1/0/0
pvc pppoeoa 2/45
map bridge Virtual-Ethernet0/0/0
#
ip route-static 0.0.0.0 0.0.0.0 Dialer1
#
return
The following is the configuration file of RouterB that adds outer Tag 60 to packets passing
through the DSLAM.
#
sysname RouterB
#
ip pool pool1
gateway-list 192.168.10.1
network 192.168.10.0 mask 255.255.255.0
#
aaa
authentication-scheme system_a
domain system
authentication-scheme system_a
local-user user1@system password cipher %#%#hH{3Ec<[%8A>Yq=g@T:=p)jt+~LXt%g/kr<>r(~.%#
%#
local-user user1@system privilege level 0
local-user user1@system service-type ppp
#
interface Virtual-Template1
ppp authentication-mode chap domain system
remote address pool pool1
ip address 192.168.10.1 255.255.255.0
#
interface GigabitEthernet1/0/0.1
pppoe-server bind Virtual-Template 1
qinq termination pe-vid 60 ce-vid 30
#
return