EVA on V5.1A-PK6

[Francois Rabe]

Can anybody tell me if I will be able to boot and ES40 from and EVA. We are running V51.A with PK6. Previously running PK2 we could see the disks on the EVA, but could not access them, so upgraded to PK6. Now we can mount and access them. The client wants to migrate all the SAN disks to EVA, but will I be able to boot from the EVA after the migrate. We are planning to use addvol and rmvol to acheive the migration. Or will it be better to upgrade to V5.1B 1st? And then use addvol and rmvol.

[Uwe Zessin]

Francois,
all current EVA systems should have firmware version 3.010 at least. The minimum version for Tru64 Unix V5.1A is PK4. Here is some documentation for help:

- Tru64 UNIX Kit V3.0B for Enterprise Virtual Array Installation and Configuration Guide
http://h20000.www2.hp.com/bizsupport/CoreRedirect.jsp?targetPage=http%3A%2F%2Fh200005.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FUCR%2FSupportManual%2FTPM_aa-rugpb-te%2FTPM_aa-rugpb-te.pdf

- Tru64 UNIX Kit V3.0B for Enterprise Virtual Array Release Notes
http://h20000.www2.hp.com/bizsupport/CoreRedirect.jsp?targetPage=http%3A%2F%2Fh200005.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FUCR%2FSupportManual%2FTPM_av-rugsb-te%281%29%2FTPM_av-rugsb-te%281%29.pdf

[Francois Rabe]

Thanks for the info. We can already see and use the disks on the EVA. The question is: Will we be able to boot from the disks on the EVA.Where and when is the driver loaded to achieve this?

[Michael Schulte zur Sur]

Hi Francois,

why not just try it. However the approach with addvol and rmvol might not work with root_domain since as much I can remember it allows only one partition. Rather copy and then set the console variables to EVA. It might be a good idea to do the update to 5.1B first, if that is what you planned to do anyway.

greetings,

Michael

[Jonathan Burelbach]

you need to use wwidmgr to assign the LUNs to the es40. Try this from the >>> prompt:

>>> wwidmgr -show ada
>>> wwidmgr -show port
>>> wwidmgr -show wwid

and see what it reports. You will need to assign a ID tag to the drive you want to boot from at the EVA level, then you can run
>>> wwidmgr -quickset -udid _ID#_
If everything is setup correctly it should report connectivity after init. Then run
>>> show N*
>>> show wwid*
and it should report some values. re-init the system and a "show dev" should show the boot drives. Install onto those and everything should be good to go.