Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 774)

750 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
VRRP/VRRP-E support
7
3. Configuration check that disallows a VE over VPLS with a PBB configuration.
In this example, an error message is displayed when the user tries to enable both VE over VPLS and
PBB in the same VPLS instance.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls vinst 2000
Brocade(config-mpls-vpls-vinst)# router-interface ve 3
Brocade(config-mpls-vpls-vinst)# pbb
Error - VE over VPLS and PBB cannot be enabled on the same VPLS instance.
Brocade(config)# router mpls
Brocade(config-mpls)#vpls vinst 2000
Brocade(config-mpls-vpls-vinst)# pbb
Brocade(config-mpls-vpls-vinst)# router-interface ve 3
Error - VE over VPLS and PBB cannot be enabled on the same VPLS instance.
4. Configuration check that disallows a VE over VPLS with a MCT configuration.
In this example, the user cannot enable both VE over VPLS and MCT in the same VPLS instance.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls vinst 2000
Brocade(config-mpls-vpls-vinst)# router-interface ve 3
Brocade(config-mpls-vpls-vinst)# cluster-peer 10.10.10.10
Error - VE over VPLS and MCT cannot be enabled on the same VPLS instance.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls vinst 2000
Brocade(config-mpls-vpls-vinst)# cluster-peer 10.10.10.10
Brocade(config-mpls-vpls-vinst)# router-interface ve 3
Error - VE over VPLS and MCT cannot be enabled on the same VPLS instance.
VRRP/VRRP-E support
VRRP/VRRP-E is supported for routing over VPLS. The following VRRP/VRRP-E functionality is
expected when using it in a routing over VPLS configuration. VRRP/e functionality expects VPLS full
mesh configuration in which each VPLS peer is connected to all other VPLS peers in a given VPLS
instance.
VRRP/VRRP-E control message flow
VRRP/VRRP-E control messages are sent over VE over VPLS interface as regular VE interface. The
VRRP/VRRP-E messages received from remote peers are forwarded to endpoints, but not to other
remote peers. Once a node is selected as master, it sends out regular gratuitous ARPs with a
VRRP/VRRP-E MAC address as the MAC for the gateway IP, causing all the endpoints and remote
peers (of other instances) to learn the master MAC address.
VRRP backup
The backup learns the master virtual MAC as a regular Layer 2 MAC. Traffic from the backup to the
master is Layer 2 switched.
VRRP-E master
Traffic from is routed from the VRRP-E master, based on the destination IP address.