VPN Configlet Generation

As mentioned earlier under the sections under VPN Design and Modeling using the VPN Wizard, the VPN Module gives you the ability to generate VPN configlets for a particular VPN. For instance, the last step under the section, L3 (Layer 3) VPN, describes how to generate and display the configlet for a L3VPN. The following figures show configlets generated for two of the VPNs discussed earlier.

Figure 1: A Configlet Generated for a L3VPN Network management interface showing Layer 3 VPN L3VPN_UNO configuration details with topology, nodes, IPs, RDs, policies, and OSPF protocol.

Network management interface showing Layer 3 VPN L3VPN_UNO configuration details with topology, nodes, IPs, RDs, policies, and OSPF protocol.

Figure 2: A Configlet Generated for a L2CCC VPN Network management interface showing Layer 2 CCC VPN L2CCC_1 configuration with topology, endpoints C_PE_RT01 and C_PE_RT02, bandwidth 10.000M, and Ethernet encapsulation.

Network management interface showing Layer 2 CCC VPN L2CCC_1 configuration with topology, endpoints C_PE_RT01 and C_PE_RT02, bandwidth 10.000M, and Ethernet encapsulation.

To generate configlets in batch for several of the VPNs in a network, you may use the VPN Configlet window (accessed via the Design > Configlets/Delta > VPN Configlet menu), shown in the following figure, where you can specify a particular directory (specified in the Directory box) to store the generated VPN configlets. In addition, you may also choose to generate configlets for particular nodes or VPNs via the Node/VPN drop-downs.

Figure 3: VPN Configlet Menu VPN Configlet interface for setting target directory, provisioning work order, and selecting CLI commands. Includes node/VPN dropdowns, VPN comparison section, and buttons: Submit, View/Edit, Template, Close, Help.

VPN Configlet interface for setting target directory, provisioning work order, and selecting CLI commands. Includes node/VPN dropdowns, VPN comparison section, and buttons: Submit, View/Edit, Template, Close, Help.

Select “CLI Commands” before clicking “Submit” to also generate the corresponding CLI commands corresponding to the configlet.

The following figure shows a VPN directory that contains all of the generated VPN configlets for the network.

Figure 4: VPN Directory with the Generated VPN Configlets File manager interface showing directories and files. Current path is /u3/BBTP/users/thl/doc-vpnl2m/spec-0930/VPN/. File list includes names like E172.16.0.0.All, permissions -rw-r--r--, owner wandl, sizes 57 bytes, modified 10/2. Disk usage is 93 percent used.

File manager interface showing directories and files. Current path is /u3/BBTP/users/thl/doc-vpnl2m/spec-0930/VPN/. File list includes names like E172.16.0.0.All, permissions -rw-r--r--, owner wandl, sizes 57 bytes, modified 10/2. Disk usage is 93 percent used.

An example of a generated VPN configlet is shown in the following figure.

Figure 5: The Configlet Generated for JUNIPER_EDGE_A Text editor displaying a Juniper device config file with Layer 2 Martini settings: routing instances empty, protocols l2circuit defined, neighbor IPs with interfaces and virtual circuit IDs.

Text editor displaying a Juniper device config file with Layer 2 Martini settings: routing instances empty, protocols l2circuit defined, neighbor IPs with interfaces and virtual circuit IDs.