Preface
Guidelines on Learning
References
Objectives
Ethernet service
CES service
ATM/IMA service
Contents
1.
2.
3.
4.
Service Types
Ethernet service
E-Line service
E-Aggr service
Service Types
ATM/IMA service
Contents
1.
2.
Configuration Process
Configuration Tasks
3.
4.
UNI-NNI E-Line
service carried by
a PW
Set the LSR ID of an
NE
Create a
network
Configure an NNI
UNI-UNI
E-Line
service
Configure the
QoS
Configure an
interface
Configure the
QoS
Configure an
interface
Configure a QinQ
link
Source NE
Configure a tunnel
Configure the
QoS
Configure an
interface
Source NE
Configure a UNI
Source NE
Sink NE
Sink NE
End
Sink NE
Create a
network
Configure the
QoS
Configure an
interface
UNIs-UNI E-Aggr
service
Configure the UNIs-UNI EAggr service
End
End
UNIs-NNI E-Aggr
service carried by a
port
Create a tunnel
End
Creating an NE
Configuring an interface
Creating a tunnel
Creating an NE
Creating an NE
Creating an NE
Select Upload.
Creating an NE
NE Explorer is displayed.
Creating an NE
Configuring an interface
Creating a tunnel
Set the LSR ID according to the network design. On a packet switched network (PSN), each NE is
allocated with a unique LSR ID.
The Start of Global Label Space parameter indicates or specifies the start value of the global
space for labels. The value of this parameter is equal to the minimum value of the ingress and
egress labels of a unicast tunnel. This parameter ranges from 0 to 1047040.
Creating an NE
Configuring an interface
Creating a tunnel
Application Scenario
Interface Type
Ethernet interface
Ethernet interface
When a radio interface is used to carry the QinQ link, the configuration process is almost the same as the configuration process when
it is used to the carry the Ethernet service. The only difference is that a different encapsulation format should be selected.
On a radio transmission network, a UNI is generally a radio interface. Hence, it is required to configure the radio interface for all the
services on the radio equipment.
Configuring a
radio link
Setting
general
attributes
Setting IF
attributes
Setting
Layer 2
attributes
Setting
advanced
attributes
Configuring a
radio link
Setting
general
attributes
Setting IF
attributes
Setting
Layer 3
attributes
Setting
advanced
attributes
Setting
general
attributes
Setting IF
attributes
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
Configuring a
radio link
Setting IF
attributes
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
Setting
general
attributes
Setting IF
attributes
Setting
Layer
2/Layer 3
attributes
The general attributes of a radio interface, including the port mode, encapsulation type, and MTU,
define the information about the radio interface at the physical layer.
When the Port Mode parameter is set to Layer 2, the value of the Encapsulation Type parameter
can be Null, 802.1Q, or QinQ. When a port needs to carry the Ethernet service, the Port Mode
parameter needs to be set to Layer 2.
When the Port Mode parameter is set to Layer 3, the value of the Encapsulation Type parameter
can only be 802.1Q. When a port needs to carry the tunnel, the Port Mode parameter needs to be
set to Layer 3. In addition, the Port Mode parameter needs to be set to Layer 3 when a PW carries
the service (including the Ethernet service, CES service, and ATM service).
The value of the MTU (byte) parameter set for an NNI must be greater than 960, because the
maximum length of a DCN packet is 960 bytes. When the value of the MTU (byte) parameter is
smaller than 960, the DCN packet in the receive direction may be lost.
Setting
advanced
attributes
Setting
general
attributes
Setting IF
attributes
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
The IF attributes of a radio interface, including the AM enabling status and ATPC status, define the information
about the IF board. Set the IF attributes according to the network planning.
This pane displays the working modes of the transmit end and the receive end and the service capacity of the
selected IF board.
Setting
general
attributes
Setting IF
attributes
Setting
Layer
2/Layer 3
attributes
After the Layer 2 attributes of a radio interface are set, this radio interface can be connected to the client-side equipment
on the edge of a PSN or forward Ethernet packets on a PSN. The Layer 2 attributes of a radio interface define the
information about the radio interface at the data link layer.
The QinQ Type Domain parameter can be set only when the Encapsulation Type parameter (contained in the general
Setting
advanced
attributes
Configuring a
radio link
Setting
general
attributes
Setting
Layer
2/Layer 3
attributes
Setting IF
attributes
Setting
advanced
attributes
If a radio interface is used to carry the tunnel, the Layer 3 attributes of the radio interface need to be set. The Layer 3 attributes of
a radio interface define the information about the radio interface at the network layer.
Parameter description
Enable Tunnel: After a tunnel is enabled, the port can identify and process the MPLS label, and thus can support the dynamic
signaling and routing.
Max Reserved Bandwidth (kbit/s): This parameter specifies the bandwidth used by a tunnel. The maximum reserved bandwidth
should not be higher than the physical bandwidth at the port.
TE Measurement: This parameter allows manual intervention in routing. When the value of this parameter is smaller, the priority of
the link is higher. In this manner, traffic congestion on the shortest path, which occurs in conventional routing, can be prevented.
Admin Group: This parameter specifies the link attribute. After the affinity attribute of a dynamic tunnel is set, it compares its affinity
attribute with the admin group attribute of links in the case of link selection. In this manner, the dynamic tunnel can determine which
links should be selected or avoided.
Specify IP and IP Address: The IP Address parameter can be set only when the Specify IP parameter is set to Manually. Ensure
that the IP address of the interface is not in the same subnet as the IP addresses of other interfaces that are already configured with
services.
Setting
general
attributes
Setting IF
attributes
Setting
Layer
2/Layer 3
attributes
You can set the parameters related to routine maintenance by setting the advanced attributes of a radio interface, so that
Setting
advanced
attributes
Interface Type
Ethernet interface
Ethernet interface
Ethernet interface
On a radio transmission network, an NNI is generally a radio interface and a UNI is generally an Ethernet interface. Hence, you only
need to set the general attributes of an Ethernet interface.
Setting general
attributes
Setting general
attributes
Setting
Layer 2
attributes
Setting
Layer 3
attributes
Setting
advanced
attributes
Setting
advanced
attributes
Configuring
the flow control
function
Configuring
the flow control
function
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
Configuring
the flow control
function
Set the general attributes of an Ethernet interface before setting the Layer 2 and Layer 3
attributes of this Ethernet interface. The general attributes of an Ethernet interface, including the
port mode, encapsulation type, and maximum frame length, define the information about the
Ethernet interface at the physical layer.
When the Port Mode parameter is set to Layer 2, the value of the Encapsulation Type parameter can be
Null, 802.1Q, or QinQ.
When the Port Mode parameter is set to Layer 3, the value of the Encapsulation Type parameter can
only be 802.1Q. When a port needs to carry the tunnel, the Port Mode parameter needs to be set to Layer
3.
The value of the Max Frame Length parameter set for an NNI must be greater than 960, because the
maximum length of a DCN packet is 960 bytes. When the value of the Max Frame Length parameter is
smaller than 960, the DCN packet in the receive direction may be lost.
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
Configuring
the flow control
function
After the Layer 2 attributes of an Ethernet interface are set, this Ethernet interface can be connected to the client-side
equipment on the edge of a PSN or forward Ethernet packets on a PSN.
Parameter description
QinQ Type Domain: This parameter can be set only when the Encapsulation Type parameter is set to
QinQ.
Tag: This parameter can be set only when the Encapsulation Type parameter is set to 802.1Q.
Default VLAN ID and VLAN Priority: The two parameters are valid only when the Tag parameter is set to
Access or Hybrid.
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
If an Ethernet interface is used to carry the tunnel, the Layer 3 attributes of the Ethernet interface need to be set.
Parameter description
Enable Tunnel: After a tunnel is enabled, the port can identify and process the MPLS label, and thus can
support the dynamic signaling and routing.
Max Reserved Bandwidth (kbit/s): This parameter specifies the bandwidth used by a tunnel. The maximum
reserved bandwidth should not be higher than the physical bandwidth at the port.
TE Measurement: This parameter allows manual intervention in routing. When the value of this parameter is
smaller, the priority of the link is higher. In this manner, traffic congestion on the shortest path, which occurs in
conventional routing, can be prevented.
Admin Group: This parameter specifies the link attribute. After the affinity attribute of a dynamic tunnel is set,
it compares its affinity attribute with the admin group attribute of links in the case of link selection. In this
manner, the dynamic tunnel can determine which links should be selected or avoided.
IP Address: Ensure that the IP address of the interface is not in the same subnet as the IP addresses of other
interfaces that are already configured with services.
Board for Unnumbered IP and Port for Unnumbered IP: The two parameters cannot be set.
Configuring
the flow control
function
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
You can set the parameters related to routine maintenance by setting the advanced attributes of an Ethernet interface.
Configuring
the flow control
function
Setting
Layer
2/Layer 3
attributes
Setting
advanced
attributes
After the flow control function is enabled, an Ethernet interface can send the PAUSE frame to pause the transmission of
the Ethernet packet from the opposite end if congestion occurs on a link. In this manner, congestion can be prevented.
Configuring
the flow control
function
Creating an NE
Configuring an interface
Creating a tunnel
You need to create a tunnel by setting the parameters related to the protocols on the control
plane.
If a static MPLS tunnel is created to carry the service, you need not set the parameters related
If a dynamic MPLS tunnel is created to carry the service, you need to set the following
parameters:
If a dynamic PW is created to carry the service, you need to set the parameters related to the
Configuring
the IGP-ISIS
protocol
Configuring the
MPLS-LDP
protocol
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Parameter description
IGP-ISIS Instance ID: Yon can select Automatically Assign or enter the planned ID (which ranges
from 1 to 65535).
Node Level: The value of this parameter can only be level 1-2 and cannot be set.
Area ID: This parameter is composed of numbers. Ensure that the nodes in the same area have the
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP
protocol
Route Color: This parameter specifies the color of the route, and a maximum of 16 colors can be set. Therefore,
the value of this parameter ranges from 1 to 16. You can divide a large autonomous domain into multiple logical subdomains by setting the route color. The sub-domains with different route colors cannot communicate the IS-IS routing
protocol packet to each other. Hence, these sub-domains are isolated from each other, which facilitates link
management and maintenance.
LSP Refresh Time (s): To ensure that all the LSPs in the entire domain are synchronized, the router periodically
transmits all the current LSPs. The period of transmitting LSPs is the LSP refresh time. It is recommended that this
parameter takes the default value.
Maximum LSP Validity (s): When an LSP router generates the system LSP, it writes the life time of this LSP into the
LSP. When this LSP is received by other routers, the life time decreases when the time elapses. If the router does not
receive the updated LSP when the life time of this LSP decreases to 0, the router directly deletes this LSP from the link
state database (LSDB). The life time is the maximum LSP validity. It is recommended that this parameter takes the
default value.
Configuring the
MPLS-LDP protocol
An IGP-ISIS protocol interface can be added successfully only after its attribute is
set to Layer 3. Otherwise, a prompt is displayed, indicating that the operation fails
due to an incorrect port type.
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Unless otherwise specified, the Link Overhead, Authentication Mode, Hello Send Interval, and Hello
Loss Count parameters take the default values. If there are special requirements, set these parameters
according to the network design.
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP
protocol
If the dynamic PW needs to be created, the MPLS-LDP protocol must be configured. The MPLS-LDP protocol is
used to create the dynamic PW and to dynamically allocate the PW label. By running the MPLS-LDP protocol, an
NE only knows its neighboring NEs. In the case of a single service, the MPLS-LDP peer entity specified in the
MPLS-LDP protocol should be configured so that the NEs at both ends can know each other. On the T2000, you
can create the MPLS-LDP peer entity and configure the MPLS-LDP protocol.
In the case of the local session and remote session, it is required to create bidirectional LDP peer entities
between the source equipment and sink equipment is required. That is, peer entities should be created from the
source to the sink and from the sink to the source.
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP
protocol
Configuring the
IGP-ISIS
protocol
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP
protocol
Configuring the
MPLS-LDP protocol
Configuring the
MPLS-RSVP protocol
The MPLS-RSVP protocol is used to create the dynamic MPLS tunnel and to allocate the label of the
dynamic tunnel. On the T2000, you can set and query the parameters related to the MPLS-RSVP
protocol. The MPLS-RSVP protocol need not be specially configured, and you can set each parameter
according to requirements.
Static route is obtained according to the preset routing options for the network.
On the T2000, you can create and query the static route.
Creating an NE
Configuring an interface
Creating a tunnel
Creating a Tunnel
On a PSN, an MPLS tunnel carries PWs that encapsulate various services, and thus realizes transparent transmission of data packets
between NEs. Multiple PWs can be transmitted in one MPLS tunnel. Hence, you need to configure the MPLS tunnel before configuring a
service.
On the T2000, you can create a unicast tunnel by using either of the following methods:
Configuration on a per-NE basis: To create a unicast MPLS tunnel, you need to set the related parameters, including the ingress
port and IP address of the next hop, for each NE that an MPLS tunnel traverses.
Configuration by using the trail function: This method includes static configuration and dynamic configuration.
Static configuration: To create a unicast MPLS tunnel, you need to specify the source NE and sink NE of this MPLS tunnel,
Dynamic configuration: To create a unicast MPLS tunnel, you need to specify only the source NE and sink NE of this MPLS
tunnel and then the equipment creates a unicast MPLS tunnel through signaling transmission.
The following description considers the configuration on a per-NE basis as an example to describe how to create an MPLS tunnel. For
details about the method for creating an MPLS tunnel by using the trail function, see the related description in the Configuration Guide
contained in the package of documents.
Creating a Tunnel
Creating a Tunnel
parameters.
Set the Node Type parameter. If Positive Value is
set to Ingress, Negative Value is set to Egress. If
Positive Value is set to Transit, Negative Value is
also set to Transit.
Creating a Tunnel
Click the OAM Parameters tab to configure OAM for the new tunnel.
Creating an NE
Configuring an interface
Creating a tunnel
You may set one or more VLAN IDs or do not set any
Configure PW.
After the
configuration is
complete, click
OK.
following
button.
button to select
Creating an NE
Configuring an interface
Creating a tunnel
Contents
1.
2.
3.
4.
Configuration Process
Configuration Tasks
clocks.
Create a
network
Configure an
interface
UNI-NNI
CES
service
the service.
plane.
If a dynamic PW is created to
End
protocols.
Creating an NE
Configuring an interface
Creating a tunnel
UNI-UNI
UNI-NNI
Application Scenario
Interface Type
E1 interface
E1 interface
E1 interface
On a radio transmission network, an NNI is generally a radio interface that is used to carry the tunnel. Hence, when the CES service is
configured, configure the radio interface based on the method of configuring a radio interface to carry the tunnel (that is, set the general
attributes and Layer 3 attributes of the radio interface); configure the E1 interface to function as the UNI (that is, set the general attributes
and advanced attributes of the E1 interface).
When the Port Mode parameter is set to Layer 1, the Encapsulation Type parameter cannot be set. In this
case, the TDM service can be accessed.
When the Port Mode parameter is set to Layer 2, the Encapsulation Type parameter can only be set to ATM.
In this case, the ATM service can be accessed.
When a PDH interface is used for the inband DCN, the Port Mode parameter for the PDH interface cannot be
set to Layer 2 or Layer 1.
When the Port Mode parameter is set to Layer 3, the Encapsulation Type parameter can be set to Null or
PPP. If the Encapsulation Type parameter is set to Null, the PPP protocol is not enabled at the interface and
thus the equipment carries less load. If the Encapsulation Type parameter is set to PPP, the interface can carry
the MPLS.
Set the Frame Format and Frame Mode parameters in Advanced Attributes
to ensure that the frame format settings of the interface are the same as the
service encapsulation format settings.
Creating an NE
Configuring an interface
Creating a tunnel
UNI-UNI
UNI-NNI
Click Apply.
Select the board and port that access the TDM service in
Contents
1.
2.
3.
4.
Configuration Process
Configuration Tasks
Start
Configuration Process
UNI-UNI ATM service
Create a
network
UNIs-NNI ATM
service
Configure an NNI
Configure an ATM
interface
End
Creating an NE
Configuring an NNI
Creating a tunnel
UNI-UNI
UNIs-NNI
Automatically Assign.
Policy Name: You can select one from the five ATM
type.
Creating an NE
Configuring an NNI
Creating a tunnel
UNI-UNI
UNIs-NNI
Select
According to the network planning, the IMA Protocol Version, IMA Symmetry Mode, Maximum Delay Between Links, Minimum
Number of Active Transmitting Links, and Minimum Number of Active Receiving Links parameter should be set the same as the
parameters set on the NodeB.
Port Type: Set this parameter to UNI. (UNI indicates that the interface is connected to the client-side equipment. NNI
indicates that the interface is connected to the ATM equipment within the network.)
Creating an NE
Configuring an NNI
Creating a tunnel
UNI-UNI
UNIs-NNI
35, 36-39), Source VCI (e.g. 35, 36-39), Sink Board, Sink
Port, Sink VPI (e.g. 35, 36-39), and Sink VCI (e.g. 35, 3639) parameters according to the network planning.
35, 36-39), Source VCI (e.g. 35, 36-39), Sink Board, Sink
Port, Sink VPI (e.g. 35, 36-39), and Sink VCI (e.g. 35, 3639) parameters according to the network planning.
Click OK.
Summary
Thank You
www.huawei.com