topic Re: wwidmgr in Operating System - OpenVMS

wwidmgr

LM_2 — Tue, 13 Jun 2006 12:00:51 GMT

I have a cluster (2 ES45's with HSG80 disk config) - when I go int wwidmgr to see what drives are reachable (wwidmgr -show r) one ES45 has two dga22's the other ES45 has two dga23's - I don't want to use these dga's - I want to make different ones available to boot off of- how do I go about doing this??

Re: wwidmgr

Uwe Zessin — Tue, 13 Jun 2006 12:19:29 GMT

Hello LM,
if you want to present different Units to the servers, you need to change the selective storage presentation. For removing access, you need to find out which Unit has which identifier assigned - use the

HSG> show id

command to find out. Let's assume one of the Unit is "D3". To remove access:

HSG> set d3 disable_access_path=all

To allow access to a different unit, you need to match the fibre channel adapter's WWN to the Connection name - the command is:

HSG> show connections

To enable access:

HSG> set d5 enable_access_path=(conn_1, conn_2)

Re: wwidmgr

Bill Hall — Tue, 13 Jun 2006 17:16:09 GMT

LM,

In addition to Uwe's comments, you'll have to use the WWIDMGR to make the boot devices known to the console outside of WWIDMGR. See the WWIDMGR Users Manual http://ftp.digital.com/pub/Digital/Alpha/firmware/archive/doc/wwidmgr_v13.pdf section 2.4.

VMS also needs an identifier set on each device. In Uwe's example on the HSG80, from the HSG80 console:
set d5 identifier=5.

At the Alpha console:
wwidmgr -quickset -udid 5
init
show device ! find the paths to the device.
dga5.1002.0.3.1 $1$DGA5 HP OPEN-E
dgb5.1001.0.3.0 $1$DGA5 HP OPEN-E
set bootdefdev dga5.1002.0.3.1,dgb5.1001.0.3.0

Re: wwidmgr

LM_2 — Wed, 14 Jun 2006 10:13:14 GMT

I should also add that this was a tru64 unix cluster first - do I need to re-init and start from fresh with the drives to work with VMS- or can I keep the setup of the drives and the raid config from tru64 unix?

Re: wwidmgr

Phillip Thayer — Wed, 14 Jun 2006 10:25:25 GMT

The Raid configs should be specific to the HSG80's and can stay as they are, but the data on the drives will naturally be overwritten with a VMS INIT command.

Phil

Re: wwidmgr

Duncan Morris — Wed, 14 Jun 2006 11:04:16 GMT

Hi,

you might need to change the OPERATING_SYSTEM type on the HSG80 connections to "VMS". They are probably still sitting at their old Tru64_Unix value.

HSG80> SHOW CONN
Connection Unit
Name Operating system Controller Port Address Status Offset

DEVT02A1 VMS THIS 1 0A1100 OL this 0

Duncan

Re: wwidmgr

LM_2 — Wed, 14 Jun 2006 12:26:58 GMT

Thanks - everything worked like a charm!!

Re: wwidmgr

LM_2 — Wed, 14 Jun 2006 12:28:44 GMT

everything worked as instructed by the people above!! Thanks for your help!