A Linux application server is being added to an existing dual-fabric Fibre Channel SAN. Each new 32 Gb FC HBA port is cabled to a separate switch, and every switch port shows an active 32 Gb link. Two boot LUNs have already been mapped to the server's worldwide port names on the storage array, but the operating system still reports no available disks on either path. Which of the following configuration tasks will MOST likely allow the server to detect the new LUNs?
Create single-initiator zones on each switch that include the server WWPNs and the storage-array WWPNs.
Configure dynamic LACP between the two HBA ports and the FC switches.
Assign a unique iSCSI qualified name (IQN) to each HBA in the server.
Enable jumbo frames on the FC switches and the storage-array ports.
On a switched Fibre Channel fabric, devices cannot communicate until they belong to at least one common zone. Even when LUNs are presented on the storage array and the physical links are up, the server's initiator ports will not see-or be able to log in to-the target ports until the FC switches contain a zone (or zones) that include both sets of WWPNs. Creating single-initiator, single-target zones on each fabric therefore enables the FLOGI/PLOGI exchange between the server and the array, after which the OS can scan and discover the mapped LUNs. Jumbo frames and LACP are Ethernet features that have no effect on Fibre Channel traffic, and an iSCSI qualified name is irrelevant to native FC HBAs.