[Info-vax] migrate P2000 from SAS to fibre - volumes not mounable

[Bob Gezelter]

On Friday, November 5, 2021 at 5:11:11 AM UTC-4, DanT wrote:
> hi 
> 
> Current working situation is: 
> 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