A10 kernel routes non-deterministic due to equal VRRP-A priorities #56
Description
Problem
A10 kernel route validation fails due to non-deterministic VRRP-A behavior when load balancers have equal priorities, causing inconsistent route ownership between lab runs and Batfish modeling.
Technical Details
When A10 load balancer pairs have identical VRRP-A priorities, the device that becomes active (and receives kernel routes) depends on boot timing rather than deterministic configuration. This creates validation inconsistencies as the actual active device may differ from Batfish modeling assumptions.
Observed In
traditional_dc_T107
Symptoms
- Kernel routes appearing on different A10 devices between lab data collection and Batfish analysis
- Main RIB validation failures due to route ownership uncertainty
- Non-deterministic VRRP-A failover behavior affecting route distribution
Configuration Patterns
A10 ACOS load balancer pairs with equal VRRP-A priorities in high availability configurations
Next Steps
Configuration update needed to assign different VRRP-A priorities to load balancer pairs to ensure deterministic active/standby selection, followed by lab data recollection