User Manual

186 Troubleshooting
3. Resolve zoning conflicts by putting the devices into the same zoning configuration.
See ”Correcting zoning setup issues” on page 187 for additional information.
Restoring a segmented fabric
Fabric segmentation is generally caused by:
Incompatible fabric parameters (see ”To reconcile fabric parameters individually:” on page 186).
Incorrect PID setting (see ”Configuring the PID format” on page 203).
Incompatible zoning configuration (see ”To check for zoning problems:” on page 185).
Domain ID conflict (see ”To reconcile a domain ID conflict:” on page 187).
A switch in a secure fabric is not running Secure Fabric OS.
Refer to the HP StorageWorks Secure Fabric OS user guide for additional information.
There are a number of settings that control the overall behavior and operation of the fabric. Some of
these values, such as the domain ID, are assigned automatically by the fabric and can differ from one
switch to another in the fabric. Other parameters, such as the BB credit, can be changed for specific
applications or operating environments, but must be the same among all switches to allow the formation
of a fabric.
The following fabric parameters must be identical for a fabric to merge:
R_A_TOV
E_D_TOV
Data field size
Sequence level switching
Disable device probing
Suppress class F traffic
VC encoded address mode
Per-frame route priority
long-distance fabric (not necessary on Bloom-based fabrics)
BB credit
Core PID
To reconcile fabric parameters individually:
1. Log in to one of the segmented switches as admin.
2. Issue the configshow command.
3. Open another telnet session and log in to another switch in the same fabric as admin.
4. Issue the configshow command.
5. Compare the two switch configurations line by line and look for differences. Do this by comparing the
two telnet windows, or by printing the configshow output.
6. Connect to the segmented switch after the discrepancy is identified.
7. Disable the switch by entering the switchdisable command.