Readme File for Cisco Prime Network 4.2.0.1.4 Point Patch€¦ · Note: Not all Point Patchs contain updates for Prime Network Operations Report. If you don’t have Prime Network

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

Readme File for Cisco Prime Network 4.2.0.1.4 Point Patch

Revised: Aug 25, 2015

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

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

to Cisco Prime Network 4.2.

Note: It is recommended to install the latest Prime Network device package available on

CCO.

Prerequisite: Prime Network 4.2.0.1.0

Note:

This document also includes instructions for workarounds to several bugs - See section

13 Known Caveats – Cisco Prime Network 4.2.0.1.4 Point Patch

https://software.cisco.com/download/type.html?mdfid=286283635&flowid=73262


Table of Contents

1 Obtaining the Point Patch 3

2 Point Patch Contents 3

3 Explanation on Contents 3

4 Installing the Point Patch 4

5 Optional – Post Installation of Prime Network Integration Layer 8

6 Optional - Prime Network Operations Report Patch Installation 9

7 Verifying the Prime Network Point Patch Installation 11

8 Post Patch Installation Tasks 13

9 Uninstalling the Prime Network Point Patch 14

10 Verifying the Prime Network Point Patch Uninstalling 17

11 Known Caveats – Cisco Prime Network 4.2.0.1.4 Point Patch 18

12 Resolved Caveats – Cisco Prime Network 4.2.0.1.4 Point Patch 18

13 Bug Resolutions That Require VNE Device Package 23

14 Obtaining Documentation, Support and Security Guidelines 23


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

https://software.cisco.com/download/type.html?mdfid=286283635&catid=null

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

support of the following:

Prime Network Patch

Resolved caveats. For a list of caveats resolved in this Point Patch , see section 14

Resolved Caveats.

3 Explanation on Contents

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

Prime Network Integration Layer base application exists. If there are any updates

associated with Operations Reports, they will also be included in this patch installation.

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

Operations Report Tool.

https://software.cisco.com/download/type.html?mdfid=286283635&catid=null


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

top of an existing Cisco Prime Network 4.2 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 PRIME NETWORK 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, 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

If you are using Operations Reports, verify that the MySql database is up prior to

installing the Prime Network Point Patch.

Example: (as ‘root’ user)


service mysqld-ib status

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.2.0.1.4

6. Grant the directory Cisco Prime Network user permission.

Example:

chown <Prime Network-user>:ana 4.2.0.1.4

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 Cisco Prime Network user permission to the 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.2.0.1.4 Point Patch with the

default option: perl upgrade.pl.

To install the Point Patch without a backup (no rollback option), 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.2.

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 the Prime Network user.

2. Navigate to the directory in which you placed the Point Patch.

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-2/administrator/guide/CiscoPrimeNetwork42AdministratorGuide.html?mdfid=286283635



3. Navigate to the patch directory location created in Step 5 and unzip the file to extract

the necessary JAR files and Perl scripts (for Prime Network and Operations Report

installation).

Example:

cd /export/home/4.2.0.1.4

unzip Prime_Network4.2.0.1.4.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.2.0.1.4.zip

2. 4.2_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.2.0.1.4.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. Enter root password when prompted to do so.

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

for NAT Units in the Cisco Prime Network 4.2 Installation Guide.

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

being installed, “Upgrading NCCM”.

11. 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 the 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).

12. 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.

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

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

Operations Report Tool Installation.

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>

16. If you are working in suite mode, log on to the Prime Central Server and restart the

Integration Layer.

itgctl stop

itgctl start

17. On the Prime Network Gateway Verify that the Prime Network Integration Layer is

up. If not start Prime Network Integration Layer.

As the Prime Network user, run:

$PRIMEHOME/local/scripts/itgctl start

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

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


5 Optional – Post Installation of Prime Network Integration Layer

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 Prime Network Point Patch, follow the install procedure specified in the

Prime Network 4.2 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, 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.2. Refer to “Installing Prime Network Operations Report” in the Prime

Network 4.2 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 Patchs contain updates for Prime Network Operations Report.

If you don’t have Prime Network Operations Report installed or if there is no 4.2 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 step 5 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.2_Reports.zip

3. As the PRIME NETWORK installation user, run the following commands to start the

patch installation:

cd ./4.2_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

Once the patch is successfully installed, the solution repository requires a restart and

refresh. Follow the steps provided below for the post installation.

Post installation steps for Operations Report Patch Install

1. Stop the server using the Pentaho master script:

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

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


~/pentaho/ctlscript.sh stop

2. Ensure all Pentaho process are stopped. 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.2.0.1.4 Point Patch has

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.2.0.1.4 _PP.jar: Prime_Network4.2.0.1.0 _PP.jar:patch.jar

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

Patch have been installed successfully:

checkPatchInstallation.pl Prime_Network4.2.0.1.4_PP.jar

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

Patch Prime_Network4.2.0.1.4_PP.jar correctly installed in the

gateway (127.0.0.1)

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

source registry (0.0.0.0)

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

<unit IP>

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

0.out log file

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

reference on file

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


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


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


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


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


reference on file

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


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


reference on file

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



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


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

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

from this patch on server 127.0.0.1

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

this patch on server 127.0.0.1

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

from this patch on server <unit IP>

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

this patch on server <unit IP>

---> Patch Prime_Network4.2.0.1.4_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.2.0.1.4_PP.jar not correctly installed or

at least one warning displayed


8 Post Patch Installation Tasks If you are using CCM on a large scale Network, change the number of allowed

connections to 400

(See installation guide for definition of Large Network .)

Run the following SQL Commands as system dba:

SQL> update <PNUSER_SCHEMA_NAME>.BOSUser set

ALLOWEDCONNECTIONNUMBER=400 where username='root';

SQL> commit;

Example:

[root@tier4-rhel-vm26 ~]# su - oracle11

oracle11@tier4-rhel-vm26 [~]# sqlplus

SQL*Plus: Release 12.1.0.1.0 Production on Sun Mar 8 14:48:45 2015

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Enter user-name: system

Enter password: XXXXXXX

Last Successful login time: Sun Mar 08 2015 09:39:31 -04:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit

Production

With the Partitioning, OLAP, Advanced Analytics and Real Application

Testing options

SQL> select ALLOWEDCONNECTIONNUMBER from pn42.BOSUser where

username='root';

ALLOWEDCONNECTIONNUMBER

-----------------------

40

SQL> update pn42.BOSUser set ALLOWEDCONNECTIONNUMBER=400 where

username='root';

1 row updated.

SQL> commit;

Commit complete.

SQL> select ALLOWEDCONNECTIONNUMBER from pn42.BOSUser where

username='root';

ALLOWEDCONNECTIONNUMBER

-----------------------

400

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network/4-2/installation/guide/CiscoPrimeNetwork42InstallationGuide/installation_requirements.html#pgfId-1182175


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 and Operation

Reports.

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.2.

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.2.0.1.4/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.2.0.1.4/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.2 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.2.0.1.4_PP.jar file does not exist in any of the

JNLP files, enter the following command:

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

The output should be empty.


find ~/Main/ -name Prime_Network4.2.0.1.4_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.2.0.1.4_PP.jar


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

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



11 Known Caveats – Cisco Prime Network 4.2.0.1.4 Point Patch

The following caveat has not been fixed in Cisco Prime Network 4.2.0.1.4 Point Patch.

Known Caveats - 4.2.0.1.4 Point Patch Identifier severity Headline

CSCut03550 3 GEO HA SUITE: PN standby gw integration info is pointing the primary PC

CSCut18510 3 ComplianceAudit filter not work properly without clearing browser...

Workaround For Bug CSCut03550

1. Edit the following file on Both Primary and Standby Prime Network Gateways:

/var/adm/cisco/prime-network/scripts/ha/rsync/rsync_exclude_pn.txt

2. Add the following three lines:

*Main/registry/suite-integ.xml

*Main/registry/ConfigurationFiles/127.0.0.1/suite-integ.xml

*Main/registry/ConfigurationFiles/0.0.0.0/suite-integ.xml

Example:

Workaround For Bug CSCut18510

1. Clear Browser Cache

12 Resolved Caveats – Cisco Prime Network 4.2.0.1.4 Point Patch

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


Resolved Caveats - 4.2.0.1.4 Point Patch

CSCuo69858 Show Command missing while importing/editing policy with showCommand

CSCus38473 Command Manager: Not able to exeute the job for more than 500 devices

CSCus47872 Copyright for PN 4.2.0.1.0 needs to be updated to include year 2015

CSCus28736 Command Manager Queue Issue(PTP Manager Pool)

CSCus21425 PN 4.2.0.1 - PP and DP installation failure

CSCus12463 PP build doesn't collect new IMO under ana.base

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

CSCur75222 CRS8S: Fan-tray out has not been developed on fan tray OIR

CSCur16547 Power Supply out service alarm not cleared on module inserted

CSCus08746 AVM25 gets stuck some times during failover scenario's

CSCur20403 False LAG link down on unreachable with LAG interface shutdown

CSCus50496 SNMP Collector gets stuck in idle for up to 30 minutes before released

CSCus79864 Remove expedite of forwarding table registr. due to performance impact

CSCur99852 LACP topology test fails to discover moved or added physical link

CSCus80991 Need null point check on in swapAddresses method of Collector.java

CSCur79402 Some Interface status down alarms not cleared on chassis connected

CSCus42041 Need to add "custom" Enum in AAARadiusAccountingGTPTriggerPolicyEnum

CScus51781 Need descriptiive message for OID doesn't exist Event Vision GUI pop up

CSCur34269 upgrade.pl warns about variable init

CSCus89798 Device Proxy asks for telnet port

CSCui05381 Device Proxy support for key based auth requires user to change jars

CSCur02707 telnet command in networkvision needs to use the protocol set in the VNE

CSCur48627 Command Sequence : Add commands filter not selecting the right commands

CSCus85088 Command Manager: Advanced Filter option is not working

CSCus85247 Image activaiton is getting failed if we run large number of devices.

CSCus38507 Distribute: All the devices are selected even though few are filtered

CSCus83910 Compliance Manager-Quick filter for hostname is not working properly

CSCup02906 adding parsing command for delay all registrations

CSCur99826 LAG member down alarm is not cleared when member is removed from group

CSCus83290 PN CCM 4.0 IPA config backup naming convention incorrect

CSCus44452 EVNE: Development of LAG down/up events sometime takes hours

CSCus22634 MPLS TE FRR State Changed to Active not cleared though inventory updated

CSCup87393 Audio alarm get broken if ticket gets cleared quickly

CSCur48022 Durin 2 units HA -java dead lock occurs on avm

CSCus45370 Need remove duplicate calls of dia-application for proxy events

CSCut03198 nullpointer in AlarmNotificationImoGenerator stops notification process

CSCut04573 IllegalDestinationAddressException in BfdCorrelationResolvingFlowMH


CSCur81697 Layer 2 tunnel down service alarms are not cleared at VNE init

CSCus95113 Hostname support for Compliance Audit

CSCut06802 Prime network 4.2 is not picking up CCM build

CSCus73492 PN sever out of processes due to failure in port_redirect_watchdog.pl

CSCut08164 X-Launch PN to PP failing - malformed URL

CSCus99853 ClassNotFoundException in released PN4.2 build

CSCur76695 context menu Tools->Telnet needs to be generic named

CSCut08286 NCCM ftp export backup configuration hours names after 12PM seee like ho

CSCui35119 NCCM - config restoration fail in device banner

CSCut12650 PN - Unable to export multiple configs in NCCM

CSCut14172 Some DS0 bundle alarms for CEM groups stay not cleared indefinitely

CSCut14244 The DS0 bundle alarms for CEM groups are not correlated to root cause

CSCuq90423 Adding large number VCB event pattern using CLI fails

CSCut20486 XMP in PN is using 32 bit instead 64 bit

CSCut09764 change log is missing newline char between lines

CSCut32817 VNE inventory shows wrong numbers for MLPPP group

CSCus81180 "Authentication expired" causes false BGP events

CSCut19582 Backup on the ASR5K failed

CSCut11958 PN 4.2 March DP: Tables not displayed for HSGW service

CSCut11955 PN 4.2 March DP: Tables not displayed for HA - service

CSCus41846 DcOid Errors in Logs for ASR5K

CSCur83563 IS IS information in IOS XR is showing wrong data

CSCut36127 BfdCorrelationResolvingFlowMsg'es overwhelm VNE message queue

CSCut41011 RuntimeException when 1 of 5 or more LAG or MLPPP member shut down

CSCut41340 Some Adaptive Polling alarms have duplicate description

CSCur77764 ASR9001: Fan status is Unknown after chassis disconnected

CSCur90050 NullPointerException in LSE DC when label forwarding table changes

CSCur33112 Add new element type in PrimeNetwork for X1200

CSCul76399 Recordings from persistency are not context aware

CSCuj44143 Telnet sequence enhancements required for Symmetricom devices

CSCut21053 system event for missing statistics should not be raised on temp tables

CSCut53461 Protection delay mechanism for repetitive commands is not working

CSCup21205 Flapping Event application is creating proxy event for traps

CSCut18143 DP is not being presented after installing PP

CSCup21269 Collector agent is suspended when a Command Script is executing

CSCur46387 Card down for non-FRU modules is not cleared

CSCur53183 Command Manager is extremely slow while creating a new command

CSCuq94869 upgrade.pl fails on permissions update

CSCut87372 Nexus7K has missing containers and evil twin errors appear in AVM log

CSCum80241 Null pointer exception in 100.out

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

CSCut33840 infobright.sh does not support multi mount points


CSCut82369 HA-Service:AAA attributes configuration is not reflecting in Vision

CSCut90972 Technology changes for PDSN:QOS Mismatch in PN

CSCup54009 vne does not search for static links with cloud

CSCut45035 Technology changes for APN-profile, Value of DSCP BE is not correct.

CSCuu06070 Modify LMA "Mobility Option type Value"

CSCut04724 PN - GGSN Service Extended Properties are causing log errors on startup

CSCut15527 ASR9K - POS interfaces are not getting modeled

CSCut30141 CCM The device is not under the scope of the user to perform operation

CSCut60231 PN creates two BGP links between pair of BGP dual stack neighbors

CSCut92020 Sometimes ITicket notification missing flagging alarm state and severity

CSCuu16533 PN: upgrade.pl died - mySQL stop timed-out restart aborted

CSCuu33515 Config backup in NCCM is failing

CSCuu33915 vcb event view -eventname all return "Error -1: null"

CSCuu39874 exception in AlarmNotificationImoGenerator.java stop notification handle

CSCuu42479 missing policy setting for ip interface in PortIpsPostTranslator.java

CSCuu47079 Link between ASR9k and Catalyst switch discovered and then removed

CSCuu63599 PN fails discover LAG ICL link configured as Ethernet Channel

CSCuq88638 PN - CPT Backup with NCCM results in BQL timeout when TL1 not defined

CSCur99687 PN - AVM log errors ImoTranslator.translate on VNE restart

CSCuu11665 PN - patch install script fails with Pentaho installed

CSCuu56148 Link down not cleared due interface status OK while oper status is down

CSCus59176 Fan Tray displayed wrongly for ASR5500 17.1 device

CSCuu35122 Environmental trap ticket is not cleared in the Network Vision

CSCuf77169 NullPointerException while parsing %OSPF-5-ADJCHG syslog

CSCuu62951 Error editing Compliance audit job with device filter and select-all

CSCuu28201 VCB & NW discovery splash screen don't show correct PP or SP version

CSCut34009 Null Pointer Exception displayed in Logs for ASR5K and QVPC-DI Device

CSCuu89131 Missing OSPF v2 interfaces in NV if configured with IPV6 addr also.

CSCuu84813 lotem ssh ghost connection prevents new connections

CSCuu22911 Frame Relay Traffic profiles are missing from logical inventory

CSCuv05888 Run command manager jobs only if Device is reachable

CSCuu93176 Port utilization alarm for DS1 controller shows wrong location

CSCuu97743 When distributing image on many devices image distribute fails

CSCuu88970 VPN IPv6 links are not ignored when ignoreVrfLinks is true in registry

CSCus75245 ASR9K satellite Host roll is not updated after IC port down

CSCut31343 Technology changes for class mapnot updated without clicking PollNow

CSCuu36668 Asr901: Issues in IS-IS technology

CSCuu35081 DcOidMapping Exception in Logs for ASR5K/QVPC SI/DI device

CSCuu46020 Tech Changes for APN Profile - Qos Service capping values

CSCuv00471 MAG Service : Information-set type & mobility option is not reflecting

CSCut89371 Port utilization counters are way beyond 100%

CSCuu27480 NCCM - config restoration fail in device banner on 6500 device series


CSCur68162 CCM job/CB exe not work when "Ask for user creds" is en and device is wi

CSCuv27158 Compliance jobs fail with null pointer exception

CSCuv19476 Device Not in User Scope for Compliance

CSCuv27146 Command manager queue connections need to be validated and removed

CSCuu45704 Image Activation Fails with " image not present on Device"

CSCut32817 VNE inventory shows wrong numbers for MLPPP group

CSCub20879 VEM modules status in Nexus 1000 is shown as unknown in GUI

CSCuf15027 ENH: LDAP need to authenticate users belonging to different subgroups

CSCuu13741 NullPointerException in IsSubTree when parsing traps

CSCuv48843 SNMP reachability test param change doesnot affect the alarm development

CSCuu34625 Add new vendor for Ruggedcom & new element type for Ruggedcom and Ciena

CSCuu74111 Cmd builder sometimes runs in 30 secs delay in ME-3600 devices

CSCuu75507 ccm config edit comma followed by space introduces new line character

CSCuv49045 Bad geometry of Registry Controller window

CSCur79402 Some Interface status down alarms are not cleared on chassis connected

CSCuv57682 Path Tracer fails to find trace route for PW originated on ASR9K VNE

CSCuv58416 Nexus 9K support is needed in CCM Framework

CSCus75143 ASR9K satellite down event is not correlate to link down

CSCus77219 Link down due to card out between ASR9K IC port to satellite is not clea

CSCut91953 Command manager gets stuck up when a device type is selected

CSCut91924 ignore-template rule does not work in case of Unassociated events

CSCuv14567 CCM restore fails when banner has empty newline spaces in it


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)

CSCur79402 All status retrieving registration must have 'onchange' flag set 'false'

04.2(00.01)PP03 04.2(00X)DP1507

CSCup02906 Removing an RSP cards - chassis disconnect alarm is generated

04.2(00.01)PP01 TBD(CSCup00169)

CSCuq90423 Default pattern for trap and syslog parsing has to be changed

04.2(00.01)PP02 04.2(00X)DP1507

CSCur46387 ASR9K: Card down for virtual module is not cleared in SIP card down test

04.2(00.01)PP02 TBD(CSCuq20214)

CSCuu06070 Modify LMA "Mobility Option type Value"

04.2(00.01)PP03 TBD(CSCut89014)

CSCuu42479

issue in CiscoIOXQoSAppliedInterfaceParser.java in splitting policy data

04.2(00.01)PP03 04.2(00X)DP1505

CSCuu22911 Frame Relay Traffic profiles are missing from logical inventory

04.2(00.01)PP03 TBD (CSCuu70507)

CSCuu34625

Add new vendor for Ruggedcom & new element type for Ruggedcom and Ciena

04.2(00.01)PP04 TBD

CSCut45035 Technology changes for APN-profile, Value of DSCP BE is not correct

04.2(00.01)PP03 TBD (CSCut40059 )

CSCuu46020 Tech Changes for APN Profile - Qos Service capping values

04.2(00.01)PP04 TBD (CSCuu06036)

CSCuv00471 MAG Service : Information-set type & mobility option is not reflecting

04.2(00.01)PP04 TBD

(CSCuu94592)

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.

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-2015 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.2.0.1.4 Point Patch€¦ · Note: Not all Point Patchs contain updates for Prime Network Operations Report. If you don’t have Prime Network