HP StorageWorks 16-EL zoning version 2.6.1 user guide - Page 24

Transactional Model

Page 24 highlights

Using Zoning Configuration mismatch Type mismatch Content mismatch Zoning is enabled in both fabrics and the zone configurations that are enabled are different in each fabric. The name of a zone object in one fabric is used for a different type of zone object in the other fabric 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. Issue the following commands to open a transaction: ■ aliAdd ■ aliCreate ■ aliDelete ■ aliRemove ■ cfgAdd ■ cfgCreate ■ cfgDelete ■ cfgRemove ■ qloopAdd ■ qloopCreate ■ qloopDelete ■ qloopRemove ■ zoneAdd ■ zoneCreate ■ zoneDelete 24 HP StorageWorks Zoning Version 2.6.1 User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76

Using Zoning
24
HP StorageWorks Zoning Version 2.6.1 User Guide
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.
Issue the following commands to open a transaction:
aliAdd
aliCreate
aliDelete
aliRemove
cfgAdd
cfgCreate
cfgDelete
cfgRemove
qloopAdd
qloopCreate
qloopDelete
qloopRemove
zoneAdd
zoneCreate
zoneDelete
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.