Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
root@fc0d038d7823:/exabgp# ./sbin/exabgp -e /etc/exabgp/exabgp.env /etc/exabgp/exabgp.conf --debug
20:03:41 | 378 | welcome | Thank you for using ExaBGP
20:03:41 | 378 | version | 4.0.2-1c737d99
20:03:41 | 378 | interpreter | 3.5.2 (default, Nov 17 2016, 17:05:23) [GCC 5.4.0 20160609]
20:03:41 | 378 | os | Linux fc0d038d7823 4.9.49-moby #1 SMP Fri Dec 8 13:40:02 UTC 2017 x86_64
20:03:41 | 378 | installation | /exabgp
20:03:41 | 378 | cli control | named pipes for the cli are:
20:03:41 | 378 | cli control | to send commands /run/exabgp/exabgp.in
20:03:41 | 378 | cli control | to read responses /run/exabgp/exabgp.out
20:03:41 | 378 | network | listening for BGP session(s) on 0.0.0.0:179
20:03:41 | 378 | configuration | performing reload of exabgp 4.0.2-1c737d99
20:03:41 | 378 | configuration | > template |
20:03:41 | 378 | configuration | > neighbor | 'all'
20:03:41 | 378 | configuration | . router-id | '172.18.0.3'
20:03:41 | 378 | configuration | . local-as | '65001'
20:03:41 | 378 | configuration | . hold-time | '20'
20:03:41 | 378 | configuration | > capability |
20:03:41 | 378 | configuration | . graceful-restart |
20:03:41 | 378 | configuration | < capability |
20:03:41 | 378 | configuration | < neighbor |
20:03:41 | 378 | configuration | < template |
20:03:41 | 378 | configuration | > neighbor | '172.18.0.2'
20:03:41 | 378 | configuration | . inherit | 'all'
20:03:41 | 378 | configuration | . local-address | '172.18.0.3'
20:03:41 | 378 | configuration | > family |
20:03:41 | 378 | configuration | . ipv4 | 'unicast'
20:03:41 | 378 | configuration | . ipv6 | 'unicast'
20:03:41 | 378 | configuration | < family |
20:03:41 | 378 | configuration | . peer-as | '65000'
20:03:41 | 378 | configuration | < neighbor |
20:03:41 | 378 | reactor | new peer: neighbor 172.18.0.2 local-ip 172.18.0.3 local-as 65001 peer-as 65000 router-id 172.18.0.3 family-allowed in-open
20:03:41 | 378 | network | listening for BGP session(s) on 0.0.0.0:179
20:03:41 | 378 | reactor | loaded new configuration successfully
20:03:41 | 378 | process | forked process api-internal-cli-8535ced6
20:03:41 | 378 | reactor | initialising connection to peer-1
20:03:41 | 378 | outgoing-1 | attempting connection to 172.18.0.2:179
20:03:41 | 378 | outgoing-1 | sending TCP payload ( 71) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0047 0104 FDE9 0014 AC12 0003 2A02 0C40 0A80 1400 0101 8000 0201 8002 0601 0400 0100 0102 0601 0400 0200 0102 0206 0002 0641 0400 00FD E9
20:03:41 | 378 | outgoing-1 | >> OPEN version=4 asn=65001 hold_time=20 router_id=172.18.0.3 capabilities=[Multiprotocol(ipv4 unicast,ipv6 unicast), Extended Message(65535), Graceful Restart Flags 0x8 Time 20 ipv4/unicast=0x80 ipv6/unicast=0x80, ASN4(65001)]
20:03:41 | 378 | ka-outgoing-1 | receive-timer 2 second(s) left
20:03:41 | 378 | outgoing-1 | outgoing-1 172.18.0.3-172.18.0.2 172.18.0.2 blocking io problem mid-way through reading a message [Errno EAGAIN] [Errno 11] Resource temporarily unavailable, trying to complete
20:03:42 | 378 | ka-outgoing-1 | receive-timer 1 second(s) left
20:03:43 | 378 | ka-outgoing-1 | receive-timer 0 second(s) left
20:03:44 | 378 | outgoing-1 | sending TCP payload ( 77) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 004D 0301 0177 6169 7465 6420 666F 7220 6F70 656E 2074 6F6F 206C 6F6E 672C 2077 6520 646F 206E 6F74 206C 696B 6520 7374 7563 6B20 696E 2061 6374 6976 65
20:03:44 | 378 | outgoing-1 | >> NOTIFICATION (1,1,"b'waited for open too long, we do not like stuck in active'")
20:03:44 | 378 | outgoing-1 | 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]
20:03:44 | 378 | outgoing-1 | outgoing-1 172.18.0.3-172.18.0.2, closing connection
20:03:44 | 378 | reactor | initialising connection to peer-1
20:03:44 | 378 | outgoing-2 | attempting connection to 172.18.0.2:179
20:03:44 | 378 | outgoing-2 | connection to 172.18.0.2 closed
20:03:44 | 378 | outgoing-2 | outgoing-2 172.18.0.3-172.18.0.2, closing connection
20:03:45 | 378 | reactor | initialising connection to peer-1
20:03:45 | 378 | outgoing-3 | attempting connection to 172.18.0.2:179
20:03:45 | 378 | outgoing-3 | connection to 172.18.0.2 closed
20:03:45 | 378 | outgoing-3 | outgoing-3 172.18.0.3-172.18.0.2, closing connection
20:03:47 | 378 | reactor | initialising connection to peer-1
20:03:47 | 378 | outgoing-4 | attempting connection to 172.18.0.2:179
20:03:47 | 378 | outgoing-4 | connection to 172.18.0.2 closed
20:03:47 | 378 | outgoing-4 | outgoing-4 172.18.0.3-172.18.0.2, closing connection
20:03:50 | 378 | reactor | initialising connection to peer-1
20:03:50 | 378 | outgoing-5 | attempting connection to 172.18.0.2:179
20:03:50 | 378 | outgoing-5 | connection to 172.18.0.2 closed
20:03:50 | 378 | outgoing-5 | outgoing-5 172.18.0.3-172.18.0.2, closing connection
20:03:54 | 378 | reactor | initialising connection to peer-1
20:03:54 | 378 | outgoing-6 | attempting connection to 172.18.0.2:179
20:03:54 | 378 | outgoing-6 | connection to 172.18.0.2 closed
20:03:54 | 378 | outgoing-6 | outgoing-6 172.18.0.3-172.18.0.2, closing connection
20:03:59 | 378 | reactor | initialising connection to peer-1
20:03:59 | 378 | outgoing-7 | attempting connection to 172.18.0.2:179
20:03:59 | 378 | outgoing-7 | connection to 172.18.0.2 closed
20:03:59 | 378 | outgoing-7 | outgoing-7 172.18.0.3-172.18.0.2, closing connection
^C20:04:04 | 378 | reactor | ^C received
20:04:04 | 378 | reactor | performing shutdown
20:04:04 | 378 | network | stopped listening on 0.0.0.0:179
20:04:04 | 378 | process | terminating process api-internal-cli-8535ced6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.