Configuring an ldp instance, Configuring routing between pe and ce, Configuration prerequisites – H3C Technologies H3C SR8800 User Manual

Page 366: Configuring static routing between pe and ce

Advertising
background image

355

NOTE:

When you configure tunnel selection preference order by using the tunnel select-seq command, a
tunnel type closer to the select-seq keyword has a higher priority. For example, with the tunnel
select-seq lsp cr-lsp load-balance-number 1 command configured, VPN uses a CR-LSP tunnel when

no LSP exists. After an LSP is created, the VPN uses the LSP tunnel instead.

If you specify more than one tunnel type and the number of tunnels of a type is less than the specified
number of tunnels for load balancing, tunnels of different types may be used.

A tunneling policy configured in VPN instance view is applicable to both IPv4 VPNs and IPv6 VPNs.

You can configure a tunneling policy for IPv6 VPNs in both VPN instance view and IPv6 VPN view. A
tunneling policy configured in IPv6 VPN view takes precedence.

Create a tunneling policy before associating it with a VPN instance. Otherwise, the default tunneling
policy is used.

Configuring an LDP instance

LDP instances are for carrier’s carrier networking applications.
This task is to enable LDP for an existing VPN instance, create an LDP instance for the VPN instance, and

configure LDP parameters for the LDP instance.
For LDP instance configuration information, see the chapter “Configuring MPLS L3VPN.”

Configuring routing between PE and CE

You can configure static routing, RIPng, OSPFv3, IPv6 IS-IS, or EBGP between PE and CE.

Configuration prerequisites

Before you configure routing between PE and CE, complete the following tasks:

Assign an IPv6 address to the CE-PE interface of the CE

Assign an IPv6 address to the PE-CE interface of the PE

Configuring static routing between PE and CE

To configure PE-CE route exchange through static routes:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Configure static routes for a

VPN instanceN/A.

ipv6 route-static ipv6-address prefix-length
{ interface-type interface-number

[ next-hop-address ] | next-hop-address |

vpn-instance d-vpn-instance-name
nexthop-address
} [ preference preference-value ]

Required
Use either

command
Perform this
configuration on

PEs. On CEs,

configure normal

static routes.

ipv6 route-static vpn-instance
s-vpn-instance-name&<1-6> ipv6-address

prefix-length { interface-type interface-number

[ next-hop-address ] | nexthop-address [ public ] |
vpn-instance d-vpn-instance-name

nexthop-address } [ preference preference-value ]

Advertising