HP Surestore 64 Planning Guide - Page 82

Benefits of Zoning, Configuring Zones

Page 82 highlights

Benefits of Zoning System administrators create zones to increase network security measures, differentiate between operating systems, and prevent data loss or corruption by controlling access between devices (such as servers and data storage units), or between separate user groups (such as engineering or human resources). Zoning allows an administrator to establish: • Logical subsets of closed user groups. Administrators can authorize access rights to specific zones for specific user groups, thereby protecting confidential data from unauthorized access. • Barriers between devices that use different operating systems. For example, it is often critical to separate servers and storage devices with different operating systems because accidental transfer of information from one to another can delete or corrupt data. Zoning prevents this by grouping devices that use the same operating systems into zones. • Groups of devices that are separate from devices in the rest of a fabric. Zoning allows certain processes (such as maintenance or testing) to be performed on devices in one group without interrupting devices in other groups. • Temporary access between devices for specific purposes. Administrators can remove zoning restrictions temporarily (for example, to perform nightly data backup), then restore zoning restrictions to perform normal processes. Configuring Zones Zoning is configured through the Fabric Manager application by authorizing or restricting access to name server information associated with device node ports (N_Ports) that attach to director fabric ports (F_Ports). A device N_Port can belong to multiple zones. Zoning is configured by: • The eight-byte (16-digit) worldwide name (WWN) assigned to the HBA or Fibre Channel interface installed in the device connected to the director. CAUTION If zoning is implemented by WWN, removal and replacement of a device HBA or Fibre Channel interface (thereby changing the device WWN) disrupts zone operation and may incorrectly include or exclude a device from a zone. 68 Security Provisions

  • 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

68
Security Provisions
Benefits of Zoning
System administrators create zones to increase network security measures, differentiate
between operating systems, and prevent data loss or corruption by controlling access
between devices (such as servers and data storage units), or between separate user groups
(such as engineering or human resources). Zoning allows an administrator to establish:
Logical subsets of closed user groups. Administrators can authorize access rights to
specific zones for specific user groups, thereby protecting confidential data from
unauthorized access.
Barriers between devices that use different operating systems. For example, it is often
critical to separate servers and storage devices with different operating systems
because accidental transfer of information from one to another can delete or corrupt
data. Zoning prevents this by grouping devices that use the same operating systems into
zones.
Groups of devices that are separate from devices in the rest of a fabric. Zoning allows
certain processes (such as maintenance or testing) to be performed on devices in one
group without interrupting devices in other groups.
Temporary access between devices for specific purposes. Administrators can remove
zoning restrictions temporarily (for example, to perform nightly data backup), then
restore zoning restrictions to perform normal processes.
Configuring Zones
Zoning is configured through the Fabric Manager application by authorizing or restricting
access to name server information associated with device node ports (N_Ports) that attach
to director fabric ports (F_Ports). A device N_Port can belong to multiple zones. Zoning is
configured by:
The eight-byte (16-digit) worldwide name (WWN) assigned to the HBA or Fibre Channel
interface installed in the device connected to the director.
C
AUTION
If zoning is implemented by WWN, removal and replacement of a device HBA
or Fibre Channel interface (thereby changing the device WWN) disrupts zone
operation and may incorrectly include or exclude a device from a zone.