Specifications

6
Troubleshooting
116
5. Lookforthe“inetaddr”value.TheSCMinthelower‐numberedslotinthechassisshould
haveaneth1IPaddressof10.0.1.1.TheSCMinthehigher‐numberedslotshouldhavethe
address10.0.1.2.Iftheaddresseswer echangedfromthesevalues—eveninthetemplate
filesthatset
theaddressesuponSCMbootup—restorethemtotheoriginalsettings
persistently.SeetheSoftwareGuideformoreinformationontheIPaddressassignment
andtemplatefiles.
IfyouareoperatingwithonlyoneSCMinstalledforalengthoftime,youmaywanttodisable
theredundancylostalarm.Todisablethealarm,usethesameproceduredescribedin
RespondingtoaPEMabsentalarmonpage 114.
Responding to a redundancy degraded event
Note:ThissectionappliesonlytoshelveswhereanSCMisactingastheShelfManager.Itdoes
notapplytoATCA‐6002shelves.
ASAHPI_ES_REDUNDANCY_DEGRADEDeventindicatesthattheShelfManagerhasdetected
aredundantShelfManager,butitisrunningadifferentsoftwareversion.Theeventis
generatedbytheShelfManagerredundancystatussensorontheShelfManagerresource.
ThenewShelfManagerfeaturesthatarenotsharedbybothShelfManagersarenot
available.Toresolvetheproblem,upgradetheLMPsoftwaretomaketheShelfManager
versionsmatch.
Responding to a shelf FRU invalid alarm
TheshelfitselfhasasensortoindicatethattheShelfManagercannotreadtheShelfFRU
data,orthatthedataisnotvalid.Ifthesensorgenerat e sanalarm,seeShelfManagermodule
bootsupindebugmodeonpage 126.
Responding to a FRU stuck in an INSERTION_PENDING hot-swap state
AFRUmaybecomestuckintheINSERTION_PENDINGhot‐swapstateafteroneofthe
followingevents:
•ShelfPowerUp
•Afterinsertingitintheshelf
•AfterpowercyclingtheFRUprogrammatically