FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 227
Both of these changes are service affecting. Other changes will not be service
affecting.
5.11 BGP VPLS
The Nokia BGP VPLS solution, compliant with RFC 4761, is described in this section.
Figure 29 depicts the service representation for BGP VPLS mesh.
Figure 29 BGP VPLS Solution
The major BGP VPLS components and the deltas from LDP VPLS with BGP AD are
explained below:
• Data plane is identical with the LDP VPLS solution: for example, VPLS instances
interconnected by pseudowire mesh. Split horizon groups may be used for loop
avoidance between pseudowires.
• Addressing is based on two (2) bytes VE ID assigned to the VPLS instance.
• BGP-AD for LDP VPLS: 4 bytes VSI-ID (system IP) identifies the VPLS instance.
• The target VPLS instance is identified by the Route Target (RT) contained in the
MP-BGP advertisement (extended community attribute).
• BGP-AD: a new MP-BGP extended community is used to identify the VPLS. RT is
used for topology control.
24383
CE2
CE1
CE5
CE3
CE4
PE4PE3
PE1PE2
Service
Provider
Network
A2 A1
A3
A5
VE BI Size (2)
Label Base (3)
VE ID (2) VE BI Off (2)
Route Distinguisher (8 octets)
BGP VPLS
Legend:
VPLS
VPLS
VPLS
VPLS
To Next Page
Loading...
