Guest

Cisco Prime Provisioning

Cisco Prime Provisioning Release Notes, 6.5

  • Viewing Options

  • PDF (354.9 KB)
  • Feedback

Table Of Contents

Cisco Prime Provisioning 6.5 Release Notes

Contents

Introduction

Installing Prime Provisioning 6.5

New Features and Enhancements in Prime Provisioning 6.5

General New Features

L2VPN/EVC/TDM-CEM/ATM New Features

Customizing EVC and MPLS Policies

Pseudowire Headend Interface

MPLS VPN New Features

L2VPN/EVC/TDM-CEM/ATM New Features

MPLS Transport Profile New Features

Impact on Prime Provisioning due to Multi-Instance of Prime Network

Commission and Decommission Notification from Prime Central

Device Commission Notification

Device Decommission Notification

Logs

API New Features

Deprecated and Removed Features

Prime Provisioning 6.5 Resolved and Open Bugs

Finding Known Problems in Prime Provisioning 6.5

Related Documentation

Accessibility Features in Prime Provisioning

Obtaining Documentation and Submitting a Service Request


Cisco Prime Provisioning 6.5 Release Notes


December 3, 2013

All documentation, including this Cisco Prime Provisioning 6.5 Release Notes document and any or all parts of the Cisco Prime Provisioning 6.5 documentation set, might be upgraded over time. Therefore, we recommend you access the Prime Provisioning 6.5 documentation set online at:

http://www.cisco.com/go/provisioning

You can also navigate to this documentation set by clicking Help on the Home Page of the Prime Provisioning 6.5 product.

The information in this release notes provides an overview of this release and helps you understand it at a high level. After reading the Cisco Prime Provisioning 6.5 Documentation Overview, please read this release note prior to reading any other documentation for Prime Provisioning 6.5.

URLs for base information about Prime Provisioning 6.5, a product overview, and suggested reading order of these documents is given in Related Documentation.


Note When searching for the product in the Bug Tool kit, enter the name "IP Solution Center". The product may not appear under the name "Prime Provisioning".


Contents

This document includes the following sections:

Contents

Introduction

Installing Prime Provisioning 6.5

New Features and Enhancements in Prime Provisioning 6.5

Deprecated and Removed Features

Prime Provisioning 6.5 Resolved and Open Bugs

Finding Known Problems in Prime Provisioning 6.5

Related Documentation

Accessibility Features in Prime Provisioning

Obtaining Documentation and Submitting a Service Request

Introduction

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 2013 suite.

Installing Prime Provisioning 6.5

When purchasing Prime Provisioning you will be prompted to select either delivery by

eDelivery, in which case you will receive an email with a download link, or

physical DVD media

If the version is not the latest, you are advised to upgrade. The latest Prime Provisioning 6.x version can be ordered for download by eDelivery (or DVD shipment) free of charge, provided that you have a Software and Services (SAS) contract. The minor upgrade can be ordered through the Product Upgrade Tool (PUT):
http://tools.cisco.com/gct/Upgrade/jsp/productUpgrade.jsp

Additionally, you are strongly advised to apply the latest available service patch. Prime Provisioning patches are available at http://software.cisco.com/download/navigator.html?mdfid=284127465&flowid=37682

For information about the installation process, see the Cisco Prime Provisioning 6.5 Installation Guide.

New Features and Enhancements in Prime Provisioning 6.5

This section describes features and enhancements added or modified in Prime Provisioning 6.5.

For system recommendations, refer to the Cisco Prime Provisioning 6.5 Installation Guide , and for device and platform support, refer to Cisco Prime Provisioning Supported Devices. It includes the network devices and related software supported with Prime Provisioning 6.5. We recommend that you thoroughly review this list before even planning your installation, to be sure you have all the hardware and software needed for a successful installation.

Prime Provisioning 6.5 is based on Cisco Prime Provisioning 6.4 and 6.4.1.

Prime Provisioning 6.5 includes problems fixed since Cisco Prime Provisioning 6.4. See Prime Provisioning 6.5 Resolved and Open Bugs.


Note Cisco Prime Provisioning 6.5 is only compatible with Cisco Prime Central 1.2. Make sure you upgrade Cisco Prime Central to version 1.2 before upgrading and integrating the current version of Prime Provisioning.



NotePrime Provisioning can be used as a standalone product or as a part of Prime Carrier Management August 2013. 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.5 include the new and changed information as documented in the following sections:

Features introduced in Prime Provisioning 6.4.1

General New Features

L2VPN/EVC/TDM-CEM/ATM New Features

Customizing EVC and MPLS Policies

Pseudowire Headend Interface

MPLS VPN New Features

Features introduced in Prime Provisioning 6.5

L2VPN/EVC/TDM-CEM/ATM New Features

MPLS Transport Profile New Features

Impact on Prime Provisioning due to Multi-Instance of Prime Network

Commission and Decommission Notification from Prime Central

General New Features

All the new features introduced in this release are explained in the Cisco Prime Provisioning 6.5 User Guide.

L2VPN/EVC/TDM-CEM/ATM New Features

This section summarizes features that were added to enhance the EVC pseudowire services in Prime Provisioning 6.4.1.

Setting the MTU Size in an EVC Pseudowire Service

Prime Provisioning allows you to set the maximum transmission unit (MTU) for an EVC pseudowire service. This MTU indicates which MTU must be configured identically at both ends of the pseudowire for the pseudowire to work. The MTU attribute can be set during the EVC policy creation. If it is set to editable, it can be edited further during service request creation as well.

To set the MTU size using the Prime Provisioning GUI:

1. Navigate to Service Design > Policy Manager > Create > Policy Type: EVC.

2. In the Service Option section, enter the maximum transmission unit in the MTU: field.

3. Make the required changes and save the EVC policy.


When you look at the configlet generated for this service, Prime Provisioning first configures the MTU under the interface and then under xconnect. If an MTU value is not specified, the default MTU values that are set on the device are used. This ensures that the port has an MTU at least as large as any service that it is carrying.

The MTU includes VLAN headers transported over the pseudowire. It does not include the size of the Ethernet header. While the specified MTU value can be configured on IOS devices, an interface MTU is configured in case it is configured on IOS-XR devices. The MTU interface is automatically determined by Prime Provisioning based on the size of the Ethernet header and the number of VLAN tags that are pushed or popped. The formula used to compute the interface MTU is as follows:

interface_mtu = pw_mtu + 14 + 4 x tags popped - 4 x tags pushed. 

For example, if you set the MTU size to 1500, and you have an IOS-XR device on one side of the pseudowire where you match 2 tags and pop 1 tag, then the interface MTU provisioned on the IOS-XR device is 1518 (which is 1500 + 14 + 4 x 1).

This feature is supported through the GUI and the NBI.


Note For more information on NBI, see Cisco Prime Provisioning 6.5 API Programmer Reference.


Provisioning a Pseudowire with U-PE Role Based Devices

While creating EVC-Ethernet services, you can provision a pseudowire on U-PE role based devices.

This enables a network architecture that has ethernet access domains, but allows for MPLS enabled switches within those domains. It is assumed that one VLAN will be set up to carry all the MPLS traffic in that domain. This enables end-to-end MPLS based services without having to allocate service provider VLANs, and allows MPLS enabled access to be inserted within existing ethernet access rings with non-MPLS enabled devices. In earlier Prime Provisioning releases, you only could configure MPLS services on provider devices with the N-PE role. However, starting in Prime Provisioning 6.4.1, Prime Provisioning checks whether the Loopback interface giving the LDP ID of the device is defined in the PE device inventory. If the LDP Loopback ID is defined, the device can be used as an endpoint for a MPLS service.

While creating Access Domain and Interface Access Domain, a new Role column displays the role of the listed PE devices when they are selected. You can also separate out devices based on their role type by using the Show PEs with Role filter option.

This support for U-PE and PE-AGG devices is extended to EVC Service Request creation and Multi segment Pseudowire functionality as well.

When you are creating an EVC service request, you can provision all the MPLS enabled devices of N-PE, U-PE and PE-AGG role types.

This feature is supported through the GUI and the NBI.

Template Support for MPLS-Enabled Nodes:
Prime Provisioning provides template support for N-PE role-based policies when a MPLS node is enabled in a direct connected link. Similarly, when a MPLS node is enabled in layer 2 links, template support is provided for U-PE or PE-AGG devices. But when a device is not enabled with an MPLS node, then no template is attached to the devices.

Support for Multi-Segment Pseudowire:
In multi-segment pseudowire, a filter is created during tunnel creation that displays all the MPLS-enabled devices. This filter allows you to populate all the MPLS-enabled devices such as U-PE with Loopback or N-PE with Loopback.

Configuring Speed and Duplex for Devices Added in Direct Connect Links

With Prime Provisioning, you can now configure the speed and duplex attributes for the EVC UNI enabled on both N-PE and U-PE role based devices added in Direct Connected Links. In addition to setting these attributes for links with L2 access, you can also set the speed and duplex attributes for Direct Connected links.

To set these attributes on devices added in Direct Connected Links:

1. Enable DCPL properties as follows:

Select Administration > Hosts.

Select an appropriate Host name and click Config.

From the Properties folder, select Provisioning > Service > fsm-UNI_DirectConnect > SpeedDuplex.

Set the property value to True. By default, this DCPL property is set to False.

2. Select a device in a Direct Connected Link.

3. Click Edit (Link Attributes).


The Link Speed and Link Duplex attributes can be set in the UNI Information section of the displayed page. The attributes are optional. The values for Link Speed are None, 10, 100, 1000, and Auto. The values for the Link Duplex attribute are None, Full, Half, and Auto.

This feature is supported through the GUI and the NBI.

VPLS Support on CPT Devices

When you create a service request for a EVC-VPLS policy in Prime Provisioning, the N-PE Pseudowire on SVI attribute is enabled and greyed out by default. Even though the attribute N-PE Pseudowire on SVI is irrelevant to CPT and ASR903 platforms, this feature helps generate proper CLIs for CPT and ASR903 devices without any user intervention.

Additional Attributes to Define Pseudowire Classes:

Using Prime Provisioning, you can now provision an EVC service with the following new pseudowire class attributes. These attributes are optional and are supported through both GUI and NBI.

Control Word: This attribute generates the cli `control-word' under the pw-class.

Sequencing: Specifies the direction in which sequencing of data packets in the pseudo wire is enabled. The values are:

BOTH: Configures sequencing on receive and transmit.

RECEIVE: Configures sequencing on receive.

TRANSMIT: Configures sequencing on transmit

Sequencing Resync: Specifies the resync value and the threshold. For example, for a resync value of 200, if the sequence type is Transmit, then the CLI generated under the pw-class for this attribute is "sequencing transmit resync 200 resync threshold". The range for the sequencing resync is from 5 to 65535.

Tunnel type - Specifies the type of the tunnel. The values are None, TE, and TP.

For steps on how to create a pseudowire class and specify these attributes, see Creating a Pseudowire Class.

Customizing EVC and MPLS Policies

With this version of Prime Provisioning, you can now embed customized command line interface (CLI) templates into EVC and MPLS policies. You can also extend policies by adding attributes that you define directly in the policy screen. This new feature simplifies the process of executing many Prime Provisioning tasks such as Additional Attributes and Template and Data File Manager.

Pseudowire Headend Interface

Prime Provisioning enables you to configure an L3 VPN attachment circuit with a Pseudowire access. The Pseudowire Headend feature on the ASR9000 facilitates this configuration without terminating the Pseudowire on an Ethernet interface, or having to allocate bridge domain for this purpose. This enables the creation of an end-to-end MPLS network where access is provided by a small switch that does not support many L3VPN instances. You configure a pseudowire on that which terminates on the ASR9000, where the pseudowire is directly connected to L3VPN.

To use this feature, you need both an L3 VPN policy and an EVC policy.


Step 1 Navigate to the Policy Editor page.

Step 2 In the PE Interface details section, check the Create virtual interface only check box. This displays the Configure Pseudowire Headend check box.

Step 3 Check the Configure Pseudowire Headend check box to enable the pseudowire headend feature for the PE interface.

Step 4 Make other required changes and save the policy.
Note that the Configure Pseudowire Headend check box is hidden until you check the Create virtual interface only check box. When you use this policy to create a service request, Prime Provisioning disables the PE Interface column in the Service Request Editor. When this service is deployed, Prime Provisioning creates a pseudowire-ether interface configured in the device.

Step 5 Create an EVC policy:

Core type- PSUEDOWIRE


Note The "Configure Pseudowire Headend' attribute must be enabled in the EVC policy in order to deploy Service with Pseudowire headend interface.


For end to end MPLS, which is the typical case, enable CE directly connected to N-PE.

Ensure that the Configure Bridge Domain check box is disabled.


To create services, follow these steps:


Step 1 Navigate to Operate > Service Request Manager.

Step 2 The Service Request Manager window appears.

Step 3 Click Create.
The Service Request Editor window appears.

Step 4 From the policy picker, choose the L3 policy that you created in steps 1-4.
The L3 VPN Service Request editor window appears. This window enables you to specify options for the service request, as well as configure links.

Step 5 Create an EVC service request using the EVC policy created in step 5 above.

Step 6 Set the pseudowire core connectivity attributes.

Step 7 Choose the pw-ether interface as the UNI interface.

Step 8 Set up links to the N-PE.

Step 9 When you have set the attributes in the EVC Service Request Editor window, click the Save button to save the settings and create the EVC service request.


You can now deploy the MPLS service. The interface will be available during EVC Service creation.

MPLS VPN New Features

This section summarizes new MPLS VPN features that are available in Prime Provisioning 6.5.

Duplicating U-PE Values at the PE

This enhancement is for cases where the customer facing interface is on an Ethernet Access switch provisioned using 'service instance'.

When configuring an access circuit with Ethernet access in Prime Provisioning 6.4, you were required to enter match criteria at the U-PE, VLAN rewrites at the U-PE, match criteria at the N-PE, and then execute further rewrites. With Prime Provisioning 6.5, you no longer have to enter these values repeatedly since the values matched at the N-PE can be determined by what is matched and rewritten at the U-PE.

Due to a change in the provisioning logic, the service provider VLAN pops on the uplink of an Ethernet switch. This is taken into account when determining the configuration of the switch. For example, if the rewrite required at the U-PE is to replace the customer VLAN with the provider VLAN, then this is achieved by popping the customer VLAN at the ingress on the customer interface, and pushing the service provider VLAN at egress on the uplink port.

Updating Device Interface Table Automatically

Prime Provisioning automatically updates the latest pseudowire headend interfaces in the Device Interface table as soon as the service request is saved. This means that the interfaces can be associated immediately with the service configuration before it is deployed.

In earlier Prime Provisioning releases, the created virtual interfaces were updated in the Device Interface table only after a successful deployment of the services that were associated with and after a Config Collect was performed. Since this list is updated automatically, you no longer have to manually perform a Collect Configuration for the pw-ether interfaces to be added to the Device Interface list.

This feature is supported through both the GUI and the NBI.

Configure Router Static and BFD Commands

With Prime Provisioning, you can enable BFD properties for PE-CE and PE-no-CE policies during Service Request creation. The BFD required attribute is enabled only when the Next Hop option is set to USE_NEXT_HOP_IPADDR or OUTGOING_INTF_NAME and NEXT_HOP_IPADDR. When the BFD required attribute is enabled, the following fields are displayed:

BFD Minimum interval

BFD Multiplier

These attributes are applicable to IOS and IOS-XR devices. During service provisioning, Prime Provisioning ensures that the configlets are generated only for IOS-XR devices.

BFD configlets are generated only if you provide a value for the "Advertised Routes for CE" attribute. Without this value, configlets are not generated, even if the BFD check box is enabled and values for BFD Minimum interval and Multiplier are given. In the generated configlet, the BFD command is generated along with the route command and it is appended with advertised routes for CE. The new attributes that appear in the configlet are as follows:

BFD Required

BFD Minimum Interval

BFD Multiplier

This feature is applicable to IPV4 and IPV6 devices and is supported only through the GUI.

L2VPN/EVC/TDM-CEM/ATM New Features

This section summarizes features that were added to enhance the EVC pseudowire services in Prime Provisioning 6.5.

Support for H-VPLS

Enhancements have been made to support multi-segment pseudowire for H-VPLS type of services under EVC. In earlier Prime Provisioning releases, only multi-segment pseudowires of type flat VPLS were supported. This feature is supported both through the GUI and the NBI.

MPLS Transport Profile New Features

This section summarizes the new MPLS-TP features that were added in Prime Provisioning 6.5.

MPLS-TP discovery from multiple instances of Prime Network is supported both in Standalone mode and in Suite mode. When installed in Suite mode, Prime Provisioning supports MPLS-TP discovery from multi-instances of Prime Network registered with Prime Central.

Prime Provisioning is 'paired' with the Prime Network instance(s) by setting the gateway details of the Prime Network(s) in the Prime Provisioning DCPL properties Inventory Import. Multiple gateways can be configured by separating the values with a comma. The order in which the Prime Network instances are configured has an impact on the MPLS-TP discovery process. The instance mentioned first in the DCPL has the highest priority, whereas the instance mentioned last has the lowest priority. The UserName and Password must be the same for all the instances of Prime Network.

When the MPLS-TP discovery process runs, Prime Provisioning checks if the chosen device(s) are present in the Prime Network instances. If the device chosen for MPLS-TP discovery is present in multiple Prime Network instances, MPLS-TP discovery is performed based on the Prime Network instance priority. MPLS-TP information is collected from the highest priority, whereas the TP enabled links alone are collected from all the Prime Network instances.

If the device chosen for MPLS-TP discovery is not present in the highest priority Prime Network, Prime Provisioning checks the next priority Prime Network instance 'paired' in the DCPL to discover the MPLS-TP information.

If the device chosen for MPLS-TP discovery is not present in any of the Prime Network instance, then this error message is logged, "MPLS-TP Discovery for device "DeviceName" failed. Device not found in any of the gateways."

If the device chosen for MPLS-TP discovery has any directly connected neighbors and is available in the Prime Provisioning inventory, MPLS-TP discovery is performed for the neighbors from the same Prime Network instance.

Impact on Prime Provisioning due to Multi-Instance of Prime Network

With the introduction of multi-instance Prime Network, Prime Provisioning functionality has been enhanced to support the following:

Integration with multiple instances of Prime Network in Suite mode and Standalone mode

Update of the configuration options

Import of the Prime Network certificate to Prime Provisioning trust store with a new script

Integration of multiple instances of Prime Provisioning with Prime Central is not supported. However, since Prime Provisioning interacts with Prime Network for inventory import functionality, the latest domain manager integrated files have to be copied to Prime Provisioning. Cross Launch from multiple instance of Prime Network integrated with Prime Central is supported by Prime Provisioning.

You can perform the following tasks in Prime Provisioning:

Import devices

Perform MPLS-TP discovery from multiple instances of Prime Network

To use HTTPS in Standalone mode, do the following:

ConfigurePrime Network properties in DCPL

Copy and import certificates from Prime Network


Note You can perform the steps above by running the new configurePN.sh script.


A device might be present in one or more instances of a Prime Network. To import a device, Prime Provisioning checks all the instances of Prime Network as there is no provision to specify one Prime Network from the Prime Provisioning. In this release, you can prioritize the Prime Network instances based on the configuration of the user.

A central user or User ID configured in Prime Central must be able to access all the instances of Prime Network that are integrated with Prime Central.

Commission and Decommission Notification from Prime Central

When Prime Provisioning is installed either in suite mode or upgraded to suite mode, it subscribes to Prime Central Device Commission/Decommission Notifications by default. Once subscribed, Prime Central forwards the device commission/decommission notifications received from the other Domain Managers to Prime Provisioning.

Device Commission Notification

The source of the notification might be any domain manager integrated with Prime Central. Prime Provisioning cannot identify the source of the Device Notification since that information is not passed on by Prime Central. Whenever a device is added in Prime Central, Prime Provisioning assumes that the device is added in the Prime Network.

When it receives a device commission/creation notification from Prime Central, it invokes the inventory import. A task is created for importing the device from Prime Network which can be viewed using Task Logs. Prime Provisioning provides the information received through the notification as an input to the inventory import functionality. The inventory import functionality interfaces with Prime Network to get the device details.

Device Decommission Notification

Prime Provisioning does not handle the decommission notification, but rather logs the delete notification message.

Logs

All the commission and decommission notifications received during creation and deletion of a device can be viewed using the PCNotification button. You can also view Logs from the console in the following directory: PRIMEP_HOME/tmp/pcnotification log file.

API New Features

All Application Programming Interface (API) features are explained in detail in the Cisco Prime Provisioning 6.5 API Programmer Guide and the accompanying Cisco Prime Provisioning 6.5 API Programmer Reference.

New features added in Prime Provisioning are generally available via both the GUI and APIs. See the respective sections in this document for a description of new features under each service.

Deprecated and Removed Features

The ATM MCPT timer has been deprecated.

Discovery of devices using CDP has been removed as of Prime Provisioning 6.4. Please use Prime Network for device existence discovery.

The MPLS Diagnostics Expert (MDE) has been deprecated as of Prime Provisioning 6.4. The feature was removed in Prime Provisioning 6.5. For service troubleshooting and diagnostics, please use Prime Network.

The Device Tools: Ping operation has been removed as of Prime Provisioning 6.4. Please use Prime Network.

Support for the Solaris operating system is deprecated from Prime Provisioning 6.4. From Prime Provisioning 6.5, only RHEL will be supported.

The Device Tools: IPSLA operation has been removed as of Prime Provisioning 6.4. Provisioning of IPSLA probes or similar can be done using templates or other customization.

Support for CatOS is being deprecated from Prime Provisioning 6.4. CatOS has reached end-of-life, and has been replaced by IOS. From Prime Provisioning 6.5 there will be no support for CatOS.

L2VPN and VPLS service types are being deprecated. Note that it is still possible to provision L2VPN and VPLS services using the EVC service type. The EVC service type should be used for all Layer 2 provisioning. Current users of VPLS and L2VPN service types can continue to do so.

The Reports feature has been deactivated and will be removed in a subsequent release. If needed, it can be reactivated using DCPL properties.

Prime Provisioning 6.5 Resolved and Open Bugs

There is one open bug for Prime Provisioning 6.5.

CSCuh73229: LAN Rewrites: Inner VLAN ID field is not visible when empty on modification.

Finding Known Problems in Prime Provisioning 6.5

To find known problems in Prime Provisioning 6.5, use the following URL:

http://tools.cisco.com/Support/Bug Tool Kit

You must log into Cisco.com.

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.5:

Product category: Cloud and Systems Management

Product: Cisco IP Solution Center or Cisco Prime Fulfillment

Software version: 6.5 (For a list of bugs open against all releases, choose ANY.)

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.


Note When searching for the product in the Bug Tool kit, enter the name "IP Solution Center". The product may not appear under the name "Prime Provisioning".


Related Documentation

The entire documentation set for Prime Provisioning, can be accessed at:

http://www.cisco.com/en/US/products/ps12199/tsd_products_support_series_home.html

An overview of the Cisco Prime Provisioning product is available at:

http://www.cisco.com/go/provisioning

The following documents comprise the Prime Provisioning 6.5 documentation set:

General Documentation (in suggested reading order)

Cisco Prime Provisioning 6.5 Documentation Overview

Cisco Prime Provisioning 6.5 Release Notes

Cisco Prime Provisioning 6.5 Installation Guide

Cisco Prime Provisioning 6.5 Supported Devices

Cisco Prime Provisioning 6.5 User Guide

Cisco Prime Provisioning 6.5 Administration Guide

Cisco Prime Provisioning 6.5 Open Source

API Documentation

Cisco Prime Provisioning 6.5 API Programmer Guide

Cisco Prime Provisioning 6.5 API Programmer Reference


Note All documentation might be upgraded over time. All upgraded documentation will be available at the same URLs specified in this document.


Other Cisco Prime Product Documentation

If you are deploying Prime Provisioning as part of the Prime Carrier Management suite, then see also the documentation for the other suite components:

Cisco Prime Central

Cisco Prime Network

Cisco Prime Optical

Cisco Prime Performance Manager

Accessibility Features in Prime Provisioning

For a list of accessibility features in Prime Provisioning, visit Cisco's Voluntary Product Accessibility Template (VPAT) website, or contact accessibility@cisco.com.

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 accessibility@cisco.com.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.