Release Notes for Cisco Prime Fulfillment 6.1.2
Available Languages
Table Of Contents
Release Notes for Cisco Prime Fulfillment 6.1.2
New Features and Enhancements in Cisco Prime Fulfillment 6.1.2
Common Infrastructure New Features
Simplified GUI Device Creation/Edit Process
Replace IBM (iLOG) CPLEX Solver
Dual-Homed Ring with ASR9000 and 7600 N-PEs
Support for Ring Discovery on ASR9000 Devices
Ring Discovery to Support Access Ring Originating from Non-Adjacent PE-AGG Devices
Automated NPC Creation with Aggregation and Access Rings
Device Import from Prime Network
Adding Additional Information to Services
ECHO Mode per Service Request (Simulated Deploy)
Resource Pool for Second N-PE in Dual-Homed Ring
1:1, 1:2, 2:1, and 2:2 VLAN Translation for all devices (U-PE/PE-AGG)
EVC Check Box Default Setting is Configurable by DCPL Property
Auto-Select EVC Check box for a Service Instance Ring
AutoPick Bridge Domain for Secondary N-PE Attribute
Locally Significant VLAN ID Pool—Service Instance Based EVC Provisioning
UNI device ID (Unique ID for EVC Link)—E-OAM
Create Interface Access Domain and EVC Outer VLAN Pool on Ring Save
Split Horizon Policy Attribute
VLAN Translation in EVC Service Request Extended for UPE/PE-AGG Role with Switchport Syntax
L2VPN Frame Relay Over MPLS Supports IOS XR Devices
Adding PE-CE Links to Management VPN for IOS XR
Traffic Engineering Management New Features
Prime Fulfillment 6.1.2 Patch Installation
Using the Upgrade Tool for Schema Upgrade
Issue with Importing Template Data Using the importExportTemplateDB.sh Script
Prime Fulfillment 6.1.2 Resolved and Open Caveats
Finding Known Problems in Cisco Prime Fulfillment 6.1.2
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Prime Fulfillment 6.1.2
March 15, 2012OL-26407-01
Cisco Prime Fulfillment 6.1.2 is a maintenance release to be added to Cisco Prime Fulfillment 6.1, 6.1.1, and all associated point patches (excluding 6.1.1.8 and 6.1.1.12). See the beginning of "New Features and Enhancements in Cisco Prime Fulfillment 6.1.2" section for details on supported releases.
All documentation, including this Release Notes for Cisco Prime Fulfillment 6.1.2 document and any or all parts of the Prime Fulfillment 6.1 or 6.2 documentation sets, might be upgraded over time. Therefore, we recommend that you access the Prime Fulfillment 6.1 and 6.2 documentation sets at:
http://www. cisco.com/go/fulfillment.
You can also navigate to this documentation set by clicking Help on the Home Page of the Prime Fulfillment 6.1.2 product. The "Related Documentation" section gives the URL for the most current version of each manual to be used with Cisco Prime Fulfillment 6.1.2.
The information in this Release Notes for Cisco Prime Fulfillment 6.1.2 document gives you an overview of this release and helps you understand what has changed since Prime Fulfillment 6.1.1. Please read this document prior to reading any other manuals or documents for Cisco Prime Fulfillment 6.1.2.
Contents
The information in this document is organized into the following sections:
•
New Features and Enhancements in Cisco Prime Fulfillment 6.1.2
•
•
•
Introduction
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.
Cisco Prime Fulfillment 6.1.2 has new functionality added and changed since Prime Fulfillment 6.1.1 (see the "New Features and Enhancements in Cisco Prime Fulfillment 6.1.2" section) and fixes to problems (see the "Prime Fulfillment 6.1.2 Resolved and Open Caveats" section).
The system recommendations for Prime Fulfillment 6.1.2 (see the "System Recommendations" section) are based on those for Prime Fulfillment 6.2 (with some restrictions, as noted). The new devices and platforms supported in addition to those supported in Prime Fulfillment 6.1.1 are referenced in the "System Recommendations" section.
Steps for installing Prime Fulfillment 6.1.2 are found in the "Installation Notes" section, and other important information is found in the "Finding Known Problems in Cisco Prime Fulfillment 6.1.2" section. For problems that were found and might still exist in Prime Fulfillment 6.1.2, see the URL in the "Prime Fulfillment 6.1.2 Resolved and Open Caveats" section.
URLs for base information about Prime Fulfillment 6.1.2 and an overview and suggested reading order of these documents is given in the Cisco Prime Fulfillment Getting Started and Documentation Guide 6.1.
The Prime Fulfillment 6.1.2 documentation includes the Prime Fulfillment 6.1 document set and the updated information for Prime Fulfillment 6.1.2 found in this Release Notes for Cisco Prime Fulfillment 6.1.2. The entire documentation set is listed in the "Related Documentation" section.
Many new features appearing in Prime Fulfillment 6.1.2 are documented in the Prime Fulfillment 6.2 documentation set. Where applicable, links point to the relevant locations in the Prime Fulfillment 6.2 documentation set for information on these features (rather than duplicating the information in this release note for Prime Fulfillment 6.1.2).
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.1.2 Release Notes.
March 15, 2012
Added Cisco IP Solution Center as bug search criteria in Product.
System Recommendations
The system recommendations and requirements are listed in the spreadsheet at the following location:
http://www.cisco.com/en/US/products/ps12199/products_device_support_tables_list.html
It includes the network devices and related software supported with Prime Fulfillment.
We recommend that you thoroughly review that list before 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.1.2
Cisco Prime Fulfillment 6.1.2 is based on Prime Fulfillment 6.1 with the addition of new and changed information that was introduced in the following Prime Fulfillment releases: 6.0.1.16, 6.1.1, 6.1.1.1, 6.1.1.2, 6.1.1.4, 6.1.1.5, 6.1.1.6, 6.1.1.7, 6.1.1.9, 6.1.1.10, and 6.1.1.11. In addition, several features have been backported from the Prime Fulfillment 6.2 release.
See Release Notes for Cisco Prime Fulfillment 6.1.1 for more information on the Prime Fulfillment 6.1.1 release.
Cisco Prime Fulfillment 6.1.2 includes problems fixed since Prime Fulfillment 6.1.1. See Prime Fulfillment 6.1.2 Resolved and Open Caveats.
Where applicable, links are provided to the relevant locations in the Prime Fulfillment 6.2 documentation set for features backported from that release.
Cisco Prime Fulfillment 6.1.2 includes the new and changed information as documented in the following sections:
•
•
Common Infrastructure New Features
This section includes new features for common components added in Prime Fulfillment 6.1.2.
Simplified GUI Device Creation/Edit Process
Following options are made available from the GUI:
•
•
•
These features are summarized in the following section.
For more documentation on these features, see the Cisco Prime Fulfillment User Guide 6.2.
Role Assignment
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.
Provider/Customer
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 NPCs has to be created and then click on the NPC button. This would auto-populate the NPCs 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.
Replace IBM (iLOG) CPLEX Solver
In Prime Fulfillment 6.1.2, the IBM (iLOG) CPLEX Solver is replaced with the CBC Solver. This update was needed due to the licensing agreement for CPLEX expiring. This change will not significantly impact current behavior, though it may generate slightly different results.
Dual-Homed Ring with ASR9000 and 7600 N-PEs
Dual-homed circuits support both ASR9000 and 7600 N-PE devices, where the endpoints are a combination of the 7600 and ASR9000 N-PE at each end (IOS/IOS XR based devices).
Support for Ring Discovery on ASR9000 Devices
Ring discovery support relies on the use of REP segments to identify each node in the ring. The ASR9000 device does not support REP. So when a ring discovery task is triggered on a topology where there is an ASR9000 series of devices, ring discovery in Prime Fulfillment 6.1.2 has been extended to support rings that are not configured with REP
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Ring Discovery to Support Access Ring Originating from Non-Adjacent PE-AGG Devices
The ring discovery task in Prime Fulfillment 6.1.2 has been enhanced to support the discovery task when it has been triggered on rings originating from non-adjacent PE-AGG devices.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Automated NPC Creation with Aggregation and Access Rings
In the Prime Fulfillment 6.1.2 release when creating NPC for a ring, the device/ring values were auto populated for an access ring. For a case where there is both aggregation and access ring, only the access ring information is auto populated. The aggregation ring has to be manually selected. This manual process was time consuming and error prone for the operator. This functionality is now automated in case of the scenario where both aggregation and access rings are present.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
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. 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.
2.
3.
4.
Rings which are not REP enabled or which do not follow the rules above can be created or edited manually.
Customizable Ring Names
All rings 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.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
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.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Device Import from Prime Network
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:
•
•
See the Cisco Prime Fulfillment User Guide 6.2 for 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.
Adding Additional Information to Services
The additional information feature allows a set of attributes (name/value pairs) to be defined in an XML file by the user. The file is subsequently associated with a policy. The additional information attributes define values to be associated with a service request. They define labels and appearance in the GUI. In the service request workflow, these values can be entered by the user. It is also possible to access these additional attribute values either from templates or from the xDE provisioning logic, to provide data values that will be configured as part of a service. Using additional attributes in combination with templates allows template attribute values to be prompted for in the policy and service request GUI, instead of having to create data files with these values.
A new appendix in the Cisco Prime Fulfillment User Guide 6.2 describes how to implement this feature.
ECHO Mode per Service Request (Simulated Deploy)
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 service requests can be saved to the draft state and completed at a later date.
Note
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
EVC/FlexUNI New Features
This section includes new features for EVC/FlexUNI added in Prime Fulfillment 6.1.2.
Resource Pool for Second N-PE in Dual-Homed Ring
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.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
1:1, 1:2, 2:1, and 2:2 VLAN Translation for all devices (U-PE/PE-AGG)
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 to the VLAN Translation attribute in the EVC policy and service request workflows.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
EVC Check Box Default Setting is Configurable by DCPL Property
A new DCPL property, Provisioning\ProvDrv\CheckFlexUniCheckBox, has been added to allow setting the EVC check box as checked/unchecked by default.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Auto-Select EVC Check box for a Service Instance Ring
Prime Fulfillment 6.1.1.2 defaulted the EVC check box to "unchecked" when provisioning an EVC service request. The user was then able to choose whether to switch this on via a DCPL Property:
Provisioning.ProvDrv.CheckFlexUNICheckBox=false
Prime Fulfillment now automatically recognizes if the ring was Service Instance or Switchport based, and auto-selects the EVC check box based on the ring type.
AutoPick Bridge Domain for Secondary N-PE Attribute
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.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Locally Significant VLAN ID Pool—Service Instance Based EVC Provisioning
A Resource Pool mechanism has been added for the Outer VLAN ID in EVC services. You can manually assign the Outer VLAN IDs for every EVC 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. The scope of this new resource pool is lifted up to the interface level. A new inventory for Interface based Access Domains has been added which is mapped with the Outer VLAN resource pool.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
UNI device ID (Unique ID for EVC Link)—E-OAM
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.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
VFI Name
A new attribute, AutoPick VFI Name, has been added in the EVC service request workflow. 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.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Create Interface Access Domain and EVC Outer VLAN Pool on Ring Save
The Prime Fulfillment 6.1.1.2 release contained the Interface access domain and EVC outer VLAN pool, which is required to be created for every new ring that is EVC/Service instance based. That process added two additional steps every time a new ring was discovered/created. Prime Fulfillment 6.1.2 now auto creates the Interface access domain and corresponding EVC outer VLAN pool while saving the ring that will be EVC/Service instance based.
Split Horizon Policy Attribute
Previous versions of Prime Fulfillment allowed the user to enable/disable split horizon at the service request level. If the value had to be changed, the service request had to be decommissioned and created again. Prime Fulfillment 6.1.2 provides the ability to set this at the policy level. The Split Horizon policy attribute is available in EVC Policy Editor under Service Options Window.
VLAN Translation in EVC Service Request Extended for UPE/PE-AGG Role with Switchport Syntax
Prime Fulfillment 6.1.1.2 was updated to support extended VLAN translation types (1:1, 1:2, 2:1, 2:2) in an EVC service request for devices in UPE/PE-AGG roles with switchport syntax. This support provides feature parity with switchport syntax on the 7600 device platform.
In Prime Fulfillment 6.1.2, support has been extended to support additional platforms, as follows:
•
•
•
L2VPN New Features
This section includes new features for L2VPN added in Prime Fulfillment 6.1.2.
L2VPN Frame Relay Over MPLS Supports IOS XR Devices
L2VPN Frame Relay over MPLS (FRoMLPS) services now support IOS XR devices.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
MPLS VPN New Features
This section includes new features for MPLS VPN added in Prime Fulfillment 6.1.2.
Adding PE-CE Links to Management VPN for IOS XR
The grey management VPN is a special VPN employed by the management subnet to manage the CEs in a Service Provider network. When a CE participates in a VPN, it is not accessible through conventional IP routing unless the CE is part of the management VPN. The management VPN connects to the managed CEs. From Prime Fulfillment 6.1.2 onwards, IOS XR devices are allowed to participate in a management VPN.
Prime Fulfillment 6.1.2 has been enhanced to support setting the option Join the Management VPN to true under the BGP Multipath Selection in the VRF and VPN Membership section of the Link Attributes workflow in Prime Fulfillment GUI and NBI.
For documentation on this feature, see the Cisco Prime Fulfillment User Guide 6.2.
Traffic Engineering Management New Features
This section includes new features for Traffic Engineering Management added in Prime Fulfillment 6.1.2.
TEM Support on Linux
Support for the Linux platform in TEM has been added in this release.
The whole of the TEM module including the RG component has been ported to RHEL Linux. This support is for RHEL 5.3 only.
API Enhancements
This section includes new features for API support added in Prime Fulfillment 6.1.2.
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.
All API features are explained in detail in the Cisco Prime Fulfillment API Programmer Guide 6.1 and the accompanying Cisco Prime Fulfillment API Programmer Reference 6.1. API features that were backported from Prime Fulfillment 6.2 are explained in the Cisco Prime Fulfillment API Programmer Guide 6.2 and the accompanying Cisco Prime Fulfillment API Programmer Reference 6.2.
Common Infrastructure:
•
•
•
EVC/FlexUNI:
•
•
•
•
•
•
•
•
•
•
MPLS VPN:
•
Installation Notes
This section contains the following information:
•
•
Version Supported
You can install Prime Fulfillment 6.1.2 from 6.1 / 6.1.1 and all associated point patches that have been merged to this release (excluding 6.1.1.8 and 6.1.1.12). There is a schema upgrade associated with moving from 6.1 (and 6.1.1, as it shares same schema as 6.1) / 6.1.1.2 / 6.1.1.4.
For any release prior to Prime Fulfillment 6.1, you must first upgrade to 6.1 before being able to progress with the procedure covered in the section, Prime Fulfillment 6.1.2 Patch Installation.
The procedure for upgrading from earlier releases is documented in the Cisco Prime Fulfillment Installation Guide 6.1.
Note
Prime Fulfillment 6.1.2 Patch Installation
To install the Prime Fulfillment 6.1.2 maintenance patch, follow these steps:
Note
Step 1
Step 2
Step 3
http://www.cisco.com/cisco/software/navigator.html?mdfid=283812776&flowid=29301
Note
Note
Step 4
Step 5
Step 6
gunzip -c prime_fulfillment_612_patch.tar.gz | tar xvf -
Step 7
$PRIMEF_HOME/prime.sh stopall
Note
Note
Step 8
./primepatchinstall
a.
b.
c.
Step 9
Step 10
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 other versions of Prime Fulfillment to Prime Fulfillment 6.1.2, perform the following steps:
Step 1
cp prime_fulfillment_612_upgradeTool.tar.gz /opt/
Step 2
gunzip -c prime_fulfillment_612_upgradeTool.tar.gz | tar xvf -
Step 3
unzip isc-upgrade.zip
Step 4
$PRIMEF_HOME/prime.sh upgradeISCSchema.sh $PRIMEF_HOME
Uninstall
To uninstall the Prime Fulfillment 6.1.2 maintenance release that was successfully installed, follow these steps:
Step 1
Step 2
Step 3
$ ./prime.sh stopall
Step 4
Step 5
$ ./primepatchrollback
a.
b.
c.
d.
Step 6
Step 7
Note
Important Notes
This section lists known caveats and issues to be aware of in this release. These are listed in the following categories:
•
Installation Notes
•
http://www.cisco.com/cisco/software/navigator.html?mdfid=283812776&flowid=29301
•
For information about the installation process, see the Cisco Prime Fulfillment Installation Guide 6.1.
Web Browser Support
1.
–
–
2.
–
–
To view fonts and colors correctly, the system display must be set to use a color quality of at least 32-bits.
3.
4.
5.
6.
7.
8.
Workaround: Try selecting individual subsections (broken, working, or to be deployed).
9.
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
Step 2
Refreshing the browser and logging out/in will not help.
Step 3
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.
Prime Fulfillment 6.1.2 Resolved and Open Caveats
Customer-found caveats that have been fixed in the Prime Fulfillment 6.1.2 release are indicated in the following table.
This includes Prime Fulfillment 6.0.1.16, 6.1.1, 6.1.1.1, 6.1.1.2, 6.1.1.4, 6.1.1.5, 6.1.1.6, 6.1.1.7, 6.1.1.9, 6.1.1.10, and 6.1.1.11.
The following open caveats apply to Prime Fulfillment 6.1.2:
Finding Known Problems in Cisco Prime Fulfillment 6.1.2
To find known problems in Cisco Prime Fulfillment 6.1.2, use the following URL:
http://tools.cisco.com/Support/BugToolKit
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 Fulfillment 6.1.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.
Related Documentation
The entire documentation set for Cisco Prime Fulfillment, can be accessed at:
http://www.cisco.com/en/US/products/ps12199/tsd_products_support_series_home.html
or at:
http://www. cisco.com/go/fulfillment
Tip
The following documents comprise the Cisco Prime Fulfillment 6.1.2 documentation set:
General Documentation (in suggested reading order)
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/roadmap/docguide.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/release/notes/relnotes.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1.1/release/notes/relnotes.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/installation/guide/installation.
html•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/user/guide/prime_fulfill.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.2/user/guide/prime_fulfill.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/theory/operations/guide/theory.html
•
•
API Documentation
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/developer/guide/apipg.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.1/developer/reference/xmlapi.zip
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.2/developer/guide/apipg.html
•
http://www.cisco.com/en/US/docs/net_mgmt/prime/fulfillment/6.2/developer/reference/xmlapi.zip
Note
Obtaining Documentation, Obtaining Support, and Security Guidelines
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.
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.
© 2012 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
Feedback