| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy92651 | Title: | Multicast is duplicated due to leftover MET chain entry |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Multicast traffic is duplicated during replication due to same entry existing 2 times in the MET table.
Conditions:
More than one EFP and one of the EFP leaves the group through a group leave.
Workaround:
Shut/no shut EFP corresponding to problem vlan.
Further Problem Description:
|
|
Last Modified: | 25-APR-2016 |
|
Known Affected Releases: | 15.4(3)S4.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz34638 | Title: | BFD Control Packets using wrong UDP port in ME-3600X-24CX |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ME3600 sends BFD Control packets with UDP src port and dest port set as 3784.
The source port MUST be in the range 49152 through 65535 per RFC5881.
As a consequence, in our lab, BFD session is not coming up between ME-3600X and ASR-907.
This issue was found in interop tests between ME-3600 and ASR-907. ASR-907 only supports BFD Control and it has hardware off-load.
This hardware performs UDP source port validation and does not initiate BFD session when neighbor is using source port 3784.
Conditions:
This condition happens only with BFD Control Packets with Hardware offload.
Workaround:
Use BFD features that demands BFD packets to be processed in software, for example, BFD authentication.
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 15.4(3)S4.1 |
|
Known Fixed Releases: | 15.6(1.27)SP |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz45578 | Title: | ME3600 env power state machine broken |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
1.Syslog and snmpwalk are not reported for power supply restored state when less than 1 sec power supply is down.
2.when input power drops, we see the wrong syslog message ?output power faulty? (should be unkown) and snmp return code 2 (warning) instead of 3 (critical).
Conditions:
na
Workaround:
Syslog and snmpwalk are reported correctly for power supply restored state when greater than 1 sec power supply is down
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu62592 | Title: | MPLS data plane broken on ME3600 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MPLS data plane is broken. Labeled traffic is dropped. IP traffic works fine
Conditions:
Link Flap or Reload
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.5(3)S2.8 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy12848 | Title: | ME3600 drop bfd packets when there is traffic congestion. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ME3600 drop bfd echo packets from the remote-node, which is returned on the local, in the egress queue when there is traffic congestion.
when we configure service-policy, we can see increment of drop counter in the output of "show policy-map interface output".
Conditions:
a) congestion happens in the queue(class) that ip precedenc 6 is allocated in "service-policy output".
(ip precedence of BFD packet is 6)
or
b) no service policy on the egress port.
Workaround:
use bfd async mode without echo (disable bfd echo mode)
Further Problem Description:
BFD session flaps were occurring because BFD echo traffic (which is from the remote node and returned on the local) is sent through transit packet queue and merged with egressing data traffic.
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 15.4(3)S1.1 |
|
Known Fixed Releases: * | 15.5(3)S2.8 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz22404 | Title: | ME3600x Constant Platform assert failure (del_l2m_phy_met) and traceback |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traceback (platform assert failure: 0: ../src-nile/src-asic-nile/nile_adjmgr.c: 13987: del_l2m_phy_met) is seen when port-channel member links are flapped
Conditions:
Issue is seen when IGMP groups should be learned for VLANs of port-channel in IGMP snooping table and member-links are flapping.
Workaround:
Issue is not seen when port-channel member links are stable
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 15.4(3)S2.1, 15.4(3)S4.1 |
|
Known Fixed Releases: * | 15.5(3)S2.9 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz16770 | Title: | Multicast stopped to work upon applying split-horizon to bridge-domain |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
The multicast traffic even after having (S,G) and (*,G) entry on Last-hop-router in the mroute table stops forwarding to receiver if split-horizon group is added to the Bridge-domain under service-instance.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 13-APR-2016 |
|
Known Affected Releases: | none |
|
Known Fixed Releases: | |
|
|
| |
没有评论:
发表评论