PDF(302.1 KB) View with Adobe Reader on a variety of devices
Updated:February 27, 2012
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.
All documentation, including this Release Notes for Cisco Prime Fulfillment 6.2 document and any or all parts of the Cisco Prime Fulfillment 6.2 documentation set, might be upgraded over time. Therefore, we recommend you access Cisco Prime Fulfillment 6.2 documentation set online at:
Cisco Prime Fulfillment is a management solution for network fulfillment and diagnostics that enables the automation and scaling of complex, policy-driven network provisioning tasks to produce consistent and reliable service deployments. Prime Fulfillment does this by planning, provisioning, and auditing services across core, aggregation, access, and consumer premises equipment devices.
Cisco Prime Fulfillment enables fast deployment and time-to-market of Multiprotocol Label Switching (MPLS) and Carrier Ethernet technologies. In addition, the Prime Fulfillment Traffic Engineering Management (TEM) module is Cisco's exclusive planning and provisioning tool for Cisco MPLS Traffic Engineering-enabled routers. For Diagnostics, use Cisco Prime Diagnostics, which is an automated, decision-tree analysis-based network management module that troubleshoots and diagnoses a wide range of problems in MPLS VPNs.
The Cisco Prime Fulfillment solution has management capabilities for MPLS VPN, L2VPN and Carrier Ethernet, MPLS Diagnostics and MPLS Traffic Engineering. These capabilities that comprise Cisco Prime Fulfillment can be used in a stand-alone or integrated manner.
New and Changed Information
The following table describes information that has been added or changed since the initial release of the Cisco Prime Fulfillment 6.2 Release Notes.
February 27, 2012
Added a bug CSCtx41572 - Silent installer throws error while unzip the upgrade tool.
The system recommendations and requirements are listed in Cisco Prime Fulfillment Supported Devices 6.2. It includes the network devices and related software supported with Cisco Prime Fulfillment 6.2. We recommend that you thoroughly review that list before even planning your installation, to be sure you have all the hardware and software needed for a successful installation. We also recommend that you review the section Important Notes, in this release note in order to be aware of any known system, installation, or other issues in the current release.
New Features and Enhancements in Cisco Prime Fulfillment 6.2
Cisco Prime Fulfillment 6.2 is based on Cisco Prime Fulfillment 6.1 with the addition of new and changed information that was introduced in Cisco Prime Fulfillment 6.1.1.
See Release Notes for Cisco Prime Fulfillment 6.1.1 for more information on the Prime Fulfillment 6.1.1 release. With the addition of new features, information from the previous release notes has been included in the Cisco Prime Fulfillment 6.2 documentation set.
Note With this release, Prime Fulfillment can be used as a standalone product or as part of the Cisco Prime for IP Next Generation Network (IP NGN) Suite. When installed as part of the suite, you can launch Prime Fulfillment from the Prime Central portal. For more information about Prime Central, see the documentation for Cisco Prime Central 1.0.
Items specific to Cisco Prime Fulfillment 6.2 include the new and changed information as documented in the following sections:
•Prime Fulfillment now supports the configuration of MPLS-TP tunnels on the Cisco 7600 platform running select IOS versions. Support for MPLS-TP Provisioning on the Carrier Packet Transport (CPT) platform with NGXP blade is also added. For more information about this feature, see http://www.cisco.com/en/US/products/ps11348/index.html.
•A dedicated MPLS-TP Discovery tool can be used to discover MPLS-TP topology and resources. MPLS-TP policies are used to aid the process of provisioning MPLS-TP services. These policies are used when creating MPLS-TP service requests, the mechanism used for configuring the network with MPLS-TP tunnels.
•Prime Fulfillment's MPLS-TP service uses resource pools to support the automatic allocation of MPLS-TP related resources and to track their usage.
•The EVC service has been extended to support RAN Backhaul management through Circuit Emulation CEM TDM services and pseudowire provisioning of ATM services. New workflows have been added to EVC policy and service request creation to support these services.
•RAN Backhaul leverages existing pseudowire class support in Prime Fulfillment. A new CEM class is added to create a logical grouping of CEM attributes, such as the dejitter buffer, payload size, and idle pattern. The CEM class allows configuring the same attribute values on every node where it is provisioned. CEM TDM services support SAToP PW3 and CESoPSPN PWE3 protocols.
•ATM services support ATM IMA VCC PWE3 and ATM IMA PVP PWE3 protocols. New template variables have been added to support CEM TDM and ATM services. The user can edit or deselect the templates associated at the service request level. The features are documented in the chapter "Managing RAN Backhaul Services" in the Cisco Prime Fulfillment User Guide 6.2.
Additional Information Attribute
User-defined attributes can now be added to MPLS, L2VPN, VPLS, and EVC policies and service requests. A new window, Additional Information, is added in the policy workflow, in which users can specify an XML definition file in order to add new attributes and fields into the policy and service requests based on the policy. Template variables can be mapped to the additional information attributes when you associate a template/template data file with the policy or service request. Additional information attributes are added to the XML document passed to the xDE provisioning engine, and can be accessed by any of the xDE procedures. A new appendix in the Cisco Prime Fulfillment User Guide 6.2 describes how to implement this feature.
The device creation and edit screens have been updated to allow role assignment. In previous releases, this required the creation of the physical device, followed by the creation of a second Provider or Customer device. This can now be done in one step. When creating the physical device, the user is provided with an option to assign the device as being either a Provider or Customer device. Based on this selection, the user can also specify the role, provider and customer assigned to this device.
You can enter the name of the provider or customer for whom the Interface Access Domain is created.
Actions - Quick Launch for Common Tasks
The deployment of common tasks has been simplified using new Actions menus. An action menu contains short-cuts for launching tasks such as Collect Configuration, Ring Discovery, MPLS-TP Discovery and MPLS Label Sync. Action menus are provided on the devices table within Inventory, the Inventory Manager and on the device creation and edit screens. Whenever an action is selected, the chosen task will be launched immediately. If a user wishes to schedule the task for a later date then they should use the Task Manager.
NPCs Automatically Populating From Ring
NPCs can be created directly from the Physical Ring page. The user can select the ring for which NPC's has to be created and then click on the NPC button. This would auto-populate the NPC's on the NPC screen.
Customer Creation from VPN Screen
Workflow for Customer Creation under Prime Fulfillment has been simplified which would allow the creation of customers even while creating Virtual Private Network (VPN) through Logical Inventory. You can perform this by accessing the Customer button in the Create New VPN window.
Prime Network Device Import
•Prime Fulfillment now supports the import of inventory from Prime Network. The inventory that can be imported are device credentials, software version, and SNMP details. All other physical and logical inventory is retrieved from the device using collect configuration.
•The two ways to import devices from Prime Network are:
–Bulk import using inventory manager
–Single device import during device creation
•See the Cisco Prime Fulfillment User Guide 6.2for steps to be followed to import Prime Network certificate into Prime Fulfillment Trust Store and also to set the Prime Network Gateway via DCPL properties.
Device Based Ring Discovery
A new ring discovery task is introduced to automate ring creation. This task is used to discover rings which have been configured using Resilient Ethernet Protocol (REP). Any rings which are discovered and which are not already known to Prime Fulfillment are added to inventory. Topology changes are identified and existing rings edited. Any ring which no longer exists on the network will be deleted from inventory. Ring discovery will always create closed rings as is required by Prime Fulfillment. Where the REP configuration does not specify a closed ring, the following actions are taken:
1. If an open REP ring is discovered which ends on two PE-AGG devices and are on the 4900 platform, the ring is closed using CDP to discover the missing link.
2. If an open REP ring is discovered but the end devices are not PE-AGGs 4900s, the ring is closed using a "virtual link". This is a link defined between the Loopback interfaces of the end devices.
Rings which are not REP enabled or which do not follow the rules above can be created or edited manually.
Two-Node Ring Support
Prime Fulfillment has the capability to create a 2-node ring. You can create a ring with minimum of two devices. Rings with two devices have the option to add more devices to the same ring through add or edit.
Customizable Ring Names
All ring can be given a user-specified name. When manually creating a ring, a text box is provided to enter the new ring name. Rings which are created via discovery are given an auto-generated name. Any existing ring can be renamed if required. Renaming a ring does not affect any services which use that ring.
Service Request Management
A new deployment option is added to simulate the deployment task without actually downloading configlets to the device and without setting the echo mode globally. This feature is supported by a new selection, Simulate Deploy, in the Deploy drop-down list of the Service Requests Manager window. To use this feature, you must first set the DCPL property Services\Common\allowSimulateDeploy to true.
Service Requests can now be saved in a draft state. The incomplete SRs can be saved to the draft state and completed at a later date.
A new template variable, EVC_UNI_DEVICE_ID, has been added to support the configuration of a unique MPID value on a per-link basis. This is used for CFM, IP SAL, and Ethernet OAM support.
EVC outer VLAN resource pools have been added to support autopicking of outer VLAN IDs in EVC services. To support this feature, support is also added to create interface-based access domains. The Interface Access Domain is a logical element that groups the physical ports of an N-PE device. Both of these logical structures are created through the Inventory > Logical Inventory tab in the Prime Fulfillment GUI. This feature is supported in EVC policy and service request workflows by the addition of the attribute AutoPick Outer VLAN, which is a check box that can be checked to have the outer VLAN ID be autopicked from a previously created pool of values.
Locally Significant VLAN ID Pool - Service Instance Based EVC Provisioning
A Resource Pool mechanism has been added for the Outer VLAN ID in FlexUNI EVC services. You can manually assign the Outer VLAN IDs for every FlexUNI service being provisioned. Mapping this to a Resource Pool will ease the operator's work on allocating and tracking different outer VLAN IDs for EVC services. This will be different from the legacy VLAN resource pool which is currently present in PRIME. The scope of this new resource pool is lifted upto interface level.
A new inventory for Interface based Access Domains has been added which is mapped with the Outer VLAN resource pool.
A new attribute, AutoPick VFI Name, has been added in the EVC service request. This allows users to provide a VFI name for EVC VPLS services. When this option is selected, the VFI name is automatically generated in the format: <VPN name>-<VC id>. When this option is not selected, the user can type in a VFI name of their own. The AutoPick VFI option can be enabled or disabled at the policy level.
•EVC outer VLAN resource pools have been added to support autopicking of outer VLAN IDs in EVC services. To support this feature, support is also added to create interface-based access domains. The Interface Access Domain is a logical element that groups the physical ports of an N-PE device. Both of these logical structures are created through the Inventory > Logical Inventory tab in the Prime Fulfillment GUI. This feature is supported in EVC policy and service request workflows by the addition of the attribute AutoPick Outer VLAN, which is a check box that can be checked to have the outer VLAN ID be autopicked from a previously created pool of values.
•Support is added for provisioning of VLAN translations on U-PE and PE-AGG devices even when EVC is enabled for an attachment circuit. All types of VLAN translations that were previously supported for EVC-disabled circuits are available for EVC-enabled circuits also. New choices have been added the VLAN Translation attribute in the EVC policy and service request workflows.
•A new DCPL property, Provisioning\ProvDrv\CheckFlexUniCheckBox, has been added to allow setting the EVC check box as checked/unchecked by default.
•A new attribute, AutoPick VFI Name, has been added in the EVC service request workflow to allow users to provide a VFI name for EVC VPLS services.
•A new attribute, AutoPick Bridge Domain/VLAN ID Secondary N-PE, has been added in the EVC service request workflow to autopick the bridge domain VLAN ID for the secondary N-PE in a dual-homed environment during service request creation.
•VPLS autodiscovery can be configured using EVC service requests in which the Core Connectivity Type is set as VPLS. VPLPS autodiscovery discovers neighbor PEs within the same VPLS domain and automatically detects when PEs are added or removed from the domain.
New features added in Prime Fulfillment 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. API support for TE Parallel Discovery has been added in this release.
The following API enhancements were added in Prime Fulfillment 6.2:
The path calculated for the MPLS-TP can be reviewed when you create MPLS-TP SR through the GUI. It can be recalculated by giving additional path constraints. Whereas, the path cannot be reviewed in API even though the existing path is used for tunnel and a SR is created. The tunnel can be manually defined through the API but this is not available in the GUI.
RAN Backhaul (IP RAN) Provisioning API
RAN Backhaul (IP RAN) Provisioning features include:
•Create/modify EVC-TDM-CEM Policy
•Create/modify EVC-TDM-CEM Service Request
•Create/modify EVC-ATM Policy
•Create/modify EVC-ATM Service Request
The above-mentioned new APIs allow you to create TDM-CEM and ATM Pseudowire services under EVC Service blade. CEM TDM feature supports provisioning of SAToP PW3 and CESoPSPN PWE3 services whereas ATM feature supports provisioning of ATM IMA VCC PWE3 and ATM IMA PVP PWE3 services.
•Create/modify CEM Class
CEM class is added to create a logical grouping of CEM attributes, such as dejitter buffer, payload size, and idle pattern. The CEM class allows configuring the same attribute values on every node where it is provisioned.
1. Prime Fulfillment GUI is supported by the following browsers:
–Firefox browser version 3.6.x.
–Internet Explorer (IE) version 8.0.
2. The recommended screen resolutions for both browser windows are:
–1024 x 768 pixels
–1280 x 1024
To view fonts and colors correctly, the system display must be set to use a color quality of at least 32-bits.
3. The Java Runtime Environment (JRE) version 6 (update 23) or later must be configured on the system running the browser.
4. The JAVA_HOME environment variable must be set to the JRE directory
5. The zoom functionality only works properly in the Prime Fulfillment GUI if the Firefox browser menu option View > Zoom > Zoom Text Only is unchecked.
6. You cannot have two Prime Fulfillment user sessions running on the same browser. This is caused by the session ID being used for both, which causes the screen context to be lost.
7. Adobe Flash player (version 10.3.183.7) and its plug-in have to be installed to support the web browser and allow viewing of the main bar and charts in the GUI.
8. If the Service Request Chart (pie chart) displays both very large and very small numbers, the pie section representing very small numbers is also very small and consequently difficult to access.
Workaround: Try selecting individual subsections (broken, working, or to be deployed).
9. For some operations that last a long time, the browser may issue a message like "Warning: Unresponsive script. A script on the page may be busy...." Two examples of this are when editing a customer device with many interfaces, and when editing user details, if there are many users.
Workaround: Increase the browser timeout value.
Issue with Importing Template Data Using the importExportTemplateDB.sh Script
Template data imported by using the importExportTemplateDB.sh script only shows up in the Template Manager GUI after the HTTPD or Prime Fulfillment processes are restarted.
One workaround is to manually create a template. Then all the previously imported templates and data files show up. With this workaround, there is no need to restart the HTTPD or Prime Fulfillment processes.
The steps to do this are as follows:
Step 1 Import the templates and data files.
Step 2 Check in Template Manager and verify if they show up.
Refreshing the browser and logging out/in will not help.
Step 3 Manually create a simple template in Template Manager.
As soon as you save and click on Close, the Template Manager window gets all the data, and all the previously imported templates, data files now appear.
Cisco Prime Fulfillment 6.2 Resolved and Open Caveats
The following caveats were resolved in Prime Fulfillment 6.2:
Static Advertise CE metric with value moved to failed audit (XRdevice).
PE to PE (Core) test returned " Test aborted due to unrecoverable errors".
TE Links tunnel audit threw session timeout error.
Prime did not generate encap command for bundle ethernet interface.
Browser did not close while opening an NPC and clicking "ok".
Decommission of MPLS SR having a UNI is used in multiple SRs. UNI description command is removed.
Negate did not generate for network command when L3VPN SR was decommissioned.
Error saving MPLS- PE-CE SR using NPC rings with multiple UPE devices.
VPLS-EWS removed vlan/interface/vfi from NPE when services exist on NPE.
GUI required Adobe Flash add-on.
EVC interfaces did not show correctly for policy with Dot1Qtunnel UNI encap.
The following open caveats apply to Prime Fulfillment 6.2:
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 Fulfillment 6.2:
•Product category: Network Management and Automation
•Product: Cisco IP Solution Center or Cisco Prime Fulfillment.
•Software version: 6.2 (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.
The entire documentation set for Cisco Prime Fulfillment, can be accessed at:
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:
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.
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. (1110R)
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.