Up until this point in the book, we have been describing all the mechanisms that make up the basic MPLS-enabled VPN architecture. We have explored several different topologies and features that provide solutions to many business and services requirements.
One of the most important issues to address with any network design is how the solution will scale, both initially and in the future. This issue will be common across all deployments, so it is important to understand how to implement the architecture in a scalable and optimal way. Although many network deployments will be similar in nature, each will require a slightly different design and optimization and may have requirements that necessitate enhancements to the features that we described in previous chapters.
This chapter introduces several advanced topics that aim to address these issues. This chapter also illustrates various mechanisms that may be used during the deployment of the MPLS-enabled VPN architecture to assist with the scaling and optimization of the network infrastructure, as well as the introduction of advanced topologies to support certain types of connectivity requirements.
The SuperCom backbone topology illustrated in Figure 12-1 will be used throughout this chapter; Table 12-1 provides all the necessary IP address assignments for the service provider backbone and VPN customers.
Company |
Site |
Subnet |
---|---|---|
FastFoods |
San Jose |
195.12.2.0/24 |
Lyon |
10.2.1.0/24 |
|
NYBank |
Denver |
196.27.5.0/24 |
San Francisco |
196.27.6.0/24 |
|
New York |
196.27.4.0/24 |
|
EuroBank |
San Francisco |
10.2.1.0/24 |
Paris |
196.7.25.0/24 |
|
SuperCom |
Paris (Loopback0) |
194.22.15.1/32 |
Paris (Loopback1) |
194.22.16.1/32 |
|
San Jose (Loopback0) |
194.22.15.2/32 |
|
San Jose (Loopback1) |
194.22.16.2/32 |
|
New York (Loopback0) |
194.22.15.3/32 |
|
FastFoods/EuroBank RR |
194.22.15.5/32 |
|
NYBank RR |
194.22.15.6/32 |