...
To respond to errors or special conditions, NOTIFICATION messages can be generated and sent to the remote peer, notification message type also indicates whether the connection should be immediately closed.
...
Connections
There can be two types of BGP connections:
...
Code Block | ||
---|---|---|
| ||
#Router2 /routing/bgp/connection add name=toR1 remote.address=192.168.1.1 as=65532 local.role=ebgp |
BGP connection menu defines BGP outgoing connections as well as acts as a template matcher for incoming BGP connections. We will discuss templating and dynamic peering later in this article.
To see the actual active sessions with selected template parameters and negotiated capabilities refer to the BGP sessions menu:
Code Block | ||
---|---|---|
| ||
[admin@MikroTik] /routing/bgp/session> print
Flags: E - established
0 E name="toR2"
remote.address=192.168.1.2 .as=65532 .id=192.168.1.1 .refused-cap-opt=no
.capabilities=mp,rr,as4 .afi=ip,ipv6 .messages=43346 .bytes=3635916 .eor=""
local.address=192.168.1.1 .as=65531 .id=192.168.44.2 .capabilities=mp,rr,gr,as4 .messages=2
.bytes=71 .eor=""
output.procid=97 .keep-sent-attributes=no
.last-notification=ffffffffffffffffffffffffffffffff0015030601
input.procid=97 .limit-process-routes=500000 ebgp limit-exceeded
hold-time=3m keepalive-time=1m uptime=4s70ms |
local.role
parameter is used to indicate that this connection will be the eBGP. Also, notice that the connection does not require a remote AS number to be specified, RouterOS can determine a remote AS number dynamically from the first received OPEN message.
...