| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy39925 | Title: | polaris-16.2 BLE Beacons, wcm crash, spectrumProcessIDRDataInformation |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
Crash is observed and core file for RP WCM is generated after this event:
XXXXX_RP_0_wcm_XXXXX_XXXXXXXX-XXXXXX-XXX.core.gz
Conditions:
Crash is effect of internal memory buffers translation for incoming traffic.
Workaround:
none possible
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: * | 16.1(2.57), 16.2(0.306), 16.3(0.104), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux98348 | Title: | LACP ping is failing |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
LACp ping is failing
Conditions:
ping
Protocol [ip]: ip
Target IP address: 1.2.1.2
Repeat count [5]: 100
Datagram size [100]: 64
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 1.2.1.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]: n
Type escape sequence to abort.
Sending 100, 64-byte ICMP Echos to 1.2.1.2, timeout is 2 seconds:
Packet sent with a source address of 1.2.1.1
......................................................................
..............................
Success rate is 0 percent (0/100)
cat3750#
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.2(0), Denali-16.1.2, Denali-16.2.1 |
|
Known Fixed Releases: * | 16.1(2.22), 16.2(0.295), 16.3(0.94), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy24302 | Title: | NGWC CMM doesn't allow to change config despite MA has no MC config |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
NGWC switch cannot create/modify ACLs due to be a Centrally Managed MA, despite no wireless configuration.
Centrally Managed MA: "ip access-list extended A" cannot be locally configured.
CMM config is still applied despite of no MC configured.
sh wireless mobility summary | i Central
Central Management : Disabled
sh cmm config
Current version number: 5
Centrally Managed: True
Conditions:
NGWC switches that were centrally Managed MA, after remove MC config and wireless mgmt interface to use it as a standalone switch.
Workaround:
Configure the switch as MC: wireless mobility controller (requires reload)
When it comes back configure it back to MA: no wireless mobility controller (requires reload)
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 10.3(110.0) |
|
Known Fixed Releases: * | 15.2(3)E4, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz24650 | Title: | Mobility Agent "Cannot be locally configured-Centrally managed MA" |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
Mobility Agent "Cannot be locally configured-Centrally managed MA"
Conditions:
Add MA into MC.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 10.3(132.31) |
|
Known Fixed Releases: * | 15.2(3)E4, 16.3(0.194), 16.4(0.12), 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw06439 | Title: | 3850 does not assign/remove SGT tag to ARP traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
--- ARP replies are tagged, phone/pc cannot install arp entry because of it
Conditions:
--- 3850 3.7.2 (Beni) and 3.6.3(Amur)
Workaround:
--- on the port toward upstream switch remove "trusted" keyword and cts manual.
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 3.6(0), 3.7(0) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 3.6(4)E, 3.6(5)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy64901 | Title: | SMD crash on active switch, maroon malloc related |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
switch crashes with SMD when APs and clients are dis-associated.
Conditions:
maroon malloc is enabled for SMD process
Workaround:
Use "sh plat sof memory smd sw ac r0" to debug memory issues for these 3 processes.
Further Problem Description:
|
|
Last Modified: | 28-JUN-2016 |
|
Known Affected Releases: * | Denali-16.2.1, Denali-16.2.2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux32504 | Title: | DHCP client in native vlan do not receive an ip address |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Users in native vlan do not receive an ip address when DHCP Snooping is enabled but it is not enabled in the vlan 1
If DAI is configured in other vlans but vlan 1 following log is observed:
%SW_DAI-4-DHCP_SNOOPING_DENY: 1 Invalid ARPs (Req) on Gi2/0/1, vlan 20.([38ed.18e8.b38d/10.176.43.76/0000.0000.0000/10.176.43.1/20:55:45 CDT Sat Sep 19 2015])
Symptom:
Users in vlan 1 do not receive an ip address when DHCP Snooping is enabled but it is not enabled in the native vlan.
If DAI is configured in other vlans but native following log is observed:
%SW_DAI-4-DHCP_SNOOPING_DENY: 1 Invalid ARPs (Req) on Gi2/0/1, vlan 20.([38ed.18e8.b38d/10.176.43.76/0000.0000.0000/10.176.43.1/20:55:45 CDT Sat Sep 19 2015])
Conditions:
DHCP Client----L2 3850-----Router(which contains the DHCP relay)-------- DHCP Server
Router on a stick configuration between switch and router.
Issue was found in 03.06.03E version.
Workaround:
- Toggling dhcp snooping for vlan 1 on and off.
- Disable DHCP Snooping globally
- Use any other Vlan then Vlan 1 for DHCP clients
- Upgrade to 3.7.0 or later that does not have this problem
- enable DHCP snooping on Vlan 1
Further Problem Description:
|
|
Last Modified: | 02-JUN-2016 |
|
Known Affected Releases: | none |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 15.2(5.1.22i)E, 3.6(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw38233 | Title: | Mobility tunnel between MA/MC drops when default egress policy is deny |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Wireless mobility control link goes down, but mobility data link is up
Conditions:
When cts role based enforcement is configured on any vlan, other than wlan
Workaround:
Allow CAPWAP traffic in the default rule ACL like below:
Permit udp dst eq 5246
Permit udp dst eq 5247
Permit udp src eq 16666 dst eq 16666
Deny ip
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 3.6(2)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 3.6(4)E, 3.6(5)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux22760 | Title: | On reload, 1G SFP is connected/up on 3750x while 3850 is notconnect/down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Topology: 3850-12S downlink port connected to uplink port of 3750X using 1G SFP.
Now on reload of 3850, 1G SFP is connected/up on 3750x while 3850 is notconnect/down.
Conditions:
Topology: 3850-12S downlink port connected to uplink port of 3750X using 1G SFP.
Now on reload of 3850, 1G SFP is connected/up on 3750x while 3850 is notconnect/down.
Workaround:
No Workaround
Further Problem Description:
The defect is fixed in Polaris dev and amur mr4 (3.6.4) and beni mr4 (3.7.4)
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(2)E3 |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 16.1(2.62), 16.2(0.199), 3.6(4)E, 3.6(5)E, 3.7(4)E, Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux19272 | Title: | FED crash at fed_init_l3if_stats |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A switch member is not able boot up and generates a FED corefile eachtime.
Conditions:
The switch is booting up to join a stack
Workaround:
None at this time
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 3.6(4)E, 3.6(5)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj10443 | Title: | Standby sw crash@crypto_engine/sw/src/keylib/lib_key_storage.c:646 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Switch crashes when being added to stack after switchoer
Conditions:
This occurs in switchover scenarios
Workaround:
Reload the complete stack and boot again.
Further Problem Description:
|
|
Last Modified: | 22-JUN-2016 |
|
Known Affected Releases: | 15.0(11.98)EMP, 15.0(12.3)EMP, 15.2(2.2.94)E |
|
Known Fixed Releases: * | 12.2(60)EZ2, 12.2(60)EZ3, 15.0(1)EZ, 15.0(1)EZ1, 15.0(12.14)EZD, 15.0(14.1)TSR, 15.0(14.49)EZD, 15.0(2)EX5, 15.0(2)EX7, 15.0(2)SE7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw19798 | Title: | GRE Tunnel not working on Catalyst 3850 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
2 Cisco Catalyst 3850 cannot ping each other using a GRE Tunnel.
Conditions:
1) Catalyst 3850 configured with GRE Tunnels.
2) IP Routing command enabled.
Workaround:
Upgrade IOS-XE version to get the fix for this bug.
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E5, 15.2(3)E3, 3.6(5)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy53713 | Title: | NGWC / 3850 / not responding to Multicast Pings |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
3850 / 3650 dont respond to Multicast Pings.
Note: with the Fix integrated, ip multicast-routing needs to be enabled in order for this to work.
Conditions:
None
Workaround:
None
Further Problem Description:
while troubleshooting OSPF/PIM/etc, we may need to ping the far end device with their link local Multicast address (like 2224.0.0.5 / 224.0.0.13 / etc).
when doing it against 3850/2650, they dont respond, causing it difficult to troubleshoot Routing protocols issues.
it doesnt even respond if IGMP join-group is configured under any SVI/L3 interface making it complex to troubleshoot Multicast deployment scenarios
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.0(1)EZ3, 15.2(2)E |
|
Known Fixed Releases: * | 15.2(2)E5, 15.2(3)E4, 16.3(0.151), 3.6(5)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz48487 | Title: | 3850 dropping MACSEC traffic |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
ICMP packets drops from ASR1 to ASR2 passing through the 3850, displaying "show plat fwd drop exceptions" we see IGR_MISC_FATAL_ERROR increasing on 3850 switch on the ASIC 1 (Gi3/0/1, Gi3/0/2). Rate of ingress errors appear to be closely related to the pings of the test. Due both ports where on the same ASIC, it is not clear to see if the packets are lost in the outgoing or the return direction of the traffic.
Current Topology
ASR1001-X version 03.17.00-(L3 Gi0/0/0.102, MACSEC)-----------(L2, Gi3/0/1)---3850 (3.6.4.E)-(L2, Gi3/0/2)------ ASR1001-X version 03.17.00-(Gi0/0/0.102 L3, MACSEC)
TEST 1
* Macsec enabled
* Dot1q encapsulation enabled
Result: Packet loss between ASR's
TEST 2
* Macsec enabled
* Dot1q encapsulation disabled
Result: No Packet loss
TEST 3
* Macsec disabled
* Dot1q encapsulation enabled
Result: No Packet loss
TEST 4
* Macsec disabled
* Dot1q encapsulation disabled
Result: No Packet loss
Some conclusions about the testing done:
1. Living both things at the same time encapsulation and MACSEC we have packet lost.
2. No packet drops at hardware (interfaces) level on 3850
Conditions:
Hardware and software:
cisco ASR1001-X : asr1001x-universalk9.03.17.00.S.156-1.S-std.SPA.bin
WS-C3850-48P, Version 03.06.04.E
CALO Lab setup is using copper SFP's while the customer is using Fiber Optics, the problem is replicated on both, so it doesn't seem to be related to HW. Configurations are the same as the customer has on his network.
Workaround:
Replacing 3850 for 4500 switch no ICMP packet drops observed on customer environment and CALO lab
Further Problem Description:
Reproduce on internal Cisco Labs
|
|
Last Modified: | 23-JUN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux24057 | Title: | Install/upgrade on a specific non-active switch will fail |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When doing a superpackage install on a specific member, other than active, using the "request platform software package install" command will result in an error message and install will fail.
Conditions:
This only occurs when doing superpackage install on a specific non-active switch.
Issue is not seen when using "switch all", or when the switch specified is the current active.
Workaround:
The expansion of the superpackage to member will be successful, only the install portion will have failed. In such cases, user can reissue the install command on that specific switch but instead of specifying the superpackage as the filename, they can use *.pkg expression to denote the necessary subpackages instead.
Example:
Superpackage cat3k_caa-universalk9.BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA.bin
expands to the following subpackages:
cat3k_caa-rpbase.BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA.pkg
cat3k_caa-srdriver.BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA.pkg
cat3k_caa-wcm.BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA.pkg
cat3k_caa-webui.BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA.pkg
Build string in this case would be BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA
So user can run install on all the extracted subpackages using:
request platform software package install switch file flash:*BLD_V161_0_THROTTLE_LATEST_20151116_230450_2.SSA.pkg
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.3(0) |
|
Known Fixed Releases: * | 16.1(2.43), 16.2(0.350), 16.3(0.140), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw01266 | Title: | ffm crash when adding 3.3.x switch to 3.6.3 stack |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
switch with 3.3.x release crashes when added to the stack running 3.6.3 release
Conditions:
Member switch running 3.3.x crashes with Feature Forwarding Manager service upon joining the stack
Workaround:
Install 3.6.3 on a switch before adding the switch to the stack
Further Problem Description:
This behavior is not seen when switch with 3.6.3 is added to the stack already running 3.6.3, switches loaded with same version will never hit this issue.
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 3.6 |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 3.6(4)E, 3.6(5)E, 3.7(3)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy54279 | Title: | duplicate entries in OBFL CLI chain and error while clearing OBFL log |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Boot up on the stack, Duplicate entries in the OBFL CLI chain.
Conditions:
Can be seen during all conditions..
Switch#clear logging ?
onboard Switch
onboard onboard information
persistent Delete persistent logging files
xml Clear XML logging buffer
Switch#clear logging onboard ?
switch Switch
switch Switch
Switch#clear logging onboard switch ?
<1-9> Switch number
<1-9> Switch number
active Active instance
standby Standby instance
Switch#clear logging onboard switch 1 ?
counter Clear onboard Counter log file
counter Clear onboard Counter log file
environment Clear onboard Environment log file
environment Clear onboard Environment log file
message Clear onboard Message log file
message Clear onboard Message log file
poe Clear onboard POE log file
poe Clear onboard POE log file
temperature Clear onboard Temperature log file
temperature Clear onboard Temperature log file
uptime Clear onboard Uptime log file
voltage Clear onboard Voltage log file
voltage Clear onboard Voltage log file
Switch#clear logging onboard switch 1
% Ambiguous command: "clear logging onboard switch 1 "
Switch#
Switch#
Also, when try to clear the OBFL log, will see this error:
Switch#clear logging onboard switch 1
% Ambiguous command: "clear logging onboard switch 1 "
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: * | 16.1(2.28), 16.2(0.315), 16.3(0.113), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw08386 | Title: | 3850 SFP send TX power even if SFP IF is shut down state |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
after shut down the SFP interface on 3850, we can see "Tx Power" displayed "N/A" from "show int transceiver ".
however , SFP still keep sending TX power to peer even if it is "shut down" state.
Conditions:
Issue occurs on 3650 1G uplink and C3850-NM-4-1G module on 3850.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 16.1(0.427), 16.1.1, 16.2(0.181), 3.6(4)E, 3.6(5)E, 3.7(3)E, Denali-16.1.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux77481 | Title: | Webauth : switch crash on config 'custom-web fail page file Faill.html' |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Ng3k stack got crashed on configuring Webauth profile with "custom-web failure page file Faillure.html"
Conditions:
Switch(config)#fallback profile WEBAUTH
Switch(config-fallback-profile)#custom-web failure page file Failure.html
Workaround:
Further Problem Description:
This cli is not recommended by cisco
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 15.2(2.5.88)E4, 3.7(2) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 15.2(5.1.1)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw97476 | Title: | Q-in-Q configured on 3850 stack is not working appropriately |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Q-in-Q is conifgured on 3850 stack.
after power off/on on the master of the 3850 stack, Q-in-Q is not working appropriate when removing the tag of those tagged packets. It caused IF going to err-disable on 3850.
error message:
--------------------
%PM-4-ERR_DISABLE: l2ptguard error detected on GiX/X/X, putting GiX/X/X in err-disable state
Conditions:
Q-in-Q configured on 3850 stack.
power off/on on the master of the 3850 stack.
Workaround:
reload the 3850 stack
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 3.6(4)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv11888 | Title: | "no switchport" reapplies Hidden "dot1x supplicant" config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The interface CLI 'DOT1X PAE AUTHENTICATOR' or 'DOT1X PAE SUPPLICANT' may re-appear on un-configuring and configuring back 'SWITCHPORT' interface CLI.
Conditions:
Interface must be L2 ('SWITCHPORT' mode)
'DOT1X PAE needs to be on the interface.
Workaround:
No workaround.
Further Problem Description:
This doesn't impact any dot1x/authentication functionality. This is just a CLI issue.
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 15.2(4.1.1), 16.1(0) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 15.2(5.0.39)E, 16.1(1.48), 16.1.2, 16.2(0.258), 16.3(0.54), 3.6(4)E, 3.7(4)E, Denali-16.1.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux77511 | Title: | 3850: Webauth not working when incorrect username/password entered |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
For a switch configured to run with WEBAUTH and MAB, when a user enters invalid username/password on logon page, the failed window opens. However, nothing is displayed and it just sits there trying to connect to the page you want to get to and doesn't connect to anything. After this, the connection is unresponsive and the login screen doesn't function. The connection becomes responsive again after resetting the connection (unplugging/plugging the Ethernet cable) but WEBAUTH only works when a valid username/password is entered.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 15.2(5.1.8)E, 15.2(5.5.66)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy73381 | Title: | shaping is not working on 3850 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
shaping is not working as expected on 3850
Conditions:
configure shaping on Cat3850 switch
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E2, 16.1.2 |
|
Known Fixed Releases: * | 15.2(3)E4, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy61470 | Title: | 6 member 385012X48U stack crashed during continuous reload test |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
- Crash seen on WS-385012X48U switch stack during reload.
- Crash was seen on member switch
- Crash was seen because of hap_sup_reset: Reason Code:[2] Reset Reason:Service [fed] pid:[5909] terminated abnormally [6
Conditions:
- 6 member WS-385012X48U stack running 3.7.3
- Crash was seen when doing multiple stack reloads
- Issue was seen only once and on member swicth
- recovered by reloading the stack
Workaround:
Reload entire stack
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 3.7(0) |
|
Known Fixed Releases: * | 15.2(3)E4, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCva22545 | Title: | Port-channel configured with LACP member is on suspended mode. |
|
Status: | Open |
|
Severity: * | 2 Severe |
Description: | Symptom:
After performing an upgrade to 3.7.4 the Port-channel sent one of members to suspended mode
Conditions:
Port-channel should be configured as LACP on image 3.7.4
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 02-JUL-2016 |
|
Known Affected Releases: | 15.2(3.7.4)PIH19 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux91239 | Title: | Observing SMD crash with secure LDAP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Active switch reboots while trying to bring up more than 1k dot1x sessions with secure ldap authentication
Conditions:
Bring up more than 1k dot1x sessions with secure ldap
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.1(2.40), 16.2(0.280), 16.3(0.77), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz81646 | Title: | 3850 stack REP "non-operational" due to neighbor mismatch detected |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
3850 stack REP changed to "non-operational" due to neighbor mismatch detected
Conditions:
issue Only happen on cases which Active 3850 booted up completely firstly.
while 3850 stack is in normal working status, powered off the Active. issue happened.
Workaround:
boot standby shortly after booting active
Further Problem Description:
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: * | 16.2(1.32), 16.3(0.229), 16.4(0.59) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus93034 | Title: | 5760 segmentation fault(11) on Auth-proxy HTTP daemon |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IOS Thread backtrace:
IOSD-EXT-SIGNAL: Segmentation fault(11), Process = Auth-proxy HTTP daemon 0
5760 crashes
Conditions:
Usage of web authentication
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 13-JUN-2016 |
|
Known Affected Releases: | 10.2(100.0) |
|
Known Fixed Releases: * | 15.2(1)SY1.105, 15.2(1)SY2, 15.2(1.2.40)SY1, 15.2(2)E3, 15.2(3)E2, 15.2(4)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(1)IE101.266 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw02650 | Title: | Ping packet loss (20~27s) during a switch add into stack |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Connection: PC---C2960X(1)===== C3650 stack ====== C6500(with SUP2T) VSS ===== C2960X(2)
In C3850 stack, ping packet loss occurred(about 20~27s) when a switch add into stack
occurring in randomly
Conditions:
Active device Power off/on, connecting with ether-channel
Workaround:
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 3.6(2)E |
|
Known Fixed Releases: * | 15.2(2)E5, 15.2(3)E4, 3.6(5)E, 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv62794 | Title: | MAC address doesn't update when flex-link switchover. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
when Flex-link switchover, ping loss happend.
Conditions:
Flex-link switchover
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.0(31.4.79) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 3.6(4)E, 3.6(5)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy30244 | Title: | 60MB increase in WCM USS |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
memory jump of 1.5% of WCM which means WCM is using 1.5% more of the total memory available in the system
Conditions:
Workaround:
none currently known
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: * | 16.1(2.69), 16.2(0.303), 16.3(0.102), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux78543 | Title: | Device-tracking database not updated after client moves |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
device-tracking database not updated afer client moves
Conditions:
Device-tracking database not updated after a SANET client moves from one port ( eg behind a Phone ) to another port
The database still shows the client on former port ( which then goes to STALE ) but new port is never shown
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.2 |
|
Known Fixed Releases: * | 16.1(2.58), 16.2(0.271), 16.3(0.62), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz69590 | Title: | AN: NG3K crash during "no autonomic" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
C3850/C3650 crashes after "no autonomic"
Conditions:
Crashes after disabling autonomic
Workaround:
N/A
Further Problem Description:
N/A
|
|
Last Modified: | 07-JUN-2016 |
|
Known Affected Releases: * | Denali-16.3.1, Denlai-16.3.1 |
|
Known Fixed Releases: * | 16.3(0.226), 16.4(0.52) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo55022 | Title: | 3850 hosts not getting DHCP addresses when Port-security is enabled |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
When connecting a host into an access-port with Port-security enabled and using VLAN 325, the switch is not learning the MAC address of the end device and no DHCP address is leased to this host.
The following errors can be seen during the issue:
Mar 26 18:55:22.255: PSECURE: swidb = GigabitEthernet1/0/16 mac_addr = 5cf6.dc1b.ce17 vlanid = 325
Mar 26 18:55:22.255: PSECURE: Adding address vlan 325 5cf6.dc1b.ce17 to port-security
Mar 26 18:55:22.255: PSECURE: Adding addresses to port-security sub block
Mar 26 18:55:22.255: PSECURE: Internal error in adding address
Conditions:
Use of VLAN 325 plus Port-security on access ports.
Example of port configuration:
interface GigabitEthernet1/0/16
switchport access vlan 325
switchport mode access
switchport port-security
switchport port-security aging time 2
switchport port-security violation restrict
switchport port-security aging type inactivity
spanning-tree portfast
spanning-tree bpduguard enable
Workaround:
Use a different VLAN for the access ports (stop using VLAN 325)
OR
Remove "switchport port-security" command from the port configuration
OR
Use 'access-session tunnel vlan < > ' command to set clients to communicate on new tunneled vlan
Further Problem Description:
|
|
Last Modified: | 06-JUN-2016 |
|
Known Affected Releases: | 15.0(1)S3.3 |
|
Known Fixed Releases: | 15.0(1)EZ4, 15.0(1.77)ZSR, 15.0(13.67)EZD, 15.0(14.1)TSR, 15.0(14.57)EZD, 15.0(2.29)ZSR, 15.2(2)E, 15.2(2b)E, 3.3(4)SE, 3.3(5)SE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue37354 | Title: | Missing the last character of power supply SN in "show inventory" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
On 3850, the last character of power supply's SN is missing in "show inventory".
Conditions:
c3850
Workaround:
Check the SN in "show env power"
Further Problem Description:
|
|
Last Modified: | 17-JUN-2016 |
|
Known Affected Releases: | 15.3(2.19)S0.1 |
|
Known Fixed Releases: | 15.0(1)EZ, 15.0(11.91)EMW, 3.3(0)SE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf90316 | Title: | In lanbase intervlan-routing uses 100% software path |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When routing traffic on a Catalyst 3850 using a lanbase image, transfer times are slow.
Conditions:
On the lanbase image, traffic is routed through software rather than hardware path.
Workaround:
None.
|
|
Last Modified: | 16-JUN-2016 |
|
Known Affected Releases: | 15.0(1.1)EX |
|
Known Fixed Releases: | 15.0(1)EZ, 15.0(11.6)EMW, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(2)E, 3.3(0)SE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy75466 | Title: | BW of interfaces port-channel shows wrong after master switch down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When both two physical interfaces up and bundled in Port-channel, interface Port-channel shows BW as 6000000 Kbit/sec what should be 1000000 Kbit/sec as expected.
Conditions:
Port-channel interfaces(mode on) on 3850 Stack switch
Workaround:
reload entire stack for recover
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(2)E4 |
|
Known Fixed Releases: * | 15.2(2)E5, 15.2(3)E4, 16.3(0.177), 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy58587 | Title: | eicored process crash from clock sync |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A stack member may encounter a crash/reload after applying ntp configs on the master:
STANDBY:2 process sysmgr: Service [eicored] pid:[6262] terminated abnormally [11].
Conditions:
This behavior has been noticed on a Stackwise with NTP [being] configured.
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(2)E1 |
|
Known Fixed Releases: * | 15.2(2)E5, 3.6(5)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv59145 | Title: | Duplex is full one end and half on the other with speed nonegotiate |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unable to use SFP link when both sides are configured with "speed nonegotiate"
Conditions:
While Executing "speed nonegotiate" on 1G fiber port, Half Duplex is getting set on uplink module.
1G Fiber should always work with Full duplex and 1G speed.
Workaround:
Do not use "speed nonegotiate"
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 3.6(2) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 16.1(1.51), 16.1.2, 16.2(0.260), 16.3(0.46), 3.6(4)E, 3.6(5)E, 3.7(4)E, Denali-16.1.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq29356 | Title: | Tracebacks generated when using IP Source Guard on IOS-XE |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traceback syslog messages may be generated when using IP Source Guard configurations on IOS-XE based switching platforms. Examples include later switches in the 4500 series, the 3850, and the 3650.
Conditions:
IP Source Guard configuration is applied to the affected device and bindings are added / changed.
The configuration of "ip verify source" under an interface without "mac-check" also enabled may trigger this behavior as well.
Workaround:
None. These traceback messages are benign and can be ignored. Upgrade to a version of code with the software fix integrated to have them removed.
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E5, 15.2(3)E, 3.6(5)E, 3.7(0)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur66937 | Title: | SPAN replication does not retain DSCP marking |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
SPAN replicated packets do not show DSCP markings of packets marked with a service-policy on egress
Conditions:
3.3.4SE
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 3.6(0) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E1, 3.6(4)E, 3.6(5)E, 3.7(1)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv03683 | Title: | %Failed to determine package type when sw install from non-Active flash |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a user attempts to do a software install where you specify the source image from a non-Active flash switch, it will fail with a "% Failed to determine package type for flash-X:image.bin"
Conditions:
Customer has to be trying to install an image from a non-Active flash in order to see the issue.
Workaround:
The workaround would be to copy the image to the Active flash and then issue the software install from that flash instead of a non-Active flash - software install file flash:image.bin.
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(3.7.1E) |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 3.6(4)E, 3.6(5)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui42745 | Title: | GUI/CLI access to Cat3850 in spite of "no wireless mgmt-via-wireless" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Wireless client can telnet/ssh/http/https to 3850/5760 even though ''no wireless mgmt-via-wireless'' is configured.
Conditions:
Default configuration.
Workaround:
Apply ACL policies on wlan to block ssh/telnet/http access to each of the IP interfaces defined
on the switch or controller.
ip access-list extended no_mgmt
deny tcp any host X.X.X.X eq www
deny tcp any host X.X.X.X eq 22
deny tcp any host X.X.X.X eq telnet
permit ip any any
wlan Exwireless 1 Exwireless
client vlan 100
ip access-group no_mgmt
no security wpa
no security wpa akm dot1x
no security wpa wpa2
no security wpa wpa2 ciphers aes
no shutdown
* X.X.X.X is 3850/5760 wireless management interface address.
Further Problem Description:
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
3.3/2.7
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:A/AC:L/Au:N/C:P/I:N/A:N/E:F/RL:OF/RC:C&version=2.0
No CVE ID has been assigned to this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.0SID |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(2)E5, 15.2(3)E3, 3.6(4)E, 3.6(5)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz02766 | Title: | NOVA: Crash in IOSd with 'EPC SM Liaison Update proc' |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A nova-based switch (3850, 4500) can crash when removing an existing capture point before it is stopped.
The crash will be within IOSd:
IOSD-EXT-SIGNAL: Segmentation fault(11), Process = EPC SM Liaison Update proc
Conditions:
The existing capture point is removed before it can be deactivated asynchronously. It is triggered on "no monitor capture "
Workaround:
The workaround would be to stop the capture before removing it. i.e:
'monitor capture stop'
'no monitor capture '
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 3.6(3)E, 3.7(3)E |
|
Known Fixed Releases: * | 15.2(3)E4, 15.2(5.1.75i)E, 16.3(0.192), 16.4(0.46), 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40358 | Title: | PIM Auto-RP information lost on device |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Pim Auto-rp information lost on device when upstream device is L2 switching multicast traffic
Conditions:
observed on 3850 device
Workaround:
Na
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 15.2(2.0)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 16.1(2.65), 16.2(0.356), 16.3(0.140), 3.6(4)E, 3.7(4)E, Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw91080 | Title: | Cat3850 stack standby side span broken after reloading the stack |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Cat3850 stack standby side span broken after reload the stack
Conditions:
1. configure span on standby side
2. source interface is port-channel member
Workaround:
reconfigure standby side span
Further Problem Description:
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 3.7(0)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E4, 16.1(1.12), 16.1.2, 16.2(0.213), 3.6(4)E, 3.7(4)E, Denali-16.1.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz76749 | Title: | State Machine Power Good wait timer timed out with POE_PORT_INTERNAL_CMD |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
- This message is seen on 3850 and 3650 when a power device is granted power, but IOS state machine hasn't got an acknowledgement
- When this message is seen, take output of 'show mgmt-infra trace messages platform-mgr-poe switch' and check for the events 'POE_PORT_INTERNAL_CMD' and/or 'POE_PORT_INTERNAL_INTR' that match with state machine power good timer timestamp.
(show mgmt-infra trace messages platform-mgr-poe switch | inc POE_PORT_INTERNAL_CMD OR show mgmt-infra trace messages platform-mgr-poe switch | inc POE_PORT_INTERNAL_INTR)
- If you see any of these events, you are running into this bug.
- When this message is seen, the power device retries to draw power again and ultimately turns ON.
- This message is seen only when PD is connected for the first time, or the port is shut/no shut or the switch is rebooted.
- Issue will not be seen when the PD is already up and running. Only the first time it tries to draw power
Conditions:
Message will be seen when a POE device has been granted power by IOS, but IOS hasn't received an acknowledgement from the POE controller whether power was ultimately granted.
Workaround:
PD device will re-try automatically
Further Problem Description:
|
|
Last Modified: | 02-JUN-2016 |
|
Known Affected Releases: | 3.7(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy11133 | Title: | Observing memory leaks with EPM after CoA |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Memory leaks would be seen after CoA. Leak would be 4500 bytes once a day assuming all the sessions using dACL go down on a day
Conditions:
Memory leaks would be seen when Change of Authorization Requests are sent
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.1(2.36), 16.2(0.308), 16.3(0.104), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz33679 | Title: | Cat3850: REP LSL PDU counter up on shut down interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Cat3850: REP LSL PDU counter up on shut down interface
Conditions:
when interface is shut
Workaround:
Added check for hwidb state using idb to block sending tx pdu when interface is shut
Further Problem Description:
1. PROBLEM SUMMARY: The Cat3850 is a stand alone device, but REP LSL PDU TX keep counting up on REP shut down interface
2. ROOT CAUSE ANALYSIS: No check for block sending tx pdu when link is down
3. SUMMARY OF CODE FIX: Added check for hwidb state using idb to block sending tx pdu when interface is shut
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: * | 16.3(0.220), 16.4(0.41) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy32054 | Title: | Observing issue with "show access-session" output post SSO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Not a functional issue. The issue is with "show access-session" CLI only.
"show access-session" displays incorrect session count post SSO
Conditions:
Perform SSO and bring down all dot1x sessions. "show access-session" shows incorrect session count.
Workaround:
Do not perform SSO.
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.1(2.35), 16.2(0.305), 16.3(0.102), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy49397 | Title: | Bundling the AP1852E fix with IOS XE Denali 16.1 and 16.2 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Bundling the Corsica - 1830, 1850 - AP fix with Denali 16.2.1 and Polaris 16.1.x
Conditions:
This change includes required fixes for Corsica AP support
Workaround:
Resolved
Further Problem Description:
None
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.2.1 |
|
Known Fixed Releases: * | 16.1(2.64), 16.2(0.308), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy34601 | Title: | SMD leak@OBJ_MAB_METH_MAC,CWA roam in webauth_pending |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
SMD memory leak with process OBJ_MAB_METH_MAC
Conditions:
Roam CWA clients in webauth_pending state
Workaround:
Move CWA clients to UP state before roaming
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: * | 16.1(2.63), 16.2(0.304), 16.3(0.103), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux66659 | Title: | Wireless Mobility Multicast: IP config validation issues observed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Wireless mobility multicast IP address can be configured same as of other multicast addresses.
Conditions:
While configuring the mobility multicast IP address, the same IP address can be configured for multicast address of AP and other mobility group.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 01-JUN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.1(2.59), 16.2(0.295), 16.3(0.94), Denali-16.1.3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39490 | Title: * | c3650/c3850 core 0 high /fed and fed-ots-main abnormal |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
there are some groups 3650/3850 stack running 03.07.00E, only a part of the switches encounter the phenomenon as below, others are normal.
Issue can occur in standalone switch as well, not restricted to stack.
+core 0 would be up to 90-100%
+fed and its subprocess fed-ots-main are high even if no much traffic punt to cpu
+check the cpu queues by command "show platform punt statistics port-asic 0 cpuq -1 direction rx" , forus queue (RXQ 2: CPU_Q_FORUS_TRAFFIC) increase repidly, but not too much, increase 100 every time
+ wireshark the packets punt to cpu, seems normal, little packets.
Conditions:
didn't find the trigger or between healthy and problematic switches for the time being.
Workaround:
cu tried to reload one of the problematic switches, the issue was gone.
Further Problem Description:
|
|
Last Modified: | 28-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: | 15.2(3)E4, 16.3(0.158), 3.7(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux14199 | Title: | error "Command rejected: Bad VLAN list" when default interface config |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
unable to default the interface with port-security and interface mode in trunk.
Switch(config)#default interface gi3/0/48
Command rejected: Bad VLAN list - character #1 is a non-numeric
character ('a').
Interface GigabitEthernet3/0/48 set to default configuration
Conditions:
interface is configured for trunk mode along with port-security access mode configured.
interface GigabitEthernet3/0/48
switchport mode trunk <<<<<<<<<<<<<<<<<<<<<<<<<<<<<
switchport port-security maximum 3
switchport port-security maximum 2 vlan access <<<<<<<<<<<<
switchport port-security maximum 2 vlan 1
Workaround:
change the switchport mode to access and they delete the configuration one by one on the interface.
Further Problem Description:
|
|
Last Modified: | 02-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(3)E4, 15.2(5.1.16)E, 15.2(5.5.66)E, 16.2(0.294), 16.3(0.84) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw19079 | Title: | DiagGoldPktTest and DiagPhyLoopbackTest failed on 03.06.03E release. |
|
Status: | Terminated |
|
Severity: | 4 Minor |
Description: * | Symptom:
DiagPhyLoopbackTest{ID=4} has failed. Error code = 0x1 (DIAG_FAILURE)
Conditions:
During the switch boot up or when running the manually daig test.
=================
DC2101#diagnostic start switch 2 test 4
%DIAG-3-TEST_FAIL: switch 2: DiagPhyLoopbackTest{ID=4} has failed. Error code = 0x1 (DIAG_FAILURE)
show diagn re sw 2 test 4
Current bootup diagnostic level: complete
Test results: (. = Pass, F = Fail, U = Untested)
4) DiagPhyLoopbackTest:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
----------------------------------------------------------------------------
. . . . . . . . . F F F F F F F F F F F F F F F
Port 25 26 27 28 29 30 31 32
----------------------------
. F . . . . . F
Workaround:
As other configurations are not recommended for DiagPhyLoopbackTest, please remove the other configuration and test with default configuration.
Further Problem Description:
N/A
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(2)E3 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw20728 | Title: | C3850-S Link goes up during reboots |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
C3850-S Link goes up during reboots once
Conditions:
Cat3850-24S
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-JUN-2016 |
|
Known Affected Releases: | 15.2(3)E, n/a |
|
Known Fixed Releases: * | 15.2(2)E5, 15.2(3)E4, 16.3(0.137), 3.6(5)E, 3.7(4)E |
|
|
| |
:
没有评论:
发表评论