Specifications

7
Updating and customizing FRU data
71
•Oneofthesepairsoffiles:
•FilesfromRadisyswithnamesendingin<version>.cfgand<version>.bintousefor
upgradingthefunctionalFRUinformation.Donotmodifyorcompilethesefilesbefore
use.
•FileswithnamesendinginCustomFields.cfgandCustomFields.binthataremodified
withcustomdataasdescribedinCustomizing
FRU‐specificdataonpage 68.
Note:Thefilesendingin<ver sion>.sfareusedforrestoringcorruptedFRUdataonly.Ifyou
encounterthissituation,contactRadisysTechnicalSupportforassistance.
Procedure:
FromaLinuxhostwithLANaccesstothetargetFRU,updatetheFRUdatabyentering:
fru_update"‐Ilan‐H<Shelf_Mgr_IP>‐ANONE‐t<IPMB>"<cfg_file>
<FRU_image>
<Shelf_Mgr_IP>istheaddressoftheactiv eShelfManage r.
<IPMB>istheIPMBaddressoftheFRUtoupdate.Toupdateashelf’sFRUdevice,usethe
IPMBaddressofaproxyFRUthatgivesaccesstotheshelfFRUdevice.UsetheproxyFRU
foryourshelfmodel:
•ForATCA‐6000,usetheIPMBaddressofthevirtualSPMifanATCA‐5010orATCA‐5014
isinstalled.SeeTable 6onpage 86fordetailsaboutIPMBaddresses.
•ForATCA‐6006,useaPEMaddress.EachshelfFRUdevicemustbeupdatedseparately.
•ForATCA‐6014andATCA‐6016,usethevirtualRCMaddress,whichupdatesbothshelf 
FRUdevices.
<cfg_file>isthenameoftheFRUdataupdateconfigurationfileendingin.cfg.
<FRU_image>isthebinaryFRUdatafileendingin.bin.
ScriptsverifythetypeofFRUbeingupdatedagainstthefilesprovidedbeforewritingthedata.
Examples:
Thefollowingcommandmakes
anRMCPconnectiontotheShelfManageratIPaddress
10.2.113.36andtargetsmoduleaddress0x82ontheIPMB(anATCA‐2210).
./fru_update"‐Ilan‐H10.2.113.36‐Anone‐t0x82"
ATCA‐2210‐FRU‐v01‐01.cfgATCA‐2210‐FRU‐v01‐01.bin
ThiscommandupgradestheATCA‐6000chassisFRU:
./fru_update"‐t0x50"ATCA‐6000‐FRU‐v01‐06.cfgATCA‐6000‐FRU‐v01‐06.bin