| < Day Day Up > |
|
The approach taken to implement a VPN will vary between the vendors. Where Dr. Yakov Rekhter of Juniper advocates the use of BGP to carry routing and switching tables across MPLS networks, others advocate the use of other protocols.
Years ago, when CR-LDP and RSVP were competing for a signaling protocol, the existing network protocol (RSVP) secured more support because it had a proven track record. It will be interesting to see if the marketplace again accepts an incumbent, proven protocol over new VPN protocols.
Using RFC 2547 as the basis of carrying switching and routing tables across an MPLS network, the core network is greatly simplified. In addition, a proven single protocol is used in service provider networks.
In this section, several examples of VPN configuration sets are shown.
These drawings and detailed slides were generously provided by permission of Dr. Rekhter, a distinguished engineer of Juniper.
Figure 7.40 outlines the simple steps needed to configure RFC2547 on a Juniper router's top level.
Figure 7.40: Top-Level RFC2547 VPN Configuration
In Figure 7.41, we see the detailed configuration commands.
Figure 7.41: Configuration Details for RFC 2547
Once the router has been configured to run the RFC 2547 protocol, the choice arises as to what type of VPN will be running. In Figure 7.42, we see the top-level configuration for a Layer-2 VPN, followed by detailed configurations in Figure 7.43.
Figure 7.42: Layer-2 VPN Top Level
Figure 7.43: Detailed VPN Configuration
Note that the code between Figures 7.43 and Figure 7.44 does not change. We find that the configuration summary is about the same for VPLS.
Figure 7.44: Top-Level VPLS Configuration
In this example of VPN configuration, we find that configurations remain simple once RFC 2547 has been configured, no matter what Layer 2 VPN is running.
| < Day Day Up > |
|