PDF(284.4 KB) View with Adobe Reader on a variety of devices
Updated:August 3, 2017
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.
Cisco Prime Provisioning 6.8.2 is a maintenance release to be installed on Prime Provisioning 6.8, 126.96.36.199 or 188.8.131.52 or 184.108.40.206. Schema upgrade is supported from 6.8/220.127.116.11/18.104.22.168/22.214.171.124 to 6.8.2.
This release contains the following enhancements under different service blades and infrastructure:
Layer 2 (L2EVC)
– EVPN-VPWS support through customization policy.
– EVPN-VPLS support through customization policy.
– Support for Manual Allocation of IPv6 Address from IPv6 Address Pool.
– Extended VLAN-ID ranges support for BVI Interfaces (ranges of 1-65535).
– initdb script enhancements to retain DCPL values with configured values.
– Red Hat Enterprise Linux support for 6.8, 7.0 and 7.2 versions.
See the New Features and Enhancements in Prime Provisioning 6.8.2 for a list of point patches whose enhancements and defect resolutions have been merged into 6.8.2.
All documentation, including this Cisco Prime Provisioning 6.8.2 Release Notes document and any or all parts of the Prime Provisioning 6.8 documentation set, might be upgraded over time. Therefore, we recommend that you access the Prime Provisioning documentation at:
You can also navigate to this documentation set by clicking Help on the Home Page of the Prime Provisioning 6.8.2 product. The “Related Documentation” section gives the URL for the most current version of each guide to be used with Cisco Prime Provisioning 6.8.2.
The information in this Cisco Prime Provisioning 6.8.2 Release Notes document gives you an overview of this release and helps you understand what has changed since Cisco Prime Provisioning 6.8.1. Please read this document prior to reading any other guides or documents for Cisco Prime Provisioning 6.8.2.
Prime Provisioning is a management solution for network provisioning that enables the automation and scaling of complex, policy-driven network provisioning tasks to produce consistent and reliable service deployments. Prime Provisioning does this by planning, provisioning, and auditing services across core, aggregation, access, and consumer premises equipment devices.
Cisco Prime Provisioning enables fast deployment and time-to-market of Multiprotocol Label Switching (MPLS) and Carrier Ethernet technologies. In addition, the Prime Provisioning Traffic Engineering Management (TEM) module is Cisco’s exclusive planning and provisioning tool for Cisco MPLS Traffic Engineering-enabled routers. MPLS Transport Profile (TP) provides service providers with a reliable packet-based technology that is based upon circuit-based transport networking, and hence is expected to align with current organizational processes and large-scale work procedures similar to other packet transport technologies.
The Cisco Prime Provisioning solution has management capabilities for MPLS VPN, L2VPN and Carrier Ethernet, MPLS TP, and MPLS Traffic Engineering. These capabilities that comprise Cisco Prime Provisioning can be used in a stand-alone manner or can be integrated with the Prime Carrier Management August 2017 suite and corresponding suite product updates.
The system recommendations for Prime Provisioning 6.8.2 are based on those for Prime Provisioning 6.8 (with some restrictions, as noted). The new devices and platforms supported in addition to those supported in Prime Provisioning 6.8.2 are referenced in the “System Recommendations” section.
The Prime Provisioning 6.8.2 documentation includes the Prime Provisioning 6.8 document set and the updated information for Prime Provisioning 6.8.2 found in this Cisco Prime Provisioning 6.8.2 Release Notes. The entire documentation set is listed in the “Related Documentation” section.
Web Browser Support
Prime Provisioning 6.8.2 GUI is supported by the following browsers:
You can install Prime Provisioning 6.8.2 on Prime Provisioning 6.8/126.96.36.199/188.8.131.52/184.108.40.206. Schema upgrade is supported from 6.8/220.127.116.11/18.104.22.168/22.214.171.124 to 6.8.2. Therefore, repository migration can only be performed from 6.8/126.96.36.199/188.8.131.52/184.108.40.206. To migrate from earlier releases (prior to 6.8), you must first upgrade to Prime Provisioning 6.8/220.127.116.11/18.104.22.168/22.214.171.124 release. See “Prime Provisioning 6.8.2 Patch Installation” section.
Note$PRIMEF_HOME and <PRIMEF_HOME> represents the location where the latest version of Cisco Prime Provisioning is installed. <REPOSITORY_HOME> represents the location of the Repository folder created in the Prime Provisioning directory.
6.8/126.96.36.199/188.8.131.52/184.108.40.206 to 6.8.2 Standalone or Suite Mode Installation
To install Prime Provisioning 6.8.2 maintenance path in Standalone mode or Suite mode follow these steps:
Note To install Prime Provisioning 6.8.2, you must have 6.8/220.127.116.11/18.104.22.168/22.214.171.124 previously installed.
Note Prior to installing Prime Provisioning 6.8.2, if you are moving a repository from one machine to another, the schema upgrade fails unless the repository has been initialized on the new machine. This requires that you successfully run initdb.sh on the repository to update the host entry. To run initdb.sh, execute the following command from <PRIMEF_HOME> location: ./prime.sh initdb.sh.
Note If you have difficulties accessing the software from this location, please go to Cisco.com and choose Support > Downloads > Cloud and Systems Management > Routing and Switching Management > Fullfillment Products > Cisco Prime Provisioning.
Note You should place the retrieved tar file in a directory outside of the <PRIMEF_HOME> directory structure.
Step 3 Before you install Prime Provisioning 6.8.2, verify that you have 100 MB of free space in the
> directory and that you are logged in with the same username as the owner of your supported version of Prime Provisioning.
Step 4 Navigate to the directory where the Prime Provisioning 6.8.2 software is downloaded.
Step 5 Untar (unzip) the software prime-provisioning-6_8_2-11.tar.gz using the command:
tar -xvf prime-provisioning-6_8_2-11.tar.gz
Step 6 If Prime Provisioning is running, navigate to <
> directory and use the following command to stop the database, name server, and WatchDog on the machine on which it is running:
Note To check if Prime Provisioning is running, execute the command ./prime.sh status in <PRIMEF_HOME> location.
Step 7 Use the following command to run the
patch installation script:
You will be prompted with the following message “Enter a new path or press
for the default
Step 8 To specify the path, where the patch has to be installed, follow the steps below:
a. Press Enter, if you want to accept the default path.
b. Enter the path, where the prime has already been installed.
c. To terminate the installer at any time, press
Step 9 At the end of the installation, you will get the following message:
"Do you want to continue the installation in Standalone mode?"
Enter yes to finish the installation. This completes the installation process and the installation stops immediately.
6.8/126.96.36.199/188.8.131.52/184.108.40.206 to 6.8.2 Suite Mode Installation
To continue installing the Prime Provisioning 6.8.2 maintenance patch in suite mode, follow these steps:
Note To install Prime Provisioning 6.8.2, you must have 6.8/220.127.116.11/18.104.22.168/22.214.171.124 previously installed.
Step 1 During patch installation, if Prime Provisioning is installed in suite mode, you will get the following message:
"Do you want to continue the patch installation?[yes/no]"
To terminate the patch installation in suite mode, enter no.
Step 2 Enter yes to continue with suite mode installation.
Step 3 Enter the following details about the Prime Central database on prompt:
Server IP Address- IP Address of the Prime Central Database server
SID- Server instance identifier of the Prime Central Database server
Port- Port number of the Prime Central Database server
DB User- Database username of the Prime Central Database server
DB Password- Database password associated with the above user name.
Upgrading Prime Provisioning
If you want to migrate from an existing installation to Prime Provisioning 6.8.2, your upgrade path depends on which release you are upgrading from. This process is explained in detail in Chapter 4, “Upgrading Prime Provisioning” of the Cisco Prime Provisioning Installation Guide 6.8.
The various possible upgrade paths are described in
for upgrade instructions
Enterprise Oracle 12C
Linux (Red Hat)
Using the Upgrade Tool for Schema Upgrade
The following steps describe how to use the upgrade tool to update the database schema. To upgrade the schema from Prime Provisioning 6.8/126.96.36.199/188.8.131.52/184.108.40.206 to Prime Provisioning 6.8.2, follow these steps:
Step 1 Copy the upgrade tool from the image location to any preferred location. For example:
Step 2 Use the following command to untar or unzip prime_provisioning_682_upgradeTool.tar.gz:
tar -xvf prime_provisioning_682_upgradeTool.tar.gz
Step 3 Unzip the file isc-upgrade.zip to extract its contents:
Step 4 Go to the upgradeTool folder and execute the following command to run the upgrade tool:
$ ./upgradeISCSchema.sh $PRIMEF_HOME
Step 5 Provide the admin credentials on prompt to continue with the upgrade tool installation.
Please enter ISC admin user name [admin]:
Please enter admin password:
Step 6 Navigate to
Step 7 Execute .
command to start Prime Provisioning.
To uninstall the Prime Provisioning 6.8.2 maintenance release that was successfully installed, follow these steps:
Step 1 Log in with the same user name as the owner of Prime Provisioning 6.8.2.
Step 2 Navigate to the
Step 3 If Prime Provisioning 6.8.2 is running, use the following command to stop the database, name server, and WatchDog on the machine on which it is running:
$ ./prime.sh stop
Step 4 Navigate to the directory
, where all the files replaced by the Prime Provisioning 6.8.2 maintenance release were stored.
Step 5 Use the following command to run the
patch script to uninstall:
a. When you run this script, you are asked to ensure that you have followed the equivalent of
b. To accept the default value for a prompt indicated in
, for example,
. To terminate the installer at any time, press
c. You are asked if you would like to roll back the patch. Answer yes or no as prompted.
d. At the end of the uninstall, you receive a message that the patch rollback is complete.
Note You can only restart Prime Provisioning if you restore a copy of the backed up repository from the version of the patch used prior to the Prime Provisioning 6.8.2 upgrade. Database schema cannot be rolled back once it is upgraded with upgrade tool.
New Features and Enhancements in Prime Provisioning 6.8.2
This section describes features and enhancements added or modified in Prime Provisioning 6.8.2.
Note Cisco Prime Provisioning 6.8.2 is only compatible with PCM August 2017 release. Make sure you upgrade to latest Prime suite components before upgrading and integrating the current version of Prime Provisioning.
Note • Prime Provisioning can be used as a standalone product or as a part of Prime Carrier Management August 2017. When installed as part of the suite, you can launch Prime Provisioning from the Prime Central portal. For more information about Prime Central, see the documentation for Cisco Prime Central.
Cisco Prime for IP Next Generation Networks (IP NGN) has been renamed as Cisco Prime for Evolved Programmable Networks (EPN). Please keep this in mind when viewing the suite and application documentation for the upcoming Cisco Prime Carrier Management release.
Items specific to Prime Provisioning 6.8.2 include the new and changed information as documented in the following sections:
This section summarizes the general feature that were added in Prime Provisioning 6.8.2.
Script Enhancements to Retain DCPL Values with Configured Values
During Prime Provisioning upgrade, to retain the Dynamic Component Properties Library (DCPL) property values without a reset, use the following CLI commands:
./prime.sh initdb.sh noreset
The values are retained or updated in the Prime Provisioning repository based on the following criteria.
1. When the initdb.sh script is run without any argument, Prime Provisioning reads the DCPL properties from vpnsc.properties and updates them in the Prime Provisioning repository.
2. When the initdb.sh script is run with noreset argument, Prime Provisioning retains the DCPL values which are already configured.
3. When the initdb.sh script is run with some irrelevant argument other than the noreset argument, Prime Provisioning will display an error message; “The only supported argument for initdb.sh is noreset.”
Supporting Manual Allocation of IPv6 Address from IPv6 Address Pool
From this release, you can enter an IPv6 address manually in the IP Address Scheme window of Cisco Prime Provisioning (CPP) while creating an MPLS service request. The IPv6 address entered must be available in the IPv6 address pools. If the IPv6 address belongs to a valid IPv6 block, then the IPv6 address is blocked as allocated and is updated in the respective IPv6 pool. The IPv6 address pool is then split as valid IPv6 address blocks or pools.
While entering the IPv6 address, ensure that you remember the following conditions:
1. The subnet mask that you enter should be same as that of the IPv6 pool mask.
2. The IPv6 address mask of the Provider Edge (PE) interface and the Customer Edge (CE) interface must be under the same subnet mask as that of the IPv6 address pool.
Once the allocation is successful, you can view the valid IPv6 address pools with Allocated status in the Resource Pools window of CPP.
To remove the MPLS service request, you need to release the IPv6 address back to the available pool. The pools that are split as blocks are combined again into a single pool. For this, you can either decommission the service or perform force delete of the IPv6 allocated block or pool.
Extending VLAN-ID Range to Support BVI Interfaces with Values Range
Prime Provisioning 6.8.2 release allows you to create MPLS SR with VLAN-ID that ranges between 1-65535 for L3VPN/MPLS services on ASR9K series devices, only when the EVC Service is enabled.
Note This functionality supports only PE devices of IOS-XR type.
When you enable the EVC Service checkbox in the MPLS Service Request Editor page, the VLAN-ID value is automatically updated/changed to support VLAN-ID ranges of 1-65535.
It is recommended to enter the VLAN-ID ranges within the specified range otherwise, an exemption occurs in the following instances:
On clicking Next, an invalid VLAN-ID error message is displayed when the value entered is greater than 65535.
If the selected device is IOS and the given VLAN-ID value is more than 4094 an error message is displayed.
Note Enabling EVC service on L3VPN creates BVI virtual interfaces to allow routing through BVI interfaces. BVI interfaces can be configured in the range of 1-65535. This is because Prime Provisioning does not have an option to provide BVI interface and thus uses the VLAN- ID value as BVI interface value. The extended value of 1-65535 specified in the VLAN-ID range field allows you to create BVI interface with BVI interface number range 1-65535.
Supporting EVPN-VPWS Attributes through a Customization XML File
From this release, EVPN-VPWS configurations are supported by importing a EVPN-VPWS customization.xar file as part of Prime Provisioning policies and service requests to manage various Ethernet Virtual Circuit services.
Before you Begin
To view or edit the EVPN-VPWS attributes in the Policy Editor window or the EVC Service Request Editor window, make sure that you have completed the following prerequisite.
1. Import the EVPNVPWSCustomization.xar file under $PRIMEP_HOME/packages/std, which is already copied as part of Prime Provisioning product (PP6.8.2 or greater). The customization XML uses merge mode as “Combine”. For more information about how to Import customization files, see Importing and Exporting Customizations
section in the Cisco Prime Provisioning 6.8 User Guide.
Note The EVPN-VPWS attributes are visible in the Policy Editor or the EVC Service Request Editor window only when you import the EVPNVPWSCustomization.xar file.
2. Make sure that the supported platform includes ASR9K with IOS-XR version 6.0 or later.
Enter or Modify EVPN-VPWS Attributes
To enter the EVPN-VPWS Attributes:
1. Create an EVC VPLS policy and import the “EVPNVPWSCustomization.xml”. Below is a configuration sample:
interface GigabitEthernet0/1/0/13.315 l2transport
encapsulation dot1q 315
xconnect group ISC
neighbor evpn evi 4341 target 64123 source 64222
2. In the Policy Editor window, in the Source ac-id field, enter the range between 1 and 16777215.
3. In the Remote ac-id field, enter the range between 1 and 16777215.
4. Click Finish to save the EVC Policy.
Note You can also create an SR (VPWS) using this policy with XR devices and enter the values for the attributes.
Supporting EVPN-VPLS Attributes through a Customization XML File
From this release, EVPN-VPLS configurations are supported by importing a EVPN-VPLS customization.xar file as part of Prime Provisioning policies and service requests to manage various Ethernet Virtual Circuit services.
Before you Begin
To view or edit the EVPN-VPLS attributes in the Policy Editor window or the EVC Service Request Editor window, make sure that you have completed the following prerequisite.
1. Import the EVPNVPLSCustomization.xar file under $PRIMEP_HOME/packages/std, which is already copied as part of Prime Provisioning product (PP6.8.2 or greater). The customization XML uses merge mode as “Combine”. For more information about how to Import customization files, see Importing and Exporting Customizations
section in the Cisco Prime Provisioning 6.8 User Guide.
Note The EVPN-VPLS attributes are visible in the Policy Editor or the EVC Service Request Editor window only when you import the EVPNVPLSCustomization.xar file.
2. Make sure that the supported platform includes ASR9K with IOS-XR version 6.0 or later.
3. Before configuring the EVPN-VPLS, configure BGP with new EVPN Address family as in the sample configuration below:
router bgp 64
bgp router-id 220.127.116.11
address-family l2vpn evpn
address-family l2vpn evpn
Enable or Modify EVPN-VPLS Attributes
To enter the EVPN-VPLS Attributes:
1. Create an EVC VPLS policy and import the “EVPNVPLSCustomization.xml”. Below is a configuration sample:
You can search for specific bugs or search for a range by product name. This tool enables you to query for keywords, severity, range, or version.
Use the following search criteria to locate bugs for Prime Provisioning 6.8.2:
Product category: Cloud and Systems Management > Routing and Switching Management > Fulfillment Products.
Product: Cisco Prime Provisioning (6.3 to 6.8.2).
The results display bug ID and title, found-in version, fixed-in version, and status. The bug ID is a hyperlink to detailed information for the bug ID’s product, component, severity, first found-in, and release notes. The results could be displayed in a feature matrix or spreadsheet.
All product documents are accessible except for images, graphics and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact firstname.lastname@example.org
Obtaining Documentation and Submitting a Service Request
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks
. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.