The Ethernet services from city 2 (Company A and B) and city 3 (Company C) are to be converged to the central node in city 1, and interconnected with the Ethernet equipment at the backbone layer through the GE interface. Services of the three companies should be isolated from each other. The Ethernet equipment in city 1 supports MPLS.
The Ethernet services of Company A and B are output through FE electrical interfaces, and the service of Company C is output through the GE optical interface. All private line services share the bandwidth.
In this example, four EVPL services should be realized. The EVPL service between city 1 and city 2 can be realized by following the method in section 4.2.1 “Ingress/Egress”, and the bandwidth is shared. The EPL service between city 1 and city 3 can be realized by following the method in section 4.1.2 “Shared MAC”.
The service requirements in this example can also be realized by the OptiX OSN 3500 on the RPR. With the combination of RPR and MPLS technology, the EVPL service and bandwidth sharing can be realized, as shown in Figure 4-8.
NE1–NE4 in Figure 4-8 are all OptiX OSN 3500s. NE1, NE2 and NE3 are equipped with the RPR processing board to realize EVPL service. Set NE1, NE2 and NE3 as node 1, node 2 and node 3 on the RPR respectively.
Figure 4-8 EVPL application on RPR
|
Implementation |
Service type: EVPL Port route + VLAN route + MPLS route The service of Company A is accessed through an FE port in NE3. Services of two branches of Company B are accessed through another FE port in NE3 and isolated by VLAN ID. The service of Company C is accessed through a GE port in NE2. All services are converged in NE1, and then sent to the Ethernet equipment at the upper layer through a GE port. These services share a 155 Mbit/s bandwidth. |
|||
|
Hardware configuration |
Configure an EMR0 board in NE1 to converge services and to interconnect with Ethernet equipment at upper layer through a GE port. Configure an EMR0 board in NE2 to access GE service from Company C. Configure an EMR0 board in NE3 to access Ethernet services from Company A and B.
The board configured in each node on the RPR shall be the same RPR processing board. For slots of EMR0, refer to “Appendix A Network Configuration Requirements”. & Note: EMR0 can be inserted in all service slots with the interface board. However, it supports 8 x VC-4 bandwidth only in the 2.5 Gbit/s slot. Its maximum bandwidth is 4 x VC-4 when inserted in a 1.25 Gbit/s slot. |
|||
|
Service route |
NE1 |
NE2 |
NE3 |
|
|
Company A: EVPL 1 |
MAC1 (GE port) + MPLS label 1 ïð RPR1 port + MPLS label 1 RPR sink node: 3 |
— |
MAC2 (FE port 1 ïð RPR1 port + MPLS label 1 RPR sink node: 1 |
|
|
Company B: EVPL 2 |
MAC1 (GE port) + MPLS label 2 + VLAN ID: 100 ïð RPR1 port + MPLS label 2 + VLAN ID: 100 RPR sink node: 3 |
— |
MAC3 (FE port 2) ïð RPR1 port + MPLS label 2 + VLAN ID: 100 RPR sink node: 1 |
|
|
Service route |
Company B: EVPL 3 |
MAC1 (GE port) + MPLS label 2 + VLAN ID: 200 ïð RPR1 port + MPLS label 2 + VLAN ID: 200 RPR sink node: 3 |
— |
MAC3 (FE port 2) ïð RPR1 port + MPLS label 2 + VLAN ID: 200 RPR sink node: 1 |
|
Company C: EVPL 4 |
MAC1 (GE port) + MPLS label 3 ïð RPR1 port + MPLS label 3 RPR sink node: 2 |
MAC1 (GE port) ïð RPR1 port + MPLS label 3 RPR sink node:1 |
— |
|
|
The RPR1 port shares a 155 Mbit/s bandwidth. |
||||
|
Protection |
The RPR realizes the protection for the EVPL service through two modes: Wrapping and Steering. Perform Wrapping for general protection switching at the beginning, and then perform Steering when the new topology and service path are established. Then no packet will be lost during protection switching and the switching time is shortened. |
|||
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.
Caution: