HP 12500 Series Configuration Manual page 230

NOTE:
Exchange of BGP routes for a VPN instance is the same as that of ordinary BGP routes.
•
The BGP configuration task in BGP-VPN instance view is the same as that in BGP view. For more
•
information, see
• For information about BGP peer and peer group configuration, see
Guide
. This chapter does not differentiate between peer and peer group.
Configuring iBGP between PE and CE
NOTE:
iBGP can be used between PE and CE devices in only common MPLS L3VPN networks. In networks such as
Extranet, inter-AS VPN, carrier's carrier, nested VPN, and HoVPN, you cannot use iBGP between PE and
CE devices.
Configure the PE
1.
To configure iBGP between PE and CE:
To do...
Enter system view
Enter BGP view
Enter BGP VPN instance view
Configure the CE as the VPN iBGP
peer
Configure the system to be the RR
and specify the CE as the client of
the RR
Enable route reflection between
clients
Configure the cluster ID for the RR
Configure BGP to filter routes to be
advertised
Layer 3—IP Routing Configuration Guide
Use the command...
system-view
bgp as-number
ipv4-family vpn-instance
vpn-instance-name
peer { group-name | ip-address }
as-number as-number
peer { group-name | ip-address }
reflect-client
reflect between-clients
reflector cluster-id { cluster-id |
ip-address }
filter-policy { acl-number |
ip-prefix ip-prefix-name } export
[ direct | isis process-id | ospf
process-id | rip process-id | static ]
.
222
Layer 3—IP Routing Configuration
Remarks
—
—
Required
Required
Optional
By default, no RR or RR client is
configured.
Optional
Enabled by default.
If the clients are fully meshed, you
do not need to enable route
reflection.
Optional
By default, each RR in a cluster uses
its own router ID as the cluster ID.
If more than one RR exists in a
cluster, use this command to
configure the same cluster ID for all
RRs in the cluster to avoid routing
loops.
Optional
By default, BGP does not filter
routes to be advertised.