>>>wwidmgr...adding wwid's

[Douglas Fisher]

In a conversation with HP presales tech support it was mentioned that you should add all your known disks with wwidmgr so they will not have to be searched for and slow down the boot process.

Not being SAN savy I opened the wwidmgr manual
but could only find adding 4 wwid's as console variables.

Can what they said be done, if so how.

Thanks very much

[Volker Halle · Accepted solution]

Douglas,

on OpenVMS Alpha systems, you only need to add your boot and dump disks to wwidmgr, so that the pathes to these disk are known to the console at boot and dump time. For shadowed system disks, you should add pathes to all members, but if you have multiple fabrics, this sometimes can not be done completely, as the no. of entries in bootdef_dev and dump_dev are limited as are the wwidmgr environment variables. This varies by system type and firmware version.

You do not add any non-system or non-dump disks.

Volker.

[Bill Hall]

Douglas,

The following is an excerpt from the V7.3 Firmware Release Notes. Please note the specific statement that wwidmgr and the environment variables it populates are intended for boot or crash dump devices, not for ALL of your FC LUNs. I typically use only four entries on every server (two paths to a normal boot disk and two paths to an alternate boot disk) while a may have a total of 200 LUNs mounted on a server.

Wwidmgr - the console supports a number of environmental variables to facilitate boot and crash dump to fibrechannel
storage volumes. Presently there are four (4) WWIDx variables that define the world-wide-ID of a storage
volume and eight (8) Nx variables that define the path to the storage volumes. The console uses these variables to
define the volumes that may be used for boot or crash dump devices.
Solution: Increase the number of Nx (16) and WWIDx (8) console environmental variables.

Bill

[Douglas Fisher]

Thank you for the help