BGP Route Reflector config

[Anzi Mukundan]

Hello All,

Router1-------Router2-----Router3

I'm attempting to set up iBGP between each of these routers. Router2 was to be set up as a route reflector.

According to Cisco configurations, when creating a neighbor on a route reflector, the neighbor must be designated as a route-reflector-client.
Only that configuration is necessary to configure the route reflector.

What will be the sonic configurations for BGP route reflector.
If the following cli on Router2 is sufficient to configure the route-reflector, for instance?
config bgp-neighbor-af add --rrclient true default 70.70.70.2 ipv4

Kindly help with this query

Thanks,

Anzi

[Sudhin Jacob]

http://docs.frrouting.org/en/latest/bgp.html#route-reflector

Please refer to the above document.

Regards,

Sudhin

--
You received this message because you are subscribed to the Google Groups "sonicproject" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonicproject...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/215dd011-2218-48a8-8dca-e633772672bfn%40googlegroups.com.

[Anzi Mukundan]

Thanks Sudhin for the update. Can you please let me know the relevant click CLI for the same command

[Anzi Mukundan]

Hi Sudhin,

I could not see this option route-reflector-client

Default-string(config-router)# neighbor 70.70.70.1
  advertisement-interval         Minimum interval between sending BGP routing updates
  bfd                            BFD support
  capability                     Advertise capability to the peer
  description                    Neighbor specific description
  disable-connected-check        one-hop away EBGP peer using loopback address
  disable-link-bw-encoding-ieee  Disable IEEE floating-point encoding for extended community bandwidth
  dont-capability-negotiate      Do not perform capability negotiation
  ebgp-multihop                  Allow EBGP neighbors not on directly connected networks
  enforce-first-as               Enforce the first AS for EBGP routes
  enforce-multihop               Enforce EBGP neighbors perform multihop
  extended-optional-parameters   Force the extended optional parameters format for OPEN messages
  graceful-restart               Graceful Restart command for a neighbor
  graceful-restart-disable       Graceful Restart Disable command for a neighbor
  graceful-restart-helper        Graceful Restart Helper command for a neighbor
  interface                      Enable BGP on interface
  local-as                       Specify a local-as number
  maximum-prefix-out             Maximum number of prefixes to be sent to this peer
  override-capability            Override capability negotiation result
  passive                        Don't send open messages to this neighbor
  password                       Set a password
  peer-group                     Member of the peer-group
  port                           Neighbor's BGP port
  remote-as                      Specify a BGP neighbor
  sender-as-path-loop-detection  Detect AS loops before sending to neighbor
  shutdown                       Administratively shut down this neighbor
  solo                           Solo peer - part of its own update group
  strict-capability-match        Strict capability negotiation match
  tcp-mss                        TCP max segment size
  timers                         BGP per neighbor timers
  ttl-security                   BGP ttl-security parameters
  update-source                  Source of routing updates
Default-string(config-router)# neighbor 70.70.70.1

Thanks,

Anzi

[Chriztoffer]

The command is there according to the v7.5.1 docs.

http://docs.frrouting.org/en/stable-7.5/bgp.html#route-reflector

**HINT** Use the (frr) 'find' command to find at which levels a
command/parameter can be used.

router# find route-reflector-client
(bgp) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp) no neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp vpnv4) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp vpnv4) no neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp vpnv6) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp vpnv6) no neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv4 unicast) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv4 unicast) no neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv4 multicast) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv4 multicast) no neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp ipv4 labeled unicast) neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp ipv4 labeled unicast) no neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp ipv6) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv6) no neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv6 multicast) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv6 multicast) no neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp ipv6 labeled unicast) neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp ipv6 labeled unicast) no neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp evpn) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp evpn) no neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv4 flowspec) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv4 flowspec) no neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client
(bgp ipv6 flowspec) neighbor <A.B.C.D|X:X::X:X|WORD> route-reflector-client
(bgp ipv6 flowspec) no neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client

router# configure terminal
router(config)# router bgp
router(config-router)# address-family ipv[64] unicast
router(config-router-af)# [no] neighbor <A.B.C.D|X:X::X:X|WORD>
route-reflector-client

> To view this discussion on the web visit https://groups.google.com/d/msgid/sonicproject/f35441d1-37eb-41a2-93bd-bc5ee5733f0en%40googlegroups.com.

[Anzi Mukundan]

Thanks Chriztoffer.