The EVPLAN service realizes dynamic sharing of services from multiple nodes and supports MPLS label for data with the same VLAN ID. In this case, a node needs to access two services with the same VLAN ID at the same time, and the two services share the bandwidth dynamically. These requirements can be realized by EVPLAN, as shown in Figure 4-7.
Figure 4-7 EVPLAN service application
Compared with EPLAN, EVPLAN can further distinguish data with the same VLAN ID through MPLS label, realizing transmitting data from different VBs but with the same VLAN ID over the same VCTRUNK. Therefore, it can realize dynamic bandwidth sharing and data isolation for Company A and B.
|
Implementation |
Service type: EVPLAN VB + MPLS route The Ethernet processing board of the OptiX OSN product supports VB and MPLS. EVPLAN supports MPLS encapsulation, allowing several VB users to share one VCTRUNK and realizing dynamic sharing of bandwidth. In this example, branch 1 of Company A belongs to VB1 and branch 1 of Company B belongs to VB2. VB1 and VB2 share VCTRUNK1 (bound with five VC-12s) in one direction, and share VCTRUNK2 (bound with five VC-12s) in the other direction. Thus, VB1 (Company A) and VB2 (Company B) can share the 10 Mbit/s bandwidth dynamically. NE2 and NE3 work in the same way as NE1. In the EVPLAN service, any two nodes must be connected with the label switch path (LSP). |
|
|
Hardware configuration |
Configure an EFS0 and an ETF8 interface board in NE1. Use two Ethernet ports to access Ethernet services from branch 1 of Company A and from branch 1 of Company B. Configure an EFS0 and an ETF8 interface board in NE2. Use two Ethernet ports to access Ethernet services from branch 2 of Company A and from branch 2 of Company B. Configure an EFS0 and an ETF8 interface board in NE3. Use two Ethernet ports to access Ethernet services from branch 3 of Company A and from branch 3 of Company B. For slots of EFS0 and ETF8, refer to “Appendix A Network Configuration Requirements”. |
|
|
Service route |
NE 1 |
|
|
Company A |
VB1 [MAC1, VCTRUNK1 (MPLS label 1), VCTRUNK2 (MPLS label 1)] VLAN ID: 100 filtering table [MAC1, VCTRUNK1, VCTRUNK2] |
|
|
Company B |
VB2 [MAC2, VCTRUNK1 (MPLS label 2), VCTRUNK2 (MPLS label 2)] VLAN ID: 100 filtering table [MAC2, VCTRUNK1, VCTRUNK2] |
|
|
VUCTRUNK1 and VCTRUNK2 are bound with five VC-12s respectively. |
||
|
The configuration of NE2 and NE3 is the same as that of NE1. |
||
|
Protection |
The service can be protected by the SDH equipment. |
|
& Note:
You can apply the same principles to implementation of GE services except that the GE service requires EGS2 board and binding VCTRUNK to one or more VC-3s.
EVPLAN service supports dual isolation through VLAN ID and MPLS label, realizing service isolation among different users and different departments of one user.
The EVPLAN service realizes multi-point dynamic sharing of the Ethernet service. However, it requires the LSP between any two nodes to form a MESH network. In addition, the EVPLAN service can avoid the broadcast storm effectively.
The OptiX OSN 3500 supports the resilient packet ring (RPR), which can carry EVPL and EVPLAN services by adopting MPLS technology. In addition, the RPR not only ensures the quality of service (QoS), but also realizes bandwidth sharing, fairness and fast protection switching for services. This section introduces the application of EVPL and EVPLAN in the RPR.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.