Limitations - Lenovo CN4093 Application Manual

Limitations

316
CN4093 Application Guide for N/OS 8.3
 automated - triggers a disruptive load-balance among the logged-in nodes in
case of any future imbalances that are caused by Fibre Channel uplink flapping
or introduction of new Fibre Channel uplink. If the Fibre Channel port is part of
a NPV VLAN and is traffic-mapped, the load-balancing algorithm will assess
the load on existing links and redistribute Enodes to the new uplink if necessary.
The CLI for this option is:
CN 4093(config-vlan)# [no] npv auto-disruptive-load-balance enable
Note: This option triggers a disruptive load-balance 60 seconds after the FC
port came online. If any uplinks are flapping in the configured VLAN,
the disruptive load-balance will not be triggered.
Note: The automated option will only take care of the imbalances caused by
Fibre Channel uplinks flapping, not Enodes flapping. In the later case,
manual load-balance command should be used.
Note: To check which VLANs are have automated disruptive load-balancing
enabled, use the following command:
CN 4093(config-vlan)# show npv auto-disruptive-load-balance
The load-balancing is disruptive in nature as few devices are forced to logout and
initiate a re-login. The switch attempts to limit disruption by moving the fewest
nodes necessary.
Only Emulex CNAs participate in load-balancing. FCoE targets (Ex: V7000) are not
load-balanced.
Other CNAs (such as Qlogic) store FCF information and try to login to the same
FCF (uplink), so they are not balanced. Servers with AIX Operating Systems also
can't be load-balanced for this reason.