HP StorageWorks 16-EL Fabric OS V3.1.1C Release Notes - Page 8

HP recommendations for redundant fabrics and drivers, Changing Compatibility Mode settings

Page 8 highlights

HP recommendations for redundant fabrics and drivers HP recommendations for redundant fabrics and drivers HP always recommends redundant fabrics and multi-pathing software for uptime-sensitive environments. Examples of scenarios protected by redundant fabrics include, but are not limited to: ■ Add / Move / Change operations for devices or switches ■ Changing the core PID format ■ Changing other fabric-wide parameters (for example, ED_TOV) ■ Erroneous zoning changes / user error ■ Major upgrades / changes to fabric architecture ■ Physical disasters, for example, a water pipe breaks above "fabric A" rack HP recommends strongly 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) ■ Updating the core PID format ■ Using hot spare switch ports to deal with failures 8 Fabric OS 3.1.1c Release Notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17

HP recommendations for redundant fabrics and drivers
8
Fabric OS 3.1.1c Release Notes
HP recommendations for redundant fabrics and drivers
HP always recommends redundant fabrics and multi-pathing software for
uptime-sensitive environments.
Examples of scenarios protected by redundant fabrics include, but are not
limited to:
Add / Move / Change operations for devices or switches
Changing the core PID format
Changing other fabric-wide parameters (for example, ED_TOV)
Erroneous zoning changes / user error
Major upgrades / changes to fabric architecture
Physical disasters, for example, a water pipe breaks above “fabric A” rack
HP recommends strongly 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)
Updating the core PID format
Using hot spare switch ports to deal with failures