Configuring is-is between an mce and a vpn site, Configuring ebgp between an mce and a vpn site – H3C Technologies H3C S12500-X Series Switches User Manual

Page 330

Advertising
background image

319

Step Command

Remarks

8.

Create an OSPF area and
enter OSPF area view.

area area-id

By default, no OSPF area is
created.

9.

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 VPN site

An IS-IS process belongs to the public network or a single VPN instance. If you create an IS-IS process

without binding it to a VPN instance, the process belongs to the public network.
Binding IS-IS processes to VPN instances can isolate routes of different VPNs. For more information about
IS-IS, see Layer 3—IP Routing Configuration Guide.
To configure IS-IS between an MCE and a VPN site:

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

Perform this configuration on the
MCE. On a VPN site, configure a

common IS-IS process.

3.

Configure a network entity
title.

network-entity net

By default, no NET is configured.

4.

Redistribute remote site routes
advertised by the PE into IS-IS.

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.

Return to system view.

quit

N/A

6.

Enter interface view.

interface interface-type
interface-number

N/A

7.

Enable the IS-IS process on

the interface.

isis enable [ process-id ]

IS-IS is disabled by default.

Configuring EBGP between an MCE and a VPN site

To run EBGP between an MCE and a VPN site, you must configure a BGP peer for each VPN instance
on the MCE, and redistribute the IGP routes of each VPN instance on the VPN site.
You can configure filtering policies to filter received routes and advertised routes.

1.

Configure the MCE:
Routes redistributed from OSPF to BGP have their OSPF attributes removed. To enable BGP to
distinguish routes redistributed from different OSPF domains, you must enable the redistributed

routes to carry the OSPF domain ID by configuring the domain-id command in OSPF view. The

domain ID is added to BGP VPN routes as an extended community attribute.
To configure the MCE:

Advertising