Fabric Segmentation; Possible Causes; About Fabric Parameters - HP StorageWorks MSA 2/8 - SAN Switch User Manual

Fabric Segmentation

Possible Causes

Fabric Segmentation is generally caused by:

About Fabric Parameters

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 may 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.
Mandatory Identical Settings
The following fabric parameters must be identical for a fabric to merge:
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Incompatible fabric parameters. See
page 204
The Core PID is not set. The Core PID is part of fabric parameters. See
"Procedures for Updating the Core PID
Incompatible zoning configuration. See
Zoning" on page 207.
Domain ID conflict. See
A switch in a secure fabric is not running Secure Fabric OS. Refer to the HP
StorageWorks Secure Fabric OS Version 1.0 User Guide.
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
"Restore a Segmented
Format" on page 154.
"Fabric Merge Conflicts Related to
"Reconcile a Domain ID
Troubleshooting
Fabric" on
Conflict" on page 205.
203