| |
|
Alert Type: | Updated * |
Bug Id: | CSCut38855 | Title: | n5k DR does not register S,G when acting as first hop router |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
a n5k acting as first hop router running 7.1(0)N1.1 will not generate PIM register messages.
Conditions:
Workaround:
no workaround known at this time
Further Problem Description:
|
|
Last Modified: | 20-NOV-2015 |
|
Known Affected Releases: | 7.1(0)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.640), 7.1(3)N1(1), 7.1(3)ZN(0.48), 7.2(2)N1(1), 7.3(0)N1(0.144), 7.3(0)N1(1), 7.3(0)ZN(0.132) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut99511 | Title: | BFD flaps with the 50 ms default timer |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ISIS-BFD randomly flapping with the 50ms default timer.
Conditions:
Using default bfd timer.
Workaround:
Increase the BFD timer to 250 ms
Further Problem Description:
|
|
Last Modified: | 20-NOV-2015 |
|
Known Affected Releases: | 7.0(6)N1(0.7), 7.1(0)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.623), 7.1(3)N1(1), 7.1(3)ZN(0.30), 7.2(2)ZN(0.13), 7.3(0)BZN(0.41), 7.3(0)N1(0.77), 7.3(0)N1(1), 7.3(0)ZN(0.75) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw92095 | Title: | NXAPI: json "show monitor session" destination interfaces incomplete |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
some destination interfaces are missing from JSON format output of the "show monitor session" command in the NXAPI Sandbox
Conditions:
Workaround:
Request the response in XML format.
Further Problem Description:
|
|
Last Modified: | 14-NOV-2015 |
|
Known Affected Releases: | 7.2(0)N1(1), 7.2(1)N1(0.9) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus68591 | Title: | Assess Nexus 5k for GHOST vulnerability (CVE-2015-0235) |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:
The following Cisco Nexus products:
Nexus 5624 Switch
Nexus 5696 Switch
Nexus 5672 Switch
Nexus 56128 Switch
Nexus 5596T switch
Nexus 5596UP switch
Nexus 5548UP switch
Nexus 5548P switch
Nexus 2348UPQ FEX
Nexus 2348TQ FEX
Nexus 2248PQ FEX
Nexus 2232TM-E FEX
Nexus 2232TM FEX
Nexus 2232PP FEX
Nexus 2248TP-E FEX
Nexus 2248TP FEX
Nexus 2224TP FEX
Nexus 2148T FEX
Nexus B22 DELL FEX
Nexus B22 Fujitsu FEX
Nexus B22 HP FEX
Nexus B22 IBM FEX
include a version of glibc that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) ID:
CVE-2015-0235
This bug was opened to assess and address the potential impact on this product.
Conditions:
Device with default configuration.
Workaround:
None.
More Info:
All previously released versions of NX-OS software are affected. The fix will be delivered for currently supported releases as follows:
5.2(1)N1(9)
6.0(2)N2(7)
7.0(6)N1(1)
7.1(1)N1(1)
7.2(0)N1(1)
Additional details about the vulnerabilities listed above can be found at http://cve.mitre.org/cve/cve.html
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: 10/7.8
https://intellishield.cisco.com/security/alertmanager/cvssCalculator.do?dispatch=1&version=2&vector=AV:N/AC:L/Au:N/C:C/I:C/A:C/E:F/RL:OF/RC:C/CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND
The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product.
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: | 30-NOV-2015 |
|
Known Affected Releases: | 5.1(3)N2(1), 6.0(2)N2(1) |
|
Known Fixed Releases: * | 5.2(1)N1(8.153), 5.2(1)N1(8.161), 5.2(1)N1(8.168), 5.2(1)N1(9), 6.0(2)N2(6.127), 6.0(2)N2(6.136), 6.0(2)N2(6.142), 6.0(2)N2(7), 7.0(1)ZN(0.745), 7.0(1)ZN(0.778) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup75270 | Title: | FC interfaces are not listed in IF-MIB snmp walk |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
FC interfaces are not listed in IF-MIB snmp walk.
Device Manager is not working correctly with the Nexus 5548UP or 5596UP (GEM modules installed) when the expansion module ports are set to fibre channel mode.
Hovering over the ports with the mouse in Device Manager will display for example, "Ethernet 1/17 Status: failed".
Looking at the same ports via CLI will show that the ports are really in FC mode and not configured as Ethernet ports.
Conditions:
Nexus 5548UP or Nexus 5596UP running NX-OS 7.0(2)N1(1) with GEM Expansion module ports configured to operate in Fibre Channel mode
Some ports are in Fibre Channel mode on the base chassis.
Workaround:
1) Use DCNM-SAN instead of Device Manager.
2) refer to bug CSCut82544:
Upgrade to NX-OS 7.2(1)N1(1)
Further Problem Description:
NX-OS 7.0(1)N1(1) and all previous software versions are not affected by this defect.
This is an NX-OS bug, not a Device Manager bug.
|
|
Last Modified: | 15-NOV-2015 |
|
Known Affected Releases: | 7.0(2)N1(1), 7.0(3)N1(0.109), 7.0(3)N1(0.122), 7.1(0)N1(0.241) |
|
Known Fixed Releases: | 7.0(1)ZN(0.677), 7.0(6)N1(0.186), 7.0(6)N1(1), 7.1(0)N1(0.386), 7.1(0)N1(1), 7.1(0)ZN(0.459), 7.1(1)N1(0.17), 7.1(1)N1(1), 7.2(0)N1(1), 7.2(0)ZN(0.91) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw73332 | Title: | VTPv3 mode changes from client to transparent after PVLAN creation |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
VTPv3 mode changes from client to transparent:
2015 Oct 14 17:27:22 Nexus5500 %VTP-2-VTP_MODE_TRANSPARENT_CREATE_SEQ_FAILED: VTP Mode changed to transparent since VTP vlan create/update failed.
Conditions:
VTPv3 Primary Server is configured on Catalyst 4900M switch.
Nexus switches have at least one port with the following configuration:
* switchport mode private-vlan trunk promiscuous
* switchport private-vlan trunk allowed vlan A,B-C,D
* switchport private-vlan mapping trunk X Y-Z
Workaround:
None at the moment.
Further Problem Description:
After the PVLAN is added on the VTPv3 Primary Server, we can see that PVLAN resources are locked on the Nexus 5500 switches until eventually there is a timeout and the VTPv3 mode changes from client to transparent.
Nexus5500# show system internal private-vlan info
System info:
------------
Global LOCKED
Private VLANs
------------
private-vlan 1:1800 vlan-type is "unknown(8)" LOCKED primary=0, otxns=1
state: PVLAN_VLAN_STATE_NORMAL_TO_PRIMARY_VLAN_MGR
associations(0):
|
|
Last Modified: | 25-NOV-2015 |
|
Known Affected Releases: | 7.2(0)N1(1) |
|
Known Fixed Releases: * | 7.3(0)N1(0.219), 7.3(0)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu73687 | Title: | N5k AAA process crash during during accounting |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
AAA feature ON and leave setup for 3-4 days.
when accounting logs reaches threshold and is being archived due to a corner case issue aaa process reloads of the switch.
Conditions:
System kept idle with accounting enabled for 3-4 days and the accounting logs size reaches threshold and in parallel there is some show accounting logs done, this issue can happen.
Workaround:
There are no specific workarounds as this is not 100% re-producible .
Some options: User can try to clear accounting logs in case it has reached a threshold set.
Further Problem Description:
|
|
Last Modified: | 18-NOV-2015 |
|
Known Affected Releases: | 7.0(3)N1(0.28), 7.1(2)N1(0.528), 7.2(1)N1(0.5) |
|
Known Fixed Releases: * | 7.0(3)I3(0.112), 7.0(3)I3(1), 7.0(7)ZN(0.115), 7.1(2)N1(0.551), 7.1(2)N1(1), 7.1(2)ZN(0.10), 7.2(0)N1(1), 7.2(1)N1(0.23), 7.2(1)N1(1), 7.3(0)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul35901 | Title: | N5K: ISSU to 6.0.2.N2.2 to flush lcsm.out file |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ISSU upgrade from 6.0.2.N1.1 to 6.0.2.N2.2 on a Nexus 5500 may fail with the following error message
Nexus5500# install all kickstart bootflash:n5000-uk9-kickstart.6.0.2.N2.2.bin system bootflash:n5000-uk9.6.0.2.N2.2.bin
Pre-upgrade check failed. Return code 0x40930062 (free space in the filesystem is below threshold).
Conditions:
The error is due to no spave left available in /var/sysmgr filesystem (Use% 100) on 'show system internal flash' command output. Deleting core files in /var/sysmgr filesystem with the 'clear cores' exec CLI command does not recover filesystem usage.
Workaround:
ISSU upgrade requires TAC assistance to clean up the /var/sysmgr filesystem.
Further Problem Description:
|
|
Last Modified: | 02-NOV-2015 |
|
Known Affected Releases: | 6.0(2)N2(2) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut49617 | Title: | N5K: 'ip router rip xxx' may disapper from running-config after reboot |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
`ip router rip ` config on SVI will sometimes disappears only from running-config after reload. At that time, startup-config still has that line.
Conditions:
This sometimes happens after reload.
Workaround:
reconfigure `ip router ip ` again.
Further Problem Description:
|
|
Last Modified: | 20-NOV-2015 |
|
Known Affected Releases: | 7.0(5)N1(1), 7.1(0)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.630), 7.1(3)N1(1), 7.1(3)ZN(0.37), 7.2(2)N1(1), 7.3(0)N1(0.122), 7.3(0)N1(1), 7.3(0)ZN(0.112) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug92414 | Title: | SVI can go down corresponding vlan active on FlexLink only |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
SVI interface can go down when corresponding VLAN is active (forwarded by) on FlexLink only.
Conditions:
This issue can happen only if you have FlexLinks and regular STP ports (trunk/access) which are allowing VLAN X.
When last non-FlexLink port belonging to VLAN X goes down, SVI interfaces goes down as well.
This happens despite on fact that FlexLink is active and VLAN X forwarded by it.
Workaround:
In order to restore SVI state, you will need to shutdown/no shutdown it.
Further Problem Description:
|
|
Last Modified: | 09-NOV-2015 |
|
Known Affected Releases: | 5.1(3)N2(1), 5.2(1)N1(2) |
|
Known Fixed Releases: * | 7.3(0)D1(0.148), 7.3(0)N1(0.197), 7.3(0)N1(0.199), 7.3(0)N1(1), 7.3(0)ZD(0.165), 7.3(0)ZN(0.180) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux06997 | Title: | inherit port-profile fails due to vpc orphan-port suspend |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Trying to inherit a port-profile on an interface throws the following error:
Nexus5500(config-if)# inherit port-profile PORT-PROFILE-NAME
Message reported by command :: vpc orphan-port suspend
ERROR: Configuration exists for some interfaces
ERROR: Failed to write VSH commands
Conditions:
"vpc orphan-port suspend" configured under the interface in question.
Workaround:
Remove "vpc orphan-port suspend" from the interface, inherit the port-profile and then add "vpc orphan-port suspend" configuration back on the interface.
Further Problem Description:
This issue does not apply when both the port-profile and the interface have "vpc orphan-port suspend" configured, where the error is expected due to mutual exclusion.
|
|
Last Modified: | 25-NOV-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.3(0)N1(0.219), 7.3(0)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq46063 | Title: | Nexus 5500 wrong port type response to CISCO-ENTITY-VENDORTYPE-OID-MIB |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Device Manager is not working correctly with the Nexus 5548UP or 5596UP (GEM modules installed) when the expansion module ports are set to fibre channel mode.
Hovering over the ports with the mouse in Device Manager will display for example, "Ethernet 1/17 Status: failed".
Looking at the same ports via CLI will show that the ports are really in FC mode and not configured as Ethernet ports.
Conditions:
Nexus 5548UP or Nexus 5596UP running NX-OS 7.0(2)N1(1) with GEM Expansion module ports configured to operate in Fibre Channel mode
Some ports are in Fibre Channel mode on the base chassis.
Workaround:
refer to bug CSCut82544:
Upgrade to NX-OS 7.2(1)N1(1)
Further Problem Description:
NX-OS 7.0(1)N1(1) and all previous software versions are not affected by this defect.
|
|
Last Modified: | 15-NOV-2015 |
|
Known Affected Releases: | 7.0(2)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua60484 | Title: | Nexus 5000: Max port channels incorrectly shows 4096 supported. |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
In a Nexus 5000/5500 series switches, following command shows 4096 as maximum
port-channels supported.
5596-A# show port-channel internal max-channels
Max port channels=4096
Where as command show port-channel capacity shows it as 1600.
5596-A# show port-channel capacity
Port-channel resources
1600 total 21 used 1579 free 1% used
Workaround:
The actual supported port-channels depends on the platform type. Refer to
configuration limits documents on cisco.com
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration_limits/limits_513/nexus_5000_config_limits_513.html
|
|
Last Modified: | 17-NOV-2015 |
|
Known Affected Releases: | 5.1(3)N2(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx89432 | Title: | Current bidirectional state: unknown; should be unidirectional instead |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
In the even of unidirectional link with UDLD enabled on the N5K port, the current bidirectional state of the show udld command output is shown as unknown instead of unidirectional.
Conditions:
Unidirectional fiber link with UDLD enabled.
Workaround:
none
|
|
Last Modified: | 05-NOV-2015 |
|
Known Affected Releases: * | 5.0(3)N2(2), 5.1(3)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug77359 | Title: | Enh: UDLD aggressive mode enhancement request |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: * | Symptoms:
If UDLD err-disable recovery is enabled, links which were error-disabled due to Unidirectional links come
up after the recovery interval and UDLD does not kick in unless there is a bi-directional state established.
This behavior can potentially introduce bridging loops.
Conditions:
Command errdisable recovery cause udld is configured.
Workaround:
Do NOT configure errdisable recovery cause udld
|
|
Last Modified: | 05-NOV-2015 |
|
Known Affected Releases: | 6.0(2)N1(2) |
|
Known Fixed Releases: | |
|
|
| |
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论