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

4 Metro 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 Oracle Communications Unified Inventory Management (UIM).

The Metro Ethernet cartridges are:

Entity Specifications

This 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 Oracle Communications Design Studio.

Custom Network Address Specifications

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

Table 4-1 Custom Network Address Specifications

Specification Description

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

    This characteristic is not a validated parameter.

    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

    This characteristic is a validated parameter.


Inventory Group Specifications

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

Table 4-2 Inventory Group Specifications

Specification Description

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.


Involvement Specifications

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

Table 4-3 Involvement Specifications

Specification Description

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.


Network Edge Specifications

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

Table 4-4 Network Edge Specifications

Specification Description

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

    This characteristic is not a validated parameter.

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

    This characteristic is not a validated parameter.


Network Node Specifications

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

Table 4-5 Network Node Specifications

Specification Description

MetroEthernetNetworkNode

Describes Metro Ethernet nodes that participate in a Metro Ethernet network


Network Specifications

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

Table 4-6 Network Specifications

Specification Description

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.


Pipe Specifications

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

Table 4-7 Pipe Specifications

Specification Description

EthernetPipe

Describes the physical connectivity between Metro Ethernet nodes

Ethernet pipes are assigned to Metro Ethernet network edges.


Pipe Termination Point Specifications

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

Table 4-8 Pipe Termination Point Specifications

Specification Description

EthernetPipeEndPoints

Describes the physical connectivity end points of Ethernet pipes


Place Specifications

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

Table 4-9 Place Specifications

Specification Description

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.


Place Configuration Specifications

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

Table 4-10 Place Configuration Specifications

Specification Description

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

    This characteristic is a validated parameter.

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

    This characteristic is a validated parameter.

    UNI EVC Id: Displays the UNI EVC identifier

    This characteristic is not a validated parameter.


Role Specifications

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

Table 4-11 Role Specifications

Specification Description

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

    This characteristic is not a validated parameter.

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

    This characteristic is not a validated parameter.

  • 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

    This characteristic is not a validated parameter.

  • 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

    This characteristic is not a validated parameter.

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

    This characteristic is a validated parameter.

  • 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

    This characteristic is a validated parameter.

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

    This characteristic is a validated parameter.

  • 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

    This characteristic is not a validated parameter.

    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


Service Specifications

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

Table 4-12 Service Specifications

Specification Description

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.


Service Configuration Specifications

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

Table 4-13 Service Configuration Specifications

Specification Description

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.

  • Connectivity-List: Contains the Connectivity configuration item:

    Connectivity: Enables you to assign a service trail, which is enabled in UIM by an external system

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.

  • Connectivity-List: Contains the Connectivity configuration item:

    Connectivity: Enables you to assign a service trail, which is enabled in UIM by an external system

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


Rulesets Included in the Technology Pack

Table 4-14 lists the rulesets that are included in the Metro Ethernet Technology Pack.

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

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

  • Validates that the tree structure is built correctly

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

  • Validates that the tree structure is built correctly

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

VALIDATE_STUB_EVCMAPSERVICE_CONFIG

VALIDATE_STUB_EVCMAPSERVICE_CONFIG_EXT

Stub ruleset to enable customization of EVC service map configuration validation

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

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