Cisco Blog » The Platform

2015年8月1日星期六

Cisco Notification Alert -Prime - Cisco Prime Network-01-Aug-2015 16:54 GMT

 

 

 

 

 

 

 


Software Updates for Prime Network

Product Name:
Prime Network 4.2
Software Type:
Prime Network Patches
Release Version:
4.2.0.1.3
Alert Type:
New File
File Name:
Prime_Network4.2.0.1.3.zip
File Description:

Prime Network Service Patch 1 Point Patch 3

File Release Date:
13-JUL-2015
Find additional information in Software Downloads index.

Known Bugs - Prime Network

Bug Id:
CSCur75646
Title:
Exception when see comma in oid in property_value of notfication table
Description:

Symptom:
Network vision does not update tickets and PN does not forward events via NBI.

Conditions:
When the event location identifier (DiffObject) has a comma (,) char. E.g. {[ManagedElement(Key=PRAPS01-RMP01)][Trap(Di ffObject=Switch#1, PowerSupply 2)]}

Workaround:
Manually update the ?PROPERTY_VALUE? for these two entries:

Update notification set PROPERTY_VALUE = Y,321,{[ManagedElement(Key=PRAPS01-RMP01)][Trap(Di
ffObject=Switch#1 PowerSupply 2)]}' where PROPERTY_VALUE like '%{[ManagedElement(Key=PRAPS01-RMP01)][Trap(DiffObject=Switch#1%';

1. stop avm100 so that no network event to complicate the problem

2. complete each of the following update sql one at a time:

UPDATE TICKET PARTITION (NONARCHIVED) T SET ARCHIVED='Y' WHERE NOT EXISTS (SELECT 1 FROM NETWORKEVENT PARTITION(NONARCHIVED) N WHERE N.TICKETOID = T.OID) and rownum<1000;
UPDATE ALARM PARTITION (NONARCHIVED) A SET ARCHIVED='Y' WHERE NOT EXISTS (SELECT 1 FROM NETWORKEVENT PARTITION(NONARCHIVED) N WHERE N.ALARMOID = A.OID) and rownum<1000;
UPDATE TICKET PARTITION (NONARCHIVED) T SET ARCHIVED='Y' WHERE NOT EXISTS (SELECT 1 FROM ALARM PARTITION(NONARCHIVED) A WHERE A.OID = T.OID) and rownum<1000;
UPDATE NETWORKEVENT PARTITION (NONARCHIVED) N SET ARCHIVED='Y' WHERE NOT EXISTS (SELECT 1 FROM ALARM PARTITION(NONARCHIVED) A WHERE A.OID=N.ALARMOID) AND TICKETOID IS NOT NULL and rownum<1000;
UPDATE ALARM PARTITION(NONARCHIVED) A SET ARCHIVED='Y' WHERE NOT EXISTS (SELECT 1 FROM TICKET PARTITION (NONARCHIVED) T WHERE T.OID=A.TICKETOID) and rownum<1000;
UPDATE NETWORKEVENT PARTITION(NONARCHIVED) N SET ARCHIVED='Y' WHERE NOT EXISTS (SELECT 1 FROM TICKET PARTITION (NONARCHIVED) T WHERE T.OID=N.TICKETOID) AND TICKETOID IS NOT NULL and rownum<1000;

3. Do the following regularly to help to bring down the number of notification:

delete from cpnadmin.notification where NOTIFICATION_TYPE !='S' and rownum < 100000;

4. Let the notification count drop to close-to-zero value

5. Do the following becasue the notification query becomes very slow:

drop index NOTIFICATION_NOTIFICATIONID;
create index NOTIFICATION_NOTIFICATIONID on NOTIFICATION (NOTIFICATION_ID);
alter index NOTIFICATION_NOTIFICATIONID rebuild;

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
02-JUL-2015
Known Affected Releases:
3.11(0)PP4
Known Fixed Releases:
Bug Id:
CSCun89143
Title:
Unable to connect to CCM web after Upgrading from 4.0.0.1.2 PP to 4.1
Description:

Symptom:
Unable to launch CCM web after upgrading from 4.0.0.1.2 PP to 4.1

Conditions:
This issue occurs after upgrading Prime Network 4.0.0.1.2 PP to Prime Network 4.1

Workaround:
NA

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
15-JUL-2015
Known Affected Releases:
4.1(0.322), 4.2(2)
Known Fixed Releases:
Bug Id:
CSCus59176
Title:
Fan Tray displayed wrongly for ASR5500 17.1 device
Description:

Symptom:
ASR5500 17.1 inventory shows all identical fan tray modules

Conditions:
ASR5500 17.1 and up

Workaround:
none

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
15-JUL-2015
Known Affected Releases:
4.1(0)PP4
Known Fixed Releases:
4.1(0.1)PP1, 4.2(0.1)PP3
Bug Id:
CSCut53461
Title:
Protection delay mechanism for repetitive commands is not working
Description:

Symptom:
When VNE reflecting network event like port down or card down, which causes updates of physical and logical inventory, the Protocol Handler queues are overwhelmed with multiple duplicates of commands. This indicates that protection delay mechanism for commands is not working.

Conditions:
The VNE is reflecting significant network event like port down or card down, which causes updates of physical and logical inventory.

Workaround:
none

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
15-JUL-2015
Known Affected Releases:
4.2(0.1)PP1, 4.2(2)
Known Fixed Releases:
4.1(0.1)PP1, 4.2(0.1)PP2, 4.2(1.0)PP1
Bug Id:
CSCup00076
Title:
Install remains on step "Starting Web Server" and does not continue
Description:



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

Conditions:
Install RedHat 6.4
2. Install Prime Network 4.2 (build 2168)
3. The installation remains on the following step: "- Starting Web Server."

Workaround:

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
16-JUL-2015
Known Affected Releases:
4.0(0.1)PP4, 4.2(0.381), 4.2(1), 4.2(2)
Known Fixed Releases:
4.0(0.1)PP4, 4.1(0)PP1
Bug Id:
CSCui74089
Title:
4.0 PP1 install fails
Description:



Symptom:
PP1 install fails

Conditions:
+ Preparing for Prime Network Upgrade
- About to upgrade to a point patch version
- Writing log to /export/home/k240/Main/upgrade-1376983399.log
- Before continuing, please make sure that all the upgrade prerequisites have been met, as mentioned in the installation guide.
Do you have an updated backup of the database? (yes,no) [default yes] yes
- Checking connectivity to the database [OK]
- Checking connectivity to the units [OK]
- Verifying free space under /export/home/k240 [OK]
- Enter the password for the OS root user:

Workaround:

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
16-JUL-2015
Known Affected Releases:
4.0(0)PP1, 4.1, 4.2, 4.2(1), 4.2(2)
Known Fixed Releases:
Bug Id:
CSCuo35057
Title:
Lotem does not close gracefully SSH session at device response timeout
Description:

Symptom:
Lotem, the NIOTelnetCollector component, does not close gracefully SSH sessions to Dragonwave Compact devices when response timeout or other failure occurs. This cause the devices keep the 'dead' sessions until number of allowed sessions is maxed out. Then the communication with the device could not be established and VNE switches to Partially Reachable state.

Conditions:
SSH connection failure to Dragonwave Compact devices

Workaround:
Not known

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
16-JUL-2015
Known Affected Releases:
4.0(0.1)PP0
Known Fixed Releases:
Bug Id:
CSCus99853
Title:
ClassNotFoundException in released PN4.2 build
Description:

Symptom:
AVM process logs ClassNotFoundException errors due to missing message handle classes for TE tunnel topology. TE Tunnel topology is not discovered.

Conditions:
VNE model includes MplsTeTunnel DC

Workaround:
none

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
16-JUL-2015
Known Affected Releases:
4.2(0.1)PP0, 4.2(1)
Known Fixed Releases:
4.2(0.1)PP1, 4.2(2)
Bug Id:
CSCuv23846
Title:
Not able to create reports after upgrade has done
Description:



Symptom:
After PN 4.2.2 has done from Pn4.2.1, we are not able to create interactive reports.

getting below exception in logs:

Archive: ./UpgradeReports/otherFiles/pentaho-cdf.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of ./UpgradeReports/otherFiles/pentaho-cdf.zip or
./UpgradeReports/otherFiles/pentaho-cdf.zip.zip, and cannot find ./UpgradeReports/otherFiles/pentaho-cdf.zip.ZIP, period.
Copied successfully
Upgrade done successfully
Got response 200 ok

Conditions:
After PN 4.2.2 has done from Pn4.2.1.

Workaround:
Not Applicable

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.2(2.652)
Known Fixed Releases:
4.2(2)
Bug Id:
CSCut18150
Title:
MPLS-TP interface inventory details are not discovered for IOS-XR device
Description:



Symptom:
MPLS-TP interface inventory details are not discovered for IOS-XR device

Conditions:
1. Installed Prime Network 4.2 and added the device ASR9K using IPCore schema (MPLS-TP and XML Agent details are configured in the device).
2. Then found that MPLS-TP interface details are not discovered and it is found to be empty in TP enabled links tab

Workaround:
none

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.2, 4.2(0X)DP0.0.999, 4.2(0X)DP1501.0.541, 4.2(1)
Known Fixed Releases:
4.0DP1503, 4.1DP1503, 4.2(2), 4.2DP1503
Bug Id:
CSCut53201
Title:
Fan Tray duplicates displayed for ASR5K
Description:



Symptom:
Fan Tray duplicates displayed for ASR5K

Conditions:
If the point patch 4.2.0.1.1 is installed in PN 4.2 server then Fan module duplicates are displayed

If the patch is unisnstalled from server then all Fan Trays are displayed correctly.

Workaround:
none

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.2(1), 4.2(1)DP0.0.591
Known Fixed Releases:
4.2(2)
Bug Id:
CSCut36127
Title:
BfdCorrelationResolvingFlowMsg'es overwhelm VNE message queue
Description:

Symptom:
The VNE is not developing any trap, or syslog alarms although continue to be operational.

Conditions:
ASR9K with very intense configuration of various aggregations like MLPPP, LACP or VLAN.

Workaround:
none

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.0(0.1)PP6, 4.2(2)
Known Fixed Releases:
4.1(0.1)PP1, 4.2(0.1)PP2, 4.2(2)
Bug Id:
CSCuv13881
Title:
Power Supply module not displayed in device for ASR5K Device
Description:



Symptom:
Power Supply module not displayed in device for ASR5K Device

Conditions:
Version : 4.2.1

Steps:

Model ASR5K Device with 18.2 setup
Power modules are not displayed in PN

Expected Behavior:

Power modules should be displayed

Workaround:
Not Applicable

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.0(0X)DP1507.0.652, 4.1(0X)DP1507.0.652, 4.2(0X)DP1507.0.652, 4.2(1)DP1507.0.652, 4.2(2)DP0.0.652
Known Fixed Releases:
Bug Id:
CSCut47661
Title:
No AVM is getting generated after disable-enable the Auto AVM creation.
Description:



Symptom:
No AVM is getting generated after disable-enable the Auto AVM creation.

Conditions:
Step to reproduce :
1. Install build PN 4.2.2 build Image#162.
2. Select tools->Registry controller -> Automatic VNE Assignment.
3. Disable Automatic AVM creation & AVM size is 1000 MB
4. Select gateway server -> properties.
5. Configure "Reserved value for VNE"as 6000 MB.
6. No AVM is generated and this is correct behavior.
7. Now again Select tools->Registry controller -> Automatic VNE Assignment.
8. Enable Automatic AVM creation.

Expected :
After enabling the Automatic AVM creation AVM should auto-generate. Even after changing the AVM size to 2000 MB and Reserved value for VNE"as 5000 MB, no AVM is generated.

Workaround:
Not Applicable

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.2(2), 4.2(2.542)
Known Fixed Releases:
4.2(2)
Bug Id:
CSCut97230
Title:
Incoming and Outgoing labels should be swapped in ASR9k bgp label tabel
Description:



Symptom:
on asr9k device we can see received label and Local labels, Received labels means Outing label and Local Label mean Incoming label. however, In PN we are seeing Received labels has Incoming labels and Local labels has Outgoing labels , hence this 2 labels should be swapped on ASR9k devices.

Conditions:
1. Telnet to above asr9k devices, use the command "show bgp ipv4 unicast labels"
2. PN vision -> ASR9k 198/199 VNE -> routing entity -> Ipv4 BGL labels -> check for the incoming and outgoing labels

Workaround:
none

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
21-JUL-2015
Known Affected Releases:
4.2(2.601)
Known Fixed Releases:
4.2(2)
Bug Id:
CSCut87372
Title:
Nexus7K has missing containers and evil twin errors appear in AVM log
Description:

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

Conditions:
1. Model Nexus7K
2. Open VNE inventory

Workaround:
N/A

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
22-JUL-2015
Known Affected Releases:
4.0(0.1)PP6, 4.1(0)PP5, 4.2(0.1)PP2, 4.2(1.0)P1, 4.2(2.622)
Known Fixed Releases:
4.1(0.1)PP1, 4.2(1.0)PP1, 4.2(2)
Bug Id:
CSCup21269
Title:
Collector agent is suspended when a Command Script is executing
Description:

Symptom:
No apparent symptoms in the GUI, all telnet command script timeout with no new provisioning event in the Event Vision/provisioning tab being added.

Conditions:
A command script freezes while executing.

Workaround:
No workaround.

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
23-JUL-2015
Known Affected Releases:
4.0(0.1)PP4
Known Fixed Releases:
4.0(0.1)PP4, 4.2(0.1)PP2
Bug Id:
CSCuv44165
Title:
PN see QVPC device as Generic Compute Server
Description:

Symptom:
PN see QVPC device as Generic Compute Server, so the device is not modeled well

Conditions:
1. Model ASR5K QVPC device

Workaround:

Further Problem Description:

Status:
Open
Severity:
2 Severe
Last Modified:
24-JUL-2015
Known Affected Releases:
4.1(0.999)
Known Fixed Releases:
Bug Id:
CSCuu41148
Title:
PW link is not showing in GUI
Description:



Symptom:
PW link is not showing in GUI

Conditions:
1.) Model two 7600 device
2.) configure pseudowire on this device
3.) Check for the PW link between the devices

Workaround:
N/A

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
27-JUL-2015
Known Affected Releases:
4.2(1.0)PP1, 4.2(2.611)
Known Fixed Releases:
4.2(1.0)PP1
Bug Id:
CSCuu76624
Title:
CFD: ASR9xx is using a depracated oid for cpu
Description:

Symptom:
PN will detect high cpu on device although there is no high cpu

Conditions:
asr9xx

Workaround:
none

Further Problem Description:

Status:
Fixed
Severity:
2 Severe
Last Modified:
29-JUL-2015
Known Affected Releases:
4.2(0X)DP1505.0.622, 4.2(1)DP1505.0.622
Known Fixed Releases:
4.2(2)
Bug Id:
CSCuu45704
Title:
Image Activation Fails with " image not present on Device"
Description:



Symptom:
Image Activation Fails with " image not present on Device"

Conditions:
While performing 9k Benchmarking for Activation operation, the Activation jobs are failing with " image not present on the Device, even though the image is present on the Device bootflash"

Steps :
1) )Install PN 4.2.1
2)Launch CCM Application with url 'https://172.18.79.14:8043/ccmweb/'
3)Schedule 4 Activation Jobs with 2250 Devices each.
4) Schedule the job with IOS by Image Flow, select image :Image asr1000rp1-adventerprisek9.03.09.01.S.153-2.S1.bin.
5) Verify the results.

Workaround:
When the Failed Device is scheduled for activation individually it is passing successfully.

Further Problem Description:



(release notes added by addprefcs-org.ksh)

Status:
Fixed
Severity:
2 Severe
Last Modified:
29-JUL-2015
Known Affected Releases:
4.2(2), 4.2(2.612)
Known Fixed Releases:
4.2(2)
Bug Id:
CSCuu84049
Title:
NCS6K: There is no association between CPAK modules and ports
Description:

Symptom:
Multiple issues related to association of Layer1 ports to CPAK pluggable modules (Layer0). The hierarchy of layer0 and layer1 components is broken and needs to be refactored.

Conditions:
Modeling of CPAK pluggable ports and "slicing" of HundredGE interfaces.

Workaround:
none

Further Problem Description:
Wrong design of the Ethernet interface "slicing"; it must be changed to comply and reuse existing VNE framework.

Status:
Fixed
Severity:
2 Severe
Last Modified:
30-JUL-2015
Known Affected Releases:
4.2(0X)DP1505.0.622
Known Fixed Releases:

Find additional information in Bug Search index.

 

2013 Cisco and/or its affiliates. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks

 

没有评论:

发表评论