Specifications

Troubleshooting

114

Responding to an IPMB isolated alarm

Themodule’sIPMChasdetectedaproblemononeorbothofitsIPMBinterfaces,andhas

isolatedtheIPMCfromtheexternalbus.

1. Verifythemoduleisseatedproperly.

2. Usethehot‐swapproceduretoextractandre‐insertthemodule.

Iftheconditionpersists,contactRadisysTechnicalSupportforassistance.

Responding to a fruinfo fail alarm

Thefruinfostartupscriptfailedtoretrievetheinformationitneeded.

1. CheckfortheShelfFRUInvalidalarm,whichindicatesthattheShelfManag ercannotread

theShelfFRUda ta,orthattheda taisnotvalid.Ifthealarmispresent,seeShelfManager

modulebootsupindebugmodeonpage 126.

2. VerifytheshelfaddressisintheRadisysformat,asspecifiedinRadisysshelfaddress

formatonpage 65.

3. VerifytheshelfIPaddressisavalidaddre ss.

Iftheconditionpersists,contactRadisysTechnicalSupportforassistance.

Responding to a PEM absent alarm

TheRadisy sshelvesaredesignedtooperatewithtworedundantpowerentrymodules

(PEMs),butcanoperatewithonlyonePEMinstalled.However,becausesomeFRUs

specificallymonitorvoltagesfromeachPEMindividually,thoseFRUsgeneratealarmswithout

bothPEMsinstalled.Evenifthesealarmsareacknowledgedtosilencetheaudiblealarm,they

maybereassertedatanytimebecausethepowerlineisfloating.

IftheshelfistoberunwithonlyonePEMforanylengthoftime,itmaybedesirabletodisable

eventgenerationfromthevoltagesensorsonthoseFRUsforthePEMthatisremoved.This

maybedoneusingtheHPIfunctionsaHpiEventEnableSet().

Todisableeventgenerationusinghpiapp:

1. AccesshpiappfromtheLinuxshellandlistallalarms:

hpiapp

2. NotetheresourceIDoftheFRUandthesensorIDlistedinthealarmdescription.

3. Displaythesensorinformation:

4. VerifythatthesensorisrelatedtothepresenceofaPEM.