 Feedback
|
Table Of Contents
Cisco Prime Provisioning 6.4.1 Release Notes
Installing Prime Provisioning 6.4.1
New Features and Enhancements in Prime Provisioning 6.4.1
Customizing EVC and MPLS Policies
L2VPN/EVC/TDM-CEM/ATM New Features
Prime Provisioning 6.4.1 Patch Installation
6.4.0.1/ 6.4.0.2 to 6.4.1 Standalone or Suite Mode Installation
6.2.1.50/ 6.3.0.3 to 6.4.1 Standalone or Suite Mode Installation
6.4 to 6.4.1 Standalone or Suite Mode Installation
6.4/ 6.4.0.1/ 6.4.0.2 to 6.4.1 Suite Mode Installation
Using the Upgrade Tool for Schema Upgrade
Prime Provisioning 6.4.1 Resolved Bugs
Prime Provisioning 6.4.1 Open Bugs
Finding Known Problems in Prime Provisioning 6.4.1
Accessibility Features in Prime Provisioning
Obtaining Documentation and Submitting a Service Request
Cisco Prime Provisioning 6.4.1 Release Notes
July 29, 2013OL-27133-02
Cisco Prime Provisioning 6.4.1 maintenance release introduces a new mechanism for customizing policies, that combines and simplifies the process of adding new attributes, and creating CLI templates related to a policy, as well as enhancements for EVC Pseudowire services and MPLS VPN services in Cisco Prime Provisioning. It is the first maintenance release based on Prime Provisioning 6.4.
You can install Cisco Prime Provisioning 6.4.1 on Cisco Prime Provisioning 6.4 or 6.4.0.1 or 6.4.0.2 based server. Schema upgrade is supported from 6.2.1.50/ 6.3.0.3/ 6.4 / 6.4.0.1 / 6.4.0.2 to 6.4.1.
See the New Features and Enhancements in Prime Provisioning 6.4.1 for a list of point patches whose enhancements and defect resolutions have been merged into 6.4.1.
All documentation, including this Cisco Prime Provisioning 6.4.1 Release Notes document and any or all parts of the Prime Provisioning 6.4 documentation set, might be upgraded over time. Therefore, we recommend that you access the Prime Provisioning documentation 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.4.1 product. The Related Documentation gives the URL for the most current version of each guide to be used with Cisco Prime Provisioning 6.4.1.
The information in this Cisco Prime Provisioning 6.4.1 Release Notes document gives you an overview of this release and helps you understand what has changed since Cisco Prime Provisioning 6.4. Please read this document prior to reading any other guides or documents for Cisco Prime Provisioning 6.4.1.
Contents
This document includes the following sections:
•
New Features and Enhancements in Prime Provisioning 6.4.1
•
•
•
•
•
Installing Prime Provisioning 6.4.1
Prime Provisioning patches are available at:
http://software.cisco.com/download/type.html?mdfid=284586808&flowid=37682
For information about the installation process, see the Installation Notes section.
Introduction
Cisco Prime Provisioning 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 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 Diagnostics, 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 IP-NGN Suite.
Cisco Prime Provisioning 6.4.1 has new functionality added and changed since Prime Provisioning 6.4 (see the "New Features and Enhancements in Prime Provisioning 6.4.1" section) and fixes to problems (see the "Prime Provisioning 6.4.1 Resolved Bugs" section).
The system recommendations for Prime Provisioning 6.4.1 (see the "System Recommendations" section) are based on those for Prime Provisioning 6.4 (with some restrictions, as noted). The new devices and platforms supported in addition to those supported in Prime Provisioning 6.4 are referenced in the "System Recommendations" section.
Steps for installing Prime Provisioning 6.4.1 are found in the "Installation Notes" section, and other important information is found in the "Finding Known Problems in Prime Provisioning 6.4.1" section. For problems that were found and might still exist in Prime Provisioning 6.4.1, see the URL in the Prime Provisioning 6.4.1 Resolved Bugs.
URLs for base information about Prime Provisioning 6.4.1 and an overview and suggested reading order of these documents is given in the Cisco Prime Provisioning 6.4 Documentation Overview.
The Prime Provisioning 6.4.1 documentation includes the Prime Provisioning 6.4 document set and the updated information for Prime Provisioning 6.4.1 found in this Cisco Prime Provisioning 6.4.1 Release Notes. The entire documentation set is listed in the "Related Documentation" section.
System Recommendations
The system recommendations and requirements are listed in Chapter 1, System Recommendations, of the Cisco Prime Provisioning 6.4 Installation Guide. For details on network devices and related software supported with Prime Provisioning 6.4.1, refer to Cisco Prime Provisioning Supported Devices.
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 Prime Provisioning 6.4.1
This section describes features and enhancements added or modified in Prime Provisioning 6.4.1.
For system recommendations, refer to the Cisco Prime Provisioning 6.4 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.4.1. 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. We also recommend that you review the section Installing Prime Provisioning 6.4.1, in this release note in order to be aware of changes to the installation or upgrade procedure.
Prime Provisioning 6.4.1 is based on Cisco Prime Provisioning 6.4.
Prime Provisioning 6.4.1 includes problems fixed since Cisco Prime Provisioning 6.4. See Prime Provisioning 6.4.1 Resolved Bugs.
Note
Items specific to Prime Provisioning 6.4.1 include the new and changed information as documented in the following sections:
•
•
Customizing EVC and MPLS Policies
In 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 the following Prime Provisioning tasks:
•
•
Adding New Attributes to a Policy
While creating EVC and MPLS policies, a new Create UI Group button on every page of the policy enables you to create any number of UI groups on any number of pages on the policy. For example, as shown in the figure below, you can create a new UI group called Security aspects using the Create UI Group button.
Figure 1 An EVC Policy with Four UI Groups.
The name (in this example, Security aspects) you provide for the UI Group appears as the title of the new section. Once you create a UI group, the Create button and the Settings icon is displayed in the title bar, enabling you to create attributes. You can further edit, delete and reorder attributes within the UI group. You can add attributes only to UI groups you create, and not to existing groups in the policy. Using the Create button, you can specify the type of attributes that you want to create. The types that you can specify are:
•
•
•
•
•
•
•
•
•
•
Using the name given to every attribute, you can refer to the value of that attribute from a CLI template. For example, if you create an attribute called cbr, using a CLI template, you can refer to this new attribute using the variable $cbr. Every attribute also has a display name and a description. While the display name is used as the label for the attribute in the Prime Provisioning UI, the description is displayed when you hover over the tool tip icon for that attribute.
Attributes can be marked Required or Optional. To verify whether optional values are provided, you can use #if ( $my_optional_attribute ) within a CLI template. Attributes marked Required are displayed on the policy and Service Request pages.
A new Create Global UI button allows you to specify global attributes which are identical across all links of a service request. These global attributes appear on the first page of the service request. Like other attributes, global attributes can also be set as editable or non-editable, and have default values assigned to them.
Creating Templates
You can now create and customize templates that consist of the CLIs that you want to deploy on devices. Templates can reference the data that you enter in UI groups. When you create a template, in a policy, you can specify:
•
•
•
•
•
•
•
•
•
Variable Completions for Specifying CLIs:Variable completions are now available while specifying CLIs in templates. This means that you can use Ctrl-Space for completion of variables that you want to enter. For example, when you type $ and then type Ctrl-Space, the list of all possible variables is displayed and you can select variables directly from this list without having to know them beforehand. Similarly if you type a prefix to a variable e.g. $SR, then a filtered list of all $SR variables is listed. Further typing while the variable list is visible will further narrow the available options. When only a single option is available, it is selected automatically.
The displayed list of variables consists of
•
•
•
•
•
•
•
•
•
•
•
•
•
Creating Rules for Templates
Every template can be associated with a set of rules that determine the type of devices on which the template can be deployed. This allows you to generate different CLIs for devices of different roles types and operating systems. Prime Provisioning deploys the template only when the criteria specified in these rules is fulfilled. When no rules are specified, the template is deployable on all devices.
You can create multiple rules for a given template. For example, you could have one rule for a template to be deployed on only IOS-XR devices of type N-PE; while another rule for the template to be deployed on IOS devices of type U-PE.
Importing and Exporting Customizations (in XML format)
You can export customizations in an XML format and save it using a text editor to create a backup of your customization. It is recommended that you create a backup of your customizations or copy the policy and modify the copy before you modify a policy with existing service requests (see Changing Customizations when a Policy is in Use), so that you can revert back to these customizations by merely importing the same XML document that you saved. To do this, an Import/Export button has been provided on the policy creation page. The customizations that you export are displayed in a new browser window from which you can copy the customizaitons onto a text editor for further use.
By exporting the customization data in an XML text format, you can:
•
•
Changing Customizations when a Policy is in Use
The new UI attributes that you define in policies can be edited even after service requests are defined based on those policies.
To introduce a new capability for only newly created services, it is recommended that you create a new policy with this capability. This can be done by copying an existing policy to create a new one and making the current policy inactive. You can also rename the policies that you copy so that operators can use the same name for the new policy. While creating new services requests, Prime Provisioning only lists the active policies so that you do not select the inactive policies used for existing service requests. This ensures that you do not face any errors while modifying in use policies.
Changes to the attributes in the policy will cause no change to the data in the associated service requests. The changes can only be noticed in the user interface and the way the service request is configured.
To create a backup of the previous version of a customization, use the Import/Export feature explained above. This enables you to revert back to the previously saved version after modifying a policy that has existing service requests.
Some types of changes that you make to a policy can result in undesired changes to a service and hence it's recommended that you review existing service requests before you make these changes to the policy. The types of changes that requires you to review existing service requests are:
•
When an attribute is removed from the policy page with its declaration existing still in the CLI template, an appropriate error with link "Has errors" is enabled in the "Provisioning CLI Customizations" page. On rolling over the mouse over the "Question mark" icon, the necessary details are shown. Although the removed attribute is no longer displayed and referenced from the provisioning logic and templates, it continues to exist in the service request.The saved value reappears only if you add an attribute with the same name. This behavior is to ensure that the removal of attributes is reversible step. When you remove attributes that continue to be referenced from the provisioning logic or from templates, the templates fail because they are referring to undefined attributes. Thus it is recommended that you first remove all references to the attributes, before you proceed with the removal of these attributes.•
This can be done by changing a string validation regular expression, restricting an integer range, and removing values for an enumeration. After you remove these values and then edit the service request, while retaining the invalid values, you will not be able to save the service request. You will need to either change the value of the attribute or cancel your edit. Thus it is recommended that you edit service requests and not use the invalid values before you change the policy.•
The attribute can not be modified and will be hidden from the service request page create using the policy with the non-editable attribute. Attribute values modified during service request creation, are not visible to the operated modifying services. To ensure that different service requests do not have different values for the same attribute, it is recommended that all service requests created with the policy contain the same default values before they are marked non-editable. Thus new service requests can only be created with the default values.Different changes that you make to existing service requests can have varied results. The results are:
•
•
•
•
After you add new attributes to a service, which translate to more lines of configuration, and re-deploy the service, managing the transition is easy since the template will be activated automatically.
However, if you remove template configurations and replacing them with new configurations, you need to ensure that you maintain the decommissioning sequence of the old features before you add the new features. Once the service is migrated, you must no longer use the old features. To do this, you can introduce an additional attribute that represents whether the service is migrated or not. This can be used as a condition with an `if' statement in the template to decide whether an old extension has to be decommissioned or not. For advanced help in migrating from template solutions to customizing policies, you can contact theh Advanced Services team.
Pseudowire Headend Interface
Using Prime Provisioning, you can now configure an L3 VPN attachment circuit, with a Pseudowire access. Using the Pseudowire Headend feature on the ASR9000, this can be achieved without terminating the Pseudowire on an Ethernet interface, or allocating bridge domain for this purpose. This enables the creation of an end to endMPLS network where access is provided by a small switch that does not support many L3VPN instances. On that switch you configure a pseudowire which terminates on the ASR9000. There the pseudowire is directly connected to L3VPN.
To prepare to use this feature you need both an L3 VPN policy and a EVC policy.
Step 1
Step 2
Step 3
Step 4
Note that the Configure Pseudowire Headend check box is hidden until you select 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
•
•
•
Then to create services, follow these steps:
Step 1
The Service Request Manager window appears.Step 2
The Service Request Editor window appears.Step 3
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 4
Step 5
Step 6
Step 7
Step 8
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
Using Prime Provisioning you can set the maximum transmission unit (MTU) for an EVC pseudowire service. This MTU indicates the MTU which must be configured identically at both ends of the pseudowire for the pseudowire to work. The MTU attribute can be set during EVC policy creation and if set to editable, it can further be edited during service request creation as well.
To set the MTU size using the Prime Provisioning GUI:
1.
2.
3.
When you look at the configlet generated for this service, you will notice that as a prerequisite Prime Provisioning configures the MTU first under the interface and then under the xconnect. If an MTU value is not specified, the default MTU values that are set on the device are used. This is to ensure that the port has an MTU at least as large as any service 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 of IOS-XR devices. The interface MTU 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,
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.
Provisioning a Pseudowire with U-PE Role Based Devices
While creating EVC-Ethernet services you can now 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. As a prerequisite it is assumed that one VLAN will be set up to carry all the MPLS traffic in that domain. This will then enable end-to-end MPLS based services without having to allocate service provider VLANs, but will allow MPLS enabled access to be inserted within existing ethernet access rings with non-MPLS enabled devices. In earlier Prime Provisioning releases, you could configure MPLS services on provider devices with only the N-PE role. However, starting in Prime Provisioning 6.4.1, Prime Provisioning checks whether in the PE device inventory the Loopback interface giving the LDP ID of the device is defined. If the LDP Loopback ID is defined, the device can be used as an endpoint for an MPLS service.
While creating Access Domain and Interface Access Domain, when you select devices as PEs, a new Role column displays the roles of the listed devices. 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, in addition to provisioning N-PE devices you can now provision MPLS enabled devices of role type U-PE and PE-AGG.
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 an MPLS node is enabled in a direct connected link. Similarly, template support is provided for U-PE or PE-AGG devices, when a MPLS node is enabled in layer 2 links. 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. It allows the picker in the filter 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
Using 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, starting in Prime Provisioning 6.4.1, 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.
–
–
–
–
2.
3.
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
In Prime Provisioning, when you create a service request for a EVC-VPLS policy, 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 CLI's 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.
•
•
–
–
–
•
•
For steps on how to create a pseudowire class and specify these attributes, see Creating a Pseudowire Class.
MPLS VPN New Features
This section summarizes features that were added to enhance MPLS VPN services in Prime Provisioning 6.4.1.
Duplicating U-PE Values at the PE
This enhancement is for cases where the customer facing interface is on an Ethernet Accesss switch provisioned using 'service instance'.
In Prime Provisioning 6.4 when configuring an access circuit with Ethernet access, 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. Since the values matched at the N-PE can be determined by what is matched and rewritten at the U-PE, it is now no longer required to enter these values repeatedly.
The provisioning logic has also been changed such that on the uplink of an Ethernet switch we always pop the service provider VLAN. 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 will automatically update 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 immediately associated 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 successful deployment of the services they were associated with and after a Config Collect was performed. But starting 6.4.1, 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
Using Prime Provisioning 6.4.1, 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 is generated only if you provide value for "Advertised Routes for CE" attribute. Without this value configlets will not be generated, even if 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:
–
–
–
This feature is applicable to IPV4 and IPV6 devices and is supported only through GUI.
Installation Notes
Prime Provisioning patches are available at:
http://software.cisco.com/download/type.html?mdfid=284586808&flowid=37682
This section contains the following information:
•
•
Version Supported
You can install Prime Provisioning 6.4.1 on Prime Provisioning 6.4 or 6.4.0.1 based server. Schema upgrade is supported from 6.2.1.50/ 6.3.0.3/ 6.4/ 6.4.0.1/ 6.4.0.2 to 6.4.1.
Prime Provisioning 6.4.1 is a maintenance release on the Prime Provisioning 6.4 release. Therefore, repository migration can only be performed from 6.4 or later versions. To migrate from earlier releases (prior to 6.4), you must first upgrade to Prime Provisioning 6.4 release. See "Prime Provisioning 6.4.1 Patch Installation" section.
The procedure for upgrading from earlier releases is documented in the Cisco Prime Provisioning 6.4 Installation Guide.
Caution
GRANT SELECT ON sys.dba_constraints TO <<PRIME PROVISIONING Oracle DB username>>
This is applicable only for the Customers who use Oracle Database with Prime Provisioning installation and not for those who use Sybase repository with Prime Provisioning installation.
Note
Prime Provisioning 6.4.1 Patch Installation
The following sections describes about the common steps for the scenarios included for Prime Provisioning 6.4.1 installation in standalone and suite mode:
•
•
•
The following section describes about the steps required for Suite Mode installation.
•
6.4.0.1/ 6.4.0.2 to 6.4.1 Standalone or Suite Mode Installation
To install Prime Provisioning 6.4.1 maintenance path in Standalone mode or Suite mode, follow these steps:
Note
Step 1
Step 2
http://software.cisco.com/download/type.html?mdfid=284586808&flowid=37682
Note
Note
Step 3
Step 4
Step 5
gunzip -c prime_provisioning_6_4_1_patch.tar.gz | tar xvf -
Step 6
$PRIMEP_HOME/prime.sh stopall
Note
Step 7
./primepatchinstall
You will be prompted with the following message "Enter a new path or press Enter for the default [<PRIMEP_OWNER_HOME_DIR>/primep-6.4.1]:".
Step 8
a.
b.
c.
Step 9
"Do you want to continue the installation in Standalone mode?"Enter yes to finish the installation in standalone mode. This completes the installation process and the installation stops immediately.
Step 10
Note
Step 11
Step 12
6.2.1.50/ 6.3.0.3 to 6.4.1 Standalone or Suite Mode Installation
To install Prime Provisioning 6.4.1 maintenance path in Standalone mode or Suite mode follow these steps:
Step 1
Step 2
Step 3
6.4 to 6.4.1 Standalone or Suite Mode Installation
To install Prime Provisioning 6.4.1 maintenance path in Standalone mode or Suite mode follow these steps:
Step 1
Step 2
Note
Step 3
Step 4
http://software.cisco.com/download/type.html?mdfid=284586808&flowid=37682
Note
Note
Step 5
Step 6
Step 7
gunzip -c prime_proviosioning_6_4_1_patch.tar.gz | tar xvf -
Step 8
$PRIMEP_HOME/prime.sh stopall
Note
Step 9
./primepatchinstall
You will be prompted with the following message "Enter a new path or press Enter for the default [<PRIMEP_OWNER_HOME_DIR>/primep-6.4.1]:".
Step 10
a.
b.
c.
Step 11
"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.
Step 12
Note
Step 13
Step 14
6.4/ 6.4.0.1/ 6.4.0.2 to 6.4.1 Suite Mode Installation
To continue installing the Prime Provisioning 6.4.1 maintenance patch in suite mode, follow these steps:
Step 1
"Please remove the already registered Prime Provisioning server from Prime Central i.e. From Prime Central Suite monitoring Portlet, remove Prime Provisioning."
Note
http://www.cisco.com/en/US/docs/net_mgmt/prime/central/1.0/user/guide/prime_central_10
_user_guide_suite_mgmt.html#wp1057447To terminate the patch installation in suite mode, enter no.
Step 2
Step 3
•
•
•
•
•
Note
Step 4
Step 5
Note
http://www.cisco.com/en/US/partner/docs/net_mgmt/prime/central/1.1/user/guide/prime_central_11_user_guide.html
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 Provisioning to Prime Provisioning 6.4.1, follow these steps:
Step 1
cp prime_provisioning_641_upgradeTool.tar.gz /opt/
Step 2
gunzip -c prime_provisioning_641_upgradeTool.tar.gz | tar xvf -
Step 3
unzip isc-upgrade.zip
Step 4
$ ./upgradeISCSchema.sh $PRIMEP_HOME
Step 5
Please enter ISC admin user name [admin]:Please enter admin password:Please enter admin password again:
Uninstall
To uninstall the Prime Provisioning 6.4.1 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
Prime Provisioning 6.4.1 Resolved Bugs
Customer-found bugs that have been fixed in the Prime Provisioning 6.4.1 release are indicated in the following table. This includes Prime Provisioning bugs from the Prime Provisioning 6.4.0.1 release.
Prime Provisioning 6.4.1 Open Bugs
The following open bugs apply to Prime Provisioning 6.4.1:
Finding Known Problems in Prime Provisioning 6.4.1
To find known problems in Prime Provisioning 6.4.1, 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.4.1:
•
•
•
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 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.4 documentation set:
General Documentation (in suggested reading order)
•
•
•
•
•
•
API Documentation
•
•
Note
Other Cisco Prime Product Documentation
See also the documentation for the following Cisco Prime products:
•
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.
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.
©1998-2013 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
