topic Re: Ignite Restore Problem in Operating System - HP-UX

Ignite Restore Problem

Sandeepbodkhe1 — Tue, 09 Jul 2013 02:05:50 GMT

Hi,

I have set up an Ignite server on bl860c i4 Blade.

It is working fine for backup /restores of i4 servers.

Howevr, I tried migrating one of the bl860c i2 blade using recovery archive. but post completing the archive processing,

It hangs on the console with below error message.

Booting kernel...

Warning: unknown processor family 33
Warning: secondary PTE is disallowed due to the uses of the default hashing function.

Note, menu interfaces might only display on the primary console device.
The current primary console device is:
Serial PcieRoot(0x30304352)/Pci(0x1,0x0)/Pci(0x0,0x5)
The primary console can be changed via the 'conconfig' UEFI shell command,
or the 'Console Configuration' option in the Boot Maintenance Manager menu.

Press: ENTER - Start boot entry execution
B / b - Launch Boot Manager (menu interface)
D / d - Launch Device Manager (menu interface)
M / m - Launch Boot Maintenance Manager (menu interface)
S / s - Launch UEFI Shell (command line interface)
I / i - Launch iLO Setup Tool (command line interface)

*** User input can now be provided ***

Automatic boot entry execution will start in 1 second(s).
HP Smart Array P410i Controller (version 5.84) 1 Logical Drive
Currently the controller is in RAID mode
Booting HP-UX Primary Boot: 0/0/0/2/0/0/0.0x0.0x4000000000000000

HP-UX Boot Loader for IPF -- Revision 2.047

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 32648 MB
loading section 0
....................................................................... (complete)
loading section 1
............. (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
.....
loading MFSFILES directory (bootfs) to MFS
..............................

================================================================================
WARNING: Multiple console output devices are configured. If this message
remains on the screen for more than a few minutes, then this is not the
device in use by HP-UX as the console output device. If you would like this
device to be the one used by HP-UX as the console output device, reboot and
use the EFI boot manager or the EFI 'conconfig' command to select this device
and deconfigure the others.
================================================================================
Launching /stand/vmunix
SIZE: Text:36184K + Data&colon;6368K + BSS:26767K = Total:69320K
Console is on Serial Device - via PCDP
Booting kernel...

Warning: unknown processor family 33
Warning: secondary PTE is disallowed due to the uses of the default hashing function.

------------------

Machinfo of the source server is as follow,

CPU info:
2 Intel(R) Itanium 2 9100 series processors (1.67 GHz, 18 MB)
666 MT/s bus, CPU version A1
4 logical processors (2 per socket)

Memory: 32737 MB (31.97 GB)

Firmware info:
Firmware revision: 04.21
FP SWA driver revision: 1.18
IPMI is supported on this system.
BMC firmware revision: 5.38

Platform info:
Model: "ia64 hp server BL860c"
Machine ID number: a42c08e8-1373-11df-9b65-a3ae937d9b4f
Machine serial number: GB8952DMYT

OS info:
Nodename: fihpbl5
Release: HP-UX B.11.31
Version: U (unlimited-user license)
Machine: ia64
ID Number: 2754349288
vmunix _release_version:
@(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf

P.S. This thread has been moved from BladeSystem > Server Blades to HP-UX > ignite. - HP Forum Moderator

Re: Ignite Restore Problem

Robert_Jewell — Mon, 08 Jul 2013 14:47:09 GMT

You mention i2 blades:

> I tried migrating one of the bl860c i2 blade

But what you have is the original BL860 blade (not i2):

> 2 Intel(R) Itanium 2 9100 series processors (1.67 GHz, 18 MB)

> Model: "ia64 hp server BL860c"

The architecture between them is different and an Ignite archive built on one, will not work for the other.

-Bob

Re: Ignite Restore Problem

Steven E. Protter — Tue, 09 Jul 2013 01:07:08 GMT

Robert is correct.

You may succed with a less hardware dependent Ignite Golden Image.

Re: Ignite Restore Problem

Torsten. — Tue, 09 Jul 2013 06:02:03 GMT

As Robert said, the source server is the older model (BL860c), so the OS is most likely too old to support the newer CPU.

Consider to install the latest hardware enablement patches first.

Re: Ignite Restore Problem

Sandeepbodkhe1 — Wed, 17 Jul 2013 21:02:14 GMT

Friends,

I am trying with drd clone by applying latest patch of hw enablement.

What i have done is, I allocated a storahe lun to source server, and then took drd image of it.

After that i have applied hw enablement patches on drd image and then shared the same lun with target hardware which is the latest bl860 i4 as described above.

Blade is in c7000 enclosure and have Flex fabric virtual connect.

server profile is created in vcem.

The problem i am stuck into is that, I am unable to discover the SAN Lun in efi shell of the target hardware to boot from.

I have tried conventional drivers the drvcfg command. but thing is that,m i dont see the configurable driver for the Fcoe hba,

any ideas..? it's driving me crazy..i have already dropped ignite recovery method as i wanted source to be unpatched and untouched for rollback.

take me out of this and Full points guranteed.

UEFI Shell version 2.30 [2.0]

Current running mode 1.1.2

Device mapping table

fs0 :Removable HardDisk - Alias hd17a0b blk0

PcieRoot(0x30304352)/Pci(0x2,0x0)/Pci(0x0,0x0)/Scsi(0x0,0x0)/HD(1,GPT,80C97A2A-ED49-11E2-8000-D6217B60E588

fs1 :Removable HardDisk - Alias hd17a0d blk1

Shell> driverseRoot(0x30304352)/Pci(0x2,0x0)/Pci(0x0,0x0)/Scsi(0x0,0x0)/HD(3,GPT,80C97A5C-ED49-11E2-8000-D6217B60E588

T Dble HardDisk - Alias hd17a0b fs0

D Y C Iot(0x30304352)/Pci(0x2,0x0)/Pci(0x0,0x0)/Scsi(0x0,0x0)/HD(1,GPT,80C97A2A-ED49-11E2-8000-D6217B60E588

R P F Able HardDisk - Alias hd17a0d fs1

V VERSION E G G #D #C DRIVER NAME IMAGE NAME)/HD(3,GPT,80C97A5C-ED49-11E2-8000-D6217B60E588

== ======== = = = == == =================================== ===================

11 00000001 ? - - - - ICH Serial ATA Controller Initializ SataControllerDxeGPT,80C97A52-ED49-11E2-8000-D6217B60E588

1A 0000000A B - - 1 61 PCI Bus Driver PciBusDxe

1E 00000014 B - - 1 1 Serial 16550 Driver Serial,0x0)

6B 0000000A ? - - - - AHCI Bus Driver AhciDxe

6C 0000000A D - - 2 - Platform Console Management Driver ConPlatformDxe

6D 0000000A D - - 2 - Platform Console Management Driver ConPlatformDxe

6E 0000000A B - - 2 2 Console Splitter Driver ConSplitterDxe

6F 0000000A B - - 1 1 Console Splitter Driver ConSplitterDxe

70 0000000A ? - - - - Console Splitter Driver ConSplitterDxe

71 0000000A B - - 2 2 Console Splitter Driver ConSplitterDxe

72 0000000A B - - 2 2 Console Splitter Driver ConSplitterDxe

75 0000000A ? - - - - UGA Console Driver GraphicsConsoleDxe

76 0000000A B - - 1 1 Serial Terminal Driver TerminalDxe

77 0000000A D - - 1 - VGA Class Driver VgaClassDxe

78 00000000 D - - 1 - PCI VGA Mini Port Driver VgaMiniPort

79 0000000A D - - 4 - Generic Disk I/O Driver DiskIoDxe

7C 0000000A D - - 2 - FAT File System Driver Fat.efi

7E 0000000A B - - 3 1 SCSI Bus Driver ScsiBus

7F 0000000A ? - - - - Scsi Disk Driver ScsiDisk

80 00000030 ? - - - - Scsi Tape Driver ScsiTape

81 0000000A B - - 1 3 Partition Driver(MBR/GPT/El Torito) PartitionDxe

82 0000000A B - - 4 2 Usb Bus Driver UsbBusDxe

83 0000000A D - - 1 - Usb Keyboard Driver UsbKbDxe

84 00000011 ? - - - - Usb Mass Storage Driver UsbMassStorageDxe

85 0000000A D - - 1 - Usb Mouse Driver UsbMouseDxe

86 00000020 D - - 3 - Usb Uhci Driver UhciDxe

87 00000030 D - - 1 - Usb Ehci Driver EhciDxe

88 0000000A D - - 14 - Simple Network Protocol Driver SnpDxe

89 0000000A B - - 14 42 MNP Network Service Driver MnpDxe

8A 0000000A B - - 14 14 ARP Network Service Driver ArpDxe

8B 0000000A B - - 14 112 IP4 Network Service Driver Ip4Dxe

8C 0000000A D - - 14 - IP4 CONFIG Network Service Driver Ip4ConfigDxe

8D 0000000A B - - 84 70 UDP Network Service Driver Udp4Dxe

8E 0000000A B - - 14 14 DHCP Protocol Driver Dhcp4Dxe

8F 0000000A B - - 28 14 MTFTP4 Network Service Mtftp4Dxe

90 0000000A D - - 98 - UEFI PXE Base Code Driver UefiPxeBcDxe

91 0000000A D - - 14 - TCP Network Service Driver TcpDxe

A2 00000352 B X X 1 2 Smart Array SAS Driver v3.52 MemoryMapped(0xB,0x

A6 000221AC B - X 14 14 Emulex 10G NIC MemoryMapped(0xB,0x

AC 00050214 D - X 2 - Emulex FCoE SCSI Pass Thru Driver MemoryMapped(0xB,0x

Shell>

Re: Ignite Restore Problem

Sandeepbodkhe1 — Wed, 17 Jul 2013 21:07:16 GMT

Hi Steve,
Could you be please elaborate your suggestion in bit more details please..
Thanks in advance

Re: Ignite Restore Problem

Robert_Jewell — Thu, 18 Jul 2013 17:35:11 GMT

What Steven is referring to is the use of an Ignite Golden Image. Basically this is a generic version of an Ignite backup that is meant to be used to deploy the OS to other servers.

Find instructions about this here:

www.hp.com/go/ignite-ux

- Scroll down and look for the link to Ignite-UX manuals

- On the manuals page scroll down and look for the "Ignite-UX Administration Guide". Info on Golden Images starts in Chapter 11.

- Also take a look at the guide "Sucessful System Cloning..."

As suggested, update the HWE patch bundle to the latest before creating the image. Also consider the following software: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=BL8x0-i2

-Bob

Re: Ignite Restore Problem

Torsten. — Fri, 19 Jul 2013 06:11:09 GMT

Never worked with FCoE on such servers, but I would try the same way like other HBAs too:

EFI> drivers

find the correct driver index "x"

EFI> devices

find the correct device index "y"

EFI> drvcfg -s x y

on a "normal" FC HBA you would set the EFISCANLEVEL to 1 to enable a search in the SAN.

Re: Ignite Restore Problem

Sanjay Yugal Kishore Ha — Thu, 15 Aug 2013 17:15:11 GMT

The BL8*0 i4 blades require a minimum OS version of HP-UX 11iv3 September 2012 release. You may either cold-install the i4 blades or upgrade the i2 blades to the 11iv3 September 2012 release and then migrate.

HTH,

Sanjay