Configuring routing between an MCE and a PE

MCE-PE routing configuration includes these tasks:

Perform the following configurations on the MCE. Configure the PE in the same way that you configure a PE in a basic MPLS L3VPN. For more information about configuring the PE, see "Configuring MPLS L3VPN."

Configuring static routing between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Configure a static route for a VPN instance.

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 ]

By default, no static routes are configured.

3. (Optional.) Set the default preference for static routes.

ip route-static default-preference default-preference

The default preference is 60.

Configuring RIP between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Create a RIP process for a VPN instance and enter RIP view.

rip [ process-id ] vpn-instance vpn-instance-name

N/A

3. Enable RIP on the interface attached to the specified network.

network network-address

By default, RIP is disabled on an interface.

4. Redistribute the VPN routes.

import-route protocol [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | route-policy route-policy-name | tag tag ] *

By default, no routes are redistributed into RIP.

Configuring OSPF between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Create an OSPF process for a VPN instance and enter OSPF view.

ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *

N/A

3. Disable routing loop detection.

vpn-instance-capability simple

By default, routing loop detection is enabled.

You must disable routing loop detection for a VPN OSPF process on the MCE. Otherwise, the MCE does not receive OSPF routes from the PE.

4. Redistribute the VPN routes.

import-route protocol [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] *

By default, no routes are redistributed into OSPF.

5. Create an OSPF area and enter OSPF area view.

area area-id

By default, no OSPF areas exist.

6. Enable OSPF on the interface attached to the specified network in the area.

network ip-address wildcard-mask

By default, an interface neither belongs to any area nor runs OSPF.

Configuring IS-IS between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Create an IS-IS process for a VPN instance and enter IS-IS view.

isis [ process-id ] vpn-instance vpn-instance-name

N/A

3. Configure a network entity title.

network-entity net

By default, no NET is configured.

4. Create the IS-IS IPv4 unicast address family and enter its view.

address-family ipv4 [ unicast ]

By default, the IS-IS IPv4 unicast address family is not created.

5. Redistribute VPN routes.

import-route protocol [ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *

By default, IS-IS does not redistribute routes from any other routing protocol.

If you do not specify the route level in the command, the command redistributes routes to the level-2 routing table by default.

6. Return to system view.

quit

N/A

7. Enter interface view.

interface interface-type interface-number

N/A

8. Enable the IS-IS process on the interface.

isis enable [ process-id ]

By default, no IS-IS process is enabled on the interface.

Configuring EBGP between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter BGP instance view.

bgp as-number [ instance instance-name ] [ multi-session-thread ]

By default, BGP is not enabled.

3. Enter BGP-VPN instance view.

ip vpn-instance vpn-instance-name

N/A

4. Configure the PE as an EBGP peer.

peer { group-name | ipv4-address [ mask-length ] } as-number as-number

By default, no BGP peers or peer groups exist.

5. Enter BGP-VPN IPv4 unicast address family view.

address-family ipv4 [ unicast ]

N/A

6. Enable BGP to exchange IPv4 unicast routes with the peer.

peer { group-name | ipv4-address [ mask-length ] } enable

By default, BGP does not exchange IPv4 unicast routes with any peer.

7. Redistribute the VPN routes of the VPN site.

import-route protocol [ process-id | all-processes ] [ allow-direct | med med-value | route-policy route-policy-name ] *

By default, no routes are redistributed into BGP.

Configuring IBGP between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter BGP instance view.

bgp as-number [ instance instance-name ] [ multi-session-thread ]

By default, BGP is not enabled.

3. Enter BGP-VPN instance view.

ip vpn-instance vpn-instance-name

N/A

4. Configure the PE as an IBGP peer.

peer { group-name | ipv4-address [ mask-length ] } as-number as-number

By default, no BGP peers or peer groups exist.

5. Enter BGP-VPN IPv4 unicast address family view.

address-family ipv4 [ unicast ]

N/A

6. Enable BGP to exchange IPv4 unicast routes with the peer.

peer { group-name | ipv4-address [ mask-length ] } enable

By default, BGP does not exchange IPv4 unicast routes with any peer.

7. Redistribute the VPN routes of the VPN site.

import-route protocol [ process-id | all-processes ] [ allow-direct | med med-value | route-policy route-policy-name ] *

By default, no routes are redistributed into BGP.