A SAN administrator created a new zone for a server to access new LUNs on an existing storage array. The server administrator rescans the server bus and reports that they cannot find the storage that

The statement that 'the server ports are logged into the fabrics' implies basic HBA functionality and compatibility with the SAN switches, making an unqualified vendor HBA an unlikely cause for the LUN discovery issue.

In Fibre Channel SAN environments, creating or modifying zoning rules often requires an explicit step to 'commit' or 'activate' the new configuration to the active running configuration of the SAN switches. If the SAN administrator created the zone but failed to commit these changes, the new zoning rules would not be enforced, preventing the server's HBA from discovering the allocated LUNs despite being logged into the fabric.

While a server reboot can sometimes help with storage discovery, a bus rescan is usually sufficient for new LUN discovery after SAN zoning changes. The problem here is with the SAN's configuration activation, not the server's ability to discover changes once they are active.

The verification that 'the server ports are logged into the fabrics' confirms that the server's HBAs are physically connected and communicating with the SAN switches, ruling out incorrect cabling as the root cause of the LUN discovery failure.