Example For Configuring Hovpn - 3Com MSR 50 Series Configuration Manual

1540 C 79: MPLS L3VPN C
HAPTER
Example for Configuring
HoVPN
ONFIGURATION
[PE1-Serial2/1] ip address 1.1.1.1 255.255.255.0
[PE1-Serial2/1] quit
# Configure a static route and redistribute it into BGP, enabling responses from
vpn2 to Host A can be sent along the correct route in vpn1 of PE 1.
[PE1] ip route-static vpn-instance vpn2 100.1.0.0 16 vpn-instance vpn1 1.1.1.2
[PE1] bgp 100
[PE1-bgp] ipv4-family vpn-instance vpn1
[PE1-bgp-vpn1] import-direct static
[PE1-bgp-vpn1] quit
[PE1-bgp] quit
# Configure a routing policy, allowing packets from Host A that have no routes in
the native VPN instance to be forwarded along private network routes in VPN
instance vpn2.
[PE1] acl number 3001
[PE1-acl-adv-3001] rule 0 permit ip vpn-instance vpn1 source 100.1.1.2 0
[PE1-acl-adv-3001] quit
[PE1] policy-based-route policy1 permit node 10
[PE1-policy-based-route] if-match acl 3001
[PE1-policy-based-route] apply access-vpn vpn-instance vpn1 vpn2
[PE1-policy-based-route] quit
# Apply the defined routing policy to interface Serial 2/1.
[PE1] interface serial 2/1
[PE1-Serial2/1] ip policy-based-route policy1
The other configurations are similar to the basic ones for MPLS L3VPN.
Network requirements
There are two levels of networks, the backbone and the MPLS VPN networks, as
shown in Figure 429.
SPEs act as PEs to allow MPLS VPNs to access the backbone.
■
UPEs act as PEs of the MPLS VPNs to allow end users to access the VPNs.
■
Performance requirements for the UPEs are lower than those for the SPEs.
■