Activating And Reading Logs at the Protocol Level: Traceoptions

Thu, 12 Mar 2026 21:31:13 +0200

Provisional reality: Each BGP speaker is dropping the ingress BGP messages from the other BGP speaker.

Configuration:


user1@R2> show configuration protocols bgp group internPeers
type internal;
traceoptions {
    file bgpDebugWassim;
}
peer-as 22;
neighbor 4.4.4.4;

user1@R2>

Observed reality:

user1@R2> show log bgpDebugWassim
Jul  2 07:54:16 trace_on: Tracing to "/var/log//bgpDebugWassim" started
Jul  2 07:54:28.866558 advertising graceful restart receiving-speaker-only capability to neighbor 4.4.4.4 (Internal AS 22)
Jul  2 07:54:28.866776 advertising LLGR receiving-speaker-only capability to neighbor 4.4.4.4 (Internal AS 22)
Jul  2 07:54:28.871406 bgp_handle_notify:5119: NOTIFICATION received from 4.4.4.4 (Internal AS 22): code 6 (Cease) subcode 5 (Connection Rejected)
Jul  2 07:56:56.882622 advertising graceful restart receiving-speaker-only capability to neighbor 4.4.4.4 (Internal AS 22)
Jul  2 07:56:56.882686 advertising LLGR receiving-speaker-only capability to neighbor 4.4.4.4 (Internal AS 22)
Jul  2 07:56:56.889349 bgp_handle_notify:5119: NOTIFICATION received from 4.4.4.4 (Internal AS 22): code 6 (Cease) subcode 5 (Connection Rejected)

user1@R2>

Adjusted provisional reality: the BGP speakers do not recognize the source address of the received BGP messages. Action: set source addresses of BGP messages on both routers.

Logging on

Activating And Reading Logs at the Protocol Level: Traceoptions