HP StorageWorks 16-EL HP StorageWorks Zoning V3.1.x/4.1.x User Guide (AA-RS26C - Page 63

Implementing Zoning on an Existing Fabric

Get HP StorageWorks 16-EL - SAN Switch PDF manuals and user guides View all HP StorageWorks 16-EL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 63 highlights

Zoning Concepts and Guidelines Configuration naming is more flexible. In general though there should be one configuration named "PROD fabricname". Fabricname is the name that the fabric has been designated. The purpose of the PROD configuration is to easily identify the configuration that can be implemented and provide the most generic services. If other configurations are used for specialized purposes, the names such as "BACKUP_A", "RECOVERY_2", "TEST_18jun02" may be used. Implementing Zoning on an Existing Fabric The fact that zoning is already implemented eliminates the first step of getting a zone and configuration created. The next step of creating aliases and zones and then adding them to the existing configuration is the same. It is acceptable to have overlapping zones. In fact, it would be expected that the single HBA zones overlap one or more of the existing zones. Once the single HBA zones are in place, then the previous zones can be removed. After the previous zones are removed, then the aliases that are no longer needed may also be removed. Carefully executed, this will be non-disruptive to the devices on the fabric. There may be a momentary disruption of data flow when the new zoning configuration is enabled due to the RSCN. Properly configured devices will handle this without issue. Zoning Version 3.1.x/4.1.x User Guide 63

  • 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
Zoning Concepts and Guidelines
63
Zoning Version 3.1.x/4.1.x User Guide
Configuration naming is more flexible. In general though there should be one
configuration named “PROD fabricname”. Fabricname is the name that the fabric
has been designated. The purpose of the PROD configuration is to easily identify
the configuration that can be implemented and provide the most generic services.
If other configurations are used for specialized purposes, the names such as
“BACKUP_A”, “RECOVERY_2”, “TEST_18jun02” may be used.
Implementing Zoning on an Existing Fabric
The fact that zoning is already implemented eliminates the first step of getting a
zone and configuration created. The next step of creating aliases and zones and
then adding them to the existing configuration is the same. It is acceptable to have
overlapping zones. In fact, it would be expected that the single HBA zones overlap
one or more of the existing zones. Once the single HBA zones are in place, then
the previous zones can be removed. After the previous zones are removed, then
the aliases that are no longer needed may also be removed. Carefully executed,
this will be non-disruptive to the devices on the fabric. There may be a momentary
disruption of data flow when the new zoning configuration is enabled due to the
RSCN. Properly configured devices will handle this without issue.