![](/images/new-backgrounds/1106489/1064899x1.webp)
OSPF
Feature Overview
Figure 3 Using a Sham-Link Between PE Routers to Connect OSPF Client Sites
| MPLS VPN Backbone |
|
|
|
|
|
|
| Net=10.3.1.7 |
|
| Winchester |
| ||
|
|
|
| ||||
|
|
| 10.3.1.7 | Area 1 | |||
|
| 10.3.1.2 |
| ||||
|
|
| Net=10.3.1.7 |
| |||
|
|
|
|
|
|
| |
| Net=10.3.1.7 |
|
|
|
|
| |
|
|
|
|
| Brighton |
| |
|
|
|
|
| |||
|
|
|
|
|
| ||
| Net=10.3.1.7 |
|
|
|
|
|
|
|
|
|
|
| |||
|
|
| Net=10.3.1.7 |
| |||
10.3.1.6 |
| 10.3.1.5 |
|
|
| ||
|
|
|
|
|
| ||
Area 1 | Vienna |
| Stockholm | Area 1 |
| ||
|
|
|
| ||||
| 10.3.1.15 |
|
| 10.3.1.3 |
|
|
70392
Because the
The section, “ Creating a
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_c/1cprt1/1cospf.htm
Sham-Link Configuration Example
The example in this section is designed to show how a
Figure 4 shows a sample MPLS VPN topology in which a sham-link configuration is necessary. A VPN client has three sites, each with a backdoor link. Two sham-links have been configured, one between PE-1 and PE-2, and another between PE-2 and PE-3. A sham-link between PE-1 and PE-3 is not necessary in this configuration because the Vienna and Winchester sites do not share a backdoor link.
Cisco IOS Release 12.2(8)T
5