• If the device is listed in the NS, the problem is between the storage device and the host. There may
be a zoning mismatch or a host/storage issue. Proceed to
Enter the portLoginShow command to check the port login status.
Enter the fcpProbeShow command to display the FCP probing information for the devices attached to
the specified F_Port or L_Port. This information includes the number of successful logins and SCSI
INQUIRY commands sent over this port and a list of the attached devices.
Check the port log to determine whether or not the device sent the FLOGI frame to the switch, and the
switch probed the device.
To check for zoning problems:
Enter the cfgActvShow command to determine if zoning is enabled.
If zoning is enabled, it is possible that the problem is being caused by zoning enforcement (for
example, two devices in different zones cannot detect each other).
If zoning is disabled, check the default zone mode by entering the defzone –show command. If it is
no access, change it to all access. To modify default zone mode from no access to all access, enter the
defzone –all command, and then the cfgsave command.
Confirm that the specific edge devices that must communicate with each other are in the same zone.
• If they are not in the same zone and zoning is enabled, proceed to
• If they are in the same zone, perform the following tasks:
• Enter the portCamShow command on the host port to verify that the target is present.
• Enter the portCamShow command on the target.
• Enter the nsZoneMember command with the port ID for the zoned devices on the host and
target to determine whether the name server is aware that these devices are zoned together.
Resolve zoning conflicts by putting the devices into the same zoning configuration.
Enter the defzone -- show command to display the current state of the zone access mode and the
access level. The defzone command sets the default zone access mode to No Access
switch:admin> defzone --show
Default Zone Access Mode
committed - No Access
transaction - No Transaction
"Correcting zoning setup
Restoring a segmented fabric
Fabric segmentation is generally caused by:
Incompatible fabric parameters (see
Incorrect PID setting (see
Incompatible zoning configuration.
If fabric segmentation is caused by "zone conflict", verify following:
• The activate cfg (zone set) on each end of segmented ISL must be same.
• Any zone object with the same name must have same the type and contents.
If fabric segmentation is caused by and "incompatible zone database", check following:
• Whether the merge results in an over limit zone database? Different FOS versions support different
zone database sizes, for example pre FOS-v5.2 supports 256Kbytes and FOSv5.2 and later
• Whether any port number greater than 255 is configured in a port zone? Any pre FOS-v5.2 switch
will not merge with a newer switches with a port index greater than 255.
Domain ID conflict (see
A switch in a secure fabric not running Secure Fabric OS.
See the Secure Fabric OS Administrator's Guide for additional information.
issues" on page 309 for additional information.
"To reconcile fabric parameters
"Configuring the PID
Format" on page 489).
"To reconcile a domain ID
"To check for zoning
individually:" on page 308).
conflict:" on page 308).
Fabric OS 6.x administrator guide 307