Arista BGP parser missing origin protocol extraction and validation

[dhalperi]

Problem

Arista BGP route parsing doesn't extract origin protocol information from show ip bgp output, resulting in incomplete BGP RIB route validation.

Technical Details

The AristaBgpRoute model and parser currently lack origin_protocol field extraction and validation. This means BGP route validation cannot properly compare origin protocols (iBGP vs eBGP, connected, aggregate, etc.) between device output and Batfish modeling.

Observed In

All labs using Arista devices with BGP configurations.

Symptoms

• BGP RIB validation missing origin protocol comparison
• Incomplete route attribute validation for Arista BGP routes
• Code comments indicate missing functionality for iBGP/eBGP distinction

Configuration Patterns

Arista devices with:

• BGP configurations with mixed route origins
• iBGP and eBGP peering
• Route redistribution from other protocols

Next Steps

Update Arista BGP parser to extract origin protocol information and enhance AristaBgpRoute model to include origin_protocol field for complete validation.