Configuring the vlag ignore split option – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 412

380
Network OS NETCONF Operations Guide
53-1003231-02
Configuring the vLAG ignore split option
26
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1004">
<get-port-channel-info-by-intf xmlns="urn:brocade.com:mgmt:brocade-lag">
<lacp>
<interface-type>tengigabitethernet</interface-type>
<interface-name>1/0/21</interface-name>
<actor-port>0x18150014</actor-port>
<admin-key>10</admin-key>
<oper-key>0</oper-key>
<actor-system-id>01-e0-52-00-01-00</actor-system-id>
<partner-system-id>01-80-c2-00-00-01</partner-system-id>
<system-priority>32768</system-priority>
<partner-oper-priority>32768</partner-oper-priority>
<actor-priority>32768</actor-priority>
<receive-machine-state>current</recieve-machine-state>
<periodic-transmission-machine-state>slow-periodic
</periodic-transmission-machine-state>
<mux-machine-state>collecting-distributing</mux-machine-state>
<admin-state>activity aggregation defaulted</admin-state>
<oper-state>activity aggregation synchronization collecting
distributing</oper-state>
<partner-oper-state>activity aggregation synchronization collecting
distributing</partner-oper-state>
<partner-oper-port>100</partner-oper-port>
</lacp>
</get-port-channel-info-by-intf>
</rpc-reply>
Configuring the vLAG ignore split option
This procedure is for LACP-based vLAGs. The scope of this configuration is per port-channel. In
scenarios where the vLAG spans more than one node, it minimizes the extent of packet loss in the
event of one of the nodes in the vLAG going down.
In a case where connectivity between nodes is lost due to a fabric split (as opposed to one of its
members going down), duplication of multicast/broadcast packets will occur.
Brocade recommends that you build redundancy in the fabric so that individual links are not single
points of failure.
displays a dual vLAG configuration with three legs of RB2, RB3, and RB4. If RB2, RB3, or
RB4 reboots while Host-1 is communicating to Host-2 or Host3, a momentary traffic disruption may
occur.