beautypg.com

Configuring routing between a pe and a ce, Configuring ripng between a pe and a ce, Configuring ospfv3 between a pe and a ce – H3C Technologies H3C S6800 Series Switches User Manual

Page 292: Required.)

background image

279

Configuring routing between a PE and a CE

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

Configuring IPv6 static routing between a PE and a CE

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Configure an IPv6 static
route for a VPN instance.

ipv6 route-static vpn-instance
s-vpn-instance-name ipv6-address prefix-length
{ interface-type interface-number

[ next-hop-address ] | nexthop-address [ public ]

| vpn-instance d-vpn-instance-name
nexthop-address } [ permanent ] [ preference

preference-value ] [ tag tag-value ] [ description

description-text ]

By default, no IPv6 static
route is configured for a

VPN instance.
Perform this configuration

on the PE. On the CE,
configure a common IPv6

static route.
For more information

about IPv6 static routing,
see Layer 3—IP Routing

Configuration Guide.

Configuring RIPng between a PE and a CE

A RIPng process belongs to the public network or a single VPN instance. If you create a RIPng process

without binding it to a VPN instance, the process belongs to the public network.
For more information about RIPng, see Layer 3—IP Routing Configuration Guide.
To configure RIPng between a PE and a CE:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Create a RIPng process for a
VPN instance and enter RIPng

view.

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

Perform this configuration on the
PE. On the CE, create a common

RIPng process.

3.

Return to system view.

quit

N/A

4.

Enter interface view.

interface interface-type
interface-number

N/A

5.

Enable RIPng on the interface. ripng process-id enable

By default, RIPng is disabled on an
interface.

Configuring OSPFv3 between a PE and a CE

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

process without binding it to a VPN instance, the process belongs to the public network.
For more information about OSPFv3, see Layer 3—IP Routing Configuration Guide.
To configure OSPFv3 between a PE and a CE: