PBB Features
Page 780 7750 SR OS Services Guide
MMRP Support Over B-VPLS SAPs and SDPs
MMRP is supported in B-VPLS instances over all the supported BVPLS SAPs and SDPs,
including the primary and standby pseudowire scheme implemented for VPLS resiliency.
When a B-VPLS with MMRP enabled receives a packet destined to a specific group BMAC, it
checks its own MFIB entries and if the group BMAC does not exist, it floods it everywhere. This
should never happen as this kind of packet will be generated at the I-VPLS/PBB PE when a
registration was received for a local I-VPLS group BMAC.
I-VPLS Changes and Related MMRP Behavior
This section describes the MMRP behavior for different changes in IVPLS.
1. When an ISID is set for a certain I-VPLS and a link to a related B-VPLS is activated (for
example, through the config>service>vpls>backbone-vpls vpls id:isid command), the
group BMAC address is declared on all B-VPLS virtual ports (SAPs or SDPs).
2. When the ISID is changed from one value to a new one, the old group BMAC address is
undeclared on all ports and the new group BMAC address is declared on all ports in the B-
VPLS.
3. When the I-VPLS is disassociated with the B-VPLS, the old group BMAC is no longer
advertised as a local attribute in the B-VPLS if no other peer B-VPLS PEs have it declared.
4. When an I-VPLS goes operationally down (either all SAPs/SDPs are down) or the I-VPLS is
shutdown, the associated group BMAC is undeclared on all ports in the B-VPLS.
5. When the I-VPLS is deleted, the group BMAC should already be un-declared on all ports in
the B-VPLS because the I-VPLS has to be shutdown in order to delete it.
Limiting the Number of MMRP Entries on a Per B-VPLS Basis
The MMRP exchanges create one entry per attribute (group BMAC) in the B-VPLS where MMRP
protocol is running. When the first registration is received for an attribute, an MFIB entry is
created for it.
Alcatel-Lucent’s implementation allows the user to control the number of MMRP attributes (group
BMACs) created on a per B-VPLS basis. Control over the number of related MFIB entries in the
B-VPLS FIB is inherited from previous releases through the use of the
config>service>vpls>mfib-table-size table-size command. This ensures that no B-VPLS will
take up all the resources from the total pool.
To Next Page
Loading...
