We use (by default) the source/destination/OXID id loadbalancing. The OXID is the exchange identifier in a fibre channel frame. Most of the time, a new exchage ID will be used when a device goes and gets a different set of data...whether that is a block of data or recognizes it as a different file, whatever depending on the driver in the initiator. So, then we will spread these sessions across the portchannel. We don't do a per-packet LB like CEF can be configured to do on the IP side. If you want to compare it to IP, we LB each TCP session down a different physical path.
