Managing Virtual Connection Endpoints (VCEs)

About Virtual Connection Endpoints (VCEs)

A Virtual Connection Endpoint (VCE) defines the NFV-based interface to use when generating NFV-based probe sessions via sensor orchestration capabilities within Provider Connectivity Assurance (formerly Skylight orchestrator). The VCE defines the NFV IP address and VLAN header for a specific remote device. When probes are generated using a VCE, the NFV IP address and VLAN header are used to encapsulate the packets associated with the probe sessions to be generated. The VCE type is also used to determine how to construct the bridge component and component ID required for Connectivity Fault Management (CFM).

The special features of a VCE include:

• A separate, dedicated IP domain for each VCE. The domain includes the VCE's default gateway and can include static routes.
• A VCE typically operates at Layer 2 but can also operate at Layer 3.
• Two termination points (TP A and TP Z) that support VLAN tagging actions on probe frames.

• A VCE can perform one of the following actions on the VLAN tags in probe frames:
  • tag: Add a VLAN tag to untagged frames
  • translate: Change the VLAN ID of tagged frames
  • untag: Remove a VLAN tag from tagged frames
  • preserve: Keep the VLAN tag of tagged frames
  • none: Do not perform any action

For NFV probes, a single VCE can only perform one action. For CFM, it is possible to concatenate several VCEs to perform a series of actions.

• A VCE will respond to a ping or trace route request.

A VCE can be used to generate and manage multiple NFV-based probe sessions. VCEs support IPv4 and IPv6 addresses.

To set up an NFV TWAMP or NFV ETH-DMM session on a Provider Connectivity Assurance (formerly Skylight) module through sensor orchestration capabilities within Provider Connectivity Assurance, a suitable VCE must have been defined for the Provider Connectivity Assurance module on the Sensor Control instance.

This article explains how to set up VCEs. For more information about setting up NFV sessions on Provider Connectivity Assurance, see the Sensor Orchestration as a Capability within Provider Connectivity Assurance section.

Parts of a VCE

The VCE is based on the 802.1Q bridge component. It consists of the following three parts:

• TP A: A virtual port on the incoming side of the Provider Connectivity Assurance module. It can be on the UNI (User Network Interface) or the NNI (Network Network Interface) side of the module. By default TP A is UNI.
• Relay: An action that will be performed on the VLAN tagging of incoming frames.
• TP Z: A virtual port on the outgoing side of the module. It can be on the UNI (User Network Interface) or the NNI (Network Network Interface) side of the module. By default TP Z is NNI.