Forum Discussion
Sep 29, 2017
When using a REST API call of
/mgmt/tm/cm/failover-status?$select=details
to both devices in a sync-failover device group you can expect results as follows:
Unit being active for traffic-group-1 and traffic-group-2:
{
"entries": {
"https://localhost/mgmt/tm/cm/failover-status/0": {
"nestedStats": {
"entries": {
"https://localhost/mgmt/tm/cm/failoverStatus/0/details": {
"nestedStats": {
"entries": {
"https://localhost/mgmt/tm/cm/failoverStatus/0/details/0": {
"nestedStats": {
"entries": {
"details": {
"description": "active for /Common/traffic-group-1"
}
}
}
},
"https://localhost/mgmt/tm/cm/failoverStatus/0/details/1": {
"nestedStats": {
"entries": {
"details": {
"description": "active for /Common/traffic-group-2"
}
}
}
}
}
}
}
}
}
}
}
}
Unit being standby for traffic-group-1 and traffic-group-2:
"entries": {
"https://localhost/mgmt/tm/cm/failover-status/0": {
"nestedStats": {
"entries": {}
}
}
}
}
Tested on TMOS v12.1.2 via BIG-IQ REST API proxy to a device service cluster of 2 BIG-IP VE.