BGP Auto-peering Feature Limitations
NoteBGP and OSPFv2 Auto-peering are mutually exclusive. Only one form of Auto-peering can exist at a time.
The following features are not supported in BGP auto-peering:
- AutoBGP LAG with Extended Edge Switching
- Static LAG attachments to AutoBGP
- AutoBGP links on Extended Edge Switching ports
- MPLS, VPLS, L2VPN, L3VPN
- PIM Snooping, PIM-SM, SSM mode
- OSPF, OSPFv3, ISIS, RIP, RIPNG per VRF
- IPv6 within VRF
- VRF route leaking
- EVPN multi-homing Ethernet segments
- Explicit-remotes mode used for VNET flooding
- AutoBGP MLAG
- EVPN does not interoperate with third-party devices
The following limitations apply:
- Manual configuration of MLAG is supported. One MLAG peer per leaf node.
- Loss of first multicast packet in the flow is expected due to slow path forwarding.
- Static router must be an external router per VRF.
- VLANS spanning multiple bridges, where each bridge is AutoBGP LAG connected, must be VXLAN-based, or AutoBGP LAG replaced with MLAG.
- VLANs behind a bridge that is AutoBGP LAG connected and AutoBGP node has same VLAN ports must be VXLAN-based or AutoBGP LAG replaced with MLAG.