H3C Technologies H3C S12500-X Series Switches - Manual (Page 331)

320
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A
3. Enter BGP-VPN instance
view.
ip vpn-instance vpn-instance-name N/A
4. Configure an EBGP peer.
peer { group-name | ip-address }
as-number as-number By default, no BGP peer is
configured.
5. Enter BGP-VPN IPv4
unicast address family
view.
address-family ipv4 [ unicast ] N/A
6. Enable BGP to exchange
IPv4 unicast routes with the
peer.
peer { group-name | ip-address } enable
By default, BGP does not
exchange IPv4 unicast
routes with any peer.
7. Allow the local AS number
to appear in the AS_PATH
attribute of routes received
from the peer, and set the
maximum number of
repetitions.
peer { group-name | ip-address }
allow-as-loop [ number ]
By default, BGP discards
incoming route updates
that contain the local AS
number.
BGP detects routing loops
by examining AS
numbers. The routing
information the MCE
advertises to a site carries
the local AS number.
Therefore, the route
updates that the MCE
receives from the site also
include the local AS
number. This causes the
MCE to be unable to
receive the route updates.
In this case, you must
configure this command to
allow routing loops.
8. Redistribute remote site
routes advertised by the PE
into BGP.
import-route protocol [ { process-id |
all-processes } [ med med-value |
route-policy route-policy-name ] * ]
By default, no routes are
redistributed into BGP.
9. (Optional.) Configure
filtering of advertised
routes.
filter-policy { acl-number | prefix-list
prefix-list-name } export [ protocol
process-id ]
By default, BGP does not
filter advertised routes.
10. (Optional.) Configure
filtering of received routes.
filter-policy { acl-number | prefix-list
prefix-list-name } import By default, BGP does not
filter received routes.
2. Configure a VPN site:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A