Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
jbown Absent Member.
Absent Member.
1121 views

SAN Controller Upgrade - Impact on NW Clusters ?

Hi All,

We are upgrading the controllers on our SAN. It's a SUN StorageTek 6140 being upgraded to the 6780 Model (Fibre Channel). The disk shelves are staying as they are and the controller heads are being upgraded. The entire environment will be shutdown during this migration.

According to the SUN Engineers the WWN of the LUNs will stay the same, however the WWPN of the controller ports will change. In some environments (eg ESX) this causes an issue and steps need to be taken to ensure that the OS does not treat the migrated LUNs as "Hardware Snapshots" where it thinks it's a copy of the old LUN. ESX writes a signature on the disk so it can track these things. After the controllers have changed there is a signature mismatch and the LUNs need to be "re-signed" before they can be used.

As far as NetWare in this environment goes we have 2 NW65 (SP7) Clusters with 4-5 nodes in each cluster. They all have LUNs on this SAN (except boot disks are local to the servers). We have also configured MPIO across all NW hosts so that the primary path is used and no "path thrashing" occurs.

I have the following questions for the experts here:

1) Will NetWare / Media Manager care if the LUNs appear on a different controller port after this migration, or will it just activate and mount the pools as per normal ?

2) Will we have to reconfigure the MPIO path priorities after the migration ?

3) Are there any special concerns we need to watch out for in relation to the SBD partitions ? Will they need to be recreated ?

Based on past experience doing P2V migrations with NetWare into VMWare I don't think NetWare will mind. However we have never done this kind of operation with Clustering also involved so I'm keen to here what others have to say.

Thanks and Advance!

Jeff
Labels (2)
0 Likes
2 Replies
Marcel_Cox Absent Member.
Absent Member.

Re: SAN Controller Upgrade - Impact on NW Clusters ?

jbown wrote:

>1) Will NetWare / Media Manager care if the LUNs appear on a different
>controller port after this migration, or will it just activate and mount
>the pools as per normal ?


NetWare does not care where it sees the storage or whether the storage
changes its location after a reboot.

>2) Will we have to reconfigure the MPIO path priorities after the
>migration ?


It might be possible that you have to reconfigure your MPIO path
priorities. Just check your priorities after the server startup to see if
they are still as expected or if they need to change.

>3) Are there any special concerns we need to watch out for in relation
>to the SBD partitions ? Will they need to be recreated ?


There are no special considerations for SBD. IT is handled just like the
data partitions.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
Highlighted
jbown Absent Member.
Absent Member.

Re: SAN Controller Upgrade - Impact on NW Clusters ?

Hi Marcel,

Thanks for the quick followup. That's great information! I was assuming that this was the answer, but it's always nice to have it confirmed. This upgrade should have minimal impact on our environment which is great.

Cheers,

Jeff
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.