HP FlexNetwork HSR6600 Configuration Manual page 390

[PE2-bgp-default-vpn1] quit
[PE2-bgp-default] quit
# Execute the display ipv6 routing-table vpn-instance command on the PEs. Verify that the
path to the peer CE is along the OSPFv3 route across the customer networks, instead of the
IPv6 BGP route across the backbone. (Details not shown.)
4. Configure a sham link:
# Configure PE 1.
[PE1] interface loopback 1
[PE1-LoopBack1] ip binding vpn-instance vpn1
[PE1-LoopBack1] ipv6 address 3::3 128
[PE1-LoopBack1] quit
[PE1] ospfv3 100
[PE1-ospfv3-100] area 1
[PE1-ospfv3-100-area-0.0.0.1] sham-link 3::3 5::5
[PE1-ospfv3-100-area-0.0.0.1] quit
[PE1-ospfv3-100] quit
# Configure PE 2.
[PE2] interface loopback 1
[PE2-LoopBack1] ip binding vpn-instance vpn1
[PE2-LoopBack1] ipv6 address 5::5 128
[PE2-LoopBack1] quit
[PE2] ospfv3 100
[PE2-ospfv3-100] area 1
[PE2-ospfv3-100-area-0.0.0.1] sham-link 5::5 3::3
[PE2-ospfv3-100-area-0.0.0.1] quit
[PE2-ospfv3-100] quit
Verifying the configuration
# Execute the display ipv6 routing-table vpn-instance command on the PEs to verify the following
results (details not shown):
•
The path to the peer CE is now along the IPv6 BGP route across the backbone.
•
A route to the sham link destination address exists.
# Execute the display ipv6 routing-table command on the CEs. Verify that the next hop of the
OSPFv3 route to the peer CE is the interface connected to the PE (GigabitEthernet 1/1/1). This
means that the VPN traffic to the peer CE is forwarded over the backbone. (Details not shown.)
# Verify that a sham link has been established on PEs, for example, on PE 1.
[PE1] display ospfv3 sham-link
Sham-link (Area: 0.0.0.1)
Neighbor ID
120.1.1.1
# Verify that the peer state is Full on PE 1.
[PE1] display ospfv3 sham-link verbose
OSPFv3 Process 100 with Router ID 100.1.1.1
State Instance ID
P-2-P 0
OSPFv3 Process 100 with Router ID 100.1.1.1
Destination address
5::5
380