Software Updates for ME 3800X Series Carrier Ethernet Switch Routers
Alert Type: | New Release | Product Name: | ME 3800X-24FS-M Switch Router | Software Type: | IOS Software | Release Version: | 15.3.3S7 | Release Date: | 22-FEB-2016 |
Software Updates for ME 3800X Series Carrier Ethernet Switch Routers
Alert Type: | New Release | Product Name: | ME 3800X-24FS-M Switch Router | Software Type: | IOS Software | Release Version: | 15.4.3S5 | Release Date: | 02-FEB-2016 |
Software Updates for ME 3800X Series Carrier Ethernet Switch Routers
Alert Type: | New Release | Product Name: | ME 3800X-24FS-M Switch Router | Software Type: | IOS Software | Release Version: | 15.5.3S2 | Release Date: | 12-FEB-2016 |
Software Updates for ME 3800X Series Carrier Ethernet Switch Routers
| ME 3800X-24FS-M Switch Router |
| | | | Suggested : | | Previously Suggested: | |
|
Known Bugs - ME 3800X Series Carrier Ethernet Switch Routers
| | |
Alert Type: | Updated * | Bug Id: | CSCtr79905 | Title: | Error msg while detaching and reattaching the policy on evc | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: Error message seen while detaching and reattaching a service policy on an EVC interface.
Conditions: The symptom is observed when detaching and reattaching the service policy on an EVC interface when port shaper is configured on the interface.
Workaround: A workaround is to not reuse the policy-map that is giving the error. Instead try to create a policy-map with a different name, copy the content over from the original policy-map, then try to attach the new policy to the target again. | |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.1(3)S | |
Known Fixed Releases: * | 15.1(2)EY1, 15.1(3)MR, 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S2.1, 15.1(3)S3, 15.1(3)S5, 15.1(3)S5a | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuq19149 | Title: | mVPN - ME3800 acting as 'P' router is causing PIM adj to drop b/w PE's | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom: mVPN setup, ME3800 acting as P router flushes S,G entry. The S,G on an 'P' router maintains the pim adjacency for the hello packets exchanged on the default mdt. Although continuous pim hello's are seen on 'P' router sent from the PE routers, but still the mroute output displays the S,G entry being deleted and re-created, thereby causing PIM adjacency to go DOWN between the PE's.
AND/OR
If the mVPN setup comprises of an PRIMARY PE which is sending mcast traffic regularly and an BACKUP PE which is passive and only takes over when PRIMARY is DOWN, it was noticed that the BACKUP PE's S,G on 'P' router was getting flushed.
Conditions: mVPN setup with ME3800 deployed as 'P' router.
Workaround: none
Further Problem Description:
| |
Last Modified: | 05-FEB-2016 | |
Known Affected Releases: | 15.3(3)S2 | |
Known Fixed Releases: * | 15.2(1)IC273.149, 15.2(2)E2, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(3)S3.13, 15.3(3)S4, 15.4(1)S2.14, 15.4(1)S3, 15.4(1)T2.1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuu99395 | Title: | BGP Flap seen with 64k ingress policer | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom: BGP packets may be dropped when 64k policer is configured on ingress
Conditions: Ingress class default policer with 64k Policer
Workaround: Increase the policer limit
Further Problem Description:
| |
Last Modified: | 15-FEB-2016 | |
Known Affected Releases: | 15.4(3)S3.1 | |
Known Fixed Releases: * | 15.5(3)S1.1, 15.5(3)S2, 15.6(0.8)S | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCua53772 | Title: | ME3800: Crash at epm_fwd_start_session on changing encap to qinq | |
Status: | Fixed | |
Severity: | 2 Severe | Description: * | Symptoms: Router crashes when scheduling a y1731 DMM IP SLA probe to run.
Conditions: This symptom happens when the probe's target cfm mep is configured under service instance with double tag encapsulation.
Workaround: There is no workaround.
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.3(1)S | |
Known Fixed Releases: * | 12.2(58)EZ, 12.2(60)EZ, 12.2(60)EZ1, 12.2(60)EZ2, 12.2(60)EZ3, 12.2(60)EZ4, 12.2(60)EZ5, 15.2(4)S0.2, 15.2(4)S1, 15.2(4)S1c | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuw93755 | Title: | ME3800 crashing due to RPF Fail packets punting to the CPU | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | ME3800 crashing due to RPF Fail packets punting to the CPU
Symptom: ME3800 crashing due to RPF Fail packets punting to the CPU
Conditions: ME3800 crashing due to RPF Fail packets punting to the CPU
Workaround: None
Further Problem Description:
| |
Last Modified: | 23-FEB-2016 | |
Known Affected Releases: | 15.4(3)S3.20 | |
Known Fixed Releases: * | 12.2(52)EY4, 15.2(1)S, 15.2(1)S1, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2, 15.2(2)SNI, 15.2(4)S1c, 15.2(4)S2, 15.2(4)S3 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv48214 | Title: | Untagged service instance encap resulting in RMEPs not being learnt | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom: RMEPs not being learnt
Conditions: 1.Configure switchport on RTB1 and RTB2 2.configure cfm mep on both box 3.configure service instance and check for RMEP
Workaround: na
Further Problem Description: na
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | 15.6(1)S | |
Known Fixed Releases: * | 15.5(3)M0.2, 15.5(3)M1, 15.5(3)S1, 15.5(3)S1a, 15.6(0.10)T, 15.6(0.13)S, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCua79633 | Title: | ME3800:Delay variance observation is not accounting when dly var = 0 | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom: When DMM are configured on whales sometimes we ignore 2 observations in the results Conditions: When we configure DMM probes on whales. Does not happen consistently Workaround: no work around | |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.3(1)S | |
Known Fixed Releases: * | 12.2(58)EZ, 15.2(4)S1.6, 15.2(4)S2, 15.3(0.10)T, 15.3(0.16)S, 15.3(0.8.4)PIH20, 15.3(1)S, 15.6(1)SN | |
|
| |
|
没有评论:
发表评论