Metro Ethernet Technology Pack Implementation Guide … · Oracle® Communications Unified...

Oracle® Communications Unified Inventory ManagementMetro Ethernet Technology Pack Implementation Guide

Release 7.2

E25334-01

April 2012

Oracle Communications Unified Inventory Management Metro Ethernet Technology Pack Implementation Guide, Release 7.2

E25334-01

Copyright © 2009, 2012, 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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....................................................................................................................................................... vDocumentation Accessibility ..................................................................................................................... viRelated Documentation.............................................................................................................................. vi

1 Metro Ethernet Technology Pack Overview

About the Metro Ethernet Technology Pack ....................................................................................... 1-1Metro Ethernet Service Topologies ................................................................................................. 1-6

Contents of the Metro Ethernet Technology Pack ............................................................................. 1-6Metro Ethernet Technology Pack Javadoc...................................................................................... 1-7Metro Ethernet Technology Pack Super JAR File.......................................................................... 1-7Metro Ethernet Technology Pack Individual Jar Files.................................................................. 1-7Metro Ethernet Technology Pack ZIP Archive Files..................................................................... 1-7

Address, Location, and Party Cartridges ................................................................................ 1-8Data Networking Cartridges..................................................................................................... 1-8Metro Ethernet Cartridges......................................................................................................... 1-8

Deploying the Metro Ethernet Technology Pack ............................................................................... 1-8Opening the Technology Pack in Design Studio ............................................................................... 1-9Enabling Debugging of Validation and Assignment Rules ............................................................ 1-9

2 Address, Location, and Party Content

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

3 Data Networking Content

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

iv

4 Metro Ethernet Content

Entity Specifications ................................................................................................................................ 4-1Custom Network Address Specifications....................................................................................... 4-1Inventory Group Specifications ....................................................................................................... 4-2Involvement Specifications............................................................................................................... 4-3Network Edge Specifications ........................................................................................................... 4-3Network Node Specifications........................................................................................................... 4-3Network Specifications...................................................................................................................... 4-4Pipe Specifications ............................................................................................................................. 4-4Pipe Termination Point Specifications ............................................................................................ 4-4Place Specifications ............................................................................................................................ 4-4Place Configuration Specifications .................................................................................................. 4-4Role Specifications ............................................................................................................................. 4-5Service Specifications......................................................................................................................... 4-6Service Configuration Specifications............................................................................................... 4-7

Rulesets Included in the Technology Pack.......................................................................................... 4-7

5 Extending the Metro Ethernet Technology Pack

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

Extending the Ethernet Termination Model .................................................................................. 5-2Extending the Ethernet Service Configurations ............................................................................ 5-2

6 Metro Ethernet Technology Pack Service Example

Overview .................................................................................................................................................... 6-1Assumptions.............................................................................................................................................. 6-1Creating the Customer Service .............................................................................................................. 6-2

Creating Customer Devices and Interfaces .................................................................................... 6-2Creating Customer Service Locations ............................................................................................. 6-2Creating Customer Sites.................................................................................................................... 6-2

Provisioning the Customer Sites............................................................................................... 6-2Creating the Data Networking Service ........................................................................................... 6-3

Creating the Transport Service .............................................................................................................. 6-4Creating the EVC Domain and Resources...................................................................................... 6-4Creating the EVC Map Service......................................................................................................... 6-5Creating the Ethernet Termination Sites......................................................................................... 6-5

Assigning PE Interfaces and Assigning the UNI-N Role ..................................................... 6-6Assigning the EVC Map Service ............................................................................................... 6-7

Creating the Metro Ethernet Service ............................................................................................... 6-7Assigning the Terminations ...................................................................................................... 6-8Assigning and Configuring the EVC Resource ...................................................................... 6-8Associating the UNI EVC Resource to Termination Sites..................................................... 6-9Validating the Metro Ethernet Service.................................................................................. 6-10

Linking the Customer and Transport Services ................................................................................ 6-10Assigning the Transport Service ................................................................................................... 6-11Assigning Terminations ................................................................................................................. 6-11

v

Preface

Oracle Communications Unified Inventory Management (UIM) technology packs provide support for specific technology domains and a base for project-specific adaptation. Wherever possible, technology packs include elements and business logic based on relevant industry standards. The use of industry standards provides a set of elements and business logic that you can use with a minimal amount of customization.

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 Metro Ethernet Technology Pack provides business entities and behaviors required by providers of data networking services using Metro Ethernet technology, as standardized by the Metro Ethernet Forum. This includes models for Ethernet Private Line and Virtual Private Line services, Ethernet Sites and logic for VLAN management.

This guide contains the following information about the Metro Ethernet Technology Pack:

■ Background and introductory information about Metro Ethernet technology and the technology pack

■ Contents of the technology pack

■ Instructions for configuring a Metro Ethernet service

■ Example implementation scenario

■ Extension points

AudienceThis document is intended for business analysts and the following groups of people who design and implement a Metro Ethernet 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 Metro Ethernet technology and UIM.

vi

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.

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

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

■ UIM Installation Guide: Describes the requirements and procedures for installing UIM.

■ UIM Migration Guide: Provides information about migrating from previous releases of UIM to the current release.

■ UIM System Administrator’s Guide: Describes maintenance and administrative tasks such as managing user security.

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

■ UIM Model Overview: Describes the UIM model entities and data elements, and explains patterns that are common across all entities.

■ UIM Base Cartridges Guide: Provides descriptions of entities included in base cartridges. These entities are used for all technology domains. Examples include telephone numbers, units of measure, and base rulesets.

■ 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.

1

Metro Ethernet Technology Pack Overview 1-1

1Metro Ethernet Technology Pack Overview

This chapter provides an overview of the Metro Ethernet Technology Pack. The chapter also provides deployment information for the technology pack.

About the Metro Ethernet Technology PackThe Metro Ethernet Technology Pack enables you to model instances of Port-based and VLAN-based Metro Ethernet services in UIM.

Metro Ethernet is a networking technology often used to connect customer networks. Because it is based on the Ethernet standard, Metro Ethernet offers lower cost and simpler implementation than other networking technologies of equivalent bandwidth. Figure 1–1 displays a simplified view of a point-to-point Metro Ethernet service.

Figure 1–1 Metro Ethernet Service Overview

The two customer sites are connected by means of a Metro Ethernet network (MEN) maintained by a service provider. A CPE (Customer Premise Equipment) device in each customer site is defined as the customer-side interface to the MEN. A UNI (User Network Interface) is defined as the dividing line between each customer site and the

About the Metro Ethernet Technology Pack

1-2 UIM Metro Ethernet Technology Pack Implementation Guide

MEN. Each UNI is dedicated to a single customer site. An interface on a PE (Provider Edge) device is designated as the UNI.

Within the MEN, an EVC (Ethernet Virtual Circuit) provides connectivity between the UNIs. The EVC ensures that the UNIs communicate only with each other and with no other devices in the MEN.

The Metro Ethernet Technology Pack models Metro Ethernet as a technology-specific implementation of generic data networking functionality. The generic data networking specifications in the technology pack enable you to model a high-level, end-to-end view of the service from the customer perspective.

Figure 1–2 illustrates the specifications used to model a data networking service.

Figure 1–2 Data Networking Service Model

Figure 1–3 illustrates the specifications used to model a data networking site. The model includes the site location, the CPE, transport termination, and the CPE interface.



Figure 1–3 Data Networking Site Model

In addition to these generic data networking specifications, the technology pack includes specifications that are unique to Metro Ethernet. These specifications build on the generic data network services to provide a model for data transport across a Metro Ethernet network. See "Metro Ethernet Service Topologies" for more information.

The Metro Ethernet Technology Pack service model aligns with the definition of Ethernet services published in Phase 2 of Releases 6.1 and 10.1 of the technical specifications by the Metro Ethernet Forum (MEF). You can download these specifications from the MEF website:

http://metroethernetforum.org

Figure 1–4 depicts the specifications used to model a Metro Ethernet service. The technology pack automates the assignment of EVCs and VLANs by using inventory groups to create domains from which resources are selected.



Figure 1–4 Metro Ethernet Service Model

Figure 1–5 illustrates the specifications used to model a Metro Ethernet network.



Figure 1–5 Metro Ethernet Service Network Model

Figure 1–6, "Metro Ethernet Termination Model" illustrates the specifications used to model Metro Ethernet termination. Note that UNI-N parameters are modeled as characteristics of a role associated with a device interface.

Figure 1–6 Metro Ethernet Termination Model

Contents of the Metro Ethernet Technology Pack


Metro Ethernet Service TopologiesThe Metro Ethernet Technology Pack models the Port-based and VLAN-based service types that may be deployed in the following topologies:

■ Port-based services:

– Ethernet Private Line (EP-Line)

– Ethernet Private LAN (EP-LAN)

– Ethernet Private tree (EP-Tree)

■ VLAN-based services:

– Ethernet Virtual Private Line (EVP-Line)

– Ethernet Virtual Private LAN (EVP-LAN)

– Ethernet Virtual Private Tree (EVP-Tree)

Table 1–1 depicts the Metro Ethernet services supported by the Metro Ethernet Technology Pack.

Contents of the Metro Ethernet Technology PackThe Metro Ethernet Technology Pack is delivered as a ZIP file that contains the following items:

Table 1–1 Metro Ethernet Services

Service Type Port-Based (All-to-One Bundling) VLAN-Based (Service Multiplexed)

E-Line (Point-to-Point EVC) Ethernet Private Line (EP-Line) Ethernet Virtual Private Line (EVP-Line)

E-LAN (Multipoint-to-Multipoint EVC)

Ethernet Private LAN (EP-LAN) Ethernet Virtual Private LAN (EVP-LAN)

E-Tree (Rooted Multipoint EVC) Ethernet Private Tree (EP-Tree) Ethernet Virtual Private Tree (EVP-Tree)

Table 1–2 Metro Ethernet Technology Pack ZIP File Contents

Item Directory

Javadoc doc/javadocForTechPacks

See "Metro Ethernet Technology Pack Javadoc" for more information.

Super JAR Archive File deploy/superJarToDeploy

See "Metro Ethernet Technology Pack Super JAR File" for more information.

Components of the Super JAR Archive File

deploy/individualJarsForSuperJar

See "Metro Ethernet Technology Pack Individual Jar Files" for more information.

Cartridge Project ZIP Files and Sample Code

designStudio/cartridgeZips

See "Metro Ethernet Technology Pack ZIP Archive Files" for more information.

Contents of the Metro Ethernet Technology Pack


Metro Ethernet Technology Pack JavadocFrom the javadocForTechPacks directory, double-click index.html to access the Javadoc provided with the Metro Ethernet Technology Pack, including information that summarizes classes, methods, and parameters.

Metro Ethernet Technology Pack Super JAR FileThe Metro Ethernet 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 System Administrator's Guide for more information about the Cartridge Deployer Tool.

Metro Ethernet 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 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

ora_uim_data_networking_service_cartproj-*.jar

ora_uim_number_group_management_cartproj-*.jar

ora_uim_vlanmgmt_cartproj-*.jar

ora_uim_ethernet_cartproj-*.jar

Metro Ethernet Technology Pack ZIP Archive FilesThe Metro Ethernet Technology Pack comprises a number of cartridges that can be divided into three broad categories:

■ Address, Location, and Party Cartridges

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:

Deploying the Metro Ethernet Technology Pack


■ Data Networking Cartridges

■ Metro Ethernet Cartridges

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

Address, Location, and Party CartridgesThe address, location, and party cartridges include entities that are used by data networking and Metro Ethernet entities to define places and people in the network. There are separate address cartridges for several different cartridges as well as generic service location and address cartridges. The country-specific cartridges provide similar capabilities with minor variations based on local standards.

The address, location, and party cartridges are:

■ Address cartridge: ora_uim_address

■ Canada address cartridge: ora_uim_canada_address

■ Norway address cartridge: ora_uim_norway_address

■ Saudi Arabia address cartridge: ora_uim_saudi_arabia_address

■ Service location cartridge: ora_uim_service_location

■ United Kingdom address cartridge: ora_uk_address

■ United States address cartridge: ora_uim_us_address

■ 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

Metro Ethernet CartridgesThe Metro Ethernet cartridges model the capabilities specific to Metro Ethernet technology. See "Metro Ethernet Content" for more information.

The Metro Ethernet cartridges are:

■ Number group cartridge: ora_uim_number_group_management

■ VLAN resource cartridge: ora_uim_vlanmgmt

■ Ethernet cartridge: ora_uim_ethernet

Deploying the Metro Ethernet Technology PackOracle recommends that you use the Cartridge Deployer Tool to deploy the Metro Ethernet Technology Pack super JAR archive file to a UIM run-time environment. Deploying the technology pack with the Cartridge Deployer Tool ensures that all

Enabling Debugging of Validation and Assignment Rules


cartridges and dependencies are deployed in the proper order. See UIM System Administrator's 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 System Administrator’s 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 JAR files that are bundled. You can open these individual files in Design Studio to review or to extend the technology pack.

See the Design Studio online Help and UIM Developer’s Guide for information about opening files in Design Studio.

See UIM Concepts for guidelines and best practices for extending technology packs in general. See Chapter 5, "Extending the Metro Ethernet Technology Pack" for information about extending this technology pack.

Enabling Debugging of Validation and Assignment RulesThe validation and assignment rules included with the Metro Ethernet technology pack include debugging code that displays messages you can monitor by using the logging capabilities supplied by Weblogic. See UIM System Administrator’s Guide for more information about logging. The debugging code allows you to observe the behavior of the validation and assignment rules and diagnose any issues that arise.

To view the debugging log entries, you must configure the log to capture and display them as described in the following procedure.

To enable debugging of validation and assignment rules:

1. Open the loggingconfig.xml file, typically found in UIM_HOME/uim/config.

2. Add the following entries to the file:

<logger name="oracle.communications.inventory.techpack.vlan" additivity="false"><level value="debug" /><appender-ref ref="stdout"/><appender-ref ref="rollingFile"/></logger>

<logger name="oracle.communications.inventory.techpack.vlan.impl" additivity="false"><level value="debug" /><appender-ref ref="stdout"/><appender-ref ref="rollingFile"/></logger>

<logger name="oracle.communications.inventory.techpack.ethernet" additivity="false">

Important: Before deploying the Metro Ethernet Technology Pack, you must deploy the base cartridges if not previously deployed. For information on how to deploy the base cartridges, see UIM Base Cartridges Guide.

Enabling Debugging of Validation and Assignment Rules


<level value="debug" /><appender-ref ref="stdout"/><appender-ref ref="rollingFile"/></logger>

<logger name="oracle.communications.inventory.techpack.ethernet.impl" additivity="false"><level value="debug" /><appender-ref ref="stdout"/><appender-ref ref="rollingFile"/></logger>

<logger name="oracle.communications.rules" additivity="false"><level value="debug" /><appender-ref ref="stdout"/><appender-ref ref="rollingFile"/></logger>

3. Save and close the file.

2

Address, Location, and Party Content 2-1

2Address, Location, and Party Content

This chapter lists the entity specifications included in the address, location, and party cartridges in the Metro Ethernet 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_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, location, and party cartridges. Most are Place specifications. You can view the details of the specifications by opening the cartridges in 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, location, and party 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

The Postal Code field is 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

The postalCode field is 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

The postalCode field is 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

The postalCode field is seven characters long.

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


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.

usAddress Postal address of the subscriber for the phone service 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

The Zip Code field is 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

Data Networking Content 3-1

3Data Networking Content

This chapter lists the entity specifications included in the data networking cartridges of the Metro Ethernet 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 Design Studio.

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

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

Table 3–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

Table 3–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 customer premise equipment. 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



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

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

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

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

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



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

Table 3–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 Metro Ethernet Termination site

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



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 3–6 Service Specifications


Data Networking Service Defines a generic data networking service

May include configurations based on the Data Networking Service Configuration specification


Data Networking Content 3-3

Table 3–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

You can add the following configuration items:

■ 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 a Metro Ethernet service



4

Metro Ethernet Content 4-1

4Metro Ethernet Content

This chapter lists the entity specifications and rules included in the Metro Ethernet-specific cartridges in the Metro Ethernet Technology Pack. It also includes a high-level overview of the tasks involved in defining a Metro Ethernet service in UIM.

The Metro Ethernet cartridges are:

■ Number group cartridge: ora_uim_number_group_management

■ VLAN resource cartridge: ora_uim_vlanmgmt

■ Ethernet cartridge: ora_uim_ethernet

Entity SpecificationsThis section lists the specifications included in the Metro Ethernet-specific cartridges, organized by specification type. You can view the details of the specifications by opening the cartridges in Design Studio.

Custom Network Address SpecificationsTable 4–1 lists and describes the Custom Network Address specifications included in the Metro Ethernet-specific cartridges of the technology pack.



Inventory Group SpecificationsTable 4–2 lists and describes the Inventory Group specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Table 4–1 Custom Network Address Specifications


EVCResource Represents an instance of an EVC-Ethernet virtual connection scoped to an EVC domain

This specification contains the following characteristics:

■ Initial EVC Domain: List where you can select the EVC domain to which the EVC resource belongs

The EVC domain must exist prior to creating the EVC resource.

■ EVC-ID: Specifies the EVC resource identifier

■ EVC-Type: List where you can select a service configuration of type E-Line (default), E-LAN, or E-Tree for the EVC resource

This characteristic is a validated parameter and is mandatory.

■ MAX UNIs: Maximum number of UNIs that can be in an EVC; default value is 2

This characteristic is a validated parameter.

■ EVC MTU: Maximum sized Service Frame allowed for an EVC. The default value is 1522

This characteristic is not a validated parameter.

■ VLAN Preservation: Determines whether the CE-VLAN ID of an egress Service Frame is identical in value to the CE-VLAN ID of the corresponding ingress Service Frame

This characteristic is selected (set to true) by default and is a validated parameter.

■ CoS Preservation: Determines whether the Class of Service of an egress Service Frame is identical in value to the Class of Service of the corresponding ingress Service Frame

This characteristic is selected (set to true) by default and is a validated parameter.

■ Unicast Service Frame Delivery: List containing the values Deliver Conditionally, Discard, and Deliver Unconditionally

The service frames are typically delivered to all UNIs in the EVC except the ingress UNI if it is not learned. Otherwise, the service frames are delivered to the UNI learned for the destination MAC address. This characteristic is not a validated parameter.

■ Multicast Service Frame Delivery: List containing the values Deliver Conditionally, Discard, and Deliver Unconditionally

The service frames are typically delivered to all UNIs in the EVC except for the ingress UNI. This characteristic is not a validated parameter.

■ Broadcast Service Frame Delivery: List containing the values Deliver Conditionally, Discard, and Deliver Unconditionally

The service frames are delivered to all UNIs in the EVC except for the ingress UNI. This characteristic is not a validated parameter.

■ Layer2 Control Protocols Processing: List used to select a control protocol mode that controls the transfer of protocol data units (PDUs) across the Metro Ethernet network


You can select one of the following values, which determine how PDUs are handled by the Metro Ethernet network:

Discard: PDUs from the CE are discarded by the Metro Ethernet network and therefore never egress from the network

Tunnel: Frames are transparently passed to a given EVC for transport across the MEN to the destination UNI

VLANResource Represents a VLAN resource scoped to a VLAN domain

■ Initial VLAN Domain: List where you can select the VLAN domain to which the VLAN resource belongs

A VLAN domain must exist prior to creating the VLAN resource. This characteristic is a validated parameter.

■ VLAN Identifier: Represents a VLAN identifier scoped to a VLAN domain




Involvement SpecificationsTable 4–3 lists and describes the Involvement specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Network Edge SpecificationsTable 4–4 lists and describes the Network Edge specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Network Node SpecificationsTable 4–5 lists and describes the Network Node specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Table 4–2 Inventory Group Specifications


EVCDomain Represents a pool or domain of EVC resources

Creating an inventory group based on this specification triggers the CREATE_EVC_DOMAIN ruleset, which creates EVC resources based on the values you enter for EVC IDs to Add. This specification includes the following characteristic:

■ EVC IDs to Add: Specifies values, each comprising a string of letters and/or numbers, for EVC resources to be created for the EVC domain

A string can have a maximum length of 255 characters.

This characteristic is a validated parameter and is optional.

VLANDomain Represents a grouping of VLAN resources

Creating an inventory group based on this specification triggers the CREATE_VLAN_RANGE ruleset, which creates VLAN resources based on the values you enter for VLAN IDs to Add. This specification includes the following characteristic:

■ VLAN IDs to Add: Specifies values separated by commas or ranges separated by dashes, for VLAN Resources to be created for the VLAN domain

For example 1-5, 10, 19, 21-25 will create a VLAN list of 1 to 5, 10, 19, and 21 to 25

The maximum combined length of the values or ranges can be 255 bytes. This characteristic is a validated parameter and is optional.

Table 4–3 Involvement Specifications


UniEvcList Implements the UNI EVC List data element; automatically created when you validate a Metro Ethernet service

UIM creates the involvement and includes the EVC resource and device interfaces with the UNI role.

Table 4–4 Network Edge Specifications


MetroEthernetNetworkEdge Describes the behavior and attributes of the edges that connect Metro Ethernet network nodes; includes the following characteristics:

■ End Point 1 Name: Text field that enables you to name the end points of the edge


■ End Point 2 Name: Text field that enables you to name the end points of the edge




Network SpecificationsTable 4–6 lists and describes the Network specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Pipe SpecificationsTable 4–7 lists and describes the Pipe specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Pipe Termination Point SpecificationsTable 4–8 lists and describes the Pipe Termination Point specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Place SpecificationsTable 4–9 lists and describes the Place specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Place Configuration SpecificationsTable 4–10 lists and describes the Place Configuration specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Table 4–5 Network Node Specifications


MetroEthernetNetworkNode

Describes Metro Ethernet nodes that participate in a Metro Ethernet network

Table 4–6 Network Specifications


MetroEthernetNetwork Describes the Metro Ethernet network as a whole

When you create an instance of a Network specification, you associate network nodes and edges to the network.

Table 4–7 Pipe Specifications


EthernetPipe Describes the physical connectivity between Metro Ethernet nodes

Ethernet pipes are assigned to Metro Ethernet network edges.

Table 4–8 Pipe Termination Point Specifications


EthernetPipeEndPoints Describes the physical connectivity end points of Ethernet pipes



EthernetTermination Represents a service provider termination that contains a PE interface used as a UNI

This specification contains the EVC map that identifies specific customer traffic directed to each EVC resource.



Role SpecificationsTable 4–11 lists and describes the Role specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Table 4–10 Place Configuration Specifications


EthernetTerminationConfig Configuration that represents Ethernet termination objects that are being configured

This specification contains the following configuration items:

■ PE-Interface: Assigns a device interface which has the UNI-N-Interface-Role role

■ EVC-VLAN-Resources: Serves as a folder for EVC maps

■ EVC-Map: Assigns one or more EVC map services; includes the following characteristics:

UNI EVCResource Ref: Assigns the EVCResource ID the EVC Map is targeting


UNI Type: Indicates whether the map represents a root or leaf if EVC type is E-Tree


UNI EVC Id: Displays the UNI EVC identifier




Service SpecificationsTable 4–12 lists and describes the Service specifications included in the Metro Ethernet-specific cartridges of the technology pack.



UNI-N-Interface-Role Defines a device as a User Network Interface on the network side; includes the following characteristics:

■ UNI Identifier: Displays the UNI identifier for each UNI


■ UNI Physical Medium: Displays the physical medium used in the UNI


■ UNI MTU: The maximum sized Service Frame allowed for a UNI

The default value is 1522. This characteristic is not a validated parameter.

■ UNI Speed: List where you can select the speed of the UNI

For example, you can select the speed of the UNI as 10 Mbps, 100Mbps, and so on


■ UNI Mode: Indicates if the UNI mode is Full Duplex or Auto

The default mode is Full Duplex. This characteristic is not a validated parameter.

■ UNI MAC Layer: Displays the MAC layer used in the UNI


■ UNI Service Multiplexing: Check box to enable UNI Service Multiplexing


■ UNI MAX EVCs: The maximum number of EVCs that can be in a UNI

The default value is 1. This characteristic is a validated parameter.

■ UNI Bundling: Check box to enable bundling of UNI; enabled by default


■ UNI All-To-One-Bundling: Check box to enable UNI All-To-One bundling


■ UNI CE-VLAN Identifier: Displays the CE-VLAN ID at a UNI

This identifier is used for untagged and high-priority tagged traffic. This characteristic is not a validated parameter.

■ Layer2 Control Protocols Processing: List used to select a control protocol mode that controls the transfer of protocol data units (PDUs) across the Metro Ethernet network


You can select one of the following values, which determine how PDUs are handled by the Metro Ethernet network:

Discard: PDUs from the CE are discarded by the Metro Ethernet network and therefore never egress from the Metro Ethernet network

Peer: Metro Ethernet network peers with CE to host the protocol

Pass to EVC: PDUs are carried across the Metro Ethernet network as normal data or an EVC associated with the CE-VLAN ID of the PDUs

Peer and Pass to EVC: Some Service Frames carrying the Layer 2 Control Protocol are processed by the MEN as a peer while other Service Frames are passed to the EVC

Rulesets Included in the Technology Pack


Service Configuration SpecificationsTable 4–13 lists and describes the Service Configuration specifications included in the Metro Ethernet-specific cartridges of the technology pack.

Rulesets Included in the Technology PackTable 4–14 lists the rulesets that are included in the Metro Ethernet Technology Pack.

Table 4–12 Service Specifications


EVCMapService EVC maps represent an association of CE-VLAN IDs with EVCs at a UNI. They act as containers or filters of customer VLAN identifiers that are applied to a unique EVC resource.

An EVCMapService can include configurations based on the VLAN-List configuration specification. The service includes the following characteristics:

■ VLAN Domain A list in which you can specify the preferred VLAN domain for the service if multiple pools of VLAN domains exist

This characteristic enables automatic assignment of a VLAN resource when the field value is specified. If the field is not specified, you must manually search for a free VLAN resource to assign. This characteristic is a validated parameter.

MetroEthernetService Represents a collection of one or more EVC resources that provide connectivity between two or more UNI-N interfaces contained in Ethernet terminations

The Metro Ethernet service may contain multiple EVC resources when they are related by a customer or service. The service can include configurations based on the Port-Based Service or VLAN-Based Service Configuration specification. The service includes the following characteristic:

■ Preferred EVC Domain: A list in which you can specify the preferred EVC domain for the service if multiple pools of EVC domains exist

This characteristic enables automatic assignment of an EVC resource when the field value is specified. If the field is not specified, you must manually search for a free EVC resource to assign. This characteristic is a validated parameter.

Table 4–13 Service Configuration Specifications


PortBased Service Metro Ethernet Service configuration used for Port-based services, such as Ethernet Private Line (EPL)

Includes two configuration items:

■ Termination-List: Parent item containing two EthernetAccessTermination configuration items, one for each termination

■ EVC-List. Parent item that includes EVC-Profile, which includes the EVC-Identity configuration items

You assign an EVC resource to the Metro Ethernet service in EVC-Identity.

VLANBased Service Metro Ethernet Service configuration used for VLAN-based services such as Ethernet Virtual Private Line (EVP-Line)

Includes two configuration items:

■ Termination-List: Parent item containing two EthernetAccessTermination configuration items, one for each termination

■ EVC-List. Parent item that includes EVC-Profile, which includes the EVC-Identity configuration items

You assign an EVC resource to the Metro Ethernet service in EVC-Identity.

VLAN-List Configuration for the EVC Map service

Represents the container for customer VLAN resources and includes this configuration item:

■ C-VLAN-Resource: An instance of a VLAN resource



Table 4–14 List of Rulesets in the Metro Ethernet Technology Pack

Ruleset/Ruleset Extension Points Functionality

ASSOCIATE_WITH_EVCDOMAIN

ASSOCIATE_WITH_EVCDOMAIN_EXT

Automatically associates a EVCResource to a EVCDomain when that EVCResource is created on its own

Triggered by creating an EVCResource and setting its domain with the EVC Domain characteristic

ASSOCIATE_WITH_VLANDOMAIN

ASSOCIATE_WITH_VLANDOMAIN_EXT

Automatically associates a VLANResource to a VLANDomain when that VLANResource is created on its own

Triggered by creating a VLANResource and setting its domain with the VLAN Domain characteristic

AUTO_ASSIGN_EVC_RESOURCE

AUTO_ASSIGN_EVC_RESOURCE_EXT

Auto-assigns an EVCResource into the Metro Ethernet Service

Triggered by the following:

■ Setting the characteristic Preferred EVC Domain in the service

■ Selecting Assign EVCResource

AUTO_ASSIGN_STUB_EVCMAPSERVICE

AUTO_ASSIGN_STUB_EVCMAPSERVICE_EXT

Stub ruleset to enable auto-assignment of resources to an EVC map service configuration

Triggered when Auto Assign is selected from the Related Pages menu in an EVC map service configuration work area

AUTO_ASSIGN_STUB_METROETHERNETSERVICE_CONFIG

AUTO_ASSIGN_STUB_METROETHERNETSERVICE_CONFIG_EXT

Stub ruleset to enable auto-assignment of resources to a Metro Ethernet service configuration

Triggered by selecting Auto Assign from the Related Pages menu in a Metro Ethernet service configuration work area

CREATE_EVC_DOMAIN

CREATE_EVC_DOMAIN_EXT

Automatically creates EVCResources using the data from the characteristic EVCList when an EVCDomain is created

Triggered by creating an EVCDomain

CREATE_VLAN_RANGE

CREATE_VLAN_RANGE_EXT

Automatically creates VLANResources using the data from the characteristic VLAN List when a VLANDomain is created

Triggered by creating a VLANDomain

DELETE_EVC_DOMAIN

DELETE_EVC_DOMAIN_EXT

Automatically deletes EVCResources when the EVCDomain is deleted

Triggered by deleting an EVCDomain

DELETE_VLAN_RANGE

DELETE_VLAN_RANGE_EXT

Automatically deletes VLANResources when the VLANDomain is deleted

Triggered by deleting a VLANDomain



IMPORT_VLAN_DOMAINS Imports a group of VLAN domains and the associated values or ranges of VLAN IDs into UIM from a user-specified input file. The input file may have either of the formats, .csv or .txt.

Use the following formats to specify the names of the VLAN domains and the VLAN IDs/ranges if the input file has a .txt format:

■ Name of the VLAN domain: Values of the associated VLAN IDs separated by commas.

■ Name of the VLAN domain: Range of values for the VLAN IDs separated by dashes

Use the following formats to specify the names of the VLAN domains and the VLAN IDs/ranges if the input file has a .csv format:

■ Name of the VLAN domain, Values of the associated VLAN IDs separated by commas.

Note: If you specify multiple values separated by commas in a single cell within the file, the ruleset reads the values as a single string.

■ Name of the VLAN domain, Range of values for the VLAN IDs separated by dashes

To import VLAN domains, select Import Inventory in the Navbar, and then select this ruleset in the RuleSet list. Specify the name of the input file, and click Process.

You use this ruleset, instead of the UIM interface, to associate a VLAN domain with VLAN IDs/ranges whose combined length exceeds 255 bytes.

The UIM interface limits the maximum length of VLAN IDs/ranges that may be associated to a VLAN domain, when it is created or modified, to 255 bytes.

PREVENT_DISASSOCIATION_FROM_EVCDOMAIN

PREVENT_DISASSOCIATION_FROM_EVCDOMAIN_EXT

Blocks the user from disassociating an EVCResource from an EVCDomain

Triggered when the user attempts to delete the item association in the EVCDomain or the inventory group association in EVCResource

PREVENT_DISASSOCIATION_FROM_VLAN_DOMAIN

PREVENT_DISASSOCIATION_FROM_VLAN_DOMAIN_EXT

Blocks the user from disassociating a VLANResource from a VLANDomain

Triggered when the user attempts to delete the item association in the VLANDomain or the inventory group association in VLANResource

UPDATE_EVC_DOMAIN

UPDATE_EVC_DOMAIN_EXT

Processes the list of EVC IDs to create custom network addresses and associates the addresses with an inventory group. This ruleset returns an error message displaying a list of duplicate addresses in case duplicate addresses are generated.

Triggered when the user updates an EVCDomain with an additional list of EVC IDs

UPDATE_VLAN_RANGE

UPDATE_VLAN_RANGE_EXT

Updates an existing VLAN domain with an additional list of VLAN IDs

Triggered when the user updates a VLAN domain with an additional list of VLAN IDs

VALIDATE_EVCMAPSERVICE_CONFIG

VALIDATE_EVCMAPSERVICE_CONFIG_EXT

Validates an EVCMap service configuration:

■ Validates that an EVCResource does not have duplicate VLAN Identifiers and that all VLAN Identifiers belong to the same VLANDomain

■ Validates that the tree structure is built correctly

Triggered by selecting Validate from the Actions menu in the EVCMap Service Configuration work area

Table 4–14 (Cont.) List of Rulesets in the Metro Ethernet Technology Pack




VALIDATE _METROETHERNETSERVICE_CONFIG

VALIDATE _METROETHERNETSERVICE_CONFIG_EXT

Validates a Metro Ethernet service configuration:

■ Validates that an EVC resource is included in the configuration

■ Validates that there are no EVC resources in an Ethernet termination that is not in the Metro Ethernet service

■ Validates that the number of Ethernet terminations does not exceed the Max UNI value of the EVC resource

■ Validates that each EVC resource has the same egress EVC map if VLAN Preservation and CoS Preservation are true

If they are not true, validates that the EVC resource ingress EVC map has an egress. There can be a different map on the egress side.

■ Validates that at least one root Ethernet termination exists for an E-TREE EVC resource


Includes a validation of Ethernet Terminations:

■ Validates that for a Port-based service, each termination only has one EVC map

■ Validates that Service Multiplexing, Bundling, and All To One Bundling are set property for the service topology

■ Validates that for a Port-based service, VLAN Preservation and CoS Preservation are set to true

■ Validates that if the EVC map contains more than one VLAN identifier, VLAN Preservation is set to true

■ Validates that when multiple EVC maps are used at an Ethernet termination, the same VLAN identifier is not duplicated across maps

■ Validates that the number of EVCs on the UNI does not exceed the UNI Max EVCs value set in the UNI-N-Interface-Role



VALIDATE_STUB_EVCMAPSERVICE_CONFIG

VALIDATE_STUB_EVCMAPSERVICE_CONFIG_EXT

Stub ruleset to enable customization of EVC service map configuration validation


VALIDATE _STUB_METROETHERNETSERVICE_CONFIG

VALIDATE _STUB_METROETHERNETSERVICE_CONFIG_EXT

Stub ruleset to enable customization of EVC service map configuration validation

Triggered by selecting Validate from the Actions menu in the Metro Ethernet Service Configuration work area

Table 4–14 (Cont.) List of Rulesets in the Metro Ethernet Technology Pack


5

Extending the Metro Ethernet Technology Pack 5-1

5Extending the Metro Ethernet Technology Pack

You can extend the Metro Ethernet 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 Design Studio online Help for general information about how you extend specifications, characteristics, and rulesets.

Extending Validation and Auto-Assignment CapabilitiesThe Metro Ethernet 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 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:

■ VALIDATE_STUB_EVCMAPSERVICE_CONFIG. Enables you to add functionality to the standard validation logic for EVC map service configurations provided by VALIDATE_EVCMAPSERVICE_CONFIG. Triggered when Validate is selected from the Actions menu in an EVC map service configuration work area.

■ VALIDATE_STUB_METROETHERNETSERVICE_CONFIG. Enables you to add functionality to the standard validation logic for Metro Ethernet service configurations provided by VALIDATE_METROETHERNETSERVICE_CONFIG. Triggered when Validate is selected from the Actions menu in a Metro Ethernet service configuration work area.

■ AUTO_ASSIGN_STUB_EVCMAPSERVICE_CONFIG. Enables you to implement auto-assignment for EVC map service configurations. Triggered when Auto Assign is selected from the Related Pages menu in an EVC map service configuration work area.

■ AUTO_ASSIGN_STUB_METROETHERNETSERVICE_CONFIG. Enables you to implement auto-assignment for Metro Ethernet service configurations. Triggered

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


when Auto Assign is selected from the Related Pages menu in a Metro Ethernet service configuration work area.

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 configuration. You can associate characteristics or specification options to these stubs from separate cartridge, 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 Ethernet Termination ModelThe Ethernet Termination configuration specification includes two stub configuration items. Table 5–1 lists and describes these configuration items.

Extending the Ethernet Service ConfigurationsThe VLANBased Service and PortBased Service configuration specifications for the Metro Ethernet service include four stub configuration items associated with the EVC-Profile configuration item. Table 5–2 lists and describes these configuration items.

Table 5–1 Stub Configuration Items for the Ethernet Termination Model

Stub Item Use

Ingress-Performance

Egress Performance

Used to support Quality of Service (QoS) standards

For example, you can include characteristics such as the Committed Info Rate, Burst Size, or Excess Information Rate.

Table 5–2 Stub Configuration Items for Ethernet Service Configurations

Stub Item Use

Ingress-Performance

Egress Performance

Used to support Quality of Service (QoS) standards

For example, you could include characteristics such as the Committed Info Rate, Burst Size, or Excess Information Rate.

Additional Characteristics Used to associate additional characteristics if necessary to the EVC profile

EVC-Composition Used to specify how the EVC is implemented

For example, you could include a specification option for a Layer 2 service

6

Metro Ethernet Technology Pack Service Example 6-1

6Metro Ethernet Technology Pack Service Example

This chapter provides an example of configuring a service using the Metro Ethernet Technology Pack.

The example is a transport-oriented Ethernet Private Line (EPL) service for private data networking. This scenario is taken from the Metro Ethernet Forum (MEF) technical specification for MEF 6.1. For more information, you can download the specification from the MEF web site:

http://metroethernetforum.org

OverviewA service such as this example comprises two services that you create in UIM:

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

■ A transport service that represents the service provider’s implementation of that connectivity. The transport service is modeled as an instance of the MetroEthernetService specification. The transport service also includes an instance of the EVCMapService specification. See "Creating the Transport Service".

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

AssumptionsIn this example, we assume that service-provider resources such as networks, network nodes, network edges, pipe termination points, logical devices, and device interfaces already exist in your inventory. See Figure 1–5, "Metro Ethernet Service Network Model" for an illustration of the relationships among these resources.

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 Service


Creating the Customer ServiceThe customer service includes the customer premise equipment (CPE) and sites that are to be connected by the service-provider Metro Ethernet network. The customer service is an instance of the Data Networking Service specification provided in the technology pack. See 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 four steps:

■ Creating Customer Devices and Interfaces

■ Creating Customer Service Locations

■ Creating Customer Sites

■ Creating the Data Networking Service

Creating Customer Devices and InterfacesThe technology pack includes the Data Networking Device specification that you can use to represent CPE logical devices. It also includes the Data Networking Device Interface specification for interfaces provided by those devices. For this example, you need:

■ Two logical device entities based on the Data Networking Device specification, one for each of the two CPE devices that are to be connected by Metro Ethernet.

■ Two device interfaces based on the Data Networking Device Interface specification, one for each CPE device. These device interfaces function as customer-side UNIs (UNI-Cs) for the Metro Ethernet network.

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 two 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 for this purpose.

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

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

■ Add a configuration version to each entity. Only one configuration specification (Data Networking Site Configuration) is available. See the next section, "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 you created by specifying their location, site termination, and CPE devices.

Creating the Customer Service


For each site configuration:

■ 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 the 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 and Transport Services".

Figure 6–1 illustrates a customer site configuration with resources assigned. The Transport Termination configuration item has not yet been assigned.

Figure 6–1 Customer Site Configuration

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 and other specifications.

You create a configuration version based on this specification so that you can assign the customer sites that you created previously. Later, you will also assign a transport service to this service configuration. See "Linking the Customer and Transport Services".

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

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

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

■ To the Sites configuration item in the service configuration, add two instances of the Data Networking Site configuration item. Assign one of the customer sites you created earlier to each of these configuration items.

Figure 6–2 illustrates a data networking service configuration with two sites assigned. The Transport Services configuration item is unassigned at this time.

Creating the Transport Service


Figure 6–2 Data Networking Service Configuration

Creating the Transport ServiceThe service provider’s implementation of connectivity for the customer service is represented by a transport service. The transport service is an instance of the MetroEthernetService specification.

To this service, you assign two termination sites that capture information about the customer-facing PE interfaces that are used to communicate with customer interfaces. These interfaces function as the network-side UNIs (UNI-Ns). You also assign an EVC Map service that directs customer traffic to EVCs.

Creating the transport service comprises several groups of tasks:

■ Creating the EVC Domain and Resources

■ Creating the EVC Map Service

■ Creating the Ethernet Termination Sites

■ Creating the Metro Ethernet Service

After the transport service is complete, you link it to the customer service. See Linking the Customer and Transport Services.

Creating the EVC Domain and ResourcesThe transport service requires an EVC resource. You create EVCs for the service by creating an EVC pool or domain. You specify this as the preferred domain when you create the Metro Ethernet service. UIM will then select from this domain automatically when you assign an EVC resource to the service.

Figure 1–4, "Metro Ethernet Service Model" illustrates the relationships among the entities used to model the EVC domain, its resources, and the Metro Ethernet service.

You create the EVC domain by using the EVCDomain Inventory Group specification. This specification enables you to create a pool of EVCs at the same time.

When you create an inventory group based on the EVCDomain specification, the CREATE_EVC_DOMAIN ruleset is triggered. This rule creates one or more EVCs as Custom Network Address entities based on the EVCResource specification.

The number of entities and their names are determined by what you enter into the EVC IDs to Add field when you create the inventory group. You can enter a string of letters and/or numbers for each EVC ID.

Alternately you can specify a range of numbers (201-205), a comma-separated list (207, 209), or a combination of numbers and ranges, for example (201-205, 207, 209).

The EVCs are named by taking the domain name and appending the numbers defined in the EVC IDs to Add field. For example, Figure 6–3 illustrates the Items area of an



EVC Domain Inventory Group Summary work area showing the EVCs created by entering 1-3 into the EVC IDs to Add field.

Figure 6–3 EVC Resources in an EVC Domain Inventory Group

You can add or remove EVCs in the inventory group later, if necessary. You can also edit EVC resource characteristics. You cannot change the association between an EVC resource and its EVC domain, however.

For this example, you can create an EVCDomain inventory group with a small number of EVCs.

Creating the EVC Map ServiceYou create an EVC Map service and an accompanying service configuration to direct customer traffic to the EVC resource you have created. The technology pack includes the EVCMapService specification for this purpose. You assign this service to the Ethernet termination sites that you define for the transport service. See "Assigning the EVC Map Service" for more information.

Figure 1–6, "Metro Ethernet Termination Model" illustrates the relationships among the EVC map service and other entities.

For this example:

■ Create a Service entity based on the EVCMapService specification. Note that this specification includes a VLAN Domain characteristic. This characteristic can be left blank for a Port-based service. For a VLAN-based service, you would use to designate the VLAN domain from which the service would draw VLAN resources.

■ Add a configuration. Only one configuration specification is available, VLAN-List.

■ Validate the service to ensure that it is complete.

Creating the Ethernet Termination SitesThe technology pack includes a Place specification called EthernetTermination that you use to represent the two termination sites for the transport service. Each termination site is assigned a device interface that represents a UNI-N.

For each termination site:

Note: If this example were VLAN-based, you would assign VLAN resources to the EVC Map service configuration. You can create these resources similarly to the way you create EVC resources. You can create an inventory group based on the VLANDomain specification, which automatically creates VLANResource entities. Customer VLAN IDs are not required in the map because this example is Port-based.



■ Create a site-type Place entity based on the EthernetTermination specification.

■ Add a configuration to the site. Only one configuration specification is available, EthernetTerminationConfig. The configuration includes PE Interface and EVC-VLAN Resource configuration items.

See "Assigning PE Interfaces and Assigning the UNI-N Role" and "Assigning the EVC Map Service" for information about assigning resources to these items.

Assigning PE Interfaces and Assigning the UNI-N Role Each Ethernet termination site configuration includes a PE Interface configuration item. You use this item to assign a device interface that represents the customer-facing PE interface for this site (the UNI-N).

The device interface that you assign to the PE Interface configuration item in the Ethernet termination configuration must be assigned the UNI-N-Interface-Role to designate its function.


■ Assign the appropriate device interface. The interface must be based on the Data Networking Device Interface specification.

■ In the Summary work area of the interface that you assigned to the termination site, assign the UNI-N-Interface-Role role to the interface.

When you assign the role, you also specify values for a number of characteristics that represent UNI service attributes. Table 6–1 shows values for these characteristics taken from the EPL example in the MEF 6.1 technical specification. See also the MEF 10.1 technical specification for definitions of these and Ethernet service attributes.

Note: For this example, we assume that you have already created logical devices based on the Data Networking Device specification and that these devices provide interfaces based on the Data Networking Device Interface. If these devices and interfaces do not already exist, however, you can create them during the process of creating and configuring the Ethernet termination sites.

Table 6–1 UNI Role Characteristics

Characteristic Value

UNI Identifier Enter an ID for this UNI. The ID must be unique for all UNIs in the Metro Ethernet network.

Physical Medium 1000BASE-SX

Physical Speed 1Gbps

UNI Mode FullDuplex

UNI Mac Layer IEEE 802.3-2005

UNI MTU size 1522 (the default value)

UNI Service Multiplexing False (unselected; default value)

UNI Bundling False (unselected; default value)

UNI All-To-One-Bundling True (selected; default value)



Assigning the EVC Map ServiceEach Ethernet termination site configuration includes an EVC-VLAN-Resources configuration item. You add an EVC-Map configuration item to this item so that you can assign the EVC Map service you created previously.


■ Add an EVC-Map configuration item to the EVC-VLAN-Resources configuration item. (EVC-Map is the only item you can add.)

■ To the EVC-Map configuration item, assign the EVC Map service you created earlier. Note that the EVC Map service configuration you created earlier is added automatically to the site configuration when you assign the service.

■ Set the characteristics of this configuration item as follows:

– In the UNI EVC ID field, enter an identifier. According to the MEF technical specification, this should represent a concatenation of the UNI ID and the EVC ID.

– Leave UNI EVCResource Ref undefined for now. You will populate it later with the ID of the EVC resource assigned to the Metro Ethernet service.

– Set UNI Type to Root (the default value).

Figure 6–4 shows an Ethernet termination site configuration with these values set.

Figure 6–4 Ethernet Termination Site Configuration Items, In-Progress

Creating the Metro Ethernet ServiceYou create an entity based on the MetroEthernetService specification to represent the transport service. The specification is accompanied by two configuration specification, PortBasedService and VLANBasedService. In this case, you use the PortBasedService configuration specification.

UNI Max EVCs 1

UNI CE-VLAN Identifier no value

Layer2 Control Protocols Processing This value depends on the layer 2 protocol used. See the MEF 6.1 technical specification for more information.

Table 6–1 (Cont.) UNI Role Characteristics




Figure 1–4, "Metro Ethernet Service Model" illustrates the relationships among the specifications used for this service.

For this example:

■ Create a service based on the MetroEthernetService specification. When you create the service, in the Preferred EVC Domain field, select the EVC domain you created earlier. This domain determines the pool of EVCs that the service configuration will select from.

■ Add a configuration version based on the PortBasedService specification. The configuration includes two configuration items, Termination-List and EVC-List. See "Assigning the Terminations" and "Assigning and Configuring the EVC Resource" for information about these configuration items.

Assigning the TerminationsYou use the Termination-List configuration item in a Metro Ethernet Service configuration to assign the two Ethernet terminations that you created earlier.

This configuration item has two EthernetAccessTermination configuration items, one for each termination. Assign one termination to each configuration item.

Assigning and Configuring the EVC ResourceIn the EVC-List configuration item, you assign an EVC resource to the Metro Ethernet service. Because you specified an inventory group in the service’s Preferred EVC Domain field, UIM automatically selects an EVC from the pool controlled by that inventory group. (If no EVC resources are available in this pool, you must add more to the pool.)

To assign the EVC resource:

■ Expand the EVC-List configuration item and its children in the Metro Ethernet service configuration to reveal the EVC-Identity configuration item. Assign a resource to this item. When you begin the assignment process, UIM automatically finds the first available resource in the EVC domain you specified for the service. This resource is assigned to the configuration item. Figure 6–5 shows an EVC resource assigned in a Metro Ethernet service configuration.

Figure 6–5 Assigned EVC Resource

After assigning an EVC resource, you must open its Summary work area and edit characteristics to specify EVC attributes. Table 6–2 shows values for these characteristics taken from the EPL example in the MEF 6.1 technical specification. See



also the MEF 10.1 technical specification for definitions of these and Ethernet service attributes.

Note that the characteristics do not include an explicit list of related UNIs as mentioned in the MEF specification. This list is created automatically when you validate the Metro Ethernet service. See "Validating the Metro Ethernet Service" for details.

Figure 6–6 illustrates these values in the Information work area of an EVC resource.

Figure 6–6 EVC Resource Characteristics

Associating the UNI EVC Resource to Termination SitesAfter you have assigned an EVC resource and set values for its characteristics, you can associate that EVC resource with the Ethernet termination sites that you created earlier. You make the association by entering the ID of the resource into the UNI EVCResource Ref characteristic for the EVC-Map configuration item of each termination site’s configuration.

Table 6–2 EVC Resource Characteristics Values


EVC-Type E-Line

EVC-Id Enter an ID for this EVC. The ID must be unique for all EVCs in the Metro Ethernet network.

Max-UNIs 2

VLAN Preservation True (selected; default value)

COS Preservation True (selected; default value)

EVC MTU 1522 (default value)

Unicast Service Frame Delivery Select Deliver Unconditionally

Multicast Service Frame Delivery Select Deliver Unconditionally

Broadcast Service Frame Delivery Select Deliver Unconditionally

Layer2 Control Protocols Processing This value depends on the layer 2 protocol used. See the MEF 6.1 technical specification for more information.

Linking the Customer and Transport Services


You can find an EVC resource’s ID in the Metro Ethernet service configuration (see Figure 6–5) or in the resource’s Summary or Information work area (see Figure 6–6). For example, the EVC resource assigned in the previous section has the ID 11.

You enter this value for the UNI EVCResource Ref for both termination sites. Figure 6–7 illustrates the configuration items for a termination site configuration, including a UNI EVCResource Ref value.

Figure 6–7 Termination Site Configuration Items and Characteristics

Validating the Metro Ethernet ServiceIt is important to validate a Metro Ethernet Service after you create it. The validation process verifies that the service is configured correctly and also creates involvement entities based on the UniEvcList specification that link together the EVC and interface entities in the service.

After the service has been validated, you can view the involvement from the Summary work area of any of the EVCs or device interfaces. Figure 6–8 shows the Involvements area from an EVC Summary work area. This area lists involvements with the two device interfaces for the Ethernet termination sites assigned to the service.

Figure 6–8 EVC Involvements Area

Linking the Customer and Transport ServicesAfter the transport service is complete, you can return to the customer service to link the two. Linking the services includes:

■ Assigning the Transport Service

■ Assigning Terminations

When these two assignments have been made, the entire EPL service is complete.



Assigning the Transport ServiceYou assign a Metro Ethernet service instance to the customer service configuration. This relationship defines the service that is used to enable connectivity between the two customer sites.

In the customer service configuration:

■ Add a Transport Service configuration item to the Transport Services configuration item. Assign the Metro Ethernet service instance you created previously.

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

For each customer site:

■ In the site configuration, assign the appropriate Ethernet 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.



Date post:	10-Nov-2018
Category:	Documents
Upload:	hatram
View:	222 times
Download:	0 times

Metro Ethernet Technology Pack Implementation Guide … · Oracle® Communications Unified...

Documents