Forum Discussion
2 Replies
Sort By
Hi,
there is no concept of primary or secondary unit in the TMOS device clustering in terms of prioritization or preference. Personally sometimes I am using "primary/secondary" to reference the active or standby unit. You can run the following to monitor it in real time on CLI:watch -d "tmsh show sys cm traffic-group"
I run the upgrade on the standby unit first and follow these steps:
1. relicense (will restart services and is not required when staying on the same maintenance release level) 2. upload base and hotfix images (will be placed in /shared/images) 3. create configuration backup 4. put unit into forced offline state 5. install hotfix to new installation volume (base image will be installed automatically if available) 6. reboot to new target volume including copy of configuration of current installation volume 7. release unit from forced offline after seeing heartbeat communication reestablished 8. put currently active unit in standby or forced offline 9. run your tests 10. repeat all steps on the remaining unitYou can monitor the installation progress on CLI as well:
watch -d "tmsh show sys software"
Thanks, Stephan
- GauravCh000_237Nimbostratus
Thank You Sir