| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw49457 | Title: | SGT still present for client's STALE state after removing client IP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
After configuring an IP-SGT mapping on the client, If connection to the peer device (with an interface with IP as in the mapping) is lost (STALE interface wrt to client), we still see the IP-SGT mapping on the client.
Conditions:
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.1(1.23), 16.2(0.261), 16.3(0.6) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut89766 | Title: | Observe FED crashed caused member removal from stacks |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
switch crash and got removed from stack
Conditions:
normal operation
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 3.7(0) |
|
Known Fixed Releases: * | 15.2(2)E3, 15.2(3)E3, 3.6(3)E, 3.7(3)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: | 20-JAN-2016 |
|
Known Affected Releases: | 3.6(0), 3.7(0) |
|
Known Fixed Releases: * | 15.2(3)E3, 3.7(3)E |
|
|
| |
| |
|
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 with 03.07.01E and 03.07.02E.
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 goes down.
Workaround:
Downgrade to 03.06.02aE release.
Further Problem Description:
|
|
Last Modified: | 20-JAN-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: | CSCuv60283 | Title: | Linkdown occur when SFP OIR on the error-disable port. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
The uplink Interfaces on a 3850 or 3650 will go down if you OIR a different uplink transceiver that is in an "admin down" or "err-disabled" state
Conditions:
Impacted Hardware:
3650
3850 with C3850-NM-4-1G
Impacted Software:
3.6.0 - 3.6.3
3.7.0 - 3.7.2
Workaround:
Remove the transceiver from the shutdown uplinks if you are experiencing this issue
If uplink is err-disabled, recover it (shut / no shut) before you OIR the transceiver
If uplink is shutdown, bring it up (no shut) before you OIR the transceiver
Issue is fixed beginning in 03.06.4E and 03.07.3E releases.
Further Problem Description:
Transceiver inserted into shutdown interface results in other Uplinks going down
%PLATFORM_PM-6-MODULE_INSERTED: SFP module inserted with interface name Gi1/1/4
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to down
Transceiver removed from same uplink results in other uplinks coming back up
%PLATFORM_PM-6-MODULE_REMOVED: SFP module with interface name Gi1/1/4 removed
%LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to up
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(2)E, 16.1(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux39091 | Title: | Traffic not forwarding on access ports on oneASIC, while Mac&ARPareLearn |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
A WS-C3850-48P may not forward packets out of the ports associated with either forwarding ASIC 1 (port 1-24) or forwarding ASIC 0 (ports 25-48). During the packet loss the EGR_MISC_FATAL_ERROR counter increments in the "show controllers ethernet-controller port-asic statistics exceptions switch {switch#} command output for the effected ASIC
Conditions:
The issue can be seen if the switch is doing L3 or L2 forwarding. MAC and ARP table entries are complete
The issue has been seen until now on a WS-C3850-48P running 3.3.5 and 3.3.0
Workaround:
The issue was resolved after an upgrade to 3.6.3. It is unclear at this point whether the code upgrade or the switch reload fixed the issue
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus96681 | Title: | IOS-XE 3.7.1 Crash When Configuring "mac addr static X.X.X vlan x drop" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A 3850 switch running IOS-XE 3.7.1 may experience a crash in the FED process when configuring a static MAC address with the "vlan [id] drop" option. Example:
SWITCH(config)#mac address-table static XXXX.XXXX.XXXX vlan x drop
Message from sysmgr: Reason Code:[2] Reset Reason:Service [fed] pid:[XXXX] terminated abnormally [11].
Conditions:
User is configuring a static MAC address with the "vlan [id] drop" option.
Workaround:
None known.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(3.1.27)E1, 15.2(3.7.1E) |
|
Known Fixed Releases: * | 15.2(3)E3, 3.7(3)E |
|
|
| |
| |
|
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: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(3)E3, 3.7(3)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: | 20-JAN-2016 |
|
Known Affected Releases: | 3.6(2)E |
|
Known Fixed Releases: * | 15.2(3)E3, 3.7(3)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: | 20-JAN-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: | CSCuu87659 | Title: | CpmCPUTotal5minRev average value of stack switch 2 on 3850 is incorrect. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The average value of cpmCPUTotal5minRev of stack switch 2 is different from an actual value.
Conditions:
3850 stack connection.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.1(2)SG7, 15.2(2)E3, 15.2(3)E3, 3.6(3)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu29813 | Title: | DHCP snoop on uplink vlan create WCDB error, does not match binding vlan |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
wireless clients will not get an IP.
Conditions:
DHCP snooping on uplink vlan. 3850 acting as a router. DHCP response coming back on a different vlan than client vlan.
Seen after upgrading to 03.06.02.
Workaround:
remove DHCP snooping from uplink vlan.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 15.2(2)E3, 15.2(3)E3, 15.2(4)E, 15.2(4.0.29)E, 15.2(4.0.64a)E, 15.2(5.0)ST, 16.1.1, 3.6(3)E, 3.7(3)E, 3.8(0)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv93759 | Title: | 3850 Inappropriate version output shown via CDP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When customer does a "show cdp neighbors detail" he is seeing version 15.2(3)E2 instead of the version 03.07.02E that the device is running shown on the "show version" output.
Conditions:
According to the developer, "The issue arose in 03.06.00.E when we switched over from using the
old non-componentized CDP code to the componentized CDP code. The cdp_common_shim.c file
that was added at that time did not properly check for the existence of an IOSXE version string; it
only returned the IOS version string."
Workaround:
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(2)IE101.140 |
|
Known Fixed Releases: * | 15.2(3)E3, 15.2(4)E, 15.2(4.0.95a)E, 15.2(4.0.99)E, 15.2(4.1.5a)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: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(3)E3, 16.2(0.213), 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu56466 | Title: | "Total output drops" counter of a certain ports does not increment |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"Total output drops" counter for Giga1/0/1 and Giga1/0/25 does not work.
Conditions:
Cat 3850/Cat 3650
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: * | 15.2(2)E3, 15.2(3)E3, 15.2(4)E, 3.6(3)E, 3.7(3)E, 3.8(0)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv19773 | Title: | "nmsp attach suppress" not being added into run-config on WS-C3850-24P |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"nmsp attach suppress" disables IPDT related feature on the interface, however command is not added into run-config, hence upon a reload IPDT is still enabled and Customer has to disable it once again:
B.06-3800-8(config)#do sh ip devic tra int gi1/0/1
--------------------------------------------
Interface GigabitEthernet1/0/1 is: STAND ALONE
IP Device Tracking = Disabled
IP Device Tracking Probe Count = 3
IP Device Tracking Probe Interval = 30
IPv6 Device Tracking Client Registered Handle: 98
IP Device Tracking Enabled Features:
HOST_TRACK_CLIENT_ATTACHMENT
--------------------------------------------
B.06-3800-8(config)#int gi1/0/1
B.06-3800-8(config-if)#nmsp attachment suppress
B.06-3800-8(config)#do sh run int gi1/0/1
Building configuration...
Current configuration : 38 bytes
!
interface GigabitEthernet1/0/1
end
B.06-3800-8(config)#do sh ip device track int gi1/0/1
--------------------------------------------
Interface GigabitEthernet1/0/1 is: STAND ALONE
IP Device Tracking = Disabled
IP Device Tracking Probe Count = 3
IP Device Tracking Probe Interval = 30
IP Device Tracking Enabled Features:
--------------------------------------------
Conditions:
- WS-C3850-24P running 3.7.0E or 3.7.1E
Workaround:
- add manually "nmsp attach suppress" under each interface upon every single reload of the switch
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 3.7(0)E |
|
Known Fixed Releases: * | 15.2(3)E3, 15.2(4.0.29)EA1, 15.2(4.0.75a)E, 15.2(4.0.80)E, 15.2(5.0.10)E, 15.3(1)IE101.241, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv22736 | Title: | After reload, C3850-NM-4-10G/GLC-SX-MM not linkup with speed nonegotiate |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After reload the switch with "speed nonegotiate" configuration, 1G Fiber link is not coming up on
3850 while connecting with other platforms like cat6k,cat2k. There is no issue with 10G fiber links.
Conditions:
This issue is only seen during bootup with "speed nonegotiate" setting.
Also this issue occurs on all 1G uplink ports on 3650 and 3850 platforms using 1G Fiber SFP.
Workaround:
Delete "speed nonegotiate" and input same configuration again.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(2)E, 15.2(3)E, 16.1(0) |
|
Known Fixed Releases: * | 15.2(2)E3, 15.2(3)E3, 3.6(3)E, 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut87285 | Title: | MAC address being learnt on an individual Port-channel member interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
*MAC addresses flapping messages are being displayed on a 3850 stack of five switches running IOS 03.06.00SE.
* Some of the MAC addresses are seen on the port-channel interface and some other MAC addresses are seen on the port-channel member interfaces.
* Issue seems to be cosmetic at this point.
%SW_MATM-4-MACFLAP_NOTIF: Host 54ee.753a.4112 in vlan 999 is flapping between port Te1/1/3 and port Po32
%SW_MATM-4-MACFLAP_NOTIF: Host 54ee.753a.4112 in vlan 999 is flapping between port Te1/1/3 and port Po32
%SW_MATM-4-MACFLAP_NOTIF: Host a0a8.cd60.2944 in vlan 883 is flapping between port Te1/1/3 and port Po3
Conditions:
* 3850 stack of 5 switches.
* Switches version 03.06.00E
* On previous versions this behavior was not seen.
Workaround:
Disabling IPDT on trunk interface helped to decrease the number of MAC flaps being logged and increased the time it will take for a particular MAC to flap.
However, the flapping still occurs approximately every 15 minutes.
Further Problem Description:
|
|
Last Modified: | 20-JAN-2016 |
|
Known Affected Releases: | 15.2(2)E |
|
Known Fixed Releases: * | 15.2(3)E3, 16.1(1.21), 16.3(0.4), 3.7(3)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux25383 | Title: | Passwords still encrypted after encryption key is removed |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After removing the encryption key with "no key config-key password-encrypt", any new passwords that are entered are still being encrypted.
Conditions:
Password encryption is enabled with "password encryption aes", and a key has been previously configured with "key config-key password-encrypt".
Note that disabling encryption does not cause any already-encrypted passwords to get decrypted. It only applies to any new passwords that are entered from that point on.
Workaround:
Disable password encryption with "no password encryption aes".
Further Problem Description:
Note that disabling encryption does not cause any already-encrypted passwords to get decrypted. It only applies to any new passwords that are entered from that point on.
|
|
Last Modified: | 11-JAN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.2(0.249), 16.3(0.33) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux24971 | Title: | WebUI: Configure>Access Points>Radio takes 3 minutes to load |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
GUI: configure>access point>radio a or b/g takes ~ 3 minutes to load
Conditions:
GUI
Workaround:
wait for GUI to load AP radio info or use CLI instead
Further Problem Description:
|
|
Last Modified: | 13-JAN-2016 |
|
Known Affected Releases: | 16.1(0) |
|
Known Fixed Releases: * | 16.2(0.252), 16.3(0.42) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCug87984 | Title: | %Generating 1024 bit RSA keys, keys will be non-exportable |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a customer boots up a switch with a default configuration, they will see the system configuration dialog prompt interrupted by the "% % Generating 1024 bit RSA keys, keys will be non-exportable..." string.
CONSOLE OUTPUT:
Would you like to enter the initial configuration dialog? [yes/no]: % Generating 1024 bit RSA keys, keys will be non-exportable...
Also, when you press a key, such as the letter 'n' to type "no," the following appears:
CONSOLE OUTPUT:
Would you like to enter the initial configuration dialog? [yes/no]: % Generating 1024 bit RSA keys, keys will be non-exportable...
[OK] (elapsed time was 1 seconds)
Compressed configuration from 2653 bytes to 1370 bytes[OK]no
Conditions:
You will only run into this issue if your switch boots up with the factory default configuration and you go through the system configuration dialog.
Workaround:
You can simply ignore the messages and just answer the prompted questions by typing "yes/no" to go through the configuration dialog or bypass it.
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 15.0SID |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 28-JAN-2016 |
|
Known Affected Releases: | 15.0SID |
|
Known Fixed Releases: * | 15.2(3)E3, 3.7(3)E |
|
|
| |
| |
|
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: | 23-JAN-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)ZD(0.239), 7.3(1)D1(0.2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux63710 | Title: | SPANTREE_VLAN_SW-2-MAX_INSTANCE message logged every time link comes up |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
%SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of 128 STP instances exceeded. No instance created for VLAN129 messages are generated every time a trunk port comes up on a system with more then 128 Vlan's running PVST
Conditions:
- More vlans are configured on the 3650/3850 switch then Spanning Tree instances supported
- Trunk port coming up carrying all VLAN's
Workaround:
Further Problem Description:
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | Denali-16.1.1 |
|
Known Fixed Releases: * | 16.1(1.51), 16.2(0.261), 16.3(0.48) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy04464 | Title: | 3850 TPID recognition |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
when 3850 get packets TPID 88A8 , it will not drop packet but forward as 8100
Conditions:
Q in Q
Workaround:
unknown
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: | 15.2(3)E |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux08368 | Title: | wshark : capture not stopped after packets limit reached |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom:
wshark capture not stopped after packets limit reached
Conditions:
wshark capture not stopped after packets limit reached on edison box after icmp packet
Workaround:
Don't know
Further Problem Description:
|
|
Last Modified: | 29-JAN-2016 |
|
Known Affected Releases: * | Denali-16.3.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux65429 | Title: | "Power Controller reports power Imax error detected" PoE log on 3850 |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom:When connecting a PoE device (Cisco Access Points in this case) on a 3850 switch (WS-C3850-48U-S) the following logs are seen:
%ILPOWER-5-IEEE_DISCONNECT: Interface Gi1/0/32: PD removed
%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/32: Power Controller reports power Imax error detected
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/32, changed state to down
%LINK-3-UPDOWN: Interface GigabitEthernet1/0/32, changed state to down
Then, the PoE devices get disconnected and turned off.
Conditions:Connecting Cisco or 3rd Party IP Phones or Access Point to any port of the 3850 switch will throw the Imax error and the PoE device will not be turned on.
The issue has been seen in versions 3.7.0 and 3.6.3.
Workaround:No workaround for this problem.
"power inline static max <>" command does not work as workaround.
|
|
Last Modified: | 22-JAN-2016 |
|
Known Affected Releases: | none |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux15679 | Title: | Dynamic SGT with VRF not getting mapped under VRF SGT mapping table |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
The Dynamic SGT with VRF is not saved in the VRF SGT-Map table. Rather, the binding is seen in the global RBM binding table.
Conditions:
If the New end point is assigned a tag and the binding is tied to an interface, the bindings are not saved in a VRF RBM table. This is because, the "cts role-based l2-vrf " creates a mapping between the vlan id and the VRF id. The CLI is not supported in polaris based platforms today. Without the CLI, the correlation of VRF to VLAN cannot be done and hence the binding will not be saved in right database.
Workaround:
There is no workaround. The CLI "cts role-based l2-vrf" needs to be supported to have mapping between VLAN and VRF.
Further Problem Description:
|
|
Last Modified: | 28-JAN-2016 |
|
Known Affected Releases: | 16.2.0 |
|
Known Fixed Releases: | |
|
|
| |
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论