377
Configuring an OSPFv3 sham link
Network requirements
As shown in
, CE 1 and CE 2 belong to VPN 1. Configure an OSPFv3 sham link between
PE 1 and PE 2 so traffic between the CEs is forwarded through the MPLS backbone instead of the
backdoor link.
Figure 97 Network diagram
Table 35 Interface and IP address assignment
Device
Interface
IP address
Device
Interface
IP address
CE 1
GE1/1/1
100::1/64
CE 2
GE1/1/1
120::1/64
S1/1/1
20::1/64 S1/1/1
30::2/64
PE 1
Loop0
1.1.1.9/32
PE 2
Loop0
2.2.2.9/32
Loop1
3::3/128 Loop1
5::5/128
GE1/1/1
100::2/64 GE1/1/1
120::2/64
S1/1/1
10.1.1.1/24
S1/1/0
10.1.1.2/24
Router A
S1/1/0
30::1/64
S1/1/1
20::2/64
Configuration procedure
1.
Configure OSPFv3 on the customer networks:
# Configure conventional OSPFv3 on CE 1, Router A, and CE 2 to advertise addresses of the
interfaces (see
). (Details not shown.)
# Set the cost value to 2 for both the link between CE 1 and Router A, and the link between CE
2 and Router A. (Details not shown.)
# Execute the
display ipv6 routing-table
command to verify that CE 1 and CE 2 have learned
the route to each other. (Details not shown.)
2.
Configure IPv6 MPLS L3VPN on the backbone:
# Configure basic MPLS and MPLS LDP on PE 1 to establish LDP LSPs.
<PE1> system-view
[PE1] interface loopback 0
