No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OSN 500 550 580 V100R008C50 Commissioning and Configuration Guide 02

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).
Service Types

Service Types

In compliance with ITU-T G.8011x/Y.1307x, Huawei MSTP equipment supports Ethernet private line (EPL), Ethernet virtual private line (EVPL), Ethernet private local area network (EPLAN), and Ethernet virtual private local area network (EVPLAN) services.

EPL Services

Two nodes are used to access EPL services and implement transparent transmission of the Ethernet services of the users. The service of one user occupies one VCTRUNK and need not share the bandwidth with the services of the other users. Hence, in the case of EPL services, a bandwidth is exclusively occupied by the service of a user and the services of different users are isolated. In addition, the extra QoS scheme and security scheme are not required.

Figure 2-46  EPL services

The corresponding relations between the PORTs (namely, external ports) and the VCTRUNKs are listed in Table 2-145.

Table 2-145  Corresponding relations between the external ports and the VCTRUNKs (EPL services)
NE1 NE2
User A1 PORT1←→VCTRUNK1 VCTRUNK1←→PORT1 User A2
User B1 PORT2←→VCTRUNK2 VCTRUNK2←→PORT2 User B2

EVPL Services

In the case of EVPL services, services of different users share the bandwidth. Hence, the VLAN/QinQ scheme needs to be used for differentiating the services of different users. If the services of different users need to be configured with different quality levels, you need to adopt the corresponding QoS scheme. EVPL services are classified into two types, depending on whether the PORT or VCTRUNK is shared.

  • PORT-shared EVPL services

As shown in Figure 2-47, the services of different users are accessed through a PORT at a station, and are then isolated from each other by using the VLAN IDs. Services are transmitted to other PORTs at this station through different VCTRUNKs.

Figure 2-47  PORT-shared EVPL services

The corresponding relations between the PORTs and the VCTRUNKs are provided in Table 2-146.

Table 2-146  Corresponding relations between the PORTs and the VCTRUNKs (PORT-shared EVPL services)
NE1 NE2
User C1 PORT1←→VCTRUNK1 VCTRUNK1←→PORT1 User C2
PORT1←→VCTRUNK2 VCTRUNK2←→PORT2 User C3
  • VCTRUNK-shared EVPL services Ethernet boards support the convergence and distribution of EVPL services by using the following modes:
    • VLAN tag-based convergence and distribution of EVPL services
    • QinQ technology-based convergence and distribution of EVPL services

As shown in Figure 2-48, the services of different users are isolated by using the VLAN/QinQ scheme. Hence, the services of different users can be transmitted in the same VCTRUNK.

Figure 2-48  VCTRUNK-shared EVPL services

The corresponding relations between the PORTs and the VCTRUNKs are provided in Table 2-147.

Table 2-147  Corresponding relations between the PORTs and the VCTRUNKs (VCTRUNK-shared EVPL services)
NE1 NE2
User D1 PORT1←→VCTRUNK1 VCTRUNK1←→PORT1 User D2
User E1 PORT2←→VCTRUNK1 VCTRUNK1←→PORT2 User E2

EPLAN Services

The EPLAN services can be accessed from a minimum of two nodes. Hence, the services of different users need not share the bandwidth. That is, in the case of EPLAN services, a bandwidth is exclusively occupied by the service of a user and the services of different users are isolated. In addition, the extra QoS scheme and security scheme are not required. The EPLAN services have more than one node. Hence, the nodes need to learn the MAC addresses and forward data according to MAC addresses. Therefore, Layer 2 switching is realized.

As shown in Figure 2-49, three branches of user F need to communicate with each other. On NE1, the IEEE 802.1d bridge is established to achieve EPLAN services. The IEEE 802.1d bridge can create the MAC address-based forwarding table, which is periodically updated by using the self-learning function of the system. The accessed data can be forwarded or broadcast within the domain of the IEEE 802.1d bridge according to the destination MAC addresses.

Figure 2-49  EPLAN services (IEEE 802.1d bridge)

EVPLAN Services

EVPLAN services of different users need to share the bandwidth. Hence, the VLAN/QinQ scheme needs to be used for differentiating the data of different users. If the services of different users need to be configured with different quality levels, you need to adopt the corresponding QoS scheme.

As shown in Figure 2-50, three branches of user G need to communicate with each other. Services of user G need to be isolated from the services of user H. Hence, the IEEE 802.1q bridge needs to be established on NE1 to achieve EVPLAN services.

IEEE 802.1q bridge: IEEE 802.1q bridge supports isolation by using one layer of VLAN tags. This bridge checks the contents of the VLAN tags that are in the data frames and performs Layer 2 switching according to the destination MAC addresses and VLAN IDs.

Figure 2-50  EVPLAN services (IEEE 802.1q bridge)

As shown in Figure 2-51, the VoIP services from user M and the HSI services from user N need to respectively access the VoIP server and the HSI server. In this case, the operator needs to separately groom the VoIP services and HSI services, and isolate the data on the transmission network side. On NE1, the IEEE 802.1ad bridge must be established to support the EVPLAN services.

IEEE 802.1ad bridge: The IEEE 802.1ad bridge supports data frames with two layers of VLAN tags. This bridge adopts the outer S-VLAN tags to isolate different VLANs and supports only the mounted ports whose attributes are C-Aware or S-Aware. This bridge supports the following switching modes:

  • This bridge does not check the contents of the VLAN tags that are in the packets and performs Layer 2 switching according to the destination MAC addresses of the packets.
  • This bridge checks the contents of the VLAN tags that are in the packets and performs Layer 2 switching according to the destination MAC addresses and the S-VLAN IDs of the packets.
Figure 2-51  EVPLAN services (IEEE 802.1ad bridge)

Translation
Download
Updated: 2019-01-21

Document ID: EDOC1100020976

Views: 57832

Downloads: 487

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next