286 Troubleshooting
To check for zoning problems
1.
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 see each other).
2.
Confirm that the specific edge devices that need to communicate with each other are in the same zone.
• 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 on the host and target to determine whether or not the
Name Server is aware that these devices are zoned together
• If they are not in the same zone and zoning is enabled, proceed to
step 3
.
3.
Resolve zoning conflicts by putting the devices into the same zoning configuration.
Refer to ”
Correcting zoning setup issues
” on page 287 for additional information.
Restoring a segmented fabric
Fabric segmentation is generally caused by:
•
Incompatible fabric parameters (refer to ”
To reconcile fabric parameters individually
” on page 286).
•
Incorrect PID setting (refer to ”
Configuring the PID format
” on page 381).
•
Incompatible zoning configuration (refer to ”
To check for zoning problems
” on page 286).
•
Domain ID conflict (refer to ”
To reconcile a domain ID conflict
” on page 287).
•
A switch in a secure fabric is not running Secure Fabric OS.
Refer to the
Secure Fabric OS Administrator’s 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
•
Per-frame route priority
•
Long distance fabric (not necessary on Bloom-based fabrics)
•
BB credit
•
PID format
To reconcile fabric parameters individually
1.
Log in to one of the segmented switches as admin (switch A).
2.
Enter the
configShow
command.
3.
Log in to another switch (switch B) in the same fabric as admin.
4.
Enter 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. Also verify that the fabric parameter
settings (see ”
Restoring a segmented fabric
” on page 286) are the same for
both
switches.
6.
Connect to the segmented switch after the discrepancy is identified.
7.
Disable the switch by entering the
switchDisable
command.
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......