I have a working Quagga config on an Ubuntu machine but when I copy the exact same config to a CumulusVX VM one of my peers is getting resets and another one doestn come up at all.
IP's are the same.
The peers that have issues are Cisco cloud services router vm's.
Exabgp peers have no problems.
The bgpd version is 0.99.22.4.
CumuluxVX bgpd version is 0.99.23.1
This is my config:
!! Zebra configuration saved from vty
! 2015/09/29 17:01:54
enable password xxxx
router bgp 7000
bgp router-id 220.127.116.11
no bgp default ipv4-unicast
neighbor 18.104.22.168 remote-as 7000
neighbor 22.214.171.124 timers 2 6
neighbor 126.96.36.199 activate
neighbor 188.8.131.52 route-server-client
neighbor 184.108.40.206 route-map RSCLIENT-IMPORT import
neighbor 220.127.116.11 route-map RSCLIENT-EXPORT export
neighbor 18.104.22.168 remote-as 7000
neighbor 22.214.171.124 timers 2 6
neighbor 126.96.36.199 activate
neighbor 188.8.131.52 route-server-client
neighbor 184.108.40.206 remote-as 7000
neighbor 220.127.116.11 timers 2 6
neighbor 18.104.22.168 activate
neighbor 22.214.171.124 route-server-client
neighbor 126.96.36.199 route-map RSCLIENT-IMPORT import
neighbor 188.8.131.52 route-map RSCLIENT-EXPORT export
neighbor 184.108.40.206 remote-as 7000
neighbor 220.127.116.11 timers 2 6
neighbor 18.104.22.168 activate
neighbor 22.214.171.124 route-server-client
ip prefix-list VIPS seq 5 permit 126.96.36.199/24 le 32
ip prefix-list VIPS seq 10 deny any
route-map RSCLIENT-EXPORT permit 10
match ip address prefix-list VIPS
route-map RSCLIENT-IMPORT deny 10
route-map R-IMPORT permit 10
route-map R-EXPORT deny 10
The peers having problems are 188.8.131.52 and 184.108.40.206.
220.127.116.11 is not contacted and 18.104.22.168 gets getting resets
I thought about evaluating Cumulus for the job as BGP route reflector but at the moment I am not convinced...