NXOS HSRP routes not modeled in Batfish route tables

[dhalperi]

Problem

Batfish does not include HSRP (Hot Standby Router Protocol) routes in route table outputs for NXOS devices, causing validation discrepancies when comparing against real device state.

Technical Details

NXOS generates local hsrp routes in the main RIB when HSRP is configured on an interface. These routes appear in show ip route output with protocol type "hsrp" but are not present in Batfish's route analysis.

Observed In

NXOS lab configurations with HSRP interface configurations

Symptoms

• Lab validation tests fail when comparing route tables between Batfish analysis and NXOS device output
• HSRP routes present in device show ip route are missing from Batfish route queries
• Current workaround: NxosValidator filters out HSRP routes from validation (line 80 in NxosValidator.py)

Configuration Patterns

NXOS interfaces with HSRP configuration generate routes like:

172.221.33.33/32, ubest/mbest: 1/0, attached
    *via 172.221.33.33, Vlan100, [0/0], 20:26:45, hsrp

Next Steps

Investigate whether Batfish should model HSRP routes in its route analysis, or if the current filtering approach is the intended behavior for these protocol-specific routes.