Configuring Routing Between An Mce And A Vpn Site - HP FlexNetwork HSR6600 Configuration Manual

Before you configure routing on an MCE, configure VPN instances, and bind the VPN instances to
the interfaces connected to the VPN sites and the PE.

Configuring routing between an MCE and a VPN site

You can configure static routing, RIP, OSPF, IS-IS, EBGP or IBGP between an MCE and a VPN site.
Configuring static routing between an MCE and a VPN site
An MCE can reach a VPN site through a static route. Static routing on a traditional CE is globally
effective and does not support address overlapping among VPNs. An MCE supports binding a static
route to a VPN instance, so that the static routes of different VPN instances can be isolated from
each other.
To configure a static route to a VPN site:
Step
1. Enter system view.
2. Configure a static
route for a VPN
instance.
3. (Optional.) Configure
the default preference
for static routes.
Configuring RIP between an MCE and a VPN site
A RIP process belongs to the public network or a single VPN instance. If you create a RIP process
without binding it to a VPN instance, the process belongs to the public network. Binding RIP
processes to VPN instances can isolate routes of different VPNs. For more information about RIP,
see Layer 3—IP Routing Configuration Guide.
To configure RIP between an MCE and a VPN site:
Step
1. Enter system view.
2. Create a RIP process for a
VPN instance and enter RIP
view.
3. Enable RIP on the interface
attached to the specified
network.
4. Redistribute remote site
routes advertised by the PE
into RIP.
Configuring OSPF between an MCE and a VPN site
An OSPF process belongs to the public network or a single VPN instance. If you create an OSPF
process without binding it to a VPN instance, the process belongs to the public network.
Command
system-view
ip route-static vpn-instance s-vpn-instance-name
dest-address { mask-length | mask } { interface-type
interface-number [ next-hop-address ] |
next-hop-address [ public ] [ track
track-entry-number ] | vpn-instance
d-vpn-instance-name next-hop-address [ track
track-entry-number ] } [ permanent ] [ preference
preference ] [ tag tag-value ] [ description text ]
ip route-static default-preference
default-preference
Command
system-view
rip [ process-id ] vpn-instance
vpn-instance-name
network network-address
import-route protocol
[ process-id | all-processes |
allow-ibgp ] [ allow-direct | cost
cost-value | route-policy
route-policy-name | tag tag ] *
514
Remarks
N/A
By default, no static
routes are configured.
Perform this
configuration on the
MCE. On the VPN
site, configure a
common static route.
The default
preference is 60.
Remarks
N/A
Perform this configuration on the
MCE. On a VPN site, create a
common RIP process.
By default, RIP is disabled on an
interface.
By default, no route is
redistributed into RIP.