HP 10500 SERIES Configuration Manual page 264

Step
5. Enter interface view.
6. Enable the IS-IS process on
the interface.
Configuring EBGP between PE and CE
Configure the PE:
1.
Step
1. Enter system view.
2. Enable BGP and enter BGP
view.
3. Enter BGP VPN instance view.
4. Configure the CE as the VPN
EBGP peer.
5. Redistribute the routes of the
local CEs.
6. Configure BGP to filter routes
to be advertised.
7. Configure BGP to filter
received routes.
8. 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.
Command
interface interface-type
interface-number
isis enable [ process-id ]
Command
system-view
bgp as-number
ipv4-family vpn-instance
vpn-instance-name
peer { group-name | ip-address }
as-number as-number
import-route protocol [ process-id ]
[ med med-value | route-policy
route-policy-name ] *
filter-policy { acl-number |
ip-prefix ip-prefix-name } export
[ direct | isis process-id | ospf
process-id | rip process-id | static ]
filter-policy { acl-number |
ip-prefix ip-prefix-name } import
peer { group-name | ip-address }
allow-as-loop [ number ]
256
Remarks
N/A
Disabled by default.
Remarks
N/A
N/A
N/A
N/A
A PE must redistribute the routes of
the local CEs into its VPN routing
table so it can advertise them to the
peer PE.
Optional.
By default, BGP does not filter
routes to be advertised.
Optional.
By default, BGP does not filter
received routes.
Optional.
Required for the hub and spoke
network.
BGP detects routing loops by AS
number. In the hub and spoke
network scheme, with EBGP
running between PE and CE, the
routing information the PE
advertises to a CE carries the
number of the AS where the PE
resides. Therefore, the route
updates that the PE receives from
the CE also include the number of
the AS where the PE resides. This
causes the PE unable to receive the
route updates. In this case, you
must configure this command to
allow routing loops.