HP MSR2000/3000/4000 Router Series MPLS Configuration Guide

132
Ste
p
Command Remarks
3. Enter BGP VPN view.
ip vpn-instance vpn-instance-name
Configuration commands in
BGP VPN view are the same
as those in BGP view. For
details, see Layer 3—IP
Routing Configuration Guide.
4. Configure the CE as the VPN
IBGP peer.
peer { group-name | ip-address }
as-number as-number
By default, no BGP peer is
created.
5. Create and enter BGP VPN IPv4
unicast family view.
address-family ipv4 [ unicast ] N/A
6. Enable IPv4 unicast route
exchange with the specified
peer.
peer { group-name | ip-address }
enable
By default, BGP does not
exchange IPv4 unicast routes
with any peer.
7. Configure the CE as a client of
the RR.
peer { group-name | ip-address }
reflect-client
By default, no RR or RR client
is configured, and the PE
does not advertise routes
learned from the IBGP peer
CE to other IBGP peers,
including VPNv4 IBGP peers.
The PE advertises routes
learned from the CE to other
IBGP peers only when you
configure the IBGP peer CE
as a client of the RR.
Configuring an RR does not
change the next hop of a
route. To change the next hop
of a route, configure an
inbound policy on the
receiving side.
8. (Optional.) Enable route
reflection between clients.
reflect between-clients
Route reflection between
clients is enabled by default.
9. (Optional.) Configure the cluster
ID for the RR.
reflector cluster-id { cluster-id |
ip-address }
By default, the RR uses its own
router ID as the cluster ID.
If multiple RRs exist in a
cluster, use this command to
configure the same cluster ID
for all RRs in the cluster to
avoid routing loops.
2. Configure the CE:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Configure the PE as an IBGP
peer.
peer { group-name | ip-address }
as-number as-number
By default, no BGP peer is
created.
4. Create and enter BGP IPv4
unicast family view.
address-family ipv4 [ unicast ] N/A