| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo50456 | Title: | WS-C3560X high CPU with REP LSL Hello PP Process during failover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:High CPU problem found on WS-C3560X with REP running.
Conditions:The STCN sent by first segment is looping back since the 2nd and 3rd segments also configured to transmit the STCN occurred in their segment back to first segement.
Workaround:None.
More Info:
|
|
Last Modified: | 15-AUG-2015 |
|
Known Affected Releases: | 15.0(31.4.119) |
|
Known Fixed Releases: * | 15.0(2)SE7, 15.2(2)E1, 15.2(2.54)PSR, 15.2(2b)E, 15.2(3)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 3.6(1)E, 3.7(0)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum56403 | Title: | FSPAN session can't work again after Reloading vlan-based FSPAN session |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
configured many lines of ACL which applied for FSPAN, and see below log messages which shows
The ACL manager cannot store the FSPAN configuration,and this feature has been temporarily
disabled for the session. and we saw that can't capture packets by monitor session.
---------------------------------------
%ACLMGR-4-UNLOADINGFSPAN: Unloading vlan-based FSPAN session 1 Macand IP feature
---------------------------------------
then we do configuration change to delete ACLs and make the ACL manager to reload the FSPAN
session, but FSPAN session can't start to work again and no packets can be captured.
-----------------------------------------------------------
%ACLMGR-4-RELOADEDFSPAN: Reloading vlan-based FSPAN session 1 IP feature
-----------------------------------------------------------
after delete and re-configure the FSPAN session config, it will starts to work again and
packets can be captured normally.
===============================
vlan access-map xxx 999
match ip address xxx
action drop log
vlan filter xxx vlan-list 999
monitor session 1 source vlan 999 rx
monitor session 1 destination interface Gi0/1
monitor session 1 filter ip access-group xxx
===============================
Conditions:
Workaround:
delete and re-configure the FSPAN session config, it will starts to work again and
packets can be captured normally.
Further Problem Description:
|
|
Last Modified: | 15-AUG-2015 |
|
Known Affected Releases: | 15.0(2)SE5 |
|
Known Fixed Releases: * | 15.0(2)SE6, 15.2(2)E, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtn47111 | Title: | 3560X: With C3KX-NM-10G Flexlink cause intermittent packet loss |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Cat3560X experience intermittent traffic loss or ping failure.
Conditions:
Catalyst 3560X with C3KX-NM-10G, running 12.2(55)SE release.
Flexlink flap is reported:
3560X#sh int switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
-------------------------------------------------------------------
GigabitEthernet1/4 GigabitEthernet1/2 Active Down/Backup Down <<==
3560X#sh int switchport backup
Switch Backup Interface Pairs:
Active Interface Backup Interface State
--------------------------------------------------------------------
GigabitEthernet1/4 GigabitEthernet1/2 Active Up/Backup Standby <<==
Workaround:
None.
Further Problem Description:
This bug is under investigation.
|
|
Last Modified: | 15-AUG-2015 |
|
Known Affected Releases: | 12.2(55)SE |
|
Known Fixed Releases: * | 12.2(58)EZ, 12.2(58)SE, 12.2(58)SE1, 12.2(58)SE2, 12.2(60)EZ, 12.2(60)EZ1, 12.2(60)EZ2, 12.2(60)EZ3, 12.2(60)EZ4, 12.2(60)EZ5 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv17071 | Title: | 3560x: PoE Available Power drops to 370w from 1440w on 152-3.E1 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
3560-X Switches will report available PoE power of 370w after upgrading IOS to 152-3.E1. PoE devices connected to the switch will be affected, as the switch will believe it does not have enough power for the devices.
Conditions:
A 3560-X switch with an 1100WAC power supply or similar, configured for PoE.
After upgrading to 152-3.E1, "show power inline" will list total available power as 370W instead of the correct value.
This will impact PoE hosts, as PoE will be denied once it exceeds the 370w value.
Workaround:
Downgrade to 152-3.E. Upgrade to fixed version of IOS. This issue is specific to 152-3.E1.
Further Problem Description:
|
|
Last Modified: | 08-AUG-2015 |
|
Known Affected Releases: | 15.2(3.7.1) |
|
Known Fixed Releases: * | 15.2(3)E2, 15.2(4.0.40)E, 15.2(4.0.64a)E, 3.7(2)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue34250 | Title: | WCCP traffic can't redirect after reloading the switch |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
WCCP traffic can't redirect after reloading the switch
Conditions:
since using 15.0.2SE or later
Workaround:
remove the wccp redirects command from the interface and put it back on it.
verify label information.
switch#show platform ip wccp label
ID Label
0 22
1 23
|
|
Last Modified: | 14-AUG-2015 |
|
Known Affected Releases: | 15.2(1.1) |
|
Known Fixed Releases: * | 15.0(2)EJ, 15.0(2)EJ1, 15.0(2)SE3, 15.0(2)SE4, 15.0(2)SE5, 15.0(2)SE6, 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq03344 | Title: | Multicast traffic drops although multicast entry exists on the table. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Multicast traffic drops although multicast entry exists on the table.
Conditions:
The issue happens when interface of Outgoing interface list is down and Multicast entry is existing.
Then interface of Outgoing interface list is up. multicast routing table is seem like that it's no problem.
But Sender fails multicast.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 08-AUG-2015 |
|
Known Affected Releases: | 15.2(2)E, 15.2(2.0)E |
|
Known Fixed Releases: * | 15.2(2)E1, 15.2(3)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 3.6(1)E, 3.7(0)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup86666 | Title: | Configuration "no logging event link-status" can't be deleted. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Configuration "no logging event link-status" can't be deleted.
Conditions:
configure an interface like below.
interface GigabitEthernet0/23
description ******
no switchport
no ip address
no logging event link-status
shutdown
no snmp trap link-status
no cdp enable
end
then input the below commands.
SW(config-if)# snmp trap link-status
SW(config-if)# logging event link-status
SW(config-if)# switchport
SW(config-if)# no description
SW(config-if)
|
没有评论:
发表评论