HP Surestore 64 HP Enterprise Connectivity Fabric Manager User's Guide - Page 75

The connection is bound to a storage port WWN. If the fiber-optic cable is disconnected

Page 75 highlights

data loss or corruption by controlling access between devices or between separate user groups (such as engineering or human resources). Server-level access control is called persistent binding. Persistent binding uses configuration information stored on the server and is implemented through the server's host bus adapter (HBA) driver. The process binds a server device name to a specific Fibre Channel storage volume or logical unit number (LUN), through a specific HBA and storage port WWN. In essence, this feature creates a reliable route across the fabric that sustains the small computer system interface (SCSI) connection between a server and storage device. For persistent binding: • Each server HBA is explicitly bound to a storage volume or LUN, and access is explicitly authorized (access is blocked by default). • The process is compatible with open system interconnection (OSI) standards. The following are transparently supported: - Different operating systems and applications. - Different storage volume managers and file systems. - Different fabric devices, including disk drives, tape drives, and tape libraries. • If the server is rebooted, the server-to-storage connection is automatically re- established. • The connection is bound to a storage port WWN. If the fiber-optic cable is disconnected from the storage port, the server-to-storage connection is automatically re-established when the port cable is reconnected. The connection is also automatically re-established if the storage port is cabled through a different managed product port. Access can also be controlled at the storage device as an addition or enhancement to redundant array of independent disks (RAID) controller software. Data access is controlled within the storage device, and server HBA access to each LUN is explicitly limited (access is blocked by default). Storage-level access control: • Provides control at the storage port and LUN level, and does not require configuration at the server. Overview 57 Fabric Zoning

  • 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
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242

Overview
57
Fabric Zoning
data loss or corruption by controlling access between devices or between separate user
groups (such as engineering or human resources).
Server-level access control is called persistent binding. Persistent binding uses
configuration information stored on the server and is implemented through the server
s
host bus adapter (HBA) driver. The process binds a server device name to a specific Fibre
Channel storage volume or logical unit number (LUN), through a specific HBA and storage
port WWN. In essence, this feature creates a reliable route across the fabric that sustains
the small computer system interface (SCSI) connection between a server and storage
device.
For persistent binding:
Each server HBA is explicitly bound to a storage volume or LUN, and access is explicitly
authorized (access is blocked by default).
The process is compatible with open system interconnection (OSI) standards. The
following are transparently supported:
Different operating systems and applications.
Different storage volume managers and file systems.
Different fabric devices, including disk drives, tape drives, and tape libraries.
If the server is rebooted, the server-to-storage connection is automatically re-
established.
The connection is bound to a storage port WWN. If the fiber-optic cable is disconnected
from the storage port, the server-to-storage connection is automatically re-established
when the port cable is reconnected. The connection is also automatically re-established
if the storage port is cabled through a different managed product port.
Access can also be controlled at the storage device as an addition or enhancement to
redundant array of independent disks (RAID) controller software. Data access is controlled
within the storage device, and server HBA access to each LUN is explicitly limited (access
is blocked by default). Storage-level access control:
Provides control at the storage port and LUN level, and does not require configuration
at the server.