HP MSR2000 Configuration Manual page 203

Step
8. (Optional.) Allow the local AS
number to appear in the
AS_PATH attribute of a received
route, and set the maximum
number of repetitions.
Configure the CE:
2.
Step
1. Enter system view.
2. Enter BGP view.
3. Configure the PE as a BGP
peer.
4. Create the BGP IPv4 unicast
family and enter its view.
5. Enable IPv4 unicast route
exchange with the specified
peer or peer group.
6. (Optional.) Configure route
redistribution.
Configuring IBGP between a PE and a CE
Use IBGP between PE and CE only in a basic MPLS L3VPN network. In networks such as Hub&Spoke,
Extranet, inter-AS VPN, carrier's carrier, nested VPN, and HoVPN, you cannot use IBGP between PE and
CE.
1. Configure the PE:
Step
1. Enter system view.
Command
peer { group-name | ip-address }
allow-as-loop [ number ]
Command
system-view
bgp as-number
peer { group-name | ip-address }
as-number as-number
address-family ipv4 [ unicast ]
peer { group-name | ip-address }
enable
import-route protocol
[ { process-id | all-processes }
[ allow-direct | med med-value |
route-policy route-policy-name ]
* ]
Command
system-view
194
Remarks
By default, BGP discards
incoming route updates that
contain the local AS
number.
BGP detects routing loops
by examining AS numbers.
In a hub-spoke network
where EBGP is running
between a PE and a CE, the
routing information the PE
advertises to a CE carries
the AS number of the PE.
Therefore, the route updates
that the PE receives from the
CE also include the AS
number of the PE. This
causes the PE to be unable
to receive the route updates.
In this case, you must
configure this command to
allow routing loops.
Remarks
N/A
N/A
By default, no BGP peer is
created.
By default, the BGP IPv4 unicast
family is not created.
By default, BGP does not
exchange IPv4 unicast routes
with any peer.
A CE must redistribute its routes
to the PE so the PE can advertise
them to the peer CE.
Remarks
N/A