| |
|
Alert Type: | Updated * |
Bug Id: | CSCus75228 | Title: | ASR9kv linear - Interface status down service alarm isn't cleared |
|
Status: * | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
In ASR9kv cascading single hos (linear)
Interface status down service alarm isn't cleared after taking out and in mod80 card (Card in/out)
Conditions:
1. Model ASR9kv device
2. Take out mod 80 card
3. Interface status down service alarm will occur
4. Insert back mod 80 card
5. Interface status down service alarm won't clear
Workaround:
Further Problem Description:
|
|
Last Modified: | 04-AUG-2015 |
|
Known Affected Releases: | 4.2(0)PP999 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv65197 | Title: | PW-Ether is not updated after port down and IP interface alarm not corre |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
PW-Ether is not updated after port down and IP interface alarm not correlated to "Layer 2 tunnel down"
Conditions:
1. Model 2 ASR9K
2. Shutdown physical ports so PW will go down
3. "Interface status down" alarm of PW-Ether not correlated to "Layer 2 Tunnel down" alarm
4. PW-Eth status not updated in VNE inventory (poll now solve the issue)
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw02122 | Title: | Nexus7K power cefc FRU removed/cefc power status trap has wrong location |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Nexus7K power "cefc FRU removed"/"cefc power status down" trap has wrong location.
The location of the POWER is Nexus2K FAN tray
Conditions:
1. Model Nexus7K
2. Power out Power supply
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 31-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1507.0.671 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv60898 | Title: | FEC-129:Naming of FEC-129 pw in EVC & pw discovery shd be end to end |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
The naming of the merged FEC-129 EVC of all types show only the IP address of one peer
Conditions:
Drop down an end to end EVC. From Add to Map->Virtual Connections -> Check the naming of the EVC.
Workaround:
Further Problem Description:
(release notes added by addprefcs-org.ksh)
|
|
Last Modified: | 28-AUG-2015 |
|
Known Affected Releases: * | 4.2(2.0)PP1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu86526 | Title: | Part of Nexus7K port down alarms not cleaned |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Part of Nexus7K port down alarms not cleaned.
This happen because part of "Interface Ethernet x/x part of vnd X is down/up" Nexus7K syslogs appear with Default context and not parsed but the belong to other context.
Conditions:
1. Model Nexus7K
2. Card out (ex: Card 3)
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 27-AUG-2015 |
|
Known Affected Releases: * | 4.1(0X)DP1505.0.622, 4.2(0X)DP1507.0.671, 4.2(1), 4.2(1)DP1505.0.622, 4.2(2) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv40300 | Title: * | Port down/Link down ticket is not cleaned after Nexus7K reload |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Port down ticket is not cleaned after Nexus7K reload.
In Invtenory the port status is "OK" but the ticket stay down.
This is not GUI update issue because the ticket stay the same after map close/open
Conditions:
1. Model Nexus7K
2. reload device
Workaround:
Further Problem Description:
|
|
Last Modified: | 27-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv93253 | Title: | FEC-129 PWs discovered in PN422 display as disabled /inactive on upgrade |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Encountered for the following installation order:
Install PN 4.2.2 FCS build > Model VNEs > Select FEC 129 pseudowires and associated components (bridges) from the respective discovery plugins such as bridge domain, VPLS, pseudowire and EVC > Install DP > Install PP.
Conditions:
Install Pn422 and model VNES -> all the FEC-129psuedowires discovered in various plugins which display as active , become inactive or disabled on upgrading to PP
Workaround:
Delete all the maps that were created before the installation of the PP so that the disabled or inactive components do not display.
Also on manually selecting the FEC-129 pws components again from PW ,VPLS and EVC discovery , the accurate discovery of FEC-129 PW can be seen.
Further Problem Description:
|
|
Last Modified: | 25-AUG-2015 |
|
Known Affected Releases: | 4.2(2)DP1508.0.671 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu60574 | Title: | CCM IOS-XR Image distribution Job is not added in Job page |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Schedule a Image distribution job in Prime network and it is not shown in Image job page.
Conditions:
Primary Product: Prime Network CCM
Component: Prime Network CCM Issues
Version: 4.1(0)
Patch Level: 4.1.0.1.0
Device type : IOS-XR
Workaround:
None, this is fixed in Prime network 4.2.
Further Problem Description:
none
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP1 |
|
Known Fixed Releases: * | 4.1(0.1)PP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu42479 | Title: | Missing ingress/egress policies setting for IP interfaces |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When open up a physical interface in with sub-interfaces (also IP interfaces) configured with policy in Network Vision , the columns ingress and egress are empty.
Conditions:
ASR9K device or any IOX device. Sub interfaces are configured with egress/ingress
Workaround:
N.A.
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.2(0.1)PP0 |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3, 4.2(1.0)PP1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut92020 | Title: | Sometimes ITicket notification missing flagging alarm state and severity |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Missing or misunderstood major functionality of Fault Management System
Symptom:
Sometimes ENS fails to receive notification of type ITicket with flagging (root cause) alarm state and severity and has clearing event state and severity.
Conditions:
Racing conditions in Notification Agent, when by the time the ITiket notification is processed the ticket has been already cleared.
Workaround:
none
Further Problem Description:
The defect creates false impression that tickets sometimes are not cleared in Netcool when ticket update notifications are filtered out. In fact, none of the tickets should be cleared with this kind of ENS and Netcool probe configuration, because new tickets should always have flagging alarm state and severity.
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 3.11(0)PP4, 4.2(0.1)PP1 |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3, 4.2(1.0)PP1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq82743 | Title: | PN: NCCM fail after ~30 min after activation fail due to lack of disk sp |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
NCCM fail after ~30 min after activation fail due to lack of disk space.
The job should fail immediately after he discover that there is lack of disk space and not after ~30 minutes.
I
Conditions:
1. Model ASR903 with ISSU
2. Open NCCM web page.
3. Activate an image when stby-bootflash has missing disk space
4. Wait for activation be failed
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.0(0.1)PP5 |
|
Known Fixed Releases: * | 4.1(0.1)PP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu88970 | Title: | VPN IPv6 links are not ignored when ignoreVrfLinks is true in registry |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
* AVM 11 crashes because heap is too small
* plugin manager indicates IPv6 link are present, even after requesting VPN links be ignored.
Conditions:
* have IPv4 and IPv6 links between devices modeled in the PN
* setup registry to disable VPN links and unneeded plugins then restart gateway
runRegTool.sh -gs localhost set 0.0.0.0 site/plugin/VpnPlugin/enable false
runRegTool.sh -gs localhost set 0.0.0.0 site/plugin/VrfSnapshotProviderPlugin/enable false
runRegTool.sh -gs localhost set 0.0.0.0 site/plugin/ServiceLinkDiscoveryPlugin/enable false
runRegTool.sh -gs localhost set 0.0.0.0 site/mmvm/services/plugin/LinkSnapshotProviderPlugin/ignoreVrfLinks true
networkctl restart
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.2(0.522) |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut30141 | Title: | CCM The device is not under the scope of the user to perform operation |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Configuration backup failed for the few devices.
Conditions:
When group of devices performing backup operation
Workaround:
Manually perform backup operation from CCM for the failed device(s).
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 3.11(0.999), 4.1, 4.2, 4.2(1), 4.2(2) |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3, 4.2(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu89131 | Title: | Missing OSPF v2 interfaces in NV if configured with IPV6 addr also. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
If OSPF interfaces with same Process ID but are configured with both IPV4 and IPV6 addresses, then the interfaces will not show up in OSPF Processes V2 logical inventory, but the same interfaces will show up in OSPF Processes V3 logical inventory.
Conditions:
OSPF interfaces with same Process ID but are configured with both IPV4 and IPV6 addresses
Workaround:
N.A.
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.2(0.1)PP3 |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv14567 | Title: | CCM restore fails when banner has empty newline spaces in it |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Configuration restore fails
Conditions:
Configuration has banner with empty new line spaces in them.
Workaround:
Remove the empty new line spaces for restore to work.
Further Problem Description:
CSCuv48919 exits on the device
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.2(1), 4.2(1.592), 4.2(2) |
|
Known Fixed Releases: * | 4.1(0.1)PP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu27480 | Title: | NCCM - config restoration fail in device banner on 6500 device series |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Configuration restore on 6500 device fails when banner exist
Conditions:
Restore config with multi banner config on 6500 as below
!
privilege exec level 6 show running-config
privilege exec level 6 copy
banner incoming ^Cmytet^C
banner login ^Ctest^C
banner motd ^C Cisco Systems, NMTG ^C
!
Workaround:
Edit the backup configuration manually and re-enter the same config and restore the edited configuration
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP0 |
|
Known Fixed Releases: * | 4.1(0.1)PP1, 4.1(0.1)PP2, 4.2(1.0)PP1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu22911 | Title: | Frame Relay Traffic profiles are missing from logical inventory |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Frame Relay Traffic profiles are missing from logical inventory
Conditions:
When the values of frCircuitTable has the same values across multiple instances.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1, 4.1(0.999), 4.2, 4.2(1) |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3, 4.2(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv43004 | Title: | command builder script window hangs or has errors in log |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
symptoms vary: more severe symptoms are rare
1) errors in the log:
2) command builder execute window hangs
3) GUI BQL connection disconnects from server
4) GUI crashes
Conditions:
* Run any command builder script that will require window to be resized
* command is run over and over until the issue is manifest
Workaround:
for show commands ( commands do not change device)
* close the script execute window, if window hangs 30s for short commands; 2min for long commands
* reopen the script execute window
* try running command again
for configuration commands
* close the window the same as for show commands
* but additionally before reopening window to try again...
-verify the command was run and succeeded, a show command can be run that shows the changed configuration.
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1(0.342) |
|
Known Fixed Releases: * | 4.1(0.1)PP2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu11665 | Title: | PN - patch install script fails with Pentaho installed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Patch install script does not complete when trying to start Pentaho reports (ctlscript.sh)
Conditions:
Pentaho installed before Patch is installed
Workaround:
Abort the script and start pentaho manually along with prime network integration layer.
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP1, 4.2(0.1)PP2 |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3, 4.2(1.0)PP1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu62951 | Title: | Error editing Compliance audit job with device filter and select-all |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Job does the audit for ENTIRE INVENTORY
Conditions:
Edit of Compliance audit job to run for few devices, using the device selection filter to filter out few devices and using the select-all option(and not individually selecting devices).
Workaround:
Scheduling another job and not editing the existing ones is an option.
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.2(1.0)PP1 |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur99687 | Title: | PN - AVM log errors ImoTranslator.translate on VNE restart |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
AVM log file contains multiple instances of the following error: ImoTranslator.translate - MiniAps:: IP: x.x.x.x Required property vendor from interface com.sheer.imo.IPhysicalLayer has no property translator, either the required property was mis-spelled, or misplaced or the property translator is MIA
Conditions:
Occurs when VNE is restarted/loading. Observed on ASR903
Workaround:
None
Further Problem Description:
(release notes added by addprefcs-org.ksh)
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.0(0)PP999, 4.2(1.0)PP1, 4.2(2) |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(0.1)PP3 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv65371 | Title: | ASR9K VNE: ClassCastException in ExecuteCommandFromIpInterfaceDc |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
While ASR9K VNE parses link down syslog or trap, it expedites Logical Investigator registrations 'satellite' and 'satellite-connection'. But ExecuteCommandFromIpInterfaceDc fails to execute registrations due to ClassCastException errors. As a result the satellite inventory is not updated properly.
Conditions:
Satellite topology of the node, usually ASR9K VNE
Workaround:
Not available
Further Problem Description:
|
|
Last Modified: | 17-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1505.0.622, 4.2(1)DP1507.0.663 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu41883 | Title: | PN - VNE does not pick up the latest DP on restart |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
VNEs are not pickup up and running with the latest DP following creation or restart.
Conditions:
Prime Network installation with DP0, DP1501 and DP1503
Workaround:
Specifically configure VNE to use DP1503 instead of "latest"
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: * | 4.1(0.1)PP1, 4.1(0.1)PP2, 4.2(0.1)PP4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv75454 | Title: | Compliance Audit policy does not get restored after upgrading to 4.2.2 |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
Compliance Audit policy does not get restored after upgrading to 4.2.2
Conditions:
1. Instal 4.1.0.1.2
2. Configure a compliance audit with compliance policy and policy profile .
3. Follow the 4.2.2 ,install guide and upgrade from 4.1.0.1.2 to 4.2.2 .
4. After upgrade has been completed , Check the Compliance audit , policy and profile got restored .
Workaround:
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: | 4.2(2)DP0.0.653 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv77939 | Title: | QVPC standby card status appear as Major and should appear as OK |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
QVPC standby card status appear as Major and should appear as OK, because standby not indicate an issue
Conditions:
1. Model QVPC device with standby card
2. Look on Standby card status in VNE physical inventory
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1507.0.671 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv61871 | Title: | PN - geo HA install fails due special char in password |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Geo HA install fails when deploying to DR location
Conditions:
* geo HA install
* have special char ! or # in password
Workaround:
do not use ! or # in the password.
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: | 4.2(2.662) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu44023 | Title: * | Pluggable CPAK Optics should be displayed as sub modules under CPAK card |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Pluggable CPAK Optics should be displayed as sub modules
Conditions:
Pluggable CPAK Optics should be displayed as sub modules under Tomahawk CPAK cards
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 31-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1505.0.621, 4.2(1) |
|
Known Fixed Releases: | 4.2(2) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv65193 | Title: | PW-Ether is not updated after port down and IP interface alarm not corre |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
PW-Ether is not updated after port down and IP interface alarm not correlated to "Layer 2 tunnel down"
Conditions:
1. Model 2 ASR9K
2. Shutdown physical ports so PW will go down
3. "Interface status down" alarm of PW-Ether not correlated to "Layer 2 Tunnel down" alarm
4. PW-Eth status not updated in VNE inventory (poll now solve the issue)
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv54487 | Title: | P-PN:CCM image activation job stuck in running state |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
NCCM activation MWR device the job state remaining in running state for long time
Conditions:
CCM image activation of MWR or another device job state stuck and user don't know if upgrading done or not
Workaround:
restart the vne or the avm will cause this state to release
Further Problem Description:
|
|
Last Modified: | 19-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv68300 | Title: | ASR9912 VNE fails update TenGigE IP interface status on demand |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
When ASR9K VNE expedites 'ip interface oper status' registration for IPInterface DC created for TenGigE interfaces or sub-interfaces, the device fails respond due to wrong CLI command.
Conditions:
Configuration of IP addresses on TenGigE interfaces or sub-interfaces
Workaround:
Not available
Further Problem Description:
Root cause: wrong DC instrumentation for 'telnetString' key.
|
|
Last Modified: | 20-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1505.0.622 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv54295 | Title: | P-PN: ATM port properties model inconsistent between MWR to ASR903 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
missing information for MWR regarding ATM properties
Conditions:
Model ASR903 and MWR that attach and you will see different in port properties
Workaround:
Further Problem Description:
|
|
Last Modified: | 20-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv56763 | Title: | SNMP Link down trap location is not parsed for Nexus1K |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
SNMP Link down trap location is not parsed for Nexus1K
Conditions:
1. Model Nexus1K
2. Shutdown port-channel
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 20-AUG-2015 |
|
Known Affected Releases: | 4.1(0X)DP1505.0.622 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu91315 | Title: | CiscoNexusRoutingParser not parse specific ipv4 and ipv6 route entries |
|
Status: * | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Missing IPv4 and IPv6 routing entries in non-default context
Conditions:
DP 1505
PN 4.2 SP1 PP1
Device: Nexus 7010
Workaround:
N.A.
Further Problem Description:
|
|
Last Modified: | 20-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1505.0.622 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv87419 | Title: | NCCM return failure on QVPC configuration restore but it success |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
NCCM return failure on QVPC configuration restore but it success
Conditions:
1. Model QVPC
2. Restore configuration via NCCM
Workaround:
Further Problem Description:
|
|
Last Modified: | 21-AUG-2015 |
|
Known Affected Releases: | 4.2(0.1)PP4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv87006 | Title: | Unable to backup QVPC using sftp |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unable to backup QVPC using sftp.
The error is not clear when backup QVPC using sftp.
In AVM log it is written that backup using SFTP is not supported but it is not understood from NCCM GUI error
Conditions:
1. Model QVPC device
2. backup QVPC via NCCM using SFTP
Workaround:
Further Problem Description:
|
|
Last Modified: | 21-AUG-2015 |
|
Known Affected Releases: | 4.2(0.1)PP4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut97716 | Title: * | Nexus5/7 ipv6 loopback is not presented in VNE IP Interfaces in the in |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Nexus5K/7K ipv6 loopback is not presented in VNE IP Interfaces in the inventory.
Stop VNE -> Delete Persistency -> start VNE also not solve the issue
Conditions:
1. Model Nexus5K with IPv6 loopback interface
2. Open VNE inventory
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1503.0.581 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur83563 | Title: | ISIS information in IOS XR is showing wrong data. |
|
Status: * | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
IPv4 Metric in ISIS information is showing wrong data.
Conditions:
On all IOS XR configured with ISIS.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 24-AUG-2015 |
|
Known Affected Releases: * | 4.1, 4.1(0.999), 4.2, 4.2(0.1)PP4, 4.2(1) |
|
Known Fixed Releases: | 4.2(2) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv91075 | Title: | Nexus1K last IPv6 loopback interface not displayed |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Nexus1K last IPv6 loopback interface not displayed
Conditions:
1. Model Nexus1K with several ipv6 loopback interfaces
2. Open VNE inventory -> Routing Entities ->Routing Entity
Workaround:
Further Problem Description:
|
|
Last Modified: | 25-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1507.0.671 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv27509 | Title: | All Nexus VNEs missing 'ip interface oper status' registration |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
During VSM card switchover on Nexus device it was noticed that previously raised alarm 'Interface status down' for mgmt interface is not cleared.
Conditions:
Change in IP interface status on any of the IP interfaces configured on Nexus device including mgmt interface.
Workaround:
Manual registry change.
Further Problem Description:
|
|
Last Modified: | 25-AUG-2015 |
|
Known Affected Releases: * | 4.2(0X)DP1507.0.671 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv91062 | Title: | CAT 4948E is not getting modeled as there is no loader |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
no physical for catalyst 49xx
Conditions:
none
Workaround:
none
Further Problem Description:
loader is not identified
|
|
Last Modified: | 25-AUG-2015 |
|
Known Affected Releases: | 4.2(0X)DP1507.0.663 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus37729 | Title: * | Unable to backup NEXUS7K configuration/Dis via SFTP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unable to backup NEXUS7K configuration via SFTP.
NCCM try using this command
sftp -o UserKnownHostsFile=/dev/null -oPort=management admin@10.56.22.56
"management" should be replaced with a port number
Conditions:
1. Model Nexus7K
2. Backup Nexus7K configuration using NCCM via SFTP
Workaround:
Backup configuration via TFTP
Further Problem Description:
|
|
Last Modified: | 25-AUG-2015 |
|
Known Affected Releases: | 4.1(0)PP4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv90200 | Title: | Pathtracer: Sometimes Layer 2 information is not displayed in results |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
When found path trace goes over DWDM DC the Layer 2 properties are not displayed in the Pathtracer results.
Conditions:
Path trace goes over DWDM DC.
Workaround:
There is no workaround for this issue.
Further Problem Description:
|
|
Last Modified: | 22-AUG-2015 |
|
Known Affected Releases: | 4.2(0.1)PP4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw01245 | Title: | VNE status does not reflect disabled reachability tracking command |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
When tracking reachability command is disabled from Registry Controller the VNE status GUI continue showing previous protocol reachability state.
Conditions:
Disabling protocol reachability tracking while VNE is running.
Workaround:
Restart VNE.
Further Problem Description:
|
|
Last Modified: | 29-AUG-2015 |
|
Known Affected Releases: | 4.2(2.0)PP1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu16533 | Title: | PN: upgrade.pl died - mySQL stop timed-out restart aborted |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Errrors seen:
- Restarting databases
Restarting embedded Oracle database [OK]
Restarting MySQL database [FAIL]
Died at upgrade.pl line 3075.
log indicates start not attempted because mqSQL DB did not stop.
Conditions:
Conditions:
* prime network in HA mode, with infobright install
* version 4.1.0.0.3
* upgrading to 4.1.0.1.0
Workaround:
restart infobirght, ensure PN, and Oracle are also running. try again.
if it still fails, code changes will be needed.
Further Problem Description:
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP0, 4.2(0)PP999, 4.2(2.999) |
|
Known Fixed Releases: * | 4.1(0.1)PP1, 4.1(0.1)PP2, 4.2(0.1)PP3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv35430 | Title: | CCM: log message appears on the sftp result while distributing. |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Some unnecessary info on the result window when distributing image with sftp.
Conditions:
while distributing image with sftp using CCM.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 28-AUG-2015 |
|
Known Affected Releases: | 4.2(1)DP1505.0.622 |
|
Known Fixed Releases: * | 4.2(2)DP1508 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu35122 | Title: | Environmental trap ticket is not cleared in the Network Vision |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
When power supply unit on 6500VSS switch was turned off and on, it was noticed that Power supply - Normal ticket created by environmental trap stays not cleared in the Network Vision - root alarm cleared, but overall ticket is not cleared. At the same time the ticket gets cleared in Event Vision and Prime Central.
Conditions:
Processing of environmental traps, possibly any notification that creates events with unique identifier.
Workaround:
Reload map in NV.
Further Problem Description:
Possible root cause is missing ISeverityAspect notification, which changes ticket severity in the NV.
|
|
Last Modified: | 09-AUG-2015 |
|
Known Affected Releases: | 4.1(0.1)PP2 |
|
Known Fixed Releases: * | 4.1(0.1)PP2, 4.2(1.0)PP1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtn20223 | Title: | Embedded Oracle is not suporting SSL |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
SSL is not supported, therefore all information is sent in the clear and could be observed by a third party.
Conditions:
None
Workaround:
None
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are
4.3/3.9:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=&version=2.0
dispatch=1&version=2&vector=AV:N/AC:M/Au:N/C:P/I:N/A:N/E:POC/RL:U/RC:C
No CVE ID has been assigned to this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 06-AUG-2015 |
|
Known Affected Releases: | 3.7(3.999) |
|
Known Fixed Releases: | |
|
|
| |
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论