Specifications

2
Performing Updates Using rsys_swm
14
Determine when to perform the update
Yourplanningshouldtak eintoaccountthetimeneededtoperformtheupdateandthe
downtimeinvolved.Table 3showstheestimatedtimeittakesforoneupdatepassona
fully‐populatedplatform.
Usingthisestimate,asingleupdatepasswilltak eapproximately16minutes.
Theactualtimeittakesonyoursystemtoperformanupdatepasswillvarydependingonthe
numberofphasesdefinedintheconfigurationfile,networkingspeed,IPMBtraffic,andJFFS
accessspeed.Thefirmwareandthesoftwareupdatesaredoneonlivesystems,sodowntime
islimitedtorebootsthattakeapproximately5minutesforallmodulesintheshelf.
Takeintoconsiderationthatyouwillneedtoperformmorethanoneupdatepasstoupgrade
afully‐populatedplatform.Forexample,ifyouareperformingasinglebankupgrade,youwill
needtoperformtwoupdatepasses.Ifyouareupgradingbothbanks,youwillneedto
performfourupdatepasses(seepage 13forexamplesoftheupgradeprocedures).Youwill
alsoneedtofactorinanytimeittakestoperformtheswitchoverandtheverificationsteps
betweentheupdatepassesforyourtotalupgr adetime.
Save the running configurations on modules
Verifyallthemodulesareinastablestateandsavetheirrunningconfigurations.
TheSMFpreser vesdefaultconfigurationsacrossupdatesfortheATCA‐1200,ATCA‐2210,
ATCA‐7220,andATCA‐9100.Configurationsarepreservedinbothbankstoretaintheexisting
setupinformation.EachATCAsoftwarereleaseCD‐ROMimagecontainsalistoffilestobe
preserved,andyoucangenerateacustomlistthatspecifiesadditionalfileswithinthe/etc
directorytopreserve.
Filepreservationworksasfollows:
•BeforetheOSupdatebegins,theconfigurationiscopiedfromtheactiveflashbanktothe
standbyflashbank.
•Aftertheupdate
isactivated,themodulerebootstothestandbybank.
Duringbootup:
•thesavedconfigurationissavedtoatemporarylocation,
Table 3. Estimated time per update pass
Tasks completed during update pass Time Affected components
Bundle download and image verification 3 minutes All modules, including Blade HSD restart for bundle
activation.
Installation and verification pass 11 minutes All LMP, IPMC, BIOS components.
The components are updated in parallel. The process
completes when everything has finished updating on all the
components.
Activation 2 minutes All the Blade HSDs.
This includes the time it takes each Blade HSD to initialize.