Oracle® Communications Unified Inventory ManagementThe MPLS L3 VPN Technology Pack enables you to model instances of an MPLS L3 VPN service in Oracle Communications Unified Inventory

Oracle® Communications Unified Inventory ManagementMPLS L3 VPN Technology Pack Implementation Guide

Release 7.2.2

E36035-01

January 2013

Oracle Communications Unified Inventory Management MPLS L3 VPN Technology Pack Implementation Guide, Release 7.2.2

E36035-01

Copyright © 2010, 2013, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

iii

Contents

Preface ................................................................................................................................................................. v

Audience....................................................................................................................................................... vRelated Documentation.............................................................................................................................. viDocumentation Accessibility ..................................................................................................................... vi

1 MPLS L3 VPN Technology Pack Overview

About the MPLS L3 VPN Technology Pack........................................................................................ 1-1Contents of the MPLS L3 VPN Technology Pack .............................................................................. 1-6

MPLS L3 VPN Technology Pack Javadoc....................................................................................... 1-7MPLS L3 VPN Technology Pack Super JAR File........................................................................... 1-7MPLS L3 VPN Technology Pack Individual Jar Files................................................................... 1-7MPLS L3 VPN Technology Pack ZIP Archive Files ...................................................................... 1-8

Address and Location Cartridges............................................................................................. 1-8Data Networking Cartridges..................................................................................................... 1-9MPLS L3 VPN Cartridges.......................................................................................................... 1-9

Deploying the MPLS L3 VPN Technology Pack................................................................................ 1-9Opening the Technology Pack in Design Studio............................................................................... 1-9

2 Address, Location, and Party Content

Entity Specifications ................................................................................................................................ 2-1Party Specifications............................................................................................................................ 2-1Place Specifications ............................................................................................................................ 2-1Role Specifications ............................................................................................................................. 2-3

3 MPLS L3 VPN Content

Entity Specifications ................................................................................................................................ 3-1Custom Network Address Specifications....................................................................................... 3-1Inventory Group Specifications ....................................................................................................... 3-3Logical Device Specifications ........................................................................................................... 3-4Logical Device Configuration Specifications ................................................................................. 3-4Network Specifications .................................................................................................................. 3-13Network Configuration Specifications ........................................................................................ 3-14Network Node Specifications........................................................................................................ 3-15Place Specifications ......................................................................................................................... 3-15Place Configuration Specifications ............................................................................................... 3-16

iv

Role Specifications .......................................................................................................................... 3-17Sequence Specifications.................................................................................................................. 3-18Service Specifications...................................................................................................................... 3-18Service Configuration Specifications............................................................................................ 3-18

Rulesets Included in the Technology Pack ...................................................................................... 3-18

4 Data Networking Content

Entity Specifications ................................................................................................................................ 4-1Device Interface Specifications......................................................................................................... 4-1Logical Device Specifications ........................................................................................................... 4-1Place Specifications ............................................................................................................................ 4-2Place Configuration Specifications .................................................................................................. 4-2Role Specifications ............................................................................................................................. 4-2Service Specifications......................................................................................................................... 4-3Service Configuration Specifications............................................................................................... 4-3

Rulesets ...................................................................................................................................................... 4-3

5 Extending the MPLS L3 VPN Technology Pack

Extending Validation and Auto-Assignment Capabilities .............................................................. 5-1Extending Configuration Specifications with Stub Configuration Items .................................... 5-2

Extending the MPLS L3 VPN Termination Model........................................................................ 5-2Extending the Extending the VRF-Lite Model............................................................................... 5-2

6 MPLS L3 VPN Technology Pack Service Example

Overview .................................................................................................................................................... 6-1Assumptions.............................................................................................................................................. 6-1Creating the Customer View.................................................................................................................. 6-1

Creating the Data Networking Service ........................................................................................... 6-2Creating Customer Service Locations ............................................................................................. 6-2Creating Customer Sites.................................................................................................................... 6-2

Provisioning the Customer Sites............................................................................................... 6-2Creating the Service Provider View ..................................................................................................... 6-3

Creating the Route Distinguishers................................................................................................... 6-3Creating Route Targets...................................................................................................................... 6-3Creating IP Addresses ....................................................................................................................... 6-4Creating VRFs..................................................................................................................................... 6-4Creating the VPN Network .............................................................................................................. 6-5Creating the Terminations ................................................................................................................ 6-5Creating the MPLS L3 VPN Service ................................................................................................ 6-6

Linking the Customer View to the Service Provider View.............................................................. 6-6Assigning the Transport Service ...................................................................................................... 6-6Assigning Terminations .................................................................................................................... 6-6

v

Preface

Oracle Communications Unified Inventory Management (UIM) technology packs provide support for specific technology domains and a solid base for project-specific adaptation. Each pack leverages Oracle's domain expertise and experience in building models to provide a rich set of business entities for a particular domain. Wherever possible, technology packs include elements and business logic based on relevant industry standards. The use of industry standards ensures that technology packs are broadly applicable, while still anticipating field extensions that enable project-specific implementations.

Technology packs are separately licensed and may evolve over multiple releases. Guidelines are provided to facilitate uptake of new or enriched elements while preserving field-developed implementations.

The MPLS L3 VPN Technology Pack provides business entities and behaviors required by providers of data networking services using MPLS Layer 3 Virtual Private Networks as standardized by RFC 4364. This includes support for hub-and-spoke, meshed, and hybrid topologies as well as extranets. VRF-Lite and interface-less VRFs are also supported.

This guide contains the following information about the MPLS L3 VPN Technology Pack:

■ Background and introductory information about MPLS L3 VPN technology and the technology pack

■ Contents of the technology pack

■ Instructions for configuring an MPLS L3 VPN service

■ Example implementation scenario

■ Extension points

AudienceThis document is intended for business analysts and the following groups of people who design and implement an MPLS L3 VPN service:

■ Customer-service subject-matter experts who model products in the application

■ Network design engineers who model equipment, connections, and networks in the application

■ Service provisioners who model services in the application

The guide assumes that readers have a working knowledge of MPLS L3 VPN technology and UIM.

vi

Related DocumentationFor more information, see the following documents in the Oracle Communications Unified Inventory Management documentation set:

■ UIM Installation Guide: Describes the requirements for installing UIM, installation procedures, and post-installation tasks.

■ UIM System Administrator’s Guide: Describes administrative tasks such as working with cartridges and technology packs, maintaining security, managing the database, configuring Oracle Map Viewer, and troubleshooting.

■ UIM Security Guide: Provides guidelines and recommendations for setting up UIM in a secure configuration.

■ UIM Concepts: Provides an overview of important concepts and an introduction to using both UIM and Design Studio.

■ UIM Developer’s Guide: Explains how to customize and extend many aspects of UIM, including the data model, life-cycle management, topology, security, rulesets, Web services, user interface, and localization.

■ UIM Information Model Reference: Describes the UIM information model entities and data attributes, and explains patterns that are common across all entities.

■ Oracle Communications Information Model Reference: Describes the Oracle Communications information model entities and data attributes, and explains patterns that are common across all entities. The information described in this reference is common across all Oracle Communications products.

■ UIM Cartridge and Technology Pack Guide: Provides information about how you use cartridges and technology packs with UIM. Describes the content of the base cartridges.

■ UIM technology pack implementation guides: Describe the content of product technology packs as well as configuration guidelines and implementation considerations.

For step-by-step instructions for performing tasks, log into each application to see the following:

■ Design Studio online Help: Provides step-by-step instructions for tasks you perform in Design Studio.

■ UIM online Help: Provides step-by-step instructions for tasks you perform in UIM.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

1

MPLS L3 VPN Technology Pack Overview 1-1

1MPLS L3 VPN Technology Pack Overview

This chapter provides an overview of the MPLS L3 VPN Technology Pack. The chapter also provides deployment information for the technology pack.

About the MPLS L3 VPN Technology PackThe MPLS L3 VPN Technology Pack enables you to model instances of an MPLS L3 VPN service in Oracle Communications Unified Inventory Management (UIM).

MPLS L3 VPN is a network-based VPN service that is used to connect customer sites. It is a Layer 3 IP-based VPN instead of traditional L2 VPN technologies. MPLS L3 VPN lets a service provider use an IP backbone to provide VPNs for its customers.

An MPLS L3 VPN service includes the following devices:

■ Customer Edge (CE) router: The routers connecting individual customer sites to the service provider network.

■ Provider Edge (PE) router: The service provider devices to which the CE routers are directly connected.

■ Provider (P) router: The service provider devices used for forwarding data in the IP backbone. The provider router is not directly connected to any customer edge router.

This technology uses a peer model in which the CE routers send their routes to the PE routers, there is no overlay visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes.

Figure 1–1 depicts a simplified view of an MPLS L3 VPN service.

About the MPLS L3 VPN Technology Pack

1-2 UIM MPLS L3 VPN Technology Pack Implementation Guide

Figure 1–1 MPLS L3 VPN Service Overview

The MPLS L3 VPN Technology Pack enables logical modeling of provider edge devices (PE), customer premise equipment (CPE) devices, VPN routing and forwarding (VRF), VRF-Lite, and interfaces. It contains extensive routing attributes for a variety of protocols, including Border Gateway Protocol (BGP), Open Shortest Path First (OSPF), Routing Information Protocol (RIP), Enhanced Interior Gateway Routing Protocol (EIGRP), and static routes. The technology pack also includes VRF attributes, enables modeling of dual-homed sites, and provides business logic for assignment of route distinguishers, route targets, and virtual private network IDs (VPN-IDs).

The data networking cartridges are included in this technology pack. See "Data Networking Content" for more information.

■ Hub-and-spoke

■ Mesh

■ Hybrid

■ Extranet

An MPLS L3 VPN service is modeled as a technology-specific instance of a data networking service. The technology pack includes specifications for modeling these generic data networking services. Figure 1–2 illustrates these specifications.



Figure 1–2 Data Networking Service Model

Figure 1–3 illustrates the specifications used to model a data networking site.



Figure 1–3 Data Networking Site Model

Figure 1–4 depicts the specifications used to model an MPLS L3 VPN network.



Figure 1–4 MPLS L3 VPN Network Model

Figure 1–5 depicts the specifications used to model an MPLS L3 VPN service.

Figure 1–5 MPLS L3 VPN Service Model

Contents of the MPLS L3 VPN Technology Pack


Figure 1–6 depicts the MPLS L3 VPN termination model.

Figure 1–6 MPLS L3 VPN Termination Model

Contents of the MPLS L3 VPN Technology PackTable 1–1 describes the contents of the MPLS L3 VPN Technology Pack, which is delivered as a ZIP file.



MPLS L3 VPN Technology Pack JavadocFrom 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 MPLS L3 VPN Technology Pack, including information that summarizes classes, methods, and parameters.

MPLS L3 VPN Technology Pack Super JAR FileThe MPLS L3 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.

MPLS L3 VPN Technology Pack Individual Jar FilesIn 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.

ora_uim_party_customer_cartproj-*.jar

ora_uim_address_cartproj-*.jar

ora_uim_us_address_cartproj-*.jar

ora_uim_canada_address_cartproj-*.jar

ora_uim_norway_address_cartproj-*.jar

ora_uim_uk_address_cartproj-*.jar

ora_uim_saudi_arabia_address_cartproj-*.jar

ora_uim_service_location_cartproj-*.jar

ora_uim_data_networking_device_cartproj-*.jar

Table 1–1 MPLS L3 VPN Technology Pack ZIP File Contents

Item Directory

Javadoc doc/javadocForTechPacks

See "MPLS L3 VPN Technology Pack Javadoc" for more information.

Super JAR Archive File deploy/superJarToDeploy

See "MPLS L3 VPN Technology Pack Super JAR File" for more information.

Components of the Super JAR Archive File

deploy/individualJarsForSuperJar

See "MPLS L3 VPN Technology Pack Individual Jar Files" for more information.

Cartridge Project ZIP Files and Sample Code

designStudio/cartridgeZips

See "MPLS L3 VPN Technology Pack ZIP Archive Files" for more information.



ora_uim_data_networking_service_cartproj-*.jar

ora_uim_internet_naming_and_addressing_cartproj-*.jar

ora_uim_routing_cartproj-*.jar

ora_uim_mpls_network_cartproj-*.jar

ora_uim_number_group_management_cartproj-*.jar

ora_uim_vpn_id_cartproj-*.jar

ora_uim_vrf_cartproj-*.jar

ora_uim_mplsl3vpn_cartproj-*.jar

MPLS L3 VPN Technology Pack ZIP Archive FilesThe MPLS L3 VPN Technology Pack comprises a number of cartridges that can be divided into three broad categories:

■ Address and location cartridges

■ Data networking cartridges

■ MPLS L3 VPN cartridges

All of these separate cartridges are included in a cartridge bundle that you can deploy into UIM.

Address and Location CartridgesThe address and location cartridges model addresses and locations that are used by data networking and MPLS L3 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 and location 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

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

■ Maintenance Pack

■ Generic Patch

■ Customer Patch

Opening the Technology Pack in Design Studio


■ Party cartridge: ora_uim_party_customer

Data Networking CartridgesThe 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 Level 3. 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

MPLS L3 VPN CartridgesThe MPLS L3 VPN cartridges model the capabilities specific to MPLS L3 VPN technology. See "MPLS L3 VPN Content" for more information.

The MPLS L3 VPN cartridges are:

■ ora_uim_mplsl3vpn

■ ora_uim_mpls_network

■ ora_uim_vpn_id

■ ora_uim_vrf

■ ora_uim_routing

■ ora_uim_number_group_management

■ ora_uim_internet_naming_and_addressing

Deploying the MPLS L3 VPN Technology PackOracle recommends that you use the Cartridge Deployer Tool to deploy the MPLS L3 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.

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.

Opening the Technology Pack in Design StudioIn addition to the 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 Oracle Communications Design Studio to review or to extend the technology pack.

Important: Before deploying the MPLS L3 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.

Opening the Technology Pack in Design Studio


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 MPLS L3 VPN Technology Pack" for information about extending this technology pack.

2

Address, Location, and Party Content 2-1

2Address, Location, and Party Content

This chapter lists the entity specifications, rules, and extension points included in the address, location, and party cartridges in the MPLS L3 VPN Technology Pack.

The 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

Entity SpecificationsThis section lists the specifications included in the address and location cartridges. Most are Place specifications. You can view the details of the specifications by opening the cartridges in Oracle Communications Design Studio.

Party SpecificationsTable 2–1 lists and describes the Party specifications included in the address, location, and party cartridges.

Place SpecificationsTable 2–2 lists and describes the Place specifications included in the address and location cartridges.

Table 2–1 Party Specifications

Specification Description

Organization Models an organization such as a business or a government agency; can be assigned the Customer role

Individual Models a single individual, such as a subscriber; can be assigned the Customer role

Entity Specifications


Table 2–2 Place Specifications


canadaAddress Postal address of the subscriber in Canada

The canadaAddress specification contains the following characteristics:

■ Address Line 1: The first line of the Address field; maximum 100 characters long

■ Address Line 2: The second line of the Address field; maximum 100 characters long

■ City: Name of the Canada city where the subscriber is located

■ Postal Code: Postal code of the area where the subscriber is located; seven characters long

■ Province: Canada province where the subscriber is located

■ Country: Name of the country where the subscriber is located

canadaCity Location specification used to populate the City field in Canadian addresses

canadaProvinceCode Location specification used to populate the Province field in Canadian addresses

country Location specification for countries

norwayAddress Postal address of the subscriber in Norway

The norwayAddress specification contains the following characteristics:



■ City: Name of the Norway city where the subscriber is located


■ postalCode: Postal code of the Norway state where the subscriber is located; five characters long

norwayCity Location specification used to populate the City field in Norwegian addresses

saudiArabiaAddress Postal address of the subscriber in Saudi Arabia

The saudiArabiaAddress specification contains the following characteristics:



■ City: Name of the Saudi city where the subscriber is located


■ postalCode: Postal code of the Saudi state where the subscriber is located; seven characters long

saudiArabiaCity Location specification used to populate the City field in Saudi addresses

serviceLocation Location specification used to define where a service is delivered

ukAddress Postal address of the subscriber in the UK

The ukAddress specification contains the following characteristics:



■ City: Name of the UK city where the subscriber is located


■ postalCode: Postal code of the UK state where the subscriber is located; seven characters long


Address, Location, and Party Content 2-3

Role SpecificationsTable 2–3 lists and describes the Role specifications included in the address, location, and party cartridges.

ukCity Location specification used to populate the City field in UK addresses

usAddress Postal address of the subscriber in the US

The usAddress specification contains the following characteristics:




■ State: Name of the US state where the subscriber is located

■ City: Name of the US city where the subscriber is located

■ Zip Code: ZIP code of the area where the subscriber is located; nine characters long

usCity Location specification used to populate the City field in US addresses

Child of usState

usStateCode Location specification used to populate the State field in US addresses

Parent of usCity.

Table 2–3 Role Specifications


Customer Designates an Organization or Individual entity as a customer

Subscriber Designates an Organization or Individual entity as a subscriber

Table 2–2 (Cont.) Place Specifications




3

MPLS L3 VPN Content 3-1

3MPLS L3 VPN Content

This chapter lists the entity specifications and rules included in the MPLS L3 VPN-specific cartridges in the MPLS L3 VPN Technology Pack.

Entity SpecificationsThis section lists the specifications included in the MPLS L3 VPN-specific cartridges, organized by specification type. You can view the details of the specifications by opening the cartridges in Oracle Communications Design Studio.

Custom Network Address SpecificationsTable 3–1 lists and describes the Custom Network Address specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.



Table 3–1 Custom Network Address Specifications


Route Distinguisher Represents a route distinguisher scoped to a route distinguisher group

A route distinguisher is added to the beginning of the customer's IP prefixes to change them into globally unique VPN-IP prefixes. A route distinguisher is made up of two values, the administrative value and the assigned value, which compiled make up six bytes.

The Route Distinguisher specification includes the following characteristics:

■ Format Type: Determines the format of the route distinguisher

The Format Type characteristic can be set to one of the following types:

Type 0 AS: Administrative value is two-byte numeric value and assigned value is four-byte numeric value.

Type 1 IP: Administrative value is IP dotted notation four-byte value and assigned value is two-byte numeric value.

Type 2 AS4: Administrative value is four-byte numeric value and assigned value is two-byte numeric value.

■ Administrator Value: The first part of the route distinguisher, which usually defines the autonomous system that the route distinguisher will use.

■ Assigned value: The second part of the route distinguisher, which assigns a unique number within administrative value’s group.

■ Initial Route Distinguisher Group Name: Set value to the route distinguisher (group) that this route distinguisher will initially be added to.

Route Target Represents a route target scoped to a route target group

A route target is used for defining VPN membership. A route target is made up of two values, the administrative value and the assigned value, which compiled make up six bytes.

The Route Target specification includes the following characteristics:

■ Format Type: Determines the format of the route target

The Format Type characteristic can be set to one of the following types:

Type 0 AS: Administrative value is two-byte numeric value and assigned value is four-byte numeric value.

Type 1 IP: Administrative value is IP dotted notation four-byte value and assigned value is two-byte numeric value.

Type 2 AS4: Administrative value is four-byte numeric value and assigned value is two-byte numeric value.

■ Administrator Value: The first part of the route target, which usually defines the autonomous system that the route target will use.

■ Assigned value: The second part of the route target, which assigns a unique number within administrative value’s group.

■ Initial Route Target Group Name: Set value to the route target (group) that this route target will initially be added to.



Inventory Group SpecificationsTable 3–2 lists and describes the Inventory Group specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

VPN ID Represents unique identifier for a VPN Service

IPv4 IP Address Represents an IPv4 address

The IPv4 IP Address specification includes the following characteristics:

■ ipv4Address: A dotted notation of an Internet address

■ ipv4Cidr: A numeric value that defines the subnet prefix

IPv6 IP Address Represents an IPv6 address

The IPv6 IP Address specification includes the following characteristics:

■ ipv6Address: A dotted notation of an Internet Address

■ ipv6Cidr: A numeric value that defines the subnet prefix

Table 3–2 Inventory Group Specifications


Route Distinguisher Type 0 Group

Represents a pool or group of Type 0 route distinguishers

Creating an inventory group based on this specification triggers the ADD_ROUTEDISTINGUISHER0_GROUP ruleset, which creates route distinguishers based on the values you enter in the Initial Route Distinguisher Range field.

The Route Distinguisher Type 0 Group specification includes the following characteristics:

■ Initial Route Distinguisher Range: Optional parameter that contains comma- or dash-separated values to specify a range of route distinguishers to be created. For example 1:1-1:3, 1:5 will create route distinguisher list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.





■ Initial Route Distinguisher Range: Optional parameter that contains comma- or dash-separated values to specify a range of route distinguishers to be created. For example 1.0.0.1:1-1.0.0.1:3, 1.0.0.1:5 will create route distinguisher list of 1.0.0.1:1, 1.0.0.1:2, 1.0.0.1:3, and 1.0.0.1:5. This characteristic is a validated parameter.





■ Initial Route Distinguisher Range: Optional parameter that contains comma- or dash-separated values to specify a range of route distinguishers to be created. For example 1:1-1:3, 1:5 will create route distinguisher list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.

Table 3–1 (Cont.) Custom Network Address Specifications




Logical Device SpecificationsTable 3–3 lists and describes the Logical Device specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Logical Device Configuration SpecificationsThe MPLS L3 VPN Technology Pack includes two Logical Device Configuration specifications, one for MPLS VPN VRF logical device configurations and the other for MPLS VPN VRF-Lite logical device configurations.

Route Target Type 0 Group

Represents a pool or group of Type 0 route targets

Creating an inventory group based on this specification triggers the ADD_ROUTETARGET0_GROUP ruleset, which creates route targets based on the values you enter in the Initial Route Target Range field.

The Route Target Type 0 Group specification includes the following characteristics:

■ Initial Route Target Range: Contains comma- or dash-separated values to specify a range of route targets to be created. For example 1:1-1:3, 1:5 will create route target list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.





■ Initial Route Target Range: Contains comma- or dash-separated values to specify a range of route targets to be created. For example 1.0.0.1:1-1.0.0.1:3, 1.0.0.1:5 will create route target list of 1.0.0.1:1, 1.0.0.1:2, 1.0.0.1:3, and 1.0.0.1:5. This characteristic is a validated parameter.





■ Initial Route Target Range: Contains comma- or dash-separated values to specify a range of route targets to be created. For example 1:1-1:3, 1:5 will create route target list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.

Table 3–3 Logical Device Specifications


DHCP Server Creates logical devices that represent DHCP servers

TFTP Server Creates logical devices that represent TFTP servers

VRF Defines a VRF instance

This object is contained within a data networking device; can include configurations based on the MPLS VPN VRF Configuration specification.

The VRF specification includes the following characteristic:

■ Preferred Route Distinguisher Group: The name of a route distinguisher group that will be used as the preferred location to assign route distinguishers when auto assignment is executed on the MPLS VPN VRF Configuration specification.

Table 3–2 (Cont.) Inventory Group Specifications




Because of their complexity, each of these specifications is described in a separate table. Table 3–4 describes the MPLS VPN VRF logical device configuration specification and Table 3–5 describes the MPLS VPN VRF-Lite logical device configuration specification.

For information about the routing characteristics, see the Juniper Networks and Cisco Systems Web sites:

http:\\www.juniper.net

http:\\www.cisco.com

Table 3–4 MPLS VPN VRF Configuration Specification

Configuration ItemChild Configuration Item Description

MPLS VPN VRF Configuration

Top-level item that includes parameters for configuring VRF details such as name and route limits.

Route Distinguisher Enables you to assign a Route Distinguisher entity used in the VRF.

Routing Protocols Contains configuration items for supported routing protocols, including RIP, OSPF, EIGRP, BGP, and BGP-VPN.

Routing Protocols RIP Defines some device-level RIP attributes and also contains other configuration items related to RIP:

Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table.

■ From BGP-VPN: Defines metrics for importing routes from BGP-VPN tables into this protocols table.

■ From OSPF: Defines metrics for importing routes from OSPF tables into this protocols table.

■ From EIGRP: Defines metrics for importing routes from EIGRP tables into this protocols table.

■ From BGP: Defines metrics for importing routes from BGP tables into this protocols table.

■ From Direct Connected: Defines metrics for importing routes derived from connected interfaces into this protocols table.

■ From Static Routes: Defines metrics for importing routes derived from static route entries into this protocols table.



Routing Protocols OSPF Defines some device-level OSPF configuration and also contains other configuration items related to OSPF:


■ From RIP: Defines metrics for importing routes from RIP tables into this protocols table.






Area: Defines an OSPF area and device-level details about the area.

Summary Addresses: Contains Summary Address configuration items.

■ Summary Address: Defines an address that summarizes other addresses for advertising.

Throttling: Defines OSPF update throttling parameters.

Table 3–4 (Cont.) MPLS VPN VRF Configuration Specification




Routing Protocols EIGRP Defines some device-level EIGRP configuration and also contains other configuration items related to EIGRP.












Routing Protocols BGP Defines some device-level BGP configuration and also contains other configuration items related to BGP.








Networks: Contains Network configuration items.

■ Network: Used to statically define a network address to be advertised in BGP.

Aggregate Addresses: Contains Aggregates Address configuration items.

■ Aggregate Address: Defines an Address that summarizes other addresses for advertising.

Multipath: Defines the Multipath load balancing and maximum path configuration.

Group: Defines a BGP Group, which is a profile of BGP configuration that a BGP Neighbor can inherit from.

■ Damping: Defines BGP Damping information specific to this BGP Group.

Damping: Defines BGP Damping information at the device-level. Can be overridden at Group or Neighbor level.

Static Routes: Contains static route configuration items.

■ IPV4 Static Route: Defines an IPv4 Static Route.






Routing Protocols BGP-VPN Defines some device-level BGP-VPN configuration and also contains other configuration items related to BGP-VPN.








Table 3–5 VRF-Lite Configuration Specification


VRF-Lite Configuration

Top-level configuration item that defines parameters for configuring the VRF, such as name and route limits. The specification includes the following characteristic:

■ Preferred Route Distinguisher Group: The name of a route distinguisher group that will be used as the preferred location to assign route distinguishers when auto assignment is executed on the VRF-Lite Configuration.

Routing Protocols Contains configuration items for supported routing protocols, including RIP, OSPF, EIGRP, BGP, and BGP-VPN.

Routing Protocols RIP Defines some device-level RIP configuration and also contains other configuration items related to RIP.












Routing Protocols OSPF Defines some device-level OSPF configuration and also contains other configuration items related to OSPF.








Throttling: Defines OSPF update throttling parameters.

Summary Addresses: Contains Summary Address configuration items.

■ Summary Address: Defines an Address that summarizes other addresses for advertising.

Area: Defines an OSPF Area and device-level details about the Area.

Routing Protocols EIGRP Defines some device-level EIGRP configuration and also contains other configuration items related to EIGRP.








Table 3–5 (Cont.) VRF-Lite Configuration Specification




Routing Protocols BGP Defines some device-level BGP configurations and also contains other configuration items related to BGP.








Networks: Contains Network configuration items.

■ Network: Used to statically define a network address to be advertised in BGP.

Aggregate Addresses: Contains Aggregates Address configuration items.

■ Aggregate Address: Defines an Address that summarizes other addresses for advertising.

Multipath: Defines the Multipath load balancing and maximum path configuration.

Group: Defines a BGP Group, which is a profile of BGP configuration that a BGP Neighbor can inherit from.

■ Damping: Defines BGP Damping information specific to this BGP Group.

Damping: Defines BGP Damping information at the device level. Can be overridden at Group or Neighbor level.








Routing Protocols BGP-VPN Defines some device-level BGP-VPN configuration and also contains other configuration items related to BGP-VPN.








VRF Interface Enables you to assign a Data Networking Device Interface entity used in the termination.

VRF Interface IP Address Enables you to assign an IP address entity used for the interface.





Network SpecificationsTable 3–6 lists and describes the Network specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

VRF Interface L3 QoS A stub configuration item, which allows custom extensions where the end user can assign L3 QoS information.

VRF Interface Routing Protocols Contains configuration items for various routing protocols such as RIP, BGP, OSPF, etc. that are specific to this interface.

RIP: Defines RIP configuration information specific to this interface.

OSPF: Defines OSPF configuration information specific to this interface.

EIGRP: Defines EIGRP configuration information specific to this interface.

BGP Neighbor: Defines BGP Neighbor configuration information and also contains other configuration items related to the BGP Neighbor.

■ BGP Timers: Defines parameters for configuring keep-alive timers for detecting dead peers.

■ Prefix Limit: Defines parameters to control how many prefixes can be received from a neighbor.

■ Damping: Defines damping parameters specific to this BGP Neighbor.

The BGP Neighbor configuration item includes the following characteristic:

■ Group Name: This characteristic refers to a BGP Group. For validation, you must create a BGP Group configuration item in the VRF-Lite Configuration.


■ IPv4 Static Route: Defines an IPv4 Static Route.

■ IPv6 Static Route: Defines an IPv6 Static Route.

DHCP Relay IP Address: Enables you to assign a DHCP Server entity that will represent the Relay IP Address.

Route Distinguisher Enables you to assign a Route Distinguisher entity used in the VRF.





Network Configuration SpecificationsTable 3–7 lists and describes the Network Configuration specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Table 3–6 Network Specifications


MPLS Core Network Defines an MPLS core switching network

The MPLS L3 VPN networks are implemented on top of MPLS networks. This specification is used to represent the devices that make up the MPLS core network. These devices are the Provider Edge devices and Provider Core devices.

MPLS L3 VPN Network Defines an MPLS L3 VPN network

Each VPN network represents a topology segment for a larger VPN network. A VPN network is either a Full Mesh topology or Hub and Spoke topology. Each VPN network can be divided into a set of Mesh and Hub and Spoke network segments. The MPLS L3 VPN Network specification defines one of the network segments. Can include configurations based on the MPLS L3 VPN Network Configuration specification.

The MPLS L3 VPN Network specification includes the following characteristics:

■ Preferred Route Target Group: The name of a route target group that is used as the preferred location to assign route targets when auto assignment is executed on the MPLS L3 VPN Network Configuration specification.



Network Node SpecificationsTable 3–8 lists and describes the Network Node specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Place SpecificationsTable 3–9 lists and describes the Place specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Table 3–7 Network Configuration Specifications


MPLS L3 VPN Network Configuration

Contains MPLS L3 VPN Network Configuration information pertaining to the MPLS L3 VPN network

The MPLS L3 VPN Network Configuration specification includes the following characteristic:

■ VPN Topology: The connectivity topology of the VRFs in the MPLS L3 VPN network. You can choose Full Mesh or Hub and Spoke.

You can add the following configuration items:

■ Route Target: Defines membership usage of a route target and enables you to assign a route target entity used in the network

The Route Target configuration item includes the following characteristics:

Mesh Action: The action that a VRF with Full Mesh Member set as their membership type will take on the route target. The action can be to either Import routes from the VPN, Export routes to the VPN or both Import and Export routes from/to the VPN.

Spoke Action: The action that a VRF with Spoke Member set as their membership type will take on the route target. The action can be to either Import routes from the VPN, Export routes from the VPN or both Import and Export routes from/to the VPN.

Hub Action: The action that a VRF with Hub Member set as their membership type will take on the route target. The action can be to either Import routes from the VPN, Export routes from the VPN or both Import and Export routes from/to the VPN.

■ VRF: Defines membership of a VRF and enables you to assign a VRF entity used in the network

The VRF configuration item includes the following characteristic:

Membership Type: The role in the VPN topology that the VRF will play depending on the topology. If the VPN network is a hub and spoke, the VRF can either be a hub or spoke member. For a full mesh VPN network, full mesh member is the only valid choice.

Table 3–8 Network Node Specifications


MPLS Label Router Represents a router in an MPLS core network

MPLS VPN VRF Represents a VRF in the MPLS L3 VPN Network Topology view



Place Configuration SpecificationsTable 3–10 describes the MPL3 VPN Termination Place Configuration specification included in the MPLS L3 VPN-specific cartridges of the technology pack.



MPLS L3 VPN Termination

Defines MPLS L3 VPN termination, which is the service provider side of the VRF attachment circuit

Can include configurations based on the MPLS L3 VPN Termination Configuration specification.

Table 3–10 Place Configuration Specifications

Configuration Item

Child Configuration Item Description

MPLS L3 VPN Termination Configuration

Contains information about the MPLS L3 VPN Termination specification

Also contains configuration items that define the content of the configuration.

VRF Attachment Circuit Termination

Contains configuration items for Provider Edge Interface, Routing Protocols, and VRF,



Role SpecificationsTable 3–11 lists and describes the Role specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.


Provider Edge Interface

Enables you to assign a Data Networking Device Interface entity used in the termination

IP Address: Enables you to assign an IP address entity used for the interface.

DHCP Relay IP Address: Enables you to assign a DHCP Server entity that will represent the Relay IP Address

L3 QoS: A stub configuration item, which allows custom extensions where the end user can assign L3 QoS information


Routing Protocols Contains configuration items for various routing protocols that are specific to this termination

eBGP Neighbor: Defines eBGP Neighbor configuration information and also contains other configuration items related to the eBGP Neighbor

■ Damping: Defines damping parameters specific to this BGP Neighbor

■ Prefix Limit: Defines parameters to control how many prefixes can be received from a neighbor

■ Timers: Defines parameters for configuring keep-alive timers for detecting dead peers

The eBGP Neighbor configuration item includes the following characteristic:

■ Group Name: This characteristic refers to a BGP Group. For validation, the user must create a BGP Group configuration item in the MPLS VPN VRF Configuration of the VRF that was assigned to this termination.

RIP: Defines RIP configuration information specific to this termination

EIGRP: Defines EIGRP configuration information specific to this termination

OSPF: Defines OSPF configuration information specific to this termination

Static Routes: Contains static route configuration items

■ IPV4 Static Route: Defines an IPv4 Static Route

■ IPV6 Static Route: Defines an IPv6 Static Route


VRF Enables you to assign a VRF entity used in the termination



MPLS Label Edge Router Defines a Label Edge Router that terminates Label Switch Paths

MPLS Label Switch Router

Defines a Label Switch Router that transits Label Switch Paths

Table 3–10 (Cont.) Place Configuration Specifications

Configuration Item

Child Configuration Item Description

Rulesets Included in the Technology Pack


Sequence SpecificationsTable 3–12 lists and describes the Sequence specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Service SpecificationsTable 3–13 lists and describes the Service specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Service Configuration SpecificationsTable 3–14 lists and describes the Service Configuration specifications included in the MPLS L3 VPN-specific cartridges of the technology pack.

Rulesets Included in the Technology PackRules are executed at the point identified in the corresponding ruleset extension point specification. This point, in turn, corresponds to a class/method signature in a base extension point included in the ora_uim_baseextpts cartridge. The MPLS L3 VPN cartridge requires the ora_uim_baseextpts cartridge. See "Deploying the MPLS L3 VPN Technology Pack" for more information. You can modify the rules and their extension points to meet your business needs. See UIM Developer’s Guide for more information.

Table 3–15 lists the rulesets that are included in the MPLS L3 VPN Technology Pack.

Table 3–12 Sequence Specifications


VPN ID Index Defines the range of numbers for the index portion of VPN IDs created by auto assignment; also defines how the numbers are incremented.

Table 3–13 Service Specifications


MPLS L3 VPN Service Defines the MPLS L3 VPN service

This specification collects all the data to define this service, which include VPN Networks and VPN Terminations; can include configurations based on the MPLS L3 VPN Service Configuration specification.

Table 3–14 Service Configuration Specifications


MPLS L3 VPN Configuration

Contains MPLS L3 VPN Service Configuration information pertaining to the MPLS L3 VPN Service.


■ MPLS Core Network: Enables you to assign an MPLS Core Network entity that is used by this Service

■ MPLS L3 VPN Network: Enables you to assign MPLS L3 VPN Network entity that is used by this Service

■ VPN ID: Enables you to assign a VPN ID entity that is used by this Service

■ VPN Transport Terminations: Contains MPLS VPN Termination configuration items

■ MPLS VPN Termination: Enables you to assign MPLS L3 VPN Termination entities that are used by this Service



Table 3–15 Rulesets in the MPLS L3 VPN Technology Pack

Ruleset/Ruleset Extension Points Functionality

VRF_ALLOCATE_ALL_VRF

VRF_ALLOCATE_ALL_VRF_EXT

Automatically assigns a route distinguisher to the VRF-Lite Configuration. If Preferred Route Distinguisher Group is set, the ruleset will assign an unassigned route distinguisher from the group. If Preferred Route Distinguisher Group is not set, then any unassigned route distinguisher will be assigned. Triggered by the Auto Assign menu item in the Related Pages menu.

VRF_VALIDATE_VRF

VRF_VALIDATE_VRF_EXT

Validates the VRF-Lite Configuration

Triggered by Validate menu item in the Actions menu

MPLSL3VPN_ALLOCATE_ALL_NETWORK

MPLSL3VPN_ALLOCATE_ALL_NETWORK_EXT

Automatically assigns route targets to the VPN Network Configuration. If Preferred Route Target Group is set, the ruleset will assign an unassigned route target from the group. If Preferred Route Distinguisher Group is not set, then any unassigned route target will be assigned.

Triggered by the Auto Assign menu item in the Related Pages menu

MPLSL3VPN_ALLOCATE_ALL_SERVICE

MPLSL3VPN_ALLOCATE_ALL_SERVICE_EXT

Automatically assigns a VPN ID to the MPLS L3 VPN Service Configuration.


MPLSL3VPN_ALLOCATE_ALL_VRF

MPLSL3VPN_ALLOCATE_ALL_VRF_EXT

Automatically assigns a route distinguisher to the VRF Configuration. If Preferred Route Distinguisher Group is set, the ruleset will assign an unassigned route distinguisher from the group. If Preferred Route Distinguisher Group is not set, then any unassigned route distinguisher will be assigned.


MPLSL3VPN_VALIDATE_NETWORK

MPLSL3VPN_VALIDATE_NETWORK_EXT

Validates the MPLS L3 VPN Network Configuration

Triggered by the Validate menu item in the Related Pages menu

MPLSL3VPN_VALIDATE_SERVICE

MPLSL3VPN_VALIDATE_SERVICE_EXT

Validates the MPLS L3 VPN Service Configuration


MPLSL3VPN_VALIDATE_PLACE

MPLSL3VPN_VALIDATE_PLACE_EXT

Validates the MPLS L3 VPN Termination Configuration


MPLSL3VPN_VALIDATE_VRF

MPLSL3VPN_VALIDATE_VRF_EXT

Validates the VRF Configuration


ADD_ROUTEDISTINGUISHER0_GROUP

ADD_ROUTEDISTINGUISHER0_GROUP_EXT

Automatically creates the corresponding Type 0 route distinguishers using the data from the characteristic Initial Route Distinguisher Range when a Route Distinguisher Type 0 Group specification is created.

Triggered by creating a Route Distinguisher Type 0 Group specification











ADD_ROUTETARGET0_GROUP

ADD_ROUTETARGET0_GROUP_EXT

Automatically creates the corresponding Type 0 Route Targets using the data from the characteristic Initial Route Target List when a Type 0 Route Target Group is created.

Triggered by creating a Type 0 Route Target Group.









ASSOCIATE_WITH_ROUTEDISTINGUISHER0_GROUP

ASSOCIATE_WITH_ROUTEDISTINGUISHER0_GROUP_EXT

Automatically associates a Type 0 Route Distinguisher to a Type 0 Route Distinguisher Group when that Route Distinguisher is created on its own.

Triggered by creating a Type 0 Route Distinguisher and setting the Route Distinguisher Group that is should belong to.









ASSOCIATE_WITH_ROUTETARGET0_GROUP

ASSOCIATE_WITH_ROUTETARGET0_GROUP_EXT

Automatically associates a Type 0 Route Target to a Route Target Type 0 Group when that route target is created on its own.

Triggered by creating a Type 0 Route Target specification and setting the route target group that is should belong to



Automatically associates a Type 1 Route Target to a Route Target Type 1 Group when that Route Target is created on its own.

Triggered by creating a Type 1 Route Target and setting the route target group that is should belong to



Automatically associates a Type 2 Route Target to a Route Target Type 2 Group when that Route Target is created on its own.

Triggered by creating a Type 2 Route Target and setting the route target group that is should belong to

DELETE_ROUTEDISTINGUISHER0_GROUP

DELETE_ROUTEDISTINGUISHER0_GROUP_EXT

Automatically deletes the corresponding route distinguishers when the Route Distinguisher Type 0 Group specification is deleted.

Triggered by deleting a Route Distinguisher Type 0 Group specification

Table 3–15 (Cont.) Rulesets in the MPLS L3 VPN Technology Pack












DELETE_ROUTETARGET0_GROUP

DELETE_ROUTETARGET0_GROUP_EXT

Automatically deletes the corresponding route targets when the Route Target Type 0 Group specification is deleted.

Triggered by deleting a Route Target Type 0 Group specification









PREVENT_DISASSOCIATION_FROM_RTRD_GROUP

PREVENT_DISASSOCIATION_FROM_RTRD_GROUP_EXT

Prevents the disassociation of a route target or route distinguisher from a group.

Triggered by disassociating a route target or a route distinguisher from its group

VALIDATE_RTRD_FORMAT

VALIDATE_RTRD_FORMAT_EXT

Validates that the route target or route distinguisher is the proper format and that it matches the format in the group selected.

Triggered by creation of a route target or route distinguisher

Table 3–15 (Cont.) Rulesets in the MPLS L3 VPN Technology Pack




4

Data Networking Content 4-1

4Data Networking Content

This chapter lists the entity specifications included in the data networking cartridges of the MPLS L3 VPN Technology Pack.

The data networking cartridges are:

■ Data networking device cartridge: ora_uim_data_networking_device

■ Data networking services cartridge: ora_uim_data_networking_service

Entity SpecificationsThis section lists the specifications included in the data networking cartridges, organized by specification type. You can view the details of the specifications by opening the cartridges in Oracle Communications Design Studio.

Device Interface SpecificationsTable 4–1 lists and describes the Device Interface specifications included in the Data Networking cartridges.

Logical Device SpecificationsTable 4–2 lists and describes the Logical Device specifications included in the Data Networking cartridges.

Table 4–1 Device Interface Specifications


Data Networking Device Interface

Defines interfaces on CPEs and PEs. Child entity of a Data Networking Device or Virtual Data Networking Device entity



Place SpecificationsTable 4–3 lists and describes the Place specifications included in the Data Networking cartridges.

Place Configuration SpecificationsTable 4–4 lists and describes the Place Configuration specifications included in the Data Networking cartridges.

Role SpecificationsTable 4–5 lists and describes the Role specifications included in the Data Networking cartridges.

Table 4–2 Logical Device Specifications


Data Networking Device Creates logical devices that represent the customer premise equipment (CPE) and provider edge (PE) equipment

The Data Networking Device specification includes the following characteristic:

■ Management IP Address: Text field to enter the Management IP address

Virtual Data Networking Device

Creates logical devices that represent the CPE. Child entity of a Data Networking Device

The Virtual Data Networking Device specification includes the following characteristic:

■ Management IP Address: Text field to enter the Management IP address



Data Networking Site Defines customer sites. Can include site configurations based on the Data Networking Site Configuration specification

Table 4–4 Place Configuration Specifications


Data Networking Site Configuration

Provides the following configuration information pertaining to the data networking site:

■ Location Address: Physical location of the site

■ Site Termination: Contains the Customer Premise Equipment Interface and Transport Termination configuration items:

Customer Premise Equipment Interface: Enables you to assign the CPE interface used to connect to the provider edge interface

Transport Termination: Enables you to assign the MPLS L3 VPN termination site

■ Customer Premise Equipment: Enables you to assign the CPE logical device at the customer site

Rulesets

Data Networking Content 4-3

Service SpecificationsTable 4–6 lists and describes the Service specifications included in the Data Networking cartridges.

Service Configuration SpecificationsTable 4–7 lists and describes the Service Configuration specifications included in the Data Networking cartridges.

RulesetsThis section lists the rulesets and ruleset extension points included in the data networking cartridges. Rulesets run before, after, or instead of the method identified by the corresponding ruleset extension point. You can view the details of the rulesets and ruleset extension points by opening the cartridges in Design Studio.

Table 4–8 lists and describes the rulesets and ruleset extension points that are included in the data networking cartridges.



Ethernet Switch Defines an Ethernet switch that is used to join two LAN segments

IP Router Defines an IP router that routes data packets across destinations using the Internet Protocol (IP)

Customer Edge Device Defines the customer edge device that provides entry points into enterprise or service provider core networks

Table 4–6 Service Specifications


Data Networking Service Defines a generic data networking service

May include configurations based on the Data Networking Service Configuration specification

Table 4–7 Service Configuration Specifications


Data Networking Service Configuration

Contains configuration information pertaining to the Data Networking Service

Specifies customer sites and links the transport service to the Data Networking Service


■ Sites: Contains the Data Networking Site configuration item:

Data Network Site: Enables you to assign a Data Networking Site entity used in the service

■ Transport Services: Contains the Transport Service configuration item:

Transport Service: Enables you to assign a transport service, such as an MPLS L3 VPN service

■ Connectivity-List: Contains the Connectivity configuration item:

Connectivity: Enables you to assign a service trail, which is enabled in Oracle Communications Unified Inventory Management (UIM) by an external system

Rulesets


Table 4–8 Rulesets and Ruleset Extension Points

Ruleset/Ruleset Extension Point Functionality

APPROVE_DATA_NETWORKING_SERVICE_CONFIG

APPROVE_DATA_NETWORKING_SERVICE_CONFIG_EXT

This is an empty ruleset that enables another cartridge to readily override it.

The ruleset is called when you approve a service configuration, and it runs before the UIM approve service configuration logic.

AUTOMATE_DATA_NETWORKING_SERVICE_CONFIG

AUTOMATE_DATA_NETWORKING_SERVICE_CONFIG_EXT


The ruleset is called when you automate a service configuration, and it runs before any custom rulesets that may be in place to automate a service configuration.

CANCEL_DATA_NETWORKING_SERVICE_CONFIG

CANCEL_DATA_NETWORKING_SERVICE_CONFIG_EXT


The ruleset is called when you cancel a service configuration, and it runs before the UIM cancel service configuration logic.

COMPLETE_DATA_NETWORKING_SERVICE_CONFIG

COMPLETE_DATA_NETWORKING_SERVICE_CONFIG_EXT


The ruleset is called when you complete a service configuration, and it runs before the UIM complete service configuration logic.

VALIDATE_DATA_NETWORKING_SERVICE_CONFIG

VALIDATE_DATA_NETWORKING_SERVICE_CONFIG_EXT


The ruleset is called when you validate a service configuration, and it runs instead of the UIM service configuration validation logic.

5

Extending the MPLS L3 VPN Technology Pack 5-1

5Extending the MPLS L3 VPN Technology Pack

You can extend the MPLS L3 VPN Technology Pack to meet the business needs of your organization. This chapter describes the content included in the technology pack to facilitate extension.

See UIM Concepts, UIM Developer’s Guide and the Oracle Communications Design Studio online Help for general information about how you extend specifications, characteristics, and rulesets.

Extending Validation and Auto-Assignment CapabilitiesThe MPLS L3 VPN Technology Pack includes a number of stub rulesets that you can use to introduce new validation and auto-assignment capabilities.

Stub rulesets are blank by default. You can develop your own rulesets in separate cartridges and give them the same name as the stub. After you deploy the technology pack into Oracle Communications Unified Inventory Management (UIM), you deploy the cartridges with your custom rulesets, which replace the stub versions. See UIM Concepts and UIM Developer’s Guide for more information.

These are the stub rulesets included in the technology pack:

■ MPLSL3VPN_VALIDATE_NETWORK_CUSTOM. Enables you to add functionality to the standard validation logic for MPLS L3 VPN Network configurations provided by MPLSL3VPN_VALIDATE_NETWORK. Triggered when Validate is selected from the Actions menu in an MPLS L3 VPN Network configuration page.

■ MPLSL3VPN_VALIDATE_SERVICE_CUSTOM. Enables you to add functionality to the standard validation logic for MPLS L3 VPN service configurations provided by MPLSL3VPN_VALIDATE_SERVICE. Triggered when Validate is selected from the Actions menu in an MPLS L3 VPN Service configuration page.

■ MPLSL3VPN_VALIDATE_PLACE_CUSTOM. Enables you to add functionality to the standard validation logic for MPLS L3 VPN Termination configurations provided by MPLSL3VPN_VALIDATE_PLACE. Triggered when Validate is selected from the Actions menu in an MPLS L3 VPN Termination configuration page.

■ MPLSL3VPN_VALIDATE_VRF_CUSTOM. Enables you to add functionality to the standard validation logic for MPLS L3 VPN VRF configurations provided by

Important: To ensure that your extensions are upgradeable and supportable, you must follow the guidelines and policies described in UIM Concepts.

Extending Configuration Specifications with Stub Configuration Items


MPLSL3VPN_VALIDATE_VRF. Triggered when Validate is selected from the Actions menu in an MPLS L3 VPN VRF configuration page.

■ VRF_VALIDATE_VRF_CUSTOM. Enables you to add functionality to the standard validation logic for VRF-Lite configurations provided by VRF_VALIDATE_VRF. Triggered when Validate is selected from the Actions menu in a VRF-Lite configuration page.

■ MPLSL3VPN_ALLOCATE_ALL_NETWORK_CUSTOM. Enables you to implement auto-assignment for MPLS L3 VPN Network configurations. Triggered when Auto Assign is selected from the Related Pages menu in an MPLS L3 VPN Network configuration page.

■ MPLSL3VPN_ALLOCATE_ALL_SERVICE_CUSTOM. Enables you to implement auto-assignment for MPLS L3 VPN service configurations. Triggered when Auto Assign is selected from the Related Pages menu in an MPLS L3 VPN Service configuration page.

■ MPLSL3VPN_ALLOCATE_ALL_VRF_CUSTOM. Enables you to implement auto-assignment for MPLS L3 VPN VRF configurations. Triggered when Auto Assign is selected from the Related Pages menu in an MPLS L3 VPN VRF configuration page.

■ VRF_ALLOCATE_ALL_VRF_CUSTOM. Enables you to implement auto-assignment for VRF-Lite configurations. Triggered when Auto Assign is selected from the Related Pages menu in a VRF-Lite configuration page.

Extending Configuration Specifications with Stub Configuration ItemsStub configuration items have no content associated with them by default. You use them to add characteristics or specification options to configurations. You can associate characteristics or specification options to these stubs from separate cartridges, so you do not need to unseal a technology pack cartridge to extend it. See UIM Concepts and the Design Studio online Help for more information.

Extending the MPLS L3 VPN Termination ModelThe MPLS L3 VPN Termination Configuration specification includes one stub configuration item. Table 5–1 lists and describes this configuration item.

Extending the Extending the VRF-Lite ModelThe VRF-Lite Configuration specification includes one stub configuration item. Table 5–2 lists and describes the configuration item.

Table 5–1 Stub Configuration Item for the MPLS L3 VPN Termination Model

Stub Item Use

L3 QoS Used to support quality of service (QoS) standards. For example, you can include characteristics such as Committed Info Rate, Burst Size, or Excess Information Rate.

Table 5–2 Stub Configuration Item for VRF-Lite Configuration

Stub Item Use

L3 QoS Used to support quality of service (QoS) standards. For example, you can include characteristics such as Committed Info Rate, Burst Size, or Excess Information Rate.

6

MPLS L3 VPN Technology Pack Service Example 6-1

6MPLS L3 VPN Technology Pack ServiceExample

This chapter provides an example of configuring a service using the MPLS L3 VPN Technology Pack.

This example is for a Full Mesh VPN with three sites.

OverviewA service such as this example comprises two services that you create in Oracle Communications Unified Inventory Management (UIM):

■ A customer service that represents sites and represents devices that require connectivity. The customer service is modeled as an instance of the Data Networking Service specification. See "Creating the Customer View" for more information.

■ A transport service that represents the service provider’s implementation of that connectivity. The transport service is modeled as an instance of the MPLS L3 VPN Service specification.

After the customer and transport services have been created, you link them together to complete the overall service. See "Linking the Customer View to the Service Provider View" for more information.

AssumptionsInventory administration includes Data Networking Device and Data Networking Device Interface specifications for PE devices and CE devices.

For this example, we will assume that all the required PE and CE devices have been discovered and populated.

Creating the Customer ViewThe customer view includes the CPE and sites that are to be connected by the service-provider MPLS L3 VPN network. The customer service is an instance of the Data Networking Service specification provided in the technology pack. See

Note: This example is based on the use of the default specifications and characteristics supplied with the technology pack. Extending the technology pack may influence how you configure the service.

Creating the Customer View


Figure 1–2, "Data Networking Service Model" for an illustration of the specifications used to model a data networking service.

Creating the customer service involves the following steps:

■ Creating the Data Networking Service

■ Creating Customer Service Locations

■ Creating Customer Sites

Creating the Data Networking ServiceThe customer service is represented by an instance of the Data Networking Service specification. This specification has an accompanying configuration specification.

See Figure 1–2, "Data Networking Service Model" to view the relationships between the Data Networking Service specification and other specifications.

You create a configuration version based on this specification so that you can assign the customer sites that you create. Later, you will also assign a transport service to this service configuration. See "Linking the Customer View to the Service Provider View".

Complete the following steps to create and provision the customer service:

■ Create a service based on the Data Networking Service specification.

■ Specify a name, for example ACME Service, for the Data Networking service.

■ Add a configuration to the service. Only one specification (Data Networking Service Configuration) is available for this configuration.

Creating Customer Service LocationsThe technology pack includes a location-type Place specification called serviceLocation. You create entities based on this specification for the locations of customer sites. These locations are then assigned to customer site configurations. For this example, you need a serviceLocation entity for each of the three customer sites.

Creating Customer SitesYou create Place entities for the customer sites where the CPE devices are located. The technology pack includes a Data Networking Site specification and an accompanying configuration specification.

You create three Place entities, one for each customer site. For each site:

■ Create a Place entity of type Site based on the Data Networking Site specification.

■ Specify a name, for example New York, Miami, and Los Angeles.

■ Add a configuration version. Only one configuration specification (Data Networking Site Configuration) is available. See "Provisioning the Customer Sites" for information about assigning resources to the site configuration.

See Figure 1–3, "Data Networking Site Model" to view the relationships among the entities used to model data networking sites.

Provisioning the Customer SitesYou provision the customer sites, New York, Miami, and Los Angeles, that you created by specifying their location, site termination, and CPE devices.

For each site configuration:

Creating the Service Provider View


■ Add a Location Address configuration item and assign one of the service locations you created previously.

■ Add a Customer Premise Equipment configuration item. Assign a Data Networking Device entity to this item, selecting the logical device entity that is appropriate for each site.

■ Add a Site Termination configuration item. To this configuration item, add a Customer Premise Equipment Interface configuration item and assign a logical device interface that is provided by the logical device you selected as the CPE.

Do not assign a resource to the Transport Termination configuration item at this time. You will assign this resource after you have created the transport service. See "Linking the Customer View to the Service Provider View" for more information.

■ In the Data Networking Service Configuration specification, under Sites, create three configuration items of type Data Networking Site.

■ For the first configuration item, assign New York; for the second configuration item, assign Miami; for the third configuration item, assign Los Angeles.

Creating the Service Provider ViewThe service provider view includes the creation of route distinguishers, route targets, IP addresses, VRFs, VPN networks, terminations, and the MPLS L3 VPN service.

Creating the Route DistinguishersThe route distinguisher is a six-byte number that is prepended to a standard IPv4 address to create a VPN-IPv4 address that is unique across the core network. PEs use route distinguishers to ensure that traffic is routed to the proper CE. You must create a pool of route distinguishers so that they can be assigned to VRF configurations.

To create a route distinguisher, do the following:

■ Create an Inventory Group entity of type Route Distinguisher Type 0 Group.

■ Specify a name for the route distinguisher inventory group, for example RD 0 Group.

■ In the Initial Route Distinguisher Group Name list, specify the range of route distinguishers you want to create, such as 1:1-1:10.

Custom Network Addresses based on the Route Distinguisher specification are created automatically. Their names correspond to the range you entered in the Initial Route Distinguisher Group Name list.

■ Verify whether the custom network address and the route distinguisher are created properly.

Creating Route TargetsThe route target represents a route target scoped to a Route Target Group. You must create a pool of route targets so that they can be assigned to VRF configurations.

To create a route target, do the following:

Note: You must not edit the route distinguishers that are automatically generated because the inventory group, Route Distinguisher Type 0 Group, controls these route distinguishers.



■ Create an Inventory Group entity of type Route Target Type 0 Group.

■ Specify a name for the route target inventory group, for example RT 0 Group.

■ In the Initial Route Target Group Name list, specify the range of route targets you want to create, such as 2:1 - 2:10.

Custom network addresses based on the Route Target specification are created automatically. Their names correspond to the range you entered in the Initial Route Target Group Name list.

You must generate a pool of route targets that would be consumed.

■ Verify whether the custom network address and the route target is created properly.

Creating IP AddressesAn IP address is a numerical representation of the computers involved in a network that use the IP for communication. IP addresses are stored as binary numbers and are usually displayed in human-readable notations. An IP address in the MPLS L3 VPN network represents an IPv4 address or an IPv6 address.

You must create three IP addresses. For each IP address:

■ Create the Custom Network Address specification, IPv4 IP Address.

■ Specify a value for the IPv4 IP address, such as 192.168.1.1/30.

■ Specify a prefix for the IPv4 IP address, such as 192.168.1.1.

■ Specify a CIDR value for the IPv4 IP address, such as 30.

■ In addition to the IPv4 IP Address that you created, you must create two more IP addresses: 192.168.1.5/30 and 192.168.1.9/30.

Creating VRFsA VRF defines a VRF instance in the MPLS L3 VPN network.

You must create three VRF instances, for example VRF1, VRF2, and VRF3. Then, associate VRF1, VRF2, and VRF3 to PE1, PE2, and PE3 respectively. The following procedure describes the steps to create VRF1. You must repeat these steps for VRF2 and VRF3:

■ Create the Logical Device specification, VRF.

■ Specify a name for the VRF instance, for example VRF1.

■ Select the route distinguisher inventory group that you created, such as RD 0 Group.

■ Associate the VRF to PE.

– Search for PE1 and associate.

■ Add a configuration. Only one configuration specification is available, MPLS VPN VRF Configuration.

Note: You must not edit the route targets that are automatically generated because the inventory group, Route Target Type 0 Group, controls these route targets.



■ UIM automatically assigns an unassigned route distinguisher from the group that you selected in the Preferred Route Distinguisher Group list. Auto Assignment occurs when the you choose the Auto-Assign menu item from the Related Pages menu.

Creating the VPN NetworkA VPN network represents a topology segment for a larger VPN network. A VPN network is either a Full Mesh topology or Hub and Spoke topology. Each VPN network can be divided into a set of Full Mesh and Hub and Spoke network segments.

To create a VPN network:

■ Create the Network specification, MPLS L3 VPN Network.

■ Specify a name for the Network specification, for example Network1.

■ In the Preferred Route Target Group list, select the route target inventory group that you created, such as RT 0 Group.

■ Add a configuration to the MPLS L3 VPN Network service. Only one configuration specification (MPLS L3 VPN Network) is available.

■ Add a route target and three VRF configuration items, for example VRF1, VRF2, and VRF3.

■ Set VPN Topology to Full Mesh.

■ Select the first, second, and third VRF configuration items and assign objects VRF1, VRF2, and VRF3 respectively, and then set the Membership Type characteristic to Full Mesh Member.

■ Assign the unassigned route target from the group that you selected in the Preferred Route Target Group list.

Creating the TerminationsThe MPLS L3 VPN termination is the service-provider side of the VRF attachment circuit. It can include configurations based on the MPLS L3 VPN Termination Configuration specification.

You must create three Terminations, for example Termination 1, Termination 2, and Termination 3. The following procedure describes the steps to create Termination 1. You must repeat these steps for Termination 2 and Termination 3:

■ Create the Place specification, MPLS L3 VPN Termination.

■ Specify a name for the Place specification, for example Termination 1.

■ Add a configuration, MPLS L3 VPN Termination Configuration, to the termination.

■ Assign VRF1 object of the type VRF.

■ Add a Provider Edge Interface configuration item.

■ Assign a PE Interface object of type Data Networking Device Interface that represents the PE customer-facing interface.

This example assumes that the PE and its interfaces are already inventoried.

■ Assign an IP Address object of type IPv4 IP Address.

Linking the Customer View to the Service Provider View


Creating the MPLS L3 VPN ServiceThe MPLS L3 VPN service includes VPN networks and VPN terminations.

You create an entity based on the MPLS L3 VPN Service specification to represent the transport service. The specification is accompanied by the configuration specification, MPLS L3 VPN Configuration.

To create a service:

■ Create the Service specification, MPLS L3 VPN Service.

■ Specify a name for the Service specification, for example ACME VPN.

■ Add a configuration, MPLS L3 VPN Configuration, to the service.

■ Add the configuration items, MPLS L3 VPN Network and VPN ID.

■ Under the VPN Transport Terminations folder, add three MPLS VPN Termination configuration items.

■ Select the first, second, and third MPLS VPN Termination configuration items and assign objects Termination 1, Termination 2, and Termination 3 respectively.

■ Assign object MPLS L3 VPN Network.

■ Assign the VPN ID.

Until now, we have created the service provider view of the service request; we created a transport service instance and attached three terminations to that service. In each of the terminations, we captured information modeling the PE interface, which is customer facing. We also captured information about the VRF termination. The service is not complete until we update the customer view of the service, which references this instance.

Linking the Customer View to the Service Provider ViewAfter the transport service is complete, you can return to the customer view to link the two. Linking the views includes:

■ Assigning the Transport Service

■ Assigning Terminations

When these two assignments have been made, the entire MPLS L3 VPN service is complete.

Assigning the Transport ServiceYou assign an MPLS L3 VPN service instance to the customer service configuration. This relationship defines the service that is used to enable connectivity between the three customer sites.

In the customer service configuration:

■ Add a Transport Service configuration item to the Transport Services configuration item. Assign the MPLS L3 VPN Service instance you created previously.

Assigning TerminationsYou assign an MPLS L3 VPN termination to each customer site. This relationship defines which service-provider termination is used to connect the customer site to the MPLS L3 VPN network.



For each customer site:

■ In the site configuration, assign the appropriate MPLS L3 VPN termination to the Transport Termination configuration item. This configuration item was left undefined when you provisioned the site originally. See "Provisioning the Customer Sites" for more information.

Now we have created the customer view of the service as well as the service provider view of the service; we created a data networking service instance composed of sites, which represents what the end user considers as the service. We also created a transport service composed of networks and terminations, which represents what the service provider considers as the implementation of interconnecting the sites together through terminations.



Oracle® Communications Unified Inventory ManagementThe MPLS L3 VPN Technology Pack enables you to model instances of an MPLS L3 VPN service in Oracle Communications Unified Inventory

Documents