Bug ID 659625: Manually adding a node to a second proxy will mark the node forced offline

Last Modified: Jun 27, 2019

Bug Tracker

Affected Product:  See more info
Application Connector All(all modules)

Known Affected Versions:
1.0.1

Fixed In:
1.1.0

Opened: Apr 20, 2017
Severity: 4-Minor

Symptoms

When manually adding nodes to two Application Connector Proxy instances, the initial state after adding is Disabled. On the BIG-IP this makes the node Forced Offline. This also applies when you manually add identical nodes to a second Application Connector Proxy instance, the initial node state on that proxy is Disabled. If the node was enabled from the other proxy, it will become disabled.

Impact

When the node is added on the second proxy, it will mark the node as Forced Offline until you enable it from either proxy.

Conditions

Two Application Connector Proxy instances connected to a BIG-IP from the same VPC and you are manually adding identical nodes for redundancy.

Workaround

This does not occur if you are creating nodes using the REST API, because they can be set to Enabled in the same API call.

Fix Information

While filling out the form to add a node, the red circle in the Status column can be clicked, it will turn to Green. This means when you save the new node it will be marked as enabled.

Behavior Change