Skip Headers
Oracle® Communications Unified Inventory Management L2 VPN Technology Pack Implementation Guide
Release 7.2.2

Part Number E36037-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 Layer 2 VPN Content

This chapter lists the entity specifications and rules included in the Layer 2 VPN-specific cartridges in the L2 VPN Technology Pack.

The Layer 2 VPN cartridges are:

Entity Specifications

This section lists the specifications included in the Layer 2 VPN-specific cartridges, organized by specification type. You can view the details of the specifications by opening the cartridges in Oracle Communications Design Studio.

Custom Network Address Specifications

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

Table 4-1 Custom Network Address Specifications

Specification Description

Route Distinguisher

Represents a route distinguisher scoped to a route distinguisher group

The Route Distinguisher specification includes the following characteristics:

  • Format Type: Determines the format of the route distinguisher

    The Format Type characteristic can be set to one of the following types:

    Type 0 AS: Administrative value is a two-byte numeric value and assigned value is a four-byte numeric value.

    Type 1 IP: Administrative value is an IP dotted notation four-byte value and assigned value is a two-byte numeric value.

    Type 2 AS4: Administrative value is a four-byte numeric value and assigned value is a two-byte numeric value.

  • Administrator Value: The first part of the route distinguisher, which usually defines the autonomous system that the route distinguisher will use

  • Assigned value: The second part of the route distinguisher, which assigns a unique number within the administrative value's group

  • Initial Route Distinguisher Group Name: Set value to the route distinguisher (group) that the route distinguisher will initially be added to

Route Target

Represents a route target scoped to a route target group

A route target is used to define virtual private network (VPN) membership. A route target is made up of two values, the administrative value and the assigned value, which compiled make up six bytes.

The Route Target specification includes the following characteristics:

  • Format Type: Determines the format of the route target

    The Format Type characteristic can be set to one of the following types:

    Type 0 AS: Administrative value is a two-byte numeric value and assigned value is a four-byte numeric value.

    Type 1 IP: Administrative value is an IP dotted notation four-byte value and assigned value is a two-byte numeric value.

    Type 2 AS4: Administrative value is a four-byte numeric value and assigned value is a two-byte numeric value.

  • Administrator Value: The first part of the route target, which usually defines the autonomous system that the route target will use

  • Assigned value: The second part of the route target, which assigns a unique number within the administrative value's group

  • Initial Route Target Group Name: Set value to the route target (group) that the route target will initially be added to

VPN ID

Represents a unique identifier for an instance of a VPN service

VLAN Resource

Represents a virtual LAN (VLAN) resource scoped to a VLAN domain

The VLAN Resource specification has the following characteristics:

  • Initial VLAN Domain: VLAN domain to which the VLAN resource belongs

    A VLAN domain must exist before a VLAN resource is created

  • VLAN Identifier: A 12-bit VLAN identifier scoped to a VLAN domain

VLL Service ID

Represents the unique virtual leased line (VLL) service identifier

VPLS Service ID

Represents the unique virtual private LAN service (VPLS) identifier


Inventory Group Specifications

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

Table 4-2 Inventory Group Specifications

Specification Description

Route Distinguisher Type 0 Group

Represents a pool or group of Type 0 route distinguishers

Creating an inventory group based on this specification triggers the ADD_ROUTEDISTINGUISHER0_GROUP ruleset, which creates route distinguishers based on the values you enter in the Initial Route Distinguisher Range field.

The Route Distinguisher Type 0 Group specification includes the following characteristic:

  • Initial Route Distinguisher Range: Optional parameter that contains comma- or dash-separated values to specify a range of route distinguishers to be created; for example, 1:1-1:3, 1:5 will create a route distinguisher list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.

Route Distinguisher Type 1 Group

Represents a pool or group of Type 1 route distinguishers

Creating an inventory group based on this specification triggers the ADD_ROUTEDISTINGUISHER1_GROUP ruleset, which creates route distinguishers based on the values you enter in the Initial Route Distinguisher Range field.

The Route Distinguisher Type 1 Group specification includes the following characteristic:

  • Initial Route Distinguisher Range: Optional parameter that contains comma- or dash-separated values to specify a range of route distinguishers to be created; for example, 1.0.0.1:1-1.0.0.1:3, 1.0.0.1:5 will create a route distinguisher list of 1.0.0.1:1, 1.0.0.1:2, 1.0.0.1:3, and 1.0.0.1:5. This characteristic is a validated parameter.

Route Distinguisher Type 2 Group

Represents a pool or group of Type 2 route distinguishers

Creating an inventory group based on this specification triggers the ADD_ROUTEDISTINGUISHER2_GROUP ruleset, which creates route distinguishers based on the values you enter in the Initial Route Distinguisher Range field.

The Route Distinguisher Type 2 Group specification includes the following characteristic:

  • Initial Route Distinguisher Range: Optional parameter that contains comma- or dash-separated values to specify a range of route distinguishers to be created; for example, 1:1-1:3, 1:5 will create a route distinguisher list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.

Route Target Type 0 Group

Represents a pool or group of Type 0 route targets

Creating an inventory group based on this specification triggers the ADD_ROUTETARGET0_GROUP ruleset, which creates route targets based on the values you enter in the Initial Route Target Range field.

The Route Target Type 0 Group specification includes the following characteristics:

  • Initial Route Target Range: Contains comma- or dash-separated values to specify a range of route targets to be created; for example, 1:1-1:3, 1:5 will create a route target list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.

Route Target Type 1 Group

Represents a pool or group of Type 1 route targets

Creating an inventory group based on this specification triggers the ADD_ROUTETARGET1_GROUP ruleset, which creates route targets based on the values you enter in the Initial Route Target Range field.

The Route Target Type 1 Group specification includes the following characteristic:

  • Initial Route Target Range: Contains comma- or dash-separated values to specify a range of route targets to be created; for example, 1.0.0.1:1-1.0.0.1:3, 1.0.0.1:5 will create a route target list of 1.0.0.1:1, 1.0.0.1:2, 1.0.0.1:3, and 1.0.0.1:5. This characteristic is a validated parameter.

Route Target Type 2 Group

Represents a pool or group of Type 2 route targets

Creating an inventory group based on this specification triggers the ADD_ROUTETARGET2_GROUP ruleset, which creates route targets based on the values you enter in the Initial Route Target Range field.

The Route Target Type 2 Group specification includes the following characteristic:

  • Initial Route Target Range: Contains comma- or dash-separated values to specify a range of route targets to be created; for example, 1:1-1:3, 1:5 will create a route target list of 1:1, 1:2, 1:3, and 1:5. This characteristic is a validated parameter.

VLAN Domain

Broadcast domain for a particular VLAN

This configuration item has the following characteristic:

  • VLAN IDs to Add: Specifies values separated by commas or ranges separated by dashes, for a list of participating VLAN IDs.

    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 is 255 bytes.

    This characteristic is a validated parameter.


Logical Device Configuration Specifications

Table 4-3 lists and describes the Logical Device Configuration specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-3 Logical Device Configuration Specifications

Configuration Item Child Configuration Item Description

VPLS VSI Configuration

N/A

Defines the configuration parameters for the VPLS virtual switching instance (VSI)

This configuration item has the following characteristics:

  • VSI Name: Name of the VSI

  • MAC Table Size: Size of the table that stores VSI-related MAC addresses

  • Description: VSI description

  • Preferred Route Distinguisher Group: Name of a route distinguisher group that is used as the preferred location to assign route distinguishers when auto assignment is executed

VPLS VSI Configuration

Route Distinguisher

Enables you to assign a route distinguisher entity used in the VSI

VPLS VSI Configuration

Additional Characteristics

Enables you to assign additional characteristics to the VPLS VSI configuration specification


Logical Device Specifications

Table 4-4 lists and describes the Logical Device specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-4 Logical Device Specifications

Specification Description

Virtual Switching Instance

Defines a VSI


Network Configuration Specifications

Table 4-5 lists and describes the Network Configuration specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-5 Network Configuration Specifications

Configuration Item Child Configuration Item Description

VPLS-BGP Network

N/A

Contains configuration information for the BGP-based Layer 2 VPN

The VPLS-BGP Network configuration specification has the following characteristics:

  • VPN Network Topology: Topology used to implement a VPLS; for example, Hub and Spoke and Full Mesh

  • Number of Sites: Maximum number of sites allowed in a VPLS

  • Hierarchy Tier: Network tier within a hierarchical VPLS

  • Preferred Route Target Group: Route target group that is used as the preferred location to assign route targets when auto assignment is executed

  • Default Pseudo Wire Type: Default pseudo wire type used in the VPLS network

    You can directly overwrite the value of the pseudo wire type if you explicitly model a particular pseudo wire. You can create an explicit pseudo wire and set its type using network topology.

VPLS-BGP Network

Virtual Switching Instances

Collection of VSIs that constitute the VPLS network

The Virtual Switching Instances configuration item has a sub-item Virtual Switching Instance that represents a VPN instance on a provider edge (PE) router.

The Virtual Switching Instance sub-item has the following characteristic:

  • Membership Type: Role the VSI node plays in the VPLS network implemented using Hub and Spoke or Mesh topologies

VPLS-BGP Network

Route Target

Defines membership usage of a route target and enables you to assign a route target entity used in the network

The Route Target configuration item includes the following characteristics:

  • Mesh Action: The action that a VSI with Full Mesh Member set as its membership type takes on the route target. The action can be either to import routes from the VPN, to export routes to the VPN, or to do both

  • Hub Action: The action that a VSI with Hub Member set as its membership type takes on the route target. The action can be either to import routes from the VPN, to export routes to the VPN, or to do both

  • Spoke Action: The action that a VSI with Spoke Member set as its membership type takes on the route target. The action can be either to import routes from the VPN, to export routes to the VPN, or to do both

VPLS-BGP Network

Additional Characteristics

Enables you to assign additional characteristics to the VPLS -BGP network configuration specification

VPLS-LDP Network

N/A

Contains configuration information for the LDP-based Layer 2 VPN

The VPLS-LDP network configuration specification has the following characteristics:

  • VPN Network Topology: Topology used to implement a VPLS; for example, Hub and Spoke and Full Mesh

  • Hierarchy Tier: Network tier within a hierachial VPLS

  • Default Pseudo Wire Type: The default pseudo wire type used in the VPLS network

    You can directly overwrite the value of the pseudo wire type if you explicitly model a particular pseudo wire. You can create an explicit pseudo wire and set its type using network topology.

VPLS-LDP Network

Virtual Switching Instances

Collection of VSIs that constitute the VPLS network

The Virtual Switching Instances configuration item has a sub-item Virtual Switching Instance that represents a VPN instance on a PE router.

The Virtual Switching Instance sub-item has the following characteristic:

  • Membership Type: Role the VSI node plays in the VPLS network implemented using Hub and Spoke or Mesh topologies

VPLS-LDP Network

Additional Characteristics

Enables you to assign additional characteristics to the VPLS -LDP network configuration specification


Network Edge Specifications

Table 4-6 lists and describes the Network Edge specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-6 Network Edge Specifications

Specification Description

Pseudo Wire Edge

Network edge in a Oracle Communications Unified Inventory Management (UIM) network topology that can be associated with a pseudo wire


Network Node Specifications

Table 4-7 lists and describes the Network Node specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-7 Network Node Specifications

Specification Description

Virtual Switching Instance Node

Represents a VSI in a VPLS network

MPLS Label Router

Represents a router in an multiprotocol label switching (MPLS) core network


Network Specifications

Table 4-8 lists and describes the Network specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-8 Network Specifications

Specification Description

VPLS Network

A provider-provisioned VPN that provides multipoint VPLS

MPLS Core Network

Defines an MPLS core switching network

The MPLS Layer 2 VPNs are implemented on top of MPLS networks. This specification is used to represent the PE and provider core devices that constitute the MPLS core network


Pipe Specifications

Table 4-9 lists and describes the Pipe specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-9 Pipe Specifications

Specification Description

Pseudo Wire

Describes the pseudo wires connecting the Layer 2 VPN nodes

Pseudo wires are assigned to PE devices at the edges of a provider network.

This specification has the following characteristics:

  • Pseudo Wire ID: A non-zero 32-bit connection ID that combines with the value of the Pseudo Wire Type characteristic to uniquely identify a pseudo wire

  • Pseudo Wire Type: A 15-bit value that identifies the type of encapsulation used on a pseudo wire

  • Group ID: An arbitrary 32-bit value that represents a group of pseudo wires used to create groups in the pseudo wire space; this is intended to be used as a port index or a virtual tunnel index.


Pipe Termination Point Specifications

Table 4-10 lists and describes the Pipe Termination Point specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-10 Pipe Termination Point Specifications

Specification Description

Pseudo Wire Termination Point

Identifies the end points of a pseudo wire pipe that provides point-to-point connectivity between the two points


Place Configuration Specifications

Table 4-11 lists and describes the Place Configuration specifications included in the Layer 2-specific cartridges of the technology pack.

Table 4-11 Place Configuration Specifications

Configuration Item Child Configuration Item Description

VLL Ethernet Port-based Termination

N/A

Configuration that represents the port-based Layer 2 VPN termination objects that are being configured

VLL Ethernet Port-based Termination

L2 QOS

Optional extensibility configuration item that the user may want to use to extend the functionality of the L2 VPN Technology Pack using Layer 2 quality of service (QoS) parameters

VLL Ethernet Port-based Termination

Provide Edge Interface

Service provider interface or port used to receive customer traffic

VLL Ethernet VLAN-based Termination

N/A

Configuration that represents the VLAN-based Layer 2 VPN termination objects that are being configured

VLL Ethernet VLAN-based Termination

L2 QOS

Optional extensibility configuration item that the user may want to use to extend the functionality of the L2 VPN Technology Pack using Layer 2 quality of service (QoS) parameters

VLL Ethernet VLAN-based Termination

Provider Edge Interface

Service provider interface or port used to receive customer traffic

VLL Ethernet VLAN-based Termination

VLAN Control

Configuration that provides parameters to control VLAN access

This configuration item has the following sub-items:

  • C-VLAN ID List: List of customer VLAN IDs entering a VPLS over a particular PE interface

  • CE-VLAN ID: Customer Edge VLAN ID used to tag untagged traffic entering the VPLS over a particular PE instance

  • S-VLAN ID: Service provider VLAN ID wrapping a Customer VLAN ID

The S-VLAN ID configuration item has the following characteristics:

  • Requested VLAN: Flag indicating if the S-VLAN ID is treated as a requested VLAN ID. A requested VLAN ID is be used by a PE that is incapable of rewriting the 802.1Q Ethernet VLAN tag on the output. If the ingress PE receives this request, it must rewrite the VLAN ID contained inside the VLAN tag at the input to match the requested VLAN ID

  • On Attachment Circuit: Flag indicating if the S-VLAN ID is already present on the attachment circuit traffic

VPLS Port Based Non Switching Termination

N/A

Configuration that represents the VPLS port-based Layer 2 VPN non-switching termination objects that are being configured

VPLS Port Based Non Switching Termination

Attachment Circuit Termination

Specifies the PE interface that receives customer edge (CE) device traffic towards the PE; specifies the path for directing the traffic at the interface to the remote VSI; also specifies the remote VSI.

The Attachment Circuit Termination configuration item has the following characteristic:

  • Pseudo Wire Type: Type of encapsulation used on the pseudo wire connecting the termination PE interface and VSI on a switching router that hosts the remote VSI

  • Site ID: A 16-bit value that is assigned to each customer site connected to a PE router

    The Site ID must be unique within the particular customer network.

The Attachment Circuit Termination configuration item has the following sub-items:

  • Provider Edge Interface: Service provider port used to receive customer traffic toward the PE device

  • Remote Virtual Switching Instance: VSI hosted by a router in the service provider network to switch incoming customer traffic at the PE router to the destination

    A remote VSI is used by a non-switching termination as an entry into a VPLS for its customer traffic.

  • Pseudo Wire: Represents a Layer 2 connection between the termination PE interface and VSI on a switching router that hosts the remote VSI

VPLS Port Based Non Switching Termination

L2 QOS

Optional extensibility configuration item that the user may want to use to extend the functionality of the L2 VPN Technology Pack using Layer 2 quality of service (QoS) parameters

VPLS Port Based Switching Termination

N/A

Configuration that represents the VPLS port-based Layer 2 VPN switching termination objects that are being configured

VPLS Port Based Switching Termination

Attachment Circuit Termination

Specifies the PE interface that receives CE device traffic towards the PE; also specifies the VSI

The Attachment Circuit Termination configuration item has the following characteristic:

  • Site ID: A 16-bit value that is assigned to each customer site connected to a PE router

    The Site ID must be unique within the particular customer network

The Attachment Circuit Termination configuration item has the following sub-items:

  • Provider Edge Interface: Service provider port used to receive customer traffic toward the PE device

  • Virtual Switching Instance: VSI hosted by the PE router in the service provider network to switch incoming customer traffic to the destination

VPLS Port Based Switching Termination

L2 QOS

Optional extensibility configuration item that the user may want to use to extend the functionality of the L2 VPN Technology Pack using Layer 2 quality of service (QoS) parameters

VPLS VLAN Based Non Switching Termination

N/A

Configuration that represents the VPLS VLAN-based Layer 2 VPN non-switching termination objects that are being configured

VPLS VLAN Based Non Switching Termination

Attachment Circuit Termination

Specifies the PE interface that receives CE device traffic towards the PE; specifies the path for directing the traffic at the interface to the remote VSI; also specifies the remote VSI

The Attachment Circuit Termination configuration item has the following characteristic:

  • Pseudo Wire Type: Type of encapsulation used on the pseudo wire connecting the termination PE interface and VSI on a switching router that hosts the remote VSI

  • Site ID: A 16-bit value assigned to each customer site connected to a PE router

    The Site ID must be unique within the particular customer network.

The Attachment Circuit Termination configuration item has the following sub-items:

  • Provider Edge Interface: Service provider port used to receive customer traffic toward the PE device

  • Pseudo Wire: Represents a Layer 2 connection between the termination PE interface and VSI on a switching router that hosts the remote VSI

  • Remote Virtual Switching Instance: VSI hosted by a router in the service provider network to switch incoming customer traffic at the PE router to the destination

    A remote VSI is used by a non-switching termination as an entry into a VPLS for its customer traffic.

VPLS VLAN Based Non Switching Termination

VLAN Control

Configuration that provides parameters to control VLAN access

This configuration item has the following sub-items:

  • C-VLAN ID List: List of customer VLAN IDs entering a VPLS over a particular PE interface

  • CE-VLAN ID: Customer Edge VLAN ID used to tag untagged traffic entering the VPLS over a particular PE instance

  • S-VLAN ID: Service provider VLAN ID wrapping a Customer VLAN ID

The S-VLAN ID configuration item has the following characteristics:

  • Requested VLAN: Flag indicating if the S-VLAN ID is treated as a requested VLAN ID. A requested VLAN ID is be used by a PE that is incapable of rewriting the 802.1Q Ethernet VLAN tag on the output. If the ingress PE receives this request, it must rewrite the VLAN ID contained inside the VLAN Tag at the input to match the requested VLAN ID.

  • On Attachment Circuit: Flag indicating if the S-VLAN ID is already present on the attachment circuit traffic

VPLS VLAN Based Non Switching Termination

L2 QOS

Optional extensibility configuration item that the user may want to use to extend the functionality of the L2 VPN Technology Pack using Layer 2 quality of service (QoS) parameters

VPLS VLAN Based Switching Termination

N/A

Configuration that represents the VPLS VLAN-based Layer 2 VPN switching termination objects that are being configured

VPLS VLAN Based Switching Termination

Attachment Circuit Termination

Specifies the PE interface that receives CE device traffic towards the PE; also specifies the VSI

The Attachment Circuit Termination configuration item has the following characteristic:

  • Site ID: A 16-bit value assigned to each customer site connected to a PE router

    The Site ID must be unique within the particular customer network.

The Attachment Circuit Termination configuration item has the following sub-items:

  • Provider Edge Interface: Service provider port used to receive customer traffic toward the PE device

  • Virtual Switching Instance: VSI hosted by the PE router in the service provider network to switch incoming customer traffic to the destination

VPLS VLAN Based Switching Termination

VLAN Control

Configuration that provides parameters to control VLAN access

This configuration item has the following sub-items:

  • C-VLAN ID List: List of customer VLAN IDs entering a VPLS over a particular PE interface

  • CE-VLAN ID: Customer Edge VLAN ID used to tag untagged traffic entering the VPLS over a particular PE instance

  • S-VLAN ID: Service provider VLAN ID wrapping a customer VLAN ID

The S-VLAN ID configuration item has the following characteristics:

  • Requested VLAN: Flag indicating if the S-VLAN ID is treated as a requested VLAN ID. A requested VLAN ID is be used by a PE that is incapable of rewriting the 802.1Q Ethernet VLAN tag on the output. If the ingress PE receives this request, it must rewrite the VLAN ID contained inside the VLAN Tag at the input to match the requested VLAN

  • On Attachment Circuit: Flag indicating if the S-VLAN ID is already present on the attachment circuit traffic

VPLS VLAN Based Switching Termination

L2 QOS

Optional extensibility configuration item that the user may want to use to extend the functionality of the L2 VPN Technology Pack using Layer 2 quality of service (QoS) parameters


Place Specifications

Table 4-12 lists and describes the Place specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-12 Place Specifications

Specification Description

VLL Termination

Configuration that represents the Layer 2 VPN termination objects that are being configured

VPLS Non Switching Termination

Configuration that represents the VPLS Layer 2 VPN non-switching termination objects that are being configured

A VPLS non-switching termination represents a termination on a router that does not have the logic to switch Ethernet traffic to the destination. A non-switching router does not support VSI.

VPLS Switching Termination

Configuration that represents the VPLS Layer 2 VPN switching termination objects that are being configured

A VPLS switching termination represents a termination on a router that has the logic to switch Ethernet traffic to the destination. A switching router supports VSI.


Service Configuration Specifications

Table 4-13 lists and describes the Service Configuration specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-13 Service Configuration Specifications

Configuration Item Child Configuration Item Description

Virtual Leased Line Service

N/A

Represents a collection of VLLs

Each VLL has its own service ID.

This configuration item has the following characteristic:

  • Default Pseudo Wire Type: Default value assumed in case a user does not explicitly specify the pseudo wire type when configuring a pseudo wire

Virtual Leased Line Service

Virtual Leased Line

Represents a connection between two customer edge (CE) devices at two different locations

A VLL transfers Layer 2 frames transparently across the CE devices.

This configuration item has the following sub items:

  • Service ID: Unique identifier for the VLL service

  • Termination: Termination point for the VLL service

  • Pseudo Wire: Identifies the pseudo wire between two termination points

Virtual Private LAN Service

N/A

Represents the multipoint VPLS between the PE routers participating in the VPN service

Virtual Private LAN Service

VPLS Terminations

Represents the termination points of the VPLS

This configuration item has the following sub-item:

  • VPLS Termination: Represents an instance of a VPLS termination point

Virtual Private LAN Service

VPLS Network

Represents a collection of VPLS networks that constitute a VPN

Virtual Private LAN Service

MPLS Core Network

Defines an MPLS core switching network

Virtual Private LAN Service

VPLS Service ID

Represents a unique identifier for an instance of the VPLS

VLAN ID List

N/A

Configuration that represents a generic list of VLAN identifiers for a VPLS or VLL service that is not necessarily tied to a PE interface

This configuration item has the following characteristic:

  • VLAN ID Domain: VLAN domain to which the VLAN ID list belongs

VLAN ID List

VLAN ID

VLAN identifier used by the service provider to identify traffic on a particular instance of VPLS or VLL service


Service Specifications

Table 4-14 lists and describes the Service specifications included in the Layer 2 VPN-specific cartridges of the technology pack.

Table 4-14 Layer 2 VPN Service Specifications

Specification Description

Virtual Leased Line Service

Represents a collection of VLLs

Each VLL has its own service ID.

Virtual Private LAN Service

Represents the multipoint VPLS between the PE routers participating in the VPN service

VLAN ID List

Represents a generic list of VLAN identifiers for a VPLS or VLL service that is not necessarily tied to a PE interface


Rulesets Included in the Technology Pack

Rules are executed at the point identified in the corresponding ruleset extension point specification. The identified point corresponds to a class or method signature in a base extension point that is included in the ora_uim_baseextpts cartridge. The Layer 2 VPN cartridge requires the ora_uim_baseextpts cartridge to execute the rules. See "Deploying the Layer 2 VPN Technology Pack" for more information. You can modify the rules and their extension points to meet your business needs. See UIM Developer's Guide for more information.

Table 4-15 lists the rulesets included in the L2 VPN Technology Pack.

Table 4-15 Rulesets in the Layer 2 VPN Technology Pack

Ruleset/Ruleset Extension Points Functionality

ASSOCIATE_WITH_VLANDOMAIN

ASSOCIATE_WITH_VLANDOMAIN_EXT

Associates a newly created VLAN resource with a VLAN domain

CREATE_VLAN_RANGE

CREATE_VLAN_RANGE_EXT

Creates a VLAN ID domain with a range of VLAN IDs

DELETE_VLAN_RANGE

DELETE_VLAN_RANGE_EXT

Deletes a VLAN ID range

UPDATE_VLAN_RANGE

UPDATE_VLAN_RANGE_EXT

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

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_VLAN_DOMAIN

PREVENT_DISASSOCIATION_FROM_VLAN_DOMAIN_EXT

Prevents the removal of a VLAN ID from a VLAN ID domain

ADD_ROUTEDISTINGUISHER0_GROUP

ADD_ROUTEDISTINGUISHER0_GROUP_EXT

Creates a Type 0 route distinguisher group based on the values in the Initial Route Distinguisher Range field

ADD_ROUTEDISTINGUISHER1_GROUP

ADD_ROUTEDISTINGUISHER1_GROUP_EXT

Creates a Type 1 route distinguisher group based on the values in the Initial Route Distinguisher Range field

ADD_ROUTEDISTINGUISHER2_GROUP

ADD_ROUTEDISTINGUISHER2_GROUP_EXT

Creates a Type 2 route distinguisher group based on the values in the Initial Route Distinguisher Range field

ADD_ROUTETARGET0_GROUP

ADD_ROUTETARGET0_GROUP_EXT

Creates a Type 0 route target group based on the values in the Initial Route Target Range field

ADD_ROUTETARGET1_GROUP

ADD_ROUTETARGET1_GROUP_EXT

Creates a Type 1 route target group based on the values in the Initial Route Target Range field

ADD_ROUTETARGET2_GROUP

ADD_ROUTETARGET2_GROUP_EXT

Creates a Type 2 route target group based on the values in the Initial Route Target Range field

ASSOCIATE_WITH_ROUTEDISTINGUISHER0_GROUP

ASSOCIATE_WITH_ROUTEDISTINGUISHER0_GROUP_EXT

Associates a Type 0 route distinguisher group with a range of route distinguishers

ASSOCIATE_WITH_ROUTEDISTINGUISHER1_GROUP

ASSOCIATE_WITH_ROUTEDISTINGUISHER1_GROUP_EXT

Associates a Type 1 route distinguisher group with a range of route distinguishers

ASSOCIATE_WITH_ROUTEDISTINGUISHER2_GROUP

ASSOCIATE_WITH_ROUTEDISTINGUISHER2_GROUP_EXT

Associates a Type 2 route distinguisher group with a range of route distinguishers

ASSOCIATE_WITH_ROUTETARGET0_GROUP

ASSOCIATE_WITH_ROUTETARGET0_GROUP_EXT

Associates a Type 0 route target group with a route target list

ASSOCIATE_WITH_ROUTETARGET1_GROUP

ASSOCIATE_WITH_ROUTETARGET1_GROUP_EXT

Associates a Type 1 route target group with a route target list

ASSOCIATE_WITH_ROUTETARGET2_GROUP

ASSOCIATE_WITH_ROUTETARGET2_GROUP_EXT

Associates a Type 2 route target group with a route target list

DELETE_ROUTEDISTINGUISHER0_GROUP

DELETE_ROUTEDISTINGUISHER0_GROUP_EXT

Deletes a Type 0 route distinguisher group from a range of route distinguishers

DELETE_ROUTEDISTINGUISHER1_GROUP

DELETE_ROUTEDISTINGUISHER1_GROUP_EXT

Deletes a Type 1 route distinguisher group from a range of route distinguishers

DELETE_ROUTEDISTINGUISHER2_GROUP

DELETE_ROUTEDISTINGUISHER2_GROUP_EXT

Deletes a Type 2 route distinguisher group from a range of route distinguishers

DELETE_ROUTETARGET0_GROUP

DELETE_ROUTETARGET0_GROUP_EXT

Deletes a Type 0 route target group from a list of route targets

DELETE_ROUTETARGET1_GROUP

DELETE_ROUTETARGET1_GROUP_EXT

Deletes a Type 1 route target group from a list of route targets

DELETE_ROUTETARGET2_GROUP

DELETE_ROUTETARGET2_GROUP_EXT

Deletes a Type 2 route target group from a list of route targets

PREVENT_DISASSOCIATION_FROM_RTRD_GROUP

PREVENT_DISASSOCIATION_FROM_RTRD_GROUP_EXT

Prevents the dissociation of a route target group from a list of route targets

VALIDATE_RTRD_FORMAT

VALIDATE_RTRD_FORMAT_EXT

Validates that the format of a route target or route distinguisher is in the correct dash- or comma-separated format

L2VPN_ALLOCATE_ALL_BGP_NETWORK

L2VPN_ALLOCATE_ALL_BGP_NETWORK_EXT

Automatically assign route targets to all BGP-based network configurations

L2VPN_ALLOCATE_ALL_LDP_NETWORK

L2VPN_ALLOCATE_ALL_LDP_NETWORK_EXT

Automatically assigns route targets to all LDP-based network configurations

L2VPN_ALLOCATE_ALL_SERVICE

L2VPN_ALLOCATE_ALL_SERVICE_EXT

Automatically assigns service IDs to all Layer 2 VPLSs

L2VPN_ALLOCATE_ALL_VLL_SERVICE

L2VPN_ALLOCATE_ALL_VLL_SERVICE_EXT

Automatically assigns service IDs to all VLL services

L2VPN_ALLOCATE_ALL_VSI

L2VPN_ALLOCATE_ALL_VSI_EXT

Automatically assigns route distinguishers to VSIs in a particular network

L2VPN_VALIDATE_NETWORK

L2VPN_VALIDATE_NETWORK_EXT

Validates VPLS network configurations regardless of the type of network

For a VPLS network, the value of Pseudo Wire Type should be either Ethernet or Ethernet VLAN.

There should not be any orphan configuration items for VPLS networks.

There should not be any duplicate route targets in a BGP-based VPLS network.

A VPLS network with a Hub and Spoke topology should have at least one hub.

L2VPN_VALIDATE_PLACE

L2VPN_VALIDATE_PLACE_EXT

Validates the VPLS Termination configurations

There should not be any orphan configuration items for VPLS terminations.

For a VPLS non-switching termination, the PE interface and remote VSI should be on separate devices.

For a VPLS switching termination, the PE interface and remote VSI should be on separate devices.

Triggered by the Validate menu item in the Related Pages menu.

L2VPN_VALIDATE_SERVICE

L2VPN_VALIDATE_SERVICE_EXT

Validates that there are no termination duplicates in the Layer 2 VPN

L2PVN_VALIDATE_VLAN_LIST

L2PVN_VALIDATE_VLAN_LIST_EXT

Validates that the VLAN ID list does not contain any duplicate VLAN IDs

All the VLAN IDs in the VLAN ID list must belong to the same pool.

L2VPN_VALIDATE_VLL_PLACE

L2VPN_VALIDATE_VLL_PLACE_EXT

Validates VLL termination configurations

There should not be any orphan configuration items for VLL terminations.

VLL Termination PE interfaces should be on separate devices.

L2VPN_VALIDATE_VLL_SERVICE

L2VPN_VALIDATE_VLL_SERVICE_EXT

Validates that the VLL service contains either port- or VLAN-based service configurations

There should not be any orphan configuration items for a VLL service.

A VLL service must not have termination duplicates.

L2VPN_VALIDATE_VSI

L2VPN_VALIDATE_VSI_EXT

Validates that, depending on the type of network, VSIs are either of type border gateway protocol (BGP) or label distribution protocol (LDP)

A VSI must be associated with a data networking device.

There should not be any orphan configuration items on a VPLS VSI.

There should not be any VSI duplicates in the VPLS network.

The VSI membership should be aligned with the network topology.

VSIs must exist for VPLS service terminations in a VPLS network.

A VPLS Non-Switching Termination remote VSI should belong to at least one LDP-based network.