| |
|
Alert Type: | New |
Bug Id: | CSCuw59189 | Title: | After issuing 'clear mac-address table dynamic' mac address not learnt |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
N3K-C3172TQ-10GT running 7.0(3)I2(1) is showing mac-address table completely empty.
ARP entries are present but dynamic CAM is empty. There were no entries in hardware as well.
If you create a static entry, that will show up but dynamic entries are still absent.
Conditions:
3172 running on 7.0(3)I2(1) or 7.0(3)I2(1a)
Workaround:
reload will fix the issue but it will come back again after a while.
Further Problem Description:
check below output
bcm-shell module 1 "g L2_MOD_FIFO_CNT"
L2_MOD_FIFO_CNT.ipipe0[1][0x1b110000]=0x80:
If the number of entries is stuck at 0x80, then we are hitting this bug. This has nothing to do with number of mac entries.
|
|
Last Modified: | 01-JAN-2016 |
|
Known Affected Releases: | 7.0(3)I2(1.31) |
|
Known Fixed Releases: | 7.0(3)I2(1.41), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75563 | Title: | PFC buffer reservation is shown same valu for 10G and 40G ports on TPlus |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On N3064 platform and QSFPs are in 40 gig mode, 10G ports show same PFC buffer as 40g ports.
Conditions:
On N3064 platform when QSFPs are in 40 gig mode, 10G ports show same PFC buffer as 40g ports.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1), 7.0(3)I2(1.40) |
|
Known Fixed Releases: * | 7.0(3)I2(1.49), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut76803 | Title: | GLDN: syslogd hap reset seen while executing fast-reload in a loop |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Nexus 3000 may experience a syslogd hap reset after a reload.
Conditions:
The syslogd core has only been reported after a reload/upgrade.
Workaround:
Unknown at this time.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U3(5.95) |
|
Known Fixed Releases: * | 6.0(2)A6(4), 6.0(2)U3(7.99), 6.0(2)U3(8), 6.0(2)U6(1.72), 6.0(2)U6(2), 7.0(3)I2(0.590), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23031 | Title: | DHCP Hop Count incorrectly incremented when multiple relays configured |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Incorrect DHCP hop count is seen on packets which are relayed by the Nexus 3000. Packets relayed to the first server are sent with original dhcp_discover hop count +1. Second relay agent is sent with original dhcp_discover hop count + 2, Third relay agent is sent with original dhcp_discover hop count +3, and so on. All of these instead should be sent with original dhcp discover hop count + 1
Conditions:
On a Nexus 3000, when there are multiple DHCP relay addresses configured the nexus incorrectly increments the hop count by 1 for every relay configured. This could lead to the dhcp server dropping the packet if there are more than 16 relay addresses configured
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U6(4) |
|
Known Fixed Releases: * | 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq05010 | Title: | Nexus 3100: QSFP-40G-SR-BD V01 Generates TX-LOS after Multiple Reloads |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Optical link does not come up after switch reload.
Conditions:
- QSFP-40G-SR-BD V01 (serial number up to and including AVM1813xxxx)
- Multiple reloads
Workaround:
Two workarounds are available on this platform:
- Reseat QSFP
- Reload switch
Further Problem Description:
This is an intermittent issue with a very low failure rate , field failure rate is less than 0.01%.
Issue is not seen in QSFP-40G-SR-BD V02.
Related bug for Nexus 7000: CSCuo76571
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U3(2.61) |
|
Known Fixed Releases: * | 6.0(2)A6(4.116), 6.0(2)A6(5), 6.0(2)U6(3.116), 6.0(2)U6(4), 7.0(3)I2(1.78), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw03055 | Title: | Fast-Reload: IPv6 traffic convergence is greater than 30seconds |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
The IPv6 traffic down time is around 32 seconds, which is 2 seconds more than the targeted 30 second data plane downtime, during fast-reload.
Conditions:
This issue is seen with IPv6 traffic over BGP.
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.592) |
|
Known Fixed Releases: * | 7.0(3)I2(1.41), 7.0(3)I2(1.45), 7.0(3)I2(1.46), 7.0(3)I2(1.49), 7.0(3)I2(1.51), 7.0(3)I2(1.57), 7.0(3)I2(1.6), 7.0(3)I2(1.74), 7.0(3)I2(2), 7.0(3)I3(0.128) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux33013 | Title: | Nexus 3k crash with "mtc_usd hap reset". |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Device can crash with "mtc_usd hap reset" as interrupt for virtual-time rate shaping is triggered.
Conditions:
N/A
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A7(1) |
|
Known Fixed Releases: * | 6.0(2)A6(5.187), 6.0(2)A6(5.188), 6.0(2)A6(6), 6.0(2)A7(0.17), 6.0(2)A7(1), 6.0(2)U7(0.17), 6.0(2)U7(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut70482 | Title: | bcm_usd may crash on fast-reload and abort upgrade |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
bcm_usd may crash on fast-reload and abort upgrade
Conditions:
While running into HW parity error
Workaround:
Disable parity interrupts to prevent running into the condition.
CLIs to Enable/disable these interrupts.
test hardware internal bcm-usd bcm-diag-shell intr disable memfail <-disable interrupts
memscan i=300000000 Rate=0 <-Disable memscan
exit
sleep 5 continue with previous workflow (fast-reload cli...)
If for some reason, fast reload had to be aborted, re-enable these two interrupts
test hardware internal bcm-usd bcm-diag-shell intr enable memfail <- Enable interrupts
memscan i=10000000 rate=4096 on <- Enable Memscan
exit
Sample outputs:
Interrupt disable case:
bcm-shell.0> intr disable memfail
Disabled with mask 0x10000000. Mask was 0x10538010
bcm-shell.0> memscan i=300000000 Rate=0
MemSCAN: Started on unit 0
bcm-shell.0> memscan
MemSCAN: Running on unit 0
MemSCAN: Interval: 300000000 usec
MemSCAN: Rate: 0
Interrupt enable case:
bcm-shell.0> intr enable memfail
Enabled with mask 0x10000000. Mask was 0x00538010
bcm-shell.0> memscan i=10000000 rate=4096 on
MemSCAN: Started on unit 0
bcm-shell.0> memscan
MemSCAN: Running on unit 0
MemSCAN: Interval: 10000000 usec
MemSCAN: Rate: 4096
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U2(4.92.4Z), 6.0(2)U2(9.99) |
|
Known Fixed Releases: * | 6.0(2)U3(7.102), 6.0(2)U3(7.96), 6.0(2)U3(8), 7.0(3)I2(0.590), 7.0(3)I2(0.591), 7.0(3)I2(1), 7.0(3)ITI2(1), 7.0(3)ITI2(1.37), 8.3(0)CV(0.248) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut32936 | Title: | PTP not sending Follow_up message on N3K |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PTP Master is not forwarding ptp followup message when ptp sync interval -1,0,1
Conditions:
If ptp sync interval -1,0,1, ptp followup message was not forwarded.
Workaround:
N/A
Further Problem Description:
N/A
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U4(1) |
|
Known Fixed Releases: * | 6.0(2)A6(1.132), 6.0(2)A6(2), 6.0(2)U6(0.132), 6.0(2)U6(1), 7.0(3)I2(0.578), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw18920 | Title: | JAMAICA : Support for IPMROUTE-STD-MIB broken on Nexus-3500 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
SNMP walk fails on IPMROUTE-STD-MIB fails.
Conditions:
snmpwalk -v2c -c public ipmroute-std-mib.8 fails with error "No Such Object available on this agent at this OID"
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A7(0.231) |
|
Known Fixed Releases: * | 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv92956 | Title: | NX-API broken on 6.0(2)U6(2) |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
While enabling feature NXAPI on U6(2) official image, we are getting "not enough memory" error and we are not enabling this feature
Conditions:
Always
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U6(1.99) |
|
Known Fixed Releases: * | 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw36188 | Title: | Wrong VLAN ID programmed on HSRP L3 Po sub interface |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When HSRP is configured on L3 port-channel sub-interfaces, the wrong VLAN ID is programmed in hardware. HSRP comes up correctly but this leads to silent packet drop.
Conditions:
When HSRP is configured on L3 port-channel sub-interfaces, the wrong VLAN ID is programmed in hardware. HSRP comes up correctly but this leads to silent packet drop.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1.29), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut97806 | Title: | 1G link not up in QI2-CR with autoneg enabled. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
1G ports does not link up between Nexus 3172PQ and other peers
Conditions:
When Nexus 3172 is configured in 48x10G+6x40G portmode
Workaround:
Two options:
a) Configure portmode as 48x10g+breakout6x40g. In this mode, 1G ports does not have this issue. Also the last QSFP ports will work in 40G mode.
b) Disable auto-negotiation (AN) on the affected interface using "no negotiate auto" in interface configuration mode. Note that this command will fail while the interface is assigned to a port-channel. Procedure in this case is to first remove the "channel-group" command, then add the "no negotiate auto" and then re-apply the "channel-group".
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U6(1) |
|
Known Fixed Releases: * | 6.0(2)A6(3), 6.0(2)U6(2), 7.0(3)I2(1.66), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw44058 | Title: | N3500: UTC offset not reused by BC when utc_offet_valid is FALSE from GM |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
GM ---------- BC1 ------------ BC2 ---------- client
In the above topology when Grand Master [GM] sends utc_offset_valid as FALSE, Boundary Clock node [BC1] propagates 36 as utc offset irrespective of the once received from GM.
In our case, GM sends UTC offset 35 with UTC_offset_valid as FALSE. However BC1 sends to BC2 with UTC offset as 36 and UTC_offset_valid as TRUE.
BC1 *must* always reuse the information received from GM.
Conditions:
NA
Workaround:
There are no known workarounds
Further Problem Description:
N3500 overides UTC offset value when GM sends utc offset valid flag as FALSE.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A6(4.124) |
|
Known Fixed Releases: * | 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw08964 | Title: | OpenSSH: Evaluation of Multiple OpenSSH CVEs for NX-OS |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Cisco Nexus Operation System (NX-OS) includes a version of Open Secure Shell (OpenSSH)
software that is affected by the vulnerabilities identified by the following Common
Vulnerability and Exposures (CVE) IDs:
CVE-2015-5600, CVE-2015-6563, CVE-2015-6564 and CVE-2015-6565
This bug was opened to address the potential impact on this product.
Conditions:
Device with default configuration.
Workaround:
Not currently available.
Further Problem Description:
Additional details about the vulnerabilities listed above can be found at
http://cve.mitre.org/cve/cve.html
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5600
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-6563
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-6564
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-6565
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 6.9/6.9:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:L/AC:M/Au:N/C:C/I:C/A:C/E:H/RL:U/RC:C&version=2.0
CVE ID CVE-2015-5600, CVE-2015-6563, CVE-2015-6564, CVE-2015-6565 has been assigned to document 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: | 22-DEC-2015 |
|
Known Affected Releases: | 7.3(0)ZN(0.89) |
|
Known Fixed Releases: * | 6.0(2)A7(0.282), 6.0(2)A7(1), 6.0(2)U6(5), 6.0(2)U7(0.282), 6.0(2)U7(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw71568 | Title: | AAA Crashes when sytem is idle |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
AAA Crash and Core dumped
Conditions:
N/A
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U3(7.99) |
|
Known Fixed Releases: * | 6.0(2)A7(0.296), 6.0(2)A7(1), 6.0(2)U6(5), 6.0(2)U7(0.296), 6.0(2)U7(1), 7.0(3)I3(0.112), 7.0(3)I3(1), 7.0(3)IDP3(1.12), 7.0(3)IDP3(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui21504 | Title: | N3548(10G) - -ve and +ve offsets are huge for sync interval -1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
N3500 shows extreme periodic time adjustment when acting as slave. This is *periodic* and is not a continuous process. Hard to see unless user monitors ptp correction always
Conditions:
3500 as slave and PTP running for long duration
Workaround:
no workaround
Further Problem Description:
When N3500 is acting as slave, show ptp correction shows about 109951162XXXX nanosec adjustment with master. Test result shows the large adjustment happens approx 25-30 times in an 24 hours, but not limited to this.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A1(1) |
|
Known Fixed Releases: * | 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv95538 | Title: | N3K AFM memory leak in libglib-2.0.so.0.1600.3 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
AFM service hap reset due to a memory leak
Conditions:
This has been seen on N3K platform running 6.0(2)A6(3) code.
show platform afm mem-stats detail
154 [r-xp]/lib/libc-2.8.so 10151 10153 985546 1220292
157 [r-xp]/lib/libglib-2.0.so.0.1600.3 210512 210684 63038322 63079362
--------------------------------------------------------------------------------
Total bytes: 64320620 (62813k)
--------------------------------------------------------------------------------
Total bytes: 455700 (445k)
--------------------------------------------------------------------------------
Grand total bytes: 89982801 (87873k)
LHC-JPM-EMM-ASN-P01# show process memory | i afm
3691 241053696 565047718 1400832 287354880 58527744 fff86900/ffffffff afm
Workaround:
Not Known
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A4(5) |
|
Known Fixed Releases: * | 6.0(2)A6(5), 6.0(2)A7(0.255), 6.0(2)A7(1), 6.0(2)U6(5), 6.0(2)U7(0.255), 6.0(2)U7(1) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCut57500 | Title: | MTC-CR: IGMP join messages are punted to the CPU thro' a wrong CoPP que |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IGMP messages are punted to CPU via a wrong copp que
Conditions:
NA
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A6(1.150) |
|
Known Fixed Releases: | 6.0(2)A6(1.19), 6.0(2)A6(2), 6.0(2)U6(0.19), 6.0(2)U6(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus93314 | Title: | Wavesplitter SR4 optics may not link up on 3132 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Wave splitter SR 4 optics may not function
Conditions:
seen on QSFP wtih P/N WST-QSFP+SR4-C on Hawaii release
Workaround:
device reload
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U5(1) |
|
Known Fixed Releases: * | 6.0(2)A6(0.2), 6.0(2)A6(0.85), 6.0(2)A6(1), 6.0(2)A6(1.112), 6.0(2)A6(2), 6.0(2)U6(0.112), 6.0(2)U6(0.2), 6.0(2)U6(0.85), 6.0(2)U6(1), 7.0(3)I2(1.77) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq59586 | Title: | back space hits 73rd character will "blank" out all characters |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
when entering long CLI command that exceeded 73 characters, if back space was used, when back space hits the 73rd character, all characters then disappeared from the command line.
Conditions:
CLI command exceeds 72 characters long and back space bar was used
Workaround:
set the terminal width to a bigger number. By default terminal width is set at 72. This can the set to a maximum number of 511.
BLR-SCL-QI2-28# terminal width ?
<24-511> Number of characters on a screen line
BLR-SCL-QI2-28# terminal width 511
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 5.0(3)U5(1h) |
|
Known Fixed Releases: * | 6.0(2)A6(0.74), 6.0(2)A6(1), 6.0(2)U6(0.74), 6.0(2)U6(1), 7.0(3)I2(1.66), 7.0(3)I2(2), 7.0(3)I3(0.128), 7.0(3)I3(1), 7.0(3)IDP3(1.12), 7.0(3)IDP3(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj75633 | Title: | Display an error message for any unsupported XML BGP command |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Nexus 3000 prints the following error message if a show ip bgp command is not supported by XML. Below is copied from a N3K:
N3K# sh ip bgp ipv4 unicast summary | xml
nftlv(output): cmd_id is 88, attr_id is 303c0275 (hex), cmd_exact_path_found is 0
...
nftlv(output): cmd_id is 88, attr_id is 303c0299 (hex), cmd_exact_path_found is 0
]]>]]>
Below is copied from a N7K:
N7K# show ip bgp ipv4 unicast summary | xml
Error: This command does not support XML output.
Conditions:
This bug is verified exists in 6.0(2)U1(2).
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U1(2) |
|
Known Fixed Releases: * | 6.0(2)A6(0.58), 6.0(2)A6(1), 6.0(2)U6(0.58), 6.0(2)U6(1), 7.0(3)I2(1.74), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv90945 | Title: | 90% traffic convergence with 30 sec; 100% traffic takes more than 30 sec |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Data convergence time is more in 7.0(3)I2(1) compared to previous releases on Nexus 3000 platforms
Conditions:
Always
Workaround:
None required
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.572) |
|
Known Fixed Releases: * | 7.0(3)I2(0.583), 7.0(3)I2(1), 7.0(3)I2(1.66), 7.0(3)I2(2), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv95675 | Title: | Fast-reload upgrade from U6 to Camden delayed in applying qos config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On N3064 device when executing a fast-reload upgrade from U6 to Camden, the network qos config gets delayed in being applied which causes long convergence time.
Conditions:
On N3064 device when executing a fast-reload upgrade from U6 to Camden, the network qos config gets delayed in being applied which causes long convergence time.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.580), 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(0.597), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.37), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw47325 | Title: | N3132X: Interface fails to come up after fast-reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After fast-reload or re-pave interface fails to come up.
Conditions:
After fast-reload or re-pave interface fails to come up.
Workaround:
Execute regular reload
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1.29), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw84260 | Title: | Hide cli copp profile on N3k when running in n3k mode |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
From the cli in global config mode when you enter the command "copp profile strict", the error message "Tcam Allocation Failure" is displayed.
Conditions:
switch(config)# copp profile strict
This operation can cause disruption of control traffic. Proceed (y/n)? [no] y
ERROR: Tcam Allocation Failure
This command is applicable only when N3k is running in N9k mode.
In N3K mode, this CLI is not used.
Workaround:
Change the mode from N3k to N9K by typing "system switch-mode n9k" and "write erase, reload" the switch. Then we can use "copp profile" CLI.
From the cli type the following:
1) conf t
system switch-mode n9k
2) copy run start
3) write erase
4) reload
5) conf t
copp profile strict
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1.56), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq83575 | Title: | Improve serviceability of message neutron_usd - failed to set mux addr |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
This is not a software bug. It is an enhancement request to improve the serviceability of the following error message:
%KERN-3-SYSTEM_MSG: [2654954.489403] neutron_usd - failed to set mux addr 0xYY ch Y err Y -
kernel
Conditions:
This bug applies to software up to 6.0(2)U3(3)
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U3(1) |
|
Known Fixed Releases: * | 6.0(2)A5(1.38), 6.0(2)A5(2), 6.0(2)A6(1.90), 6.0(2)A6(2), 6.0(2)U5(1.38), 6.0(2)U5(2), 6.0(2)U6(0.90), 6.0(2)U6(1), 7.0(3)I2(1.69), 7.0(3)I2(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux05718 | Title: | Display of configured L2 MTU value |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
In Pre 7.0(3)I2(x), HW MTU value is displayed in "show queuing interface <>" output. But in 7.0(3)I2(1) onwards , the output does not show the HW MTU value. This is a cosmetic issue and is being fixed. No functional impact.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: | 7.0(3)I2(2.15), 7.0(3)I2(2a), 7.0(3)I2(3), 7.0(3)I3(0.126), 7.0(3)I3(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw53989 | Title: | QC: ARP request not sent to from SVI member interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ARP request not sent from SVI
Conditions:
Affects only 3048, is seen usually after adjacent device is restarted
Workaround:
bounce the SVI VLAN interface
or
Start ICMP echo request to initiate ARP from the peer.
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U3(7.99) |
|
Known Fixed Releases: * | 6.0(2)A6(5), 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw69322 | Title: | N3500 counts ICMP NAT flows against dynamic NAT max limit |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ICMP traffic might get translated if 'ip nat trans max' is already reached.
Conditions:
if lot of traffic is sent and number of nat-entries were already reach the max-limit,
then, icmp nat-entries won't be created which would result in unable to translate ICMP-traffic too.
Workaround:
Reduce the active number of flow or
execute 'clear ip nat'
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A6(4.132) |
|
Known Fixed Releases: * | 6.0(2)A6(5), 6.0(2)A7(0.285), 6.0(2)A7(1), 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39205 | Title: | DoM information is only shown for lane1 w/QSFP SR4 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
DoM information for SR4 optics only shows one lane
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U6(4) |
|
Known Fixed Releases: * | 6.0(2)A6(5.181), 6.0(2)A6(5.182), 6.0(2)A6(6), 6.0(2)U6(4.181), 6.0(2)U6(4.182), 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv33390 | Title: | MSDP timers should match (S,G) state |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Currently in NX-OS, MSDP timers rely on the generation of Null-Registers on the RP to keep the SA state active. Even if the (S,G) expiry timer is increased and the source stops sending, the SA will eventually time out due to inactivity from the source as the Null-Registers will stop even though the (S,G) is still active.
Conditions:
This is the default behavior in NX-OS.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A4(3) |
|
Known Fixed Releases: * | 6.0(2)U6(5), 7.3(0)D1(0.178), 7.3(0)GLF(0.44), 7.3(0)RTG(0.98), 7.3(0)SC(0.14), 7.3(0)ZD(0.195), 7.3(0)ZN(0.211) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux03216 | Title: | N3500 ip pim dr-delay command does not work |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Nexus 3500 connected to each other with L3 Link and PIM enabled on the SVI5
Conditions:
When the PIM DR is reloaded and it comes back up or its pim interface comes up after no shut, it preempts the current DR and becomes DR again.
Workaround:
N/A.
Further Problem Description:
'ip pim dr-delay' cli is currently not supported on Nexus 3500
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A4(5) |
|
Known Fixed Releases: * | 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux56810 | Title: | Dublin_N3K: IP address is missing in HW on kickstart of DUT linux prompt |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
Management IP address is not reachable from kickstart boot prompt (also known as recovery prompt)
Conditions:
Always
Workaround:
Reconfigure the IP address and unshut the management port as below -
switch(boot)# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(boot)(config)# interface mgmt 0
switch(boot)(config-if)# ip address 10.197.121.219 255.255.255.0
switch(boot)(config-if)# no shutdown
switch(boot)(config-if)# exit
switch(boot)(config)# ip default-gateway 10.197.121.1
switch(boot)(config)# exit
switch(boot)#
Further Problem Description:
|
|
Last Modified: | 19-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I3(0.190) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux02122 | Title: | Loss of control plane with high Memory utilization on 3k - no core |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Memory utilization increased from 62% to 78% over the last 3-months. The memory is leaking in the FWM process:
Nexus# show process memory
PID MemAlloc MemLimit StkSize RSSMem LibMem StackBase/Ptr Process
----- -------- ---------- ------- ------- ------- ------------- ---------
.
.
3380 421928960 931326668 86016 458145792 78491648 ffbab540/ffffffff fwm
In the example above we see the RSSMEM (holding memory) for the fwm process is at 458145792. Looking in more detail, we find that the memory is being held by FWM_MEM_fwm_temp_t:
Nexus# show platform fwm mem-stats detail
.
.
Private Mem stats for UUID : Forwarding manager Daemon(652) Max types: 371
--------------------------------------------------------------------------------
TYPE NAME ALLOCS BYTES
CURR MAX CURR MAX
41 FWM_MEM_fwm_temp_t 1560000 1560002 299520000 299524016
When memory got above 78% the switch became unresponsive. Initially SNMP access was lost. Then, L2 forwarding loop was observed. Nothing coming out of console serial port. Upon reload the switch came back fine.
Conditions:
When "show mac address-table" or "show mac address-table static" is executed,
Workaround:
Not to execute "show mac address-table" or "show mac address-table static"
Further Problem Description:
Each iteration was found to be leaking around 96KB of memory.
Issue not present in NXOS 7.x
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U5(2) |
|
Known Fixed Releases: | 6.0(2)A6(5.183), 6.0(2)A6(6), 6.0(2)U6(4.183), 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux52926 | Title: | FWM Heartbeat Failure with Trident ASIC MAC Event |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
The switch resets from an "fwm" hap reset. The output of "show process log detail" shows the "Last heartbeat" time to have been around 10 minutes ago (~600 seconds)
Conditions:
The issue seems to occur when we're programming new L2/MAC addresses onto the Trident ASIC. More specific conditions are unknown.
Workaround:
Unknown
Further Problem Description:
|
|
Last Modified: | 13-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U5(2) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw74480 | Title: | ipqosmgr core on N3064 fast-reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ipqosmgr service crashes after fast-reload completes on N3064 device
Conditions:
ipqosmgr service crashes after fast-reload completes on N3064 device
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1.48), 7.0(3)I2(2), 8.3(0)CV(0.248) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw62676 | Title: | N3k: CoPP process crash. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A Nexus 300 switch encounters a CoPP crash/HAP reset when attempting to copy the copp policy. As an illustration, refer to the following snippet:
3K-1(config)# copp copy profile strict prefix PSAC2
2015 Oct 9 18:07:06 N3K-1 %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "copp" (PID 5605) hasn't caught signal 11 (core will be saved).
2015 Oct 9 18:07:06 N3K-1 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: end of default policer - copp
2015 Oct 9 18:07:06 N3K-1 %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "copp" (PID 6831) hasn't caught signal 11 (core will be saved).
2015 Oct 9 18:07:06 N3K-1 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: end of default policer - copp
2015 Oct 9 18:07:06 N3K-1 %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "copp" (PID 6833) hasn't caught signal 11 (core will be saved).
Conditions:
This problem has been reported in 7.0(3)I2(1) release. The prior 6.0x releases should not hit this bug since this is an unsupported command which was introduced post-6.0x
Workaround:
There is no way to avoiding this crash when executing this command.
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1.43), 7.0(3)I2(2), 8.3(0)CV(0.248) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut02440 | Title: | When N3500 is GM, PTP Announce comes with utc_reasonable flag set to F |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a Nexus 3500 is Grandmaster, the utc_reasonable flag in the ptp announce message is set to false.
In a design with an active and standby GM clocks. In case of active GM failure, Nexus may become GM for a short while till the standby takes over. Because Nexus doesn't set the utc_reasonable flag, the clock on the slave ptp devices will jump by utc_offset (35 sec).
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A1(1c), 6.0(2)A4(4) |
|
Known Fixed Releases: * | 6.0(2)A4(5.47), 6.0(2)A4(6), 6.0(2)A6(1.127), 6.0(2)A6(2), 6.0(2)U4(4.47), 6.0(2)U4(5), 6.0(2)U6(0.127), 6.0(2)U6(1), 7.0(3)I2(0.569), 7.0(3)I2(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu74705 | Title: | After breakout, ports come in no shutdown mode (N9k breakout) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Breakout ports are in administratively enabled state after breakout or breakin. This is a behavior change from 7.0(3)I2(1) release on Nexus 3000 platforms.
Conditions:
After breakout of the ports into 4x10G mode or breakin of ports into 40G mode
Workaround:
None required. On upgrade from earlier releases, the configuration restored will take care of restoring the appropriate administrative state of the ports.
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.360) |
|
Known Fixed Releases: * | 7.0(3)I2(1.33), 7.0(3)I2(2), 7.0(3)I3(0.122), 7.0(3)I3(1), 8.3(0)CV(0.248) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux41329 | Title: | Evaluation of nexus-3500 for OpenSSL December 2015 vulnerabilities |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Cisco Nexus 3X00 Series Switches includes a version of OpenSSL that is affected by the vulnerability identified by one or more of the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2015-3193, CVE-2015-3194, CVE-2015-3195, CVE-2015-3196 and CVE-2015-1794
And disclosed in http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20151204-openssl
This bug has been opened to address the potential impact on this product.
Conditions:
Exposure is not configuration dependent.
Cisco has reviewed and concluded that this product is affected by one or more of these vulnerabilities.
Cisco Nexus 3X00 Series Switches is affected by:
CVE-2015-3195
Cisco Nexus 3X00 Series Switches is not affected by:
CVE-2015-3193, CVE-2015-3194, CVE-2015-3196 and CVE-2015-1794
Workaround:
Not available.
Further Problem Description:
Additional details about those vulnerabilities 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: 4.3/3.4
http://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AV:N/AC:M/Au:N/C:N/I:N/A:P/E:POC/RL:OF/RC:C
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/web/about/security/psirt/security_vulnerability_policy.html
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A7(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux48252 | Title: | openflow flow not able to match on 0x0 ethertype |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traffic does not match flow if flow is programmed using ethertype 0x0 (flow shows ethertype as dl_type)
Conditions:
Switch version: 6.0(2)A6(5)
OFA Agent: 1.1.5 (ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova)
Nexus Data Broker Controller Version: 2.2.0 (running embedded)
Attempting to program a flow using "all ethertypes" which correlates on the controller using ethertype 0x0
Example flow:
Flow: 7
Match: in_port=5,dl_type=0x0000
Actions: output:21
Priority: 500
Table: 0
Cookie: 0x0
Duration: 1050.884s
Number of packets: 0
Number of bytes: 0
Workaround:
Program flow without any ethertype requirement, eg:
Flow: 2
Match: in_port=5
Actions: output:21
Priority: 5
Table: 0
Cookie: 0x0
Duration: 834.083s
Number of packets: 414035
Number of bytes: 60577298
Further Problem Description:
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A6(5.184) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw02035 | Title: | Cisco NX-OS Malformed ARP Header Vulnerability |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A vulnerability in Address Resolution Protocol (ARP) feature of the Cisco Nexus Operating System (NX-OS) could allow an
unauthenticated, adjacent attacker to cause a partial denial of service (DoS) condition due to the ARP process unexpectedly
restarting.
The vulnerability is due to improper input validation of the fields in the ARP packet header. An attacker could exploit this
vulnerability by sending a crafted ARP packet from an adjacent network to the affected device. An exploit could allow the
attacker to cause a partial DoS condition because the ARP process could unexpectedly restart when processing the
crafted ARP packet.
Conditions:
Device running with default configuration running an affected version of software.
Workaround:
None.
Further Problem Description:
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 6.1/5.8:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:A/AC:L/Au:N/C:N/I:N/A:C/E:F/RL:U/RC:C&version=2.0
CVE ID CVE-2015-6277 has been assigned to document 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: | 30-DEC-2015 |
|
Known Affected Releases: * | 7.3(0)ZD(0.47), 7.3(0)ZD(0.61) |
|
Known Fixed Releases: | 6.0(2)A6(4.129), 6.0(2)A6(5), 6.0(2)U6(3.129), 6.0(2)U6(4), 6.0(2)U6(5), 7.0(3)I2(1.66), 7.0(3)I2(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux67091 | Title: | N3K BGP Slab message |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When modifying BGP neighbors / attributes the logs below are being displayed
2015 Nov 5 17:23:03 TCLSW01 %BGP-3-SLAB_ERR: -Traceback: librsw.so+0x96c7f librsw.so+0x96f63 librpm_dll.so+0x29cba librpm.so+0x3e9c 0x81b8ca1 0x807765e 0x80894e8 0x808bacd 0x80b0129 librsw.so+0xcda28 librsw.so+0xcde66 librsw.so+0xcc2c2 librsw.so+0xcd6b6 librsw.so+0x9ea37 libpt*
2015 Nov 5 17:23:03 TCLSW01 %BGP-2-SLAB_LIB_SLAB_ELEM_ERR: Slab element Alloc PC: 0xab3848ad, Element index: 741
2015 Nov 5 17:23:03 TCLSW01 %BGP-2-SLAB_ELEM_ERR: -Traceback: librsw.so+0x96dd0 librsw.so+0x96f63 librpm_dll.so+0x29cba librpm.so+0x3e9c 0x81b8ca1 0x807765e 0x80894e8 0x808bacd 0x80b0129 librsw.so+0xcda28 librsw.so+0xcde66 librsw.so+0xcc2c2 librsw.so+0xcd6b6 librsw.so+0x9ea37 *
2015 Nov 5 17:23:03 TCLSW01 %BGP-3-SLAB_LIB_SLAB_ERR: Slab error [double free attempted] in RPM Prefix tree slab
2015 Nov 5 17:23:03 TCLSW01 %BGP-3-SLAB_ERR: -Traceback: librsw.so+0x96c7f librsw.so+0x96f63 librpm_dll.so+0x29cf7 librpm.so+0x3e9c 0x81b8ca1 0x807765e 0x80894e8 0x808bacd 0x80b0129 librsw.so+0xcda28 librsw.so+0xcde66 librsw.so+0xcc2c2 librsw.so+0xcd6b6 librsw.so+0x9ea37 libpt*
2015 Nov 5 17:23:03 TCLSW01 %BGP-2-SLAB_LIB_SLAB_ELEM_ERR: Slab element Alloc PC: 0xab38472f, Element index: 933
2015 Nov 5 17:23:03 TCLSW01 %BGP-2-SLAB_ELEM_ERR: -Traceback: librsw.so+0x96dd0 librsw.so+0x96f63 librpm_dll.so+0x29cf7 librpm.so+0x3e9c 0x81b8ca1 0x807765e 0x80894e8 0x808bacd 0x80b0129 librsw.so+0xcda28 librsw.so+0xcde66 librsw.so+0xcc2c2 librsw.so+0xcd6b6 librsw.so+0x9ea37 *
Conditions:
When editing route-maps assigned to neighbors / deleting neighbor statements
Workaround:
n/a
Further Problem Description:
n/a
|
|
Last Modified: | 30-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U3(3.87) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux38660 | Title: | Encoder error on executing `show lldp neighbor | xml` |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When running `show lldp neighbor | xml` or `show lldp neighbor | json` chassis may response with `encoder error` message
Conditions:
So far issue was observed on N3K-C3164PQ running 7.0(3)I1(2). Please note, other NX-OS version may also be affected.
Workaround:
As temporary workaround, you may use `show lldp neighbor detail | xml` or `show lldp neighbor detail | json`
Further Problem Description:
True cause is under investigation
|
|
Last Modified: | 27-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I1(1.251) |
|
Known Fixed Releases: * | 7.0(3)I3(0.192), 7.0(3)I3(1), 7.0(3)IAB3(0), 7.0(3)IAB3(0.53) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus90555 | Title: | LR4 transcievers not recognized in 3132 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Wave splitter PLRL4 transceivers may not get recognized.
Conditions:
Wavesplitter with P/N WST-QSFP+PL4L-C
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U5(1) |
|
Known Fixed Releases: * | 6.0(2)A6(0.2), 6.0(2)A6(0.85), 6.0(2)A6(1), 6.0(2)U6(0.2), 6.0(2)U6(0.85), 6.0(2)U6(1), 7.0(3)I2(1.77), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv86148 | Title: | N3064: 4x10 QSFP breakout ints have different buffer boost |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When N3064 has QSFPs broken out into 4x10gig, the interfaces can have different buffer boost by default which due to this, the 4 interfaces cannot be placed into a single port-channel.
Conditions:
When N3064 has QSFPs broken out into 4x10gig, the interfaces can have different buffer boost by default which due to this, the 4 interfaces cannot be placed into a single port-channel.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.568) |
|
Known Fixed Releases: * | 7.0(3)I2(0.572), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu69356 | Title: | VPC peer-link between Camden & Prev releases |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
For Cisco Nexus 3000 vPC topologies, a non-disruptive upgrade from Cisco NX-OS Release 6.0(2)U6(X) to 7.0(3)I2(1) is not supported as the upgrade will cause a traffic disruption. An upcoming maintenance release will support non-disruptive upgrades for vPC topologies.
Conditions:
For Cisco Nexus 3000 vPC topologies, a non-disruptive upgrade from Cisco NX-OS Release 6.0(2)U6(X) to 7.0(3)I2(1) is not supported as the upgrade will cause a traffic disruption. An upcoming maintenance release will support non-disruptive upgrades for vPC topologies.
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.3(0)ZN(0.14) |
|
Known Fixed Releases: * | 6.0(2)A6(4.108), 6.0(2)A6(4.109), 6.0(2)A6(5), 6.0(2)U6(2.108), 6.0(2)U6(2.109), 6.0(2)U6(4), 7.0(3)I2(0.599), 7.0(3)I2(0.600), 7.0(3)I2(0.601), 7.0(3)I2(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw83221 | Title: | WARP mode does not get enable after reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
WARP mode is not enabled after it's configured, and the device reloaded. We still see the forwarding mode as "normal".
Conditions:
Observed on a 3524-P and 35xx running 6.0(2)A6(4).
Workaround:
None available.
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: * | 6.0(2)A6(4), 6.0(2)A7(1) |
|
Known Fixed Releases: | 6.0(2)A6(4.147), 6.0(2)A6(5), 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw58443 | Title: | TCAM full condition - enhanced handling needed after condition clears |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After TCAM full condition clears, flows for some prefixes are softsare switched
Conditions:
During TCAM full condition, any new flows will not be installed in hardware
Now once TCAM full condition clears the flows that were not installed in hardware previously will continue to be in that state, even though TCAM resources are available
Workaround:
Run CC, identify prefixes not in hardware and clear ip route for them to re-progream
Further Problem Description:
|
|
Last Modified: | 26-DEC-2015 |
|
Known Affected Releases: | 6.0(2)U6(4) |
|
Known Fixed Releases: * | /bin/sh:, 6.0(2)A6(4.151), 6.0(2)A6(4.154), 6.0(2)A6(5), 6.0(2)A6(5.168), 6.0(2)A6(6), 6.0(2)U6(4.151), 6.0(2)U6(4.154), 6.0(2)U6(4.168), 6.0(2)U6(5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus36166 | Title: | Monitoring LACP groupd via SNMP always returns value of 1 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
The SNMP agent in the Nexus 3000 series always returns a value of 1 for the object dot3adAggAggregateOrIndividual, regardless of how the device is actually configured.
Conditions:
Workaround:
At this time, there is no workaround.
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 5.0(3)U5(1e) |
|
Known Fixed Releases: * | 6.0(2)A6(0.18), 6.0(2)A6(1), 6.0(2)U6(0.18), 6.0(2)U6(1), 7.0(3)I2(1.75), 7.0(3)I2(2), 7.0(3)IDP3(1.13), 8.3(0)CV(0.248) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw40330 | Title: | Add space between acl udf matching and "set-erspan" option |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
No space between acl udf matching and set-erpspan attributes in running config makes reading difficult
Conditions:
No space between acl udf matching and set-erpspan attributes in running config makes reading difficult. See below
ip access-list acl-erspan
statistics per-entry
10 permit ip any 188.0.0.0/8
20 permit udf udf_in_tcp_prt12 0xeeee 0xffffset-erspan-dscp 40 <--
30 permit ip any any udf udf_in_tcp_prt12 0xeeee 0xffffset-erspan-gre-proto 35006 <--
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1.24), 7.0(3)I2(2), 8.3(0)CV(0.248), 8.3(0)KMS(0.31) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub27721 | Title: | Remove Show Interface Flowcontrol from Configuration Guide |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: * | Symptom:
Nexus 3000 does not have a configurable command for link flowcontrol. Thus, show interface flowcontrol is not a valid command.
The URL below shows that show interface flowcontrol is a valid command:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus3000/sw/layer2/503_U3_1/b_Cisco_n3k_Layer_2_Switching_Config_503_U31_chapter_00100.html#ref_474613599843229544
The bug requests to remove show interface flowcontrol from the above URL.
Conditions:
The bug affects Configuration Guide up to 5.0(3)U3(x).
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.0(3)U3(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux50309 | Title: | auto-recovery GAP |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
The minimum value for vPC auto-recovery timer on Nexus3500 is 240 Secs. Suggest to change to 60 Secs as Nexus7000
Conditions:
N/A
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 6.0(2)A7(1) |
|
Known Fixed Releases: | |
|
|
| |
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论