HP StorageWorks 2/32 - SAN Switch Note de mise à jour - Page 24

Parcourez en ligne ou téléchargez le pdf Note de mise à jour pour {nom_de_la_catégorie} HP StorageWorks 2/32 - SAN Switch. HP StorageWorks 2/32 - SAN Switch 32 pages. Fabric manager version 3.0.x release notes
Également pour HP StorageWorks 2/32 - SAN Switch : Manuel d'instructions d'installation (20 pages), Manuel de l'utilisateur (22 pages), Notes de mise à jour du micrologiciel (14 pages), Note de mise à jour (48 pages), Manuel d'instructions d'installation (6 pages), Note de mise à jour (14 pages), Note de mise à jour (4 pages)

Licenses

Prior to replacing a switch or motherboard, display and record the current licenses that

are active in the unit. Additional licenses could have been added to the switch after the

installation. Licenses that are active can be viewed from a Telnet session using the

command, or they can be viewed from the Web Tools GUI.

licenseshow

Replacement units are shipped with all licenses enabled, with the exception of the

license for the Fabric Manager option.

Optional software (for example, Fabric Manager) does not require a license key, just

the license supplied at the time of purchase.

Zoning Licensing

HP provides Zoning as a standard feature on its SAN and Core Fibre Channel

switches. This means that the Zoning license is factory installed on each of these

switches. Therefore, references in the product documentation to installing the Zoning

license or to Zoning being an optionally purchased product should be ignored.

Read the following section for a list of current Fabric OS Version 4.0.2b limitations

and possible workarounds.

OpenVMS Path Failback

In very specific configurations utilizing multiple OpenVMS hosts connected to

multiple ports of an HP StorageWorks SAN Switch 2/32, it is possible that not all

paths will re-establish to a switch after a failover/failback failure scenario. In all cases

where a path failure occurs, initial path failover to an alternate path occurs as

expected, with no loss of data. Once the initial failed path is repaired however, it is

possible under certain rare conditions, for the failback sequence to the repaired path to

be unsuccessful.

HP believes the likelihood of occurrence is extremely low and has only encountered

this condition under extensive, multiple repeated failover/failback test sequences. This

condition is expected to be corrected in a future release.

SAN switch 2/32, version 4.0.2b release notes