3Com MSR 50, MSR 30 manual Information about the received BGP Open message, 1023

1023

IPv4-UNC (1/1)

CAP Type: 2 (RouteRefresh) CAP Len: 0

// Information about the received BGP Open message

*0.2683500 4945 RM/6/RMDEBUG:

BGP.: 11.1.1.2 Send KEEPALIVE

Length 19

// Information about the sent BGP Keepalive message

*0.2683609 4945 RM/6/RMDEBUG:

BGP.: 11.1.1.2 Recv KEEPALIVE

Length: 19

// Information about the received BGP Keepalive message

[Sysname-bgp] import-route static

*0.2710031 4945 RM/6/RMDEBUG:

BGP.: Send UPDATE to 11.1.1.2 for following destinations :

Origin	: Incomplete
AS Path	: 100
Next Hop	: 11.1.1.1
MED	: 0
111.1.1.1/32,

// Information about the sent BGP update of a redistributed static route

*0.2728250 4945 RM/6/RMDEBUG:

BGP.: Recv UPDATE from 11.1.1.2 with following destinations :

Update message		length : 53
MED	:	0
Origin	:	Incomplete
AS Path	:	200
Next Hop	: 11.1.1.2
222.1.1.1/32

// Information about the received BGP Update of a redistributed static route

#Device A and Device B has established a peer relationship. On Device A, enable debugging for the received BGP route-refresh messages. On Device B, enable debugging for the sent BGP route-refresh messages and execute the refresh bgp all import command.

<Sysname> debugging bgp route-refresh send <Sysname> refresh bgp all import

*0.340484 Sysname RM/6/RMDEBUG:

BGP.: 3.3.3.3 Send ROUTEREFRESH MSG :

Length: 23, AFI: 1, SAFI: 1.

//Device B sent a BGP Route-refresh message, with a length of 23, address family of 1, and sub-address family of 1.

<Sysname> debugging bgp route-refresh receive

*0.45337687 Sysname RM/6/RMDEBUG:

BGP.: 2.2.2.2 Recv ROUTEREFRESH MSG:

Length: 23, AFI: 1, SAFI: 1, WTR: 0.