Академический Документы
Профессиональный Документы
Культура Документы
General
Topology
|--------PE12----- -------PE11----|
CE01 MPLS Backbone CE02
|--------PE14----- -------PE17----|
Configuration
PE12
PE14
PE11
PE17
Juniper Internal
swap;
vlan-id 952;
}
output-vlan-map swap;
family vpls;
Verification
PE12 (primary PE for site 1)
Conclusion
Juniper Internal
if we look in detail the verification section above, we will see that:
o both primary and backup PE on local site setup pseudowire to the _primary PE on remote
site
o both primary and backup PE on local site put pseudowire to the _backup PE on remote site
as standby
o show mac table shows that primary PE will learn mac address from local PE-CE interface and
also from lsi interface which represent pseudowire to remote site
o on the other hand, backup PE only learn mac address from local PE-CE interface only.
this is because there is no return pseudowire connection from remote primary PE to
the local backup PE.
this is to prevent layer 2 domain looping.
unlike BGP-based VPLS, in LDP-based VPLS, it is the remote PE that decide which local PE that
become primary and which one become backup
It is recommended that on local PE, both PE has consistent configuration, which means, refer to
example above:
o if PE12 choose PE11 as remote primary PE, PE14 must do the same.
o the same thing from other side, if PE11 choose PE12 as primary, PE17 must choose PE12 as
primary as well.
Misc
we are using different vlan between site 1 and site 2, therefore, vlan conversion is required.
o at site 1, we use "vlan-id" knob within routing-instance stanza
o at site 2, we use input/output vlan mapping within logical interface stanza
Juniper Internal