Peer information sync, End point status handling, End point mismatch – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 711: Hitless upgrade, Configuring mct vll, L2vpn peer configuration, Configuration considerations
Multi-Service IronWare Switching Configuration Guide
681
53-1003036-02
MCT for VLL
18
Peer information sync
If VLL information is already sent to the MCT peer and VLL peer is updated, then the VLL peer
information will sync to the MCT peer. VLL Peer information includes PW status and redundancy
status.
End point status handling
Whenever there are any end point status changes, they are synchronized by MCT infrastructure and
the events will be handled whenever logical status of endpoint changes from UP to DOWN or DOWN
to UP.
End point mismatch
When end points configured in MCT nodes belongs to different MCT Clients, then the end point
mismatch in both MCT nodes for that VLL and PWs for that VLL will be down.
Hitless upgrade
MCT VLL does not support Hitless upgrade, but is Hitless compatible.
Configuration Considerations
Brocade recommends making sure the VLL instance configuration is same on both nodes in the
following aspects:
•
Endpoint type(untagged or tagged or dual-tagged) and VLAN
•
VC type(tagged-mode or raw-mode)
•
Mtu and other operational parameters
•
Peers configured for a given VLL instance
Configuring MCT VLL
MCT VLL requires following cluster level configurations. See
“Configuring the cluster operation
for additioan information on creating clusters.
L2VPN peer configuration
For each MCT VLL instance, a spoke-PW session is formed internally using the l2vpn-peer
command to form a PW session to the remote MCT node. In this example, spoke-PW will be formed
to peer 2.2.2.2.
Brocade(config-mpls)#l2vpn-peer 2.2.2.2 rbridge-id 2
Syntax: [no] l2vpn-peer
The
The
To disable the configuration, enter the no form of the command.