| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo10325 | Title: | igmp snooping flooded on stp blocking after stp change |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:IGMP reports are forwarded to router ports even if the port is in blocking state
Conditions:Can happen if the port was originally in forwarding state and was learnt as a router port. And some change in STP topo causes the router port to go into blocking state. But the port is not removed from IGMP snoopings router port list. So until the router port gets timed out, any report received on this vlan, will be forwarded out of this blocked port as well.
Workaround:Forwarding over blocked ports will stop once the router port gets timed out. If this is not acceptable, then disable IGMP snooping for the problem vlan.
More Info:Note that the fix will not work if upgrading to an image with the fix using ISSU. It will only work if switch is reloaded and booted up with an image that has the fix. If switch is running an image which doesn't have the fix, and is upgraded to an image which has the fix using non-disruptive ISSU, then this fix will not work. If for some reason ISSU is the only way switches can be upgraded, please contact Cisco support to help provide steps which would avoid this IGMP loop issue.
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 5.1(3)N2(1a) |
|
Known Fixed Releases: * | 5.2(1)N1(7.114), 5.2(1)N1(8), 6.0(2)N2(5.94), 6.0(2)N2(6), 7.0(0)BZ(0.46), 7.0(0)HSK(0.317), 7.0(0)KM(0.97), 7.0(1)ZD(0.254), 7.0(1)ZN(0.511), 7.0(1)ZN(0.523) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud56630 | Title: | not able to unload mib using 'no snmp-server load-mib' command |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In NX-OS release 5.2 or 6.x we are unable to unload the mibs using command no snmp-server load-mib
Conditions:
Trying to remove one of the loaded mibs on the nexus switch. Use command show snmp internal loaded mibs to view the list of loaded mibs.
Workaround:
Stop polling the respective mib from snmp server.
Further Problem Description:
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: | 6.0(0)N1(0.53), 7.2(1)N1(0.259) |
|
Known Fixed Releases: * | 7.2(1)D1(0.10), 7.2(1)D1(0.44), 7.2(1)N1(0.243), 7.2(1)N1(0.277), 7.2(1)N1(1), 7.2(1)ZD(0.38), 7.2(1)ZD(0.8), 7.2(1)ZN(0.41), 7.2(1)ZN(0.9), 7.3(0)D1(0.94) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv03880 | Title: | Nexus 5696 Cant display DOM of TX RX power reading WSP-Q40GLR4L |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
F340.12.22-N5K-C5696-1# sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 2.1.0
Power Sequencer Firmware:
Module 1: v1.0
Module 1: v1.0
Module 2: v1.0
Module 8: v2.0
Fabric Power Sequencer Firmware: Module 0: version v3.0
Microcontroller Firmware: version v1.2.2.0
QSFP Microcontroller Firmware:
Module 1: v1.7.0.0
Module 2: v1.7.0.0
CXP Microcontroller Firmware:
Module not detected
kickstart: version 7.1(1)N1(1)
system: version 7.1(1)N1(1)
BIOS compile time: 09/01/2014
kickstart image file is: bootflash:///n6000-uk9-kickstart.7.1.1.N1.1.bin
kickstart compile time: 4/18/2015 10:00:00 [04/18/2015 20:23:20]
system image file is: bootflash:///n6000-uk9.7.1.1.N1.1.bin
system compile time: 4/18/2015 10:00:00 [04/18/2015 20:24:07]
Hardware
cisco Nexus 5696 Chassis ("Nexus 5696 Supervisor")
Intel(R) Xeon(R) CPU @ 1.80 with 16511900 kB of memory.
Processor Board ID FOC1832A5AE
Device name: F340.12.22-N5K-C5696-1
bootflash: 7864320 kB
Kernel uptime is 0 day(s), 1 hour(s), 24 minute(s), 47 second(s)
Last reset
Reason: Unknown
System version: 7.1(1)N1(1)
Service:
plugin
Core Plugin, Ethernet Plugin
sh module
F340.12.22-N5K-C5696-1# sh module
Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ---------------------- -----------
0 0 Nexus 5696 Supervisor N5K-C5696Q-SUP active *
1 12 Nexus 5696 12xQSFP Ethernet Module N5696-M12Q ok
2 12 Nexus 5696 12xQSFP Ethernet Module N5696-M12Q ok
8 20 Nexus 5696 20xUnified Port Module N6004X-M20UP ok
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ ---------------------------------------------------
0 7.1(1)N1(1) 1.0 --
1 7.1(1)N1(1) 1.0 --
2 7.1(1)N1(1) 1.0 --
8 7.1(1)N1(1) 1.0 --
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
0 002a.6aed.3900 to 002a.6aed.391f FOC1832A5AE
1 ccd8.c180.51a8 to ccd8.c180.51b7 FOC18330H0X
2 0c68.0311.bb28 to 0c68.0311.bb37 FOC18330GPB
8 dca5.f4e1.70d0 to dca5.f4e1.70df FOC18038YLR
F340.12.22-N5K-C5696-1# sh int eth 2/1 transceiver details
Ethernet2/1
transceiver is present
type is WSP-Q40GLR4L
name is CISCO
part number is FTL4C1QL1C-C1
revision is A
serial number is FNS18440G0S
nominal bitrate is 10300 MBit/sec
Link length supported for SMF fiber is 2 km
cisco id is --
cisco extended id number is 208
SFP Detail Diagnostics Information (internal calibration)
----------------------------------------------------------------------------
Current Alarms Warnings
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.620), 7.1(3)N1(1), 7.1(3)ZN(0.27), 7.2(1)N1(0.298), 7.2(1)N1(1), 7.2(1)ZN(0.62), 7.3(0)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun45981 | Title: | L3 N5K: Inbound and output ICMP frames on different ports |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ICMP Echo Request and Reply using different Inband ports.
For N5k/N6k this is observed since 7.x releases. While for N6k this may be observed in 6.x releases as well.
Conditions:
Ethanalyzer capture shows ICMP Requests coming from network are seen in Inband-Low Q, while reply is seen in Inband-Hi Q
Workaround:
ICMP flows might now have to be tracked on both Inband ports till this is fixed. There is no impact in respect to handling of traffic.
Further Problem Description:
|
|
Last Modified: | 07-OCT-2015 |
|
Known Affected Releases: | 7.0(0)N1(1) |
|
Known Fixed Releases: * | 7.0(7)N1(0.287), 7.0(7)N1(1), 7.0(7)ZN(0.166), 7.0(7)ZN(0.167), 7.1(0)AV(0.38), 7.1(0)PDB(0.317), 7.1(0)SIB(99.82), 7.1(2)N1(0.549), 7.1(2)N1(1), 7.1(2)ZD(0.6) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc24181 | Title: | output discards are seen in vfc interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom
show interface vfc shows output discards that increment slowly, but constantly.
Conditions
Adapter-FEX setup
Workaround
none. The discards are cosmetic in nature. No operational impact and do not impact data traffic.
|
|
Last Modified: | 08-OCT-2015 |
|
Known Affected Releases: * | 5.2(1)N1(4), 6.0(2)N1(0.329) |
|
Known Fixed Releases: | 5.2(1)N1(6), 6.0(2)A1(1), 6.0(2)U1(1) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw54656 | Title: | N5672 Crash Reason: statsclient hap reset; No core file -Silent Reload |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | $
Symptom:
N5672 Running 7.0.5.N1.1 crash with reason Statsclient hap reset, no core file generated
Conditions:
Silent Reload on N5672 with 7.0.5.N1.1
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 7.0(5)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf02755 | Title: | fctrace stops working to local attached fc stations after some time |
|
Status: * | Terminated |
|
Severity: | 3 Moderate |
Description: | fctrace command on a N5596UP switch may stop to work after some time of operation.
Workaround:
None.
Please note. fctrace command is tool to check connectivity but is not used for basic fc forwarding.
|
|
Last Modified: | 29-OCT-2015 |
|
Known Affected Releases: | 5.0(3)N2(2a) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw31547 | Title: | N5k/N6k stale param-lists in config which user cannot |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
customer is unable to delete stale param-list manually with the no command:
Leaf11(config)# no param-list param_list_name_instance_vni_30000_205
ERROR: Parameter instance being used cannot be deleted
Leaf11(config)# no param-list param_list_name_instance_vni_30004_4
ERROR: Parameter instance being used cannot be deleted
Leaf11(config)# no param-list param_list_name_instance_vni_30006_2
Conditions:
Workaround:
copy config in text program,modify it and then copy modified config file directly in startup and reload
Further Problem Description:
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.671), 7.1(3)N1(1), 7.3(0)N1(0.151), 7.3(0)N1(1), 7.3(0)ZN(0.139) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw28430 | Title: | Disabling password strength-check does not take effect |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On a Nexus 5000/5500/5600/6000, disabling password strength-check may still cause weak passwords to be rejected.
Conditions:
This is seen after configuring 'no password strength-check'.
Workaround:
Use strong passwords.
Alternatively, copy pasting the encrypted password directly from a different device also is accepted.
Further Problem Description:
|
|
Last Modified: | 23-OCT-2015 |
|
Known Affected Releases: | 7.1(0)N1(1), 7.1(1)N1(1), 7.2(0)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.640), 7.1(3)N1(0.645), 7.1(3)N1(1), 7.1(3)ZN(0.53), 7.2(2)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut75399 | Title: | update rdecode.sh to support n3k/5k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Some nexus platforms lack the tooling necessary to decode tracebacks.
Conditions:
This was seen for nexus 3k, 5k, and 6k.
Workaround:
Further Problem Description:
|
|
Last Modified: | 28-OCT-2015 |
|
Known Affected Releases: | 7.0(4)N1(1) |
|
Known Fixed Releases: | 7.1(2)N1(0.544), 7.1(2)N1(1), 7.1(2)ZD(0.3), 7.1(2)ZN(0.3), 7.2(1)D1(0.1), 7.2(1)PIB(0.4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur61078 | Title: | Unicast TX and RX counters incrementing on HIF without traffic |
|
Status: * | Other |
|
Severity: * | 4 Minor |
Description: | Symptom:
Unicast TX and RX counters kept incrementing on BBC HIF ports even after traffic was stopped.
Even after shutting the port, unicast TX and RX counters kept incrementing.
Conditions:
n/a
Workaround:
Further Problem Description:
|
|
Last Modified: | 21-OCT-2015 |
|
Known Affected Releases: | 7.1(0)N1(0.386) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug81375 | Title: | N5K : (Command Parsing Failed) when trying to add vlan to a trunk |
|
Status: | Other |
|
Severity: | 4 Minor |
Description: * | Symptom:
when trying to add/remove a vlan on a trunk port on a N5000-switch,
you sometimes might see following error-line:
Warning: Failed saving command: (Command Parsing Failed)
However the trunk vlan allowed list is still correctly changed as result,
so purely cosmetic
Conditions:
seen on one N5010 switch running 5.2(1)N1(2a)
Basically seen when removing trunk allowed vlan add 125 and then adding a vlan(Below).
switch(config-if)# no switchport trunk allowed vlan add 125
switch(config-if)# switchport trunk allowed vlan add 35
Warning: Failed saving command: (Command Parsing Failed)
switch(config-if)#
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 5.2(1)N1(2a) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw50408 | Title: | "ETHPORT-3-IF_NON_CISCO_TRANSCEIVER: Non-Cisco" for some twinax cables |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: * | Symptom:
The following error message is observed in the log:
%ETHPORT-3-IF_NON_CISCO_TRANSCEIVER: Non-Cisco transceiver on interface Ethernet is detected
The SFP shows find in "show interface transceiver" and the port is up and passing traffic, though.
Conditions:
This has been observed with the following Twinax transceiver model:
type is SFP-H10GB-CU3M
name is CISCO-LOROM
part number is LRHSPB54D030
revision is B0
Workaround:
None - not service impacting. Just ignore the message.
Further Problem Description:
|
|
Last Modified: | 05-OCT-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus53253 | Title: | N5K/N6K don't return expected results for cieIfDot1dBaseMappingPort |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
Nexus 5000/6000 series switches don't return expected values for cieIfDot1dBaseMappingPort from CISCO-IF-EXTENSION-MIB
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-OCT-2015 |
|
Known Affected Releases: | 7.1(0)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
:
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论