12-05-2011 04:05 AM - edited 12-05-2011 04:46 AM
Hopefuly this should be a simple question. I have
1 RX2800, patched to current (update 6)
1 P2000 G3 FC device (5 disks) firmware according to the logs is:
MC: L230R025 baselevel L100
2 Brocade SAN switches
What is the black magic incantation for getting the OpenVMS host to see the volumes I create? There are 16 volumes required under a single vDisk. None of the volume LUNs are zero.
I can get some of the disks to appear if I set up a volume with the LUN vms_lun1. However this is hit or miss and not all volumes appear.
The fabric itself seems to be working, the disk controller can see the host and so on.
12-05-2011 05:02 AM
a bit more information might be helpful. Are you setting up these volumes through the CLI?
An example of a volume setup would be handy.
Have you set the host-profile to OpenVMS?
Have you set up UIDs for these volumes?
For a volume to be accessed by an OpenVMS host, assign a volume ID in the range 1–32767 to
identify the volume to the host.
Does the volume have volume-description?
• For OpenVMS, a numeric value (set with create volume or set volume) that identifies the volume
to an OpenVMS host.
• For HP-UX, a text value (set in-band by a host application) that identifies the volume.
• Blank if not set.
On the OpenVMS system what have you done to check for the volumes?
SYSMAN> IO SCSI_PATH_VERIFY
SYSMAN> IO AUTO
12-05-2011 05:24 AM
I'm using the Web Interface to the system.
The ovms-uid IDs have been set
I'll have a go at seeting the host type to VMS (I don't recall doing this on the G2 though).
I'm not seeing the volume description anywhere. I
I'll login via the CLI and see if that helps.
12-05-2011 05:51 AM
It looks as though the volume descriptions are being up correctly. I've tried setting the host type to openVMS (this made no difference).(See attached text file).
I've also run the to commands Duncan suggested (several times now).
Replies may be slow as the system is not on the network and is one floor away.
12-05-2011 06:15 AM
so far so good!
I wonder if the G3 requires you to specifically map the volumes?
Try issuing a map volume command for one of those volumes to specify read-write access. To save you running up and down too much, try one volume without a specified host and one with the OpenVMS host specified.
You can then check the mappings with
12-05-2011 06:47 AM
Well I scrapped all the config, set the host up to VMS and entered all the details again. This time round the VMS host saw all the disks. Assuming it survives a reboot it looks as though you MUST set the host type to openVMS before doing anything else. This could be a pain if we ever need to swap machines.
With any luck, all I need to do now is work out how to boot the other RX2800 from DVD (it stalls) and I may be on my way.
12-06-2011 02:50 AM
You might want to contact OpenVMS Engineering. It seems that they are creating or have created a new I64 V8.4 DVD with Patch Update kit V5 or V6 integrated. This makes it possible to boot from DVD drive on rx2800 i2.
I have heard that an OpenVMS Ambassador has done the same thing and it works fine. But I do not know which Ambassador this person is.
12-07-2011 03:07 AM
For what its worth, the images I got via VMS Engineering were missing a boot block. I backed the DVD up to another disk, wrote the boot block to it and was finally able to install OpenVMS 8-4 on an RX2800.
I have to say that the disk controller on the RX2800 is a real pain.
12-07-2011 06:09 AM
You can decode the contents of the bootblock on the provided DVD using the sys$setboot tool, if you're interested.
$ sb -s -f ddcu:
Where ddcu: is the device name of the target device. (Use -? for help.)
That'll decode the MBR and GPT structures, though it won't decode the El Torito structures.
If the disk does have a valid MBR boot block or MBR boot block and GPT, then it's probably got the offsets for a 512-byte disk and not the 2048-byte optical media sector size.