Specifications

6
Troubleshooting
125
Inventory Data Record (IDR) topics
Radisyscanprovideatoolcalledfruupdatethatcanbeusedtoupda teexistingFRUinventory
dataonIPMCs.CurrentlyhoweveraddingnewrecordstoIPMCFRUinventorydataisnot
allowedvia HPI.
ThefruupdatetoolacceptsanewFRUda taimageandconfigfileasinput.ThenewFRUdata
imagemustbecreatedbytheuserwiththeircustomFRUdatarecords.Theconfigfile
specifiestheidentityofthoserecords.ThetoolretrievescurrentdatafromtheIPMCandthen
applieschangesspecifiedbytheconfigfiletotheretrievedimagesoanewupdatedimageis
created.ThetoolthenwritestheupdatedFRUdataimagebacktotheIPMC.Thetoolcomes
withdocumentationthattheusercanfollowtocreatethenewFRUdataimageandsetupthe
configfile.
HPI and IPMI topics
The“PlatformAdaptationLayer”(PAL)transmitseachrequestmessagethreetimesat50sec
intervalsfollowingatimeoutresponse.Requestsareonlyretriedfortimeoutandbusyerror
codes.
IfanHPIclientusesRMCP,thedestinationofthemessagefromtheclientisthedestinationIP
addressoftheactiveShelfManagerandthedestinationportis623(RMCPport).Usuallythe
userisexpectedtousetheactiveShelfManagerIPaddress(boundtothedtl0:1interfaceon
theactiveSCM)forthispurpose.
ForsomerequeststheHPIserverandShelfManagercandirectlyrespondtotherequest
withoutneedingtoretrieveinformationfromtheIPMCsintheshelf(e.g.GetRptEntry,
GetDomainInfo,GetEventLog,andsoon).
Forothers,likeGetSensorReading,IPMIrequestsaresendviaShMCthroughtheIPMB‐0to
theIPMC.TheIPMCrespondstotherequestthattheShelfManagertranslatestoHPI‐specific
dataandrespondstotheuser.