[Info-vax] Migrating OpenVMS to a Fiber Channel storage device.

Jan-Erik Soderholm jan-erik.soderholm at telia.com
Sat Dec 21 09:08:26 EST 2013


Stephen Hoffman wrote 2013-12-21 14:48:
> On 2013-12-21 05:33:15 +0000, Jerome Ibanes said:
>
>> Our ES47 currently has two fiber channel cards, as such:
>> ...
>> The system runs OpenVMS 8.4 from dkc0 (HP 146GB at 15k drive), my goal would
>> be to "copy" the contents of this block device to a lun of an equal size
>> on the (netapp) SAN.
>
> Boot from the CD or boot from another VMS system root somewhere, and BACKUP
> /IMAGE the disk from the brick to the SAN.
>
>> Would there be an easier alternative to boot from a SAN (I imagine
>> installing OpenVMS directly to a SAN isn't an option but please correct
>> me if I'm wrong).
>
> VMS can be installed onto FC SAN devices.  Check the installation manual
> for details on the sequence.
>

Or upgraded from a SAN device. In our setup, we have a image copy of
the VMS 8.4 CD distrubution on an SAN volume that is bootable. We
can shutdown a system, boot from the VMS 8.4 dist SAN device and
then just run the upgrade "as usual". And you can select "INSTALL"
or "UPGRADE".


> <http://h71000.www7.hp.com/doc/84final/ba322_90087/ba322_90087.pdf>
>
> Chapter 3 and Appendix E will be of interest.
>
> Here <http://labs.hoffmanlabs.com/node/786> is some Alpha SRM WWIDMGR
> information, including an overview of using quickset, and some links to the
> documentation for and the limitations of quickset.   You might not be able
> to use quickset here, depending on details of your configuration.

Yes, I had to use the detailed commands, quickset was missing something.
Here is a copy of the command that I saved:

P00>>>wwidmgr -show port
[0] 1000-0000-c95d-c734
[1] 21fc-0027-f80a-686a
[2] 5005-0763-0833-84fd
[3] 5005-0763-0838-84fd
[4] 1000-0000-c93f-c997
[5] 21fc-0027-f80b-d8bb
[6] 5005-0763-0813-84fd
[7] 5005-0763-0818-84fd

P00>>>wwidmgr -set port -item 2 -node 1
P00>>>wwidmgr -set port -item 3 -node 2
P00>>>wwidmgr -set port -item 6 -node 3
P00>>>wwidmgr -set port -item 7 -node 4

P00>>>wwidmgr -show port
[0] 1000-0000-c95d-c734
[1] 21fc-0027-f80a-686a
[2] 5005-0763-0833-84fd (N1)(N1)
[3] 5005-0763-0838-84fd (N2)(N2)
[4] 1000-0000-c93f-c997
[5] 21fc-0027-f80b-d8bb
[6] 5005-0763-0813-84fd (N3)(N3)
[7] 5005-0763-0818-84fd (N4)(N4)

P00>>>wwidmgr -set wwid -udid 1600
P00>>>wwidmgr -set wwid -udid 1300
P00>>>wwidmgr -set wwid -udid 1400
P00>>>wwidmgr -set wwid -udid 1901

P00>>>wwidmgr -show wwid
[0] UDID:1300 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e00 (ev:wwid1)
[1] UDID:1301 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f00 (ev:none)
[2] UDID:1310 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e01 (ev:none)
[3] UDID:1311 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f01 (ev:none)
[4] UDID:1320 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e02 (ev:none)
[5] UDID:1400 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e03 (ev:wwid2)
[6] UDID:1401 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f03 (ev:none)
[7] UDID:1410 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e04 (ev:none)
[8] UDID:1411 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f04 (ev:none)
[9] UDID:1420 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e05 (ev:none)
[10] UDID:1421 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f05 (ev:none)
[11] UDID:1600 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e06 (ev:wwid0)
[12] UDID:1601 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f06 (ev:none)
[13] UDID:1610 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e07 (ev:none)
[14] UDID:1611 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f07 (ev:none)
[15] UDID:1620 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e08 (ev:none)
[16] UDID:1621 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f08 (ev:none)
[17] UDID:1901 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e09 (ev:wwid3)
[18] UDID:1902 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1f09 (ev:none)

P00>>>wwidmgr -show ev
wwid0       1600 1 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e06
wwid1       1300 1 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e00
wwid2       1400 1 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e03
wwid3       1901 1 WWID:01000010:6005-0763-08ff-c4fd-0000-0000-0000-1e09
wwid4
wwid5
wwid6
wwid7
N1                      50050763083384fd
N2                      50050763083884fd
N3                      50050763081384fd
N4                      50050763081884fd
N5
...
...
N15
N16


P00>>>show dev dga
dga1300.1001.0.7.1         $1$DGA1300              IBM 2107900  .171
dga1300.1002.0.7.1         $1$DGA1300              IBM 2107900  .171
dga1400.1001.0.7.1         $1$DGA1400              IBM 2107900  .171
dga1400.1002.0.7.1         $1$DGA1400              IBM 2107900  .171
dga1600.1001.0.7.1         $1$DGA1600              IBM 2107900  .171
dga1600.1002.0.7.1         $1$DGA1600              IBM 2107900  .171
dga1901.1001.0.7.1         $1$DGA1901              IBM 2107900  .171
dga1901.1002.0.7.1         $1$DGA1901              IBM 2107900  .171


Regards,
Jan-Erik.


> This
> WWIDMGR morass is how you convince the SRM console to map the SAN morass to
> a VMS device name that it (SRM) can then make visible to VMS, which then
> allows the rest of the stack to work.
>
>
>




More information about the Info-vax mailing list