Replacing HP 4Gb VC-FC Module with HP VC 8Gb 24 - Port FC Module

[dtnsup]

Hi,

i would like to replace my productive environment on Bay 4+5
- 2 x old "HP 4Gb VC-FC Module" 409513-B21 with
- 2 x new "HP VC 8Gb 24 - Port FC Module" 466484-001 / 466539-001

The Firmware of the new HP VC 8Gb matches the requirement of the enclosure (I can update the firmware in a second, non-productive C7000).

Question: How should I replace the modules? What's the right order? Is there a downtime (FC)  necessary?

best regards
Danny

[frenchy94]

There are a wp about this

Please refer to the "Upgrading to an HP Virtual Connect 8Gb 24-Port FC
Module" section of the HP Virtual Connect for c-Class BladeSystem Setup and
Installation Guide
1732252.pdf> on page 45 and follow these steps:







Replacing an HP 4Gb VC-FC Module, HP VC 4Gb FC Module, or HP 8Gb 20-Port FC
Module with an HP VC 8Gb 24-Port FC Module

1. Upgrade the VC domain firmware to v2.10 or higher.

2. Verify that the replacement will result in a good configuration. See
"Multiple enclosure guidelines (on page 20)."

3. Verify that the user has Server privileges.

4. Remove any FC profile connections that are connected to the interconnect
bays being upgraded. To remove the profile connections, un-assign the
profile, and then delete the connections from the profile.

5. If any FC SAN fabrics were created using uplinks from the interconnect
bays that are being upgraded, delete these FC SAN fabrics from the Virtual
Connect domain.

6. Physically remove the existing modules from BOTH horizontally adjacent
bays for each enclosure in the domain. In a double-dense domain, remove the
modules from Bay 7 and Bay 8 when removing modules in Bay 5 and Bay 6.

7. Ensure that the VC-FC modules are no longer shown in the domain.

8. Install the HP VC 8Gb 24-Port FC Modules.

9. Re-create previously deleted FC SAN fabrics.

10. Re-assign the server profiles, and then add the FC connections to the
profiles.



It is true that you can simply delete domain and swap modules. you won't be
able to recover binary config file since module types are different and it
won't' necessarily preserve WWN assignments.



Secondly, when MACs and WWNs are manually specified in the "add
xxx-connection" commands, they are no longer considered VC-managed
attributes, but rather externally-managed. What this means is that when a
profile is assigned with these MACs/WWNs, they will be removed from the
MAC/WWN pool, but if the profile is ever deleted, they will not be returned
to the MAC/WWN pool because VCM assumes that the profile still could exist
on another enclosure or another domain and would want to avoid duplication,
so essentially you are creating holes in the pools of MACs and WWNs by
manually assigning these attributes.







---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus