The debugging bgp all command enables all BGP debugging functions.
The undo debugging bgp all command disables all BGP debugging functions.
By default, all BGP debugging functions is disabled.
debugging bgp all
debugging bgp all vpn-instance vrf-name [ peer { peerIpv4Addr | peerIpv6Addr } ]
debugging bgp all peer { peerIpv4Addr | peerIpv6Addr }
debugging bgp instance bgpName all
debugging bgp instance bgpName all peer peerIpv4Addr
undo debugging bgp all
undo debugging bgp all vpn-instance vrf-name [ peer { peerIpv4Addr | peerIpv6Addr } ]
undo debugging bgp all peer { peerIpv4Addr | peerIpv6Addr }
undo debugging bgp instance bgpName all
undo debugging bgp instance bgpName all peer peerIpv4Addr
| Parameter | Description | Value |
|---|---|---|
| instance bgpName |
Specifies the name of a BGP multi-instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
| vpn-instance vrf-name |
Specify a VPN-Instance (VRF) name. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. In addition, the VPN instance name must not be _public_. When double quotation marks are used around the string, spaces are allowed in the string. |
| peer peerIpv4Addr |
Specifies the IP address of an IPv4 peer. |
The value is in dotted decimal notation. |
| peerIpv6Addr |
Specifies the IPv6 address of an IPv6 peer. |
The value is in the X:X:X:X:X:X:X:X format. |
Usage Scenario
The debugging bgp all command enables all BGP debugging functions. The debugging functions help you view the information about BGP packet sending and receiving, interaction with the socket process, change of neighbor state machines, GR, and next-hop iteration.
When much information is output, you can filter the output information by VPN instance, peer.Follow-up Procedure
Run the undo debugging bgp all command to disable all BGP debugging functions.
<HUAWEI> debugging bgp all
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738910;
BGP(VPN 0): 10.1.1.2 changes state from ESTABLISHED to ESTABLISHED on event KA_TIMER.
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738910;
BGP.NM(VPN 0): Sent KEEPALIVE to 10.1.1.2, Length: 19
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738910;
BGP(VPN 0): 19 bytes are writen to socket(10) for 10.1.1.2.
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738910;
BGP(VPN 0): Sent message to 10.1.1.2
(Displaying bytes from 1 to 19)
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00 13 04
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP(VPN 0): 19 bytes are read on socket(525) from 3.3.3.3.
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP(VPN 0): Received message from 3.3.3.3
(Displaying bytes from 1 to 19)
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00 13 04
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP.NM(VPN 0): Received KEEPALIVE from 3.3.3.3, Length: 19
2011-02-23 01:45:11 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP(VPN 0): 3.3.3.3 changes state from ESTABLISHED to ESTABLISHED on event RECV_KA.
2011-02-23 01:45:18 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP(VPN 0): 1.1.1.1 changes state from ACTIVE to CONNECT on event CR_TIMER.
2011-02-23 01:45:18 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP(VPN 0): 1.1.1.1 create connect socket.
2011-02-23 01:45:18 RTA %%01bgpcomm/3/DEBUG_INFO(d):CID=2148738916;
BGP(VPN 0): 1.1.1.1 changes state from CONNECT to ACTIVE on event TCP_FAIL.