| |
|
Alert Type: | Updated * |
Bug Id: | CSCux24542 | Title: | FCoE FLOGI from NPV switch gets LS_RJT due to solicit not done |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: * | Symptom:
FCoE FLOGI from NPV switch gets LS_RJT due to solicit not done
Conditions:
Occurs when there is an FCoE NPV to NPIV link only.
Workaround:
Connect the devices involved into the NPIV switch itself.
Further Problem Description:
None.
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 6.0(2)N1(2a), 7.0(7)N1(1) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.136), 7.1(4)N1(0.701), 7.1(4)N1(1), 7.2(2)N1(0.355), 7.2(2)N1(1), 7.2(2)ZN(0.39), 7.3(0)N1(0.236), 7.3(0)N1(1), 7.3(0)ZN(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo69417 | Title: | Nexus 6000/5600: Link degraded messages seen been port and fabric ASIC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In a Nexus 6000/5600 series switches, link degraded messages such as following can be seen between port ASIC and fabric ASIC.
USER-2-SYSTEM_MSG: A fabric link on module 3 has degraded, some packets may be corrupted - bigsurusd
USER-2-SYSTEM_MSG: A fabric link on module 3 has degraded, some packets may be corrupted - bigsurusd
USER-2-SYSTEM_MSG: A fabric link on module 3 has degraded, some packets may be corrupted - bigsurusd
Conditions:
Seen during normal production. Fabric link can be degraded for other hardware related issues which this bug does
not address. The root cause for this software issue is incorrect Fabric init issue.
Workaround:
A power cycle of LEM or switch might recover if the root cause is software fabric init issue
Further Problem Description:
|
|
Last Modified: | 01-JAN-2016 |
|
Known Affected Releases: | 7.0(3)N1(0.47) |
|
Known Fixed Releases: * | 7.0(1)ZN(0.474), 7.0(4)N1(0.126), 7.0(4)N1(1), 7.1(0)N1(0.254), 7.1(0)N1(0.256), 7.1(0)N1(1), 7.1(0)ZN(0.351), 7.1(0)ZN(0.353), 7.3(0)ZN(0.190) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv65538 | Title: | STP core after bringing up VPC heartbeat and peer link |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
STP core after bringing up VPC heartbeat and peer link
Conditions:
The trigger for the crash was the turn-up of the VPC peer's heartbeat and VPC peer link
ports. Within less than a minute of the VPC peer link becoming active the
device rebooted.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 03-DEC-2015 |
|
Known Affected Releases: | 7.1(0)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCus89408 | Title: | USB HID class driver crashes the system |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: | Symptom:
A vulnerability in the USB driver of the Nexus 5000 (N5K) Series Switch could allow an unauthenticated, local attacker to perform a Denial of
Service (DoS) condition due to a kernel crash.
The vulnerability is due to insufficient handling of USB input parameters. An attacker could exploit this vulnerability by sending crafted USB
parameters to be processed by the kernel. An exploit could allow the attacker to create a Denial of Service condition on the affected device.
Conditions:
Device with default configuration.
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 4.9/4.9:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:L/AC:L/Au:N/C:N/I:N/A:C/E:H/RL:U/RC:C&version=2.0
CVE ID CVE-2015-6394 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: | 04-DEC-2015 |
|
Known Affected Releases: | 5.2(9)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux69897 | Title: | N5K/N6K vshd crash with EEM CLI regex match |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
A crash in the 'vshd' service may be observed. This will cause the switch to reboot with the reset-reason listed as "vshd hap reset".
Conditions:
This has been observed after configuring an EEM applet with an 'event cli match' parameter that does regular expression matching. Exact conditions to hit the issue are not currently known.
Workaround:
Avoid using EEM scripts that perform regular expression matching on CLI input.
Further Problem Description:
|
|
Last Modified: | 30-DEC-2015 |
|
Known Affected Releases: | 7.0(2)N1(1), 7.0(7)N1(1), 7.1(3)N1(1), 7.2(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux68524 | Title: | Process carmelusd crashes on Nexus 5k with version 7.1(1)N1(1) |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
N5K with 7.1(1)N1(1) may see process carmelusd crash
Conditions:
None
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 26-DEC-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw61934 | Title: | N5K Global DB lock after ISSU |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:After doing ISSU from 5.2(1)N1(7) to 7.0(7)N1(1) the switch-profile is locked on global DB.
Any commands on this switch, in attempt to correct the missing configurations fail with error:
"Failed: Global-db modification in progress"
Deleting the complete switch-profile on itself also fails:
# no switch-profile swprof12 profile-only local
Error: Global-db modification in progress
Conditions:Using switch profile in the N5Ks and performing an ISSU.
Workaround:There is an hidden command that can be used to release the global db lock.
#test csm csm-flag global-db-modify 0|1
The command should be used ONLY under Cisco TAC supervision.
The more elaborate steps for lock reset is given below:
To check the ref count, please execute: show system internal csm info trace | grep "ref cnt"
The output of the command should show up as given below:
Thu Mar 18 12:25:02.90010 (CSM_T) csm_sp_reset_gldb_mdfy_progress(829): Reset gldb ref cnt -1
Thu Mar 18 12:24:15.431698 (CSM_T) csm_sp_reset_gldb_mdfy_progress(829): Reset gldb ref cnt 0
Thu Mar 18 12:24:15.375479 (CSM_T) csm_sp_set_gldb_mdfy_progress(821): Set gldb ref cnt 1
Note that, the latest ref-cnt is -1, which means we are hitting the issue. It could be -2 also.
Or if due to some reasons, the above command doesn't show any ref count, you can simply try "resync-database" under conf-sync mode twice. The command will succeed for the first time and the second time it will show the global-db is locked.
To confirm it is the same issue, check the ref cnt again after resync-database.
2. Execute, test csm csm-flag global-db-modify 1
Check, show system internal csm info trace | grep "ref cnt" again and the output will look like:
Thu Mar 18 12:24:15.375479 (CSM_T) csm_sp_set_gldb_mdfy_progress(821): Set gldb ref cnt 0
If the ref-count is still negative, apply the same command again to make it zero.
Now we have made the ref count is zero, but the lock is not reset.
3. To reset the lock, Execute again, test csm csm-flag global-db-modify 1
Check, show system internal csm info trace | grep "ref cnt" again and the output will look like:
Thu Mar 18 12:24:15.375479 (CSM_T) csm_sp_set_gldb_mdfy_progress(821): Set gldb ref cnt 1
4) Finally, test csm csm-flag global-db-modify 0
Check, show system internal csm info trace | grep "ref cnt" again and the output will look like:
Thu Mar 18 12:24:15.431698 (CSM_T) csm_sp_reset_gldb_mdfy_progress(829): Reset gldb ref cnt 0
Now the ref count is zero and the lock is reset, please do a "verify" under the switch-profile to check if verification is successful.
More Info:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 7.0(7)N1(0.9) |
|
Known Fixed Releases: * | 7.1(3)N1(0.675), 7.1(3)N1(1), 7.1(3)ZN(0.87), 7.2(2)N1(0.357), 7.2(2)N1(1), 7.2(2)ZN(0.41), 7.3(0)N1(0.192), 7.3(0)N1(1), 7.3(0)ZN(0.176) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCun34005 | Title: | Nexus2k/5k/6k: Continuous memory leak messages seen for ethpm |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Possible memory leak messages for ethpm are observed.
Exemplary logs:
%$ VDC-1 %$ Feb 25 06:32:17 %KERN-2-SYSTEM_MSG: [20640.784304] [sap 175][pid 3969][comm:ethpm] WARNING: possible memory leak is detected on pers queue (len=649,bytes=15825069) - kernel
%$ VDC-1 %$ Feb 25 06:32:27 %KERN-2-SYSTEM_MSG: [20650.122663] [sap 175][pid 3969][comm:ethpm] WARNING: possible memory leak is detected on pers queue (len=647,bytes=15773045) - kernel
Conditions:
This problem was observed on the Nexus 5000 after pasting the configuration with 500+ vlans to the running-config.
Also config replay of these vlans are extremely slow (might take a few hours to complete).
Workaround:
copy the config from a temporary file to startup config and reload the switch for the configs to take effect.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(1)N1(0.106), 7.0(6)N1(0.185), 7.1(3)N1(0.647), 7.1(3)N1(0.662), 7.2(0)N1(0.111), 7.2(0)N1(0.180), 7.2(1)N1(0.313) |
|
Known Fixed Releases: | 7.3(0)N1(0.221), 7.3(0)N1(1), 7.3(0)ZN(0.198) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46009 | Title: | Nexus 802.1x: suffix delimited with @ is not sent in RADIUS request |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Username suffix delimited by '@' is stripped off in RADIUS acces-request.
Conditions:
Dot1x authentication on N5k, username contains domain name.
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 7.2(2)N1(0.1) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.136), 7.1(4)N1(0.701), 7.1(4)N1(1), 7.2(2)N1(0.355), 7.2(2)N1(1), 7.2(2)ZN(0.39), 7.3(0)N1(0.242), 7.3(0)N1(1), 7.3(0)ZN(0.219) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux63018 | Title: | fcoe fails to come up wih cfg non default native vlan not created |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
fcoe vfc interface does not complete fip vlan discovery.
Conditions:
upgrade from nx-os 5.x.x.x.x or 6.x.x.x.x to 7.x.x.x.x.
AND a non default native vlan configured on the physical
ethernet / port-channel to the fcoe end device
AND this non default native vlan is not created as a vlan on the switch
If you are doing fcoe and you are using the default native vlan, vlan 1, then you are not affectged by this issue
described here.
Workaround:
create the vlan used as native vlan on the switch. Ideally before the upgrade.
Further Problem Description:
in some rare circumstances it may be necessary to reload the switch after the vlan creation of the native vlan.
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 7.0(7)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw53377 | Title: | Nexus5672 WCCP process crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:WCCP process crash when wccp appliance disconnected and core generated
Conditions:when wccp appliance disconnected/ reconnected
Workaround:none
More Info:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 7.1(0)N1(1) |
|
Known Fixed Releases: | 7.0(7)N1(0.307), 7.0(7)N1(1), 7.1(3)ZN(0.115), 7.1(4)N1(0.689), 7.1(4)N1(1), 7.2(2)N1(0.339), 7.2(2)N1(1), 7.2(2)ZN(0.22), 7.3(0)N1(0.211), 7.3(0)N1(1) |
|
|
| |
| |
|
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: | 19-DEC-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)D1(1), 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) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv48304 | Title: | vpc hap reset during auto-config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
vpc process hap reset may occur when adding many VNIs to a VNE interface.
Conditions:
The process crash occurs when adding more than around 700 VNIs, depending on system load.
Workaround:
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 7.2(1)N1(0.272), 7.3(0)N1(0.63) |
|
Known Fixed Releases: | 7.3(0)IZN(0.7), 7.3(0)N1(0.187), 7.3(0)N1(1), 7.3(0)ZN(0.170) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul85203 | Title: | N5K Port in Internal-Fail errDisable : fu ha standby message queued |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
N5k Port connected to N1110X goes to "Internal-Fail errDisable" state if the N1110 Appliance is powered off for HA Testing.
-----
this symptom will also happen when partner device is nexus.
Conditions:
Nexus 5000 ( 5548 )
Ver : 6.0(2)N2(1)
Feature LLDP is turned off
Feature FCoE is turn on
Workaround:
Turn on LLDP
Further Problem Description:
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: * | 6.0(2)N2(1), 7.3(0)N1(0.141) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub48265 | Title: | B22 fex 10gig HIF port auto negotiates to 1gig during init server bootup |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
HP B22 FEX Host Interface ports going to server auto negotiate to 1gig during
initial link bringup ie when the blade chassis server is rebooted or installed.
Conditions:
Nexus 5000 series switch connected to B22 FEX. Issue is seen with multiple
10gig NIC Card Vendors.
Issue does not happen in following releases:
5.1.3.N1.1
5.1.3.N1.1a
Issue happens in the following releases:
5.1.3.N2.1
5.1.3.N2.1a
5.2.1.N1.1
Workaround:
- shut/ no shut the port
- hardcode the port for 'speed 10000'
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1(3)N2(1) |
|
Known Fixed Releases: | 5.1(3)N2(1b), 5.2(1)N1(1b), 6.0(2)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub20658 | Title: | N5K: Task netstack hogs cpu leading system processes to crash |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
N5K Crashs
SYSMGR-3-HEARTBEAT_FAILURE: Service "lldp" sent SIGABRT for not setting heartbeat for last 4 periods.
SYSMGR-2-SERVICE_CRASHED: Service "lldp" (PID xxxx) hasn't caught signal 6 (core will be saved).
Last reset at XXXXXX usecs after XXXXXXXXXXXXXXXXX
Reason: Reset triggered due to HA policy of Reset
System version: 5.0(3)N2(2a)
Service: lldp hap reset
This issue is very rare.
Conditions:
Taking TAC-PAC or show-tech
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.0(3)N2(2a) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw48559 | Title: | Nexus 5K: Change fan detection logic |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In Nexus 55xx switches, fans stop getting detected by the switch even though the fans are present in the system and spinning. if this condition is hit, messages such as following will be printed and the switch will shut down even though the fans are present and spinning.
2015 Mar 19 22:13:44.791 Nexus5548UP %$ VDC-1 %$ %NOHMS-2-NOHMS_ENV_ERR_FAN_DOWN: System minor alarm on fans: One fan missing or failed
2015 Mar 19 22:13:44.792 Nexus5548UP %$ VDC-1 %$ %PFMA-2-PFMA_FAN_REMOVED: Fan module 1 N5548P-FAN removed
2015 Mar 19 22:13:45.015 Nexus5548UP %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in 60 seconds due to fan removal
2015 Mar 19 22:13:45.015 Nexus5548UP %$ VDC-1 %$ %NOHMS-2-NOHMS_ENV_ERR_FANS_DOWN: System major alarm on fans: Multiple fans missing or failed
2015 Mar 19 22:13:45.017 Nexus5548UP %$ VDC-1 %$ %PFMA-2-PFMA_FAN_REMOVED: Fan module 2 N5548P-FAN removed
2015 Mar 19 22:13:50.012 Nexus5548UP %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in 55 seconds due to fan removal
2015 Mar 19 22:13:55.013 Nexus5548UP %$ VDC-1 %$ %PFMA-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in 50 seconds due to fan removal
Conditions:
Unknown
Workaround:
None
Further Problem Description:
The problem is seen due to system micro-controller not seeing fans even though it records the fan speed RPM. As part of this bug fix, the fan detection logic has been made more robust by also looking at RPM readings.
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 5.2(1)N1(7) |
|
Known Fixed Releases: * | 7.0(7)N1(0.307), 7.0(7)N1(1), 7.1(3)N1(0.656), 7.1(3)N1(1), 7.1(3)ZN(0.64), 7.2(2)N1(0.5), 7.2(2)N1(1), 7.3(0)N1(0.195), 7.3(0)N1(1), 7.3(0)ZN(0.178) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux06997 | Title: | inherit port-profile fails due to vpc orphan-port suspend |
|
Status: | Fixed |
|
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: | 07-DEC-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.3(0)N1(0.219), 7.3(0)N1(1), 7.3(0)ZN(0.196) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur29789 | Title: | N5k/N6k might unexpectedly reload due to "eth_port_sec hap reset" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
N5k/N6k might unexpectedly reload due to "eth_port_sec hap reset"
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: * | 6.0(2)N2(5), 7.0(4)N1(0.148) |
|
Known Fixed Releases: | 7.0(1)ZN(0.724), 7.0(6)N1(0.227), 7.0(6)N1(1), 7.1(0)N1(0.398), 7.1(0)N1(1), 7.1(0)ZN(0.473), 7.1(1)N1(0.17), 7.1(1)N1(1), 7.2(0)AB(9), 7.2(0)N1(0.137) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40608 | Title: | Nexus 5K FCoE NPV switch not sending FLOGI to NPIV switch on port VSAN |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Nexus 5000 NPV sends FCoE FLOGI to the NPIV core switch on the highest VSAN allowed on the TNP (trunking NP port) instead of on the VFC's VSAN as in the VSAN database.
Conditions:
Occurs when Nexus 5000 is running in NPV mode with an FCoE uplink to the NPIV core switch.
Workaround:
None.
Further Problem Description:
It appears that the NPV switch sends the FCoE FLOGI upstream using the highest VSAN allowed on the trunk. Not the VFC's port VSAN like it should.
Resolution Summary:
To be determined once resolved.
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 7.0(7)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw99621 | Title: | Kokomo: Unable to clear full mac table after limit |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
"clear mac address-table dynamic" command may not clear all the mac address-table in single attempt.
Conditions:
Mac address table reaches the limit which gives the following warning message "%$ VDC-1 %$ %FWM-2-STM_LIMIT_REACHED: Unicast station table dynamic capacity reached (limit 123305)"
Workaround:
Try "clear mac address-table dynamic" multiple times.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.191) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv61110 | Title: | N5K/N6K: Errors when modifying vlan allowed list in port-profile on FEX |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On a Nexus 5000 or 6000 Series Switch, modification to an existing vlan allowed list in a port-profile can cause other VLANs in that list to be briefly removed and reconfigured. In vPC deployments, the peer will show vlans were suspended with "Reason: Vlan is not configured on remote vPC interface." This is immediately followed by the vlans being removed from the suspended state and should not cause any packet loss.
Conditions:
When the vlan allowed list within a port-profile exceeds 80 characters (including all text in the command) and the port-profile is inherited by a FEX HIF on 7.x code.
Workaround:
Use vlan ranges (-) to ensure the command does not exceed 80 characters in the running config or manually apply the config to the FEX HIF instead of via port-profile.
Further Problem Description:
|
|
Last Modified: | 11-DEC-2015 |
|
Known Affected Releases: | 7.0(5)N1(1), 7.1(1)N1(1), 7.2(0)N1(1) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.125), 7.1(4)N1(0.690), 7.1(4)N1(1), 7.2(2)N1(0.347), 7.2(2)N1(1), 7.2(2)ZN(0.30) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug92414 | Title: | SVI can go down corresponding vlan active on FlexLink only |
|
Status: | Fixed |
|
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: | 19-DEC-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)GLF(0.43), 7.3(0)IB(0.122), 7.3(0)N1(0.197), 7.3(0)N1(0.199), 7.3(0)N1(1), 7.3(0)PDB(0.112), 7.3(0)SC(0.14), 7.3(0)ZD(0.165), 7.3(0)ZN(0.180) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw27142 | Title: | Need CLI to clear snmp counters for Nexus switches |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
In Device Manager GUI for a Nexus switch, summary error counters are not cleared when corresponding interface counters are cleared via CLI.
Conditions:
Interface counters for FC interfaces are showing up in Summary window of Device Manager and can't be cleared in any way.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 07-DEC-2015 |
|
Known Affected Releases: | 5.2(1)N1(9) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub77421 | Title: | POAP fails saving config due to L3 module being in power-up state |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Poap process may fail at final step when saving running-configuration to startup-configuration with message
Copy complete, now saving to disk (please wait)...
Configuration update aborted: system not ready
The Poap process will abort and start over from the beginning.
Conditions:
Condition can be intermittent, and not fail each time.
One cause of the failure is that the L3 module installed in the chassis is still initializing when the configuration save is attempted. This results in the save failing as the system is not in a stable condition.
Testing also showed that if the poap process detects the images named in the script are not present on the bootflash: and must be downloaded as part of the poap process, that the timing of the configuration save is different and this problem may not occur.
Workaround:
Once in this condition, the only way to resolve it is to attach a console to the N5K and manually abort the poap process. Once you set the admin password, and then log into the N5K, you will likely see that the running-configuration matches the configuration in the file that was downloaded by the poap process. The startup-configuration will be empty. Once the L3 module shows 'ok' status, you can issue the command 'copy running-configuration startup-configuration' to complete the N5K setup. It will be stable at this point, as once there is a startup-configuration file, the poap process is bypassed for all subsequent reloads. (assuming a 'write erase' has not been performed)
|
|
Last Modified: | 29-DEC-2015 |
|
Known Affected Releases: | 5.2(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua34584 | Title: | ISSU failed ER to GC, Maximum down time exceeded due to hw clock change |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ISSU may fail with the following error causing reload of the switch. ISSU from any software prior 5.1(3)N2(1b) may hit this problem
switch# show system reset-reason
----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---
1) At 229369 usecs after Thu Jul 12 22:01:39 2012
Reason: Reset Requested due to Fatal System Error
Service: ISSU failure: 0x4093003B
In the output of "show install internal logs" we see a negative time for the control plane being down.
is_fs_upg_bootup_time_exceeded: Total time control plane was down: -1342143738 seconds
is_fs_upg_bootup_time_exceeded: Total time between control plane being down and fspf restoring state and handshaking: -1342143739 seconds
is_fs_upg_bootup_time_exceeded: Total time taken between control plane being down and box online: 1150 seconds
boot_installer: Unacceptable bootup time- printing warning.
installer_state_change: installer_state_change: old_state: INSTALLER_BOOT_STATE_INIT, new_state: INSTALLER_STATE_REBOOT_FS_UPG_FAILURE
Conditions:
None.
Workaround:
None.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1(3)N1(1), 5.2(1)N1(0.195) |
|
Known Fixed Releases: * | 5.1(3)N2(1b), 5.2(1)N1(1a), 7.3(0)ZN(0.190) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua65570 | Title: | Nexus 5596UP and 5548UP discovery over UDP from FM or DCNM fails |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Can not discover 5596UP or 5548UP via DCNM-SAN using UDP.
Same problem with Fabric Manager and UDP.
Error Message: Validate seed switch failed.
Cannot verify seed switch from SNMP:timeout
Conditions:
Using DCNM-SAN or Fabric Manager to discover the Nexus switch using UDP instead of TCP.
DCNM-SAN can be configured to use UDP by setting "snmp.preferTCP=false" in "server.properties" for FM or in Admin > Properties in the DCNM Web Client.
Workaround:
Use TCP ( the default ) for DCNM or FM instead of UDP.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.1(3)N2(1) |
|
Known Fixed Releases: | 5.2(1)N1(3), 6.0(2)A1(1), 6.0(2)N1(1), 6.0(2)U1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua55506 | Title: | IPv6 ND fails for v6 address which were on SVI but moved to hosts |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
In a Nexus 5000/5500, IPv6 neighbor discovery might fail for IPv6 hosts.
Conditions:
This is seen for hosts whose IPv6 addresses were configured on VLAN interface but removed later on and moved to hosts in the network.
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: * | 5.1(3)N1(1a), 5.1(3)N2(1) |
|
Known Fixed Releases: | 5.2(1)N1(4), 6.0(2)A1(1), 6.0(2)N1(1), 6.0(2)U1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw89463 | Title: | MTS buffer leaks for mcecm on the peer device with MCT flap |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Observed MTS buffer leaks on vPC secondary device with MCT flap
Conditions:
On a vPC setup, mts buffer leaks for vPC SAP (450) are seen after flapping MCT on vPC primary repeatedly around 20 times.
Workaround:
No workaround exists.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.177) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.137), 7.1(4)N1(0.702), 7.1(4)N1(1), 7.2(2)N1(0.356), 7.2(2)N1(1), 7.2(2)ZN(0.40), 7.3(0)N1(0.211), 7.3(0)N1(1), 7.3(0)ZN(0.190) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub52777 | Title: | config-sync-if mode in switch-profile configuration |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Unexpected config mode without entering into the particular switch-profile:
Nexus5k(config-sync)# interface Ethernet101/1/1
Nexus5k(config-sync-if)# description test
Nexus5k(config-sync-if)# switchport access vlan 10
Error: Command is not mutually exclusive
Nexus5k(config-sync-if)# verify
Verification Successful
Conditions:
n/a
Workaround:
n/a
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 5.0(3)N1(1c) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuo24670 | Title: | N5K/FEX FEX Interface Incrementing output discards rapidly |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
A high amount of output discards seen in "show interface" output:
26940307856 output discard
These are incrementing very rapidly, 10,000s per second on a connected interface in UP state.
This issue can also be seen on ports which are in down state.
Conditions:
N5K 5596 running 5.2(1)N1(1) with N2K-C2248TP-E-1GE connected
Workaround:
None identified at this time, but these can be ignored as this is a cosmetic issue.
Further Problem Description:
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 5.2(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut94326 | Title: | Nexus 5596UP as FC switch: cannot change FSPF cost under fc interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Not able to change fspf cost of a fc interface.
Conditions:
Will be updated once root cause is found.
Workaround:
Will be updated once root cause is found.
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 7.2(0.1), 7.3(0)N1(0.150) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.126), 7.1(4)N1(0.691), 7.1(4)N1(1), 7.3(0)IZN(0.7), 7.3(0)N1(0.174), 7.3(0)N1(1), 7.3(0)ZN(0.159) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw83480 | Title: | show-fan displays rpm value as 0x0 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
show-fan dbgsh satctrl command shows rpm value as 0x0
satctrl/env> show-fan
Fan present: yes
Fan online : 3
speed : 100 %
spin status: 0x0
rpm: 0x0
Fan present: no
Fan online : 0
speed : 40 %
spin status: 0x0
rpm: 0x0
Fan present: no
Fan online : 0
speed : 40 %
spin status: 0x0
rpm: 0x0
Fan present: no
Fan online : 0
speed : 40 %
spin status: 0x0
rpm: 0x0
Conditions:
issue is seen in ZEPHYR_VE fex
Workaround:
No
Further Problem Description:
rpm value is not updated after initialization in satctrl_woo_prt_hw_get_fan_spin.
After we read RPM value for fan we need to update satctrl_fan global struct
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.177) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.126), 7.1(4)N1(0.691), 7.1(4)N1(1), 7.2(2)N1(0.347), 7.2(2)N1(1), 7.2(2)ZN(0.30), 7.3(0)IZN(0.7), 7.3(0)N1(0.190), 7.3(0)N1(1), 7.3(0)ZN(0.173) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75517 | Title: | Add transceiver direction information to entPhysicalName OID |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
Direction (transmit/receive) information from transceiver sensor is not provided in entPhysicalName OID description.
iso.3.6.1.2.1.47.1.1.1.1.7.25827 = STRING: "Ethernet1/1(dBm)"
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.25827 = INTEGER: -3223
iso.3.6.1.2.1.47.1.1.1.1.7.25828 = STRING: "Ethernet1/1(dBm)"
iso.3.6.1.4.1.9.9.91.1.1.1.1.4.25828 = INTEGER: -2291
Conditions:
Problem seen with N5K/N6K 7.1 release.
Workaround:
None
Further Problem Description:
Enhancement to ENTITY-MIB entPhysicalName OID (iso.3.6.1.2.1.47.1.1.1.1.7) to include direction (transmit/receive) information from transceiver sensor
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: * | 7.1(3)N1(0.674), 7.1(3)N1(1), 7.1(3)ZN(0.86), 7.2(2)N1(0.351), 7.2(2)N1(1), 7.2(2)ZN(0.36), 7.3(0)N1(0.192), 7.3(0)N1(1), 7.3(0)ZN(0.176) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux61137 | Title: | Nexus 5600: command "no fex queue-limit" is not saved |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: | Symptom:
+ After saving the configuration too, the line "no fex queue-limit" under "system qos" does not show up in startup-config.
+ After reload too, the line "no fex queue-limit" shows up only in "show run ipqos" and "show run all", but not in "show run" or "show start".
+ After multiple reloads too, the non-default configuration line "no fex queue-limit" under "system qos" shows up only in "show run ipqos" and "show run all", but it never shows up in "show run" or "show start".
Conditions:
none
Workaround:
none
Further Problem Description:
there is difference between running-config anf startup config, this line "no fex queue-limit" is not synchronized the startup-config even after saving the running-config.
|
|
Last Modified: | 18-DEC-2015 |
|
Known Affected Releases: | 7.1(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt19787 | Title: | support for ACL object-groups on 5k |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Not able to configure object-groups
Conditions:
Support for IP ACL object-groups on N5k platform.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 19-DEC-2015 |
|
Known Affected Releases: | 5.0(3)N1(1b), 7.2(0)N1(0.19) |
|
Known Fixed Releases: * | 7.3(0)BZN(0.47), 7.3(0)D1(0.79), 7.3(0)EG(0.3), 7.3(0)IB(0.67), 7.3(0)MMD(0.9), 7.3(0)N1(0.105), 7.3(0)N1(0.115), 7.3(0)N1(1), 7.3(0)OTT(0.32), 7.3(0)PDB(0.45) |
|
|
| |
:
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论