Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuration Example: Composite Service Consisting of E-Line and E-LAN Services
This section describes the networking of and configuration method for a composite service consisting of E-Line and E-LAN services.
- Networking Diagram
The networking diagram shows the requirements for a composite service consisting of E-Line and E-LAN services. - Service Planning
The engineering information for configuring a composite service consisting of E-Line and E-LAN services includes information for configuring: tunnels that carry PWs, UNI-NNI E-Line services carried by PWs, E-LAN services carried by PWs, and points that connect E-Line and E-LAN services to form a composite service. - Configuration Process
This section describes how to configure a composite service consisting of E-Line and E-LAN services in end-to-end mode. - Verifying the Composite Service Consisting of E-Line and E-LAN Services
You can check whether packet loss has occurred in an Ethernet packet service by looping back the service at one end and testing packet loss with a SmartBits at the other end.
Networking Diagram
The networking diagram shows the requirements for a composite service consisting of E-Line and E-LAN services.
On the network shown in Figure 3-43, services with the same VLAN ID from User A1 and User A2 are received/transmitted by different ports on NE1. NE1 transmits the services to NE4, which then aggregates them and transmits them to User A3.
- Services from User A1 are received/transmitted by the 4-EM6F-3 port on NE1; services from User A2 are received/transmitted by the 4-EM6F-4 port on NE1; services from User A3 are received/transmitted by the 4-EM6F-3 port on NE4.
- Services between User A1 and User A3 are data services, of which the VLAN ID is 100, CIR is 30 Mbit/s, and PIR is 50 Mbit/s.
- Services between User A2 and User A3 are data services, of which the VLAN ID is 100, CIR is 30 Mbit/s, and PIR is 50 Mbit/s.
- Services between User A1/User A2 and User A3 are carried by PWs. E-Line services are configured on NE1, and E-LAN services are configured on NE4.
- Services between User A1/User A2 and User A3 are protected by tunnel APS.
- The working path is NE1-NE2-NE4.
- The protection path is NE1-NE3-NE4.
Figure 3-43 Networking of a composite service consisting of E-Line and E-LAN services
![]()
![]()
NOTE:
![]()
NOTE:
![]()
NOTE:
NOTE: - This topic considers the OptiX OSN 550 as an example to describe the board layout. In the case of other products, the configuration method is the same, except for the slots. For the slot information, see the Hardware Description of the relevant product.
- On a live data network, an Ethernet service is added to the source NE, passed through the transit NEs, and dropped from the sink NE. Follow instructions in Configuring Transit NEs for Ethernet Services Carried by PWs to configure transit NEs for the Ethernet services carried by PWs.
NOTE: The method for configuring services from User A2 to User A3 is the same as that for configuring services from User A1 to User A3. When planning and configuring services from User A2 to User A3, follow instructions in sections that describe how to plan and configure services from User A1 to User A3.
| NE | IP Address | IP Mask | LSR ID | |
|---|---|---|---|---|
| NE1 | 4-EM6F-1 | 18.1.1.1 | 255.255.255.252 | 130.0.0.1 |
| 4-EM6F-2 | 18.1.2.1 | 255.255.255.252 | ||
| NE2 | 4-EM6F-1 | 18.1.1.2 | 255.255.255.252 | 130.0.0.2 |
| 4-EM6F-2 | 18.1.1.5 | 255.255.255.252 | ||
| NE3 | 4-EM6F-1 | 18.1.2.2 | 255.255.255.252 | 130.0.0.3 |
| 4-EM6F-2 | 18.1.2.5 | 255.255.255.252 | ||
| NE4 | 4-EM6F-1 | 18.1.1.6 | 255.255.255.252 | 130.0.0.4 |
| 4-EM6F-2 | 18.1.2.6 | 255.255.255.252 | ||
NOTE: - The IP addresses of Ethernet ports on an NE must not be on the same network segment.
- The IP addresses of ports at both ends of a tunnel must be on the same network segment.
Service Planning
The engineering information for configuring a composite service consisting of E-Line and E-LAN services includes information for configuring: tunnels that carry PWs, UNI-NNI E-Line services carried by PWs, E-LAN services carried by PWs, and points that connect E-Line and E-LAN services to form a composite service.
You need to plan a tunnel for carrying PWs according to the service plan. When planning a composite service consisting of E-Line and E-LAN services:
- Plan a tunnel for carrying PWs by reference to Table 3-226 and Table 3-227.
- Plan MPLS tunnel OAM by reference to Table 3-228.
- Plan MPLS tunnel APS by reference to Table 3-229.
- Plan UNI-NNI E-Line services carried by PWs by reference to Table 3-230.
- Plan E-LAN services carried by PWs by reference to Table 3-231.
- Plan the composite service by reference to Table 3-232.
Table 3-226 Basic attributes of a tunnel
| Parameter | Parameter Planning |
|---|---|
| Tunnel Name | Auto-Assign NOTE:
The rule of auto-assigned Tunnel Name:
Source NE-Sink NE-SignalType-ServiceID-0000000x |
| Protection Tunnel Name | Auto-Assign NOTE:
The rule of auto-assigned Protection
Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000x_PRT |
| Protocol Type | MPLS |
| Signaling Type | Static CR |
| Service Direction | Bidirectional |
| Protection Type | 1:1 |
| Protection Group Name | Auto-Assign NOTE:
The rule of auto-assigned ProtectionSource
NE-Sink NE-PG-0000000x |
| Switching ModeSingle | Single-Ended switching |
Table 3-227 Planning information of the tunnels
| Tunnel | Tunnel ID | Node | Node Type | In Interface | In Label | Reverse In Label | Out Interface | Out Label | Reverse Out Label | Next Hop | Reverse Next Hop | Source Node | Sink Node |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Working Tunnel | Auto-Assign | NE1 | Ingress | - | - | 102 | 4-EM6F-1 | 100 | - | 18.1.1.2 | - | - | 130.0.0.4 |
| NE2 | Transit | 4-EM6F-1 | 100 | 103 | 4-EM6F-2 | 101 | 102 | 18.1.1.6 | 18.1.1.1 | 130.0.0.1 | 130.0.0.4 | ||
| NE4 | Egress | 4-EM6F-1 | 101 | - | - | - | 103 | - | 18.1.1.5 | 130.0.0.1 | - | ||
| Protection Tunnel | Auto-Assign | NE1 | Ingress | - | - | 202 | 4-EM6F-2 | 200 | - | 18.1.2.2 | - | - | 130.0.0.4 |
| NE3 | Transit | 4-EM6F-1 | 200 | 203 | 4-EM6F-2 | 201 | 202 | 18.1.2.6 | 18.1.2.1 | 130.0.0.1 | 130.0.0.4 | ||
| NE4 | Egress | 4-EM6F-2 | 201 | - | - | - | 203 | - | 18.1.2.5 | 130.0.0.1 | - |
Table 3-228 Parameter planning for MPLS tunnel OAM
| Parameter | Parameter Planning | |
|---|---|---|
| OAM Status | Enable Sending and Receiving | Enable Sending and Receiving |
| Detection Mode | Manual | Manual |
| Detection Packet Type | FFD NOTE:
Detection Packet Period can be set only when Detection Packet Type is FFD. |
FFD |
| Detection Packet Period (ms) | 3.3 NOTE:
Generally, the OAM packet is reported
after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet
the requirement (less than 50 ms) after a fault occurs. |
3.3 |
Table 3-229 Parameter planning for MPLS tunnel APS
| Parameter | Parameter Planning | |
|---|---|---|
| Protocol Status | Enabled | |
| Revertive Mode | Revertive | |
| WTR Time(min) | 5 | |
| Hold-off Time(100ms) | 0 NOTE:
Services are not protected with multiple
protection schemes. Therefore, the setting of Hold-off Time(100ms) is unnecessary. |
|
Table 3-230 E-Line service parameters
Parameter |
Parameter Planning |
|---|---|
Service Type |
ETH |
Service ID |
1 |
Service Name |
pwe3_NE1 |
Protection Type |
Protection-Free |
| Node List | |
Source |
NE1: 4-EM6F-3 |
VLAN ID |
100 |
Unterminated > Sink |
130.0.0.4 |
| PW | |
PW ID |
35 |
Signaling Type |
Static |
Forward Type |
Static Binding |
Forward Tunnel |
NE1_NE4_working |
Forward Label |
20 |
Reverse Label |
20 |
Encapsulation Type |
MPLS |
| PW QoS | |
Bandwidth Limited |
Enabled |
CIR (kbit/s) |
30000 |
PIR (kbit/s) |
50000 |
| Advanced attributes for PWs | |
PW Type |
Ethernet |
Other parameters |
Default values |
Table 3-231 E-LAN service parameters
Parameter |
Parameter Planning |
|---|---|
Service Name |
vpls |
Signaling Type |
LDP/Static |
Networking Mode |
Full-Mesh VPLS |
Service Type |
Service VPLS |
VSI Name |
vsi1 |
VSI ID |
50 |
NPE |
NE4 |
| VSI Configuration | |
MTU |
1500 |
Tag Type |
C-Aware |
MAC Address Learning |
Enable |
Learning Mode |
Quality (IVL) |
Enable BPDU Transparent Transmission |
Not Transparently Transmitted |
| PW Configuration | |
Unterminated PW |
Set parameters as follows:
|
| Service port configuration | |
NE |
NE4 |
Interface |
4-EM6F-4 |
VLAN |
100 |
Other parameters |
Default values |
Table 3-232 Composite service parameters
Parameter |
Parameter Planning |
|---|---|
Service Name |
PWE3+VPLS |
Creation Type |
Customize |
Service Component |
Select service components as follows:
|
PW Connection Point |
Set parameters as follows:
|
Configuration Process
This section describes how to configure a composite service consisting of E-Line and E-LAN services in end-to-end mode.
Prerequisites
- You must be familiar with the networking requirements and service plan of the composite service.
- You are an NM user with Administrators rights or higher.
Procedure
- Follow instructions in Configuring an MPLS Tunnel in an End-to-End Mode to configure a tunnel for carrying PWs.
Table 3-233 Basic attributes of a tunnel
Parameter Parameter Planning Tunnel Name Auto-Assign
NOTE:The rule of auto-assigned Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000xProtection Tunnel Name Auto-Assign
NOTE:The rule of auto-assigned Protection Tunnel Name: Source NE-Sink NE-SignalType-ServiceID-0000000x_PRTProtocol Type MPLS Signaling Type Static CR Service Direction Bidirectional Protection Type 1:1 Protection Group Name Auto-Assign
NOTE:The rule of auto-assigned ProtectionSource NE-Sink NE-PG-0000000xSwitching ModeSingle Single-Ended switching Table 3-234 Planning information of the tunnelsTunnel Tunnel ID Node Node Type In Interface In Label Reverse In Label Out Interface Out Label Reverse Out Label Next Hop Reverse Next Hop Source Node Sink Node Working Tunnel Auto-Assign NE1 Ingress - - 102 4-EM6F-1 100 - 18.1.1.2 - - 130.0.0.4 NE2 Transit 4-EM6F-1 100 103 4-EM6F-2 101 102 18.1.1.6 18.1.1.1 130.0.0.1 130.0.0.4 NE4 Egress 4-EM6F-1 101 - - - 103 - 18.1.1.5 130.0.0.1 - Protection Tunnel Auto-Assign NE1 Ingress - - 202 4-EM6F-2 200 - 18.1.2.2 - - 130.0.0.4 NE3 Transit 4-EM6F-1 200 203 4-EM6F-2 201 202 18.1.2.6 18.1.2.1 130.0.0.1 130.0.0.4 NE4 Egress 4-EM6F-2 201 - - - 203 - 18.1.2.5 130.0.0.1 - - Follow instructions in Configuring MPLS Tunnel OAM to configure MPLS tunnel OAM.
Table 3-235 Parameter planning for MPLS tunnel OAM
Parameter Parameter Planning OAM Status Enable Sending and Receiving Enable Sending and Receiving Detection Mode Manual Manual Detection Packet Type FFD NOTE:Detection Packet Period can be set only when Detection Packet Type is FFD.FFD Detection Packet Period (ms) 3.3 NOTE:Generally, the OAM packet is reported after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet the requirement (less than 50 ms) after a fault occurs.3.3 - Follow instructions in Configuring Tunnel APS to configure MPLS tunnel APS.
- Configure PW-carried E-Line services in end-to-end mode.
On NE1, configure PW-carried E-Line services that are emulated using PWE3 and are transmitted to NE4.
- Configure PW-carried E-Line services in end-to-end mode.
Configure PW-carried E-Line services on NE4.
- Configure a composite service.
Related Task
Follow instructions in Verifying the Composite Service Consisting of E-Line and E-LAN Services to check whether the composite service is configured correctly.
Verifying the Composite Service Consisting of E-Line and E-LAN Services
You can check whether packet loss has occurred in an Ethernet packet service by looping back the service at one end and testing packet loss with a SmartBits at the other end.
Prerequisites
- You are an NM user with Administrators rights or higher.
- Ethernet services have been configured. For details on how to configure Ethernet services, see Configuring ETH PWE3 Services in the Configuration Guide (Packet Transport Domain).
Connection Diagram for the Test
Figure 3-44 shows a connection diagram for testing packet Ethernet services.
Figure 3-44 Connection diagram for testing packet Ethernet services
![]()
![]()
NOTE:
NOTE: The connection diagram is only an example. In this example, a MAC-layer inloop is performed on an Ethernet port on NE1, and the SmartBits is connected to an Ethernet port on NE2. If required, you can connect the SmartBits to any Ethernet
board on the source or sink NE of a packet Ethernet service.
Precautions
- Keep irrelevant personnel away from the testing environment during a test.
- Do not touch fibers, electrical wires, or cables unless necessary.
Procedure
- According to the test connection diagram, connect the SmartBits to the Ethernet port on NE2.
- Log in to the U2000. Follow instructions in Enabling NE Performance Monitoring to enable 15-minute and 24-hour performance monitoring for NE1 and NE2.
![]()
NOTE: Performance monitoring needs to be enabled in case that a fault detected in the test can be located. - Log in to the U2000 and set a MAC-layer inloop for the Ethernet port on NE1.
- In the Workbench view, double-click Main Topology to display the main topology.
- Right-click the NE to be looped back on the Main Topology of the U2000, and choose NE Explorer from the shortcut menu.
- Select the Ethernet board to be looped back, and choose from the Function Tree.
- Select Advanced Attributes.
- In the list, select an Ethernet interface, and then double-click PHY Loopback or MAC Loopback to select a loopback mode.
- Click Query. After the Prompt dialog box is displayed, click OK.
- After the Operation Result dialog box is displayed, click Close.
- Use the SmartBits to perform tests on packet receiving and transmission.
![]()
NOTE: - Packets with all 0s are regarded as special packets. Therefore, do not use packets of all 0s for testing transmitted and received packets.
- When the SmartBits transmits and receives packets for the first time, packet loss occurs due to MAC address learning. Therefore, it is normal that the number of transmitted packets is different from the number of received packets.
- In the tests after the first time, if the number of transmitted packets is the same as the number of received packets, the cross-domain service channels are normal.
- If packet loss occurs during the tests, troubleshoot the fault and then perform 24-hour tests until the channels pass the tests.
Previous
