Configure Backup Routing Neighbors on BGP Peer

You can configure backup routing neighbors with additional attributes, such as bidirectional forwarding detection, route-maps and prefix-lists.

By default, backup routing neighbor is configured with remote-as and next-hop-self. You can provide md5-password as a fabric setting which is applied on the neighbors.

Note

Note

You can modify the MD5 password for the backup routing neighbors only by configuring and re-configuring the fabric.

  1. To create backup routing neighbors when you create a BGP peer, run the following command:
    efa tenant service bgp peer create --name <bgp-peer-name> --tenant <tenant-name>  --ipv4-uc-nbr <device-ip,vrf-name:neighbor-ip,remote-asn>   --ipv4-uc-nbr-bfd <device-ip,vrf-name:neighbor-ip,true|false>  --ipv4-uc-nbr-default-originate <device-ip,vrf-name:neighbor-ip,true/false>  --ipv4-uc-nbr-default-originate-route-map <device-ip,vrf-name:neighbor-ip,route-map>
  2. To create backup routing neighbors when you update a BGP peer, run the following command:
    efa tenant service bgp peer update --name <bgp-peer-name> --tenant <tenant-name>   --operation peer-add --ipv4-uc-nbr <device-ip,vrf-name:neighbor-ip,remote-asn>  --ipv4-uc-nbr-bfd <device-ip,vrf-name:neighbor-ip,true|false>  --ipv4-uc-nbr-default-originate <device-ip,vrf-name:neighbor-ip,true/false>
  3. To remove the backup routing neighbors association with BGP service when you delete a BGP peer, run the following command:
    efa tenant service bgp peer delete --name <bgp-peer-name> --tenant <tenant-name>