3Com MSR 50, MSR 30 Debugging bgp update vpnv4, Examples None, BGP VPNv4 Update messages, 1035

1035

Refer to “debugging bgp update vpnv4” on page 1035 for the description of the update message information.

Examples None

debugging bgp update vpnv4

Syntax	debugging bgp update vpnv4 [ peer { ipv4-addressgroup-name} ] [ receive send ]
	[ verbose ]
	undo debugging bgp update vpnv4 [ peer { ipv4-addressgroup-name} ] [ receive
	send ] [ verbose ]
View	User view
Default Level	1: Monitor level
Parameters	peer { ipv4-address group-name}: Enables/disables BGP Update message
	debugging for the specified peer/peer group.
	receive: Enables/disables the debugging for the received BGP VPNv4 packets.
	send: Enables/disables the debugging for the sent BGP VPNv4 packets.
	verbose: Displays detailed debugging information.
Description	Use the debugging bgp update vpnv4 command to enable debugging for
	BGP VPNv4 Update messages.
	Use the undo debugging bgp update vpnv4 command to disable debugging
	for BGP VPNv4 Update messages.
	By default, this debugging is disabled.
	Enabling debugging may affect system performance; therefore, use this command
	only when necessary and disable debugging once the debugging operation is
	complete.
Examples	# Device A and Device B have established a BGP peer relationship under the VPNv4
	instance. On Device A, enable debugging for received BGP VPNv4 update
	messages; on Device B, enable debugging for sent BGP VPNv4 update messages.
	<Sysname> debugging bgp update vpnv4
	%Sep	4 16:14:32:00 2006 Sysname RM/3/RMLOG:
	BGP.: 2.2.2.2 State is changed from OPENCONFIRM to ESTABLISHED.
	*Sep	4 16:14:32:16 2006 Sysname RM/6/RMDEBUG:
	BGP_L3VPN.: Send UPDATE to peer 2.2.2.2 for following destinations :
	*Sep	4 16:14:32:16 2006 Sysname RM/6/RMDEBUG:
		Origin	: Incomplete
		AS Path	:
		Next Hop	: 1.1.1.1