Connection problem between ExaBGP and Quagga

瀏覽次數:302 次
跳到第一則未讀訊息

Akilnath Bodipudi

未讀,
2020年5月12日 凌晨4:11:232020/5/12
收件者:exabgp-users

I am facing problem in connecting both the quagga and Exabgp, Could you help me in resolving it


Quagga
hostname SoftBGP
password zebra987
enable password zebra987
log file /var/log/quagga/bgpd.log

debug bgp events
debug bgp filters
debug bgp fsm
debug bgp keepalives
debug bgp updates

router bgp 65530
bgp router-id 172.16.0.18
bgp log-neighbor-changes

neighbor 172.16.0.26 remote-as 65501


ExaBGP
group Core_v4 {
hold-time 180;
local-as 65501;
peer-as 65530;
router-id 172.16.0.26;
graceful-restart 1200;
static {
route 10.10.10.1/32 next-hop 172.16.0.26 community 65501:666;
}
neighbor 172.16.0.18 {
local-address 172.16.0.26;
description "Quagga";
}
}


Run ExaBGP

sudo env exabgp.daemon.user=root exabgp.daemon.daemonize=true exabgp.daemon.pid=/var/run/exabgp.pid exabgp.log.destination=/var/log/exabgp.log exabgp /etc/exabgp_blackhole.conf


exabgp: 137982 configuration environment file missing
exabgp: 137982 configuration generate it using "exabgp --fi > /usr/etc/exabgp/exabgp.env"


Output ExaBGP

sudo cat /var/log/exabgp.log
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [notification sent (1,1)] error[Message header error / Connection Not Synchronized / waited for open too long, we do not like stuck in active]
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [closing connection] error[the TCP connection was closed by the remote end]
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [notification sent (1,1)] error[Message header error / Connection Not Synchronized / waited for open too long, we do not like stuck in active]
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [closing connection] error[the TCP connection was closed by the remote end]
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [notification sent (1,1)] error[Message header error / Connection Not Synchronized / waited for open too long, we do not like stuck in active]
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [closing connection] error[the TCP connection was closed by the remote end]
exabgp: 137982 network Peer 172.16.0.18 ASN 65530 out loop, peer reset, message [closing connection] error[the TCP connection was closed by the remote end]


Run Quagga

/etc/init.d/quagga restart


Output Quagga

sudo vtysh -d bgpd -c "show ip bgp summary"

BGP router identifier 172.16.0.18, local AS number 65530
RIB entries 0, using 0 bytes of memory
Peers 1, using 4568 bytes of memory

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
172.16.0.26 4 65501 8 16 0 0 0 never Active

Total number of neighbors 1

Thomas Mangin

未讀,
2020年5月12日 清晨5:12:212020/5/12
收件者:exabgp...@googlegroups.com
Hi,

Can you please provide the output of exabgp with "-d" as an option. I am not a quagga/frr user and can only help you with ExaBGP.

Also while I will be the first to admit that the documentation is atrocious, I have really little time to explain how the software works and really only look at bugs, not usage questions.
That said, if you provide the requested information, we may be able to help here.

Sincerely,

Thomas

--
You received this message because you are subscribed to the Google Groups "exabgp-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exabgp-users...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/exabgp-users/fc15ebe6-0961-403e-a335-d900e3a83f9b%40googlegroups.com.

Akilnath Bodipudi

未讀,
2020年5月12日 上午11:15:192020/5/12
收件者:exabgp...@googlegroups.com
Thanks a lot Thomas, I really appreciate your work and dedication towards ExaBGP. Any leads regarding the ExaBGP is really a great help towards my project.
ScreenShot 1.png
Screenshot2.png


Thomas Mangin

未讀,
2020年5月12日 上午11:55:272020/5/12
收件者:exabgp...@googlegroups.com
Hi,

ExaBGP tells you what to do. This is not an issue with the program. You have multiple BGP daemon on the same machine.
Please follow the configuration advice given by ExaBGP about not binding and it may work if setup correctly.

Sincerely,

Thomas



Akilnath Bodipudi

未讀,
2020年5月12日 中午12:02:512020/5/12
收件者:exabgp...@googlegroups.com
Thanks thomas, I will work on it. and let you  know the update about it.

Akilnath Bodipudi

未讀,
2020年5月12日 下午1:14:182020/5/12
收件者:exabgp...@googlegroups.com
Hi,
 I ran this command on quagga side.
netstat -lnpt|grep 179

Now on ExaBGP side. Started to run Exabgp.
fybercom@ddos:~$ sudo env exabgp.daemon.user=root exabgp.tcp.bind="0.0.0.0" exabgp.tcp.port=179 exabgp.daemon.daemonize=false exabgp.daemon.pid=/var/run/exabgp.pid exabgp.log.destination=/var/log/exabgp.log exabgp /etc/exabgp_blackhole.conf

After few secs, did with Exabgp -d command
Exabgp - Screen shot 1.png
Exabgp - Screen Shot 2.png
Exabgp - Screen Shot 3.png
Exabgp - Screen Shot 4.png
Quagga - Screen Shot 1.png

But i dont find Exabgp is established with quagga. Thanks in adavance
回覆所有人
回覆作者
轉寄
0 則新訊息