Describes a scenario where the Acme manufacturing company has three offices, with branch offices exchanging data only with headquarters.
This example illustrates a scenario where the Acme manufacturing company has three offices, but permits the two branch (er1.par and er1.fra) offices to exchange data only with headquarters (er1.lon). Additionally, the headquarters communicates with an SP VPN node (er1.bru) that is not in the Acme VPN.
VPN configuration details
Example RT connectivity and Acme VPN footprint shows the footprint of the Acme VPN and the RTs set for all VPN nodes in this example.
-
The VPN is named Acme, and it is set to a Connectivity of RT and a Type of L3VPN.
-
In turn, each branch office is set to the Acme VPN with a Type of L3VPN.
-
To exchange data with two other VPN nodes in the Acme VPN, headquarters (er1.lon) imports the offices' exported route targets of 2:1 (er1.par) and 3:1 (er1.fra).
-
In turn, headquarters (er1.lon) exports a route target of 1:1. All three other VPN nodes import it (both offices and the SP VPN node).
-
Because the SP VPN node (er1.bru) is not in the Acme VPN, its communication with er1.lon is not within the context of the Acme VPN.
The VPN footprint in Example RT connectivity and Acme VPN footprint shows that if the circuit between er1.fra and er1.bru becomes congested or fails, the VPN is impacted. However, a failure of the circuit between the two branch offices is not impacted. This failure is illustrated in Example failure between branch offices in the Acme VPN, which shows that none of the demands associated with the VPN are rerouted.
For this example, VPN nodes belonging to Acme VPN, and Acme VPN filtered to demands illustrates the VPN nodes belonging to Acme VPN and the filtering of the Acme VPN to its associated demand traffic. It also shows the calculations of the Total connect and VPN connect columns in the VPN Nodes table.
-
The Total connect for the VPN node residing on er1.lon headquarters is the highest because it exchanges data with three other VPN nodes. Each of the offices and the service provider VPN node have 2 in the Total connect column.
-
The VPN connect for the VPN node at the er1.lon headquarters is the highest because it exchanges data with and is in the same VPN as the two offices. All three VPN nodes share the same VPN name.
Each office has 1 in the VPN connect column because it communicates with only one VPN node in the same VPN.
The service provider VPN node (er1.bru) has 0 VPN connects because it is not part of the Acme VPN.
