fcocquyt_104704
Nimbostratus
Nimbostratushow to verify the fail-over status via cli (tmos)
Hello,
I'm running 10.2.1 Build 511.0. How can I check the failover status via CLI ? I have both boxes in standby status...
Thanks, frederik
Forum Discussion
8 Replies
Os_69448Hi.
Please try the following show commands for HA tables and failures.
b ha table
b ha table failures
EDIT: for tmsh, try
show /sys ha-status all-properties
Regards Os
fcocquyt_104704On the first one: [admin@xxxxxxxxx:Standby] ~ b ha table HIGH AVAILABILITY TABLE Feature Key Action En? Act Data Daemon Heartbeat mcpd restart all yes no 6.452M Invalid License mcpd go offline downlinks no no 0 Forced Offline sod no action yes no 0 Daemon Running tmm go offline downlinks yes no 0 Network Failover peer_state go active yes no 5 Config Not Received sod go offline yes no 0 Daemon Running bcm56xxd go offline downlinks yes no 0 TMM Detect Failure tmm failover yes no 0 Daemon Heartbeat tmm go offline downlinks restart yes no 194094 Switchboard Failsafe lacpd go offline abort tm yes no 0 Daemon Running named go offline downlinks yes no 0 Interface Failsafe tmm1 reboot yes no 0 Daemon Heartbeat tmm1 go offline downlinks restart yes no 194092 Interface Failsafe tmm2 reboot yes no 0 Daemon Heartbeat tmm2 go offline downlinks restart yes no 194088 Interface Failsafe tmm3 reboot yes no 0 Daemon Heartbeat tmm3 go offline downlinks restart yes no 194094 Interface Failsafe tmm4 reboot yes no 0 Daemon Heartbeat tmm4 go offline downlinks restart yes no 194094 Interface Failsafe tmm5 reboot yes no 0 Daemon Heartbeat tmm5 go offline downlinks restart yes no 194092 Interface Failsafe tmm6 reboot yes no 0 Daemon Heartbeat tmm6 go offline downlinks restart yes no 194091 Interface Failsafe tmm7 reboot yes no 0 Daemon Heartbeat tmm7 go offline downlinks restart yes no 194092 Daemon Heartbeat tmrouted restart no no 0 Daemon Heartbeat cbrd restart yes no 98669 Software Update lind reboot yes no 0 Ready for World tmm7 no action yes yes 0 Ready for World tmm6 no action yes yes 0 Ready for World tmm5 no action yes yes 0 Ready for World tmm4 no action yes yes 0 Ready for World tmm3 no action yes yes 0 Ready for World tmm2 no action yes yes 0 Ready for World tmm1 no action yes yes 0 Daemon Heartbeat bcm56xxd restart yes no 88209 Interface Failsafe tmm reboot yes no 0 Ready for World tmm no action yes yes 0 Daemon Running tmrouted failover no no 0 Hardwired Failover sod go active yes no 0 Reboot Requested sod reboot yes no 0 Daemon Running mcpd go offline downlinks yes no 0 Daemon Heartbeat sod restart all yes no 990631 Overdog Control watchdog no action yes no 0 Daemon Heartbeat bigd restart yes no 193999 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 Pool Min Up Member Gateway-Unit1 failover yes yes 1 [admin@xxxxxxxxx:Standby] ~ b ha table failures HIGH AVAILABILITY TABLE Feature Key Action En? Act Data VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 VLAN Failsafe Internal-53 failover yes yes 0 Pool Min Up Member Gateway-Unit1 failover yes yes 1 [admin@Ixxxxxxxx:Standby] ~ On the sec. one: [admin@yyyyyyyyyyy:Standby] ~ b ha table HIGH AVAILABILITY TABLE Feature Key Action En? Act Data Daemon Heartbeat mcpd restart all yes no 528.3M Invalid License mcpd go offline downlinks no no 0 Forced Offline sod no action yes no 0 Daemon Running tmm go offline downlinks yes no 0 Network Failover peer_state go active yes no 5 Config Not Received sod go offline yes no 0 Daemon Running tmrouted failover no no 0 TMM Detect Failure tmm failover yes no 0 Daemon Heartbeat tmm go offline downlinks restart yes no 49.20M Daemon Heartbeat bcm56xxd restart yes no 22.20M Ready for World tmm1 no action yes yes 0 Daemon Heartbeat tmm1 go offline downlinks restart yes no 49.20M Interface Failsafe tmm2 reboot yes no 0 Ready for World tmm3 no action yes yes 0 Daemon Heartbeat tmm3 go offline downlinks restart yes no 49.20M Interface Failsafe tmm4 reboot yes no 0 Ready for World tmm5 no action yes yes 0 Daemon Heartbeat tmm5 go offline downlinks restart yes no 49.20M Interface Failsafe tmm6 reboot yes no 0 Ready for World tmm7 no action yes yes 0 Daemon Heartbeat tmm7 go offline downlinks restart yes no 49.20M Daemon Heartbeat tmrouted restart no no 0 Daemon Heartbeat cbrd restart yes no 24.60M Software Update lind reboot yes no 0 Interface Failsafe tmm7 reboot yes no 0 Daemon Heartbeat tmm6 go offline downlinks restart yes no 49.20M Ready for World tmm6 no action yes yes 0 Interface Failsafe tmm5 reboot yes no 0 Daemon Heartbeat tmm4 go offline downlinks restart yes no 49.20M Ready for World tmm4 no action yes yes 0 Interface Failsafe tmm3 reboot yes no 0 Daemon Heartbeat tmm2 go offline downlinks restart yes no 49.20M Ready for World tmm2 no action yes yes 0 Interface Failsafe tmm1 reboot yes no 0 Daemon Running named go offline downlinks yes no 0 Switchboard Failsafe lacpd go offline abort tm yes no 0 Interface Failsafe tmm reboot yes no 0 Ready for World tmm no action yes yes 0 Daemon Running bcm56xxd go offline downlinks yes no 0 Hardwired Failover sod go active yes no 0 Reboot Requested sod reboot yes no 0 Daemon Running mcpd go offline downlinks yes no 0 Daemon Heartbeat sod restart all yes no 250.5M Overdog Control watchdog no action yes no 0 Daemon Heartbeat bigd restart yes no 49.11M Pool Min Up Member Gateway-Unit2 failover yes yes 1 [admin@yyyyyyyyyyy:Standby] ~ [admin@yyyyyyyyyy:Standby] ~ b ha table failures HIGH AVAILABILITY TABLE Feature Key Action En? Act Data Pool Min Up Member Gateway-Unit2 failover yes yes 1 [admin@yyyyyyyyyy:Standby] ~- fcocquyt_104704
I can ping both units there FO IP's so it seems they see each other. I'm not sure why both show as "standby". Isn't there away to force on active ?
Kind regards, frederik
- nag_54823
Cirrostratus
pls check failover.forcestandby is enabled on both the boxes ? default conifg for failover.forceactive and failover.forcestandby should be in disabled state.
- nag_54823
also check any gateway failover configured . if so , please see whether u r able to reach the ip which is conifgured in gateway pool.
Sorry for being a bit late on the subject.
To monitor device states and traffic-groups especially during upgrades and other breathtaking operations in real-time I´m simply using the following line:watch -n 1 -d tmsh show cm traffic-groupIt will list the available devices and their state and the current device for each floating traffic-group updated every second. The "-d" switch highlights changes by inverting them.
Regarding the specific question here:
1. legacy failsafe mechanisms (vlan & gateway) may cause a standby/standby 2. check /var/log/ltm for "failsafe" related messages, pleaseThanks, Stephan
nitassEmployee
I can ping both units there FO IP's so it seems they see each other. I'm not sure why both show as "standby". Isn't there away to force on active ?
failsafe is triggered on both units (xxxxxxxxx and yyyyyyyyyy). you have to fix the failsafe issue or disable it. forcing active won't work.
sol12277: How simultaneous failsafe events affect a redundant system
http://support.f5.com/kb/en-us/solutions/public/12000/200/sol12277
