H3C Technologies H3C S10500 Series Switches - Manual (Page 271)

260
To do… Use the command… Remarks
Add a peer to the nested VPN peer
group
peer peer-address vpn-instance
vpn-instance-name group
group-name Optional
By default, a peer is not in any
nested VPN peer group.
Apply a routing policy to routes
received from a nested VPN peer
or peer group
peer { group-name |
peer-address } vpn-instance
vpn-instance-name route-policy
route-policy-name import
Optional
By default, no routing policy is
applied 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, configure the corresponding CE peer or peer group
in BGP VPN instance view.
• Nested VPN does not support multi-hop eBGP. A service provider PE and its peer must use the addresses
of the directly connected interfaces to establish neighbor relationship.
• On some devices, if a CE of a sub-VPN is directly connected to a service provider’s PE, policy routing
must be configured on the PE to allow mutual access between the sub-VPN and the VPN on the
backbone.
Configuring HoVPN
For hierarchical VPNs, you can adopt HoVPN to reduce the performance requirements for PEs.
Configuration prerequisites
Complete the basic MPLS L3VPN configuration on UPE and SPE.
Configuring HoVPN
Follow these steps to configure HoVPN:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Enter BGP-VPNv4 subaddress
family view
ipv4-family vpnv4 Required
Enable the exchange of
BGP-VPNv4 routing information
with a peer
peer { group-name | ip-address }
enable
Required
Specify a BGP peer or peer group
as the UPE peer { group-name | ip-address }
upe
Required
Advertise default routes of a VPN
instance to a UPE
peer { group-name | ip-address }
default-route-advertise
vpn-instance vpn-instance-name
Required
Configure either command.