Configuring routing between an MCE and a PE

MCE-PE routing configuration includes the following tasks:

Perform the following configurations on the MCE. Configure the PE in the same way that a PE in a basic MPLS L3VPN is configured. 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-value ] [ tag tag-value ] [ description description-text ]

By default, no static route is configured.

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

ip route-static default-preference default-preference-value

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 ] [ cost cost | route-policy route-policy-name | tag tag ] *

By default, no routes are redistributed into RIP.

5. (Optional.) Configure the default cost for redistributed routes.

default cost value

The default cost is 0.

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 cannot receive OSPF routes from the PE.

4. (Optional.) Configure the OSPF domain ID.

domain-id domain-id [ secondary ]

The default domain ID is 0.

5. (Optional.) Configure the type codes of OSPF extended community attributes.

ext-community-type { domain-id type-code1 | router-id type-code2 | route-type type-code3 }

The defaults are as follows:

  • 0x0005 for Domain ID.

  • 0x0107 for Router ID.

  • 0x0306 for Route Type.

6. (Optional.) Configure the external route tag for imported VPN routes.

route-tag tag-value

By default, no route tag is configured.

In some networks, a VPN might be connected to multiple MCEs. When one MCE advertises the routes learned from BGP to the VPN, the other MCEs might learn the routes, resulting in routing loops. To avoid such routing loops, you can configure route tags for VPN instances on an MCE. HP recommends that you configure the same route tag for the same VPN on the MCEs.

7. Redistribute the VPN routes.

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

By default, no routes are redistributed into OSPF.

8. (Optional.) Configure OSPF to redistribute the default route.

default-route-advertise summary cost cost

By default, OSPF does not redistribute the default route.

This command redistributes the default route in a Type-3 LSA. The MCE advertises the default route to the PE.

9. (Optional.) Configure filtering of advertised routes.

filter-policy { acl-number | prefix-list prefix-list-name } export [ protocol [ process-id ] ]

By default, redistributed routes are not filtered.

10. (Optional.) Configure the default parameters for redistributed routes (cost, route number, tag, and type).

default { cost cost | tag tag | type type } *

The default cost is 1, the default tag is 1, and default type of redistributed routes is Type-2.

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

area area-id

By default, no OSPF area is created.

12. 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. Redistribute VPN routes.

import-route protocol [ process-id | all-processes | allow-ibgp ] [ cost cost | 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.

5. (Optional.) Configure filtering of advertised routes.

filter-policy { acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ protocol [ process-id ] ]

By default, IS-IS does not filter advertised routes.

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.

Configuring EBGP between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter BGP view.

bgp as-number

N/A

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 | ip-address } as-number as-number

N/A

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 | ip-address } 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 ] [ med med-value | route-policy route-policy-name ] *

By default, no routes are redistributed into BGP.

8. (Optional.) Configure filtering of advertised routes.

filter-policy { acl-number | prefix-list prefix-list-name } export [ protocol process-id ]

By default, BGP does not filter advertised routes.

9. (Optional.) Configure filtering of received routes.

filter-policy { acl-number | prefix-list prefix-list-name } import

By default, BGP does not filter received routes.

Configuring IBGP between an MCE and a PE

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter BGP view.

bgp as-number

N/A

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 | ip-address } as-number as-number

N/A

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 | ip-address } 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 ] [ med med-value | route-policy route-policy-name ] *

By default, no routes are redistributed into BGP.

8. (Optional.) Configure filtering of advertised routes.

filter-policy { acl-number | prefix-list prefix-list-name } export [ protocol process-id ]

By default, BGP does not filter advertised routes.

9. (Optional.) Configure filtering of received routes.

filter-policy { acl-number | prefix-list prefix-list-name } import

By default, BGP does not filter received routes.