readme file for cisco prime network 3.10.0.1.0 service patch · from this patch on server patch...

All contents are Copyright © 2013 Cisco Systems, Inc. All rights reserved.

Readme File for Cisco Prime Network 3.10.0.1.0 Service Patch

Revised: July 1, 2013

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

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

Cisco Prime Network 3.10. This Service Patch accumulates previous Point Patches of

3.10.0.0.x.

Note: This Service Patch installation reminds the user to run the 'ivne' command to install

additional Device Packages when the upgrade completes.

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

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

Prerequisite: Before installing Prime Network 3.10.0.1.0, one needs to install Prime

Network 3.10.0.0.1 which is available at CCO:

http://software.cisco.com/download/type.html?mdfid=284560160&flowid=39388

Table of Contents

1 Obtaining the Service Patch 1

2 Service Patch Contents 2

3 Installing the Service Patch 2

4 Verifying the Service Patch Installation 5

5 Uninstalling the Service Patch 7

6 Verifying the Service Patch Uninstalling 11

7 Resolved Caveats – Cisco Prime Network 3.10.0.1.0 Service Patch. 12

8 Bug Resolutions That Require VNE Device Package 16

9 Obtaining Documentation, Support and Security Guidelines 17

1 Obtaining the Service Patch To obtain the Cisco Prime Network 3.10.0.1.0 Service Patch for installation downloaded it

from Cisco.com:





2 Service Patch Contents Cisco Prime Network 3.10.0.1.0 Service Patch contains:

The necessary files and scripts to upgrade successfully.

Resolved caveats, identified in Resolved Caveats – Cisco Prime Network 3.10.0.1.0

Service Patch.

3 Installing the Service Patch This procedure describes how to install the Cisco Prime Network 3.10.0.1.0 Service Patch

on top of an existing Cisco Prime Network 3.10 installation and Cisco Prime Network

3.10 Service Patch 1.

Prerequisite: Before installing Prime Network 3.10.0.1.0, one needs to install Prime

Network 3.10.0.0.1 which is available at CCO:


Before You Begin

1. If you are using the HA/DR VERITAS solution:

a) Uncheck the critical flag from the Cisco Prime Network gateway resource in the

VERITAS Cluster Manager application.

b) Via the VERITAS Cluster Manager, bring Prime Network offline.

c) Disable the Cisco Prime Network gateway resource in the VERITAS Cluster

Manager application.

d) Login to the gateway and start Prime Network by running “networkctl start“.

e) Wait until Prime Network gateway and units are up and running before continuing

with this patch installation.

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

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

installing the Service Patch.

4. Copy the Service Patch to a directory outside of the Cisco Prime Network home

directory.



5. Grant the directory Cisco Prime Network user permission.

For example, after you login to the Cisco Prime Network gateway as root user, you

might enter commands similar to the following:

cd /export/home

mkdir 3.10.0.1.0

chown <Prime Network-user>:ana 3.10.0.1.0

Example: chown [network-user]:ana 3.10.0.1.0

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 $ANAHOME.

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 3.10.0.1.0 Service Patch with

the default option: perl upgrade.pl –p.

To install the Service 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 –p –nobackup

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

to rollback to a previous Service Patch, 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, 3.10.

The upgrade script prompts you with an option to install VNE Drivers.

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

has completed successfully.

http://www.cisco.com/en/US/docs/net_mgmt/prime/network/3.10/administrator/guide/adminguide10.html

http://www.cisco.com/en/US/docs/net_mgmt/prime/network/3.10/administrator/guide/adminguide10.html


Installation Procedure

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

2. Navigate to the directory in which you placed the Service Patch. (See Before You

Begin.)

3. To extract the necessary JAR files and Perl scripts, unzip the file by entering the

following command:

unzip Prime_Network3.10.0.1.0.zip

4. Navigate to the 3.10.0_PP directory:

cd Prime_Network_upgrade/3.10.0_SP

5. Extract the necessary XMP_DATACENTER JAR and SDU files, by entering the

following command:

jar –xvf Prime_Network3.10.0.1.0_others.jar

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 Service Patch with the option to roll back:

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

perl upgrade.pl -p

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

perl upgrade.pl –p -nobackup

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

9. As Prime Network user navigate to $ANAHOME/local/scripts and run the following

commands:

a. su root

b. enter root password

c. tcsh

d. ./setFpingPermissions.tcsh

10. If you are using the HA/DR VERITAS solution, enable the Prime Network gateway

resource and mark it as critical in the VERITAS Cluster Manager application.


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


a) clusvcadm –U <Prime Network service>

b) clusvcadm –U <Oracle service>


4 Verifying the Service Patch Installation This section describes how to verify that Cisco Prime Network 3.10.0.1.0 Service Patch

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

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

the Service 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 Service Patch installed:

checkPatchInstallation.pl -p

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

Current patch (in 127.0.0.1):

Prime_Network3.10.0.1.0_SP.jar:patch.jar

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

Patch installed successfully:

checkPatchInstallation.pl Prime_Network3.10.0.1.0_SP.jar

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

Patch Prime_Network3.10.0.1.0_SP.jar correctly installed in the

gateway (127.0.0.1)

Patch Prime_Network3.10.0.1.0_SP.jar correctly installed in the

golden source registry (0.0.0.0)

Patch Prime_Network3.10.0.1.0_SP.jar correctly installed in the unit

<unit IP>

Patch Prime_Network3.10.0.1.0_SP.jar correctly found at the start of

0.out log file

Patch Prime_Network3.10.0.1.0_SP.jar correctly found as the first

reference on file

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


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


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


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


reference on file

/export/home/ana310/Main/webstart/networkvision.jnlp


reference on file

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


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



reference on file

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


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


reference on file

/export/home/ana310/Main/webstart/workflowstudio.jnlp

Patch Prime_Network3.10.0.1.0_SP.jar's classes files are being called

from this patch on server 127.0.0.1

Patch Prime_Network3.10.0.1.0_SP.jar's xml files are being called

from this patch on server 127.0.0.1

Patch Prime_Network3.10.0.1.0_SP.jar's classes files are being called

from this patch on server <unit IP>

Patch Prime_Network3.10.0.1.0_SP.jar's xml files are being called

from this patch on server <unit IP>

---> Patch Prime_Network3.10.0.1.0_SP.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_Network3.10.0.1.0_SP.jar not correctly installed or

at least one warning displayed

ana310


5 Uninstalling the Service Patch This procedure describes how to uninstall the Service Patch. You do not need to uninstall

a Service Patch unless you need to completely remove the Service Patch.

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

using the command: perl upgrade.pl –p.

Rollback Procedure

1. If you are using the HA/DR VERITAS solution:

a) Uncheck the critical flag from the Cisco Prime Network gateway resource in the

VERITAS Cluster Manager application.

b) Via the VERITAS Cluster Manager, bring Prime Network offline.

c) Disable the Cisco Prime Network gateway resource in the VERITAS Cluster

Manager application.

d) Login to the gateway and start Prime Network by running “networkctl start“.

e) Wait until Prime Network gateway and units are up and running before continuing

with this patch uninstall.

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


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


clusvcadm –Z <Prime Network service>

clusvcadm –Z <Oracle service>

For example:

clusvcadm –Z ana

clusvcadm –Z oracle_db

4. Login to Prime Network Administration and remove all redundant units.

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

6. 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, 3.10.

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.

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

subsequent steps.

8. Navigate to the Prime_Network_upgrade directory in the 3.10.0.1.0 directory you

created for installing the Service Patch:

cd 3.10.0.1.0/Prime_Network_upgrade

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

10. 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]

11. 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:

/export/home/3.10.0.1.0/PrimeNetworkBackup/PrimeNetworkBackUp_<unix_t

ime>.tar.gz

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

http://www.cisco.com/en/US/docs/net_mgmt/prime/network/3.10/administrator/guide/pn-image.html#wp1127799


- Removing content of /export/home/network310

[OK]

- Extracting backup archive under /export/home/network310

[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>

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

Do expect the following Error message:

+ Would you like to start Prime Network unit? (yes,no) [default yes]

Starting Prime Network unit...............................

**** Prime Network failed to start with the following error:

ERROR: unable to retreieve Golden source files, will not load.

14. Copy avm99.xml from Prime Network Gateway

~/Main/registry/ConfigurationFiles/<unit_ip> to the unit registry.

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

16. Log into all Cisco Prime Network Units as Prime Network user, for each unit , Delete

the necessary XMP_DATACENTER JAR and SDU files ,by entering the following

commands:

rm –fr $ANAHOME/Main/XMP_DATACENTER/xmp_inventory/xde-

home/lib/ext/vsphere_pal_handler-1.1.15.jar

rm –fr $ANAHOME/Main/XMP_DATACENTER/xmp_inventory/processed/ucs-

0.3.22-sdu.sdu

rm –rf $ANAHOME/Main/XMP_DATACENTER/xmp_inventory/dar/*

rm –rf $ANAHOME/Main/XMP_DATACENTER/xmp_inventory/xde-

home/packages/standard/logicalhost_vsphere-0.3.22.xar


home/packages/standard/logicalvirtualmachine_vsphere-0.3.22.xar


home/packages/standard/physicalresource_fabric-0.3.22.xar



home/packages/standard/physicalresource_ucs-0.3.22.xar

17. Log into the Cisco Prime Network gateway as Prime Network user

Navigate to 3.10.0.1.0/Prime_Network_upgrade/3.10.0_PP/

cd Build/lib/xmp/patches.

For each unit perform the following procedure:

scp vsphere_pal_handler-1.1.21.jar

<Unit_IP>:Main/XMP_DATACENTER/xmp_inventory/xde-

home/lib/ext/vsphere_pal_handler-1.1.21.jar

scp ucs-0.3.26-sdu.sdu

<Unit_IP>:Main/XMP_DATACENTER/xmp_inventory/dar/ucs-0.3.26-sdu.sdu

18. If you are using the HA/DR VERITAS solution, enable the Prime Network gateway

resource and mark it as critical in the VERITAS Cluster Manager application.


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


clusvcadm –U <Prime Network service> clusvcadm –U <Oracle service>

20. Use Cisco Prime Network Manage to reconnect the standby unit.

21. After the rollback to your original Cisco Prime Network 3.10 environment is complete,

reconfigure your user-defined crontabs.

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

($ANAHOME/prime_integrator/DMIntegrator.sh)


6 Verifying the Service Patch Uninstalling This procedure allows you to verify that the Service 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 Service 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_Network3.10.0.1.0_SP.jar file does not exist in any of the

JNLP files, enter the following command:

cat ~/Main/webstart/*.jnlp | grep Prime_Network3.10.0.1.0_SP.jar

The output should be empty.


find ~/Main/ -name Prime_Network3.10.0.1.0_SP.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_Network3.10.0.1.0_SP.jar


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

cat 11.out | grep Prime_Network3.10.0.1.0_SP.jar



7 Resolved Caveats – Cisco Prime Network 3.10.0.1.0 Service Patch.

The following caveats have been fixed in Cisco Prime Network 3.10.0.1.0 Service Patch.

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

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

Resolved Caveats - 3.10.0.1.0 Service Patch

Identifier Summary

CSCud07240 3.10 PP1 dummy patch because of wrong version compare

CSCuc74616 OSPF Neighbor Down service alarm stays not cleared indefinitely

CSCud11502 Link is not rediscover in card out-in scenario

CSCuc54022 BFD connectivity down alarm stays not cleared indefinitely

CSCud56602 OutOfMemory is immediatly received when the VNE starts.

CSCud21013 Patch Mechanism for VNE Drivers in 3.9

CSCud79675 Delivering XMP Collectors fixes to enable UCS VNE fix

CSCud44888 Add support for VPLS in CPT

CSCud88960 upgrade_build.pl - no need to pack XMP_DATACENTER folder

CSCud22506 Virtualization modeling taking too long time to modeling in VMDC scale

CSCud61567 Add/delete param to published CB script not reflected on execution panel

CSCuc96792 Reading from persistency causing AVM to crash due to memory consumption

CSCud88113 Static links are missing

CSCud97941 PN3.10: Failed to update Unit behind NAT

CSCud55430 Fault category for ACE syslog is not updated in Vision

CSCud80495 IllegalArgumentException in StringToMacAddressFormatter

CSCud29894 Corrupted telnet results when VNE switches to slow polling mode

CSCud59967 Stack overflow in AVM log

CSCud74402 Hardware detail report doesn't show subslot, fan & power modules info.

CSCub49124 Multiple instances of MPLS-TP tunnels in service map

CSCuc67095 ENS doesn't forward BT if the BT is on non ip-interface

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

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


















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




Identifier Summary

CSCud97831 Incompatible MLPPP information - encounters twin dc exception

CSCud87294 P-PN: Opening event properies getting Oid doesn't exist as user viewer

CSCud87427 P-PN: Running command builder with user viewer getting exception

CSCud87306 P-PN:trying open device details as user viewer getting Security Violatio

CSCud14155 Sub interfaces on Havoc Port missing in ANA310

CSCub86388 ExpeditePollingTest failed due to bug in ModuleData

CSCud57466 VNE Customization Builder should not show proxy sub type events

CSCub39406 Prime Network does not recognize NETWORK-3.9-K9 string

CSCue47081 Generic VNE has duplicate entries in the ip table under the routing enti

CSCuc81683 PN3.10- License report error (when PN as part of Prime central)

CSCue55208 3.10PP - Changes in build.xml

CSCue58220 upgrade.pl scripts compares dir name to current version and fails

CSCue59246 PN failed to update NSA version during running upgrade.pl

CSCue23974 Device Proxy devices ssh user not in command

CSCuc30410 PN checkPatchInstallation.pl...._pp.jar failed to read inner class

CSCud70595 collect_graph_counters.pl script misses AVM with 3+ GB memory on SunOS

CSCud93045 PN checkPatchInstallation script isn't find PP as first resourse in jnlp

CSCue82000 PN need to add validation in upgrade.pl verify if 3.10-PP1 is installed

CSCue76780 Some of the PIM neighbor loss syslog alarms are not cleared

CSCuf07526 LINEPROTO syslog recognized as generic when CDP is not enabled

CSCue97635 Soft Property Snmp Table is not optimized to handle large scale table

CSCtu14594 Unit servers at 100% cpu due to XBgpRouterIDAdvertiseMsg message flood

CSCuf23650 SNMP Table Soft Property is removed from polling

CSCuf77193 Out Of Memory does not print the stack trace

CSCuf77270 VNE EventManager is filling the log with data, potentially causing OOM

CSCuf41481 ASR903 VNE LSP role is not updated after lockout

CSCue15151 Add event rate limiter to protect against single source & type floods

CSCuf77169 NullPointerException while parsing %OSPF-5-ADJCHG syslog









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











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


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









Identifier Summary

CSCuf77651 NumberFormatException in RegistrationLoader should not be thrown.

CSCuf56502 G709 status down alram should be generated only when the status change

CSCuc53971 Multiple 'Not handled yet' registrations stuck forever

CSCud69004 Exception in Tl1Collector

CSCue06112 PW link is missing between CPT 600 devices

CSCue46668 PN - License keys using NETWORK-3-K9 and NETWORK-3-LAB-K9 do not

work

CSCuf90721 Card in ticket is not cleared due to some service alarms not cleared

CSCuf94075 ConcurrentModificationException in FilterAllOnUnreachableFilter class

CSCud87115 No limiter on persister exceptions dump

CSCuf52126 clear-n-remove card down alarm in NV removes ASR5K slot if status is out

CSCuf25895 ATM counter topology created high CPU on MWR VNE

CSCug22422 DC Model elements are not removed from the model

CSCub70196 ASR9K: MPLS-TP tunnel bandwidth showing as 0

CSCue04013 modifying VPN name on map is failing

CSCug20403 ASR903 EVNE - Duplicate card down after RSP multiple switchovers

CSCug48618 updatectl failed to stop update.pl process

CSCug43786 PN - Partially discovered VNE and no card-out/in - physical-command fail

CSCuc82722 Duplicate agentId (xid) created within the avmxxx.xml files

CSCtr94015 Enhancement:Need to support a new Product type as "Packet Microwave"

CSCug28039 Unit pow down causes GW to stop SSL conn with active unit after failover

CSCug19632 PW overlay for CPT devices not working - all NW elements are grayed out

CSCuc98377 PN-7600,A903,9K-PW link discov fail if LDP ID & Static signaling are set

CSCug23602 Issues in TL1 collector

CSCuf38701 L3VPN links missing in map

CSCug91673 telnet is disconnecting when post telnet command is wrong

CSCug48552 when all the subinterfaces under a bundle - no hypelink in cdp

CSCud21857 PN failed to export Command Builder using GSR12K

CSCug81310 EVC name unavailable in Pseudowire inventory












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







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












Identifier Summary

CSCug55889 integrity break loops method is not sending notification on root event

CSCug85781 Duplicate BFD connectivity down service alarms on LAG interfaces

CSCuh04196 CPT600: VNE fails to discover transceivers when device SW is upgraded

CSCuh08822 Device Unreachable ticket is not cleared for Partially Reachable ticket

CSCug78520 Missing Pluggable Port panel in the port properties window

CSCug92260 VCB subtype identification cannot have the dash character

CSCuh20651 Duplicate not cleared Port down tickets with LAG down

CSCuc68475 When you delete Aggregations map you get deadlock message on P.Vision

CSCuc70809 LinkSnapshot slow memory leak and many errors in the log

CSCug67749 command-builder script fails on 1st run on CPT device

CSCue90898 AutoArchiveAgent is getting into infinit loop and crashing AVM11

CSCuf57146 BQL routed through webpage has timeout

CSCue84452 NIO Telnet Collector looses data due to an unnecessary "reset" call.

CSCue36578 IOS: No physical command expedited on %OIR-6-INSCARD syslog

CSCuh05640 ClockService not supported for Context based VNE's

CSCuh50660 LAG Low priority member down ticket stays not cleared in card OIR test

CSCuh38821 VNE is becoming unreachable due to an infinite loop when doing a Get

CSCuh57715 Reports: Adding Serail number and SW version to the HW Detailed report

CSCug42988 MPLS-TP service: EP and MP are not being detected

CSCug76733 Command Builder not working under Managed Element for CPT VNE

CSCug87078 BQL commands are failed in a scale setup

CSCuh65205 Static topology does not work on DWDM

CSCuh65336 Unknown VNE driver & package info in VNE Properties panel

CSCud60792 Customized fields are not populated in ENS for non network events

CSCuh68215 MPLS TP LSP Type enum has to be changed to protect



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
























8 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)

CSCud79675 Delivering XMP Collectors fixes to enable UCS VNE fix

Prime Network 3.10.0.0.1

VNE 3.10.x DP1.0 (T.B.D)

CSCud44888 Add support for VPLS in CPT Prime Network 3.10.0.0.1

VNE 3.10.x DP1301 (CSCud44784)

CSCud97831 Incompatible MLPPP information - encounters twin dc exception


VNE 3.10.x DP1303 (CSCud47893)

CSCud14155 Sub interfaces on Havoc Port missing in ANA310


VNE 3.10.x DP1303 (CSCud19034)

CSCub70196 ASR9K: MPLS-TP tunnel bandwidth showing as 0


VNE 3.10.x DP0.0 (CSCub43770

CSCtr94015 Enhancement:Need to support a new Product type as "Packet Microwave"


T.B.D. (CSCty80395)

CSCug48552 when all the subinterfaces under a bundle - no hypelink in cdp


VNE 3.10.x DP1303 (CSCud97831)

CSCug81310 EVC name unavailable in Pseudowire inventory - Only for CPT devices


T.B.D. (CSCug88772)

CSCuh05640 ClockService not supported for Context based VNE's


T.B.D. (CSCuh80857)

CSCug76733 Command Builder not working under Managed Element for CPT VNE


VNE 3.10.x DP1305 (CSCug81940)


9 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

readme file for cisco prime network 3.10.0.1.0 service patch · from this patch on server patch...

Documents