Discussion:
migrate P2000 from SAS to fibre - volumes not mounable
Add Reply
Bob Gezelter
2021-11-05 23:31:01 UTC
Reply
Permalink
hi
P2000 storage currently hosted through SAS by BL860c blades in a C3000 enclosure, each having a P711m mezzanine SAS controller. SAS switch in C3000.
We want to migrate this P2000 to fibrechannel, connect to a FC switch and in a first step host by a rx2800i4 with a FC passthrough PCIe card.
There is already another P2000 enclosure connected to that FC switch and its volumes mounted fine in OpenVMS running on the rx2800i4. So we can say, FC switch and rx2800 are fine.
On a first test, we exchanged the SAS controller from the P2000 enclosure with a FC controller. The vdisks and volumes are shown as expected in the controllers web GUI. So far so good.
Once connected to the FC switch and rx2800 rebooted, OpenVMS could not see any of those volumes though.
Somewhere I read that "LUN 0 must be created and present so that the OpenVMS system can detect the rest of the assigned volumes." . Previously on the SAS controller there was no disk volume with LUN 0 though, as there LUN 0 is reserved for SSC/SES. Now with the FC controller though, we can create a volume with LUN 0, which I did.
Volumes were then detected by OpenVMS, great. BUT we can not mount, neither initialize any. Although the volumes all show as "online", trying to mount or initialize will error out with "medium is offline".
The volumes of the other P2000 are still mounting fine.
Anyone having any clue why?
BTW: I now have deleted the volume with LUN 0 again, and OpenVMS can still see them all.
Thanks for any suggestion!
(we are not experts on OpenVMS or those hardware, just helping out a customer)
DanT,

More information is needed. For one thing, there is a OpenVMS Unit number setting for each logical volume on the P2000.

Much depends upon precisely how many things are set.

I can understand why it might be uncomfortable to post that information publicly. If that is an issue, you are certainly welcome to contact me privately.

- Bob Gezelter, http://www.rlgsc.com
DanT
2021-11-06 06:56:17 UTC
Reply
Permalink
Post by Bob Gezelter
hi
P2000 storage currently hosted through SAS by BL860c blades in a C3000 enclosure, each having a P711m mezzanine SAS controller. SAS switch in C3000.
We want to migrate this P2000 to fibrechannel, connect to a FC switch and in a first step host by a rx2800i4 with a FC passthrough PCIe card.
There is already another P2000 enclosure connected to that FC switch and its volumes mounted fine in OpenVMS running on the rx2800i4. So we can say, FC switch and rx2800 are fine.
On a first test, we exchanged the SAS controller from the P2000 enclosure with a FC controller. The vdisks and volumes are shown as expected in the controllers web GUI. So far so good.
Once connected to the FC switch and rx2800 rebooted, OpenVMS could not see any of those volumes though.
Somewhere I read that "LUN 0 must be created and present so that the OpenVMS system can detect the rest of the assigned volumes." . Previously on the SAS controller there was no disk volume with LUN 0 though, as there LUN 0 is reserved for SSC/SES. Now with the FC controller though, we can create a volume with LUN 0, which I did.
Volumes were then detected by OpenVMS, great. BUT we can not mount, neither initialize any. Although the volumes all show as "online", trying to mount or initialize will error out with "medium is offline".
The volumes of the other P2000 are still mounting fine.
Anyone having any clue why?
BTW: I now have deleted the volume with LUN 0 again, and OpenVMS can still see them all.
Thanks for any suggestion!
(we are not experts on OpenVMS or those hardware, just helping out a customer)
DanT,
More information is needed. For one thing, there is a OpenVMS Unit number setting for each logical volume on the P2000.
Much depends upon precisely how many things are set.
I can understand why it might be uncomfortable to post that information publicly. If that is an issue, you are certainly welcome to contact me privately.
- Bob Gezelter, http://www.rlgsc.com
Hi Bob

I should be able to post any information needed.
The P2000 is set up with one VDISK, containing 22 logical volumes, each having a unique name, LUN and OpenVMS UID. These OpenVMS UIDs do not interfere with the ones from the other P2000. We even had that other one disconnected for testing.

# show vdisks
Name Size Free Own Pref RAID Disks Spr Chk Status Jobs Job% Serial Number Drive Spin Down Spin Down Delay Health Health Reason Health Recommendation
-------------------------------------------------------------------------------------------------------------------
vd01 19.9TB 1000.0MB A A RAID6 12 0 64k FTOL VRSC 57% 00c0ff15f273000001e24a5100000000 Disabled 0 OK
-------------------------------------------------------------------------------------------------------------------
Success: Command completed successfully. (2021-11-06 05:04:00)

# show volumes
Vdisk Name Size Serial Number WR Policy Cache Opt Read Ahead Size Type Class Qualifier Volume Description WWN Health Health Reason Health Recommendation
---------------------------------------------------------------------------------------------------------------------------------
vd01 vd01_v001 299.9GB 00c0ff15f27300008017505101000000 write-back standard Default standard standard N/A 1 600C0FF00015F2738017505101000000 OK
vd01 vd01_v002 298.9GB 00c0ff1585f600009e07846101000000 write-back standard Default standard standard N/A 2 600C0FF0001585F69E07846101000000 OK
vd01 vd01_v003 989.9GB 00c0ff15f27300007b18505101000000 write-back standard Default standard standard N/A 3 600C0FF00015F2737B18505101000000 OK
vd01 vd01_v004 989.9GB 00c0ff15f27300009e18505101000000 write-back standard Default standard standard N/A 4 600C0FF00015F2739E18505101000000 OK
vd01 vd01_v005 989.9GB 00c0ff15f2730000d318505101000000 write-back standard Default standard standard N/A 5 600C0FF00015F273D318505101000000 OK
vd01 vd01_v006 989.9GB 00c0ff15f2730000f918505101000000 write-back standard Default standard standard N/A 6 600C0FF00015F273F918505101000000 OK
vd01 vd01_v007 989.9GB 00c0ff15f2730000221a505101000000 write-back standard Default standard standard N/A 7 600C0FF00015F273221A505101000000 OK
vd01 vd01_v008 989.9GB 00c0ff15f27300005e1a505101000000 write-back standard Default standard standard N/A 8 600C0FF00015F2735E1A505101000000 OK
vd01 vd01_v009 989.9GB 00c0ff15f2730000931a505101000000 write-back standard Default standard standard N/A 9 600C0FF00015F273931A505101000000 OK
vd01 vd01_v010 989.9GB 00c0ff15f2730000d51a505101000000 write-back standard Default standard standard N/A 10 600C0FF00015F273D51A505101000000 OK
vd01 vd01_v011 989.9GB 00c0ff15f2730000f11a505101000000 write-back standard Default standard standard N/A 11 600C0FF00015F273F11A505101000000 OK
vd01 vd01_v012 989.9GB 00c0ff15f2730000211b505101000000 write-back standard Default standard standard N/A 12 600C0FF00015F273211B505101000000 OK
vd01 vd01_v013 989.9GB 00c0ff15f27300004a1b505101000000 write-back standard Default standard standard N/A 13 600C0FF00015F2734A1B505101000000 OK
vd01 vd01_v014 989.9GB 00c0ff15f27300006a1b505101000000 write-back standard Default standard standard N/A 14 600C0FF00015F2736A1B505101000000 OK
vd01 vd01_v015 989.9GB 00c0ff15f2730000861b505101000000 write-back standard Default standard standard N/A 15 600C0FF00015F273861B505101000000 OK
vd01 vd01_v016 989.9GB 00c0ff15f2730000991b505101000000 write-back standard Default standard standard N/A 16 600C0FF00015F273991B505101000000 OK
vd01 vd01_v017 989.9GB 00c0ff15f2730000bf1b505101000000 write-back standard Default standard standard N/A 17 600C0FF00015F273BF1B505101000000 OK
vd01 vd01_v018 989.9GB 00c0ff15f2730000d61b505101000000 write-back standard Default standard standard N/A 18 600C0FF00015F273D61B505101000000 OK
vd01 vd01_v019 989.9GB 00c0ff15f2730000e91b505101000000 write-back standard Default standard standard N/A 19 600C0FF00015F273E91B505101000000 OK
vd01 vd01_v020 989.9GB 00c0ff15f2730000fd1b505101000000 write-back standard Default standard standard N/A 20 600C0FF00015F273FD1B505101000000 OK
vd01 vd01_v021 989.9GB 00c0ff15f27300000d1c505101000000 write-back standard Default standard standard N/A 21 600C0FF00015F2730D1C505101000000 OK
vd01 vd01_v022 573.8GB 00c0ff15f27300001e1c505101000000 write-back standard Default standard standard N/A 22 600C0FF00015F2731E1C505101000000 OK
---------------------------------------------------------------------------------------------------------------------------------
Success: Command completed successfully. (2021-11-06 05:04:05)


Consider, it all works fine while having the SAS controller in place and connected through a SAS switch to the C3000 enclosure.
On both SAS and FC controller all information in the web interface of the controller looks exactly the same.

The fibre channel switch is on "default zoning mode" with "All Access".

Any specific information I should pull from the controller ?

Thanks a lot so far!

Dan
Eberhard Heuser
2021-11-06 09:34:12 UTC
Reply
Permalink
hi
...
One point might be the firmware version of the P2000 FC controller:

https://www.seagate.com/de/de/support/dothill-san/assuredsan-3000-series/#downloads

TS252P006 is the FW that definitely works.

Eberhard
eh
2021-11-06 08:30:47 UTC
Reply
Permalink
hi
P2000 storage currently hosted through SAS by BL860c blades in a C3000 enclosure, each having a P711m mezzanine SAS controller. SAS switch in C3000.
...
One point might be the firmware version of the P2000 FC controller:

https://www.seagate.com/de/de/support/dothill-san/assuredsan-3000-series/#downloads

TS252P006
<https://www.seagate.com/files/dothill-content/support/documentation/3000
Series FW - TS252P006.zip> is the FW that definitely works.

Eberhard
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
DanT
2021-11-07 16:06:03 UTC
Reply
Permalink
Post by Eberhard Heuser
hi
P2000 storage currently hosted through SAS by BL860c blades in a C3000 enclosure, each having a P711m mezzanine SAS controller. SAS switch in C3000.
...
https://www.seagate.com/de/de/support/dothill-san/assuredsan-3000-series/#downloads
TS252P006
<https://www.seagate.com/files/dothill-content/support/documentation/3000
Series FW - TS252P006.zip> is the FW that definitely works.
Eberhard
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Hi

We tried the very same controllers as where in the other P2000, they work there, but not in this (ex. SAS controlled) P2000.
I wonder if we simply have to re-configure all VDisks and volumes from scratch. Might be worth a try, althouhg this requires us to move off a lot of TB data somewhere first.
vaxinf@gmail.com
2021-11-06 09:05:20 UTC
Reply
Permalink
hi
P2000 storage currently hosted through SAS by BL860c blades in a C3000 enclosure, each having a P711m mezzanine SAS controller. SAS switch in C3000.
...
One point might be the firmware version of the P2000 FC controller:

https://www.seagate.com/de/de/support/dothill-san/assuredsan-3000-series/#downloads

TS252P006
<https://www.seagate.com/files/dothill-content/support/documentation/3000
Series FW - TS252P006.zip> is the FW that definitely works.

Eberhard
Loading...