Purpose
When unexpected events or problems occur, or if you want to diagnose BGP establishment issues, you can view more detailed information by configuring options specific to BGP. You can also configure tracing for a specific BGP peer or peer group. For more information, see the JUNOS System Basics Configuration Guide.
Action
To display BGP protocol information in detail, follow these steps:
For example:
For example:
- [edit protocols bgp traceoptions]
- user@pro5-a# run show log bgp
- Sep 17 14:47:16 trace_on: Tracing to "/var/log/bgp" started
- Sep 17 14:47:17 bgp_read_v4_update: receiving packet(s)
from 10.255.245.53 (Internal AS 10458)
- Sep 17 14:47:17 BGP RECV 10.255.245.53+179 -> 10.255.245.50+1141
- Sep 17 14:47:17 BGP RECV message type 2 (Update) length
128
- Sep 17 14:47:17 BGP RECV flags 0x40 code Origin(1): IGP
- Sep 17 14:47:17 BGP RECV flags 0x40 code ASPath(2): 2
- Sep 17 14:47:17 BGP RECV flags 0x80 code MultiExitDisc(4):
0
- Sep 17 14:47:17 BGP RECV flags 0x40 code LocalPref(5):
100
- Sep 17 14:47:17 BGP RECV flags 0xc0 code Extended Communities(16):
2:10458:1
- [...Output truncated...]
Meaning
Table 53 lists tracing flags specific to BGP and presents example output for some of the flags. You can also configure tracing for a specific BGP peer or peer group. For more information, see the JUNOS System Basics Configuration Guide.
Table 53: BGP Protocol Tracing Flags
To trace BGP session establishment problems.
To trace BGP session establishment problems, follow these steps:
For example:
For example:
Sep 17 17:13:14 trace_on: Tracing to "/var/log/bgplog"
started
Sep 17 17:13:14 bgp_read_v4_update: done with
201.0.0.2 (Internal AS 10458) received 19 octets 0 updates 0 routes
Sep 17 17:13:15 bgp_read_v4_update: receiving packet(s)
from 201.0.0.3 (Internal AS 10458)
Sep 17 17:13:15
bgp_read_v4_update: done with 201.0.0.3 (Internal AS 10458) received
19 octets 0 updates 0 routes
Sep 17 17:13:44 bgp_read_v4_update:
receiving packet(s) from 201.0.0.2 (Internal AS 10458)
[...Output truncated...]