|Oracle® Communications Unified Inventory Management L2 VPN Technology Pack Implementation Guide
Part Number E36037-01
|PDF · Mobi · ePub|
This chapter provides an overview of the L2 VPN Technology Pack. The chapter also provides deployment information for the technology pack.
Layer 2 virtual private networks (VPNs) offer an alternative to implementing Layer 2 solutions. Service providers provision Layer 2 VPN services over an IP network that typically uses multi-protocol label switching (MPLS) to rapidly switch data packets supported by various Layer 2 technologies, including Ethernet, over the network. The shared network infrastructure helps reduce operational and capital costs. Figure 1-1 depicts a simplified view of the domain of a Layer 2 VPN.
Service providers mainly use virtual leased line (VLL) and virtual private LAN service (VPLS) to provide Layer 2 VPN services to customers. The L2 VPN Technology Pack provides business entities and behaviors to model instances of VLL service and VPLS.
A VLL service connects two customer edge (CE) devices at different locations. The VLL service uses a pseudo wire to connect the provider edge (PE) devices. A Layer 2 access network may be used to attach each CE device to a PE device in the provider network. The L2 VPN Technology Pack models the CE and PE devices and the interface between the CE and PE devices. Figure 1-2 depicts the domain of a VLL service.
A pseudo wire uses MPLS label switched paths (LSPs) to transport Layer 2 frames between the PE devices. The L2 VPN Technology Pack supports extensions for pseudo wires and LSPs to meet specific business needs of customers. Figure 1-3 depicts the Oracle Communications Unified Inventory Management (UIM) model for a pseudo wire.
A VPLS provides Layer 2 Ethernet connectivity across multiple customer sites in a manner that is transparent to the CE devices. The service provider takes care of transporting the Layer 2 frames and switching them across the provider network from one customer site to the other.
Service providers typically offer VPLS over a shared MPLS-based IP network. The L2 VPN Technology Pack models a VPLS deployed as a full mesh of pseudo wires between the PEs. In addition, the technology pack supports modeling of VPLS deployed using hierarchical and hub-and-spoke architectures. The technology pack also enables you to model dual-homed sites. Figure 1-4 depicts the domain of a VPLS.
The L2 VPN Technology Pack models PE routers in a VPLS network. A VPLS network consists of VPN virtual switching instances (VSIs) that reside on the PE routers. A single PE router may host multiple VPNs. Each VPN is uniquely identified by a service ID.
A PE router that provides a switched VPLS termination maintains a separate Layer 2 VSI for every host VPN. The PE router switches the Layer 2 frames entering a particular VPN to their destination based on the switching information in the associated VSI.
A PE router that provides a non-switched VPLS termination does not maintain VSIs for the host VPNs. Instead, the PE router forwards the Layer 2 frames to an intermediate router that maintains VSIs remotely for the host VPNs on the PE router. The intermediate router switches the Layer 2 frames that belong to a particular VPN based on the switching information in the associated VSI.The L2 VPN Technology Pack provides the business logic that models the VSI. Figure 1-5 depicts the specifications required to model a VPLS.
The L2 VPN Technology Pack models two variants of VPLS: Lassare (based on the label distribution protocol (LDP)) and Kompella (based on the border gateway protocol (BGP) auto discovery). In the Lassare variant, VPLS uses LDP to communicate between PE routers. Figure 1-6 depicts the elements in an LDP-based VPLS.
In the Kompella variant, each router connects to a central cloud and communicates with other routers using BGP. Existing routers automatically add new routers to the service. Figure 1-7 depicts the elements in a BGP auto discovery-based VPLS.
The L2 VPN Technology Pack also supports modeling of a combination of LDP- and BGP-based networks.
A Layer 2 VPN service is a realization of a transport service used by the data networking layer.
A data networking layer provides a high-level end-to-end view of the Layer 2 VPN service from a customer's perspective. The data networking layer may contain multiple transport services at a time.
The L2 VPN Technology Pack provides data networking cartridges that include specifications for modeling the data networking layer. Figure 1-8 illustrates these specifications. See "Data Networking Content" for more information.
Figure 1-9 illustrates the specifications used to model a VLL data networking site.
Figure 1-10 illustrates the specifications used to model a VPLS data networking site.
Table 1-1 describes the Layer 2 VPN Technology Pack, which is delivered as a ZIP file.
See "Layer 2 VPN Technology Pack Javadoc" for more information.
Super JAR Archive File
See "Layer 2 VPN Technology Pack Super JAR File" for more information.
Components of the Super JAR Archive File
See "Layer 2 VPN Technology Pack Individual Jar Files" for more information.
Cartridge Project ZIP Files and Sample Code
See "Layer 2 VPN Technology ZIP Archive Files" for more information.
From the javadocForTechPacks directory, open the javadoc_rel.date.time.build.zip file and extract the javadoc directory. Double-click the extracted javadoc/index.html file to access the Javadoc provided with the Layer 2 VPN Technology Pack, including information that summarizes classes, methods, and parameters.
The Layer 2 VPN Technology Pack super JAR file contains the entire contents of the technology pack and is ready for deployment using the Cartridge Deployer Tool. You use the Cartridge Deployer Tool to simultaneously deploy multiple cartridges to UIM run-time environments.
See UIM Cartridge and Technology Pack Guide for more information about the Cartridge Deployer Tool.
In addition to the deployable super JAR file, technology packs include individually JAR files. Deploying individual JAR files may be required if you extend a cartridge in Oracle Communications Design Studio.
JAR files must be deployed in the order shown below to ensure that all dependencies are met.
Note:The asterisk in the JAR file names in the previous list represent a five-segment release version number followed by a build number. The five-segment release version numbers represent the:
Major Version Number
Minor Version Number
The L2 VPN Technology Pack comprises a number of cartridges, which can be divided into three broad categories:
All of these separate cartridges are bundled together as the Layer 2 VPN cartridge bundle that you can deploy into Oracle Communications Unified Inventory Management (UIM).
The address, location, and party cartridges model addresses, locations, and parties that are used by data networking and Layer 2 VPN entities. There are separate address cartridges for several different cartridges as well as generic service location and address cartridges. The country-specific cartridges provide similar capabilities with minor variations based on local standards.
The address, location, and party cartridges are:
Address cartridge: ora_uim_address
Canada address cartridge: ora_uim_canada_address
Norway address cartridge: ora_uim_norway_address
Saudi Arabia address cartridge: ora_uim_saudi_arabia_address
Service location cartridge: ora_uim_service_location
United Kingdom address cartridge: ora_uim_uk_address
United States address cartridge: ora_uim_us_address
Party cartridge: ora_uim_party_customer
The data networking cartridges model capabilities that are independent of the technology used to implement the network. These cartridges can be used with other networking services, such as MPLS Layer 3 VPN or Metro Ethernet. See "Data Networking Content" for more information.
The data networking cartridges are:
Data networking device cartridge: ora_uim_data_networking_device
Data networking services cartridge: ora_uim_data_networking_service
The Layer 2 VPN cartridges model the capabilities specific to Layer 2 VPN technology. See "Layer 2 VPN Content" for more information.
The Layer 2 VPN cartridges are:
MPLS network cartridge: ora_uim_mpls_network
VPN id cartridge: ora_uim_vpn_id
Number group management cartridge: ora_uim_number_group_management
VLAN management cartridge: ora_uim_vlanmgmt
Layer 2 VPN core cartridge: ora_uim_l2vpn
Oracle recommends that you use the Cartridge Deployer Tool to deploy the Layer 2 VPN Technology Pack super JAR archive file to a UIM run-time environment. Deploying the technology pack with the Cartridge Deployer Tool ensures that all cartridges and dependencies are deployed in the proper order. See UIM Cartridge and Technology Pack Guide for more information about the Cartridge Deployer Tool.
Important:Before deploying the Layer 2 VPN Technology Pack, you must deploy the base cartridges if not previously deployed. For information on how to deploy the base cartridges, see UIM Cartridge and Technology Pack Guide.
For information about how to deploy individual cartridges into a UIM test environment, see the Design Studio Help. For information about how to deploy a cartridge into a UIM production environment, see UIM Cartridge and Technology Pack Guide.
In addition to the Layer 2 VPN cartridge bundle that you deploy into UIM, you can download a ZIP file that contains the individual cartridges that are bundled. You can open these individual files in Design Studio to review or to extend the technology pack.
See the Design Studio online Help and UIM Developer's Guide for information about opening files in Design Studio.
See UIM Concepts for guidelines and best practices for extending technology packs in general. See "Extending the Layer 2 VPN Technology Pack" for information about extending the L2 VPN Technology Pack.