3Com MSR 50, MSR 30 manual Peer allow-as-loop BGP/BGP-VPN instance view, 985

985

Use the undo peer advertise-ext-community command to disable the advertisement.

By default, no extended community attribute is advertised to a peer/peer group.

For related information, refer to “ip extcommunity-list” on page 1205, “if-match extcommunity” on page 1199 and “apply extcommunity” on page 1190.

Examples # In BGP view, advertise the extended community attribute to the peer group test.

<Sysname> system-view [Sysname] bgp 100

[Sysname-bgp] peer test advertise-ext-community

#In BGP-VPN view, advertise the extended community attribute to the peer group test (the VPN has been created).

<Sysname> system-view [Sysname] bgp 100

[Sysname-bgp] ipv4-family vpn-instance vpn1 [Sysname-bgp-vpn1] peer test advertise-community

peer allow-as-loop (BGP/BGP-VPN instance view)

Syntax peer { group-name ip-address } allow-as-loop[ number ]

undo peer { group-name ip-address } allow-as-loop

View BGP view/BGP-VPN instance view

Parameters group-name: Name of a peer group, a string of 1 to 47 characters.

ip-address: IP address of a peer.

number: Specifies the repeating times of the local AS number, in the range 1 to 10. The default number is 1.

Description Use the peer allow-as-loopcommand to allow the local AS number to exist in the AS_PATH attribute of routes from a peer/peer group, and to configure the repeating times of the local AS number.

Use the undo peer allow-as-loopcommand to remove the configuration.

By default, the local AS number is allowed.

Related commands: display bgp routing-table peer.

Examples # In BGP view, configure the repeating times of the local AS number as 2 for routes from peer 1.1.1.1.

<Sysname> system-view [Sysname] bgp 100

[Sysname-bgp] peer 1.1.1.1 allow-as-loop 2