| |
|
Alert Type: | Updated * |
Bug Id: | CSCui59004 | Title: | iosd crash while configuring no ntp server |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IOSd crashes while removing NTP server from the configuration.
Conditions:
This may occur rarely, when removing "ntp server " from configuration. ntp servers configured with ip addresses will not cause the same.
Workaround:
Timing the "no ntp" configuration such that it does not overlap with the 60 second DNS resolution timer.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.0(1)EX2 |
|
Known Fixed Releases: * | 15.0(1)EZ, 15.0(1)EZ1, 15.0(12.15)EZD, 15.0(14.1)TSR, 15.0(14.49)EZD, 15.0(2.29)ZSR, 15.1(1)ICA4.122, 15.1(1)SY3.11, 15.1(1)SY4, 15.1(1)XO0.32 |
|
|
| |
| |
|
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: | 23-FEB-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E4, 3.6(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu18029 | Title: | 3650/3850 May Experience RP Protocol Flaps with Aggressive Timers. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The 3650 and 3850 switches may experience Routing Protocol Flaps when using aggressive timers.
Conditions:
The problem has been seen on the NGWC switches with RP protocols using 3 seconds or less for dead/hold-down timers.
Workaround:
It is recommended to use the default routing protocol timers. If faster convergence is required do not use anything less than 10 second dead/hold-down to avoid this defect.
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 15.2(2.0)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E3, 3.6(4)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw55669 | Title: | Crash is seen in iosd on switch and auth-mgr |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Switch with IOSD crashes in auth-manager with this symptom:
IOSD-EXT-SIGNAL: Segmentation fault(11), Process = EPM MAIN PROCESS
Conditions:
The system crashed due to stack overflow caused by loop calls between PI sanet and vlan group plugin on switch platform while dumping sanet trace messages in the case when handling dynamic vlan updates for a given vlan on standby switch.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-FEB-2016 |
|
Known Affected Releases: | 3.6(0) |
|
Known Fixed Releases: * | 15.2(3)E3, 15.2(4)E1, 15.2(4.0.95)EA1, 15.2(4.0.95a)E, 15.2(4.1.25)EA1, 15.2(4.1.5a)E, 15.2(5.0.38)E, 15.2(5.5.36)E, 15.2(5.6.1)E, 16.1(1.20) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue60618 | Title: | Katana: ability to shut NMSP (default) service on TCP port 16113 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Katana: ability to shut NMSP (default) service on TCP port 16113.
Conditions: This symptom is observed in the default configuration.
Workaround: There is no workaround.
More Info: After this fix, the NMSP feature needs to be explicitly enabled using CLI nmsp enable. This change satisfies the security baseline requirement that no TCP ports should be open as a default option. The NMSP port 16113 can now be disabled with CLI no nmsp enable which was not an option before this fix.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 10.1(0.22), 10.1(100.0), 10.2(1.1), 10.2(1.25), 15.0(1)EZ, 15.0(10.1)PKD, 15.0(11.11)EMW, 16.1.1, 3.3(0)SE, Denali-16.1.1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux97532 | Title: | only one switch boots up with stack-power |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Two C3850 in the stack are stack-power connected, at first both of them are down; and if we power on one switch, only one switch(with high priority) will boot up, the other one will keep down.
Conditions:
1. two C3850 in the stack are stack-power connected.
2. redundant power mode is used.
Workaround:
change the stack-power mode from "redundant" to "power-shared".
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 15.2(2)E3 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv89764 | Title: | 3.7.1E/3.7.2E: Catalyst 3850 stop forwarding multicast/broadcast packets |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Catalyst 3850 stack stop forwarding broadcast and layer2 multicast frames.
As a result, one or more of the following symptoms could be seen:
- ARP incomplete seen for devices connected to Catalyst 3850
- Ping timeouts
- HSRP Hellos traversing through Catalyst 3850 gets dropped causing the routers running HSRP to go active/active.
Conditions:
This behavior is seen in Catalyst 3850 running 3.7.x releases
AND
Catalyst 3850 is configured in converged access mode - with Access Points (APs) connected and wireless hosts connected to the Wireless Controller.
Known trigger:
Switch interface connected to VoIP Phone going down.
Workaround:
Downgrade to 3.6.2aE or 3.6.3E releases.
Issue is resolved in 3.7.3E or later releases.
More Info:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.2(3.7.2) |
|
Known Fixed Releases: | 15.2(3)E3, 16.2(0.151), 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw91252 | Title: | Only 10 domain names supported in domain list for FQDN ACL DNS snooping |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Currently Only 10 domain names are supported in domain list for FQDN ACL DNS snooping but GUI is allowing 25 domain names.
There is no functional impact but traffic would be allowed for 10 domains only.
Conditions:
More than 10 Domain Names/URLs Configured through GUI.
Workaround:
Use 10 or less domain names through GUI configuration
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 15.2(2)E3, 15.2(4)E, 16.1(1.21), 16.2(0.299), 16.3(0.5) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux24057 | Title: | Install/upgrade on a specific non-active switch will fail |
|
Status: | Open |
|
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: | 23-FEB-2016 |
|
Known Affected Releases: * | 16.3(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul19814 | Title: | SCHED-3-tHRASHING at fnf-rpc_context_wait_for_completion |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: After collecting "raw netflow" data, the active switch crashes. The show flow monitor v4 cache command causes the reboot of the switch with the following message:
%SCHED-3-TRASHING: Process thrashing on watched message event.
Conditions: This symptom occurs due to the show flow monitor command.
Workaround: There is no workaround.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.0(1)EZ |
|
Known Fixed Releases: * | 15.0(1)EZ2, 15.0(10.37)PKD, 15.0(10.37)PKP, 15.0(12.72)EZD, 15.0(14.1)TSR, 15.0(14.49)EZD, 15.0(2.29)ZSR, 15.2(1.1)PSR, 15.2(1.24)PSR, 15.2(2)E |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux96093 | Title: | smd crash when processing framed-netmask attribute from radius |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The process smd will crash and the switch will reload/switchover.
Conditions:
If the AAA server sends Framed-NetMask attribute as one of the attributes for the wireless clients, that will trigger the smd crash.
Workaround:
Framed-NetMask is not useful for wireless clients anyway, so remove this attribute in AAA server so it does not send it to the controller.
Recovery:
Switch will reload or switchover. This can repeat again if the same attribute is sent again.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | Denali-16.1.1 |
|
Known Fixed Releases: | 16.1(1.56), 16.2(0.273), 16.3(0.72) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw56706 | Title: | LACP with 16 ports - After a switchover ports in H state goes to D state |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Consider an etherchannel running the LACP protocol and with one or more hot standby ports. Prior to switchover, these ports will be in the "H" state and ready to take over if one of the active port channel members go down. After a switchover, these ports will be marked as "D" (link down) and will not be able to take over if one of the active port channel members were to go down.
Conditions:
As mentioned in the symtoms
Workaround:
After switchover, do a 'shut' 'no shut' on the affected ports. This should move them back to the correct state
Further Problem Description:
This issue only happens after a switchover. The hot-standby functionality in LACP will work correctly without a switchover
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.2(0.275), 16.3(0.75) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy09339 | Title: | Observing few dot1x sessions stuck in pending deletion state |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
AAA accounting, Reauthentication timer
Conditions:
If AAA dot1x accounting is enabled(presence of CLI aaa accounting dot1x .../aaa accounting identity ....), then this issue CAN be hit.
Also internally the issue was seen with scale sessions on the box(>1000) all of them having reauth timer applied with termination action as terminate. Hence all these sessions were being cleared and created fresh upon timer expiry.
Workaround:
Removing the service policy from the interface and reapplying might help in getting out of this issue.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 18-FEB-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: | CSCuv78424 | Title: | Unicast ARP packets are duplicated |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
3650/3850 duplicates unicast ARP request packets destined for its IP and sends back 2 replies for one ARP request packet sent by the host.
Conditions:
NA
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E3, 16.2(0.151), 3.6(4)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux85960 | Title: | 3850 stack - FED randomly crashed with IPSG failed initialization |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
stack might crashed with FED crashed on IPSG init failure in system report
===================== log file: /mnt/pss/sup_sysmgr_reset.log =====================
hap_sup_reset: Reason Code:[2] Reset Reason:Service [fed] pid:[6062] terminated abnormally [6].
===================== Trace Buffer: fed-btrace =====================
[01/11/16 10:09:13.651 UTC 1 6062] btrace xos-procname [fed-btrace] started for process ID 6062 with 128 modules
[01/11/16 10:11:26.960 UTC 2 6062] [errmsg]: (ERR): %FED-3-INIT_FAILED: Module IPSG failed initialization
show logs
===================== Trace Buffer: logs =====================
snipped
[01/11/16 10:11:10.589 UTC 16 6661] Notification received from active plogd,
[01/11/16 10:11:10.589 UTC 17 6661] Active Plog Message Server was born
[01/11/16 10:11:26.959 UTC 18 6661] plog_send_log_message: %FED-3-INIT_FAILED: 2 fed: Module IPSG failed initialization
[01/11/16 10:11:26.960 UTC 19 6661] plog_deliver_log_message_spi: Plog_role: plog-member is_dc = 0
[01/11/16 10:11:26.965 UTC 1a 6661] plog_send_log_message: %IOSXE-3-PLATFORM: 2 process sysmgr: Service [fed] pid:[6062] terminated abnormally [6].
[01/11/16 10:11:26.966 UTC 1b 6661] plog_deliver_log_message_spi: Plog_role: plog-member is_dc = 0
[01/11/16 10:11:26.967 UTC 1c 6661] plog_send_log_message: %STACKMGR-1-RELOAD: 2 stack-mgr: Reloading due to reason
Conditions:
random and unexpected during normal operation
Workaround:
unknown
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv14903 | Title: | multigig switch dropping pass through packets received on the uplink |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
This issue can be seen in WS-C3850-12XS and WS-C3850-12X48U when used with IOS version (3.7.1) release. Traffic Drop might be seen for some traffic if the incoming port and outgoing port are in 2 different ASIC cores in hardware.
Conditions:
If traffic comes into the system through up-link ports and going out on a down-link which is in another ASIC core e.g. port 41, 42 in WS-C3850-12X48U then the traffic drop might be seen, if the traffic has .1Q packet having CoS values that instruct a priority treatment. The COS values 2-7 might map to a internal queue which is not enabled. The "show platform port-asic ifm mappings local-port" CLI can be used to find the ASIC core for a local port number. The ASIC number in the output can be used to find where the port belongs. If the incoming port is in asic 0 then the out going port should not be in ASIC 1 and vice versa. If the incoming port is in ASIC 2 the outgoing port should not be in ASIC 3 and vice versa.
Workaround:
If the incoming and outgoing impacted port moved to same ASIC core or across switches in the same stack.
Further Problem Description:
|
|
Last Modified: | 19-FEB-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: | 15.2(3)E2, 3.7(2)E |
|
|
| |
| |
|
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: | 25-FEB-2016 |
|
Known Affected Releases: | none |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(5.1.22i)E, 3.6(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: | 26-FEB-2016 |
|
Known Affected Releases: | 15.2(2.0)E |
|
Known Fixed Releases: * | 15.2(2)E4, 3.6(4)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus34808 | Title: | IPDT table locked by process-id and communication is hang on for 5s-10m |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
After entering command "show ip device tracking all"
1.Some users on the switch were not able to communicate with other hosts
2. Bellow log message appeared:
*Apr 17 11:54:00.690: %IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED: Table already locked by process-id 201(SSH Process)
Conditions:
IPDT is enabled
Workaround:
Before running the show command "show ip device tracking all", set "terminal length 0" to display without breaks; alternatively, scrolling through the entire show command output very quickly can also reduce its incidence.
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 3.3(2)SE |
|
Known Fixed Releases: | 15.2(2)E3, 15.2(3)E3, 15.2(4)E, 15.2(4.0.49)E, 15.2(4.0.64a)E, 3.6(3)E, 3.7(3)E, 3.8(0)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu56511 | Title: | OutDiscards counter does not increment |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OutDiscards counter of "show interface counters errors" does not increment even if "Total output drops" counter of "show interface" increments.
Conditions:
Cat3850/Cat3650
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E4, 15.2(3)E3, 16.2(0.213), 3.6(4)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux11452 | Title: | Cat3850 crash when execute "no queue-limit" command |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
crash occur when execute "no queue-limit" command on Cat3850, when there exists 'queue-limit cos|dscp value ...' configuration.
Conditions:
Execute "no queue-limit" command when there exists "queue-limit cos values .." or "queue-limit dscp values .." configuration.
Workaround:
Remove by executing specific CLI - "no queue-limit cos values .." or "no queue-limit dscp values .." which will work fine as intended. "no queue-limit" in working scenario is a no-op in this case because it is not specific enough.
Further Problem Description:
User should use specific 'no queue-limit ...' command with parameters to remove. 'no queue-limit' when there exists detailed queue-limit will simply be ignored.
|
|
Last Modified: | 17-FEB-2016 |
|
Known Affected Releases: | 15.2(2)E3, 15.2(3)E |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur40920 | Title: | Switch reloads intermittently with ASIC ballot issue |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Switch reloads with the error
Reloading due to reason ASIC ballot failed
Conditions:
No crashinfo/core is saved - only systemreport
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.2(3.0.85)E1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy19892 | Title: | Doc: Working with Cisco IOS XE Software Bundles should be rewitten |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
The 16.1.1 software configuration guides have a chapter how to work with software bundles with IOS-XE but does not have a chapter on how to work with software bundles with IOS 16.1.1 .
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | Denali-16.1.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud22987 | Title: | STANDBY wcm: %OSAPI-4-TIME_SHIFT_DETECTED: Detected backward time shift |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
STANDBY wcm: %OSAPI-4-TIME_SHIFT_DETECTED: Detected backward time shift
message may be seen on a 3850
Conditions:
The message is seen on a switch running IOS-XE 3.2.0, 3.2.1 or 3.2.2
Workaround:
None. The message is cosmetic and may be ignored.
|
|
Last Modified: | 09-FEB-2016 |
|
Known Affected Releases: | 10.0(1.178), 10.0(1.179) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo11789 | Title: | 3850 IOSD crash at hashtable_get_nth_entry |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
3850 will crash in IOSD.
A crash with IOSD on a 3850 running 03.03.01.SE / 15.0(1)EZ1 in a 3-member switch stack
===================== Exception Data ====================
Exception in 'iosd' with Signal=SIGSEGV(11)
Conditions:
This seems to be synchronization issue while accessing a epm data structure. This might occur
when last no. of clients are joining and clearing the session fast.
Workaround:
Added a syncblk to synchronise the access to epm data structure.
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.0(1)EZ1 |
|
Known Fixed Releases: * | 15.0(1)EZ4, 15.0(1.1)TTT, 15.0(1.77)ZSR, 15.0(13.76)EZD, 15.0(14.1)TSR, 15.0(14.57)EZD, 15.0(2.29)ZSR, 15.2(1)IC273.87, 15.2(2)DB101.101, 15.2(2)DB101.112 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui87313 | Title: | Incorect state entry in "sh ip admisn cache" after roaming |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Incorrect state entry in show ip admission cache
Conditions:
Configure wlan with web-auth security and do roam,then will hit issue
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.0(51.33) |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.1(1)ICB40.1, 15.2(2)E, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.5(0.17)S, 15.6(1)SN, 16.1(0.14) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq20595 | Title: * | Nova switch crash on SNMP GetNext query |
|
Status: * | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
A nova-based switch (Cat3850, 4500X, etc) may unexpectedly reload due to a crash in the IOSd process.
Conditions:
This crash occurs when the switch is processing an SNMP GetNext request. It was observed on a switch running IOS-XE 3.3.3SE when the cHsrpGrpVirtualIpAddr object (1.3.6.1.4.1.9.9.106.1.2.1.1.11) was polled. It was also seen on 3.4.6SG when polling cpmCPUTotalEntry.
Further conditions may exist but are not currently known.
Workaround:
Disable SNMP polling of the switch, or do not poll the cHsrpGrpVirtualIpAddr or cpmCPUTotalEntry object.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 15.0(1)EZ3 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw79758 | Title: | Duplicate IP detected in Windows 7/8 clients with "tracking" enabled |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Windows 7/8 clients report duplicate IP address
Conditions:
If "tracking" is included in a device-tracking policy which is active, the Windows 7/8 clients may give up their ip when they are probed.
Workaround:
configure SVI for the VLAN and assign it an IP address
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.1(1.36), 16.2(0.242), 16.3(0.8), 7.3(0)D1(1), 7.3(0)ZD(0.239), 7.3(1)D1(0.2), 7.3(1)PDB(0.19), 7.3(1)PIB(0.24), 8.3(0)CV(0.337) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur31055 | Title: * | Ten gig links gets err-disable after enable "UDLD enable" on 3850 |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Teng gig links gets err-disable on remote device after using "UDLD enable" command on 3850 switch.
Conditions:
When using (SFP-H10GB-CU5M ) cable to connect 4500 and 3850 switch.
Workaround:
not known.
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 3.6(0)E |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy34487 | Title: | authentication mac-move permit needs documentation for default behavior |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
In legacy authentication mode, "authentication mac-move" is DENY by default. However the document states that "authentication mac-move" is PERMIT by default. The document needs to be modified to reflect the correct default behavior
Conditions:
NA
Workaround:
NA
Further Problem Description:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3e/consolidated_guide/command_reference/b_consolidated_3850_3e_cr/b_consolidated_3850_3e_cr_chapter_01101.html#wp1977723595
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.2(2.0.0) |
|
Known Fixed Releases: | |
|
|
| |
:
没有评论:
发表评论