HPE Storage Users Group

Hello Everyone, this is my first post on the forum.

I'm trying to get my Open VMS server to talk to my V400. The V400 is run
ning 311 MU1 and all other requirements are met. I managed to get the openVMS server to see the 5 LUNS by giving them LUN ID's 0-4.

However the OpenVMS chap said that lun 0 holds a special significance for OpenVMS and could I change the range to 200. This I duly did and assigned the 5 luns with the range 201-205 (200 was taken). - He could then not see anything!

Anyone have any tips or experience in this strange new world of OpenVMS and 3Par? Can anyone point me to some docs or videos that explain lun ID's (i'm quite new to storage).

Many Thanks

PearMotion

_________________
PEAR-Motion

2xNode 3PAR StoreServ 7200
4xNode 3PAR Storeserv 7400 with LFF and SFF
2xNode 3PAR Storeserv 10400

You're the first OpenVMS user I have heard from, nice to meet you.

What Persona are you using for this client?

_________________
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.

just checking - you might be confusing lun ID with os_unit_id (aka udid, aka unit numbers, aka identifier). This (os_unit_id) is a vms specific field used for the presentation (export in 3parlance) of a virtual disk/volume. It's hard to respond to your post, not being sure to what you refer.

At my location, we have been demoing a small 3par with the latest (as of a month or two ago) array code, and there are some peculiarities with the way they have implemented to os_unit_id. They have just made it equal to the virtual volume id. This will cause us some headaches, as the vv id is assigned at volume creation time, and
can't be changed, also non-vms volumes get a vv, which uses up the space of numbers available (we have an allocation scheme where each array gets a different range of os_unit_ids; there are good reasons to do this. We''ve used this with hsg80 arrays and now eva/p6000).

Hopefully they will rethink the implementation.

Thanks for the reply yoy. I have put this on a very faraway back burner for the moment, but i'll update if/when I have to have another go at it

_________________
PEAR-Motion

2xNode 3PAR StoreServ 7200
4xNode 3PAR Storeserv 7400 with LFF and SFF
2xNode 3PAR Storeserv 10400

Yoy,

Thanks. This is what I’was looking for.

I’m not sure what you mean with “virtual volume id”
I assume : you mean “Id Name”
Set by:
createvv -f -i 1010 FC_raid6_42 test_ap_01 18G
Test cli% showvv
---Rsvd(MB)--- -(MB)-
Id Name Prov Type CopyOf BsId Rd -Detailed_State- Adm Snp Usr VSize
1 .srdata full base --- 1 RW normal 0 0 61440 61440
0 admin full base --- 0 RW normal 0 0 10240 10240
1010 test_ap_01 full base --- 1010 RW normal 0 0 18432 18432

Can You confirm this?

This ID is limit to 0-8190
Persona used = 12 (OpenVMS)

lun 0 holds a special significance for OpenVMS as mentiond by “PEAR-Motion”
Id “0” is already taken by a lun that’s there from installation time.
Lun 0 was used in hsj40, hsg80 and eva for the Command Console Lun (CCL)
CCL could be used to communicate to the storage controller.
For example CommandView EVA uses this CCL to communicate with EVA’s
If I’m correct OpenVMS is the only OS capable using this CCL.
I think there is a T4 option to collect EVA performance.

Agree: Hopefully HP will rethink/improves the implementation.

Regards Henk

After an update from the 3par firmware to MU2 you can set OS_UNIT_ID from 0 to 31999.
In a technical whitepaer HP calls this parameter UUID.
It is the index as mentiond before.
I have tested it and it works correct

The naam UUID is not correct for this parameter
Kind Regrads
Henk

Also, starting from 3.1.2 MU1, that special significance of "LUN 0" has been dropped as you don't have to export a vv as LUN 0 for an OpenVMS to see 3PAR. In fact, you cannot do this anymore.

Regards,
Mugur

Mugur,

Als HP to upgrade to 3.1.2 MU2.
Much better for VMS support.

Regards
Henk

I am also struggling to change the virtual volume ID in the 3PAR management console, we are using OpenVMS 8.4 and when the volume is presented the volume ID is used and not the LUN ID.

Anyone here know how to change the ID under Virtual Volumes > Summery and General ID?

_________________
Jamie Edgar, Savant Limited, MBCS, LinkedIn

Jamie,

I use CLI.

% createvv -f -comment "System Common" -i 1001 FC_raid6_42 vmsdisk_SC_01 18G

specify "-i" followed bij the ID. This ID will be your $1$DGAxxx.
this way you have full controll.

Hope this helps

Regards
Henk