Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Defining the Proxy Load-Balancing Algorithm
When the QFX Series is configured as an FCoE-FC gateway, it balances the FCoE session load assigned to each NP_Port link between the gateway and the FC switch in the FC SAN to avoid overloading or underutilizing each link. The QFX Series supports two types of load-balancing mechanisms:
- Simple load balancing—Load balancing is based on the weighted utilization (load) of the NP_Ports connected to an FC fabric. Each new ENode fabric login (FLOGI) or VN_Port fabric discovery (FDISC) session is assigned to the least-loaded link. This means that an FDISC session initiated by the VN_Port on an ENode might not be assigned to the same link as the parent ENode’s FLOGI session. Simple load balancing is the default algorithm.
- ENode-based load balancing—Load balancing is based on ENode FLOGIs. When an ENode logs in to the fabric, all subsequent VN_Port FDISC sessions associated with that ENode are placed on the same link as the ENode FLOGI session, regardless of the link load. New ENode FLOGIs are placed on the least-loaded link.
To define the proxy load-balancing algorithm for a proxy fabric on the FCoE-FC gateway, set the algorithm as either enode-based or simple:
[edit fc-fabrics fabric-name proxy]
user@switch# set load-balance-algorithm (enode-based | simple)For example, to configure a gateway fabric named san_fab1 to use enode-based load balancing:
user@switch# set fc-fabrics san_fab1 rproxy load-balance-algorithm enode-based
