The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
For a detailed overview of the provisioning support in Cisco EPN Manager , see Provision Circuits/VCs.
To create and provision a new circuit/VC:
Step 1 | From the left sidebar, choose . | ||
Step 2 | Click Device Groups, and then select the location in which you want to create the circuit/VC. | ||
Step 3 | Close the Device Groups popup window. | ||
Step 4 | In the Network Topology window, click Circuits/VCs | ||
Step 5 | Click the '+'
icon to open the Provisioning Wizard in a new pane to the right of the map.
| ||
Step 6 | From the Technology drop-down list, choose the required technology. For example, if you are creating a circuit for Optical/DWDM network, choose Optical. | ||
Step 7 | In the Service Type area, choose the type of circuit/VC you want to create. For example, if you are creating a circuit/VC for Optical/DWDM network, the various circuit types include OCHNC WSON, OCHCC WSON, OCH-Trail WSON, OCH-Trail UNI, ODU UNI, ODU Tunnel and OPU over ODU. | ||
Step 8 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||
Step 9 | Click Next to go to the Customer Service Details page. | ||
Step 10 | (Optional) Select the customer for whom the circuit/VC is being created. If there are no customers in the list, go to to create the customer in the system, and then go to the Provisioning Wizard to start provisioning the circuit/VC. | ||
Step 11 | Enter the service name and its description. | ||
Step 12 | From the Deployment Action drop-down list, choose the action that you want to perform after defining the attributes for the circuit/VC. The options are: | ||
Step 13 | Click Next to choose the endpoints and define the attributes based on the technology you have selected. | ||
Step 14 | Click Submit. Depending on the deployment action you have chosen, the relevant action will be performed. That is, if you have chosen to preview the configuration, the preview page will be displayed where you can view the configurations, and then click Deploy. If you have chosen to deploy, the configurations will be directly deployed to the relevant devices. | ||
Step 15 | (Optional)
Click the
Leave
this View button to continue using
Cisco EPN Manager
and to enable the service deployment to continue in the background.
|
The circuit/VC should be
added to the list in the Circuits/VCs pane in the Network Topology window. To
check the provisioning state, click the i icon next to the circuit/VC name to
see the Circuit/VC 360 view.
When you deploy a service to devices, if the devices are pre-occupied or busy, the service request created waits for a pre-configured period of time to acquire a ‘device lock’ for deploying the service. By default, the timeout value is set to 60 minutes.
To change the default timeout value:
When you deploy a circuit/VC, Cisco EPN Manager performs configuration changes in all the participating devices. Only when the configuration changes are successfully deployed to all the devices, the circuit/VC will be considered as successfully provisioned. If the deployment of configuration changes fails in any one of the participating device, Cisco EPN Manager rolls back the configuration changes made so far in all the devices.
Deployment succeeds in all the participating devices; roll back is not initiated—In this scenario, all devices are successfully configured and the circuit provisioning is successful.
Deployment fails; roll back is initiated and succeeds—In this scenario, when configuring multiple devices, the configuration fails in one of the device. The failure could be due to various reasons, for example, the device has declined the configuration. Cisco EPN Manager identifies the failure and successfully rolls back all the configuration changes that were made on all the devices. In this scenario, all device configurations are restored to the states, which were there before the deployment was attempted.
Here is an example with three devices, A, B, and C, which are configured in a sequential order to provision a circuit. The configuration changes are deployed successfully in device A, but the deployment fails in device B. Cisco EPN Manager detects the failure and stops further configuration in devices B and C. It rolls back the configuration in the reverse order of provisioning, that is, it first rolls back the device B, followed by device A. Following are the actions that are performed sequentially in the three devices:
Device C—Rollback is not required for device C because there were no changes deployed to the device. This is because the configuration failure was detected in device B before configurations changes were sent to device C.
Device B—Cisco EPN Manager checks if there are any configuration changes made on this device before the deployment failed. If there are any changes, the partial configuration on this device is removed and the device is rolled back to the previous configuration.
Device A—Cisco EPN Manager performs a complete roll back in device A, where all the configuration changes that were successfully deployed earlier are removed and the device is rolled back to the previous configuration.
Deployment fails; roll back is initiated but fails— In this scenario, when the configuration deployment fails on any of the participating device(s), Cisco EPN Manager performs a roll back, but the roll back on one or more devices fail. Now, the device(s) on which the roll back had failed, has the partial configuration.
For example, the configuration changes are successfully deployed in devices A and B, the deployment fails in device C. Cisco EPN Manager identifies the failure and initiates the roll back in the reverse order of provisioning, that is, it first rolls back the device C, device B, and then device A. Following are the actions that are performed sequentially in the three devices:
Device C—Cisco EPN Manager performs a successful roll back in device C.
Device B—When attempting a rollback on device B, device connectivity is lost and there could be partial configurations left on the device.
Device A—Cisco EPN Manager performs a rollback of Device A, even if the roll back fails in device B.
Note | The roll back may fail due to various other reasons. |
In the Provisioning Wizard, after previewing the configurations, click Deploy. When the deployment fails, the rollback configuration and the status for each participating device is displayed. From the Device(s) drop-down list, choose the device for which you want to view the rollback configuration and the status.
The following
figure illustrates the rollback configuration and the rollback status for each
device.
1 |
Attempted Configuration— Shows the configurations that were deployed to the device selected in the Device(s) drop-down list. |
2 |
Deployment Status— Shows the deployment status of the selected device. If the deployment succeeds, it shows the status as "Success". If the deployment fails, it provides information about the failure. |
3 |
Roll back Configuration— Shows the configurations for which rollback is automatically attempted. |
4 |
Roll back Status— Shows the roll back status of the selected device. If the roll back succeeds, it shows the status as "Success". If the roll back fails, it provides information about the failure. You can use this information to manually clean up the partial configurations on the device. |
For information about how to troubleshoot deployment and rollback failures, see Troubleshoot Configuration Deployment Failures and Roll Back Failures.
Deployment fails, but roll back succeeds— If the configuration deployment fails, roll back is automatically initiated and the results are displayed in the results page. Analyse the attempted configuration and error message shown in the results page for each device and identify the root cause of the deployment failure.
Note | Before deleting the circuit, ensure that it is not in use. |
Ensure that the device is reachable and perform a device re-synch.
If there were any device issues that were reported in the previous deployment, try to fix the issues.
Edit the circuit and update the attributes, if required, and then re-attempt the circuit deployment.
If the deployment fails, Cisco EPN Manager will initiate the roll back.
If the roll back fails again, identify the cause of the roll back failure.
To identify the cause of the failure, you can use the configuration and roll back transaction details, history of the service deployment attempts, and the roll back attempts that are displayed in the Circuit/VC 360 view. See Get Quick Information About a Circuit/VC: Circuit/VC 360 View.
Manually remove the partial configurations that are stored on the device.
You can also contact the Cisco representative to analyse and identify the root cause of configuration deployment failure and roll back failure.
This topic provides a summary of the Carrier Ethernet service provisioning support in Cisco EPN Manager 2.1. For a more detailed overview of the different types of EVCs and the supported underlying networks, see Overview of Circuit/VC Discovery and Provisioning.
Cisco EPN Manager supports provisioning of both port-based and VLAN-based VCs of the following types:
Cisco EPN Manager supports the following supplementary provisioning functions that can be used during EVC creation:
The following prerequisites must be met before you can provision EVCs:
default interface 'interface-name’
interface GigabitEthernetXX/XX switchport trunk allowed vlan none switchport mode trunk
EVCs are created in the context of the topology map. You can access the topology map and the Provisioning Wizard by choosing
in the left sidebar or you can open the Provisioning Wizard from the topology map, as described in the procedure below.For information about the prerequisites that must be met before you can provision EVCs, see Prerequisites for EVC Provisioning.
To create a new EVC:
Step 1 | In the left sidebar, choose . | ||||||
Step 2 | Click the Device Groups button in the toolbar and select the group of devices you want to show on the map. | ||||||
Step 3 | In the Circuits/VCs tab, click the '+' icon to open the Provisioning Wizard in a new pane to the right of the map. | ||||||
Step 4 | Select Carrier Ethernet in the Technology drop-down list. Cisco EPN Manager displays a list of relevant circuit/VC types in the Service Type area. For example, Carrier Ethernet service types include EPL, EVPL, EP-LAN, and so on. | ||||||
Step 5 | In the Service Type list, select the type of circuit/VC you want to create. | ||||||
Step 6 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||||||
Step 7 | Click Next to go to the Service Details page. | ||||||
Step 8 | Select the customer for whom the EVC is being created. If there are no customers in the list, go to Inventory > Other > Customers to create the customer in the system, and then restart the Provisioning Wizard. | ||||||
Step 9 | Enter the Service Details. See Service Details Reference for descriptions of the fields and attributes. | ||||||
Step 10 | For E-Line, E-Tree, and E-LAN EVCs: If required, configure the service OAM which enables fault and performance monitoring across the EVC. For E-Line EVCs, select the Enable CFM check box to enable the Service OAM options. See Service OAM. Click the Plus icon to add a row to the Service OAM table and provide values in the relevant columns. For E-Tree EVCs, you must specify the direction, i.e., Leaf-to-Root, Root-to-Leaf, or Root-to-Root. | ||||||
Step 11 | In the Deployment Action field, specify what you want to do when the EVC creation process is completed. You can either request a preview of the configurations that will be deployed to the relevant devices before the actual deployment or you can deploy the configurations immediately upon completion. | ||||||
Step 12 | Click Next to go to the page(s) in which you define the UNI(s). In the case of E-Access, there is an additional page for defining the ENNI. | ||||||
Step 13 | Identify the
device and interface that will serve as the UNI:
| ||||||
Step 14 | If you are creating a new UNI, enter the New UNI Details. See New UNI Details Reference for descriptions of the fields and attributes. | ||||||
Step 15 | Enter the UNI Service Details. See UNI Service Details Reference for descriptions of the fields and attributes. | ||||||
Step 16 | If one of the endpoints is an interface on a device that is not managed by Cisco EPN Manager , select the Unmanaged check box and provide information for the unmanaged device. See Provision a Circuit/VC with an Unmanaged Endpoint for more information. | ||||||
Step 17 | For E-LAN and E-TREE EVCs with H-VPLS as the core technology, select the devices that will serve as the primary and secondary hubs. | ||||||
Step 18 | For E-Line and
E-Access EVCs: In the Pseudowire Settings page, you can select a TE tunnel over
which the EVC will traverse, as follows:
| ||||||
Step 19 | Optional. If you want to append a template with additional CLI commands that will be configured on the devices participating in the service, do so in the Service Template page. See Extend a Circuit/VC Using Templates for more information. | ||||||
Step 20 | When you have provided all the required information for the circuit/VC, click Submit. If you chose to see a preview of the CLI that will be deployed to the devices, it will be displayed now and you can click Edit Attributes to change the attributes. Otherwise, the configurations will be deployed to the devices immediately. | ||||||
Step 21 | The circuit/VC should be added to the list in the Circuits/VCs tab in the Network Topology window. |
If the configuration deployment fails, see the What Happens When a Deployment Fails section.
Note | You can have multiple UNIs on the same device for EVCs using VPLS as the core technology, but not for H-VPLS-based EVCs. |
For information about the prerequisites that must be met before you can provision EVCs, see Prerequisites for EVC Provisioning.
To create a new EVC:
Step 1 | From the left
sidebar, choose
.
The network topology window opens. |
Step 2 | From the toolbar, click Device Groups and then select the group of devices you want to show on the map. |
Step 3 | Click the Circuits/VCs tab. |
Step 4 | From the
Circuits/VCs pane toolbar, click the
+ (Create) icon.
The Provisioning Wizard opens in a new pane to the right of the map. |
Step 5 | Select Carrier Ethernet in the Technology drop-down list |
Step 6 | In the Service Type list, select a multipoint EVC type. |
Step 7 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. |
Step 8 | Click Next to go to the Service Details page. |
Step 9 | Select the customer for whom the EVC is being created. If there are no customers in the list, go to Inventory > Other > Customers to create the customer in the system, and then restart the Provisioning Wizard. |
Step 10 | Enter the Service Details. See Service Details Reference for descriptions of the fields and attributes. |
Step 11 | In the Deployment Action field, specify what you want to do when the EVC creation process is completed. You can either request a preview of the configurations that will be deployed to the relevant devices before the actual deployment or you can deploy the configurations immediately upon completion. |
Step 12 | Click Next to go to the page(s) in which you define the UNI(s). |
Step 13 | In the Multi UNI
area, click the Plus icon to add the first UNI to the table. The UNI is given a
default name and is automatically selected in the table. Each time you click
the Plus icon, a new UNI is added to the table.
Alternatively, you can click on devices in the map to add new UNIs to the table. In this case, the device name will be populated in the Device field under New UNI details. |
Step 14 | Select a UNI in the table to define or edit its attributes. |
Step 15 | Identify the device and interface that will serve as the UNI: |
Step 16 | If you are creating a new UNI, enter the New UNI Details. The New UNI details are relevant for the UNI that is currently selected in the Multi UNI table. See New UNI Details Reference for descriptions of the fields and attributes. |
Step 17 | Enter the UNI Service Details. See UNI Service Details Reference for descriptions of the fields and attributes. Click Next. |
Step 18 | If one of the endpoints is an interface on a device that is not managed by Cisco EPN Manager , provide information for the unmanaged device in the Unmanaged page. See Provision a Circuit/VC with an Unmanaged Endpoint |
Step 19 | Optional. If you want to append a template with additional CLI commands that will be configured on the devices participating in the service, do so in the Service Template page. See XREF for more information. |
Step 20 | When you have provided all the required information for the circuit/VC, click Submit. If you chose to see a preview of the CLI that will be deployed to the devices, it will be displayed now and you can click Edit Attributes to change the attributes. Otherwise, the configurations will be deployed to the devices immediately. |
Step 21 | The circuit/VC should be added to the list in the Circuits/VCs pane in the Network Topology window. |
The following table lists and describes the attributes that define the EVC on the service level. Note that not all attributes are relevant for all the EVC types.
Attribute |
Description |
||
---|---|---|---|
Service Name |
Unique name to identify the circuit/VC. |
||
Service Description |
Description of the VC that will help to identify the VC. |
||
Service Type |
Prepopulated based on the type of service you are creating—EPL, EVPL, EP-LAN, and so on. |
||
Service MTU |
The maximum size, in bytes, of any frame passing through the VC. Values can be between 1522 and 9216. The service MTU must be lower than or equal to the MTU defined on the UNI. |
||
Core Technology |
VPLS or H-VPLS. See Core Technology for Multipoint EVCs. |
||
VPN ID |
|
||
Bundling |
Enables multiple VLANs on this VC. Multiple CE-VLAN IDs are bundled to one EVC. |
||
CE-VLAN ID Preservation |
Ensures that the CE-VLAN ID of an egress service frame is identical in value to the CE-VLAN ID of the corresponding ingress service frame. This must be enabled if bundling is enabled. |
||
CE-VLAN ID CoS Preservation |
Ensures that the CE-VLAN CoS of an egress service frame is identical in value to the CE-VLAN CoS of the corresponding ingress service frame. The CoS markings are unaltered. |
The following table lists and describes the attributes relating to the port that is specified as the UNI. Note that not all attributes are relevant for all the EVC types.
Attribute |
Description |
---|---|
MTU |
The Maximum Transmission Size, in bytes, of a packet passing through the interface. The MTU of the UNI must be greater than or equal to the MTU defined on the service level. |
Speed |
Port speed. You can reduce the speed if this is supported on the port. |
Duplex Mode |
|
Service Multiplexing |
Allows the UNI to participate in more than one EVC instance. |
UNI Allows Bundling |
Allows the UNI to participate in VCs with Bundling enabled. See Bundling in Service Details Reference |
Untagged CE-VLAN ID |
The ID of the CE-VLAN assigned to untagged traffic. |
Ingress/Egress QoS Profile |
Select the required QoS profile for ingress or egress traffic on the UNI. The list of profiles includes policy maps that were configured on the device and discovered by the system, as well as user-defined QoS profiles. Refer to Create QoS Profiles for information on how to create QoS profiles. |
UNI QoS Profile |
Applies a QoS profile on the UNI itself to define the bandwidth profile and other quality of service attributes of the UNI. If you apply a QoS profile on the UNI level, you should not apply a QoS profile on the service level. |
Enable Link OAM |
Enables IEEE 803.1ah link operation and maintenance. If Link OAM is enabled, you will see events relating to the state of the link between this UNI and the customer’s access switch. |
Enable Link Management |
Enables the customer access switch to get information about this UNI, VLAN IDs, services on the UNI, and so on. |
The following table lists and describes the attributes of the EVC in relation to the UNI, i.e., how the EVC operates on this UNI. Note that not all attributes are relevant for all the EVC types.
Note | For QinQ attributes, only the attributes that are supported on the selected device will appear in the wizard. |
Attribute |
Description |
Additional Information |
---|---|---|
Ingress/Egress Service QoS Profile |
Select the required QoS profile for ingress or egress traffic on the UNI. The list of profiles includes policy maps that were configured on the device and discovered by the system, as well as user-defined QoS profiles. Refer to Create QoS Profiles for information on how to create QoS profiles. |
|
Layer 2 Control Protocol Profile |
Profile that determines how the various communication protocols are handled. Frames using the various protocols are either tunneled, dropped or peered. Refer to MEF 6.1 for details. |
|
Designation |
For E-Tree: Select the role of the UNI in the VC, either Leaf or Root. |
|
Use point to point connection with Root |
For E-Tree: If the UNI is designated as a leaf, you can select this check box to create an active pseudowire between root and leaf. The check box will not appear if there is more than one endpoint on a single device or if there is more than one root in the service. |
|
Match |
Select the type of tagging the traffic should have in order to enter the UNI: |
Dot1AD is not supported on ME3600 devices running15.3(3)software version. |
VLAN(s) |
VLAN identifier, an integer between 1 and 4094. You can enter a range of VLAN IDs using a hyphen or a comma-separated series of VLAN IDs. |
|
Inner VLAN(s) |
VLAN identifier for the second level of VLAN tagging, an integer between 1 and 4094. You can enter a range of VLAN IDs using a hyphen or a comma-separated series of VLAN IDs. |
|
Untagged Bundled |
Enables traffic with no VLAN tags to be bundled together with VLAN tagged frames. |
|
Priority Tagged Bundled |
Enables priority tagged traffic to be bundled together with VLAN tagged frames. |
|
Exact |
Prevents admittance of traffic with additional inner VLAN tags other than those that are matched to be carried by the service. |
Applicable for IOS-XR devices only. |
Outer VLAN CoS |
The outer VLAN Class of Service identifier that should be associated with the frame. The CoS ID can be an integer between 0 and 7. |
Applicable for IOS devices only. |
Inner VLAN CoS |
The inner VLAN Class of Service identifier that should be associated with the frame. The CoS ID can be an integer between 0 and 7. |
Applicable for IOS devices only. |
E-Type |
|
Applicable for IOS devices only. |
Rewrite Definition Action |
|
The Translate action is applicable for IOS-XR devices only. |
On the service level, you can define EOAM (Ethernet Operations, Administration and Management) parameters that will allow monitoring and troubleshooting of the EVC. Effectively, you will be configuring Connectivity Fault Management (CFM) components on the endpoints of the EVC.
For a point-to-point EVC, you can define OAM parameters in one direction, i.e., from UNI A to UNI Z or in both directions. For a multipoint EVC, you can define the source and destination MEP groups and then associate the EVC endpoints with a specific MEP group.
See Configure EOAM Fault and Performance Monitoring for more information about CFM and for device-level CFM configuration.
Note | Your input in the From and To fields creates MEP groups, or ordered sets of UNIs. In the next page of the wizard, you will associate the UNI with one of these MEP groups. |
The User Network Interface (UNI) is the physical demarcation point between the responsibility of the Subscriber (the Customer Edge or CE) and the responsibility of the Service Provider (the Provider Edge or PE).
UNIs demarcate the endpoints of EVCs, so configuring device interfaces as UNIs is an essential part of VC provisioning. UNI configuration can be done during the VC creation process. Alternatively, you can configure UNIs independently of VC creation. These UNIs will be available for selection during VC creation.
To configure a UNI:
Step 1 | Follow the instructions in Create and Provision a New Carrier Ethernet EVC to access the Provisioning Wizard. |
Step 2 | Select Carrier Ethernet from the Technology drop-down list. |
Step 3 | Select UNI from the Service Types list. |
Step 4 | Click Next to go to the Customer Service Details page. |
Step 5 | Provide a unique name and description for the UNI, and associate it with a customer, if required. |
Step 6 | Define the
service attributes of the UNI, as follows:
|
Step 7 | Under Deploy, select whether you want to deploy the UNI immediately upon completion or first display a preview of the CLI that will be deployed to the device. |
Step 8 | Click Next to go to the UNI Details definition page. |
Step 9 | Select the device and port you want to configure as the UNI. |
Step 10 | Configure the UNI attributes, as described in New UNI Details Reference. |
Step 11 | Click Submit. If you previously chose to deploy the circuit upon completion, a job is created and the required CLI is deployed to the devices. If you chose to see a preview of the CLI before actually deploying to the devices, the preview will be displayed now . Verify the CLI and if you want to change any of the attributes, click Edit Attributes. Else, click Deploy. |
The External Network to Network Interface (ENNI) specifies the reference point that is the interface between two Metro Ethernet Networks (MENs) where each operator network is under the control of a distinct administration authority. The ENNI is intended to support the extension of Ethernet services across multiple operator MENs, while preserving the characteristics of the service.
When provisioning an E-Access VC, you need to define the ENNI that will carry traffic through to the adjacent network. ENNI configuration can be done during the VC creation process. Alternatively, you can configure ENNIs independently of VC creation. These ENNIs will be available for selection during VC creation.
To configure an ENNI:
Step 1 | Follow the instructions in Create and Provision a New Carrier Ethernet EVC to access the Provisioning Wizard. |
Step 2 | Select Carrier Ethernet from the Technology drop-down list. |
Step 3 | Select ENNI from the Service Types list. |
Step 4 | Click Next to go to the Customer Service Details page. |
Step 5 | Provide a unique name and description for the ENNI, and associate it with a customer/operator, if required. |
Step 6 | Under Deploy, select whether you want to deploy the ENNI immediately upon completion or first display a preview of the CLI that will be deployed to the device. |
Step 7 | Click Next to go to the ENNI Details definition page. |
Step 8 | Select the device and port(s) you want to configure as the ENNI. |
Step 9 | Define the
following parameters for the ENNI:
|
Step 10 | Click Submit. If you previously chose to deploy the circuit upon completion, a job is created and the required CLI is deployed to the devices. If you chose to see a preview of the CLI before actually deploying to the devices, the preview will be displayed now. Verify the CLI and if you want to change any of the attributes, click Edit Attributes. Else, click Deploy. |
Cisco EPN Manager supports the provisioning of Dense Wavelength Division Multiplexing (DWDM) optical channel (OCH) circuit types. The DWDM optical technology is used to increase bandwidth over existing fiber optic backbones. It combines and transmits multiple signals simultaneously at different wavelengths on the same fiber. In effect, one fiber is transformed into multiple virtual fibers.
Cisco EPN Manager supports the following optical circuits:
Following are the prerequisites for provisioning an optical circuit:
To provision an OCH circuit:
For information about the prerequisites that must be met before you can provision an optical circuit, see Prerequisites for Provisioning Optical Circuits.
Step 1 | From the left sidebar, choose . | ||||
Step 2 | Click Device Groups, and then select the location in which you want to create the OCH circuit. | ||||
Step 3 | Close the Device Groups popup window. | ||||
Step 4 | In the Network Topology window, click Circuits/VCs. | ||||
Step 5 | Click the
Circuits/VCs tab, then click the
+ (Create) icon in the
Circuits/VCs pane toolbar. The Provisioning
Wizard opens in a new pane to the right of the map.
You can also access the Provisioning wizard by choosing . | ||||
Step 6 | From the Technology drop-down list, choose Optical. Cisco EPN Manager displays a list of relevant circuit types in the Service Type area. For example, Optical service types for OCH circuits include OCHNC WSON, OCHCC WSON, OCH-Trail WSON, and OCH-Trail UNI. | ||||
Step 7 | In the Service Type area, choose the type of OCH circuit you want to create. | ||||
Step 8 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||||
Step 9 | Click Next to go to the Customer Section page. | ||||
Step 10 | (Optional) Select the customer for whom the circuit is being created. If there are no customers in the list, go to to create the customer in the system, and then restart the Provisioning Wizard. | ||||
Step 11 | Enter the circuit name and its description in the Customer Section page. | ||||
Step 12 | Click
Next to go to the
Circuit Section page.
| ||||
Step 13 | Enter the circuit details. See Circuit Section Reference for OCH Circuit Types for descriptions of the fields and attributes. | ||||
Step 14 | Click Next to go to the Endpoint Section page. | ||||
Step 15 | Select a row in
the Endpoint table, and then click a device in the map to populate the Device
Name column with the selected device. Alternatively, you can click the row in
the Endpoint table to edit the Device Name, Termination Point, and Add/Drop
Port columns. Only network elements that are available and compatible with the
circuit type you chose will be displayed.
| ||||
Step 16 | Click Next to go to the Constraints Section page. | ||||
Step 17 | Click a device
node or a link in the map to add it to the Constraints table. Alternatively,
you can click the '+' button in the table tool bar to add a new row to the
table and edit the Node/Link Name, Include/Exclude, and Route columns. Only
network elements and links that are compatible with the circuit type you chose
will be displayed.
| ||||
Step 18 | Click Create Now to create the circuit. If you chose to see a preview of the TL1 or CLI commands that will be deployed to the devices, it will be displayed on clicking Preview and now, you can either deploy the configurations to the device or cancel it but you cannot edit the attributes. | ||||
Step 19 | The circuit should be added to the list in the Circuits/VCs pane in the Network Topology window. To check the provisioning state, click the i icon next to the circuit/VC name to see the Circuit/VC 360 view. |
Use this procedure to create two OCH-Trail UNI circuits that are mutually diverse from each other. Both the circuits must originate from the same device. You can create both the circuits quickly using the Provisioning wizard in a single workflow .
For information about the prerequisites that must be met before you can provision an optical circuit, see Prerequisites for Provisioning Optical Circuits.
Step 1 | From the left sidebar, choose . | ||
Step 2 | Click Device Groups, and then select the location in which you want to create the OCH circuit. | ||
Step 3 | Close the Device Groups popup window. | ||
Step 4 | In the Network Topology window, click Circuits/VCs. | ||
Step 5 | Click the
Circuits/VCs tab, then click the
+ (Create) icon in the
Circuits/VCs pane toolbar. The Provisioning
Wizard opens in a new pane to the right of the map.
You can also access the Provisioning wizard by choosing . | ||
Step 6 | From the Technology drop-down list, choose Optical. | ||
Step 7 | In the Service Type area, choose OCH-Trail UNI. | ||
Step 8 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||
Step 9 | Click Next to go to the Customer Section page. | ||
Step 10 | Check the Mutual Diversity check box to create two OCH-Trail UNI circuits that are mutually diverse from each other. | ||
Step 11 | Enter the circuit name and its description in the Customer Section page. | ||
Step 12 | Click Next to go to the Endpoint Section page. | ||
Step 13 | Select a row in
the Endpoint table, and then click a device in the map to populate the Device
Name column with the selected device. Alternatively, you can click the row in
the Endpoint table to edit the Device Name and Interface.
| ||
Step 14 | Click Next to go to the Circuit Section page. | ||
Step 15 | Enter the circuit details. See Circuit Section Reference for OCH Circuit Types for descriptions of the fields and attributes. | ||
Step 16 | Click Next to go to the Constraints Section page. | ||
Step 17 | Click a device
node or a link in the map to add it to the Constraints table. Alternatively,
you can click the '+' button in the table tool bar to add a new row to the
table and edit the Node/Link Name, Include/Exclude, and Route columns. Only
network elements and links that are compatible with the circuit type you chose
will be displayed.
| ||
Step 18 | Click Next. The Customer Section page for the second circuit is displayed. | ||
Step 19 | Repeat Step 11 to Step 17 to create the second circuit. | ||
Step 20 | Click Create Now to create the circuit. If you chose to see a preview of the TL1 or CLI commands that will be deployed to the devices, it will be displayed on clicking Preview and now, you can either deploy the configurations to the device or cancel it but you cannot edit the attributes. | ||
Step 21 | The circuits should be added to the list in the Circuits/VCs pane in the Network Topology window. To check the provisioning state, click the i icon next to the circuit/VC names to see the Circuit/VC 360 view. |
To provision an OTN circuit:
For information about the prerequisites that must be met before you can provision an optical circuit, see Prerequisites for Provisioning Optical Circuits.
Step 1 | From the left sidebar, choose . | ||
Step 2 | Click Device Groups, and then select the location in which you want to create the OTN circuit. | ||
Step 3 | In the Network Topology window, click Circuits/VCs. | ||
Step 4 | Click the
Circuits/VCs tab, then click the
+ (Create) icon in the
Circuits/VCs pane toolbar. The Provisioning Wizard
opens in a new pane to the right of the map.
You can also access the Provisioning wizard by choosing . | ||
Step 5 | From the Technology drop-down list, choose Optical. Cisco EPN Manager displays a list of relevant circuit types in the Service Type area. For example, service types for OTN circuits include ODU UNI, ODU Tunnel, OPU over ODU, and ODU UNI Hairpin. | ||
Step 6 | In the Service Type area, choose the type of OTN circuit you want to create. | ||
Step 7 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||
Step 8 | Click Next to go to the Customer Details page. | ||
Step 9 | (Optional) Select the customer for whom the circuit is being created. If there are no customers in the list, go to to create the customer in the system, and then restart the Provisioning Wizard. | ||
Step 10 | Enter the circuit name and its description in the Customer Details page. | ||
Step 11 | Click Next to go to the Circuit Details page. | ||
Step 12 | Enter the circuit details. See Circuit Section Reference for OTN Circuit Types for descriptions of the fields and attributes. | ||
Step 13 | Click Next to go to the Endpoint Section page. | ||
Step 14 | Select a row in
the Endpoint table, and then click a device in the map to populate the Device
Name column with the selected device. Alternatively, you can click the row in
the Endpoint table to edit the Device Name and Interface/Termination Point
columns. Only network elements that are available and compatible with the
circuit type you chose will be displayed.
| ||
Step 15 | Enter the protection type and path options for the circuit. See Endpoint Section Reference for OTN Circuit Types for descriptions of the fields and attributes. | ||
Step 16 | Click Create Now to create the circuit. If you chose to see a preview of the TL1 or CLI commands that will be deployed to the devices, it will be displayed on clicking Preview. After seeing the preview of the TL1 or CLI commands, you can either deploy the configurations to the devices or cancel the provisioning operation. |
The circuit should be added to the list in the Circuits/VCs tab in the Network Topology window. To check the provisioning state, click the i icon next to the circuit/VC name to see the Circuit/VC 360 view.
The following table lists and describes the attributes that define the OTN circuit types.
Attribute |
Description |
Enabled |
||
---|---|---|---|---|
Circuit Properties | ||||
Bandwidth |
Bandwidth required to provision the OTN circuit. See Table for the mapping of values in the Bandwidth, and Service Type fields. |
For all OTN circuit types. |
||
A-End Open Ended |
Check this check box to create an open-ended circuit, in which the source end point is connected to an ODU subcontroller, instead of a client payload controller.
|
For ODU UNI circuit type when the Bandwidth field is set to ODU0, ODU1, ODU2, or ODU2E. |
||
Z-End Open Ended |
Check this check box to create an open-ended circuit, in which the destination end point is connected to an ODU subcontroller, instead of a client payload controller.
|
For ODU UNI circuit type when the Bandwidth field is set to ODU0, ODU1, ODU2, or ODU2E. |
||
Service Type |
Service types supported for the selected bandwidth. See Table for the mapping of values in the Bandwidth and Service Type fields. |
For ODU UNI circuit type. |
||
Route Properties | ||||
Bit Rate |
Total number of bits per second. |
For all OTN circuit types (except ODU UNI Hairpin) when the Bandwidth field is set to ODUFLEX. |
||
Framing Type |
|
For all OTN circuit types (except ODU UNI Hairpin) when the Bandwidth field is set to ODUFLEX. |
||
Record Route |
Check this check box to record the circuit route. |
For all OTN circuit types (except ODU UNI Hairpin). |
The following table lists and describes the attributes that define the protection type and path options for OTN circuit types.
Attribute |
Description |
Enabled |
||
---|---|---|---|---|
Endpoints | ||||
Device Name |
A end and Z end devices of the circuit.
|
For all OTN circuit types. |
||
Interface |
Interface names for the A end and Z end devices. |
For ODU UNI circuits. |
||
Termination Point |
Termination point for the cards. |
For OPU over ODU and ODU UNI Hairpin circuits. |
||
Protection Type |
|
For all OTN circuit types (except ODU UNI Hairpin). |
||
Diverse From Tunnel ID |
Select a tunnel to ensure that it is not used by the circuit you are provisioning. This is to ensure that if there is a failure in a tunnel, the same tunnel is not used by another circuit. |
For all OTN circuit types(except ODU UNI Hairpin). |
||
Working Path,Protected Path, and Restored Path The Protected Path field group is available for all OTN circuit types (except ODU UNI Hairpin) only when the Protection Type field is set to 1+1 or 1+1+R. The Restored Path field group is available for all OTN circuit types (except ODU UNI Hairpin) only when the Protection Type field is set to 1+R or 1+1+R. |
||||
Type |
Choose the type of working path or protected path for the circuit. Values are Dynamic and Explicit. |
For all OTN circuit types (except ODU UNI Hairpin). |
||
New |
Check this check box to create a new explicit working or protected path for the circuit. |
For all OTN circuit types (except ODU UNI Hairpin) when the Type field is set to Explicit. |
||
Select Existing EP |
Choose an existing explicit working or protected path for the circuit. |
For all OTN circuit types (except ODU UNI Hairpin) when the Type field is set to Explicit and the New check box is unchecked. |
||
New Name |
Enter a name for the explicit path that you are creating. In the table below the New Name field, click the '+' button to add a new row to the table, and then select a device and an explicit path controller as the interface for the device. |
For all OTN circuit types (except ODU UNI Hairpin) when the Type field is set to Explicit and the New check box is checked. |
||
Protection Profile The Protection Profile field group is available for all OTN circuit types (except ODU UNI Hairpin) only when the Protection Type field is set to 1+1, 1+R, or 1+1+R and a valid A end device is selected. |
||||
Protection Profile |
The details of the protection profile such as the protection type, SNC, hold off, wait to restore, and whether the circuit is revertive are displayed. |
The following table maps the values in the Bandwidth and Service Type fields for the ODU UNI circuits
Bandwidth |
Service Type |
---|---|
ODU0 |
|
ODU1 |
|
ODU1E |
|
ODU1F |
|
ODU2 |
|
ODU2E |
|
ODU2F |
|
ODU4 |
|
ODUFLEX |
An MPLS Layer 3 VPN creates a private IP network. The customer connects to the network via customer edge (CE) routers, which act as IP peers of provider edge (PE) routers.
Virtual Routing and Forwarding (VRFs)
On the PE, Virtual Routing and Forwarding (VRF) instances act as virtual IP routers dedicated to forwarding traffic for the L3VPN service. The VRFs learn the routes to each other via the Multi-Protocol Border Gateway Protocol (MP-BGP), and then forward traffic using MPLS.
A VPN is comprised of at least one but typically several VRFs. Cisco EPN Manager uses the VPN ID to discover which VRFs together form a single VPN. If Cisco EPN Manager discovers an existing network where no VPN ID has been provisioned, it takes all VRFs with the same name and associates them into one VPN. For VPNs created using Cisco Prime Provisioning, which uses a naming convention with version number prefixes and different suffixes, Cisco EPN Manager will recognize the different VRFs as belonging to one VPN.
In general there is a regular expression which can be configured to allow for varying naming convention.
Route Targets (RTs)
The connections between VRFs are defined using Route Targets (RTs) that are imported and exported by the VRFs. Cisco EPN Manager makes it easy to set up a full mesh of connections, and automatically allocates the route target to be used. The route target consists of a prefix which is either an AS number or an IPv4 address, for example, a full mesh prefix, 100 [681682]. The prefix can be selected from the existing BGP autonomous system (AS) numbers in the network, or it can be entered manually. The second number following the prefix is allocated automatically by Cisco EPN Manager .
Alternatively or in addition to the full mesh, it is possible to manually select route targets. During VPN creation, there is an initial screen where you type in the route targets to be used within a VPN, and then for each VRF you can select which route targets you import and export. You also specify for which address family (IPv4 or IPv6) you will use the route target. This can be used for example to configure extranets, by importing route targets used in other VPNs.
Route Redistribution
The routes that are exchanged between the PE and the CE have to be redistributed into the MP-BGP routing protocol so that remote endpoints can know which prefixes can be reached at each VRF. To control route redistribution, Cisco EPN Manager allows you to define the required protocol (Static, Connected, or RIP), the protocol's metric value, and optionally the applicable route policy.
Endpoints
Cisco EPN Manager supports the creation of IP endpoints on Ethernet subinterfaces. It supports selecting untagged encapsulation, or specifying an outer and optionally an inner VLAN, with 802.1q or 802.1ad encapsulation. You can specify both IPv4 and Ipv6 addresses at an endpoint. You can also specify the BGP neighbor details to provision BGP neighbors between the CE and PE.
For information on how to provision L3VPN service using Cisco EPN Manager , see, Provision L3VPN Services.
Cisco EPN Manager supports the following L3VPN features:
Creation of VRFs.
Automatic allocation of VPN IDs and Route Target IDs.
Automatic allocation of route distinguishers.
Discovery of VPNs consisting of several VRFs, based on multiple criteria (VPN ID, common name, and Prime Provisioning naming conventions).
You can select devices for L3VPN provisioning using the Point and Click method of provisioning.
Definition of IP endpoints attached to a VRF. Associating Ethernet subinterfaces with VRFs.
Provisioning of BGP neighbors between the CE and PE.
Attaching QoS profiles to the endpoint interfaces.
Adding new VRFs to existing VPNs.
Modifying VPNs and associated VRFs created and deployed (or discovered and promoted) using Cisco EPN Manager .
Overlays in the Network Topology for L3VPN services.
Promotion of L3VPN services discovered directly from the device. This further helps in modifying and deleting discovered services.
Using route targets with OSPF dual AS routing.
Using integrated routing and bridging to provision L3VPN services using BDI/BVI interfaces (subinterfaces).
Associating IP Service Level Agreements (SLAs) and CLI templates with L3VPN services.
Route redistribution between the PE-CE link and the MP-BGP core using connected, static, RIP, or OSPF routes.
Provisioning L3VPN services using LAG interfaces.
Cisco EPN Manager has the following L3VPN limitations:
VRFs are supported only on Cisco ASR9000, Cisco ASR90X, Cisco ASR 920X, and Cisco ASR901S devices.
You cannot provision multicast VPNs. Only unicast VPNs are supported.
While creating the L3VPN service, you can add only up to five VRFs to the VPN. More VRFs can later be added to the VPN using the Modify VRF and Add VRF options.
Only one VRF per device is supported. You can create multiple VRFs but on different devices either with the same VRF name or with different VRF names.
Route policies can be selected but cannot be defined within the L3VPN service.
Only BGP PE-CE routing protocol is supported.
There is no support for multiple attached PEs, and so there is no Site of Origin and HSRP support.
IP SLA operations can be associated with VRFs only during service creation and not during service modification.
Deleting an L3VPN service deletes the IP SLA operations associated with the service from the device. And the associated operations that are deleted will not be available for future usage.
For more information about implementing L3VPNs, see Implementing MPLS Layer 3 VPNs.
Before you begin provisioning L3VPN services, ensure that the following pre-requisites are followed.
Following are the prerequisites for provisioning an L3VPN service:
Pre-configuration changes required to set up BGP:
Configure the BGP router-id as shown in the example below:
router bgp 65300 bgp router-id 1.1.1.1
Set Vpn4 and Vpn6 as the parent address family using these commands:
router bgp 100 address-family vpnv4 unicast address-family vpnv6 unicast
Cisco EPN Manager associates multiple VRFs into a single VPN using multiple criteria:
If VRFs were configured with a VPN ID: then the VPN service is discovered using the VPN ID to identify the VRFs that belong to the same VPN. If you have VPNs that you need to discover, where differing VRF names are used within one VPN, then configuring a common VPN ID in all the VRFs enables Cisco EPN Manager to discover the VRFs as a single VPN.
In cases where no more than one VRF is created per device, it is common practice to simply use the same VRF name everywhere across the VPN. If Cisco EPN Manager sees multiple VRFs with the same name and no VPN ID, then it considers them as a single VPN, and the VPN name will be the name of the VRFs.
If VPNs that were originally provisioned using Prime Provisioning: Cisco EPN Manager is also aware of the Prime Provisioning VRF naming convention. The naming convention used by Prime Provisioning is in the format:
V<number>:<VPN name><optional suffix, one of -s -h -etc>
VRFs with the same names and numbers will belong to the same VPN. For example these are VRFs belonging to a VPN called 'ABC':
V1:ABC, V2:ABC, V4:ABC-s, V22:ABC-h, V001:ABC, etc.
The Prime Provisioning naming convention feature is driven by a regular expression that is embedded in the product. If configuring a VPN is not an option for you and you have a naming convention that could be matched with a regular expression, it is possible to change it. To change the regular expression, please contact your Cisco Advanced Services representative.
The process of creating and provisioning a unicast L3VPN involves:
(Optional) Associating a customer to the VPN.
Adding up to five VRFs to the VPN.
Defining the attributes that influence how traffic that is delivered over the L3VPN and through its endpoints will be treated.
Specifying the endpoints and route redistribution values of the L3VPN.
(Optional) Configuring IP Service Level Agreements (SLAs) operation to monitor end-to-end response time between devices using IPv4 or IPv6.
(Optional) Associating user defined CLI templates with the L3VPN service.
Note: Only Unicast L3VPN services are supported in this release.
To create a new L3VPN service:
Step 1 | From the left
sidebar, choose
.
The network topology window opens. | ||||||||||||||||||||||||||||
Step 2 | From the toolbar, click Device Groups and then select the group of devices you want to show on the map. | ||||||||||||||||||||||||||||
Step 3 | Click the
Circuits/VCs tab, then click the
+ (Create) icon in the
Circuits/VCs pane toolbar.
The Provisioning Wizard opens in a new pane to the right of the map. You can also access the L3VPN Provisioning wizard by choosing Configuration > Network > Service Provisioning. | ||||||||||||||||||||||||||||
Step 4 | From the Technology drop-down list, select L3VPN. A list of supported L3VPN service types is displayed. | ||||||||||||||||||||||||||||
Step 5 | In the Service Type section, choose Unicast and click Next to enter the customer and service details. In this release, only service type Unicast L3VPN is supported. | ||||||||||||||||||||||||||||
Step 6 | (Optional) Select the customer that you want to associate with the VPN. If there are no customers in the drop-down list, you can go to Inventory > Other > Customers to create the customer and return to this step. | ||||||||||||||||||||||||||||
Step 7 | Specify the
basic L3VPN parameters:
| ||||||||||||||||||||||||||||
Step 8 | Use the
Route
Target Allocation
section to manually specify the route target address
families (IPv4,
IPv6, or Both) and their associated route target values. You can
create multiple route targets for the L3VPN service. These route targets can be
associated with any VRF that you attach to this L3VPN service in the following
steps.
| ||||||||||||||||||||||||||||
Step 9 | In the Deployment Action drop-down menu, specify the task that must be taken up when the service creation process is completed. Your options are: | ||||||||||||||||||||||||||||
Step 10 | Click Next to associate VRFs to the L3VPN service. | ||||||||||||||||||||||||||||
Step 11 | Select the
required VRFs from the
VRFs
drop-down menu or add a new VRF as explained below, and
then click
Next. During L3VPN service creation, you can
associate up to five VRFs with the VPN. To associate more VRFs to the VPN, see
Add and Copy VRFs to an L3VPN Service.
To create a new VRF:
| ||||||||||||||||||||||||||||
Step 12 | Specify the IPv4
and IPv6 route targets and route distribution details:
| ||||||||||||||||||||||||||||
Step 13 | Specify the IP
endpoints and UNIs values manually as follows:
For a detailed description of the fields and attributes in the UNI table, see New UNI Details Reference. | ||||||||||||||||||||||||||||
Step 14 | Specify the
service end point to be associated with the L3VPN by providing the following
details, and then click
Next:
| ||||||||||||||||||||||||||||
Step 15 | (Optional)
Enter the BGP neighbor details described in the table below and then click
Next.
| ||||||||||||||||||||||||||||
Step 16 | (Optional)
Select existing IP SLA parameters from the list, or specify the IP SLA
operation parameters described in the table below and then click
Next.
| ||||||||||||||||||||||||||||
Step 17 | (Optional) Use the Service Template page to append a template with additional CLI commands that will be configured on the devices participating in the service. See Extend a Circuit/VC Using Templates for more information. | ||||||||||||||||||||||||||||
Step 18 | When you have
provided all the required information for the service, click
Submit. If you chose to see a preview of the CLI
that will be deployed to the devices, it will be displayed now and you can
click
Edit
Attributes
to change the L3VPN attributes. Otherwise, the
configurations will be deployed to the devices immediately.
In case of a deploy failure on even a single device that is part of the service, the configration is rolled back on all devices participating in the service. To delete the endpoints associated with the service, see, Delete an L3VPN Service Endpoint. To add more VRFs to this L3VPN service, see Add and Copy VRFs to an L3VPN Service. |
The following are examples of the configuration deployed to a Cisco ASR 9000 device with the following parameters:
Creation of VRF and IP addresses (both IPv4 and IPv6) under the BDI (virtual) interface.
Redistribution of OSPF protocol to the BGP protocol.
Example: Provisioning an L3VPN service on a Cisco ASR 9000 device's BVI enabled interface (sub-interface).
vrf vrfrbvibdi9k vpn id aaaaaa:21 address-family ipv4 unicast import route-target 6:55 address-family ipv6 unicast import route-target 6:55 export route-target 6:55 interface GigabitEthernet0/0/0/17 no shutdown exit interface GigabitEthernet0/0/0/17.1 encapsulation dot1q 1198 shutdown interface BVI 1 vrf vrfrbvibdi9k ipv4 address 88.7.6.4 255.224.0.0 l2vpn bridge group BDI1 bridge-domain 1 routed interface BVI 1 interface GigabitEthernet0/0/0/17.1 router bgp 140 vrf vrfrbvibdi9k rd auto address-family ipv6 unicast address-family ipv4 unicast exit exit exit
Example: Using a BVI enabled interface for provisioning an L3VPN service with OSPF route distribution (using dual AS):
vrf definition VRF2-2VRF-2UNI-BDI vpn id AAAAAA:2 rd 532533:2 address-family ipv4 route-target import 6:5 route-target export 6:5 address-family ipv6 route-target export 6:5 interface GigabitEthernet0/0/0 duplex full service instance 2 ethernet encapsulation dot1q 761 bridge-domain 14 shutdown exit interface BDI14 vrf forwarding VRF2-2VRF-2UNI-BDI ip address 5.44.3.7 255.255.0.0 router bgp 120 address-family ipv4 vrf VRF2-2VRF-2UNI-BDI neighbor 55.4.3.2 remote-as 71 neighbor 55.4.3.2 activate redistribute rip metric 6 neighbor 55.4.3.2 local-as 387 address-family ipv6 vrf VRF2-2VRF-2UNI-BDI neighbor c5::98 remote-as 50 neighbor c5::98 activate redistribute ospf 65 match external metric 2 neighbor c5::98 local-as 324 no-prepend replace-as dual-as exit exit
Using Cisco EPN Manager , you can view the detailed information about an L3VPN service in the following ways:
Using the Circuit/VC 360 View: The Circuit/VC 360 view provides detailed information available for a specific L3VPN created using Cisco EPN Manager . See View Circuit/VC Details. The different parameters associated with the L3VPN service are displayed in three different tabs: Summary, VRFs, Site Details, and BGP Neighbors.
Using the Network Topology and Service Details View: The Network Topology window presents a graphical, topological map view of devices, the links between them, and the active alarms on the devices or links. It also enables you to visualize L3VPNs within the displayed topology map.
To view a complete list of L3VPNs and its details, see View a Device Group's Circuits/VCs List in the Topology Window. See, Circuit/VC 360 View.
To view the L3VPN service details for a specific device, see View Circuits/VCs In Which a Specific Device Participates.
Using the Alarms Table: The Alarms Table in Cisco EPN Manager provides several ways to see, at a glance, if there are any problems with your L3VPN services. See Check Circuits/VCs for Faults.
Following are the attributes available in different L3VPN Service Details views:
Tab Name |
Attributes |
Descriptions |
---|---|---|
Summary |
Discovery State |
Identifies whether the service was discovered from the device fully or partially or not discovered at all. This state is not defined by the service being provisioned or discovered from the network. |
Name |
Unique name that identifies the L3VPN service. For services that are discovered directly from the device, this name represents the VLAN ID (numerical value) of the service. |
|
Customer |
Customer associated with the L3VPN. |
|
Description |
Description of the L3VPN that will help to identify the L3VPN. |
|
Type |
L3VPN service type that is prepopulated based on the type of service that is created. |
|
Operational State |
The state in which the L3VPN service is functioning. The states are Defined, Deploying, Failed, Discovered, and Unknown. Note- If the service state indicates Operational, Serviceability, or Primary, it represents the state of the service endpoint and not the state of the L3VPN service itself. |
|
MTU |
The service MTU is the size in bytes of the largest IP packet that can be carried unfragmented across the L3VPN. It does not include layer 2 headers. The configured interface MTU is the service MTU plus the size of any layer 2 headers. For Ethernet, this will add 14 bytes plus 4 bytes per VLAN header. |
|
Provisioning Status |
The service's provisioning state represents whether there is a provisioning intent for the service and, if so, its status. The possible values are: Failed, In Progress, Planned, and Succeeded. |
|
Serviceability State |
A combination of the service's admin and operational states. The admin state is shown because it impacts service operability. The operational state is shown to quickly identify whether a service is working or not. The values are: Admin Down, Down, Up, Auto Up, Unavailable, and Partial. |
|
VRFs |
Device |
Name of the device on which the VRF is configured. |
VRF |
Name to identify the VRF. |
|
Description |
Description of the VRF that will be configured on the device. |
|
Site Details (IP Endpoints) |
UNI Name |
Name of the UNI associated with the L3VPN. |
Device Name |
Name of the device where the UNI is located. |
|
Interface Name |
Name of the interface on the device which connects to the UNI. |
|
IP Address/Subnet Mask |
The subnet mask in CIDR notation used to identify the IP address of the endpoint. |
|
VRF |
The VRF with which this endpoint is connected. |
|
BGP Neighbors |
Device |
The device where the VRF is located. |
VRF |
The VRF used to reach this neighbor. |
|
IP Address |
The IP address of the neighbor. |
|
Neighbor AS |
The autonomous system number of this neighbor. |
|
Ingress RP |
The route policy applied to any BGP routes received from this neighbor. |
|
Egress RP |
The route policy applied to any routes sent to this neighbor. |
You can modify L3VPN services that are created and deployed using Cisco EPN Manager . While the full mesh prefix, QoS profiles, and RT values associated with the service can be modified, you cannot modify parameters such as the customer details, VPN name, and service MTU values associated with the service. To modify these parameters, delete the service, and re-create it with new values. You can also modify the VRFs associated with L3VPN services.
To modify L3VPN services and VRFs:
To modify L3VPN services that are discovered and promoted using Cisco EPN Manager , you must ensure that that the route distinguisher for the L3VPN service is specified in the format rd device_ip:number. For example:
vrf definition vdvvgfr420 rd 10.104.120.133:420 vpn id 36B:420 ! address-family...
If the route distinguisher is specified in any other format, you will not be able to edit the service.
Step 1 | Navigate to . | ||
Step 2 | Click the Circuits/VCs tab, and select the L3VPN service that you want to modify. | ||
Step 3 | Click the pencil (Modify) icon. | ||
Step 4 | To modify the
selected L3VPN, choose
Modify
VPN and click
Next.
The Provisioning wizard displays the VRFs, endpoints, and other details associated with the selected L3VPN. | ||
Step 5 | To modify the
VRFs associated with the selected L3VPN, choose
Modify
VRF and click
Next.
The Provisioning wizard displays the VRFs, endpoints, and other details associated with the selected L3VPN. Along with modifying existing VRF parameters, you can also associate new Route Target values to the VRF. While modifying VRFs, you cannot modify the QoS profiles associated with the UNIs, however, you can modify the QoS policies associated with the service endpoints.
| ||
Step 6 | Make the
required changes and click
Submit to preview the configuration that will be
deployed to the device.
| ||
Step 7 | Review your
changes and click
Deploy to deploy your changes to the device.
In case of a deploy failure on even a single device that is part of the service, the configration is rolled back on all devices participating in the service. | ||
Step 8 | To verify that your changes were saved, view the L3VPN service details. See View L3VPN Service Details. |
Using Cisco EPN Manager you can create and associate new VRFs to existing L3VPN services. You can also copy the route target and other details from existing VRFs to create new VRFs for the L3VPN service.
To associate new VRFs with an L3VPN service:
Step 1 | Navigate to . |
Step 2 | Click the
Circuits/VCs
tab and select the L3VPN service to which you want to
associate new VRFs.
You can also access the L3VPN Provisioning wizard by choosing Configuration > Network > Service Provisioning. |
Step 3 | Click the pencil (Modify) icon.
The L3VPN Provisioning wizard is displayed. |
Step 4 | Select Add VRF and click Next. |
Step 5 | Click the + icon to add the new VRF details manually. To auto populate the VRF details, click the device on the map to select it. The device details and a new name for the VRF are automatically populated on the VRF's page. |
Step 6 | You can copy
VRF details from an existing VRF by clicking the
Copy
From drop-down list and selecting the required VRF.
Only those VRFs that are associated with the selected L3VPN are displayed along with the VRFs route target, and route redistribution details. |
Step 7 | Otherwise, manually specify the details of the VRFs that you want to add to the selected VPN service. For more information about the different VRF parameters, see, Create and Provision a New L3VPN Service. |
Step 8 | Make any required changes such as adding endpoint and BGP neighbor details and click Submit. |
Step 9 | Preview the
configuration that is to be deployed to the device, make the required changes,
and click
Deploy
to deploy the changes to the device.
To verify that your changes were deployed, view the selected L3VPN service's details. See View L3VPN Service Details. For more information on modifying and deleting L3VPN services, see Delete an L3VPN Service Endpoint and Modify L3VPNs and VRFs. |
Cisco EPN Manager supports the provisioning of Circuit Emulation (CEM) services. CEM provides a bridge between the traditional TDM network and the packet switched network (PSN). It encapsulates the TDM data into packets, provides appropriate header, and send the packets through PSN to the destination node. For more information, see Supported Circuit Emulation Services.
You can also assign a MPLS TE tunnel to a CEM service to allow the CEM service to traverse through the network. Use the Preferred Path drop-down list in the Provisioning Wizard to assign a MPLS TE tunnel for a CEM service. For more information, see CEM Service Details References.
The following prerequisites must be met before you can provision a CEM service:
For information about the prerequisites that must be met before you can provision a CEM service, see Prerequisites for CEM Provisioning.
Step 1 | In the left sidebar, choose . | ||
Step 2 | Click Device Groups, and then select the location in which you want to create the CEM service. | ||
Step 3 | Close the Device Groups popup window. | ||
Step 4 | In the Network Topology window, click Circuits/VCs. | ||
Step 5 | Click the '+'
icon to open the Provisioning Wizard in a new pane to the right of the map.
You can also access the Provisioning wizard by choosing . | ||
Step 6 | From the Technology drop-down list, choose Circuit Emulation. | ||
Step 7 | From the Service Type drop-down list, choose the required CEM service type depending on the rate at which you want the circuit to transmit the data. For a list of CEM service types that Cisco EPN Manager supports, see Supported Circuit Emulation Services. | ||
Step 8 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||
Step 9 | Click Next to go to the Customer Service Details page. | ||
Step 10 | (Optional) Select the customer for whom the EVC is being created. If there are no customers in the list, go to Inventory > Other > Customers to create the customer in the system, and then go to the Provisioning Wizard to start provisioning the CEM service. | ||
Step 11 | Check the Activate check box to activate the interface associated with the service that you are provisioning. | ||
Step 12 | Enter the service name and its description. | ||
Step 13 | In the Deployment Action field, specify what you want to do when the CEM service creation process is completed. You can either request a preview of the configurations that will be deployed to the relevant devices before the actual deployment or you can deploy the configurations immediately upon completion. | ||
Step 14 | Click Next, and then enter the A End and Z End configurations, and the transport settings for the CEM service. See CEM Service Details References for descriptions of the fields and attributes. | ||
Step 15 | If one of the
endpoints is an interface on a device that is not managed by
Cisco EPN Manager
,
check the
Unmanaged Device check box and provide information
for the unmanaged device. See
Provision a Circuit/VC with an Unmanaged Endpoint
for more information.
| ||
Step 16 | (Optional) If you want to append a template with additional CLI commands that will be configured on the devices participating in the service, do so in the Template Details page. See Extend a Circuit/VC Using Templates for more information. | ||
Step 17 | When you have provided all the required information for the service, click Submit. If you chose to see a preview of the CLI that will be deployed to the devices, it will be displayed now and you can click Edit Attributes to change the attributes. Otherwise, the configurations will be deployed to the devices immediately. |
The CEM service should be added to the list in the Circuits/VCs pane in the Network Topology window To check the provisioning state, click on thei icon next to the circuit/VC name to see the Circuit/VC 360 view.
The following table lists and describes the attributes that define the CEM service types.
Attribute |
Description |
||
---|---|---|---|
A End and Z End Configurations | |||
Device |
Name of the source and destination devices in the CEM service. |
||
Working Path and Protecting Path | |||
Port Name or Interface Name |
Name of the interface on the source and destination devices in the CEM service. You can choose either the port name or the port group. When you choose the port name under the Protecting Path area, the unidirectional path switched ring (UPSR) protection mechanism is enabled. When you choose the port group under the Protecting Path area, the Automatic Protection Switching (APS) protection mechanism is enabled. For more information about how to configure protection groups, see View Protection Groups. |
||
Higher Order Path |
When a SONET/SDH line is channelized, it is logically divided into smaller bandwidth channels called higher order paths (HOP) and lower order paths (LOP). HOP or synchronous transport signal (STS) path is used to transport TDM data of higher bandwidth. HOPs can also contain LOPs within it. Select the path and path mode available for the CEM service. |
||
Lower Order Path |
LOPs or virtual tributary (VT) path is used to transport TDM data of lower bandwidth. |
||
DS0 Time Slot |
|
||
Clocking
The nodes in a network may be at different clock rates. Differences in timing at nodes may cause the receiving node to either drop or reread information sent to it. Clocking is essential to synchronize all nodes to the same clock rate. For more information about clocking, see Configure Clocking for CEM. |
|||
Clock Source |
|
||
QOS
The list of profiles available for selection includes policy maps that were configured on the device and discovered by the system, as well as user-defined QoS profiles. Refer to Create QoS Profiles for information on how to create QoS profiles. |
|||
Ingress QoS Profile |
Select the ingress QoS policies that are configured on the A end and Z end devices. |
||
Unmanaged Device
Details
|
|||
Unmanaged Device |
Check this check box to include a device that is not managed by Cisco EPN Manager and create partial service. |
||
New Device |
Check this check box to create a new unmanaged device. |
||
Device |
Choose an unmanaged device from the drop-down list.
|
||
Device Name |
Enter a unique name for the new unmanaged device that you want to create.
|
||
Device IP |
Enter the IP address of the new unmanaged device that you want to create.
|
||
LDP IP |
Enter a valid LDP IP for the unmanaged device. |
||
VC ID |
Enter a unique Virtual Circuit (VC) ID for the unmanaged device. |
||
Transport Settings | |||
Frame Type |
This field is display-only and is auto-populated based on the CEM service type that you chose when creating the CEM service. The values are SAToP and CEP. |
||
Payload Size |
Number of bytes put into each IP packet. The valid range is 32 – 1312. The bandwidth value is calculated based on the value specified for payload. If the payload value is blank, then bandwidth is calculated based on the default payload size of the service.
|
||
Dejitter Buffer Size |
Determines the ability of the emulated circuit to tolerate network jitter. The valid range is 1 - 32.
|
||
Idle pattern |
Idle pattern to transmit the data when the service goes down. The valid range is 0x00 - 0xFF. |
||
Dummy Mode |
Enables you to set a bit pattern for filling in for lost or corrupted frames. The values are last-frame and user-defined. |
||
Dummy Pattern |
|
||
RTP Header Enabled |
Check this check box to enable the Real-Time Transport Protocol (RTP) header for the CEM service. |
||
RTP Compression Enabled |
Check this check box to compress the IP header in a packet before the packet is transmitted. It reduces network overhead and speeds up the transmission of RTP. |
||
Pseudowire Settings | |||
Preferred Path Type |
Choose the Preferred Path Type as Bidirectional or Unidirectional. |
||
Preferred Path |
Select the MPLS bidirectional TE tunnel through which you want the CEM service to pass through.
|
||
Preferred Path (A-Z) |
Select the required unidirectional tunnel through which you want the CEM service to travel from the A endpoint to the Z endpoint.
|
||
Preferred Path (Z-A) |
Select the required unidirectional tunnel through which you want the CEM service to travel from the Z endpoint to the A endpoint.
|
||
Allow Fallback to LDP |
|
||
Send Control Word |
Check this check box if you want a control word to be used to identify the pseudowire payload on both sides of the connection. |
Cisco EPN Manager supports the provisioning of MPLS Traffic Engineering services. MPLS TE enables an MPLS backbone to replicate and expand the TE capabilities of Layer 2 over Layer 3. MPLS TE uses Resource Reservation Protocol (RSVP) to establish and maintain label-switched path (LSP) across the backbone. For more information, see Supported MPLS Traffic Engineering Services.
Cisco EPN Manager supports the following MPLS TE features:
Support for constraint-based routing, and trunk admission control.
Provision for path protection mechanism against link and node failures.
Usage of Resource Reservation Protocol (RSVP) to establish and maintain label-switched path (LSP).
Ability to advertise TE links using OSPF and ISIS.
Note | For the list of devices that support the provisioning of MPLS TE tunnel, see Cisco Evolved Programmable Network Manager Supported Devices |
The following prerequisites must be met before you can provision an MPLS TE service:
OSPF or IS-IS must be configured on the devices that participate on the MPLS TE service.
All links that will be used for MPLS TE service provisioning must be TE enabled.
The TE enabled links must be operationally up.
The tunnel's source and destination nodes must be reachable.
MPLS reachability must be set up between the devices. MPLS core network configuration must be set up.
Inventory collection status for the devices on which the MPLS TE service will be provisioned must be Completed. To check this, go to Last Inventory Collection Status column.
, and look at the status in theOptionally, customers can be created in the system so that you can associate an MPLS TE service to a customer during the service creation and provisioning process. From the left sidebar, choose
to create and manage customers.To provision an MPLS TE tunnel:
For information about the prerequisites that must be met before you can provision an MPLS TE tunnel, see Prerequisites for Provisioning an MPLS TE Service
Step 1 | From the left sidebar, choose . |
Step 2 | Click Device Groups, and then select the location in which you want to create the MPLS TE tunnel. |
Step 3 | Close the Device Groups popup window. |
Step 4 | In the Network Topology window, click Circuits/VCs. |
Step 5 | Click the '+' icon to open the Provisioning Wizard in a new pane to the right of the map. |
Step 6 | From the Technology drop-down list, choose MPLS TE. Cisco EPN Manager displays a list of relevant service types in a Service Type area. |
Step 7 | In the Service Type area, choose Unidirectional TE Tunnel or Bidirectional TE Tunnel. |
Step 8 | If you have defined profiles to set the attributes of the different services, choose the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. |
Step 9 | Click Next to go to the Customer Service Details page. |
Step 10 | (Optional) Select the customer for whom the service is being provisioned. If there are no customers in the list, go to to create the customer in the system, and then restart the Provisioning wizard. |
Step 11 | Enter the service name and its description, and then enter the service details. See Field References for Service Details—MPLS TE Tunnel. |
Step 12 | Click Next, and then enter the tunnel creation parameters. See Field References for Tunnel Creation—MPLS TE Tunnel for descriptions of the fields and attributes. |
Step 13 | Click Next, and then enter the path constraint details. See Field References for Path Constraint Details—MPLS TE Tunnel for descriptions of the fields and attributes. |
Step 14 | Click Submit. If you chose to see a preview of the CLI that will be deployed to the devices, it will be displayed now and you can click Edit Attributes to change the attributes. Otherwise, the configurations will be deployed to the devices immediately. |
The service should be added to the list in the Circuits/VCs pane in the Network Topology window. To check the provisioning state, click the i icon next to the circuit/VC name to see the Circuit/VC 360 view.
The following table lists and describes the attributes that define the service details for creating a MPLS TE tunnel.
Attribute |
Description |
||
---|---|---|---|
Enable FRR |
Check this check box to enable the fast reroute feature that provides link and node protection for your MPLS TE tunnel.
|
||
Enable Auto Bandwidth |
Check this check box to automatically assign maximum and minimum bandwidth to the TE tunnel based on the traffic.
|
||
Wrap Protection |
Check this check box to detect mid-link failure scenarios. |
||
Enable Fault OAM |
Check this check box to enable the fault OAM protocols and messages that support the provisioning and maintenance of MPLS TE tunnels.
|
||
Enable Autoroute |
Check this check box to enable autoroute for the tunnel. |
||
Enable LockDown |
Check this check box if you do not want to reoptimize the working LSP. |
||
Enable BFD Settings |
Check this check box to enable the Bidirectional Forwarding Detection (BFD) protocol. BFD provides fast forwarding path failure detection time and a consistent failure detection method. |
||
Protection Type |
Choose one of the following protection mechanism for the TE tunnel:
|
||
Deployment Action |
Choose one of the following options to specify what you want to do when the MPLS TE tunnel creation process is completed: |
The following table lists and describes the attributes that define the MPLS TE tunnel creation.
Attribute |
Description |
||
---|---|---|---|
Create Tunnel | |||
Source |
Source or A endpoint of the tunnel. |
||
Source routing Process |
OSPF routing process that is TE enabled and configured on the source endpoint selected. You can determine the router ID and loopback address configured on the source endpoint based on the OSPF routing process. |
||
Destination |
Destination or Z endpoint of the tunnel. |
||
Destination Routing Process |
OSPF routing process that is TE enabled and configured on the destination endpoint selected. You can determine the router ID and loopback address configured on the destination endpoint based on the OSPF routing process. |
||
Tunnel Setting | |||
Global ID |
The global ID assigned to both, source and destination endpoints. This ID must be the same to bind two unidirectional tunnels into a bidirectional TE tunnel. The default value is 0. |
||
Affinity Bits |
The affinity bit determines the link attribute that the bidirectional TE tunnel will use when configuring the dynamic backup paths. |
||
Affinity Mask |
The affinity mask determines which link attribute the router must check. You can use affinity bits and affinity mask to include or exclude link attributes when configuring the dynamic backup paths. If a bit in the mask is 0, the value of the associated link attribute for that bit is irrelevant. In this case, the link attribute is excluded when configuring the dynamic backup paths. If a bit in the mask is 1, the value of the associated link attribute must match the affinity of the tunnel for that bit. In this case, the link attribute is included when configuring the dynamic backup paths. |
||
Setup Priority |
Setup priority assigned to an LSP for the bidirectional TE tunnel. Based on this priority, the LSP can determine which existing tunnels or LSPs with low priority can be blocked.
|
||
Hold Priority |
Hold priority assigned to an LSP for the bidirectional TE tunnel. Based on this priority, the LSP can determine whether it must be blocked by another signaling LSP with a high setup priority. Valid values are from 0 to 7. A lower number indicates a higher priority. For example, an LSP with a hold priority of 0 cannot be blocked by another LSP. |
||
Bandwidth Pool Type |
|
||
Bandwidth |
Bandwidth for the bidirectional TE tunnel. The value must be specified in the units of Kbps. For example, if you want to assign a bandwidth of 1000000 Kbps for the tunnel, enter the value as 1000000 Gbps.
|
||
Auto Bandwidth Max |
Cisco EPN Manager automatically assigns the maximum bandwidth for the unidirectional TE tunnel based on the traffic. However, you can change the bandwidth, if required.
|
||
Auto Bandwidth Min |
Cisco EPN Manager automatically assigns the minimum bandwidth for the unidirectional TE tunnel based on the traffic. However, you can change the bandwidth, if required.
|
||
Bandwidth Change Frequency (Sec) |
Enter the bandwidth change frequency in seconds. The valid range is between 300 to 604800. |
||
BFD Settings | |||
Min Interval |
BFD uses intervals and multipliers to specify the periods at which control and echo packets are sent in asynchronous mode and their corresponding failure detection. A failure detection timer is started based on (I x M), where I is the minimum interval, and M is the multiplier.
|
||
Multiplier |
The following table lists and describes the attributes that define the path constraint details for creating a MPLS TE tunnel.
Attribute |
Description |
||
---|---|---|---|
Path Type |
Choose the required path for the TE tunnel. The values are Working, Protected, and Restore. |
||
Working Path,
Protection Path, and
Restore Path
Based on the value you choose in the Path Type field, the respective field group is available. |
|||
Type |
Choose the type of working path or protected path for the tunnel. Values are Dynamic and Explicit. |
||
New |
|
||
Select Existing Path |
Choose an existing explicit working, protected, or restore path for the tunnel.
|
||
Path Name |
Enter a name for the explicit path that you are creating. In the Working Path, Protection Path, or Restore Path table, click the '+' button to add a new row to the table, and then select a MPLS-enabled device, an explicit path controller as the interface for the device, and a path constraint type. In the path table, you can select any MPLS-enabled device except the source and destinations devices. Cisco EPN Manager supports only strict path constraint type.
|
To provision an MPLS Layer 3 Link:
For information about the prerequisites that must be met before you can provision an MPLS Layer 3 Link, see Prerequisites for Provisioning an MPLS TE Service.
Step 1 | From the left sidebar, choose | ||
Step 2 | Click Device Groups, and then select the location in which you want to create the MPLS Layer 3 Link. | ||
Step 3 | Close the Device Groups popup window. | ||
Step 4 | In the Network Topology window, click Circuits/VCs. | ||
Step 5 | Click the '+' icon to open the Provisioning Wizard in a new pane to the right of the map. | ||
Step 6 | From the Technology drop-down list, choose MPLS TE. Cisco EPN Manager displays a list of relevant service types in the Service Type area. | ||
Step 7 | In the Service Type area, choose Layer 3 Link. | ||
Step 8 | If you have defined profiles to set the attributes of the different services, choose the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. | ||
Step 9 | Click Next to go to the Link Settings page. | ||
Step 10 | Enter a name and description for the layer 3 link. | ||
Step 11 | Choose the
A End
Device,
A End
Interface,
Z End
Device, and
Z End
Interface fields using one of the following ways:
| ||
Step 12 | Enter the IP address and mask for the A End and Z End devices. | ||
Step 13 | Choose an L2
Discovery Protocol from the following options:
| ||
Step 14 | Choose the required routing protocol for the layer 3 link. The values are BGP, ISIS, and OSPF. For information about how to configure the routing protocols, see Configure Routing Protocols and Security | ||
Step 15 | (Optional) Enter a Link VLAN ID for the layer 3 link. | ||
Step 16 | (Optional)
Check the
Enable
MPLS TE check box to support MPLS TE on the layer 3 link that you
are provisioning.
| ||
Step 17 | Click Next, and then enter the A End and Z End details. See Field References for A End Details and Z End Details in MPLS Layer 3 Link for descriptions of the fields and attributes. | ||
Step 18 | In the Deployment Action field, specify what you want to do when the MPLS layer 3 link creation process is completed. You can either request a preview of the configurations that will be deployed to the relevant devices before the actual deployment or you can deploy the configurations immediately upon completion. | ||
Step 19 | Click Submit. If you chose to see a preview of the CLI that will be deployed to the devices, it will be displayed now and you can click Edit Attributes to change the attributes. Otherwise, the configurations will be deployed to the devices immediately. |
The service should be added to the list in the Circuits/VCs tab in the Network Topology window. To check the provisioning state, click the i icon next to the circuit/VC name to see the Circuit/VC 360 view.
The following table lists and describes the attributes that define the MPLS Layer 3 Link.
Attribute |
Description |
Available when the routing protocol is: |
||
---|---|---|---|---|
Same as A End |
|
BGP, ISIS, and OSPF |
||
BGP AS Number |
Choose the unique BGP autonomous system number assigned for your network. |
BGP |
||
Route Policy |
Choose the routing policy to control which routes the BGP stores in and retrieves from the routing table. |
BGP |
||
Route Reflector Client |
Check this check box to configure the BGP neighbor as the route reflector client for the local route reflector to advertise the available routes. |
BGP |
||
Use AIGP |
Check this check box to use the Accumulated Interior Gateway Protocol (AIGP) metric attribute for the layer 3 link. The AIGP is the BGP attribute that carries the accumulated end-to-end metrics for the paths in the network. |
BGP |
||
Update Source |
Choose the required source interface.
|
BGP |
||
ISIS Process ID |
Choose an ISIS routing process ID that is available to both A end and Z end devices. For information about how to configure an ISIS process, see Configure an IS-IS Routing Protocol. |
ISIS |
||
Network |
The network ID is automatically populated based on the ISIS process ID selected. |
ISIS |
||
Circuit Type |
Choose the type of adjacency required for the layer 3 link from the following options:
|
ISIS |
||
Level 1 Metric |
Enter the metric that must be used in the SPF calculation for Level 1 (intra-area) routing.
|
ISIS |
||
Level 2 Metric |
Enter the metric that must be used in the SPF calculation for Level 2 (inter-area) routing.
|
ISIS |
||
OSPF Process ID |
Choose an OSPF routing process ID. For information about how to configure an OSPF process, see Configure OSPF Routing Processes.
|
OSPF |
||
OSPF Area |
Enter the area in which you want to deploy the OSPF routing process. |
OSPF |
||
Metric |
Enter the routing metric used by the OSPF routing process. |
OSPF |
||
BFD Template |
Choose a BFD template for the layer 3 link. A BFD template defines the set of configurable parameters used by a BFD session. These include the transmit and receive timers used for BFD control and echo packets, the transmit timer interval used when the session is providing a CV function, the multiplier value, and the echo-receive interval. |
BGP, ISIS, and OSPF |
||
BFD Min Interval |
Enter the minimum control packet interval for BFD sessions for the corresponding BFD configuration scope.
|
BGP, ISIS, and OSPF |
||
BFD Multiplier |
Enter the BFD multiplier. This value along with the BFD minimum interval is used to determine the intervals and failure detection times for both control and echo packets in asynchronous mode on bundle member links.
|
BGP, ISIS, and OSPF |
||
BFD Fast Detect |
Check this check box to quickly detect failures in the path between adjacent forwarding engines. ISIS and OSPF |
|||
Authentication Mode |
Choose the required authentication mode used to send and receive ISIS packets.
|
ISIS |
||
Authentication Key Chain |
Choose the authentication key chain. This enables authentication for routing protocols and identifies a group of authentication keys. |
ISIS |
||
Authentication for Send Only |
Check this check box to perform authentication only for ISIS packets that are being sent. |
ISIS |
||
Password Type |
Choose the password type as Encrypted or Plain Text. |
BGP |
||
Password |
Type the desired password. Password is required to establish connection between two peers. |
BGP |
||
MPLS-TE | ||||
Loopback Interface |
Choose a loopback interface address for the layer 3 link. For information about how to configure a loopback interface, see Configure Loopback Interfaces. |
ISIS and OSPF |
||
TE Metric |
Enter the MPLS TE tunnel metric with mode absolute. |
ISIS and OSPF |
||
TE Attributes |
Enter the MPLS TE Link attribute to be compared with a tunnel's affinity bits during path selection. |
ISIS and OSPF |
||
Is Percentage |
Check this check box to assign the bandwidth in percentage for the layer 3 link. |
ISIS and OSPF |
||
Global Bandwidth |
Enter the regular TE tunnel bandwidth that will be reserved for the layer 3 link for CBR. For example, if you want to assign 10% as the global bandwidth for the layer 3 link, select the Is Percentage check box and enter the value 10 in the Global Bandwidth field. Whereas, if you want to assign 50 Kbps as the global bandwidth, uncheck the Is Percentage check box, choose Kbps from the Bandwidth Unit drop-down list, and then enter the value 50 in the Global Bandwidth field. |
ISIS and OSPF |
||
Subpool Bandwidth |
Enter the subpool bandwidth that is reserved from the global pool bandwidth. For example, if you want to assign 10% as the subpool bandwidth for the layer 3 link, select the Is Percentage check box and enter the value 10 in the Subpool Bandwidth field. Whereas, if you want to assign 50 Kbps as the subpool bandwidth, uncheck the Is Percentage check box, choose Kbps from the Bandwidth Unit drop-down list, and then enter the value 50 in the Subpool Bandwidth field. |
ISIS and OSPF |
||
QoS | ||||
Ingress Policy |
Select the ingress QoS policies that are configured on the A end and Z end devices. |
BGP, ISIS, and OSPF |
||
Egress Policy |
Select the egress QoS policies that are configured on the A end and Z end devices. |
BGP, ISIS, and OSPF |
||
Additional Settings | ||||
Enable MPLS |
Check this check box to support MPLS on the layer 3 link that you are provisioning. |
BGP |
||
Enable SyncE |
Check this check box to enable Synchronous Ethernet at the interface level for the layer 3 link. |
BGP, ISIS, and OSPF |
Following are the prerequisites to provision a serial circuit/VC:
Communication between devices must be set up before you can provision a serial circuit/VC.
Inventory collection status for the devices on which the Serial circuits/VCs will be provisioned must be "Completed". To check this, go to
, and look at the status in the Last Inventory Collection Status column.Optionally, customers must be created in the system so that you can associate a circuit/VC to a customer during the circuit/VC creation and provisioning process. From the left sidebar, choose
to create and manage customers.To create a new serial circuit/VC:
For information about the prerequisites that must be met before you can provision a serial circuit/VC, see Prerequisites for Serial Circuits/VCs Provisioning.
Step 1 | From the left
sidebar, choose
.
The network topology window opens. |
Step 2 | From the toolbar, click Device Groups and then select the group of devices you want to show on the map. |
Step 3 | Click the Circuits/VCs tab. |
Step 4 | From the
Circuits/VCs pane toolbar, click the
+ (Create) icon.
The Provisioning Wizard opens in a new pane to the right of the map. |
Step 5 | Select Serial in the Technology drop-down list |
Step 6 | In the Service Type list, select RS232. |
Step 7 | If you have defined profiles to set the attributes of the different services, select the required profile from the Select Profile drop-down list. See Create Circuit/VC Profiles. |
Step 8 | Click Next to go to the Service Details page. |
Step 9 | Select the customer for whom the circuit/VC is being created. If there are no customers in the list, go to Inventory > Other > Customers to create the customer in the system, and then restart the Provisioning Wizard. |
Step 10 | In the Deployment Action field, specify what you want to do when the circuit/VC creation process is completed. You can either request a preview of the configurations that will be deployed to the relevant devices before the actual deployment or you can deploy the configurations immediately upon completion. |
Step 11 | Click Next to go to the page in which you configure the endpoints. |
Step 12 | If one of the endpoints is an interface on a device that is not managed by Cisco EPN Manager , provide information for the unmanaged device. See Provision a Circuit/VC with an Unmanaged Endpoint |
Step 13 | Click Next to go to the Line Settings and Pseudowire Settings page. See Serial Service Details Reference |
Step 14 | Optional. If you want to append a template with additional CLI commands that will be configured on the devices participating in the circuit/VC, do so in the Template Details page. See XREF for more information. |
Step 15 | When you have provided all the required information for the circuit/VC, click Submit. If you chose to see a preview of the CLI that will be deployed to the devices, it will be displayed now and you can click Edit Attributes to change the attributes. Otherwise, the configurations will be deployed to the devices immediately. |
Step 16 | The circuit/VC should be added to the list in the Circuits/VCs pane in the Network Topology window. |
The following table lists and describes the attributes that define the serial service type.
Attribute |
Description |
||
---|---|---|---|
A Endpoint and Z Endpoint Configurations | |||
Device Name |
Name of the source and destination devices in the serial service. |
||
Port Name and Description |
Name and description of the interface on the source and destination devices in the serial service. |
||
QOS
The list of profiles available for selection includes policy maps that were configured on the device and discovered by the system, as well as user-defined QoS profiles. Refer to Create QoS Profiles for information on how to create QoS profiles. |
|||
Ingress QoS Profile |
Select the ingress QoS policies that are configured on the A end and Z end devices. |
||
Egress QoS Profile |
Select the egress QoS policies that are configured on the A end and Z end devices. |
||
Unmanaged Device
Details
|
|||
Unmanaged Device |
Check this check box to include a device that is not managed by Cisco EPN Manager and create partial service. |
||
New Device |
Check this check box to create a new unmanaged device. |
||
Device |
Choose an unmanaged device from the drop-down list.
|
||
Device Name |
Enter a unique name for the new unmanaged device that you want to create.
|
||
Device IP |
Enter the IP address of the new unmanaged device that you want to create.
|
||
LDP IP |
Enter a valid LDP IP for the unmanaged device. |
||
VC ID |
Enter a unique Virtual Circuit (VC) ID for the unmanaged device. |
||
Line Settings | |||
Speed |
The speed of the serial link in kilo bits per second. |
||
Data Bits |
The measurement of actual data per packet that is transmitted through the serial circuit/VC. The values are 5, 6, 7, and 8. |
||
Stop Bits |
Indicates the end of communication for a single packet. The values are 1, 1.5, and 2 bits. Since the data is clocked across the lines and each device has its own clock, it is possible for the two devices to become slightly out of sync. Therefore, the stop bits not only indicate the end of transmission but also provides the network with some lenience to synchronize the different clocks. The more bits that are used for stop bits, the greater the lenience in synchronizing the different clocks, but slower the data transmission rate. |
||
Flow Control In and Flow Control Out |
Manages the rate of data transmitted between two devices when the source device transmits data at a faster rate than the destination device can receive it. It provides a mechanism for the source device to control the transmission speed, so that the destination device is not overwhelmed with data that is transmitted. The values are None, Hardware, and Software. |
||
Flow Control Lock |
Enables or disables the flow control mechanism for the serial circuit/VC. The values are True and False. |
||
Parity |
Used to check errors in serial communication. The values are:
|
||
Pseudowire Settings | |||
Preferred Path Type |
Choose the Preferred Path Type as Bidirectional or Unidirectional. |
||
Preferred Path |
Select the MPLS bidirectional TE tunnel through which you want the serial service to pass through.
|
||
Preferred Path (A-Z) |
Select the required unidirectional tunnel through which you want the serial service to travel from the A endpoint to the Z endpoint.
|
||
Preferred Path (Z-A) |
Select the required unidirectional tunnel through which you want the serial service to travel from the Z endpoint to the A endpoint.
|
||
Send Control Word |
Check this check box if you want a control word to be used to identify the pseudowire payload on both sides of the connection. |
Profiles contain sets of attributes specific to the different types of circuits/VCs. Once a profile is created, it will be available to all users for selection during circuit/VC creation. When a profile is selected, the Provisioning Wizard is populated with the profile attributes. Users only have to define the endpoints of the service and, if necessary, make small changes before provisioning the circuit/VC.
The types of profiles you can create mirror the types of circuits/VCs that can be provisioned.
Each profile is given a unique name, so you can create multiple profiles per circuit/VC type, depending on your needs.
To create a profile:
Step 1 | Choose Inventory > Other > Profiles in the left navigation pane. The Profiles window opens, showing a table of existing profiles (if any). You can select a profile in the table to edit or delete it. |
Step 2 | Click Create Profile. |
Step 3 | In the Create Profile wizard, provide a unique name for the profile and enter a description. |
Step 4 | Select Carrier Ethernet or Optical or L3VPN from the Technology list. The relevant service types for the selected technology are displayed. |
Step 5 | Select the
required service type.
For L3VPN services, choose Unicast to create a profile that helps pre-populate values for most L3VPN service creation fields. And choose IPSLA Operations to create a profile with IP SLA specific options for the L3VPN service. |
Step 6 | Click
Next to go to
the attribute definition pages and define the attributes for the selected
service type. The attributes in the profile are the same as the attributes in
the Provisioning Wizard and they are described in the reference sections, as
follows:
Information on Ethernet VCs attributes is provided in these topics:
Information on L3VPN attributes is provided in Create and Provision a New L3VPN Service and View L3VPN Service Details. |
Step 7 | Click Create Profile when you have defined the attributes. The profile will be added to the table in the Profiles window. |
You can create a library of QoS profiles that will be available for selection when creating and provisioning EVCs. The selected QoS profile determines the bandwidth profile for traffic of various classes on the UNI or the EVC level, and defines how the classified traffic is treated.
The QoS profile can define up to four levels of bandwidth profile: Extra High, High, Medium, and Low. For each bandwidth profile, you specify the matching criteria that must be met for the traffic to be classified as belonging to that bandwidth profile.
To create a QoS profile:
Step 1 | Follow the instructions in Create and Provision a New Carrier Ethernet EVC to access the Provisioning Wizard. |
Step 2 | Select Carrier Ethernet from the Technology drop-down list. |
Step 3 | Select QoS Profile from the Service Types drop-down list. |
Step 4 | Click Next to go to the QoS Profile definition page. |
Step 5 | Provide the QoS profile with a unique name and description. |
Step 6 | Check the
required check boxes to define where the QoS profile will be available for
selection (i.e., it will appear in the drop-down list of QoS profiles):
|
Step 7 | In the
Classification field, indicate what method will be used to identify and
classify the traffic, then enter the relevant values in the Match Criteria
field for the required bandwidth profiles:
|
Step 8 | Select one or more classes of service that will apply to the service. |
Step 9 | For each class of service you selected, define a bandwidth profile to specify the match criteria and how the matching traffic will be handled.For each bandwidth profile, enter the match criteria, as described in Step 7 above. |
Step 10 | For each
bandwidth profile, create rules to specify how the matching traffic will be
handled. You can create a separate rule for ingress and egress traffic or you
can create a rule for traffic moving in both directions. In each rule, you can
specify the following:
|
Step 11 | Click Submit when you have defined all the required bandwidth profiles. Your QoS profile will be created and will be available for selection when you are creating VCs. |
Customers must be created in the system so that they are available for selection during the circuit/VC provisioning process.
To create a customer:
You can create and provision a circuit/VC even if one or more of the endpoints is a device that is not managed by Cisco EPN Manager . The Provisioning Wizard allows you to identify an endpoint device as "unmanaged" and to provide information about that device so that the system can create the circuit/VC. Once you identify the unmanaged device, it will be available in the system in the Unmanaged Devices group and can be used for other services.
Step 1 | Start the circuit/VC creation process for the required technology, as described in Provision Circuits/VCs. |
Step 2 | For a
point-to-point EVC and a CEM service:
|
Step 3 | For a point-to multipoint or multipoint -to-multipoint EVC: In the Unmanaged UNI page, click the Plus icon in the table to add a row and then define the Unmanaged Device Details and Service Endpoint details for the selected row. |
Step 4 | Complete the circuit/VC creation and provisioning process for the required technology, as described in Provision Circuits/VCs. |
When you create and provision a circuit/VC, Cisco EPN Manager configures a set of CLI commands on the participating devices. If you need to configure additional commands on the same devices, you can create a template containing these commands and you can include it during the circuit/VC creation process. This effectively extends the circuit/VC beyond what is configured by Cisco EPN Manager . This functionality is available in the provisioning wizard but it is dependent on the template being created prior to creating or modifying the circuit/VC.
Extending a circuit/VC using CLI templates involves the following steps:
Create the CLI template using blank templates or existing templates. See Create a New CLI Configuration Template Using a Blank Template and Create a New CLI Configuration Template Using An Existing Template.
Create/modify a circuit/VC and append the CLI template. See Provision Circuits/VCs.
Step 1 | Create the CLI
template:
|
Step 2 | Create/modify a
service that includes the template you created (or a different template if
relevant):
|
Example Configuration 1: Extending an L3VPN service on a Cisco ASR 903 device using a CLI template with Global and Template (Local) variables:
vrf definition Testdoc1 exit vrf Testdoc1 vpn id 36B:3 address-family ipv4 unicast import route-target 65:1 export route-target 65:1 address-family ipv6 unicast import route-target 65:1 export route-target 65:1 interface GigabitEthernet0/0/0/11.2 vrf Testdoc1 ipv4 address 4.5.7.8 255.255.255.0 mtu 1522 router bgp 140 vrf Testdoc1 rd auto address-family ipv6 unicast address-family ipv4 unicast redistribute static metric 54 neighbor 3.4.6.8 remote-as 21 address-family ipv4 unicast exit exit exit exit interface GigabitEthernet0/0/6 desc postconfig delay 5988 mtu 436 exit
Example Configuration 2: Extending a CEM service using a CLI template with a global variable and a template (local) variable:
#set($interfaceNameList = $gv.service-cem-cemInterfaceNameList.split(",")) #set($cemGroupNumberList = $gv.service-cem-cemGroupNumberList.split(",")) #set($count = 0) #foreach($interfaceName in $interfaceNameList) interface $interfaceName service-policy input MainInterfacePolicy #if($count == 0) cem $cemGroupNumberList[0] #else cem $cemGroupNumberList[1] #end service-policy input servicePolicy #set($count = $count+1) #end
Example Configuration 3: Extending a CEM service to configure QoS over CEM:
#set($count = 0) #foreach($interfaceName in $gv.service-cem-cemInterfaceNameList) interface $interfaceName service-policy input MainInterfacePolicy #if($count == 0) cem $gv.service-cem-cemGroupNumberList[0] #else cem $gv.service-cem-cemGroupNumberList[1] #end service-policy input servicePolicy #set($count = $count+1) #end exit
Example Configuration 4: Extending a CE service using a CLI template with global and template variables on a Cisco ME3800 device. The highlighted text represents the pre-config and post-config configuration changes that are appended and prepended to the CE service provisioning configuration.
pseudowire-class PWClass_51_192-168-12-29 protocol ldp exit ethernet cfm domain EVC level 4 service evplextnpseudowireclass_ evc evplextnpseudowireclass_ continuity-check continuity-check interval 1s ethernet evc evplextnpseudowireclass interface GigabitEthernet0/11 no shutdown no spanning-tree portfast mtu 1522 ethernet uni id 3800x service instance 1 ethernet evplextnpseudowireclass encapsulation dot1q 88 xconnect 192.168.12.29 51 encapsulation mpls pw-class PWClass_51_192-168-12-29 mtu 1508 service instance 1 ethernet evplextnpseudowireclass_ cfm mep domain EVC mpid 2 ethernet lmi ce-vlan map 88 ip sla 17 ethernet y1731 loss SLM domain EVC evc evplextnpseudowireclass_ mpid 1 cos 5 source mpid 2 history interval 5 aggregate interval 60 ip sla schedule 17 life forever start-time after 00:02:00 interface GigabitEthernet0/11 desc postconfig exit