SD-WAN Edge and Gateway BGP flaps are not reported in the Orchestrator.
search cancel

SD-WAN Edge and Gateway BGP flaps are not reported in the Orchestrator.

book

Article ID: 372998

calendar_today

Updated On:

Products

VMware VeloCloud SD-WAN Edge Appliance VMWare SD-WAN VMware SD-WAN by VeloCloud VMware VeloCloud SD-WAN

Issue/Introduction

When an edge BGP neighbor is flapping, not all the neighbor state changes will show up in the VCO events for that edge.

In the case of a gateway BGP peer, the "Related State Change Events" on the "BGP Gateway Neighbor State" may not reflect the latest BGP flap, but the Up/Down time will indicate the peer state has changed more recently.

Cause

This is due to the way we currently identify neighbor state changes and send them to the VCO:

  1. The edge or gateway polls the BGP state every 60 seconds, and sends the results to the VCO.

  2. The VCO compares this to the last reported state and generates an event if it's different.

This means any BGP flap that happens within that 60 seconds does not show up on the VCO.  If for example the neighbor state was Established, and then was at another state like Active or Connect during the next 60-second poll, that change would show up as an event in the VCO.

 

Resolution

This is the way we currently report BGP neighbor state events in the VCO.

If there is any interest in submitting an enhancement request to improve how we do this, please speak with your account manager or solutions engineer with Broadcom SD-WAN.