HP StorageWorks 2/32 SAN switch 2/32 version 4.0.x installation guide - Page 96

changing to WWN binding., This may involve changing them to the new PIDs, or may preferably involve

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

Page 96 highlights

Updating the Core Switch PID Format 5. One at a time, re-enable the switches in the updated fabric. In a core/edge network, enable the core switches first. 6. Once the fabric re-converges, type cfgEnable myZoningCfg, (where myZoningCfg is the name of your zone configuration). Press Enter to update zoning. Note: This does not change the definition of zones in the fabric, but causes the lowest tables in the zoning database to update with the new Core Switch PID format. 7. Repeat steps 3 through 6 for all fabrics in the SAN. 8. Bring the devices online in the order appropriate to the SAN. This usually involves starting up the storage arrays first, and the hosts last. 9. For any devices manually bound by PID, bring the device back online, but do not start applications. Update their bindings and reboot again if necessary. This may involve changing them to the new PIDs, or may (preferably) involve changing to WWN binding. 10. For any devices automatically bound by PID, reboot the device to rebuild the device tree. (Some operating systems require a special command to do this. E.g. boot -r in Solaris.) 11. For devices that do not bind by PID or have had their PID binding updated, bring them back up and resume I/O. 12. Verify that all I/O has resumed correctly. Note: Migrating from manual PID binding (e.g. persistent binding on an HBA) to manual WWN binding and/or upgrading drivers to versions that do not bind by PID can often be done before setting the core PID format. This can be advantageous, as it prevents the update process from having as many variables. Note: Once the switch PID format is set, it is stored in the flash memory of the switch, and it is NOT necessary to set it again during subsequent firmware upgrades. 96 SAN Switch 2/32 Installation 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
  • 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
Updating the Core Switch PID Format
96
SAN Switch 2/32 Installation Guide
5.
One at a time, re-enable the switches in the updated fabric. In a core/edge
network, enable the core switches first.
6.
Once the fabric re-converges, type
cfgEnable myZoningCfg
, (where
myZoningCfg
is the name of your zone configuration). Press
Enter
to
update zoning.
Note:
This does not change the definition of zones in the fabric, but causes the lowest
tables in the zoning database to update with the new Core Switch PID format.
7.
Repeat steps 3 through 6 for all fabrics in the SAN.
8.
Bring the devices online in the order appropriate to the SAN. This usually
involves starting up the storage arrays first, and the hosts last.
9.
For any devices manually bound by PID, bring the device back online, but do
not start applications. Update their bindings and reboot again if necessary.
This may involve changing them to the new PIDs, or may (preferably) involve
changing to WWN binding.
10.
For any devices automatically bound by PID, reboot the device to rebuild the
device tree. (Some operating systems require a special command to do this.
E.g.
boot –r
in Solaris.)
11.
For devices that do not bind by PID or have had their PID binding updated,
bring them back up and resume I/O.
12.
Verify that all I/O has resumed correctly.
Note:
Migrating from manual PID binding (e.g. persistent binding on an HBA) to
manual WWN binding and/or upgrading drivers to versions that do not bind by PID
can often be done before setting the core PID format. This can be advantageous, as it
prevents the update process from having as many variables.
Note:
Once the switch PID format is set, it is stored in the flash memory of the switch,
and it is NOT necessary to set it again during subsequent firmware upgrades.