...
In addition to connection-specific parameters, template-specific parameters are also directly exposed in this menu, for easier configuration in simple scenarios (when templates are not necessary).
When a local address is not specified, BGP will try to guess the local address depending on the current setup:
- if the peer is iBGP
- if loopback available
- pick the highest loopback address
- if loopback is not available
- pick any highest IP address on the router
- if loopback available
- if the peer is eBGP
- if a remote peers peer's IP is not from a directly connected network:
- and multihop is not set, then throw an error
- and multihop is enabled:
- if loopback available
- pick the highest loopback address
- if loopback is not available
- pick any highest IP address on the router
- if loopback available
- if a remote peers peer's IP is from a directly connected network:
- and multihop is not set:
- pick the local routers IP address from that connected network
- and multihop is set:
- if loopback available
- pick the highest loopback address
- if loopback is not available
- pick any highest IP address on the router
- if loopback available
- and multihop is not set:
- if a remote peers peer's IP is not from a directly connected network:
...
This menu shows read-only cached BGP session information. It will show the current status of the session, session flags, last received notification, and negotiated session parameters.
Even if the BGP session is not active anymore, the cache can still be stored for some time. Routes received from a particular session are removed only if the cache expires, this allows to mitigate extensive routing table recalculations if the BGP session is flapping.
Commands
...
Command | Description | |
---|---|---|
clear | Clear all the session flags. For example, to be able to re-establish a session after the prefix limit is reached "limit-exceeded" flag must be cleared. | |
dump-saved-advertisements | Dump saved advertisements from specified BGP session in the *.pcap file. Filename to store data is set by "save-to " parameter. | |
refresh | Send route refresh to a specified BGP session. Is used to trigger re-sending all the routes from the remote peer. | |
resend | Resend prefixes to a specified BGP session. | |
reset | Reset specified BGP session. | |
stop | Stop specified BGP session. |
...