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
PDF · Mobi · ePub

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

Overview

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

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.

Assumptions

In 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

The 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

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

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

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

You provision the customer sites you created by specifying their location, site termination, and CPE devices.

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

Described in the surrounding text.

Creating the Data Networking Service

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

Figure 6-2 Data Networking Service Configuration

Described in the surrounding text.

Creating the Transport Service

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

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 Resources

The 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

Described in the surrounding text.

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 Service

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

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.

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 Sites

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

  • 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).

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.

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.

For each termination site:

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

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)

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.


Assigning the EVC Map Service

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

For each termination site:

  • 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

    Described in the surrounding text.

Creating the Metro Ethernet Service

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

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 Terminations

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

In 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

    Described in the surrounding text.

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.

Table 6-2 EVC Resource Characteristics Values

Characteristic Value

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.


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

Figure 6-6 EVC Resource Characteristics

Described in the surrounding text.

Associating the UNI EVC Resource to Termination Sites

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

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

Described in the surrounding text.

Validating the Metro Ethernet Service

It 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

Described in the surrounding text.

Linking the Customer and Transport Services

After the transport service is complete, you can return to the customer service to link the two. Linking the services includes:

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

Assigning the Transport Service

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

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