Adding Virtual Connection Endpoints (VCEs)
  • 23 Jan 2024
  • 4 Minutes to read
  • Contributors
  • PDF

Adding Virtual Connection Endpoints (VCEs)

  • PDF

Article summary

Depending on the use case, a VCE element has a “component type” attribute: Customer (CVLAN), Operator (S-VLAN) or Tunnel (S-VLAN):

  • A Tunnel VCE is used for trunking use cases (Access Provider).
  • An Operator VCE is used to tag the data frames in the operator's network.
  • A Customer VCE is used to handle customer (tagged or untagged) traffic (usually at UNI and at VUNI).

To add a new VCE or edit an existing VCE

  1. Access Virtual Connection ▶VCE ▶Configuration.
    A list of all existing VCEs and their current status is displayed.

  2. Click Add to create a new VCE or click the Name of an existing VCE to edit its settings.

  3. Enter values in the required fields, then click Apply.


Note: A type Tunnel VCE will create an implicit VCA which can be included within another VCA. Also, a VCE with both TP A and TP Z ports configured as external will generate an implicit VCA.

For more information on specific parameters, refer to the following tables.

VCE Configuration and Status (Virtual Connection ▶VCE ▶Configuration)

ParameterDescription
VCE NameA name that uniquely identifies the VCE on the Skylight element: LX.
TypeType indicates which type of VCE is being created. The default is Customer. The available options are:
  • Customer
  • Operator
  • Tunnel
TPIDThe TPID (Tag Protocol Identifier). Specifies the type of VLANtagging used in the frames that will be handled by this VCE. Available tag protocol options are:
  • 0x8100: C-VLAN
  • 0x88a8: S-VLAN
  • 0x9100: T-VLAN
Component IDThe ID of the Component into which the VCE will be attached. Specifying 0 indicates that the system shall automatically assign a component ID.
Frame TypeSpecifies the type of frames that will be selected for handling by this VCE.

Available options are:

  • all-to-one: Multiple frames that are associated with a single VLAN. Used for port-based service interface definition.
  • untagged: Frames that are not associated with a VLAN.
  • vlan-tagged: Frames that are associated with a VLAN.
  • any: Frames that are associated with any VLAN.
Relay ActionSelect the action to be performed on incoming frames.
  • tag: Add a VLAN tag to untagged frames.
  • untag: Remove a VLAN tag from tagged frames.
  • preserve: Keep the VLAN tag of tagged frames.
  • translate: Change the VLAN ID of tagged frames.
A VCE can only perform one action. If you need to perform a series of actions, you must define multiple VCEs.
TP AUse this parameter to configure the incoming Terminal Point (TP). The TP A is a virtual UNI (User Network Interface) port. It can be either:
  • External: is used to identify the TP as being connected to an external port.
  • Internal: is used to identify the TP as being connected to another VCE.
TP ZUse this parameter to configure the outgoing Terminal Point (TP). The TP Z is always a virtual NNI (Network Network Interface) port. It can be either:
  • External: is used to identify the TP as being connected to an external port.
  • Internal: is used to identify the TP as being connected to another VCE.
TP A PortThe TP A Port defines the Ingress port of VCE.
TP Z PortThe TP Z Port defines the Egress port of VCE.
TP A VIDThe TP A VID is used to assign a VID to frames. When Frame Type is configured as 'untagged' the option is unavailable. A single VLAN-ID chosen from the range 1–4094 is assigned to this parameter. If the Frame Type is Customer, multiple VLANIDs may be specified in the following format: [-],[-] ...(e.g. 1, 2, 100–200 will include VIDs 1, 2, 100, 101, 102, 103... 200).
TP Z VIDThe TP Z VID is applicable when 'vid-relay-action' is set to 'translate' or 'tag'. Only a single value for the VID may be specified.

CoS Mapping

ParameterDescription
TP A PCP MappingThe TP A PCP Mapping is the ingress CoS profile name with the type PCP.
TP Z PCP MappingThe TP Z PCP Mapping is the egress CoS profile name with the type PCP.

VCE Examples

This section provides examples of how to set up the VCEs required for two different types of sessions on the unit:

VCE Settings Example #1: C-VLAN Bridge

ParameterDescription
VCE NameC_VID_1000
TypeCustomer
TPID0x8100
Frame typeVlan-tagged
VID Relay ActionPreserve
TP A PortPORT-1
TP A VID1000
TP A PCP Mapping
TP Z PortPORT-8
TP Z VID1000
TP Z PCP Mapping
Component ID1

VCE Settings Example #2: Tagged Service Interface

ParameterDescription
VCE NameC_VID_1000
TypeCustomer
TPID0x8100
Frame typeVlan-tagged
VID Relay ActionPreserve
TP A PortPORT-6
TP A VID1000
TP A PCP Mapping
TP Z PortPORT-8
TP ZInternal
TP Z VID1000
TP Z PCP Mapping
Component ID1

VCE Settings Example #3: Operator

ParameterDescription
VCE NameS_VID_5
TypeOperator
TPID0x88A8
Frame typeall-to-one
VID Relay ActionTag
TP AInternal
TP A VID
TP A PCP Mapping
TP ZPORT-5
TP Z VID5
TP Z PCP Mapping
Component ID2

© 2024 Cisco and/or its affiliates. All rights reserved.
 
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms

For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks



Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.