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

HP Recommendations on Changing the Core Switch PID Format, Changing Compatibility Mode settings.

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 92 highlights

Updating the Core Switch PID Format HP Recommendations on Changing the Core Switch PID Format Proactively setting the core PID format on all new fabrics before they enter production will prevent the need to update those fabrics in the future. This is strongly recommended as a step in the deployment of all new fabrics. There is no difference in the behavior of a fabric with either PID format; changing to the new format during deployment will merely save administrative effort later on. HP strongly recommends against using drivers that bind by PID. There are several routine maintenance procedures which may result in a device receiving a new PID; the core PID format update is just one example of such a procedure. Examples include but are not limited to: ■ Changing "Compatibility Mode" settings. ■ Changing switch domain IDs. ■ Merging fabrics. ■ Relocating devices to new ports or new switches (that is, for Add, Move, Change type operations. ■ Using hot spare switch ports to deal with failures. ■ In every case where devices bind by PID, any such procedure will become difficult or impossible to execute without downtime. Note: HP always recommends redundant fabrics and multi-pathing software for uptime-sensitive environments. If a redundant SAN architecture is in place, the Core PID update can take place without application downtime. To ensure maximum ease of administration, this parameter can and should be proactively set on a fabric before it ever enters production, whether or not an upgrade to larger switches is planned. 92 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
92
SAN Switch 2/32 Installation Guide
HP Recommendations on Changing the Core
Switch PID Format
Proactively setting the core PID format on all new fabrics before they enter
production will prevent the need to update those fabrics in the future. This is
strongly recommended as a step in the deployment of all new fabrics. There is no
difference in the behavior of a fabric with either PID format; changing to the new
format during deployment will merely save administrative effort later on.
HP strongly recommends against using drivers that bind by PID. There are several
routine maintenance procedures which may result in a device receiving a new
PID; the core PID format update is just one example of such a procedure.
Examples include but are not limited to:
■
Changing “Compatibility Mode” settings.
■
Changing switch domain IDs.
■
Merging fabrics.
■
Relocating devices to new ports or new switches (that is, for Add, Move,
Change type operations.
■
Using hot spare switch ports to deal with failures.
■
In every case where devices bind by PID, any such procedure will become
difficult or impossible to execute without downtime.
Note:
HP always recommends redundant fabrics and multi-pathing software for
uptime-sensitive environments. If a redundant SAN architecture is in place, the Core PID
update can take place without application downtime. To ensure maximum ease of
administration, this parameter can and should be proactively set on a fabric before it
ever enters production, whether or not an upgrade to larger switches is planned.