Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 712)

682 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
MCT for VLL
18
VLL global pw-redundancy (optional)
Once MCT is enabled for a VLL instance, the two MCT cluster nodes synchronize the configuration
with each other over the CP and decide which node will take up the Active role and Standby role.
PW redundancy support provides is backup PWs ready so that traffic can be quickly failed over to
the backup PWs. This command can be configured either globally for all VLL instances with MCT or
for each VLL instance individually.
NOTE
If it is not configured, the MCT node with lower rbridge-id will be elected as Active to signal to the
remote PE’s.
Use the vll-pw-redundancy-active command at the global mode to set the pw-redundancy option for
all VLL Instances with MCT.
Brocade(config-cluster-PE1-client-2)# rbridge-id 101
Brocade(config-cluster-PE1-client-2)# client-interface ethernet 1/1
Brocade(config-cluster-PE1-client-2)# vll-pw-redundancy-active
Brocade(config-cluster-PE1-client-2)# deploy
Syntax: [no] vll-pw-redundancy-active
The no form of this command removes the pw redundancy option.
Per VLL instance pw-redundancy (optional)
If vll-pw-reduncancy-active is not configured per VLL instance, the selection will be based on the
global configuration. The per VLL Instance configuration always has the higher priority over global
configuration.
Vll-pw-redundancy-active option is used to load-balance VLL instances using client (for one client
VLLs, one node is active and for other client, another MCT node can be active).
All VLL instances will not be active only on one node. This allows flexibility to provision VLL
instances for each client differently.
When the client is deployed, all VLL instances that share the same MCT end-point(port e 1/1 in the
example) will become MCT VLLs.
When the client configuration is un-deployed the VLL instance will be brought down and up without
MCT.
The vll-pw-redundancy-active option if configured cannot be changed without un-deploying the
client.
For VLL, two remote peers (remote MCT cluster pair) must be configured to support PW
redundancy. In the configuration below, 3.3.3.3 and 4.4.4.4 are peers to reach remote node.
Brocade(config-mpls)#vll test 10
Brocade(config-mpls-vll-test)#vll-peer 3.3.3.3 [4.4.4.4]
Brocade(config-mpls-vll-test)#vll-pw-redundancy-active
Syntax: [no] vll-pw-redundancy-active
The no form of this command removes the pw redundancy option.
If only one peer is specified, the PW redundancy status TLV with local status as active is supported.