Skip Headers
Oracle® Communications Unified Inventory Management Metro Ethernet Technology Pack Implementation Guide
Release 7.2.2

Part Number E36036-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

1 Metro 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 Pack

The Metro Ethernet Technology Pack enables you to model instances of Port-based and VLAN-based Metro Ethernet services in Oracle Communications Unified Inventory Management (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

Described in the surrounding text.

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

Described in the surrounding text.

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

Described in the surrounding text.

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

Described in the surrounding text.

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

Figure 1-5 Metro Ethernet Service Network Model

Described in the surrounding text.

Figure 1-6 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

Described in the surrounding text.

Metro Ethernet Service Topologies

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

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)


Contents of the Metro Ethernet Technology Pack

Table 1-2 describes the Metro Ethernet Technology Pack, which is delivered as a ZIP file.

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.


Metro Ethernet 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 Metro Ethernet Technology Pack, including information that summarizes classes, methods, and parameters.

Metro Ethernet Technology Pack Super JAR File

The 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 Cartridge and Technology Pack Guide for more information about the Cartridge Deployer Tool.

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

  • ora_uim_data_networking_service_cartproj-*.jar

  • ora_uim_number_group_management_cartproj-*.jar

  • ora_uim_vlanmgmt_cartproj-*.jar

  • ora_uim_ethernet_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

Metro Ethernet Technology Pack ZIP Archive Files

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

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

Address, Location, and Party Cartridges

The 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 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

Metro Ethernet Cartridges

The 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 Pack

Oracle 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 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 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 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 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 Rules

The 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">
    <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.