Forum Discussion
TomSu_93471
Jan 30, 2012Nimbostratus
Splitting 2 production Viprion clusters(active-stdby) into two..
Hi,
I need to split 2 production Viprion clusters (redundant pair -Active/Stdby) into two standalone clusters.
Since this is Active-Stdby config I suppose I could just force offline the stdb...
TomSu_93471
Jan 31, 2012Nimbostratus
@nitass
Thanks for confirmation.
1) Regarding the sod process, I was able to find this on AskF5:
" The sod process is the high availability management daemon for the BIG-IP system. The heartbeat timeout for the sod process is 60 seconds, and the default failover action for redundant systems is restart all. Therefore, if the sod process does not increment its heartbeat in 60 seconds, the BIG-IP system restarts all system services.
When the heartbeat timeout for the sod process expires, the system logs the following message to the /var/log/ltm file:
overdog[1628]: 01140029:5: HA daemon_heartbeat sod fails action is restart all.
"
so as far as I understood it, in your case on Active cluster sod was restarted due to your config change -> SingleDevice, which makes sense since sod is ha deamon so its need to be restarted due to such config change. And for the redundant node heartbeat failed and it had restarted all its services and they have come up in active state?
2) When you changed the setting to SingleDevice was all the realted HA config deleted automatically ? I mean things like: - gateway failsafe/vlan failsafe - config sync mechanism - network mirroring - mirror persistency and etc. ? I'd like to know if there are any left overs in the config which must be manually removed to not case issues later.
Thanks, Tom
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects