Symptoms

When a blade becomes unreachable over the internal network on a VELOS chassis, the following symptoms may be observed: HA arbitration-state event messages appear in system logs (show system events or velos.log) Messages indicate "Asserted: local arbitration request-active state" and "Asserted: peer arbitration request-active state" followed by corresponding "Deasserted" messages Events are logged on both controller-1 and controller-2 Example log entries: event="66048 controller-2 arbitration-state EVENT Network Access 'Asserted: local arbitration request-active state'" event="66048 controller-2 arbitration-state EVENT Network Access 'Deasserted: local arbitration request-active state'" event="66048 controller-1 arbitration-state EVENT Network Access 'Asserted: peer arbitration request-active state'" event="66048 controller-1 arbitration-state EVENT Network Access 'Deasserted: peer arbitration request-active state'"

Impact

-- Cosmetic/Informational: The arbitration event messages are spurious and do not reflect an actual HA failover condition -- No functional impact: The active controller remains active and stable; no actual failover occurs -- No service disruption: The HA state machine correctly determines the proper active controller, and the standby controller deasserts its REQUEST_ACTIVE state appropriately

Conditions

-- VELOS chassis with dual system controllers configured in HA mode -- A blade is installed and present in the chassis -- Internal control plane network connectivity to the blade is lost or interrupted (e.g., control plane links to the blade slot are disabled on both controllers) -- Complete loss of connectivity to the blade, including console access

Workaround

These messages can be safely ignored as they do not indicate a real HA problem or require any corrective action.The HA arbitration state resolves automatically once the HA state machine completes its evaluation

Fix Information

None

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips