Configuring Route Exchange Between PE and CE Devices

Enter the system view.

system-view

-

Configure a static route for a VPN instance.

ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } interface-type interface-number [ nexthop-address ] [ preference preference | tag tag ] ^*

-

Enter the BGP view.

bgp { as-number-plain | as-number-dot }

-

Enter the BGP-VPN instance IPv4 address family view.

ipv4-family vpn-instance vpn-instance-name

-

Import the configured static route to the routing table of the BGP-VPN instance IPv4 address family.

import-route static [ med med | route-policy route-policy-name ] ^*

After this command is run in the BGP-VPN instance IPv4 address family view, the PE will import the VPN routes learned from the attached CE into the BGP routing table and advertise VPNv4 routes to the remote PE.

Enter the system view.

system-view

-

Create a RIP process running between the PE and CE devices and enter the RIP view.

rip process-id vpn-instance vpn-instance-name

A RIP process can be bound to only one VPN instance. If a RIP process is not bound to any VPN instance before it is started, this process becomes a public network process and can no longer be bound to a VPN instance.

Enable RIP on the network segment of the interface to which the VPN instance is bound.

network network-address

-

Import BGP routes to the RIP routing table.

import-route bgp [ cost { cost | transparent } | route-policy route-policy-name ] ^*

After this command is executed in the RIP view, the PE device can import the VPNv4 routes learned from the remote PE device into the RIP routing table and advertise them to the attached CE device.

Return to system view.

quit

-

Enter the BGP view.

bgp { as-number-plain | as-number-dot }

-

Enter the BGP-VPN instance IPv4 address family view.

ipv4-family vpn-instance vpn-instance-name

-

Import RIP routes into the routing table of the BGP-VPN instance IPv4 address family.

import-route rip process-id [ med med | route-policy route-policy-name ] ^*

After this command is run in the BGP-VPN instance IPv4 address family view, the PE will import the VPN routes learned from the attached CE into the BGP routing table and advertise VPNv4 routes to the remote PE.

Enter the system view.

system-view

-

Create an OSPF process running between the PE and CE device and enter the OSPF view.

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

An OSPF process can be bound to only one VPN instance. If an OSPF process is not bound to any VPN instance before it is started, this process becomes a public network process and can no longer be bound to a VPN instance.

A router ID needs to be specified when an OSPF process is started after it is bound to a VPN instance. The router ID must be different from the public network router ID configured in the system view. If the router ID is not specified, OSPF selects the IP address of one of the interfaces bound to the VPN instance as the router ID based on a certain rule.

(Optional) Configure a domain ID for the OSPF process.

domain-id domain-id [ secondary ]

The domain ID of an OSPF process is contained in the routes generated by the process. When OSPF routes are imported into BGP, the domain ID is added to the BGP VPN routes and forwarded as the BGP extended community attribute.

There are no restrictions on the domain IDs of the OSPF processes of different VPNs on a PE device. The OSPF processes of the same VPN must be configured with the same domain ID to ensure proper route advertisement.

The default domain ID is 0.

(Optional) Configure a VPN route tag.

route-tag tag

The VPN route tag prevents loops of Type-5 LSAs in CE dual-homing networking.

By default, the VPN route tag is calculated using the BGP AS number. If BGP is not configured, the VPN route tag is 0.

Import BGP routes to the OSPF routing table.

import-route bgp [ cost cost | route-policy route-policy-name | tag tag | type type ] ^*

After this command is executed in the OSPF view, the PE can import the VPNv4 routes learned from the remote PE into the OSPF routing table and advertise them to the attached CE.

Enter the OSPF area view.

area area-id

-

Enable OSPF on the network segment of the interface to which the VPN instance is bound.

network ip-address wildcard-mask

-

Return to the OSPF view.

quit

-

Return to system view.

quit

-

Enter the BGP view.

bgp { as-number-plain | as-number-dot }

-

Enter the BGP-VPN instance IPv4 address family view.

ipv4-family vpn-instance vpn-instance-name

-

Import OSPF routes into the routing table of the BGP-VPN instance IPv4 address family.

import-route ospf process-id [ med med | route-policy route-policy-name ] ^*

After this command is run in the BGP-VPN instance IPv4 address family view, the PE will import the VPN routes learned from the attached CE into the BGP routing table and advertise VPNv4 routes to the remote PE.

Enter the system view.

system-view

-

Create an IS-IS process running between the PE and CE devices and enter the IS-IS view.

isis process-id vpn-instance vpn-instance-name

An IS-IS process can be bound to only one VPN instance. If an IS-IS process is not bound to any VPN instance before it is started, this process becomes a public network process and can no longer be bound to a VPN instance.

Set a network entity title (NET) for the IS-IS process.

network-entity net

A NET specifies the current IS-IS area address and the system ID of the switch. An IS-IS process on one switch can be configured with a maximum of three NETs.

(Optional) Set the level of the PE device.

is-level { level-1 | level-1-2 | level-2 }

By default, the IS-IS level of the switch is Level-1-2.

Import BGP routes to the IS-IS routing table.

If the IS-IS level is not specified in the command, BGP routes will be imported into the Level-2 IS-IS routing table.

After this command is executed in the ISIS view, the PE can import the VPNv4 routes learned from the remote PE into the IS-IS routing table and advertise them to the attached CE.

Return to system view.

quit

-

Enter the view of the interface to which the VPN instance is bound.

interface interface-type interface-number

-

Enable IS-IS on the interface.

isis enable [ process-id ]

-

Return to system view.

quit

-

Enter the BGP view.

bgp { as-number-plain | as-number-dot }

-

Enter the BGP-VPN instance IPv4 address family view.

ipv4-family vpn-instance vpn-instance-name

-

Import IS-IS routes into the routing table of the BGP-VPN instance IPv4 address family.

import-route isis process-id [ med med | route-policy route-policy-name ] ^*

After this command is run in the BGP-VPN instance IPv4 address family view, the PE will import the VPN routes learned from the attached CE into the BGP routing table and advertise VPNv4 routes to the remote PE.