HP Surestore 6164 Switch - Manual (Page 20)

3-8 Zoning User’s Guide
Using Zoning
3
In the simplest case, where both fabrics have identical zone configuration data and the same
configuration enabled, the fabrics join to make one larger fabric with the same zone configuration
enabled across the new fabric.
If the fabrics have different zone configuration data, the two sets of zone configuration data are
merged if possible. If not possible, the ISL is segmented. A merge is not possible if any of the
following exist:
Configuration mismatch Zoning is enabled in both fabrics and the zone configurations that
are enabled are different in each fabric.
Type mismatch The name of a zone object in one fabric is used for a different type
of zone object in the other fabric.
Content mismatch The definition of a zone object in one fabric is different from the
definition of zone object with the same name in the other fabric.
Transactional Model
Zoning commands are executed under the transactional model. A working copy of defined
configurations is created by copying all information from zone or cfg lists at the start of a
transaction.
The following commands are issued to open a transaction:
•
cfgCreate
•
cfgAdd
•
cfgDelete
•
cfgRemove
The following commands are issued to end a transaction:
•
cfgSave
•
cfgEnable
•
cfgDisable
When a transaction is opened, all new zoning information is placed in a transactional buffer. Unless
the transaction is closed, the new changes are not applied to the fabric. A transaction is aborted by
the cfgTransAbort, or when another switch closes its transaction.When a transaction is closed,
all new (form the transactional buffer) and existing zoning information is saved to memory and
applied to the fabric.