Configuring Hovpn - 3Com 3C13636 Configuration Manual

3Com Router 3000 Ethernet Family
Configuration Guide
[PE1] interface serial0/0/0
[PE1-Serial0/0/0] ip binding vpn-instance vpn1
[PE1-Serial0/0/0] ip address 1.1.1.1 255.255.255.0
[PE1-Serial0/0/0] quit
# Configure static route, so that PC1 can access the packets returned from VPN2 and
find correct route to PC1 in the VPN-instance for VPN1.
[PE1] ip route-static vpn-instance vpn2 100.1.0.0 16 vpn-instance vpn1 1.1.1.2
# Define policy routing, allowing the router to search private routes within VPN1 and
VPN2 for packets sent by PC1.
[PE1] acl number 3101
[PE1-acl-adv-3101] rule 0 permit ip vpn-instance vpn1 source 100.1.1.2 0
[PE1-acl-adv-3101] quit
[PE1] route-policy aaa permit node 10
[PE1-route-policy] if-match acl 3101
[PE1-route-policy] apply access-vpn vpn-instance vpn2
[PE1-route-policy] quit
# Enable routing policy at the interface Serial0/0/0.
[PE1] interface serial0/0/0
[PE1-Serial0/0/0] ip policy route-policy aaa

3.4.7 Configuring HoVPN

I. Network requirements
For those VPNs that have distinct hierarchy, an MPLS VPN covering a province and its
cities. For example, incorporating the backbone network at the province level and the
networks at the city level into a single MPLS VPN imposes a high requirement in
performance on the equipment on the entire network, in the event that the network
topology size is large. However, the requirement in equipment performance can
become lower if this MPLS VPN is separated into two VPNs, the network at the
province level and the network at the city level, for example.
SPE acts as a PE on the network at the province level, and is connected with a
downstream MPLS VPN at the city level. UPE acts as a PE on the network at the city
level and provide access service for the VPN clients which are normally low-end
routers.
Chapter 3 BGP/MPLS VPN Configuration
3Com Corporation
3-60