P2V planning

[Jose Mosquera]

Hi,

Planning move P2V from physical Integrity rx8620 with HP-UX 11.23 to a BL870c i2 with Integrity VM B.04.30. I have reviewed HP Integrity Virtual Machines 4.3: Release Notes, chapter 11.4 HP-UX Guest Support (Page 35), and indicates that HP-UX Guest Support under VM B.04.30 guests pre-requisite must be on HP-UX 11iv2 December 2007, with this I understand that physical server (rx8620) must be patched at December 2007 before move it to Virtual. In this case our patch level on physical is:
HWEnable11i: May 2005 (B.11.23.0505.022b)
FEATURE11i: May 2005 (B.11.23.0505.022e)
QPKBASE/QPKAPPS: June 2009 (B.11.23.0906.079)

As you see QPKBASE/QPKAPPS satisfies this pre-requisite, but HWEnable11i & FEATURE11i not.

I think that HWEnable11i & FEATURE11i are keys (mainly HWEnable11i), and must be updated on origin before this movement with the last available bundle version for 11.23 (Dec '10 ).

This will be my first P2V migration. Comments in this respect will be apreciated and rewarded.

Rgds.

[likid0]

Hi Jose,


I think what they mean by HP-UX 11iv2 December 2007 is you OE release, not your patch level, you can check your OE release:

# swlist | grep OE
HPUX11i-OE-Ent B.11.23.0609 HP-UX Enterprise Operating Environment Component

If you have and older release you can upgrade using update-ux(with a nice DrD clone just in case)

Although as you say also having your patch level up to date, specially the HWEnable bundle patch, is fundamental for the new blade servers.

[Jose Mosquera]

Hi Daniel,

Whole my last outputs are on my current physical side )rx8620), also this one:
#swlist|grep OE
HPUX11i-OE-MC B.11.23.0403 HP-UX Mission Critical Operating Environment Component

Are you refering to my current physical box or my target blade side components?
In this moment I'm trying to cover any pre-requisite on source physical box.

We do not have the new box (BL870c i2) yet, also I've planned do this movement with a Ignite/UX, of course I haven't previous experiencies with Ignite in P2V movements, just P2V.

Rgds.

[Eric SAUBIGNAC · Accepted solution]

Bonjour,

"Are you refering to my current physical box or my target blade side components?"

==> current physical box : Daniel is right, the OE itself must be updated to the December 2007 release to be supported as a VM Guest.

[ In my mind the latest known one (June 2008) is also eligible since the kernel is based on the December 2007 one ]

It is best to update you current RX8620 physical box (with update-ux) before moving it into a VM Guest on the new blade system. I mean it could work if you update after the installation of the Guest, but you may face some side effects. So, just protect you original OS with ignite or DRD, then update it.

And of course it is also a good job to apply latest 11iv2 patch bundles.

Finally, if you plan to use Ignite to install the VM Guest with an image of the source RX8620 box, it could be a good idea to also install latest Guest AVIO drivers before creating the image. Working this way, you will be able to install the rx8620'OS in a Guest straight designed with AVIO virtual hardware. In the future VIO support will be deprecated and I see very few advantage to work with VIO drivers. Prefer AVIO architecture

Eric

[likid0]

Yes, the source box.

Couldn't be better explained Eric.

[Jose Mosquera]

Hi guys,

Thank you very much for your answers with detailed info.

Well, my first step is request the update media. The lastest is December 2010 and include B.11.23.0712 for HPUX11i-OE and HPUX11i-OE-MC components. This because I've
one rx2600 and two rx8620 physical Integrity servers, with the following current OE Components:
1) HPUX11i-OE B.11.23.0403 HP-UX Foundation Operating Environment Component
2) HPUX11i-OE-MC B.11.23.0403 HP-UX Mission Critical Operating Environment Component
3) HPUX11i-OE-MC B.11.23.0403 HP-UX Mission Critical Operating Environment Component

As you see all of them are on 0403. I've reviwed HP Software Releases & Media details at:
http://www.hp.com/softwarereleases/releases-media2/latest/RA1009/media.htm

On the HP-UX 11i v2 OE Not Updated in March 2011 I see these the following servers product availability:
OE - FOE Core (5013-8359/5013-8360) for my first server with HPUX11i-OE, and,
OE -MCOE Core (5013-8365/5013-8366) to other two servers with HPUX11i-OE-MC.

Checking inside of them I can see that is included Integrity VM Guest Support Libraries (VMGuestLib), Are included Guest AVIO drivers there?

I guess that also need:
Support Pack Updated December 2010 (B9106-10013)
DVD application 11i v2 (B9106-10010/B9106-10009)
Instant Info 11i - DVD- English (B3921-10072)

I must check If these media are available, in the oposite case I must request them to HP. Is there a faster way to receive these?

Then, after make a previous -mandatory- Ignite, a update-ux must be done to update OEs from 0403 to 0712. Also this will be my first time with update-ux, reviwing man pages looks like a fancy and silent way to done this, Are there some crashed experience (eg: SAN connections, scsi paths, middleware software as Oracle9i R2, etc)?

Eric, as you say:
>>I mean it could work if you update after the installation of the Guest, but you may face some side effects.<<
Remembering that is my first P2V migration, I can't imagine this OEs updates on Guests after recover them from an Ignite process, on this novice scenerio is higly recommended update first on physical.

Keep awaiting for feedback, Rgds.

[Eric SAUBIGNAC]

--- "Checking inside of them I can see that is included Integrity VM Guest Support Libraries (VMGuestLib), Are included Guest AVIO drivers there?"

AVIO Drivers are NOT included in the VMGuestLib. But they are part of the second 11iv2 OE DVD : GuestAVIOStor and GuestAvioLan .

You probably will have to explicitly select them during the update. You can forget HostAVIOStor and HostAvioLan because their use is intended for a VM Host only.

Anyway, you will have to update the GuestAvio drivers with the latest release : the one on the OE DVD is rather old.
Check @ https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AVIO

--- "Is there a faster way to receive these?"

For DVD application 11iv2, I think there is no faster way. Don't forget to check that you also receive application codewords (for example C-Ansi)

Regarding Support pack you can download patch bundles @ http://www.itrc.hp.com/service/patch/releaseIndexPage.do?BC=main|

and diagnostics @ https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

Instant info is not mandatory. Just documentation

--- "Are there some crashed experience"

I have no experience of this kind. But of course it doesn't mean you will not fall in ... One success key is to always check logfiles. ANd of course protect your source system with ignite and/or DRD.

And it is probably going against what I said in my previous post, but upgrading once the VM has been ignited will let your original system intact. If your March 2004 release doesn't work in a VM Guest, or if the update process in the VM fails, you will have wasted some time, and probably won some experience, that's all ... Maybe it's a safer way to start if you are a novice with update-ux ?

In this case don't use AVIO architecture, because the OS you will install from the ignite image doesn't support it. You will move to AVIO once the OS will be properly updated.

Just present a VIO OS lun, a VIO lan card, sufficient memory, at least 2GB, try to install the ignite image, and don't forget to modify the VM host name and IP adresses so that the original host is kept still working.

Then you will have a clone of your original system to play with


--- "Remembering that is my first P2V migration"

Don't worry, virtualization is not a total transformation. If you have a good HP-UX knowledge background, it will fit.