This requires the configuration in the M-VPLS, under vpls-group, of the following attributes: VLAN ranges, vpls-template and vpls-sap-template bindings. As soon as the VPLS group is enabled, the configured attributes are used to auto-instantiate, on a per-VLAN basis, a VPLS FDB and related SAPs in the switches and on the ‟trunk ports” specified in the M-VPLS context. The trunk ports are ports associated with an M-VPLS SAP not configured as an end-station.
The following procedure is used.
The vpls-template binding is used to instantiate the VPLS instance where the service ID is derived from the VLAN value as per service-range configuration.
The vpls-sap-template binding is used to create dot1q SAPs by deriving from the VLAN value the service delimiter as per service-range configuration.
The above procedure may be used outside of the MVRP context to pre-provision a large number of VPLS contexts that share the same infrastructure and attributes.
The MVRP control of the auto-instantiated services can be enabled using the mvrp-control command under the vpls-group.
If mvrp-control is disabled, the auto-created VPLS instances and related SAPs are ready to forward.
If mvrp-control is enabled, the auto-created VPLS instances are instantiated initially with an empty flooding domain. According to the operator configuration the MVRP exchanges gradually enable service connectivity – between configured SAPs in the data VPLS context.
This also provides protection against operational mistakes that may generate flooding throughout the auto-instantiated VLAN FDBs.
From an MVRP perspective, these SAPs can be either ‟full MVRP” or ‟end-station” interfaces.
A full MVRP interface is a full participant in the local M-VPLS scope as described below.
VLAN attributes received in an MVRP registration on this MVRP interface are declared on all the other full MVRP SAPs in the control VPLS.
VLAN attributes received in an MVRP registration on other full MVRP interfaces in the local M-VPLS context are declared on this MVRP interface.
In an MVRP end-station interface, the attributes registered on that interface have local significance, as described below.
VLAN attributes received in an MVRP registration on this interface are not declared on any other MVRP SAPs in the control VPLS. The attributes are registered only on the local port.
Only locally active VLAN attributes are declared on the end-station interface; VLAN attributes registered on any other MVRP interfaces are not declared on end-station interfaces.
Also defining an M-VPLS SAP as an end-station does not instantiate any objects on the local switch; the command is used just to define which SAP needs to be monitored by MVRP to declare the related VLAN value.
The following example describes the M-VPLS configuration required to auto-instantiate the VLAN FDBs and related trunks in non-PBB switches.
mrp
— no shutdown
— mmrp
— shutdown
— mvrp
— no shutdown
sap 1/1/1:0
— mrp mvrp
— no shutdown
sap 2/1/2:0
— mrp mvrp
— no shutdown
sap 3/1/10:0
— mrp mvrp
— no shutdown
vpls-group 1
— service-range 100-2000
— vpls-template-binding Autovpls1
— sap-template-binding Autosap1
— mvrp-control
— no shutdown
A similar M-VPLS configuration may be used to auto-instantiate the VLAN FDBs and related trunks in PBB switches. The vpls-group command is replaced by the end-station command under the downward-facing SAPs as in the following example.
config>service>vpls control-mvrp m-vpls create customer 1
— [..]
— sap 1/1/1:0
— mvrp mvrp
— endstation-vid-group 1 vlan-id 100-2000
— no shutdown