Users Guide

System log messages are received when the system closes a session for rebalancing. The log message provides the Fabric id,
VLAN Id, FCoE MAC and the reason for termination.
Load balancing after system reboot
After reboot, upstream FC connections to the end-devices become operational first and carry more sessions than the other
upstream FC connections to SAN. This requires load balancing. You can address load balancing in the following ways:
● After reboot, check the system state and trigger rebalance using the CLI.
● Configure the delay fcf-adv timer. The delay timer starts when a new FC upstream interface is available. When the timer
expires, the upstream connection and the other available connections become operational. This configuration ensures that
there is enough time for all upstream connections to become operational before processing the session requests from end
devices. Depending on the topology, you can decide the timeout value.
NPG rebalance topology
The NPG rebalance topology has an OS10 switch operating in NPG mode and two FC upstream interfaces (fc 1/1/1 and fc
1/1/2) having a speed of 16 G.
Two FCoE end points (C NAs) are attached to ports eth 1/1/54 and eth 1/1/55, which carry the FCoE traffic. FC end points
(HBAs) are attached to ports fc 1/1/9 and fc 1/1/10, and they carry pure FC traffic.
Both the FCoE traffic and FC traffic need to be balanced across the FC upstream interfaces (fc 1/1/1 and fc 1/1/2) available in
the NPG switch.
Use the information in the following sections to configure an NPG switch:
NPG switch configurations
Enable NPG mode of operation
OS10# show fc switch
Switch Mode : Disabled
Switch WWN :
OS10(config)# feature fc npg
OS10# show fc switch
Switch Mode : NPG
Switch WWN : 10:00:14:18:77:20:73:cf
OS10#
Fibre Channel
365