HP 6125XLG R2306-HP 6125XLG Blade Switch FCoE Configuration Guide - Page 83

Zone merge rules, Access control, FC zone configuration task list

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 83 highlights

NOTE: Consistent active zone sets among switches can be achieved by a merge. Consistent zone databases achieved after a merge, however, require all participating switches to be configured with complete merge. Zone merge rules Table 3 Zone merge rules Local database Neighbor database Merge status The databases contain zone sets with the same name, but zones in these zone sets have different names. Successful The databases contain zone sets with different names. Successful The databases contain zones or zone aliases with different names. Successful The databases contain zones or zone aliases with the same name but different member ports. Failed Empty Contain data Successful Contain data Empty Successful Merge result The union of the local database and neighbor database. Zone sets with the same name are merged. The union of the local database and neighbor database. All zone sets with different names are retained. The union of the local database and neighbor database. All zone sets or zone aliases with different names are retained. Both databases remain unchanged. The neighbor database overwrites the local database. The local database overwrites the neighbor database. NOTE: • If two switches have active zone sets with different names, the larger name obtained by comparison of strings serves as the name of the active zone set after merging. • If the active zone sets on two switches fail to merge, the two switches isolate their connecting link by bringing down the relevant ports in the VSAN, in addition to keeping their zone databases unchanged. Access control If a server wants to access a disk through the name service, the server needs to determine whether the server and the disk are in one zone of the active zone set. Members in the same zone can access each other. Otherwise, they cannot access each other. FC zone configuration task list Tasks at a glance (Optional.) Configuring zone aliases (Required.) Configuring zones (Required.) Configuring zone sets 77

  • 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
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
77
NOTE:
Consistent active zone sets among switches can be achieved by a merge. Consistent zone databases
achieved after a merge, however, require all participating switches to be configured with complete merge.
Zone merge rules
Table 3
Zone merge rules
Local database
Neighbor database
Merge status
Merge result
The databases contain zone sets with the same name,
but zones in these zone sets have different names.
Successful
The union of the local database
and neighbor database. Zone sets
with the same name are merged.
The databases contain zone sets with different names.
Successful
The union of the local database
and neighbor database. All zone
sets with different names are
retained.
The databases contain zones or zone aliases with
different names.
Successful
The union of the local database
and neighbor database. All zone
sets or zone aliases with different
names are retained.
The databases contain zones or zone aliases with the
same name but different member ports.
Failed
Both databases remain
unchanged.
Empty
Contain data
Successful
The neighbor database overwrites
the local database.
Contain data
Empty
Successful
The local database overwrites the
neighbor database.
NOTE:
•
If two switches have active zone sets with different names, the larger name obtained by comparison of
strings serves as the name of the active zone set after merging.
•
If the active zone sets on two switches fail to merge, the two switches isolate their connecting link by
bringing down the relevant ports in the VSAN, in addition to keeping their zone databases unchanged.
Access control
If a server wants to access a disk through the name service, the server needs to determine whether the
server and the disk are in one zone of the active zone set. Members in the same zone can access each
other. Otherwise, they cannot access each other.
FC zone configuration task list
Tasks at a glance
(Optional.)
Configuring zone aliases
(Required.)
Configuring zones
(Required.)
Configuring zone sets