- Print
- PDF
Setting Up a Virtual Connection Access (VCA) Configuration Job
The Virtual Connection Access (VCA) functionality is used to define the end-to-end connectivity between two ports of an Cisco Provider Connectivity Assurance Sensor or Provider Connectivity Assurance Sensor Module. A VCA is composed of one or more Virtual Connection Endpoints (VCE).
For an introduction to VCAs and VCEs and detailed descriptions of how to set them up, see the appropriate user documentation:
- Provider Connectivity Assurance Sensors (GT, LX and LT models)
For detailed information, see the user material or online help for that model. - Second generation modules (modules that are remote devices of a Provider Connectivity Assurance Sensor Control).
For detailed information, see the Assurance Sensor Control Features and User Material.
To set up a configuration job for a VCA
Access the page Commission ▶ Jobs.
To add a new configuration job, click the button (above the list of existing jobs).
You can also:
- Copy a job by selecting it in the list and clicking the duplicate button .
- Edit an existing job by double-clicking the job in the list.
The Job configuration dialog is displayed.
Set all common configuration job settings, as described in "Creating Configuration Jobs in GUI Mode" and in "Creating Configuration Jobs Using Data Sets".
Select Virtual Connection Access in the left pane. The Virtual Connection Access tab is displayed in the right pane.
Complete all fields of the Virtual Connection Access tab as required. Note that the Virtual Connection Access tab includes three sub-tabs. For more information on the parameters, see the table below this procedure.
Use the Add button or Duplicate button to add VCAs as required.
Note: When duplicating a row, always select the row to duplicate before clicking the Duplicate button.
Click Apply, then click Close.
Click the Refresh button to refresh the user interface.
Virtual Connection Access (VCA) tab (Commission ▶ Jobs)
VCA configuration
Parameter | Description |
---|---|
VCA name | A unique name for the VCA. If the job will be executed on an Assurance Sensor, the name must uniquely identify the VCA on the Assurance Sensor. If the job will be executed on an Assurance Sensor Module, the name must uniquely identify the VCA on the Assurance Sensor Control with which the Assurance Sensor Module is associated. |
VCA list | A comma-separated list of VCE names. The VCEs must be of type Operator or Customer or an implicit VCA containing a VCE tunnel instance referenced by name. |
AtoZ Classification and ZtoA Classification
Parameters required for a classification profile are the same in either direction (AtoZ or ZtoA). Not applicable to Assurance Sensors. Optional for Assurance Sensor Modules.
Parameter | Description |
---|---|
Name | Unique name for the classification profile. |
Filter type | The filter type used to classify traffic. Possible values:
|
Filter name | Select one of the filters available for the type selected in the Filter type field. The values listed below are the default filters that are available for Assurance Sensor Modules. Additional filters may have been configured. You can enter the name of a custom filter manually in this field. Layer-2:
|
Action | The action that will be applied to traffic that matches the filter. Possible values:
|
CoS mapping order | Defines the order in which Class of Service (CoS) mapping will be applied. Possible values:
|
PCP Mapping Enable | Check this box to enable PCP mapping as one of the CoS mapping options that will be applied. |
DSCP / IP Mapping Enable | Check this box to enable DSCP/IP mapping as one of the CoS mapping options that will be applied. If you enable DSCP/IP mapping, you must also select a value in the DSCP/IP pre mapping dropdown list. |
DSCP / IP pre mapping | Specifies the type of priority upon which the bandwidth regulator set is based. Possible values:
|
Direct PCP | Sets the PCP value used for Direct Mapping. Possible values: Integer from 0 to 7 |
CFI DEI | Sets the CFI/DEI value used for Direct Mapping.
This parameter should be set to 0 for connections to Ethernet switches. CFI is used to ensure compatibility between Ethernet type networks and Token Ring type networks. If a frame received at an Ethernet port has a CFI set to 1, the frame should not be forwarded as is to an untagged port. |
© 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