Specifications

2
Software Architecture
22
RMCP,arequest‐responseprotocol,isasimplepacket‐basedcommunicationmechanism.
RMCPpack etsincludeafieldthatindicatestheclassofmessageembeddedinthepack et.The
messagesbetweentheHPIclientandHPIserverareencapsulatedinRMCPpacketsusingthe
OEMclass.Formoreinformation,seethe
RMCPsectionoftheIntelligentPlatform
ManagementInterfaceSpecificationv2.0,DocumentRevision1.0.
TheHPIservice reportsthesystemstatusfromtheperspectiveofthesystemitisrunningon.
WhenashelfhasredundantSCMs,theHPIserveralsoemploysanactive/standbyredundancy
model.Inthismodel,theactiveHPIserverrunsontheactiveShelfManagerandthestandby
HPIserverrunsonthestandbyShelfManager. Formoreinformation,seeHPIserver
redundancyonpage 31.
Inarun‐timeenvironment,theHPIclientlibraryisconsideredanextensionofthe
managementapplication.Theremotenetworkinterfaceprovidedbytheclientlibraryallows
themanagementapplicationtoexecutefromanywherewithinthenetworkandonany
modulerunningtheLinuxoperatingsystem.Theclientlibrarymayex ecuteonthesame
moduleastheShelfManager.Inalocalenvironment,theclientstillusesthesocketinterface
butinitslocalform.
Domain alarm table (DAT)
HPImaintainsadomainalarmtableofactivealarmsrelatedtotheshelf.Thetable’scurrent
alarmscausethealarmLEDstoturnonandoff,unlessthesystemmanageroverridesthis
behavior.Unacknowledgedalarmsadditionallycausetheaudiblealarmtosound,unlessthe
systemmanageroverridesthis.Alarmsareremovedfromthetablewhentheconditionis
resolved.
ForinformationoninteractingwiththeDAT,seeRespondingtoalarmsonpage 100.For
detailsonhowtheShelfManagerrespondstoalarms,seeManagingAlarmsandEventson
page 82.ForgeneralinformationabouttheDAT,seethedomainalarmtablesectionofthe
SAFHPISpecification.
System event log (SEL)
TheIPMCofeachintelligentFRUkeepsalocalsystemeventlogcontainingallevents
generatedbytheIPMC.Someeventsannouncestatechanges,andothersindicatehealth
conditionsandcausealarms.TheSELontheactiveShelfManagermoduleactsastheSELfor
theentireshelf.ItisacollectionoftheSELentriesfromallFRUsintheshelf,andidentifies
eacheventbytheIPMBaddressoftheFRUthatgenerate dit(intheleastsignificantbyteof
thegeneratorID).
TheSELisprimarilyintendedfortroubleshootingpurposesanddoesnotofferaprogrammatic
interface.ThesimilarDomaineventlog(DEL)canbeaccessedprogrammaticallybyasystem
manager.TheSELcontainsacompletelistofIPMCevents,soitisthebestsourceforevents
suchassystemprogresscheckpointeventsgenerate dbyRadisysmodules,whichareexcluded
fromthedomaineventlog.