Professional Documents
Culture Documents
V200R002C00
02
Date
2012-03-30
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2012-03-30)
Commissioning engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
CAUTION
Issue 02 (2012-03-30)
TIP
NOTE
ii
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... }*
[ x | y | ... ]*
&<1-n>
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Issue 02 (2012-03-30)
iii
Issue 02 (2012-03-30)
iv
Contents
Contents
About This Document.....................................................................................................................ii
1 Interface Overview........................................................................................................................1
1.1 Interface Types...................................................................................................................................................2
1.2 Interface Numbering...........................................................................................................................................4
Contents
vi
Contents
Issue 02 (2012-03-30)
vii
1 Interface Overview
Interface Overview
Issue 02 (2012-03-30)
1 Interface Overview
Physical Interfaces
Physical interfaces exist on boards.
Physical interfaces are classified into the following types:
l
LAN-side interface: is used by the router to exchange data with network devices on LANs.
WAN-side interface: is used by the router to exchange data with devices on external
networks.
Sub-type
Description
FE interface
Asymmetric Digital
Subscriber Line (ADSL)
interface
WAN-side
interface
NOTE
Only the AR157 AR206, AR207, AR207V, and
AR207V-P support ADSL interfaces.
Issue 02 (2012-03-30)
Type
1 Interface Overview
Sub-type
Description
Voice Interfaces
Logical Interfaces
Logical interfaces are manually configured interfaces and can be used to exchange data but do
not exist physically.
Table 1-2 Logical interface types
Type
Sub-type
Description
LAN-side
interface
LAN-side Eth-Trunk
interface
WAN-side
interface
Issue 02 (2012-03-30)
Virtual template
interface
MP group interface
Dialer interface
Type
1 Interface Overview
Sub-type
Description
WAN-side Eth-Trunk
interface
Tunnel interface
VLANIF interface
Sub-interface
Loopback interface
Null interface
Bridge interface
Slot ID
The slot ID specifies the ID of the slot where a card resides.
The SRU of the AR200 is integrated with the chassis, so the slot ID is fixed as 0.
Subcard ID
The subcard ID specifies the ID of a subcard. The cards of AR routers series routers do not
support subcards. Therefore, the subcard ID of the AR routers is fixed as 0.
Issue 02 (2012-03-30)
1 Interface Overview
There are two rows of interfaces on the interface card. These interfaces are numbered
from bottom to top and left to right starting with 0.
Issue 02 (2012-03-30)
11
10
Issue 02 (2012-03-30)
Context
To maintain a large number of interfaces, you need to set interface descriptions to accurately
and rapidly recognize the interfaces.
Procedure
Step 1 Run:
system-view
Example
Run the display interface description command. If the description of the interface is displayed,
it means that the configuration succeeds. For example:
<Huawei> display interface description ethernet 2/0/0
PHY: Physical
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
(b): BFD down
(d): Dampening Suppressed
Interface
PHY
Protocol Description
Eth2/0/0
up
up
HUAWEI, AR Series, Ethernet2/0/0
Interface
Applicable Environment
To easily collect the traffic volume and rate on interfaces, you can configure the interval for
collecting traffic statistics.
You can collect traffic statistics on all interfaces or a specified interface by configuring the
interval for collecting traffic statistics in the system view or interface view.
NOTE
l The interval set in the interface view takes effect on the current interface.
l The interval set in the system view takes effect on all the interfaces that use the default interval set in
the interface view.
Pre-configuration Tasks
Before configuring the interval for collecting the traffic statistics on an interface, complete the
following task:
l
Data Preparation
To configure the interval for collecting the traffic statistics on an interface, you need the
following data.
Issue 02 (2012-03-30)
No.
Data
Context
Perform the following steps on the router to configure the global interval for collecting traffic
statistics.
Procedure
Step 1 Run:
system-view
Context
Perform the following steps on the router to configure interval for collecting traffic statistics on
an interface:
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
Prerequisites
The interval for collecting traffic statistics on an interface or the global interval has been
configured.
Procedure
l
Run the
In the system view, run the display this command to check the global interval for collecting
traffic statistics.
----End
Example
Run the display this command to view the global interval for collecting traffic statistics. Run
the display interface [ interface-type [ interface-number ] | slot slot-id ] command to view the
global interval for collecting the traffic statistics. You can see that the interval for collecting
traffic statistics on all the interfaces that previously use the default interval changes to the global
interval. If a non-default interval is configured on an interface, the interval remains unchanged.
[Huawei] display this
#
set flow-stat interval 100
#
return
<Huawei> display interface ethernet 0/0/0
Ethernet0/0/0 current state : UP
Line protocol current state : UP
Description:HUAWEI, AR Series, Ethernet0/0/0 Interface
Switch Port, PVID :
1, TPID : 8100(Hex), The Maximum Frame Length is 1628
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc01-0005
Last physical up time
: 2011-01-27 14:26:10
Last physical down time : 2011-01-27 14:26:06
Current system time: 2011-01-27 14:38:18
Port Mode: COMMON COPPER
Speed : 100, Loopback: NONE
Duplex: FULL, Negotiation: ENABLE
Mdi
: AUTO
Last 100 seconds input rate 104 bits/sec, 0 packets/sec
Last 100 seconds output rate 584 bits/sec, 0 packets/sec
Input peak rate 1104 bits/sec,Record time: 2011-01-28 16:25:35
Output peak rate 1832 bits/sec,Record time: 2011-01-28 16:26:03
Issue 02 (2012-03-30)
10
0,
0,
0,
0,
0
Giants:
Throttles:
Alignments:
Ignoreds:
0,
0,
0
2671
0
0
0
0
0
0
41054
0
0
ExcessiveCollisions:
Deferreds:
0
0
Context
Running the display interface command, you can view the current status and description of the
interface and the statistics of the received and sent packets.
Procedure
l
Run the display interface brief command in any view to check the brief information about
all the interfaces on the device, including the physical status, protocol status, and bandwidth
utilization of the interface.
Run one of the following commands in any view to check brief IP configuration of the
interface.
display ip interface brief [ interface-type [ interface-number ] ]
----End
Issue 02 (2012-03-30)
11
Context
CAUTION
Statistics cannot be restored after you clear them. So, confirm the action before you use the
command.
To clear the interface statistics collected using the NMS or the display interface command, run
the following commands in the user view to clear previous traffic statistics on the interface.
Procedure
l
----End
Issue 02 (2012-03-30)
12
Issue 02 (2012-03-30)
13
Layer 2 Ethernet interface (LAN-side Ethernet interface): works at the data link layer to
process Layer 2 protocol packets.
Layer 3 Ethernet interface (WAN-side Ethernet interface): works at the network layer to
process Layer 3 protocol packets and provide routing capabilities. A Layer 3 Ethernet
interface can be assigned an IP address.
Layer 2 Ethernet interfaces on the AR150/200 include fast Ethernet (FE) interfaces. Layer 2 FE
interfaces are electrical interfaces. Table 3-1 lists attributes of the Layer 2 Ethernet interfaces
supported by the AR150/200.
Table 3-1 Attributes of Layer 2 Ethernet interfaces
Interface
Type
Rate (Mbit/
s)
Auto-Negotiation
Non-Auto Negotiation
Full
Duplex
Half
Duplex
Full
Duplex
Half
Duplex
Ethernet
electrical
interface
10
Yes
Yes
Yes
Yes
100
Yes
Yes
Yes
Yes
Layer 3 Ethernet interfaces on the AR150/200 include fast Ethernet (FE) interfaces. Layer 3 FE
interfaces are electrical interfaces. Table 3-2 lists attributes of the Layer 3 Ethernet interfaces
supported by the AR150/200.
NOTE
By default, Ethernet0/0/0 is a Layer 2 Ethernet interface. On the AR150/200, you can use the undo
portswitch command to change the working mode of Ethernet0/0/0 from Layer 3 mode to Layer 2 mode.
Issue 02 (2012-03-30)
Interface
Type
Rate (Mbit/
s)
Auto-Negotiation
Non-Auto Negotiation
Full
Duplex
Half
Duplex
Full
Duplex
Half
Duplex
Ethernet
electrical
interface
10
Yes
Yes
Yes
Yes
100
Yes
Yes
Yes
Yes
14
NOTE
By default, an Ethernet interface works in auto-negotiation mode. The default mode is recommended. If
auto-negotiation succeeds, interfaces on both ends work at the same duplex mode and rate.
Port Group
The port group function of the AR150/200 allows you to configure multiple interfaces in a port
group at the same time. A command executed in the port group view applies to all the interfaces
in the port group.
Auto-Negotiation
The auto-negotiation function allows interfaces on both ends of a link to select the same operating
parameters by exchanging information. In auto-negotiation mode, interfaces negotiate their
operating parameters, including the duplex mode, rate, and flow control. If the negotiation
succeeds, the two interfaces use the same operating parameters.
Port Isolation
The simplest method of isolating interfaces on the AR150/200 is to add different interfaces to
different VLANs, but this wastes VLAN resources. The port isolation function allows you to
add interfaces to a port isolation group so that these interfaces can be isolated from each other.
Therefore, this function helps implement secure and flexible networking schemes.
NOTE
Applicable Environment
The configuration task is required in the following cases:
Issue 02 (2012-03-30)
15
You can configure the description for an Ethernet interface to facilitate identification,
maintenance, and configuration of the interface.
By default, an Ethernet interface automatically identifies the network cable type. If the
interface cannot identify the cable type, set the cable type manually.
You can configure the auto-negotiation mode, duplex mode, rate, and bandwidth utilization
parameters on an interface.
NOTE
All parameters in this section have default values, and these default values are recommended.
Pre-configuration Tasks
Before configuring attributes for an Ethernet interface, complete the following task:
l
Data Preparation
To configure attributes for an Ethernet interface, you need the following data.
No.
Data
Context
To perform the same configurations on multiple interfaces, add these interfaces to a port group.
In the port group view, you only need to run configuration commands one time, and the
configurations apply to all the interfaces in the port group. This reduces the configuration
workload.
Procedure
l
Run:
system-view
Run:
port-group port-group-name
A permanent port group is created and the port group view is displayed.
3.
Run:
group-member { interface-type interface-number1 [ to interface-type
interface-number2 ] } &<1-5>
16
1.
Run:
system-view
Run:
port-group group-member { interface-type interface-number1 [ to interfacetype interface-number2 ] } &<1-5>
A temporary port group is created and the port group view is displayed.
----End
Run the display port-group all command to check the configurations of all port groups.
<Huawei> display port-group all
Portgroup: group1
Ethernet0/0/0
Ethernet0/0/1
Context
In auto-negotiation mode, interfaces negotiate their operating parameters, including the duplex
mode, rate, and flow control. If the negotiation succeeds, the two interfaces use the same
operating parameters. In non-auto negotiation mode, the operating parameters must be set
manually.
Procedure
Step 1 Run:
system-view
17
NOTE
Interfaces on both ends of a link must work in the same negotiation mode.
----End
Context
An Ethernet interface works in either half duplex or full duplex mode:
l
In half duplex mode, an Ethernet interface only receives or sends data at a time, and the
transmission distance is limited.
In full duplex mode, an Ethernet interface can receive and send data at the same time, and
the maximum throughput is double that in half duplex mode. There is no limit on the
maximum transmission distance.
You can set the duplex mode for an interface in either auto-negotiation or non-auto negotiation
mode.
l
In auto-negotiation mode, interfaces on both ends of a link negotiate their duplex mode. If
the negotiated duplex mode is not the required mode, you can set the duplex mode for the
two interfaces. For example, two interfaces negotiate to work in half duplex mode, but they
are required to work in full duplex mode (they both support full duplex), run the auto
duplex full command to set the full duplex mode for the two interfaces.
In non-auto negotiation mode, you can set the required duplex mode for interfaces.
Procedure
1.
Run:
system-view
Run:
interface { ethernet | gigabitethernet } interface-number
Run:
auto duplex { full | half }*
Run:
system-view
Run:
interface { ethernet | gigabitethernet } interface-number
Issue 02 (2012-03-30)
18
Run:
undo negotiation auto
Run:
duplex { full | half }
Context
In auto-negotiation mode, interfaces on both ends of a link negotiate their rate. If the negotiated
rate is not the required rate, you can set the auto-negotiation rate range to limit the negotiated
rate. For example, if two interfaces negotiate to work at a rate of 10 Mbit/s, but they are required
to work at a rate of 100 Mbit/s, you can run the auto speed 100 command to set the rate of the
interfaces to 100 Mbit/s.
In non-auto negotiation mode, you must set the rate for interfaces so that devices of the interfaces
can communicate.
Procedure
l
Run:
system-view
Run:
interface { ethernet | gigabitethernet } interface-number
Run:
auto speed { 10 | 100 }*
The auto-negotiation rate range is set for the Ethernet interface.
By default, Ethernet interfaces on both ends can negotiate to any rate supported by
them. The rate of an FE interface cannot be set to 1000 Mbit/s.
Run:
system-view
Run:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
19
Run:
undo negotiation auto
Run:
speed { 10 | 100 }
Procedure
Step 1 Run:
system-view
The outbound and inbound bandwidth utilization alarm function is enabled on all Ethernet
interfaces.
Step 3 Run:
interface { ethernet | gigabitethernet } interface-number
The threshold of the outbound or inbound bandwidth utilization is configured on the Ethernet
interface.
By default, the threshold of the outbound and inbound bandwidth utilization is 100%.
----End
20
Procedure
Step 1 Run:
system-view
----End
Prerequisites
The configurations of Ethernet interface parameters are complete.
Procedure
Step 1 Run the display interface [ interface-type [ interface-number ] ] command to check the
configuration of an Ethernet interface.
----End
Example
Run the display interface [ interface-type [ interface-number ] ] command, and you can check
whether the configuration of the Ethernet interface is correct.
<Huawei> display interface ethernet 2/0/0
Ethernet2/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2010-09-08 22:27:47
Description:HUAWEI, AR Series, Ethernet2/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 151.1.1.2/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc01-0ae3
Last physical up time
: 2010-09-08 22:27:47
Last physical down time : 2010-09-08 22:22:56
Current system time: 2010-09-09 14:34:29
Port Mode: COMMON COPPER
Speed : 100, Loopback: NONE
Duplex: FULL, Negotiation: ENABLE
Mdi
: AUTO
Last 300 seconds input rate 19184 bits/sec, 36 packets/sec
Last 300 seconds output rate 1640 bits/sec, 3 packets/sec
Issue 02 (2012-03-30)
21
Input peak rate 0 bits/sec,Record time: Output peak rate 0 bits/sec,Record time: Input: 6771660 packets, 447253294 bytes
Unicast:
0, Multicast:
Broadcast:
0, Jumbo:
Discard:
0, Total Error:
CRC:
Jabbers:
Runts:
Alignments:
Ignoreds:
0,
0,
0,
0,
0,
Giants:
Throttles:
DropEvents:
Symbols:
Frames:
0,
0,
0
ExcessiveCollisions:
Deferreds:
0
0
0
0
0
0
0
0
0
0
0
0
0
Applicable Environment
The AR150/200 provides two types of Ethernet interfaces: Layer 2 Ethernet interface and Layer
3 Ethernet interface. A Layer 2 Ethernet interface works at the data link layer, processes Layer
2 protocol packets, and implements Layer 2 forwarding.
NOTE
For details about other configurations on the Layer 2 Ethernet interface, see 3.3 Configuring General Attributes
of Ethernet Interfaces.
Traffic control can be configured to prevent packet loss caused by network congestion.
Pre-configuration Tasks
Before setting parameters for a Layer 2 Ethernet interface, complete the following tasks:
Issue 02 (2012-03-30)
22
Data Preparation
To set parameters for a Layer 2 Ethernet interface, you need the following data.
No.
Data
Applicable Environment
Table 3-3 shows the port isolation methods and application scenarios.
Table 3-3 Port isolation methods and application scenarios
Port
Isolation
Method
Application Scenario
Configure
unidirectio
nal
isolation
on
interfaces
Configure
a port
isolation
group
l Interfaces in a port isolation group are isolated from each other, but interfaces
in different port isolation groups can communicate. To isolate interfaces in
different port isolation groups, configure unidirectional isolation between
these interfaces.
Pre-configuration Tasks
Before configuring port isolation, complete the following task:
l
Creating a VLAN
Procedure
Issue 02 (2012-03-30)
23
1.
Run:
system-view
Run:
am isolate { interface-type interface-number } & <1-8>
If interface A is isolated from interface B unidirectionally, packets sent from interface A cannot
reach interface B, but packets sent from interface B can reach interface A.
Run:
system-view
Run:
interface { ethernet | gigabitethernet } interface-number
Run:
port-isolate enable [ group group-id ]
Interfaces in a port isolation group are isolated from each other, but interfaces in different port
isolation groups can communicate. If group-id is not specified, interfaces are added to port
isolation group 1.
----End
Context
Network congestion causes packet loss. Flow control is a method of avoiding packet loss. After
flow control is enabled on an interface, the interface sends a data frame to inform its remote
interface when the received traffic rate reaches or exceeds its capacity. If the remote interface
also supports flow control, it then sends data at a lower rate to prevent packet loss.
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
24
Prerequisites
The configurations of Ethernet interface parameters are complete.
Procedure
Step 1 Run the display interface [ interface-type [ interface-number ] ] command to check the
configuration of an Ethernet interface.
----End
Example
Run the display interface [ interface-type [ interface-number ] ] command to check the
configuration of an Ethernet interface.
<Huawei> display interface ethernet 0/0/0
Ethernet0/0/0 current state : UP
Line protocol current state : UP
Description:HUAWEI, AR Series, Ethernet0/0/0 Interface
Switch Port, PVID :
1, TPID : 8100(Hex), The Maximum Frame Length is 1628
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0018-2000-0083
Last physical up time
: 2010-07-21 15:35:37
Last physical down time : 2010-07-20 01:06:25
Current system time: 2010-07-21 16:07:53-05:13
Port Mode: COMMON COPPER
Speed : 100, Loopback: NONE
Duplex: FULL, Negotiation: ENABLE
Mdi
: AUTO
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Input peak rate 0 bits/sec,Record time: Output peak rate 0 bits/sec,Record time: Input: 126 packets, 34204 bytes
Unicast:
0, Multicast:
Broadcast:
74, Jumbo:
Discard:
0, Total Error:
CRC:
Jabbers:
Runts:
Issue 02 (2012-03-30)
0,
0,
0,
Giants:
Throttles:
Alignments:
52
0
0
0
0
0
25
Ignoreds:
0,
0,
0
ExcessiveCollisions:
Deferreds:
1461
0
0
0
0
Context
CAUTION
Performing loopback detection affects system performance. After loopback detection is
performed, run the undo loopback command immediately to disable loopback detection.
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
26
The interface status is checked. If the current interface status is Up, the internal forwarding
function works properly; otherwise, a fault occurs during internal forwarding.
----End
Procedure
Step 1 Run:
system-view
Networking Requirements
As shown in Figure 3-1, PC1, PC2, and PC3 connect to Ethernet0/0/0, Ethernet0/0/1, and
Ethernet0/0/2 of RouterA and access the Internet by using an uplink.
PC1, PC2, and PC3 work at a rate of 100 Mbit/s, and Ethernet0/0/3 connecting RouterA and the
Internet also works at a rate of 100 Mbit/s. If the auto-negotiation rate range is not specified, the
rate negotiated between the interfaces (Ethernet0/0/0, Ethernet0/0/1, and Ethernet0/0/2) and the
PCs (PC1, PC2, and PC3) is 100 Mbit/s. This may cause congestion on outbound interface
Ethernet0/0/3.
Issue 02 (2012-03-30)
27
IP Network
Router
Ethernet0/0/3
RouterA
PC1
Ethernet0/0/1
Ethernet0/0/0
PC2
Ethernet0/0/2
PC3
Configuration Roadmap
In auto-negotiation mode, Ethernet interfaces on both ends of a link negotiate their rate. The
negotiated rate may be any rate supported by Ethernet interfaces. By setting the auto-negotiation
rate range, you can configure Ethernet interfaces to negotiate their rate within the specified range.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Configure the auto-negotiation mode.
# Configure auto-negotiation on Ethernet0/0/0.
<Huawei> system-view
[Huawei] sysname RouterA
[RouterA] interface ethernet 0/0/0
[RouterA-Ethernet0/0/0] negotiation auto
[RouterA-Ethernet0/0/0] quit
28
----End
Configuration Files
Configuration file of RouterA
#
sysname RouterA
#
interface Ethernet0/0/0
auto speed 10
#
interface Ethernet0/0/1
auto speed 10
#
interface Ethernet0/0/2
auto speed 10
#
return
Networking Requirements
As shown in Figure 3-2, PC1, PC2, and PC3 belong to VLAN 10 and are connected to
Ethernet0/0/0, Ethernet0/0/1, and Ethernet0/0/2 on the Router.
The requirements are as follows: PC1 and PC2 cannot communicate with each other but they
can communicate with PC3.
Issue 02 (2012-03-30)
29
Router
PC1
Ethernet0/0/1
Ethernet0/0/0
Ethernet0/0/2
PC2
PC3
VLAN 10
Configuration Roadmap
Add interfaces to a port isolation group to implement Layer 2 isolation between these interfaces.
Data Preparation
To complete the configuration, you need the following data:
l
Port isolation group that the interfaces connected to PC1 and PC2 belong to
Procedure
Step 1 Configure port isolation.
# Configure port isolation on Ethernet0/0/0.
<Router> system-view
[Router] interface ethernet 0/0/0
[Router-Ethernet0/0/0] port-isolate enable
[Router-Ethernet0/0/0] quit
30
Configuration Files
The following lists only the configuration file of the Router.
#
sysname Router
#
interface Ethernet0/0/0
port link-type access
port default vlan 10
port-isolate enable group 1
#
interface Ethernet0/0/1
port link-type access
port default vlan 10
port-isolate enable group 1
#
interface Ethernet0/0/2
port link-type access
port default vlan 10
#
return
Issue 02 (2012-03-30)
31
Issue 02 (2012-03-30)
32
Background
Depending on transmission media, network access modes include wired access, wireless access,
and combination of wired and wireless access. Wired access includes twisted pair access, fiber
access, and access by using both twisted pairs and fibers. Traditional copper twisted pairs are
widely used for access, so ADSL becomes the most competitive access mode.
ADSL uses the frequency division multiplexing (FDM) technology to classify telephone lines
into regular telephone lines, upstream channels, and downstream channels, avoiding
interference. ADSL can provide channelized data services (including E1/Tl, FR, IP, and ATM
services) and transmit data, voice, and video signals at a high rate.
ADSL Evolution
The first ADSL standards (G.992.1 G.DMT and G.992.2 G.Lite) supported the upstream
transmission rate of 640 kbit/s to 2 Mbit/s, downstream transmission rate of 1 Mbit/s to 8 Mbit/
s, and transmission distance of 3 to 5 km. Since the release of ADSL in June 1999, the ITU has
been improving the ADSL transmission performance, anti-attenuation and anti-interference
capabilities, line diagnosis, and operation maintenance. In 2002, the ITU released ADSL2, which
comprises two new ADSL standards (G.992.3 and G.992.4). In 2003, the ITU defined G.992.5,
which is referred to as ADSL2+.
Compared with the first ADSL technology, ADSL2/2+ has the following advantages:
1.
ADSL2 improves performance in long-distance transmission, anti-attenuation, and antinoise. ADSL2 also improves the frame structure, so it can provide a maximum of 1 Mbit/
s upstream transmission rate and 12 Mbit/s downstream transmission rate. Expanding the
frequency spectrum used, ADSL2+ greatly improves transmission performance and
provides a maximum rate of 1 Mbit/s upstream and 24 Mbit/s downstream.
2.
3.
ADSL2/2+ saves energy. The first ADSL technology provides the same transmission rate
regardless of whether data is being transmitted. ADSL2/2+ enables a transmitter to enter
the sleep state when the data transmission rate is low or no data is being transmitted,
reducing power consumption and heat dissipation.
ADSL System
As shown in Figure 4-1, an ADSL system consists of a Digital Subscriber Line Access
Multiplexer (DSLAM) and Customer Premises Equipment (CPE).
l
Issue 02 (2012-03-30)
A DSLAM is an aggregation device that terminates ADSL packets on the central office.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
33
A CPE provides interfaces for users, modulates and demodulates data signals, and uploads
user data to a DSLAM.
NOTE
In the ADSL system, downstream transmission refers to data transmission from a DSLAM to a
CPE, and upstream transmission refers to data transmission from a CPE to a DSLAM. ADSL
interfaces on the AR150/200 are upstream interfaces.
Figure 4-1 ADSL system
Only the AR206, AR207, AR207V, and AR207V-P support ADSL interfaces.
Interface Activation
Activation of a G.SHDSL interface refers to the training between a DSLAM and a CPE. During
the training, the two devices check the line distance and status and negotiate parameters such as
the transmission standard, upstream and downstream line rates, and specified noise margin. If
the training succeeds, the G.SHDSL interface on the CPE is activated and can transmit data.
After an AR150/200 starts, its G.SHDSL interface is automatically activated. The G.SHDSL
interface remains activated as long as its G.SHDSL line works properly. To set line parameters,
deactivate the G.SHDSL interface on the CPE. After setting parameters, activate the interface
to make configurations take effect.
Issue 02 (2012-03-30)
34
Transmission Standard
Parameters for an ADSL interface include the transmission standard, bit exchange status,
seamless rate adaptation status, and trellis coding status.
Transmission Standard
Table 4-1 lists the transmission standards supported by the AR150/200.
The AR150/200 functions as a CPE and must be configured with the same transmission standard
as the DSLAM. It is recommended that you configure the AR150/200 to automatically adapt to
the transmission standard of the DSLAM.
Table 4-1 Transmission standards supported by the AR150/200
Transmission Standard
Description
G.DMT (G992.1)
ADSL2 (G992.3)
AnnexL
ADSL2+ (G992.5)
AnnexM
T1.413
Issue 02 (2012-03-30)
35
NOTE
The performance of an ADSL interface depends on external factors, such as DSLAM line card types, DSLAM
software version, line noise, line length, and temperature.
Bit Exchange
During line activation, every sub-channel calculates the signal-to-noise ratio (SNR) and the
number of bits to be transmitted. After the line is activated, the SNR may change because the
external environment changes. For example, the SNRs of some sub-channels decrease, whereas
the SNRs of others increase. After a long period of time, the line may disconnect.
The bit exchange function addresses this issue in the following ways:
l
Allows sub-channels with low SNRs switch some bits that they cannot transmit to subchannels with higher SNRs.
Reduces the transmit power of sub-channels with higher SNRs to increase the sending rate
and SNRs of sub-channels with lower SNRs.
These measures reduce the bit error rate without triggering line negotiation.
36
Applicable Environment
Parameters for an ADSL interface include the transmission standard, bit exchange status,
seamless rate adaptation status, and trellis coding status. The AR150/200 must be configured
with the same transmission standard as the DSLAM; otherwise, the ADSL interface on the
AR150/200 cannot be activated. Bit exchange, seamless rate adaptation and trellis coding take
effect only when they are enabled on both the AR150/200 and DSLAM.
Pre-configuration Tasks
Before setting parameters for an ADSL interface, complete the following task:
l
Installing an ADSL-A/M or ADSL-B interface card on the AR150/200 and ensuring that
it is registered successfully
Data Preparation
To set parameters for an ADSL interface, you need the following data.
No.
Data
Prerequisites
None.
Context
Deactivating an ADSL interface disconnects it from a DSLAM. To enable the ADSL interface
to transmit services, reactivate the interface.
NOTE
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
37
Prerequisites
The ADSL interface has been deactivated.
Context
Parameters for an ADSL interface include the transmission standard, bit exchange status,
seamless rate adaptation status, and trellis coding status.
Procedure
Step 1 Run:
system-view
The AnnexM standard is enabled on the AR150/200 by default. You can use the AnnexM standard to activate
the ADSL interface on the AR150/200 only when the AnnexM standard is also enabled on the DSLAM.
Step 4 Run:
adsl bitswap { off | on }
38
Prerequisites
Parameters have been set for an ADSL interface.
Context
Activation of an ADSL interface refers to the training between a DSLAM and a CPE. During
the training, the two devices check the line distance and status and negotiate parameters such as
the transmission standard, upstream and downstream line rates, and specified noise margin. If
the training succeeds, the ADSL interface on the CPE is activated and can transmit data.
After an AR150/200 starts, its ADSL interface is automatically activated. The ADSL interface
remains activated as long as the ADSL line works properly. To set line parameters, deactivate
the ADSL interface on the CPE. After setting parameters, activate the interface to make
configurations take effect.
Procedure
Step 1 Run:
system-view
39
Prerequisites
All the configurations of the ADSL interface are complete.
Procedure
l
Run the display dsl interface atm interface-number command to check the information
about an ADSL interface.
Run the display interface atm [ interface-number ] command to check the configuration
and status of an ADSL interface.
----End
Example
Run the display dsl interface atm interface-number command on the AR150/200, you can
check the training status, transmission standard, line status, performance statistics, bit exchange
status, seamless rate adaptation status, trellis coding status, and board version of the ADSL
interface.
<Huawei> display dsl interface atm 1/0/0
-------------------------------------------------------------DSL driver and PHY status
Training Status
: Showtime
Transmission mode
: ADSL2
Line Status
: No Defect
Downstream max. attainable rate(Kbps): 28184
Upstream max. attainable rate(Kbps) : 2529
Downstream actual net data rate(Kbps): 24538
Upstream actual net data rate(Kbps) : 1021
Downstream SNR margin(dB)
: 13.1
Upstream SNR margin(dB)
: 18.9
Downstream attenuation(dB)
: 0.0
Upstream attenuation(dB)
: 4.8
Downstream output power(dB)
: 7.2
Upstream output power(dB)
: -8.3
Downstream total cells
: 3305378
Upstream total cells
: 74443
Downstream data cells
: 36545
Upstream data cells
: 5447
Downstream bit errors
: 124
Upstream bit errors
: 365
Total drop cells
: 241
Downstream total ES count
: 0
Upstream total ES count
: 0
Downstream total SES count
: 0
Upstream total SES count
: 0
Downstream total UAS count
: 72
Upstream total UAS count
: 72
Total AS count
: 36
Line modulations
G.Dmt
ADSL2
T1.413
ADSL2+
Enabled
Issue 02 (2012-03-30)
: Disabled
: Disabled
: Disabled
:
40
Line capability
Bitswap
SRA
Trellis coding
: On
: Off
: On
Board version
Board ID:
: 963281TAN
Software version
: 4.06L.03
Bootloader (CFE) version
: 1.0.37-106.24
DSL PHY and driver version
: A2pD033a.d23c
Build timestamp
: 20110221_2122
--------------------------------------------------------------
Run the display interface atm [ interface-number ] command on the AR150/200. The status of
and performance statistics about the ADSL interface are displayed.
<Huawei> display interface atm 1/0/0
Atm1/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2011-7-27 14:57:48
Description:HUAWEI, AR Series, Atm1/0/0 Interface
Route Port,The Maximum Transmit Unit is 1488
Internet Address is 20.161.163.2/24
AAL enabled: AAL5, Maximum VCs: 32
VCs on main-interface: 1 (Total VCs: 1)
VPs on main-interface: 0 (Total VPs: 0)
Last physical up time
: 2010-06-21
14:56:32
Last physical down time : 2010-06-21 14:56:31
Current system time: 2011-08-01 15:42:04
Port PHY type
: ADSL
The physical uptimes since the system startup : 2
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Input correct packet:
OAM Cells:
Packet Errors:
0,
0 bytes
ASM Cells:
0
0
0
0%
0%
Networking Requirements
As shown in Figure 4-2, multiple hosts in Enterprise A connect to the Interface through an
enterprise gateway (Router).
Enterprise A requires a data access solution that is easy to deploy and provides high-speed
downstream transmission to meet requirements of data and video services. To meet these service
requirements, the carrier provides an ADSL line for Enterprise A so that the Router can connect
to the DSLAM by using an ADSL interface.
Issue 02 (2012-03-30)
41
Router
DSLAM
ATM1/0/0
Internet
Enterprise A
Configuration Roadmap
The configuration roadmap is as follows:
1.
2.
3.
Data Preparation
To complete the configuration, you need the following data:
l
Procedure
Step 1 Deactivate ATM1/0/0.
<Huawei> system-view
[Huawei] sysname Router
[Router] interface atm 1/0/0
[Router-Atm1/0/0] shutdown
Step 2 Configure the transmission standard ADSL2+ for the ADSL interface.
[Router-Atm1/0/0] adsl standard adsl2+
42
: Disabled
: Disabled
: Disabled
:
Line capability
Bitswap
SRA
Trellis coding
: On
: Off
: On
Board version
Board ID:
: 963281TAN
Software version
: 4.06L.03
Bootloader (CFE) version
: 1.0.37-106.24
DSL PHY and driver version
: A2pD033a.d23c
Build timestamp
: 20110221_2122
--------------------------------------------------------------
# Check the status of and performance statistics about the ADSL interface.
<Router> display interface atm 1/0/0
Atm1/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2011-7-27 14:57:48
Description:HUAWEI, AR Series, Atm1/0/0 Interface
Route Port,The Maximum Transmit Unit is 1488
Internet Address is 20.161.163.2/24
AAL enabled: AAL5, Maximum VCs: 32
VCs on main-interface: 1 (Total VCs: 1)
VPs on main-interface: 0 (Total VPs: 0)
Last physical up time
: 2010-06-21
14:56:32
Last physical down time : 2010-06-21 14:56:31
Current system time: 2011-08-01 15:42:04
Port PHY type
Issue 02 (2012-03-30)
: ADSL
43
0,
ASM Cells:
0 bytes
0
0
0
0%
0%
----End
Configuration Files
l
Issue 02 (2012-03-30)
44
Issue 02 (2012-03-30)
45
Background
Asymmetric Digital Subscriber Line (ADSL) is the most commonly used broadband access
technology. It provides asymmetric transmit and receive data rates over copper twisted pairs and
is useful for transmitting asymmetric services such as Internet access and Video on Demand
(VoD). However, ADSL cannot meet requirements of commercial broadband applications that
require bidirectional and symmetric traffic and are sensitive to performance fluctuation. The
G.SHDSL technology solves this problem.
G.SHDSL complies with ITU Recommendation G.991.2 and provides bidirectional data
transmission with symmetric data rates over twisted pairs. It reduces the transmission spectrum,
improves the anti-noise performance, and extends the maximum transmission distance to 6 km
by using 16-trellis coded pulse amplitude modulation (TCPAM).
G.SHDSL System
As shown in Figure 5-1, a G.SHDSL system consists of a Digital Subscriber Line Access
Multiplexer (DSLAM) and Customer Premises Equipment (CPE).
l
A DSLAM is an aggregation device that terminates G.SHDSL packets on the central office.
A CPE is a user-side device that modules and demodulates user data, and transmits user
data to a DSLAM.
NOTE
In the G.SHDSL system, downstream transmission refers to data transmission from a DSLAM
to a CPE, and upstream transmission refers to data transmission from a CPE to a DSLAM.
G.SHDSL interfaces on the AR150/200 are upstream interfaces.
Figure 5-1 G.SHDSL system
Issue 02 (2012-03-30)
46
Advantages of G.SHDSL
G.SHDSL provides high-speed commercial broadband services and has the following
advantages:
l
Long transmission distance and high signal-to-noise ratio (SNR): Compared with other
DSL technologies, G.SHDSL provides a longer transmission distance for the same
transmission rate, a higher transmission rate for the same transmission distance, and a
greater SNR for the same transmission distance and rate.
WARNING
After installing the G.SHDSL cable, do not remove the G.SHDSL cable within 8 seconds.
Working Mode
An AR150/200 supports two working modes for G.SHDSL interfaces:
l
Asynchronous Transfer Mode (ATM): ATM cells are transmitted over G.SHDSL lines.
Packet Transfer Mode (PTM): Ethernet frames are transmitted over G.SHDSL lines.
Ethernet frames do not need to be fragmented into ATM cells. 1483B/1483R encapsulation,
ATM Adaptation Layer 5 (AAL5) encapsulation, and ATM cell encapsulation are not
required, enabling Ethernet services to be transmitted more rapidly than in ATM mode.
A G.SHDSL interface on the AR150/200 must work in the same mode as the G.SHDSL interface
on the DSLAM.
Issue 02 (2012-03-30)
47
Parameters
You can set the following parameters for a G.SHDSL interface on the AR150/200:
l
Transmission standard
The AR150/200 must be configured with the same transmission standard as the DSLAM.
The AR150/200 supports the following transmission standards:
G.991.2 Annex A: a North American standard useful for G.SHDSL over Plain Old
Telephone Service (POTS) and compatible with POTS services.
G.991.2 Annex B: a European standard useful for G.SHDSL over Integrated Services
Digital Network (ISDN) and compatible with ISDN services.
Interface Activation
Activation of a G.SHDSL interface refers to the training between a DSLAM and a CPE. During
the training, the two devices check the line distance and status and negotiate parameters such as
the transmission standard, upstream and downstream line rates, and specified noise margin. If
the training succeeds, the G.SHDSL interface on the CPE is activated and can transmit data.
After an AR150/200 starts, its G.SHDSL interface is automatically activated. The G.SHDSL
interface remains activated as long as its G.SHDSL line works properly. To set line parameters,
deactivate the G.SHDSL interface on the CPE. After setting parameters, activate the interface
to make configurations take effect.
Issue 02 (2012-03-30)
48
Applicable Environment
The AR150/200 supports two working modes for G.SHDSL interfaces: ATM for transmitting
ATM cells and PTM for transmitting Ethernet frames. The AR150/200 functions as a CPE. a
G.SHDSL interface on the AR150/200 must work in the same mode as the G.SHDSL interface
on the DSLAM.
Pre-configuration Tasks
Before setting the working mode for a G.SHDSL interface on the AR150/200, complete the
following tasks:
l
Procedure
Step 1 Run:
system-view
49
Applicable Environment
Parameters for a G.SHDSL interface include the interface binding mode, transmission standard,
PSD mode, and line probing function. The G.SHDSL interface must be configured with the same
parameters as the G.SHDSL interface on the DSLAM except the line probing function.
Pre-configuration Tasks
Before setting parameters for a G.SHDSL interface, complete the following tasks:
l
Data preparation
To set parameters for a G.SHDSL interface, you need the following data.
No.
Data
Context
Deactivating a G.SHDSL interface disconnecting it from the DSLAM. To enable the G.SHDSL
interface to transmit services, reactivate this G.SHDSL interface.
NOTE
Procedure
Step 1 Run:
system-view
Step 3 Run:
shutdown
50
Prerequisites
The G.SHDSL interface has been deactivated.
Context
A 4G.SHDSL board on the AR150/200 has only one physical interface. This physical interface
can be virtualized into four G.SHDSL interfaces numbered from 0 to 3.
The AR150/200 must be configured with the same interface binding mode as the DSLAM. For
example, if the DSLAM is configured with binding between interfaces 1 and 2, the
AR150/200 must also be configured with binding between interfaces 1 and 2. When binding
interfaces, the following requirements apply:
l
Only contiguous interfaces on the same 4G.SHDSL board can be bound together. The
number of the first interface to be bound must be 0 or 2. The first bound interface is the
main interface, and the remaining bound interfaces are slave interfaces.
Before binding, interfaces must be deactivated and not configured with any service.
Procedure
Step 1 Run:
system-view
Step 3 Run:
shdsl bind { efm | m-pair } link_number
l If the working mode is set to ATM, the interface binding mode must be set to M-Pair binding. After
G.SHDSL interfaces are bound together, the transmission standard, PSD mode, and line probing status
of these interfaces are restored to the default settings. To activate all the bound interfaces or set
parameters for these interfaces, activate the main interface or set parameters for the main interface.
Other bound interfaces inherit the configurations from the main interface. For example, if the main
interface is activated, other interfaces in the same binding group are also activated. When one bound
interface fails, all services are interrupted.
l If the working mode is set to PTM, the interface binding mode must be set to EFM binding. After
G.SHDSL interfaces are bound successfully, you can set different parameters for these interfaces. For
example, you can set different transmission standards for interfaces in the same binding group. When
one bound interface fails, traffic on this interface automatically switches to other bound interfaces.
Services are not interrupted if the traffic rate is smaller than the actual interface bandwidth.
----End
Issue 02 (2012-03-30)
51
Prerequisites
The G.SHDSL interface has been deactivated.
Context
The AR150/200 supports the following transmission standards:
l
G.991.2 Annex A: a North American standard useful for G.SHDSL over Plain Old
Telephone Service (POTS) and compatible with POTS services.
G.991.2 Annex B: a European standard useful for G.SHDSL over Integrated Services
Digital Network (ISDN) and compatible with ISDN services.
A G.SHDSL interface must use the same transmission standard as the remote G.SHDSL interface
on the DSLAM.
Procedure
Step 1 Run:
system-view
Step 3 Run:
shdsl annex { a | all | b }
Prerequisites
The G.SHDSL interface has been deactivated.
Context
A G.SHDSL interface supports the following PSD modes:
Issue 02 (2012-03-30)
52
Symmetric PSD: The G.SHDSL interface is spectral-compatible with other services, uses
less power, and is suitable for short-distance transmission.
Asymmetric PSD: The G.SHDSL interface uses a high output power for better transmission
performance and is suitable for long-distance transmission.
Procedure
Step 1 Run:
system-view
Step 3 Run:
shdsl psd { asymmetry | symmetry }
Prerequisites
The G.SHDSL interface has been deactivated.
Context
To enable the AR150/200 to connect to the peer device, configure the capability for the
G.SHDSL interface card based on the chip type of the peer device. When the peer device uses
the g-shdsl mode, you must configure the g-shdsl mode on the AR150/200.
NOTE
When the g-shdsl mode is configured, strictly perform the following operations. Otherwise, the g-shdsl mode
will switch to the g-shdsl.bis mode.
Procedure
l
Run:
system-view
Run:
interface atm interface-number
Issue 02 (2012-03-30)
53
Run:
shdsl capability { auto | g-shdsl.bis }
A capability is configured.
By default, an G.SHDSL interface uses the auto mode.
4.
Run:
shdsl pam { 16 | 32 | auto }
Run:
shdsl bind m-pair 2 pairs { auto-enhanced | enhanced | standard }
The shdsl bind m-pair 2 pairs command can only be configured on an interface in slot 0 or slot 2.
6.
Run:
shdsl rate miaximum miaximum
Run:
shdsl rate minimum minimum
Run:
system-view
Run:
interface atm interface-number
Run:
shdsl capability g-shdsl
A capability is configured.
4.
Run:
shdsl pam 16
Run:
shdsl bind m-pair 2 pairs enhanced
The shdsl bind m-pair 2 pairs command can only be configured on an interface in slot 0 or slot 2.
6.
Issue 02 (2012-03-30)
Run:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
54
Run:
shdsl rate minimum minimum
Prerequisites
The G.SHDSL interface has been deactivated.
Context
The AR150/200 supports the following SNR settings:
l
Uplink and downlink SNRs: When the actual SNR of the AR150/200 is greater than the
configured SNR, the AR150/200 is activated successfully.
Lowest uplink and downlink SNRs: When the actual lowest SNR of the AR150/200 is
smaller than the configured lowest SNR, the AR150/200 is disconnected.
Procedure
1.
Run:
system-view
Run:
interface atm interface-number
Run:
shdsl current target snr margin upstream value
Run:
shdsl current target snr margin downstream value
Run:
system-view
Issue 02 (2012-03-30)
55
Run:
interface atm interface-number
Run:
shdsl worst case target snr margin upstream value
Run:
shdsl worst case target snr margin downstream value
Prerequisites
The G.SHDSL interface has been deactivated.
Context
If the remote DSLAM is configured with the maximum and minimum G.SHDSL line rates, the
local G.SHDSL interface must be activated at a rate within the specified range. Enable the line
probing function on the G.SHDSL interface so that the interface can automatically select an
appropriate rate that is within the specified range.
If the remote DSLAM is configured with a fixed G.SHDSL line rate, the local G.SHDSL
interface must be activated at the fixed G.SHDSL line rate. By disabling the line probing function
on the G.SHDSL interface, enable the G.SHDSL interface to be activated at the fixed G.SHDSL
line rate.
Procedure
Step 1 Run:
system-view
Step 3 Run:
shdsl line-probing enable
56
Context
Activation of a G.SHDSL interface refers to the training between a DSLAM and a CPE. During
the training, the two devices check the line distance and status based on parameters such as the
transmission standard, upstream and downstream line rates, and specified noise margin to
determine whether they can work properly under the existing conditions. If the training succeeds,
the G.SHDSL interface on the CPE is activated and can transmit services between the two
devices.
After an AR150/200 starts, its G.SHDSL interface is automatically activated. The G.SHDSL
interface remains activated as long as the G.SHDSL line works properly. To enable a CPE to
communicate with a DSLAM, deactivate the G.SHDSL interface on the CPE, set parameters
such as the transmission standard, interface binding mode, PSD mode, and line probing function
for the interface, and then reactivate this interface to make configurations take effect.
Procedure
Step 1 Run:
system-view
Step 3 Run:
undo shutdown
l To activate G.SHDSL interfaces bound in M-Pair mode, you only need to activate the main interface
because slave interfaces will be activated together with the main interface.
l To activate G.SHDSL interfaces bound in EFM mode, activate the main and slave interfaces in
sequence.
----End
Prerequisites
All the configurations of the G.SHDSL interface are complete.
Issue 02 (2012-03-30)
57
Procedure
Step 1 Run the display dsl interface { atm | ethernet } interface-number command to check
information about the G.SHDSL interface.
NOTE
You can select the G.SHDSL interface to view according to the interface working mode (ATM or PTM).
The fields displayed in the command output are the same for G.SHDSL interfaces working in ATM or
PTM mode.
----End
Example
Run the display dsl interface { atm | ethernet } interface-number command. The command
output shows the status, parameters, vendor information, and traffic statistics of the specified
G.SHDSL interface.
<Huawei> display dsl interface atm 1/0/0
------------------------------------------------------------------Port admin status
:Active
Port running status
:Activated
Port bind status
:MPair-2
Bind group master port
:0
Port transmission mode
:G.991.2 Annex B
Port power spectral density
:Asymmetric
Port line probe
:Disable
Line Status of SHDSL port 0
Current line rate(unit:kbps)
:5704
Current transmission mode
:G.991.2 Annex B
Actual attainable payload line rate(unit:kbps) :5696
Current modulation mode
:TCPAM-32
Current PBO downstream(unit:dB)
:6.0
Current PBO upstream(unit:dB)
:0.0
Current loop attenuation downstream(unit:dB)
:0
Current loop attenuation upstream(unit:dB)
:0
Current SNR margin downstream(unit:dB)
:19
Current SNR margin upstream(unit:dB)
:0
Inventory of SHDSL port 0
Vendor ID
:Infineon
Vendor mode
:SOCRATES
Vendor serial
:4e_2e_1e
EOC version
:0
Standard version
:8
Vendor list
:Vendor issue
:1
Software code
:1.6.3
Equipment code
:Information of other vendor
:B01D01
Transmission mode capability
:G.991.2 Annex A&B
Current 15 minutes statistic of SHDSL port 0
Total seconds counted in 15 minutes
:254
ES count in 15 minutes (unit:Second)
:0
SES count in 15 minutes (unit:Second)
:0
CRC anomaly count in 15 minutes
:0
LOSW count in 15 minutes (unit:Second)
:0
UAS count in 15 minutes (unit:Second)
:254
-------------------------------------------------------------------
58
Networking Requirements
As shown in Figure 5-2, Enterprise A requires a data access solution that is easy to deploy and
provides high-speed upstream and downstream transmission for security, VPN, and video
conference services. To meet these service requirements, the carrier provides a G.SHDSL line
for Enterprise A. The enterprise gateway (Router) must connect to the DSLAM by using
G.SHDSL interfaces.
When Enterprise A requires a higher bandwidth for data transmission, the carrier can bind
multiple G.SHDSL interfaces to increase the bandwidth.
Figure 5-2 Network diagram of G.SHDSL interface configurations
Router
ATM1/0/0
ATM1/0/1
ATM1/0/2
M-Pair
ATM1/0/0
ATM1/0/1
ATM1/0/2
DSLAM
Internet
EnterpriseA
Configuration Roadmap
The configuration roadmap is as follows:
1.
Configure the same working mode as G.SHDSL interfaces on the DSLAM for G.SHDSL
interfaces on the Router.
2.
3.
Set parameters for these G.SHDSL interfaces. The parameters include the interface binding
mode, transmission standard, PSD mode, and line probing function. All the parameters
except the line probing function must be the same as those on the DSLAM. Otherwise, the
G.SHDSL interfaces cannot be activated.
4.
Data preparation
To complete the configuration, you need the following data:
l
Interface binding mode of G.SHDSL interfaces on the DSLAM: M-Pair binding with three
G.SHDSL interfaces bound together
Issue 02 (2012-03-30)
59
NOTE
In this section, the configuration of G.SHDSL interfaces working in ATM mode is used as an example.
The configuration of G.SHDSL interfaces working in PTM mode is similar except for the working mode
and interface binding mode.
Procedure
Step 1 Set the working mode for G.SHDSL interfaces on the Router to ATM.
<Huawei> system-view
[Huawei] sysname Router
[Router] set workmode slot 0 shdsl atm
Warning: All the configuration will be saved to the next startup configuration.
Continue ? [y/n]:y
It will take several minutes to save configuration file, please wait......
Configuration file had been saved successfully
Note: The configuration file will take effect after being activated
Changing the working mode will reset the board in slot 0. Continue? [y/n]:y
NOTE
# Deactivate ATM1/0/1.
[Router] interface atm 1/0/1
[Router-Atm1/0/1] shutdown
[Router-Atm1/0/1] quit
# Deactivate ATM1/0/2.
[Router] interface atm 1/0/2
[Router-Atm1/0/2] shutdown
[Router-Atm1/0/2] quit
Issue 02 (2012-03-30)
60
:286
:0
:0
:0
:0
:286
----End
Configuration Files
l
Issue 02 (2012-03-30)
61
3
shdsl annex
b
#
return
Issue 02 (2012-03-30)
62
Issue 02 (2012-03-30)
63
Eth-Trunk interface: includes Layer 2 and Layer 3 Eth-Trunk interfaces, which increase
bandwidth and improves transmission reliability.
VLANIF interface: has Layer 3 features and enables VLANs to communicate after being
assigned an IP address.
Loopback interface: used when the status of the interface needs to be always Up or the
interface needs to be configured with 32-bit subnet mask.
Null interface: used in route filtering because any network packets sent to this interface are
discarded.
MP group interface: used to perform MP binding. MP group interfaces are dedicated to the
MP application and usually used in scenarios requiring dynamic bandwidth.
Dialer interface: used to implement the Dialer Control Center (DCC) function. A physical
interface can be bound to a dialer interface to inherit the configuration of the dialer interface.
Tunnel interface: has Layer 3 features, transmits packets, and identifies and processes
packets transmitted over a tunnel.
Virtual-Template (VT) interface: used in the MP binding or when other data link layer
protocols need to be transmitted over a PPP link.
Virtual-Ethernet (VE) interface: used when other data link layer protocols need to be carried
by the Ethernet protocol.
NOTE
l For the configurations of Eth-Trunk interfaces and VLANIF interfaces, see the Huawei AR150&200
Series Enterprise Routers Configuration Guide - LAN.
l For the configurations of MP group interfaces, MFR interfaces, and dialer interfaces, see the Huawei
AR150&200 Series Enterprise Routers Configuration Guide - WAN.
l For the configuration of the tunnel interface, see the Huawei AR150&200 Series Enterprise Routers
Configuration Guide - VPN.
64
Applicable Environment
On the AR150/200, sub-interfaces can be configured on Layer 3 Ethernet interfaces.
NOTE
Pre-configuration Tasks
Before configuring an Ethernet sub-interface, complete the following tasks:
l
Data Preparation
To configure an Ethernet sub-interface, you need the following data.
No.
Data
Procedure
l
Run:
system-view
Issue 02 (2012-03-30)
65
Run:
interface { ethernet | gigabitethernet } interface-number.subinterfacenumber
----End
Procedure
Step 1 Run:
system-view
When two or more IP addresses are configured for an Ethernet interface, the keyword sub must be used to
indicate the second IP address and the following IP addresses.
----End
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
66
Context
To implement inter-VLAN communication, you can create Ethernet sub-interfaces on an
Ethernet interface and configure the sub-interfaces for dot1q VLAN termination to remove tags
from VLAN packets.
Procedure
Step 1 Run:
system-view
The mappings between the control VLAN and the Ethernet sub-interface are specified.
Step 4 Run:
dot1q termination vid vid
The allowed VLAN is configured on the Ethernet sub-interface for dot1q VLAN termination.
Step 5 Run:
arp broadcast enable
When you enable or disable the ARP broadcast function on a sub-interface, the routing status of the sub-interface
becomes Down and then Up. This may result in flapping of routes on the entire network, affecting the normal
operation of services.
----End
Issue 02 (2012-03-30)
67
Prerequisites
The configurations of an Ethernet sub-interface are complete.
Procedure
l
----End
Example
Run the display interface command. If the parameters of the Ethernet sub-interface, such as the
physical status, protocol status, MTU, IP address and mask, and interface mode, are displayed,
the configuration succeeds. For example:
<Huawei> display interface ethernet 1/0/0.1
Ethernet1/0/0.1 current state : UP
Line protocol current state : UP
Description : HUAWEI, AR Series, Ethernet1/0/0.1 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 2.1.1.100/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-3177-e201
Current system time: 2010-08-29 20:26:18
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
Realtime 81 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 81 seconds output rate 0 bits/sec, 0 packets/sec
Input: 0 packets,0 bytes,
0 unicast,0 broadcast,0 multicast
Output:1 packets,64 bytes,
0 unicast,1 broadcast,0 multicast
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
Applicable Environment
Layer 3 Eth-Trunk interfaces on the AR150/200 can be configured with sub-interfaces.
Pre-configuration Tasks
Before configuring an Eth-Trunk sub-interface, complete the following tasks:
Issue 02 (2012-03-30)
68
Data Preparation
To configure an Eth-Trunk sub-interface, you need the following data.
No.
Data
Procedure
Step 1 Run:
system-view
69
Procedure
Step 1 Run:
system-view
If two or more IP addresses are configured for an Eth-Trunk interface, the keyword sub must be used to
indicate the second IP address and the following IP addresses.
----End
Procedure
Step 1 Run:
system-view
The mappings between the control VLAN and the Eth-Trunk sub-interface are specified.
Step 4 Run:
dot1q termination vid vid
Issue 02 (2012-03-30)
70
The allowed VLAN is configured on the Eth-Trunk sub-interface for dot1q VLAN termination.
Step 5 Run:
arp broadcast enable
When you enable or disable the ARP broadcast function on a sub-interface, the routing status of the sub-interface
becomes Down and then Up. This may result in flapping of routes on the entire network, affecting the normal
operation of services.
----End
Prerequisites
The configurations of an Eth-Trunk sub-interface are complete.
Procedure
Step 1 Run the display interface eth-trunk [ trunk-id [ .subnumber ] ] command to check the status
of the Eth-Trunk sub-interface.
----End
Example
Run the display interface eth-trunk command. If information about the Eth-Trunk subinterface, including its IP address and MAC address, is displayed, it means that the configuration
succeeds. For example:
<Huawei> display interface eth-trunk 1.1
Eth-Trunk1.1 current state : UP
Line protocol current state : UP
Description : HUAWEI, AR Series, Eth-Trunk1.1 Interface
Route Port, Hash arithmetic : According to SIP-XOR-DIP, The Maximum Transmit Unit
is 1500
Internet Address is 10.10.10.100/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-3f60-ec00
Current system time: 2010-08-25 00:28:20
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 0 bytes/sec, 0 packets/sec
Realtime 77 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 77 seconds output rate 0 bits/sec, 0 packets/sec
Input: 0 packets,0 bytes,
Output:0 packets,0 bytes,
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
----------------------------------------------------PortName
Status
Weight
----------------------------------------------------Ethernet1/0/0
UP
1
----------------------------------------------------The Number of Ports in Trunk : 1
The Number of UP Ports in Trunk : 1
Issue 02 (2012-03-30)
71
Procedure
Step 1 Run:
system-view
Applicable Environment
As the loopback interface always remains in the Up state once created and executes the loopback
function, it can be used to improve connection reliability.
Loopback interfaces have the following functions:
l
The IP address of a loopback interface can be designated as the source address of packets.
The IP address of a loopback interface can be used to control the access interface and filter
logs.
If more than one link can reach the same neighbor, a loopback interface can be used as the
BGP neighbor of the local router. This avoids neighbor relationship failures caused by
interface faults when other types of interfaces are used as BGP neighbors.
Pre-configuration Tasks
Before configuring a Loopback interface, power on the router and start the router.
Issue 02 (2012-03-30)
72
Data Preparation
To configure a loopback interface, you need the following data.
No.
Data
Procedure
Step 1 Run:
system-view
Prerequisites
The configurations of a loopback interface are complete.
Procedure
Step 1 Run the display interface loopback [ loopback-number ] command to check the status of a
loopback interface.
----End
Issue 02 (2012-03-30)
73
Example
Run the display interface loopback command. The following information shows that the link
layer protocol status of the interface is Up.
<Huawei> display interface loopback 6
LoopBack6 current state : UP
Line protocol current state :UP (spoofing)
Description:HUAWEI, AR Series, LoopBack6 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 10.10.1.1/24
Physical is Loopback
Current system time: 2010-09-10 10:03:18
Statistics last cleared: 2008-08-02 15:32:27
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Realtime 6 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 6 seconds output rate 0 bits/sec, 0 packets/sec
Input: 0 bytes
Output:0 bytes
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
Applicable Environment
A Null interface is like the null devices supported by some operating systems. All packets sent
to a Null interface are dropped. The system automatically creates a Null interface NULL0.
Since all packets sent to a Null interface are dropped, you can specify a Null interface as the
outbound interface for packets to be filtered out. In this case, you do not need to configure an
ACL.
For example, using the following command discards all packets sent to the 192.101.0.0 network
segment.
[Huawei] ip route-static 192.101.0.0 255.255.0.0 NULL 0
Pre-configuration Tasks
Before configuring a Null interface, power on the router and start the router.
Data Preparation
None.
74
Procedure
Step 1 Run:
system-view
Prerequisites
The configurations of a null interface are complete.
Procedure
Step 1 Run the display interface null [ 0 ] command to check the status of a null interface.
----End
Example
Run the display interface null command. The following information shows that the status of
the null interface is Up.
<Huawei> display interface null 0
NULL0 current state : UP
Line protocol current state :UP (spoofing)
Description:HUAWEI, AR Series, NULL0 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
Physical is NULL DEV
Current system time: 2010-09-10 10:03:18
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
Input: 0 bytes
Output:0 bytes
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
75
Applicable Environment
Multiple PPP links can be bound to an MP group to increase link bandwidth. This is called MP
binding. MP fragments the packets whose length is greater than the minimum packet length and
sends the fragments to the peer device over multiple PPP links in the MP group. After receiving
these fragments, the peer device assembles these fragments and sends assembled packets to the
network layer. An MP group interface is dedicated to the MP application and used in scenarios
requiring dynamic bandwidth.
Pre-configuration Tasks
Before configuring an MP Group interface, power on the router and start the router.
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
76
Applicable Environment
Dial Control Center (DCC) allows a router to communicate by using the Integrated Service
Digital Network (ISDN) or Public Switched Telephone Network (PSTN). DCC provides ondemand dialup services. A dialer interface is a logical interface used to implement DCC. A
physical interface can be bound to a dialer interface to inherit the configuration of the dialer
interface.
Pre-configuration Tasks
Before configuring a Dialer interface, power on the router and start the router.
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
77
Applicable Environment
Virtual-Ethernet (VE) interfaces are used in PPPoEoA and IPoEoA. VE interfaces can also be
used to configure the firewall and routes.
Configuration of the VE interface is like that of the Ethernet interface. For details, refer to the
chapter LAN-Side Ethernet Interface Configuration.
VE interfaces support the following features:
l
Routing protocols
VLAN configuration
Pre-configuration Tasks
Before configuring a VE interface, power on the router and start the router.
Data Preparation
To configure a VE interface, you need the following data.
No.
Data
Procedure
Step 1 Run:
system-view
ve-number
78
After establishing a binding relationship between a VE interface and the permanent virtual channel (PVC)
that transmits PPPoEoA or IPoEoA data, you can delete this VE interface only when you unbind the VE
interface from the PVC.
----End
Prerequisites
The configurations of Virtual-Ethernet interfaces are complete.
Procedure
Step 1 Run the display interface virtual-ethernet [ ve-number ] command to check the status of a VE
interface.
----End
Example
Run the display interface virtual-ethernet command. If the configuration and status of the
specified VE interface are displayed, it means that the configuration succeeds. For example:
<Huawei> display interface Virtual-Ethernet
Virtual-Ethernet0/0/0 current state : DOWN
Line protocol current state : DOWN
Description:HUAWEI, AR Series, Virtual-Ethernet0/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc99-9999
Current system time: 2010-09-10 10:03:18
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
Virtual-Ethernet0/0/1 current state : UP
Line protocol current state : UP
Last line protocol up time: 2007-11-03, 17:24:24
Description:HUAWEI, AR Series, Virtual-Ethernet0/0/1 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 200.1.1.2/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc99-9999
Carrier Layer: 1 PVC total, 1 map up, 0 map down
Current system time: 2010-09-10 10:03:18
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 drops
5 packets output, 300 bytes, 0 drops
79
Applicable Environment
A VT interface is used in VPN, MP and ATM applications. The system creates and deletes VA
interfaces and the process is transparent to users.
The link layer of VT interfaces only supports the PPP protocol, and the network layer only
supports IP.
CAUTION
l The newly configured or modified parameters of a VT interface take effect only after the
shutdown and the undo shutdown command are run.
l After configuring or modifying services such as MPLS, MTU or IS-IS, modify VT
configuration on the interfaces with the services configured.
Pre-configuration Tasks
Before configuring a VT interface, complete the following tasks:
l
Data Preparation
To configure a VT interface, you need the following data.
No.
Data
Procedure
Step 1 Run:
system-view
Issue 02 (2012-03-30)
80
Procedure
Step 1 Run:
system-view
vt-number
number
The maximum number of links supported by the VT interface for sending multicast or broadcast
packets is configured.
Multicast or broadcast packets sent out from each link may affect system performance if there
are too many links in the VT interface.
Using the broadcast-limit link command, you can restrict the packets since the packets are
dropped when the link number exceeds the maximum number.
NOTE
Do not configure multiple services such as MP, L2TP and PPPoE on a VT.
81
Prerequisites
The configurations of VT interfaces are complete.
Procedure
l
Run the display interface virtual-template [ vt-number ] command to check the status of
a VT interface.
Run the display virtual-access [ vt vt-number | dialer dialer-interface-number | user username | peer peer-address | va-number ] * command to check the status of a VA interface.
----End
Example
Run the display interface virtual-template command. If the configuration of a VT interface is
displayed, the configuration succeeds.
<Huawei> display interface Virtual-Template 0
Virtual-Template0 current state : UP
Line protocol current state :UP (spoofing)
Description:HUAWEI, AR Series, Virtual-Template0 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 10.1.1.1/24
Link layer protocol is PPP
LCP initial, MP opened
Physical is None, baudrate is 64000 bps
Current system time: 2010-09-10 10:03:18
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
Input: 0 bytes
Output:0 bytes
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
Run the display virtual-access command. If the status of a VA interface is displayed, the
configuration succeeds. For example:
<Huawei> display virtual-access
Virtual-Template1:0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2011-10-12 14:14:32
Description:HUAWEI, AR Series, Virtual-Template1:0 Interface
Route Port,The Maximum Transmit Unit is 1480
Link layer protocol is PPP
LCP opened, IPCP opened
Current system time: 2011-10-12 14:20:22
Input bandwidth utilization :
0%
Output bandwidth utilization :
0%
Issue 02 (2012-03-30)
82