You can configure a peer group on a tenant BGP.
efa tenant service bgp peer-group create --name <peer-group-name> --tenant <tenant-name> --description <description> --pg-name <border-leaf-ip:pg-name> --pg-asn <border-leaf-ip:pg-name,remote-asn> --pg-bfd <border-leaf-ip:pg-name,bfd-enable(true/false),interval,min-rx,multiplier> --pg-next-hop-self <border-leaf-ip:pg-name,next-hop-self(true/false/always)> --pg-update-source-ip <border-leaf-ip:pg-name,update-source-ip>
The following example creates a BGP peer group on tenant BGP:
efa tenant service bgp peer-group create –name ten1BgpPG1 --tenant tenant1 --pg-name BL1-IP:pg1 --pg-asn BL1-IP:pg1,6000 --pg-bfd BL1-IP:pg1,true,100,200,5 --pg-next-hop-self BL1-IP:pg1,true --pg-update-source-ip BL1-IP:pg1,10.20.30.40
efa tenant service bgp peer-group update --name <peer-group-name> --tenant <tenant-name> --operation <peer-group-add|peer-group-delete|peer-group-desc-update> --description <description> --pg-name <border-leaf-ip:pg-name> --pg-asn <border-leaf-ip:pg-name,remote-asn> --pg-bfd <border-leaf-ip:pg-name,bfd-enable(true/false),interval,min-rx,multiplier> --pg-next-hop-self <border-leaf-ip:pg-name,next-hop-self(true/false/always)> --pg-update-source-ip <border-leaf-ip:pg-name,update-source-ip>
The following example updates a BGP peer group on tenant BGP:
efa tenant service bgp peer-group update --name ten1BgpPG1 --tenant tenant1 --operation peer-group-add --pg-name BL1-IP:pg2 –pg-asn BL1-IP:pg2,7000 --pg-bfd BL1-IP:pg2,true,200,300,6 --pg-next-hop-self BL1-IP:pg2,true --pg-update-source-ip BL1-IP:pg2,10.20.30.41