frr.conf: setting timers manually that would be set by the --enable-datacenter flag on frr. this way we don't have to compile our own frr. --enable-cumulus at this point only enables and alias for bgp address-family of evpn vs address-family l2vpn evpn. which we don't use anyway or already do it the right way
This commit is contained in:
parent
48abb08b5a
commit
c99727567d
|
@ -17,12 +17,18 @@ interface feth2
|
|||
!
|
||||
router bgp NODEASN
|
||||
bgp router-id FRRROUTERID
|
||||
bgp log-neighbor-changes
|
||||
no bgp default ipv4-unicast
|
||||
bgp default show-hostname
|
||||
bgp deterministic-med
|
||||
coalesce-time 1000
|
||||
bgp bestpath as-path multipath-relax
|
||||
bgp bestpath compare-routerid
|
||||
bgp network import-check
|
||||
timers bgp 3 9
|
||||
neighbor fabric peer-group
|
||||
neighbor fabric remote-as external
|
||||
neighbor fabric timers connect 10
|
||||
neighbor feth1 interface peer-group fabric
|
||||
neighbor feth2 interface peer-group fabric
|
||||
!!! neighbor GRE peer-group
|
||||
|
@ -30,16 +36,22 @@ router bgp NODEASN
|
|||
!!! neighbor GRE local-as FRR_GRE_ASN
|
||||
!!! neighbor GRE password wIt2Go
|
||||
!!! neighbor GRE ebgp-multihop 255
|
||||
!!! neighbor GRE timers connect 10
|
||||
!!! neighbor eBGPv4 peer-group
|
||||
!!! neighbor eBGPv4 remote-as external
|
||||
!!! neighbor eBGPv4 timers connect 10
|
||||
!!! neighbor eBGPv6 peer-group
|
||||
!!! neighbor eBGPv6 remote-as external
|
||||
!!! neighbor eBGPv6 timers connect 10
|
||||
!!! neighbor iBGP peer-group
|
||||
!!! neighbor iBGP remote-as internal
|
||||
!!! neighbor iBGP timers connect 10
|
||||
!!! neighbor CUSTOMERv4 peer-group
|
||||
!!! neighbor CUSTOMERv4 remote-as external
|
||||
!!! neighbor CUSTOMERv4 timers connect 10
|
||||
!!! neighbor CUSTOMERv6 peer-group
|
||||
!!! neighbor CUSTOMERv6 remote-as external
|
||||
!!! neighbor CUSTOMERv6 timers connect 10
|
||||
!!! FRR_EDGE_NEIGH
|
||||
!
|
||||
address-family ipv4 unicast
|
||||
|
|
Loading…
Reference in New Issue