Specifications

2
Performing Updates Using rsys_swm
34
Using rsys_swm to perform upgrades
Thedefaultbehaviorofthersys_swmutilityistoupgradeallentitiesunderthedefaultroot
entitypathwhennophasesarespecifiedintheconfigurationfile.However,additionalcontrol
overtheorderandphasingoftheupgradescanbecontrolledthroughtheupgradecampaign
file.Forinformationonconfiguringanupgradecampaignfile,seepage 26.Sample
configurationfilesarealsoprovidedonpage 41.
Before performing an upgrade on a shelf, verify the following:
•Allmodulesareinastablestate.
•Therunningconfigurationsforallmoduleshavebeensaved.
•TheRadisysShMSismanagingtheshelfandthatalltheupdatetargetsareaccessiblefrom
theactiveShMS.
ToverifytheShMSisrunningandmanagingtheshelf,youcanentereitherofthe
followingcommandsonanATCA‐2210.
FromtheLinuxroot:
root@ATCA‐2210@43‐1‐7:~#shmgrstatus
FromtheCLI,enter:
platform‐mgmt
showchassisstatus
•Theupdaterepositoryhasbeensetupandisavailablelocallyontheupdatehost
machine.
•Theupdatehostisrunning theappropriatefiletransferservers(TFTPorFTPdaemons)so
theupdatebundlescanbedownloadedtothemodulesfromtherepository.
•AllupdatetargetsarereachableovertheBaseEthernetinterfacefromthehostmachine
runningrsys_swmduringandaftertheirupdate.
•TheBladeHSDsforallthemodulesareregisteredwiththeShMS,ifyouareperforminga
shelf‐levelupgradewithmultiplebladesandphases.Seepage 18forinformation.
•Forsinglemoduleupgrades,verifytheBladeHSDisrunningonthemoduleanditis
accessibleovertheBaseEthernet.Seepage 18forinformation.