| |
Bug Id: | CSCus84535 |
Title: | ME3600 - Native Vlan Packets Getting Tagged. |
|
Description: | Symptom:
ME3600 - Native Vlan Packets Getting Tagged.
The issue is seen only for the forwarding traffic not the device generated traffic.
Issue was seen on IOS 15.4(3)S1
Conditions:
nterface GigabitEthernet0/5
switchport trunk native vlan 901
switchport trunk allowed vlan 901
switchport mode trunk
The packets leaving the interface Gi0/5 if it is forwarding traffic will tagged with vl 901 which they shouldn't
The issue is seen only for forwarding traffic not the device generated traffic.
Workaround:
Configure the interface as access interface if the allowed vlan and native vlan is same
But it vary based on the scenario.
Further Problem Description:
none
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 04-MAY-2015 |
|
Known Affected Releases: | 15.4(3)SS |
|
Known Fixed Releases: | 15.5(2.22)S |
|
|
| |
| |
Bug Id: | CSCus95026 |
Title: | High CPU utilization seen with E-Line circuit and mac-learning disabled |
|
Description: | Symptom:
High CPU utilization seen with E-Line circuit and mac-learning disabled
Conditions:
High CPU utilization seen with E-Line circuit and when mac-learning is disabled
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 05-MAY-2015 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: | 15.4(3)S2.9, 15.5(1)S1.1, 15.5(2.17)S |
|
|
| |
| |
Bug Id: | CSCuo31527 |
Title: | OSPF packets NOT forwarded |
|
Description: | Symptom:
OSPF neighbourship will not form, and all other control plane which uses Multicast address will be affected. This issue is a timing issue, so it wont be seen always.
Conditions:
the timing issue should happen to the first EFP which is added. if the problem doesnt happen for the first EFP, further efp's created will not have a problem
Workaround:
Disable igmp snooping and enable again.
Further Problem Description:
None
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | 15.3(3)S3.6, 15.3(3)S4, 15.4(1)S2.7, 15.4(1)S3, 15.4(2)S2, 15.4(2.17)S0.11, 15.4(3)S, 15.5(0.10)S |
|
|
| |
| |
Bug Id: | CSCus56197 |
Title: | ME1200 controller: ME3600 reloads in 15.4(3)S1 |
|
Description: | Symptom:
Customer reported ME3600 reload with NID controller support added in the image.
Conditions:
ME3600 running 15.4(3)S1
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 06-MAY-2015 |
|
Known Affected Releases: | 15.4(3)S1.1 |
|
Known Fixed Releases: | 15.5(1)S0.10, 15.5(1)S1, 15.5(1)SN1, 15.5(1.18)S0.9, 15.5(2.10)S |
|
|
| |
| |
Bug Id: | CSCum55294 |
Title: | vlanTrunkPortDynamicState OID not available when interface goes up |
|
Description: | Symptom:
vlanTrunkPortDynamicState OID is available and returns some value when interface is in either down or admin down state. As soon as the interface goes up this OID is no longer available and the switch returns that "No Such Instance currently exists at this OID".
Conditions:
Discovered in 15.3(3)S. Also affecting 15.4(1)S. Found on ME3600X.
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 07-MAY-2015 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | 15.3(3)S3.6, 15.3(3)S4, 15.4(1)S2.20, 15.4(1)S3, 15.4(2)S2.1, 15.4(2)S3, 15.4(2.17)S0.7, 15.4(3)S, 15.4(3)SN1, 15.5(0.7)S |
|
|
| |
| |
Bug Id: | CSCup42207 |
Title: | wanphy flag j1 transmit inconsistent behaviour with Run/Start config |
|
Description: | Symptom:
1) wanphy flag j1 transmit command availability is having inconsistent behavior with Run/Start config,
1) description is removed from the running config after reload though it is available in start-up config
3) random config is seen in running config after reload though it is not configured in start-up config
Conditions:
Seen only on "wanphy flag j1 transmi" configured with no value available in "Running config" or in "Start-up Config"
issue 2 & 3 is seen after reload of the device.
Workaround:
for issue 2 need to configure the same after reload and for issue 3 random config we should remove it from running config.
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 11-MAY-2015 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | 15.3(3)S3.8, 15.3(3)S4, 15.4(1)S2.19, 15.4(1)S3, 15.4(2)S1.4, 15.4(2)S2, 15.4(3)S0.3, 15.4(3)S1, 15.4(3)S2, 15.5(0.15)S |
|
|
| |
| |
Bug Id: | CSCuq96419 |
Title: | WH2: Address MCB timeout issue on VSC8574x |
|
Description: | Symptom:
The following log is observed after the system bootup (and continues to be observed later as well):
000268: Aug 29 08:46:00.269 brz-3: SPI pause fail!, port 340020368
000269: Aug 29 08:46:00.269 brz-3: MCB timeout, port_no 340020264
When this issue occurs, some 1G port in the system (due to another bug in the software, the port number is not displayed correctly in above log message), has an issue in dealing with PTP packets. The timestamp module on those ports in the PHY does not work correctly and the recovered clock accuracy could go bad. No other traffic is impacted when this symptom is seen.
Conditions:
The problem could occur when the switches have Rev.D PHY chips with a very thin frequency (of about 2-3 times a year with multiple reboots). From the observations of this issue, the occurrence has been linked to the bootup of the box with the PTP configuration.
Workaround:
Router reload is the only workaround, based on the strong observation so far that the occurrence rate is very thin.
Further Problem Description:
The issue is reasoned out to be a bug in the PHY chip that results in a lockup inside the chip resulting in the 1588 registers being not accessible. So, further 1588 register read/write access on the PHY fails that presents this issue.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 12-MAY-2015 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: | 15.4(1)S2.23, 15.4(1)S3, 15.4(2)S2.2, 15.4(2)S3, 15.4(3)S1.5, 15.4(3)S2, 15.5(1)S1.1, 15.5(1.13)S, 15.5(2)S |
|
|
| |
| |
Bug Id: | CSCuo85634 |
Title: | W2: PTP sideband processor is getting rebooted after every 14day |
|
Description: | Symptom:
PTP sideband processor reboots every 14 days.
Conditions:
PTP is configured and kept running for a long duration
Workaround:
None
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Last Modified: | 18-MAY-2015 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: | 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)SXI10, 12.2(33)SXI11, 12.2(33)SXI12 |
|
|
| |
| |
Bug Id: | CSCui73553 |
Title: | CPUHOG/High Cpu issue with SFF8472 on ME-3600X/ME-3800X |
|
Description: | Symptom:
Metro Ethernet switch may see high cpu and/or CPUHOG errors at process SFF8472. This condition may eventually lead to a crash.
Conditions:
SFPs in use which support DOM.
Workaround:
use a sfp without Dom or disable Dom monitor
ME3600(config)# transceiver type all
ME3600(config-xcvr-type)# no monitoring
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 19-MAY-2015 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | 15.3(3)S0.8, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S3, 15.3(3)S4, 15.4(0.19)S0.4, 15.4(1)S, 15.4(1)S0a |
|
|
| |
| |
Bug Id: | CSCus16820 |
Title: | High cpu due to virtual exec or non-qos events process |
|
Description: | Symptom:
High cpu can be observed caused by two processes:
1. When service-policy is being applied/removed, high cpu caused by virtual exec is observed and vty session hangs
2. When switchport trunk allowed vlan command is executed, high cpu is caused by non-qos events process
Duration of high cpu (and vty session hangs) depends on number of vlans allowed on switch. Changing number of allowed vlans to small value doesn't fix the problem.
In some rare cases this may lead to crash of metro ethernet switch.
Conditions:
Problem starts when we apply command switchport trunk allowed vlan with big range of vlans which are also in vlan database (more than 500) and service-policy on same interface. After that problem is propagated to all other interfaces regardless what is configured there. Problem is also there when we remove both configuration lines (only removing configuration and reload fix the problem).
So far problem was not seen in IOS 15.4(2)S, 15.4(3)S and 15.5(1)S
Workaround:
Do not have interface configuration with service-policy and switchport trunk allowed vlan (more than 500 vlans).
Upgrade to 15.4(2)S, 15.4(3)S or 15.5(1)S
Problem is also not seen in version 15.4(1)S1. Last IOS where problem is seen is 15.4(1)S
Further Problem Description:
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 21-MAY-2015 |
|
Known Affected Releases: | 15.3(3)S1, 15.4(1)S |
|
Known Fixed Releases: | 15.5(1)S1.1, 15.5(1)SN1 |
|
|
| |
| |
Bug Id: | CSCue30590 |
Title: | IPv6 site-local multicast packet gets looped back on svi-eompls |
|
Description: | Symptoms: Packet loss are seen over pseudowire and high CPU.
Conditions: This symptom is observed when IPv6 site-local multicast MAC traffic
is sent over SVI EoMPLS, the traffic is looped between the PE of the EoMPLS.
Workaround: There is no workaround.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 21-MAY-2015 |
|
Known Affected Releases: | 15.2(4)S1, 15.3(1)S |
|
Known Fixed Releases: | 15.2(4)S2.11, 15.2(4)S3, 15.2(4)S3a, 15.2(4)S4, 15.2(4)S4a, 15.2(4)S5, 15.2(4)S6, 15.3(1)S1.2, 15.3(1)S2, 15.3(1.17)S0.13 |
|
|
| |
| |
Bug Id: | CSCus96586 |
Title: | Ptp clock stuck on ACQUIRING state for very long time |
|
Description: | Symptom:
PTP slave stuck on ACQUIRING state for very long time . seems to be large mean path delay and clock offset .
Conditions:
you could see this issue with ptp config .
Workaround:
not known
Further Problem Description:
none
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 23-MAY-2015 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: | 15.4(3)S2.5, 15.5(1)S1.1 |
|
|
| |
| |
Bug Id: | CSCuh69434 |
Title: | ME-3600X-24FS-M/15.3(2)S1 newly created AToM pseudowires are down |
|
Description: | Symptom:
newly created AToM pseudowires are down
Conditions:
ME-3600X-24FS-M/15.3(2)S1
after the software upgrade from 15.2(2)S1 to 15.3(2)S1
Workaround:
not awailable
|
|
Status: | Other |
|
Severity: | 2 Severe |
Last Modified: | 26-MAY-2015 |
|
Known Affected Releases: | 15.3(2)S1 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCub36217 |
Title: | MAC securtiy is not working in MCP_DEV/XE37 |
|
Description: | Symptom:
When the ME3800 router is running IOS 15.2(04)S software, if EVC maximum MAC security
address limit is reached for a service instance, new MAC address is not rejected.
Conditions:
when EVC MAC security is enabled under a service instance.
Workaround:
There is no workaround.
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
1.7/1.3:
https://intellishield.cisco.com/security/alertmanager/cvssCalculator.do?dispatch=1&version=2&vector=AV:L/AC:L/Au:S/C:N/I:P/A:N/E:U/RL:OF/RC:C
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
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 26-MAY-2015 |
|
Known Affected Releases: | 15.2(4)S, 15.3(1)S |
|
Known Fixed Releases: | 12.2(50)SE1, 12.2(50)SE2, 12.2(50)SE3, 12.2(50)SE4, 12.2(50)SE5, 12.2(50)SG4, 12.2(50)SG6, 12.2(50)SQ, 12.2(50)SQ5, 12.2(50)SQ6 |
|
|
| |
| |
Bug Id: | CSCur98665 |
Title: | ciscoipc process crashed when do swap ptp master/slave role |
|
Description: | Symptom:
ciscoipc process crashed , service disruptive
Conditions:
you can see this issue while swap the ptp role
Workaround:
The PTP processor could be reloaded to apply the configuration again through the following command:
test platform software ptp reset
Further Problem Description:
none
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 27-MAY-2015 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: | 15.4(3)S2.3, 15.5(1)S1.1, 15.5(2.21)S0.5 |
|
|
| |
| |
Bug Id: | CSCuu49953 |
Title: | Unicast Flooding is observed on a Customer routed Pseudo wire network |
|
Description: | Symptom:
Unicast Flooding is observed on a Customer routed Pseudo wire network
Conditions:
Topology
========
Spirent1 ?????? 881 ?????? KJJ-SW1 ?????? KJJ-SW2 ?????? Spirent2
1. Configure a Routed Pseudowire between KJJSW1 and KJJSW2.
2.Configure a routed port between KJJsw1 to router 881 working as NAT.
3. Create a loopback ip address on 881 router.
4.Ping the loopback ip address from Kjjsw2.
5. we could see the packets are flooded to spirent2.
customer is trying to ping the lopopback address which is located on cisco 881 router from KJJSW2(Whales 2).
Ping packet are flodded to all the ports in vlan 10 .
On our topogy, It going out to Spirent2.
Workaround:
NA
Further Problem Description:
NA
|
|
Status: | Open |
|
Severity: | 2 Severe |
Last Modified: | 28-MAY-2015 |
|
Known Affected Releases: | 15.4(3)S2.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
Bug Id: | CSCtu42387 |
Title: | %SFF8472-3-THRESHOLD_VIOLATION: Gi0/11: Rx power high alarm |
|
Description: | Symptoms: Gigabit and 10 Gigabit Fiber link reporting threshold violation alarm
in Cisco ME3600, Cisco ME3800, and Cisco 7600 devices.
The "%SFF8472-3-THRESHOLD_VIOLATION: Gi0/11: Rx power high alarm" error message
is seen on ports.
Conditions: This symptom is observed on Cisco ME3600, Cisco ME3800, and Cisco
7600 devices. The messages are seen with the interface shut or no shut.
SFF8472-3-THRESHOLD_VIOLATION Gi5/1: Rx power low alarm; Operating value:
-28.5 dBm, Threshold value: -24.0 dBm
Workaround: Fixing the fiber signal issue or disconnecting the fiber from the
transceiver has been known to stop the messages.
|
|
Status: | Fixed |
|
Severity: | 2 Severe |
Last Modified: | 28-MAY-2015 |
|
Known Affected Releases: | 12.2(33)SRE, 12.2(33)SRE6, 12.2(33)SRE7a, 15.1(3)S3, 15.2(2)S |
|
Known Fixed Releases: | 12.2(33)SRE8, 12.2(33.7.15)SRE, 15.1(3)S4.21, 15.1(3)S5, 15.1(3)S7, 15.1(3)S7.1, 15.2(1.18)S0.6, 15.2(2)S, 15.2(2.5)S, 15.2(4)S5.7 |
|
|
| |
没有评论:
发表评论