[Definition]

Native Ethernet services are also called VLAN services. A VLAN is a logic subnet divided from a real network. Broadcast packets in a VLAN cannot be transmitted to other VLANs. In other words, one VLAN is mapped to one broadcast domain.

Figure 1 shows a VLAN application. All Ethernet devices of a company belong to one LAN, and the Ethernet devices of different departments form their independent VLANs. Broadcast packets in a VLAN can be transmitted only in this VLAN. With this method, Ethernet packets of different departments are isolated, and broadcast packets do not flood on a LAN.

The E2E native Ethernet module is a functional component for fast multi-point service configuration, including configuring and managing native E-Line services, E-LAN services, and E-Line_E-LAN services.

Figure 1-1 Networking diagram of a VLAN application

[Benefits]

The E2E native Ethernet module provides visualized service configuration and management.

The E2E native Ethernet module allows you to configure services for all devices in a window, including service-related configurations, such as service ports, C-VLANs or S-VLANs, port attributes (port encapsulation type and tag type), and split horizon groups. In addition, you can perform automatic route calculation for E-Line services. Compared with service configuration for NEs one by one in the NE Explorer, E2E native Ethernet service configuration greatly improves the service provisioning efficiency.

The E2E native Ethernet module supports service-based management and monitoring functions, such as topology display, alarm locating, and Ethernet OAM fault detection, which improves the routine operation and maintenance (O&M) efficiency.

[Application Scenario]

l   E-Line scenario 1 – Both the BTS and the BSC support VLANs.

The BTS can be configured with one or more VLAN IDs; all data on the ports must carry VLAN tags.

l   E-Line scenario 2 – The BTS does not support VLANs and the BSC does.

All data on the ports does not carry any VLAN tag. (Packets carrying VLAN tags will be discarded in access mode.)

l   E-Line scenario 3 – Neither the BTS nor the BSC supports or uses VLANs.

If the BSC does not support or use VLANs, packets cannot be transmitted in different lines when a single link is connected to the transmission network. In this case, Layer 3 packet forwarding is required by using routers.

l   E-LAN (802.1q) scenario 1 – Both the BTS and the BSC support VLANs.

The BTS can be configured with one or more VLAN IDs; all data on the ports must carry VLAN tags.

If all or some VLAN IDs are the same, you can use the 802.1q bridge to set the BTS access port attribute to Access and the attributes of other ports to Tag Aware.

Setting a split horizon group can reduce broadcast storms.

l   E-LAN (802.1q) scenario 2 – The BTS does not support VLANs and the BSC does.

No data on the ports carries VLAN tags. (Packets carrying VLAN tags will be discarded in access mode.)

If all or some VLAN IDs are the same, the 802.1q bridge is available. Set the BTS access port attribute to Access and the attributes of other ports to Tag Aware.

Setting a split horizon group can reduce broadcast storms.

l   E-LAN (802.1q) scenario 3 – Neither the BTS nor the BSC supports or uses VLANs.

If all or some VLAN IDs are the same, the 802.1q bridge is available. Set the BTS access port attribute to Access and the attributes of other ports to Tag Aware.

Setting a split horizon group can reduce broadcast storms.

l   E-LAN (802.1d) scenario 4 – The tag attribute of the BTS or the BSC is not concerned.

If no VLAN is planned or VLAN information cannot be obtained, the 802.1d bridge is available networkwide. This ensures that all packets can be transmitted from the BTS to the BSC.

You are not advised to use the 802.1d bridge networkwide, because this operation places the entire network in a broadcast domain and brings large security risks.

Setting a split horizon group can reduce broadcast storms.