Readme File for Cisco Prime Network 4.1.0.0.1 Point Patch · manual rollback), run the upgrade.pl script with the –nobackup option, as follows: perl upgrade.pl –nobackup This

All contents are Copyright © 2014 Cisco Systems, Inc. All rights reserved. Page 1

Readme File for Cisco Prime Network 4.1.0.0.1

Point Patch

Revised: Aug 7thth, 2014

This document supports the release of the Prime Network 4.1.0.0.1, which is installed on

top of Cisco Prime Network 4.1. All changes described in this document apply only to

Cisco Prime Network 4.1.

Note: Please make sure to review this Point-Patch Test Report for the list of possible

issues/caveats – EDCS-1439191 (Cisco Internal Only)

Prerequisite: Prime Network 4.1

Table of Contents

1 Obtaining the Point Patch 2

2 Point Patch Contents 2

3 Explanation on Contents 2

4 Installing the Point Patch 3

5 Optional – Installing Prime Network Integration Layer patch post the install of PN 4.1 Point Patch 1 7

6 Optional - Prime Network Operations Report Patch Installation 8

7 Verifying the Prime Network Point Patch Installation 10

8 Verifying the Prime Network Integration Layer Patch Installation 12

9 Uninstalling the Prime Network Point Patch 13

10 Verifying the Prime Network Point Patch Uninstalling 16

11 Uninstalling the Integration Layer patch 17

12 Resolved Caveats – Cisco Prime Network 4.1.0.0.1 Point Patch. 18

13 Bug Resolutions That Require VNE Device Package 20

14 Obtaining Documentation, Support and Security Guidelines 20


1 Obtaining the Point Patch To obtain the Cisco Prime Network 4.1.0.0.1Point Patch installation, download it from

Cisco.com:

http://software.cisco.com/download/type.html?mdfid=285956832&flowid=60323

2 Point Patch Contents Cisco Prime Network 4.1.0.0.1 Point Patch contains the necessary files and scripts in

support of the following:

Prime Network Patch

Network Configuration Change management (NCCM) Patch

Resolved caveats, identified in Resolved Caveats – Cisco Prime Network Point Patch.

3 Explanation on Contents Beginning in Prime Network 4.0, the patch delivery process includes several changes that

combine the delivery of fixes and upgrades of multiple components into a single delivery

method. This patch includes the normal patch upgrade for Prime Network that has been

delivered in previous versions. However, the NCCM patches are now being included into

this patch process instead of being delivered and installed separately. With PN 4.0 comes

the introduction of an integration layer (Prime Network Integration Layer) that supports

the ability to have multiple Prime Network domains integrated with Prime Central. The

patch will automatically install the Prime Network Integration Layer patch if the Prime

Network Integration Layer base application exists. With the Cisco Prime Network 4.0

comes the introduction of a new Operations Report Tool. The updates associated with this

tool are also being included in this patch installation.

Note: Not all Point Patches contain updates for Prime Network Integration Layer and

Operations Report Tool.

http://software.cisco.com/download/type.html?mdfid=285956832&flowid=60323


4 Installing the Point Patch This procedure describes how to install the Cisco Prime Network 4.1.0.0.1Point Patch on

top of an existing Cisco Prime Network 4.1 installation.

Before You Begin

1. If you are using the LINUX RHCS solution:

Login to the Cisco Prime Network gateway as root user and move the services into

freeze mode, by running:

a) clusvcadm –Z <Prime Network service>

b) clusvcadm –Z <Oracle service>

For example:

clusvcadm –Z ana

clusvcadm –Z oracle_db

2. If you are using Geo HA solution:

a. Unzip the RH_ha.zip from the installation package.

b. Copy the folder RH_ha/perlForHA/PrimeNetwork to /var/adm/cisco/prime-

network/scripts/ha/util/perlForHA directory on all of the gateways of the

system.

c. Set the privilege and ownership of the copied "PrimeNetwork" folder and its

included subfolders and files to the values same as other folders and files in

/var/adm/cisco/prime-network/scripts/ha/util/.

d. Remove the perl folder if exists (owned by root) from /var/adm/cisco/prime-

network/scripts/ha/util on all of the gateways of the system (The SP/PP install

script will create the same perl folder, but this time the perl folder will be

owned by PN user)..

3. Make sure the Cisco Prime Network gateway and units are up and running before

installing the point patch (Except for Unit behind NAT, see next step).

4. If you are using Unit behind NAT please stop the Prime Network application and

remove the current crontab. Enter the following commands on each of the NAT units:

a) networkctl stop

b) crontab -r

5. Copy the Point Patch to a directory outside of the Cisco Prime Network home

directory (as user ‘root’).

Example:


cd /export/home

mkdir 4.1.0.0.1

6. Grant the directory Cisco Prime Network user permission.

Example:

chown <Prime Network-user>:ana 4.1.0.0.1

Notes

The installation process is configured to execute automatic backup of all the files

under the Cisco Prime Network home directory. Creating the backup zip file can take

up to one hour.

You can abort the installation if a backup of the database has not been performed.

You are prompted for a destination path for the backup file and to indicate the

required disk space requirements. This path location cannot be

$PRIME_NETWORK_HOME.

Grant Prime Network user permission to the Cisco Prime Network backup

directory.

The backup file name is appended with the UNIX time stamp of the gateway

machine.

The file format of the backup is PrimeNetworkBackUp_<unix_time>.tar.gz.

We recommend that you install Cisco Prime Network 4.1.0.0.1 Point Patch with the

default option: perl upgrade.pl.

To install the Point Patch without a backup (that is, without the option to rollback, or a

manual rollback), run the upgrade.pl script with the –nobackup option, as follows:

perl upgrade.pl –nobackup

This Point Patch might include database table changes. If you would like the option to

rollback to a previous Cisco Prime Network version, backup the database.

If your setup is installed with an embedded database, see the “Performing a Manual

Backup of an Embedded Database and Cisco Prime Network” section in the Cisco

Prime Network Administrator Guide, 4.1.

The Cisco Prime Network gateway and units restart automatically after the installation

has completed successfully.

Installation Procedure

1. Login to the Cisco Prime Network gateway as Prime Network user.

2. Navigate to the directory in which you placed the Point Patch. (See Before You Begin).

3. To extract the necessary JAR files and Perl scripts, for Prime Network and Operations

Report installation, go to the patch directory location created in Step 5 above and unzip

the file by entering the following command:

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-1/administrator/guide/CiscoPrimeNetwork41AdministratorGuide.html



Example:

cd /export/home/4.1.0.0.1

unzip Prime_Network4.1.0.0.1.zip –d ./Point-Patch

4. The zip file will contain 2 separate additional zip files. One contains the files

associated with installing the Prime Network patch (same name as original zip file)

and the other for installing patches related to the Operations Report Tool.

Note: Operations Report Tool zip file will exist only if there are updates available to

this Point Patch

1. Prime_Network4.1.0.0.1.zip

2. 4.1_Reports.zip

5. For installing the Prime Network patch, go to the newly created sub directory (ie.

Point-Patch) and unzip the Prime Network Patch zip file:

Example:

cd ./Point-Patch

unzip Prime_Network4.1.0.0.1.zip

6. Navigate to the Prime_Network_upgrade directory:

cd Prime_Network_upgrade

7. Enter one of the following commands, depending on whether or not you want to install

the Point Patch with the option to roll back:

To install the Point Patch and create a backup file, enter:

perl upgrade.pl

To install the Point Patch without creating a backup file, enter:

perl upgrade.pl -nobackup


8. If you are using a Unit behind NAT please restart the crontab, see Restarting Crontab

Jobs for NAT Units (Cisco Prime Network Installation Guide, 4.1)

9. During the patch installation, the console output will indicated that the NCCM patch is

being installed, “Upgrading NCCM”.

10. If you observe the following output from the install script “Upgrading Integration

Layer”, then the base Prime Network Integration Layer was previously installed and

the script is upgrading Prime Network Integration Layer patch. If the base Prime

Network Integration Layer is not installed, then no action is taken by the script. The

base Prime Network Integration Layer is required for Suite setups and optional for

Standalone setups (enables MTOSI and 3GPP web service implementations via WS-

SOAP NBI).

11. The script will provide a user prompt “Do you want to proceed (Yes/No)?” Answer

“Yes” to install the Prime Network Integration Layer patch. Answering “No”

continues the installation but does not install the Prime Network Integration Layer

patch.

12. Wait until the Cisco Prime Network gateway is up and running.

13. For installing the Operations Report Tool patch, refer to section Prime Network

Operations Report Tool Installation.

14. To complete the upgrade and ensure successful functioning of the network discovery tool,

run the following command to set the necessary file permissions for the Fping utility:

su root -c '$PRIME_NETWORK_HOME/local/scripts/setFpingPermissions.tcsh'

15. If you are using the LINUX RHCS solution:

Log into the Cisco Prime Network gateway as root user and move the services out of

freeze mode, by running:

clusvcadm –U <Prime Network service>

clusvcadm –U <Oracle service>

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-1/installation/guide/CiscoPrimeNetwork41InstallationGuide.pdf

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-1/installation/guide/CiscoPrimeNetwork41InstallationGuide.pdf


5 Optional – Installing Prime Network Integration

Layer patch post the install of PN 4.1 Point Patch

1 The upgrade script provides the user with the option of installing the Prime Network

Integration Layer patch. To install the Prime Network Integration Layer patch post the

installation of PN 4.1 Point Patch 1, please follow the install procedure specified in the PN

4.1 install guide (Base Install) and then follow these steps for the patch installation:

Note: Not all Point Patches contain updates for Prime Network Integration Layer

Post the Prime Network Integration Layer install; please perform the following steps as the

Prime Network User:

$PRIMEHOME/local/scripts/il-watch-dog.sh disable

itgctl stop

cd ~/.setup/independent/integrationlayer/patch

./patchIntegrationLayer.sh

$PRIMEHOME/local/scripts/il-watch-dog.sh enable

itgctl start


6 Optional - Prime Network Operations Report

Patch Installation Prerequisite - The Reporting tool is an optional installation requirement with Prime

Network 4.1. Please refer to “Installing Prime Network Operations Report” in the Prime

Network 4.1 Installation Guide for details. This reporting tool and associated Infobright

database must be installed on the gateway and unit(s) prior to installing any required

patches for this tool.

Note: Not all Point Patches contain updates for Prime Network Operations Report

If you don’t have Prime Network Operations Report installed or if there is no 4.1

Reports zip file in the point patch, skip to the next section.

You can confirm if the tool is already installed (as a Cisco Prime Network user) by either

checking for the existence of a ~/pentaho directory under $PRIME_NETWORK_HOME,

launching the Operations report tool using https://<gw-ip>:8445/prime-network-

reports/Login or checking to see if the server is listening to the default port: (ie. netstat -

a | grep LISTEN | grep 8445)

Perform the following steps as a Cisco Prime Network user to install the Operations

Report patch:

1. Navigate to the directory in which you placed the Point Patch. (See Before You

Begin.)

2. To extract the necessary JAR files and Perl scripts, for Operations Report installation,

unzip the file by entering the following command:

unzip 4.1_Reports.zip

3. As the PN installation user, run the following commands to start the patch installation:

cd ./4.1_Reports

chmod +x install-reports-patch.sh (makes script executable)

./install-reports-patch.sh (initiates the patch installation)

4. Check the log file for any errors. Both progress and status are printed to the console

and the following log file:

$PRIME_NETWORK_HOME/install-reports.log

5. Once the patch is successfully installed, a restart and refreshing the solution repository

is required. Please follow the instructions detailed below for the Post installation steps.

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-1/installation/guide/CiscoPrimeNetwork41InstallationGuide.html

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-1/installation/guide/CiscoPrimeNetwork41InstallationGuide.html


Post installation steps for Operations Report Patch Install

1. Stop the server using the Pentaho master script

~/pentaho/ctlscript.sh stop

2. Ensure all Pentaho process are killed. Run the command:

ps –ef | grep pentaho

If any process is listed, stop them using kill command:

kill -9 <pid>

3. Start the server using the Pentaho master script:

~/pentaho/ctlscript.sh start

4. Update the solution repository by logging into the Operations Report server

(https://<gw-ip>:8445/prime-network-reports/Login) and performing the following

actions:

> Tools > Refresh > Repository Cache

> Tools > Refresh > Reporting Metadata


7 Verifying the Prime Network Point Patch

Installation This section describes how to verify that Cisco Prime Network 4.1.0.0.1 Point Patchhas

been installed successfully, as explained in Section 4, Installing the Point Patch..

This procedure uses the script ~/Main/scripts/checkPatchInstallation.pl to confirm that

the Point Patch has been installed correctly.

Note: Execute the commands from the gateway.

Verification Procedure

1. Enter the following command to determine the version of the Point Patch installed:

checkPatchInstallation.pl -p

The gateway responds with the Point Patch information, such as:

Current patch (in 127.0.0.1): Prime_Network4.1.0.0.1_PP.jar: patch.jar

2. Enter the following command to determine whether all components of the Point Patch

installed successfully:

checkPatchInstallation.pl Prime_Network4.1.0.0.1_PP.jar

If the installation was successful, information similar to the following is displayed:

Patch Prime_Network4.1.0.0.1_PP.jar correctly installed in the

gateway (127.0.0.1)

Patch Prime_Network4.1.0.0.1_PP.jar correctly installed in the golden

source registry (0.0.0.0)

Patch Prime_Network4.1.0.0.1_PP.jar correctly installed in the unit

<unit IP>

Patch Prime_Network4.1.0.0.1_PP.jar correctly found at the start of

0.out log file

Patch Prime_Network4.1.0.0.1_PP.jar correctly found as the first

reference on file

/export/home/pn40/Main/webstart/agentregistryviewer.jnlp


reference on file /export/home/pn40/Main/webstart/bosmanage.jnlp


reference on file /export/home/pn40/Main/webstart/dcdebugger.jnlp


reference on file /export/home/pn40/Main/webstart/eventvision.jnlp


reference on file /export/home/pn40/Main/webstart/networkvision.jnlp


reference on file

/export/home/pn40/Main/webstart/processdebugger.jnlp


reference on file /export/home/pn40/Main/webstart/regedit.jnlp



reference on file

/export/home/pn40/Main/webstart/sessiondebugger.jnlp


reference on file /export/home/pn40/Main/webstart/stresser.jnlp


reference on file /export/home/pn40/Main/webstart/workflowstudio.jnlp

Patch Prime_Network4.1.0.0.1_PP.jar's classes files are being called

from this patch on server 127.0.0.1

Patch Prime_Network4.1.0.0.1_PP.jar's xml files are being called from

this patch on server 127.0.0.1

Patch Prime_Network4.1.0.0.1_PP.jar's classes files are being called

from this patch on server <unit IP>

Patch Prime_Network4.1.0.0.1_PP.jar's xml files are being called from

this patch on server <unit IP>

---> Patch Prime_Network4.1.0.0.1_PP.jar correctly installed

If the installation was not successful, messages are displayed that indicate where

problems are located. The final line in the report is:

---> Patch Prime_Network4.1.0.0.1_PP.jar not correctly installed or

at least one warning displayed


8 Verifying the Prime Network Integration Layer

Patch Installation To verify that the Prime Network Integration Layer patch was installed successfully,

execute the following command:


cd $PRIMEHOME/install/scripts

./version.sh get

To check the logs for errors, go to:

cd $PRIMEHOME/patches/1.1.0.1/


9 Uninstalling the Prime Network Point Patch This procedure describes how to uninstall the Point Patch. Performing an uninstall will

completely remove the Point Patch from the system.

Note: you can uninstall the Point Patch only if it was installed with the backup option,

using the command: perl upgrade.pl –p.

Note: Rolling back the Prime Network Point Patch will also roll back any applied patches

related to other components such as Prime Network Integration Layer, Operation Reports

and CCM.

Rollback Procedure

1. Verify that the gateway and unit workstations can communicate via SSH.

2. Login to Prime Network Administration and disconnect Standby and NAT units from

the gateway using the Administration GUI.

3. Login to the Cisco Prime Network gateway as Prime Network user.

Stop Cisco Prime Network by entering the following commands:

networkctl stop

Note: The above step is only applicable for non-embedded databases. If using an

embedded database, the embdclt script will automatically stop the gateway and units.

4. If you are using GEO HA: On the Remote DB machine, stop the replication:

cd /var/adm/cisco/prime-network/scripts/ha/util/

perl primeha –stop

5. Restore the Cisco Prime Network database alone:

For an embedded database, see the “Restoring an Embedded Database and

Prime Network“ section in the Cisco Prime Network Administrator Guide, 4.1.

Make sure to use the instructions to “Restore Prime Network Embedded

Database Alone“ (i.e. use the ‘emdbctl --restore_db’ command).

For a non-embedded database setup, restore the backed-up database and start

the database services and the listener. The database table structure is changed

during the upgrade. In order for the system to function correctly after a rollback,

the old table structure must be recovered through a database backup.

6. Reinstall the units. This is required prior to running the rollback.pl script in the

subsequent steps.



7. Navigate to the Prime_Network_upgrade directory you created for installing the Point

Patch:

Example:

cd 4.1.0.0.1/Point-Patch/Prime_Network_upgrade

8. As the Cisco Prime Network user, enter the following command on the Cisco Prime

Network gateway only:

perl rollback.pl

Note: Running the rollback.pl script will also restore the Cisco and Non-Cisco Device

driver files associated with Device Package (DP) installations. Therefore, any VNE

device driver files associated with DP installations that occurred after the last backup

procedure will be overwritten. The rollback procedure removes and replaces the entire

contents of the Cisco Prime Network home directory which includes the

~/Main/drivers directory.

9. At the prompt "Are you sure you want to rollback the current Prime Network

installation?" enter yes.

- Writing log to /export/home/network-upgrade/PrimeNetwork_upgrade/rollback-

number.log

- Have you rolled back the database? (yes,no) [default yes]

- Have you reinstalled the units? (Y,N) [default Y]

- Are you sure you want to rollback the current Prime Network installation?

(yes,no)[default yes]

10. At the prompt "Please enter the full path to the backup archive file," enter the location

of the backup archive directory. The rollback.pl script does not delete the backup

archive.

- Please enter the full path to the backup archive file:

Example:

/export/home/4.1.0.0.1/PrimeNetworkBackup/PrimeNetworkBackUp_<unix_time

>.tar.gz

11. The scripts revert the gateway back to its earlier version:

- Removing content of /export/home/network40 [OK]

- Extracting backup archive under /export/home/network40 [OK]

- Removing Standby Units

[OK]

- Starting Prime Network on GW

+ Rollback completed successfully.

Please remember to do the following:

- Re-login as the Prime Network user for environment changes take place

check logs for further information.

- Rollback logs can be found at <logFile>


12. Run the “network-conf –rollback” command on the unit machines.

13. Run "networkctl start" on the unit machines.

14. If you are using GEO HA: From the RH_ha directory (extracted during the install

process of this PP) run the following command as root user:

perl setup_Prime_DR.pl

This will setup the replication between the local and remote sites and copy the db files

to the remote site.

This may be a lengthy process depending on the size of the database.

15. After the rollback to your original Cisco Prime Network 4.1 environment is complete,

reconfigure your user-defined crontabs.

16. For Prime Suite environments, you must run the DMIntegrator.sh script in order for

the Prime Network Version in the Suite Monitoring portlet to be reverted back

successfully.

$PRIME_NETWORK_HOME/prime_integrator/DMIntegrator.sh


10 Verifying the Prime Network Point Patch

Uninstalling This procedure allows you to verify that the Point Patch was uninstalled successfully.

Uninstalling Verification Procedure

1. On the Cisco Prime Network gateway, login as Prime Network user.

2. Navigate to the Main directory.

3. Enter the following command:

./runRegTool.sh -gs 127.0.0.1 get 0.0.0.0 site/mvm/services/bsm/patchjar

You should not see the Point Patch that was removed.


./runRegTool.sh -gs 127.0.0.1 get 127.0.0.1 site/mvm/services/bsm/patchjar


5. Enter the following command from the Cisco Prime Network gateway for all the units:

./runRegTool.sh -gs 127.0.0.1 get <unit ip> site/mvm/services/bsm/patchjar


6. To verify that the Prime_Network4.1.0.0.1_PP.jar file does not exist in any of the

JNLP files, enter the following command:

cat ~/Main/webstart/*.jnlp | grep Prime_Network4.1.0.0.1_PP.jar

The output should be empty.


find ~/Main/ -name Prime_Network4.1.0.0.1_PP.jar


8. Navigate to the logs directory (~/Main/logs).

9. Check the AVM 0 log file by entering the following command:

cat 0.out | grep Prime_Network4.1.0.0.1_PP.jar



10. Check the AVM 11 log file by entering the following command:

cat 11.out | grep Prime_Network4.1.0.0.1_PP.jar


11 Uninstalling the Integration Layer patch

To uninstall the Prime Network Integration Patch, perform the following steps:


1. As Prime Network application user log in to PN server and Disable Prime Network

Integration Layer.

$PRIMEHOME/local/scripts/il-watch-dog.sh disable

2. ESB directory will be backed up under patches directory

($PRIMEHOME/patches/<patch-id>/.backup/esb). Copy esb folder and replace

$PRIMEHOME/esb

mv $PRIMEHOME/esb_X $PRIMEHOME/esb_X_backup // Where X is the

instanceId, instanceId can be found by command "itgctl list"

# In case patch-id is 1.1.0.1

cd $PRIMEHOME/patches/1.1.0.1/.backup

cp -fr esb $PRIMEHOME/esb_X

3. Edit version file and change the patch number

vi $PRIMEHOME/install/files/.version

change PATCH=1.1.0.1 to PATCH=0.0.0.0

4. Enable Prime Network Integration Layer

$PRIMEHOME/local/scripts/il-watch-dog.sh enable


12 Resolved Caveats – Cisco Prime Network

4.1.0.0.1 Point Patch. The following caveats have been fixed in Cisco Prime Network 4.1.0.0.1 Point Patch.

Note: Please make sure to review this Point-Patch Test Report for the list of possible

issues/caveats – EDCS-1439191 (Cisco Internal Only)

Resolved Caveats - 4.1.0.0.1 Point Patch

Identifier Summary

CSCui63646 Command manager edit takes long time to saveIntegrate CCM patch with PN SP and PP

CSCui72300 Command manager edit fails when Implementation is changedIntegrate PN integration layer with PN during upgrade

CSCuo32623 Compliance audit job fails when using SCP protocolPN 4.1 build is not picking up NCCM installer zip

CSCuo26261 Deleting the commands in command manager leaves in-progress circleNot able to install PN4.1 May DP over PN4.1 PP1.

CSCun27884 Command Manager-Admin/configurator not able to see other user's jobsAssociation of alarms with VLAN interfaces is incorrect in GUI

CSCuo27878 Special character in configuration is failing Config Audit jobThe 'LSP down' alarms are not cleared at VNE initialization

CSCun79722 Compliance audit generates a wrong violation reportASR9K: Missing entries in the LLDP table

CSCun79708 Perform activation jobs in Parallel/Sequential orderAny kind of Notifications are not being sent.

CSCup21205 CCM - About and splash screen don't show CCM PP or SP versionFlapping Event application is creating proxy event for traps

CSCuo22457 Thousands of telnet archive registrations are created at once

CSCul46808 configurator commands should have urgent priority

CSCuo18874 device get stuck in discovery

CSCup26514 Technology change for Satellite Phy Inv not updated on Port Range change

CSCuo61487 Archiving non flagging events is freezing event processing

CSCun37125 PPM TCA traps can have very long descriptions

CSCun10969 650K message drops every 30 seconds

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCui63646

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCui72300

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuo32623


http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCun27884




http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCup21205


http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCul46808







Resolved Caveats - 4.1.0.0.1 Point Patch

Identifier Summary

CSCup99687 PN: Webclients are not working after upgrading from 4.1 to 4.1-PP1

CSCun84136 Command manager edit takes long time to save

CSCun84154 Command manager edit fails when Implementation is changed

CSCun92962 IE8 Blank Execution Parameter screen & loses selected list of devices

CSCun95386 Compliance Audit Page Renders wth "js" error sometimes

CSCun95760 Compliance audit job fails when using SCP protocol

CSCun95894 Deleting the commands in command manager leaves in-progress circle

CSCuo04951 Command Manager-Admin/configurator not able to see other user's jobs

CSCuo22448 Special character in configuration is failing Config Audit job

CSCuo34442 Compliance audit generates a wrong violation report

CSCuo48848 Event trigerred backup is failing with null pointer

CSCuo21651 Perform activation jobs in Parallel/Sequential order

CSCuj27901 CCM - About and splash screen don't show CCM PP or SP version

CSCup00076 Install remains on step "Starting Web Server" and does not continue

CSCua67398 JuneDP-Satellite status improper after the it's interface link made down

CSCup78313 Admin/configurator not able to see other user's jobs



13 Bug Resolutions That Require VNE Device Package The following bug resolutions are contained in this Prime Network Point-Patch. However,

to completely resolve the bug you must also install a VNE Device Package that contains

the associated VNE software fix. The following table describes these bugs and the VNE

Device Package that is required (along with the associated VNE bug). To obtain any

Prime Network patches, contact your Cisco representative.

Identifier Headline Resolved in Required Device Package Onwards (VNE Bug)

CSCun27884 Association of alarms with VLAN interfaces is incorrect in GUI

04.1(00)PP01 04.1(00X)DP1405.00.321

CSCup26514 Technology change for Satellite Phy Inv not updated on Port Range change

04.1(00)PP01 TBD

14 Obtaining Documentation, Support and Security

Guidelines For information on obtaining documentation, obtaining support, providing documentation

feedback, security guidelines, and also recommended aliases and general Cisco

documents, 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

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures

included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 1999-2013 Cisco Systems, Inc. All rights reserved.

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

Documents

Readme File for Cisco Prime Network 4.1.0.0.1 Point Patch · manual rollback), run the upgrade.pl script with the –nobackup option, as follows: perl upgrade.pl –nobackup This