Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 1
Readme File for Cisco Prime Network 4.2.2.0.2
Point Patch
Revised: Oct 15, 2015
This document supports the release of the Prime Network 4.2.2.0.2, which is installed on
top of Cisco Prime Network 4.2.2. All changes described in this document apply only to
Cisco Prime Network 4.2.2.0
Note: It is recommended to install the latest Prime Network device package available on
CCO.
Prerequisites:
Prime Network 4.2.2.0.0 / 4.2.2.0.1
Prime Network VNE Driver - 4.2.2-DP1509 + Hotfix for Defect: CSCuw57870- P-PN: Publish
CB failed also running CM failed due missing hierarchy loc. (Please refer to VNE Driver
readme for further information)
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 2
Table of Contents
1 What’s New 3
2 Obtaining the Point Patch 4
3 Point Patch Contents 4
4 Explanation on Contents 4
5 Installing the Point Patch 5
6 Optional – Post Installation of Prime Network Integration Layer 9
7 Optional - Prime Network Operations Report Patch Installation 10
8 Verifying the Prime Network Point Patch Installation 12
9 Post Patch Installation Tasks 14
10 Uninstalling the Prime Network Point Patch 15
11 Verifying the Prime Network Point Patch Uninstalling 18
12 Resolved Caveats – Cisco Prime Network 4.2.2.0.2 Point Patch 19
13 Bug Resolutions That Require VNE Device Package 21
14 Obtaining Documentation, Support and Security Guidelines 21
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 3
1 What’s New 1. Port down and pluggable transceiver out event correlation
Added logic to correlate port down and pluggable transceiver out events.
2. Prime Network Logical Inventory - 'Non Revertive' field
Logical Inventory - Ethernet Link Aggregation - Data Link Aggregations was enhanced
with a new 'Non Revertive' field for Bundle-Ethernet on ASR9k with image version 5.3.2.
This new field represents the status of the non revertive functionality on a bundle:
If Non Revertive has enabled for the bundle, then it will be shown as 'Enabled‘'.
If Non Revertive has disabled for the bundle, then it will be shown 'Disabled'.
For ASR9k devices with HW Image below 5.3.2, the 'Non Revertive' field value will be
shown 'N/A' as it is not sent from the device. Revertive is the default behavior for link
aggregation.
Note: this feature requires also the installation of DP1509.
3. Detailed device status for cancelled jobs
Prime Network CCM was enhanced to display for each cancelled job, the devices in which
the tasks were completed successfully, failed, or cancelled.
These details can be used when cancelling a job run in error to identify the devices
requiring to be addressed as the job completed, when cancelling jobs at the end of the
maintenance window to identify the devices that will require the job to be executed on the
next maintenance window, and more.
4. Improvements to the Compliance jobs cancellation
Prime Network CCM Compliance jobs cancellation was enhanced to immediately stop any
device interaction in progress at any step in the job process.
5. Originating trap Id added to EPM MIB notifications
Prime Network EPM MIB Notifications wizard was enhanced with the option for users to
choose to include the ID, long description and troubleshooting information of the first trap that
caused the ticket to be created (in addition to the ID of the trap that is listed as the current root
cause)
This information will also be forwarded to PC 1.5 which will include it in the enhanced 3GPP SOAP XML alarm forwarding
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 4
2 Obtaining the Point Patch To obtain the Cisco Prime Network 4.2.2.0.2 Point Patch installation, download it from:
https://software.cisco.com/download/type.html?mdfid=286287455&flowid=76162
3 Point Patch Contents Cisco Prime Network 4.2.2.0.2 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 12
Resolved Caveats.
4 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.
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 5
5 Installing the Point Patch This procedure describes how to install the Cisco Prime Network 4.2.2.0.2 Point Patch on
top of an existing Cisco Prime Network 4.2.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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 6
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.2.0.2
6. Grant the directory Cisco Prime Network user permission.
Example:
chown <Prime Network-user>:ana 4.2.2.0.2
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.2.0.2 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.
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 7
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.2.0.2
unzip Prime_Network4.2.2.0.2.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.2.0.2.zip
2. 4.2_Reports.zip
5. For installing the Prime Network patch, go to the newly created sub directory (i.e.
Point-Patch) and unzip the Prime Network Patch zip file:
Example:
cd ./Point-Patch
unzip Prime_Network4.2.2.0.2.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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 8
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 7 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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 9
6 Optional – Post Installation of Prime Network
Integration Layer 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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 10
7 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 Patches 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: (i.e. 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. (Refer to Step 5 in
Section 5, Installing the Point Patch)
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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 11
1. Stop the server using the Pentaho master script:
~/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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 12
8 Verifying the Prime Network Point Patch
Installation This section describes how to verify that Cisco Prime Network 4.2.2.0.2 Point Patch has
been installed successfully, as explained in Section 5, 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.2.0.2 _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.2.0.2_PP.jar
If the installation was successful, information similar to the following is displayed:
Patch Prime_Network4.2.2.0.2_PP.jar correctly installed in the
gateway (127.0.0.1)
Patch Prime_Network4.2.2.0.2_PP.jar correctly installed in the golden
source registry (0.0.0.0)
Patch Prime_Network4.2.2.0.2_PP.jar correctly installed in the unit
<unit IP>
Patch Prime_Network4.2.2.0.2_PP.jar correctly found at the start of
0.out log file
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file
/export/home/pn42/Main/webstart/agentregistryviewer.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/bosmanage.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/dcdebugger.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/eventvision.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/networkvision.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file
/export/home/pn42/Main/webstart/processdebugger.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/regedit.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file
/export/home/pn42/Main/webstart/sessiondebugger.jnlp
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 13
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/stresser.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar correctly found as the first
reference on file /export/home/pn42/Main/webstart/workflowstudio.jnlp
Patch Prime_Network4.2.2.0.2_PP.jar's classes files are being called
from this patch on server 127.0.0.1
Patch Prime_Network4.2.2.0.2_PP.jar's xml files are being called from
this patch on server 127.0.0.1
Patch Prime_Network4.2.2.0.2_PP.jar's classes files are being called
from this patch on server <unit IP>
Patch Prime_Network4.2.2.0.2_PP.jar's xml files are being called from
this patch on server <unit IP>
---> Patch Prime_Network4.2.2.0.2_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.2.0.2_PP.jar not correctly installed or
at least one warning displayed
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 14
9 Post Patch Installation Tasks 1. After installing or upgrading PN it is recommended to clear the browser cache before
using the CCM application.
2. 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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 15
-----------------------
400
10 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.
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.
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 16
7. Navigate to the Prime_Network_upgrade directory you created for installing the Point
Patch:
Example:
cd 4.2.2.0.2/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.2.0.2/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>
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 17
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
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 18
11 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.
4. Enter the following command:
./runRegTool.sh -gs 127.0.0.1 get 127.0.0.1 site/mvm/services/bsm/patchjar
You should not see the Point Patch that was removed.
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
You should not see the Point Patch that was removed.
6. To verify that the Prime_Network4.2.2.0.2_PP.jar file does not exist in any of the
JNLP files, enter the following command:
cat ~/Main/webstart/*.jnlp | grep Prime_Network4.2.2.0.2_PP.jar
The output should be empty.
7. Enter the following command:
find ~/Main/ -name Prime_Network4.2.2.0.2_PP.jar
The output should be empty.
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.2.0.2_PP.jar
The output should be empty.
10. Check the AVM 11 log file by entering the following command:
cat 11.out | grep Prime_Network4.2.2.0.2_PP.jar
The output should be empty.
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 19
12 Resolved Caveats – Cisco Prime Network
4.2.2.0.2 Point Patch The following caveats have been fixed in Cisco Prime Network 4.2.2.0.2 Point Patch.
Resolved Caveats - 4.2.2.0.2 Point Patch
Identifier Headline
CSCuv60898 FEC-129:Naming of FEC-129 pw in EVC & pw discovery shd be end
to end
CSCuv77599 FEC-129: Incomplete IP address in EVC representation
CSCuv85452 VNE is not modeled using SSH
CSCuv07170 CCM: Shift-click selection and select-all have different behavior
CSCuv93149 Compliance Audit Dialog box is not populating data in ALL JOBS.
CSCuv51845 Image Distribution: Same device result is showing multiple times.
CSCuu97806 com.jcraft.jsch.JSchException: verify: false during Image distribution
CSCuj27901 CCM - About and splash screen don't show CCM PP or SP version
CSCuu34625 Add new vendor for Ruggedcom & new element type for Ruggedcom
and Ciena
CSCuv58416 Nexus 9K support is needed in CCM Framework
CSCuv87277 Support of Cancel Job in NCCM and Switch user in CM
CSCuw32083 MPLS-TE topology links are not shown in maps
CSCuw21580 MPLS TE liink down ticket hyperlink not working.
CSCuw21575 MPLS TE links colour does not change on link down.
CSCuw01245 VNE status does not reflect disabled reachability tracking command
CSCuw12046 Cancelled job:Compliance:Jobs are not getting cancelled
CSCuv63126 Getting OUT OF BOUNDS:18 value in GUI for G.8032 service
container
CSCuw02863 Port Down and Pluggable transceiver out is not Correlating
CSCuw26649 Issues in Cancel Task
CSCuw29749 Listing out cancelled tasks in new dialog for NCCM
CSCut71391 Add new vendor for Edgewater, element type for Edgewater and
Adtran
CSCuw26959 Non-revertive lag support in Bundle Ethernet for ASR9k
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 20
CSCus75245 ASR9K satellite Host roll is not updated after IC port down
CSCut32817 VNE inventory shows wrong numbers for MLPPP group
CSCuf15027 ENH: LDAP need to authenticate users belonging to different
subgroups
CSCup21269 Collector agent is suspended when a Command Script is executing
CSCur75222 CRS8S: Fan-tray out has not been developed on fan tray OIR
CSCur68162 CCM job/CB exe not work when "Ask for user creds" is en and device
is wi
CSCuq11869 PN - NCCM - Help About is showing SNAPSHOT reference in version
CSCui35119 NCCM - config restoration fail in device banner
CSCur75646 Exception when see comma in oid in property_value of notfication
table
CSCus83290 PN CCM 4.0 IPA config backup naming convention incorrect
CSCus81180 "Authentication expired" causes false BGP events
CSCuu13741 NullPointerException in IsSubTree when parsing traps
CSCut91924 ignore-template rule does not work in case of Unassociated events
CSCuv14567 CCM restore fails when banner has empty newline spaces in it
CSCub20879 VEM modules status in Nexus 1000 is shown as unknown in GUI
CSCur79402 Some Interface status down alarms are not cleared on chassis connected
CSCut89371 Port utilization counters are way beyond 100%
CSCuv49045 Bad geometry of Registry Controller window
CSCuv48843 SNMP reachability test param change doesnot affect the alarm
development
CSCuv57682 Path Tracer fails to find trace route for PW originated on ASR9K VNE
CSCuv55493 EFP policy bindings are not added/updated when interface
added/changed
CSCuv91862 special characters removal on telnet result from ASR9K
CSCuv90200 Pathtracer: Sometimes Layer 2 information is not displayed in results
CSCuw01748 ana startup fails because "ssh localhost" fails.
CSCuv05316 Patch stream build issue
CSCuw14772 Remove compliance policies backup for PP/SP from upgrade.pl
CSCuw09429 Events do not get updated with a Null Pointer Exception
CSCuw39377 Cancelled Task:It is showing junk values in cancelled tasks
CSCuw37658 Cancelled user name is not coming on jobs page of Compliance audit.
CSCuw40593 PN failed to discover MPLS link between ASR903 and ASR920
CSCuw44366 VNE Failed to push MPLS topology data for matching
CSCul46808 configurator commands should have urgent priority
CSCuw44404 Any user other than administrator not able to run command manager
job
CSCuv73336 Image Distribution: Running jobs are not getting cancelled
All contents are Copyright © 2015 Cisco Systems, Inc. All rights reserved. Page 21
CSCuw15861 Not able to upgrade to 4.2.2.0.2 from 4.2.2.0.1
CSCuw43125 Wrong dialog box is displaying while clicking on cancelled hyperlink
CSCuw48039 Command manager result "no managed devices found with device
profile"
CSCuw28688 Cmd Manager:Edit: Residual devices present after deselection of
devices.
CSCuw35168 Command manager parent job - view and edit is not working properly
CSCuw50081 Command Manager Cancelled Job: Still runs in the backend
CSCuw45121 CCM Cancelled Jobs: Does not display the device details
CSCuw26080 Refresh Button Is not ressponding in ALL JOBS Page
CSCuw62710 CCM: XR Image Distribute and activate in a single job fails
CSCuu88970 VPN IPv6 links are not ignored when ignoreVrfLinks is true in registry
CSCut23090 ArrayIndexOutOfBoundsException flood AVM 11 log
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)
See – Pre-requisites
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.