Oracle Communications Unified Inventory Management

Transcription

1 Oracle Communications Unified Inventory Management MPLS L3 VPN Technology Pack Implementation Guide Release E January 2013

2 Oracle Communications Unified Inventory Management MPLS L3 VPN Technology Pack Implementation Guide, Release E 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.

3 Contents Preface... v Audience... Related Documentation... Documentation Accessibility... v vi vi 1 MPLS L3 VPN Technology Pack Overview About the MPLS L3 VPN Technology Pack Contents of the MPLS L3 VPN Technology Pack MPLS L3 VPN Technology Pack Javadoc MPLS L3 VPN Technology Pack Super JAR File MPLS L3 VPN Technology Pack Individual Jar Files MPLS L3 VPN Technology Pack ZIP Archive Files Address and Location Cartridges Data Networking Cartridges MPLS L3 VPN Cartridges Deploying the MPLS L3 VPN Technology Pack Opening the Technology Pack in Design Studio Address, Location, and Party Content Entity Specifications Party Specifications Place Specifications Role Specifications MPLS L3 VPN Content Entity Specifications Custom Network Address Specifications Inventory Group Specifications Logical Device Specifications Logical Device Configuration Specifications Network Specifications Network Configuration Specifications Network Node Specifications Place Specifications Place Configuration Specifications iii

4 Role Specifications Sequence Specifications Service Specifications Service Configuration Specifications Rulesets Included in the Technology Pack Data Networking Content Entity Specifications Device Interface Specifications Logical Device Specifications Place Specifications Place Configuration Specifications Role Specifications Service Specifications Service Configuration Specifications Rulesets Extending the MPLS L3 VPN Technology Pack Extending Validation and Auto-Assignment Capabilities Extending Configuration Specifications with Stub Configuration Items Extending the MPLS L3 VPN Termination Model Extending the Extending the VRF-Lite Model MPLS L3 VPN Technology Pack Service Example Overview Assumptions Creating the Customer View Creating the Data Networking Service Creating Customer Service Locations Creating Customer Sites Provisioning the Customer Sites Creating the Service Provider View Creating the Route Distinguishers Creating Route Targets Creating IP Addresses Creating VRFs Creating the VPN Network Creating the Terminations Creating the MPLS L3 VPN Service Linking the Customer View to the Service Provider View Assigning the Transport Service Assigning Terminations iv

5 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 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 Audience This 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. v

6 Related Documentation For 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 Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired. vi

7 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 Pack The 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. MPLS L3 VPN Technology Pack Overview 1-1

8 About the MPLS L3 VPN Technology Pack 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. 1-2 UIM MPLS L3 VPN Technology Pack Implementation Guide

9 About the MPLS L3 VPN Technology Pack Figure 1 2 Data Networking Service Model Figure 1 3 illustrates the specifications used to model a data networking site. MPLS L3 VPN Technology Pack Overview 1-3

10 About the MPLS L3 VPN Technology Pack Figure 1 3 Data Networking Site Model Figure 1 4 depicts the specifications used to model an MPLS L3 VPN network. 1-4 UIM MPLS L3 VPN Technology Pack Implementation Guide

11 About the MPLS L3 VPN Technology Pack 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 MPLS L3 VPN Technology Pack Overview 1-5

12 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 Pack Table 1 1 describes the contents of the MPLS L3 VPN Technology Pack, which is delivered as a ZIP file. 1-6 UIM MPLS L3 VPN Technology Pack Implementation Guide

13 Contents of the MPLS L3 VPN Technology Pack Table 1 1 Item Javadoc Super JAR Archive File MPLS L3 VPN Technology Pack ZIP File Contents Components of the Super JAR Archive File Cartridge Project ZIP Files and Sample Code Directory doc/javadocfortechpacks See "MPLS L3 VPN Technology Pack Javadoc" for more information. deploy/superjartodeploy See "MPLS L3 VPN Technology Pack Super JAR File" for more information. deploy/individualjarsforsuperjar See "MPLS L3 VPN Technology Pack Individual Jar Files" for more information. designstudio/cartridgezips See "MPLS L3 VPN Technology Pack ZIP Archive Files" for more information. MPLS L3 VPN Technology Pack Javadoc 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 MPLS L3 VPN Technology Pack, including information that summarizes classes, methods, and parameters. MPLS L3 VPN Technology Pack Super JAR File The 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 Files 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. 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 MPLS L3 VPN Technology Pack Overview 1-7

14 Contents of the MPLS L3 VPN Technology Pack 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 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 MPLS L3 VPN Technology Pack ZIP Archive Files The 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 Cartridges The 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 1-8 UIM MPLS L3 VPN Technology Pack Implementation Guide

15 Opening the Technology Pack in Design Studio Party cartridge: ora_uim_party_customer Data Networking Cartridges 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 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 Cartridges The 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 Pack Oracle 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. 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. 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 Studio In 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. MPLS L3 VPN Technology Pack Overview 1-9

16 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 UIM MPLS L3 VPN Technology Pack Implementation Guide

17 2 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 Specifications Party Specifications This 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. Table 2 1 lists and describes the Party specifications included in the address, location, and party cartridges. Table 2 1 Party Specifications Specification Organization Individual Models an organization such as a business or a government agency; can be assigned the Customer role Models a single individual, such as a subscriber; can be assigned the Customer role Place Specifications Table 2 2 lists and describes the Place specifications included in the address and location cartridges. Address, Location, and Party Content 2-1

18 Entity Specifications Table 2 2 Specification canadaaddress canadacity canadaprovincecode country norwayaddress norwaycity saudiarabiaaddress saudiarabiacity servicelocation ukaddress Place Specifications 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 Location specification used to populate the City field in Canadian addresses Location specification used to populate the Province field in Canadian addresses Location specification for countries Postal address of the subscriber in Norway The norwayaddress 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 Norway city where the subscriber is located Country: Name of the country where the subscriber is located postalcode: Postal code of the Norway state where the subscriber is located; five characters long Location specification used to populate the City field in Norwegian addresses Postal address of the subscriber in Saudi Arabia The saudiarabiaaddress 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 Saudi city where the subscriber is located Country: Name of the country where the subscriber is located postalcode: Postal code of the Saudi state where the subscriber is located; seven characters long Location specification used to populate the City field in Saudi addresses Location specification used to define where a service is delivered Postal address of the subscriber in the UK The ukaddress 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 UK city where the subscriber is located Country: Name of the country where the subscriber is located postalcode: Postal code of the UK state where the subscriber is located; seven characters long 2-2 UIM MPLS L3 VPN Technology Pack Implementation Guide

19 Entity Specifications Table 2 2 Specification ukcity usaddress uscity usstatecode (Cont.) Place Specifications Location specification used to populate the City field in UK addresses Postal address of the subscriber in the US The usaddress 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 Country: Name of the country where the subscriber is located 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 Location specification used to populate the City field in US addresses Child of usstate Location specification used to populate the State field in US addresses Parent of uscity. Role Specifications Table 2 3 Specification Customer Subscriber Table 2 3 lists and describes the Role specifications included in the address, location, and party cartridges. Role Specifications Designates an Organization or Individual entity as a customer Designates an Organization or Individual entity as a subscriber Address, Location, and Party Content 2-3

20 Entity Specifications 2-4 UIM MPLS L3 VPN Technology Pack Implementation Guide

21 3 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 Specifications This 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 Specifications Table 3 1 lists and describes the Custom Network Address specifications included in the MPLS L3 VPN-specific cartridges of the technology pack. MPLS L3 VPN Content 3-1

22 Entity Specifications Table 3 1 Specification Route Distinguisher Route Target Custom Network Address Specifications 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. 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. 3-2 UIM MPLS L3 VPN Technology Pack Implementation Guide

23 Entity Specifications Table 3 1 (Cont.) Custom Network Address Specifications Specification 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 Inventory Group Specifications Table 3 2 Specification Route Distinguisher Type 0 Group Route Distinguisher Type 1 Group Route Distinguisher Type 2 Group Table 3 2 lists and describes the Inventory Group specifications included in the MPLS L3 VPN-specific cartridges of the technology pack. Inventory Group Specifications 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. Represents a pool or group of Type 1 route distinguishers Creating an inventory group based on this specification triggers the ADD_ ROUTEDISTINGUISHER1_GROUP ruleset, which creates route distinguishers based on the values you enter in the Initial Route Distinguisher Range field. The Route Distinguisher Type 1 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 : :3, :5 will create route distinguisher list of :1, :2, :3, and :5. This characteristic is a validated parameter. Represents a pool or group of Type 2 route distinguishers Creating an inventory group based on this specification triggers the ADD_ ROUTEDISTINGUISHER2_GROUP ruleset, which creates route distinguishers based on the values you enter in the Initial Route Distinguisher Range field. The Route Distinguisher Type 2 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. MPLS L3 VPN Content 3-3

24 Entity Specifications Table 3 2 Specification Route Target Type 0 Group Route Target Type 1 Group Route Target Type 2 Group (Cont.) Inventory Group Specifications 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. Represents a pool or group of Type 1 route targets Creating an inventory group based on this specification triggers the ADD_ ROUTETARGET1_GROUP ruleset, which creates route targets based on the values you enter in the Initial Route Target Range field. The Route Target Type 1 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 : :3, :5 will create route target list of :1, :2, :3, and :5. This characteristic is a validated parameter. Represents a pool or group of Type 2 route targets Creating an inventory group based on this specification triggers the ADD_ ROUTETARGET2_GROUP ruleset, which creates route targets based on the values you enter in the Initial Route Target Range field. The Route Target Type 2 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. Logical Device Specifications Table 3 3 Specification DHCP Server TFTP Server VRF Table 3 3 lists and describes the Logical Device specifications included in the MPLS L3 VPN-specific cartridges of the technology pack. Logical Device Specifications Creates logical devices that represent DHCP servers Creates logical devices that represent TFTP servers 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. Logical Device Configuration Specifications The 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. 3-4 UIM MPLS L3 VPN Technology Pack Implementation Guide

25 Entity Specifications Table 3 4 Configuration Item MPLS VPN VRF Configuration Route Distinguisher Routing Protocols 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: MPLS VPN VRF Configuration Specification Child Configuration Item Top-level item that includes parameters for configuring VRF details such as name and route limits. Enables you to assign a Route Distinguisher entity used in the VRF. 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. MPLS L3 VPN Content 3-5

26 Entity Specifications Table 3 4 Configuration Item (Cont.) MPLS VPN VRF Configuration Specification Child Configuration Item Routing Protocols OSPF Defines some device-level OSPF configuration and also contains other configuration items related to OSPF: Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From RIP: Defines metrics for importing routes from RIP 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 BGP-VPN: Defines metrics for importing routes from BGP-VPN 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. 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. 3-6 UIM MPLS L3 VPN Technology Pack Implementation Guide

27 Entity Specifications Table 3 4 Configuration Item (Cont.) MPLS VPN VRF Configuration Specification Child Configuration Item Routing Protocols EIGRP Defines some device-level EIGRP configuration and also contains other configuration items related to EIGRP. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From BGP: Defines metrics for importing routes from BGP tables into this protocols table. From OSPF: Defines metrics for importing routes from OSPF tables into this protocols table. From RIP: Defines metrics for importing routes from RIP tables into this protocols table. From Static Routes: Defines metrics for importing routes derived from static route entries into this protocols table. From Direct Connected: Defines metrics for importing routes derived from connected interfaces into this protocols table. From BGP-VPN: Defines metrics for importing routes from BGP-VPN tables into this protocols table. MPLS L3 VPN Content 3-7

28 Entity Specifications Table 3 4 Configuration Item (Cont.) MPLS VPN VRF Configuration Specification Child Configuration Item Routing Protocols BGP Defines some device-level BGP configuration and also contains other configuration items related to BGP. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From RIP: Defines metrics for importing routes from RIP tables into this protocols table. From OSPF: Defines metrics for importing routes from OSPF tables into this protocols table. From BGP-VPN: Defines metrics for importing routes from BGP-VPN tables into this protocols table. From EIGRP: Defines metrics for importing routes from EIGRP 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. 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. IPV6 Static Route: Defines an IPv6 Static Route. 3-8 UIM MPLS L3 VPN Technology Pack Implementation Guide

29 Entity Specifications Table 3 4 Configuration Item (Cont.) MPLS VPN VRF Configuration Specification Child Configuration Item Routing Protocols BGP-VPN Defines some device-level BGP-VPN configuration and also contains other configuration items related to BGP-VPN. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From BGP: Defines metrics for importing routes from BGP tables into this protocols table. From RIP: Defines metrics for importing routes from RIP 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 Static Routes: Defines metrics for importing routes derived from static route entries into this protocols table. From Direct Connected: Defines metrics for importing routes derived from connected interfaces into this protocols table. Table 3 5 Configuration Item VRF-Lite Configuration Routing Protocols VRF-Lite Configuration Specification Child Configuration Item 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. 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. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported 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 BGP-VPN: Defines metrics for importing routes from BGP-VPN 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. MPLS L3 VPN Content 3-9

30 Entity Specifications Table 3 5 Configuration Item (Cont.) VRF-Lite Configuration Specification Child Configuration Item Routing Protocols OSPF Defines some device-level OSPF configuration and also contains other configuration items related to OSPF. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From BGP: Defines metrics for importing routes from BGP tables into this protocols table. From RIP: Defines metrics for importing routes from RIP tables into this protocols table. From EIGRP: Defines metrics for importing routes from EIGRP tables into this protocols table. From BGP-VPN: Defines metrics for importing routes from BGP-VPN 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. 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. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From RIP: Defines metrics for importing routes from RIP tables into this protocols table. From OSPF: Defines metrics for importing routes from OSPF tables into this protocols table. From BGP: Defines metrics for importing routes from BGP tables into this protocols table. From BGP-VPN: Defines metrics for importing routes from BGP-VPN 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 UIM MPLS L3 VPN Technology Pack Implementation Guide

31 Entity Specifications Table 3 5 Configuration Item (Cont.) VRF-Lite Configuration Specification Child Configuration Item Routing Protocols BGP Defines some device-level BGP configurations and also contains other configuration items related to BGP. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From RIP: Defines metrics for importing routes from RIP 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-VPN: Defines metrics for importing routes from BGP-VPN 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. 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. IPV6 Static Route: Defines an IPv6 Static Route. MPLS L3 VPN Content 3-11

32 Entity Specifications Table 3 5 Configuration Item Routing Protocols BGP-VPN Defines some device-level BGP-VPN configuration and also contains other configuration items related to BGP-VPN. Redistribution: Contains redistribution configuration items related to various routing protocols routing table entries that are imported into this protocols table. From BGP: Defines metrics for importing routes from BGP tables into this protocols table. From RIP: Defines metrics for importing routes from RIP tables into this protocols table. From EIGRP: Defines metrics for importing routes from EIGRP tables into this protocols table. From OSPF: Defines metrics for importing routes from OSPF 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. VRF Interface (Cont.) VRF-Lite Configuration Specification Child Configuration Item 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 UIM MPLS L3 VPN Technology Pack Implementation Guide

33 Entity Specifications Table 3 5 Configuration Item 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. Static Routes: Contains static route configuration items. 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 (Cont.) VRF-Lite Configuration Specification Child Configuration Item Enables you to assign a Route Distinguisher entity used in the VRF. Network Specifications Table 3 6 lists and describes the Network specifications included in the MPLS L3 VPN-specific cartridges of the technology pack. MPLS L3 VPN Content 3-13