Forum Discussion
Nimbostratus"sod process" enabled in standalone mode causing undesirables failover.
Can I disable sod process in a standalone bigip deployment? My bigip it´s operating in standalone mode and sod forced a standalone bigip to go offline. there is no floating IP configured nor high availability VLAN.
I think sod process should be disabled...
Please you advice, here are the sod loggs:
log zgrep 'sod' /var/log/ltm
/var/log/ltm:Jan 21 16:36:12 dns1 info sod[5657]: 0114002b:6: HA forced_offline sod enabled.
/var/log/ltm:Jan 21 16:36:12 dns1 info sod[5657]: 0114002b:6: HA reboot_request_t sod enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 0114002b:6: HA proc_running mcpd enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 0114002b:6: HA daemon_heartbeat sod enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 0114002b:6: HA proc_running tmm enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 0114002b:6: HA proc_running bd enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 0114002b:6: HA proc_running datasyncd enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 notice sod[5657]: 010c0057:5: Activating traffic group traffic-group-1.
/var/log/ltm:Jan 21 16:36:43 dns1 notice sod[5657]: 010c0054:5: Offline for traffic group traffic-group-1.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 010c0022:6: Opening /dev/tty01 for failover monitoring.
/var/log/ltm:Jan 21 16:36:43 dns1 info sod[5657]: 0114002b:6: HA hw_failover sod enabled.
/var/log/ltm:Jan 21 16:36:43 dns1 notice sod[5657]: 010c005f:5: Mcpd has reached phase base, current phase is running.
/var/log/ltm:Jan 21 16:36:43 dns1 notice sod[5657]: 010c006d:5: Leaving Offline for Standby for dbvar not redundant (tmm not ready).
/var/log/ltm:Jan 21 16:36:43 dns1 notice sod[5657]: 010c0052:5: Standby for traffic group traffic-group-1.
/var/log/ltm:Jan 21 16:36:43 dns1 notice sod[5657]: 010c0018:5: Standby
/var/log/ltm:Jan 21 16:36:45 dns1 warning sod[5657]: 01140029:4: HA proc_running tmm fails action is go offline and down links.
2 Replies
Lee_SutcliffeNacreous
traffic-group-1 looks to be going offline, this is a default traffic group but something may be triggering it to go offline
run the following command and see what failover objects are associated with it, it may give you a clue as to the problem
tmsh show cm traffic-group traffic-group-1 failover-objects
gu3rr3ir0Has anyone found the workaround for this problem? I´m having the same problem, and is putting one of the blades offline, after that message appears
