Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
What does a status circle split in two mean in the vService list in a cluster?
Short answer
While the cluster is enabled, the Status circle in the vService list is split into two halves. The left half is for the device logged in to and the right half is for the peer device: each shows the status that device evaluates for that vService; when the pointer is moved over a half, the tooltip shows the name of the device and the status. The colors show the status on each device: green OK, yellow Warning, red Error, gray Disabled. The two halves being in different colors shows that the problem is on only one device; for example, the Backend Services cannot be reached from only one device, or the cluster connection with the peer device has been lost. The status of the VIP is reflected on both halves together; if the VIP has moved to the peer device, both halves become Warning.
Colors
| Color | Tooltip | Meaning on this device |
|---|---|---|
| Green | OK | The vService is running, its Frontend IPs are in place, the Backend Services are healthy |
| Yellow | Warning | Some Backend Services are unhealthy or in maintenance, some Frontend IPs have a problem, the VIP is on the Slave device, or there is a risk of the VIP being active on both devices at once because the peer device cannot be reached |
| Red | Error | The vService is not running, there is no healthy Backend Service, or all of its Frontend IPs have a problem; in the peer device half, additionally, the loss of the cluster connection |
| Gray | Disabled | The vService has been turned off manually, the license has stopped the traffic (Stopped by the license in Details), or it has no active Frontend IP on this device |
| Accent color | Evaluating | The vService is being created, edited or reloaded |
| Dark accent | Unknown | The status could not be read yet |
Each device performs the health check of the Backend Services itself; therefore, the Backend Service evaluation of the two halves may differ (Health Checks).
Typical Views
| Left / right | Meaning |
|---|---|
| Green / green | Both devices are healthy, the VIP is on the Master device |
| Yellow / yellow | The VIP has moved to the Slave device (failover has occurred), or some Backend Services are unhealthy on both devices |
| Yellow / red | The peer device cannot be reached (the cluster connection is down or the peer device is off) |
| Green / yellow or red | The problem is only on the peer device; mostly the access from that device to the Backend Services |
| Green / gray | The vService has no active Frontend IP on the peer device; e.g. the VIP has been turned off for that device with Disable for |
How Is It Inspected?
- In the Load Balancer vService list, the pointer is moved over the half; the device name and the status are seen in the tooltip (listing screen).
- The row is clicked; the status messages are read in the Details tab of the preview panel (e.g. "VIP … is on slave") (preview).
- If it is caused by the VIP, the status of the VIP in the two device columns is checked on the Network → Interfaces screen (interface and IP statuses).
Common Misconceptions
- "The left half is the Master device." The left half is always the device logged in to; Master/Slave is separate for each VIP.
- "If both halves are yellow, the service has stopped." If the VIP is on the peer device, the service continues to run; the yellow color shows that the VIP is not where it is configured to be.
- "The Status value in the filter bar counts the two halves separately." Filtering and sorting use a single combined status calculated from the two halves.
How it is done in the documentation
