EMS error message

[Patricio Besteiro]

Hi Admins,

I got this EMS message:

Summary : BOOT_BAD_IPL_ADDR_OTHR


Verify IPL start address is non-zero and aligned on 2KB boundary

could you guys help me to know how to check this?

Thanks in advance!

[Dennis Handly]

What type of server do you have? What HP-UX version?

[Patricio Besteiro]

thanks dennis for your quick response, it's a rp3440, 11.11

[Torsten.]

Did you boot from disk, CD or tape?

[Robert_Jewell]

Is the system booted? The message would indicate a problem in trying to boot. The message was likely logged after a failed boot attempt (as such with a non-bootable disk, or with a boot disk with a corrupt IPL boot area).

-Bob

[Patricio Besteiro]

This server is booting from disk.

/root > uptime
10:56am up 16 days, 19:35, 3 users, load average: 0.03, 0.03, 0.03


The detail of this event is not formatted.
EventNo : 1
Severity : Minor
EventId : 2708
Summary : PDC is validating LIF header.
Time Of Archive : 2010-12-04 17:27:01
Event Category : Unknown
ActualEventThreshold : 1
ActualEventTimeWindow : 0
AlertType : 0
AlertingElementFormat : 2
AlertingManagedElement :
ClusterWideEvent : FALSE
Description : PDC is validating LIF header.
DeviceModel :
DevicePermanentName :
DevicePermanentNameFormat : 2
EventCategory : 0
EventID : 2708
EventSubCategory : 0
EventThreshold :
EventTime : 20101204162653.000000-420
EventTimeWindow :
HWManufacturer :
HWPartNumber :
HWPhysicalLocation :
IndicationIdentifier : 2708020101204222700
IndicationTime : 20101204172700.978230-300
InformationURL : http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#2708
OSType : 8
OSVersion :
OtherAlertType :
OtherAlertingElementFormat :
OtherEventCategory :
OtherEventSubCategory :
OtherPermanentNameFormat :
OtherSeverity :
PerceivedSeverity : 4
ProbableCause : 0
ProbableCauseDescription : { The LIF on the non primary boot path is invalid.Verify IPL start address is non-zero and aligned on 2KB boundary. }
ProviderName : FPL_IndicationProvider
ProviderVersion : A.04.01.01
Query :
Summary : BOOT_BAD_IPL_ADDR_OTHR
SystemCreationClassName : CIM_ComputerSystem
SystemFirmwareVersion :
SystemModel : 9000/800/rp3440

It's been booted 16 days ago, but this alert is from 3 days ago... is this some I should care about since it's minor severity.

Thanks,

[Torsten.]

>> ProbableCauseDescription : { The LIF on the non primary boot path is invalid.Verify IPL start address is non-zero and aligned on 2KB boundary. }


first do a

# lvlnboot -v

then do a "lifls -l" for both boot disks.

Example:

# lifls -l /dev/rdsk/c2t2d0


Post the results.

[Patricio Besteiro]

[root@usatch15] /root > lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
Root: lvol3 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
Swap: lvol2 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
Dump: lvol2 on: /dev/dsk/c2t0d0, 0


[root@usatch15] /root > lifls -l /dev/dsk/c2t0d0
volume ISL10 data size 7984 directory size 8 02/05/10 16:25:44
filename type start size implement created
===============================================================
HPUX -12928 584 848 0 07/06/08 17:02:23
AUTO -12289 1432 1 0 07/03/23 09:30:26
ISL -12800 1440 306 0 02/05/10 16:25:44
PAD -12290 1752 1580 0 02/05/10 16:25:45
LABEL BIN 3336 8 0 05/01/19 10:57:08
[root@usatch15] /root > lifls -l /dev/dsk/c2t1d0
volume ISL10 data size 7984 directory size 8 02/05/10 16:25:44
filename type start size implement created
===============================================================
HPUX -12928 584 848 0 07/06/08 17:02:23
ISL -12800 1432 306 0 02/05/10 16:25:44
AUTO -12289 1744 1 0 02/05/10 16:25:44
PAD -12290 1752 1580 0 02/05/10 16:25:45
LABEL BIN 3336 8 0 05/01/27 14:42:53

[Torsten.]

This looks good.

Not sure why you get this message.

Maybe a false alert from a buggy CIM provider?

However, if you have time, boot from both pathes to ensure it is working.

Maybe you want to write the LIF again.

This is up to you.

[rajos]

What means this error? 01003600000200