Configuring Multi-Role Host; Configuration Prerequisites; Configuring And Applying Policy Routing - H3C SR8800 10G Mpls Configuration Manual

Step
8. Activate a nested VPN peer or
peer group, and enable the
BGP-VPNv4 route exchange
capability.
9. Add a peer to the nested VPN
peer group.
10. Apply a routing policy to
routes received from a nested
VPN peer or peer group.
NOTE:
The address ranges for sub-VPNs of a VPN cannot overlap.
•
Do not give nested VPN peers addresses that public network peers use.
•
Before specifying a nested VPN peer or peer group, be sure to configure the corresponding CE peer or
•
peer group in BGP VPN instance view.
Nested VPN does not support multi-hop EBGP networking. A service provider PE and its peer must use
•
the addresses of the directly connected interfaces to establish neighbor relationship.
• Nested VPN does not allow a sub-VPN of a customer VPN and another backbone VPN to import routes
from each other for mutual communication. If they need to communicate, you must configure route
exchange between the customer VPN and that backbone VPN. For example, an ISP has backbone
VPNs VPN A and VPN B. VPN A has a sub-VPN VPN A-1. If VPN A-1 and VPN B need to communicate,
you must configure route exchange between VPN A and VPN B instead of that between VPN A-1 and
VPN B.

Configuring multi-role host

To allow a CE to access multiple VPNs, you need to configure the multi-role host feature on the PE.
All configurations for the multi-role host feature are on the PE connecting that CE.
NOTE:
For more information about policy routing, see

Configuration prerequisites

Before you configure the multi-role host feature, complete the following tasks:
Create VPN instances for the VPNs
•
• Configure basic MPLS L3VPN

Configuring and applying policy routing

To configure and apply policy routing:
Command
peer { group-name |
peer-address } vpn-instance
vpn-instance-name enable
peer peer-address vpn-instance
vpn-instance-name group
group-name
peer { group-name |
peer-address } vpn-instance
vpn-instance-name route-policy
route-policy-name import
Layer 3—IP Routing Configuration Guide
262
Remarks
By default, only IPv4 routes and no
BGP-VPNv4 routes can be
exchanged between nested VPN
peers/peer groups.
Optional.
By default, a peer is not in any
nested VPN peer group.
Optional.
By default, no routing policy is
applied to routes received from a
nested VPN peer or peer group.
.