HP B-series Embedded Switches Manual do Utilizador descarregar pdf (Página 203)

Troubleshooting

203Fabric OS Procedures Version 3.1.x/4.1.x User Guide

Fabric Segmentation

Possible Causes

Fabric Segmentation is generally caused by:

■ Incompatible fabric parameters. See “Restore a Segmented Fabric” on

page 204

■ The Core PID is not set. The Core PID is part of fabric parameters. See

“Procedures for Updating the Core PID Format” on page 154.

■ Incompatible zoning configuration. See “Fabric Merge Conflicts Related to

Zoning” on page 207.

■ Domain ID conflict. See “Reconcile a Domain ID Conflict” on page 205.

■ 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.

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:

■ 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

1 2 ... 198 199 200 201 202 203 204 205 206 207 208 ... 269 270

Sem comentários

HP B-series Embedded Switches Manual do Utilizador Página 203