| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq02069 | Title: | CUBE-SP HA Calls Fail/High CPU if CRYPTO PKI command entered on Standby |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: | Symptom:
CUBE-SP calls start failing and high CPU is reported when a crypto pki command is entered on the stand-by ASR.
Conditions:
CUBE-SP is configured for HA
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(1)S1.1 |
|
Known Fixed Releases: * | 15.3(3)S3.8, 15.3(3)S4, 15.4(1)S2.10, 15.4(1)S3, 15.4(2)S1.4, 15.4(2)S2, 15.4(3)S0.1, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts42154 | Title: | ASR Fails to Register after the Initial Attempt Failing |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: After the Cisco IOS ASR 1006 router is reloaded, it fails to
reregister to the key server. From the debugs, it is observed that the
attempt to register is generated too early before the GDOI is ON. This
registration attempt is made before the interface, through which GDOI
registration traffic with the key server passes, goes to the UP state.
Conditions: This symptom is observed on a Cisco IOS ASR 1006 router that runs
Cisco IOS Release 15.0(1)S2 and Cisco IOS Release 15.0(1)S3.
Workaround: Use the clear crypto gdoi command to fix this
issue.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.0(1)S2, 15.0(1)S3 |
|
Known Fixed Releases: * | 15.0(2)EA, 15.0(2)EB, 15.0(2)EC, 15.0(2)ED, 15.0(2)EH, 15.0(2)EJ, 15.0(2)EJ1, 15.0(2)EK, 15.0(2)EK1, 15.0(2)EX |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtr29831 | Title: | ASR1000-WATCHDOG: Process = SXP CORE when adding 1k sxp connection |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
SXP cored
Conditions:
when bring up 1000 sxp connections
Workaround:
None
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S |
|
Known Fixed Releases: * | 15.0(1)SY1, 15.0(1)SY2, 15.0(1)SY3, 15.0(1)SY4, 15.0(1)SY5, 15.0(1)SY6, 15.0(1)SY7, 15.0(1)SY7a, 15.0(1.9)AWD, 15.0(10.32)EMW |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts99455 | Title: | ASR1K BR FP crash when MC controls applications through PBR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: BR FP crash occurs on a Cisco ASR 1000 series router when the Master Controller controls applications through PBR.
Conditions: This symptom occurs when the PfR Master Controller tries to enforce its path selection for application traffic (PBR based route control). The FP on BRs crashes and reloads.
Workaround: There is no workaround.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.1(3)MR, 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S1.5, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt23038 | Title: | IOSD core @flow_lock_lock when issuing show command during HA tests |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: IOSD crashes while executing the "show flow monitor name monitor2"
command after an RP downgrade on bay 0.
Conditions: This symptom is observed during a Cisco ASR 1004 ISSU downgrade
from MCPDEV to Cisco IOS XE Release 3.5.
Workaround: There is no workaround.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.0(5.2)DPB20, 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2, 15.1(2)SY3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt32165 | Title: | ASR - Cube Ent. race condition causes calls to fail with cause 47 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: The Cisco Unified Border Element Enterprise on the Cisco ASR 1000
series router can fail a call with cause 47 immediately after the call connects.
Conditions: This symptom is observed with a sufficient call volume and a call
flow that redirects many calls. The Cisco ASR router can fail to provision the
forwarding plane for the new call due a race condition where a prior call is
not completely cleaned up on the forwarding plane before trying to use the same
structure again.
The show voip fpi stats command output indicates that a
failure has occurred if the last column is greater than zero. For example:
show voip fpi stats | include provisn rsp
provisn rsp 0 32790 15
Workaround: There is no workaround. However, Cisco IOS Release 3.4.1 is less
impacted by these call failures due to a resolution of defect CSCts20058.
Upgrade to Cisco IOS Release 3.4.1 until such time as this defect is resolved.
In a fully redundant Cisco ASR 1006 router, you can failover the ESP slots to
clear the hung entries in the forwarding plane. Other platforms will require a
reload.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S, 15.2(0.2)S |
|
Known Fixed Releases: * | 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S1.7, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6, 15.1(3)S7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt35936 | Title: | RLS3.4 EIGRP route updates are not sent to DMVPN spokes |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: EIGRP route updates are not sent to DMVPN spokes. The show
ip eigrp inter command output shows pending routes in interface Q,
which remains constant. The show ip eigrp int deta command
output shows that the next sequence number of the interface remains the same
(does not advance).
Conditions: This symptom occurs when EIGRP session flapped, resulting in routes
being withdrawn and restored.
Workaround: Add a static route on any spoke that kicks out EIGRP learned routes
from the RIB table; this will again kick the interface on the HUB.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S1 |
|
Known Fixed Releases: * | 15.0(1)IA273.167, 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2, 15.1(2)SY3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtu08608 | Title: | ASR Cube Ent - Standby RP Crashing |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptoms: The standby RP crashes due to Voip HA Session App.
Conditions: The Cisco ASR 1000 platform with redundant RPs and Cisco Unified
Border Element Enterprise. The signature in the crashinfo is as follows:
UNIX-EXT-SIGNAL: Segmentation fault(11), Process = Voip HA Session App
Workaround: There is no workaround.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S, 15.2(2)S |
|
Known Fixed Releases: * | 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S1.5, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6, 15.1(3)S7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt21701 | Title: | ASR CUBE crashed while changing the SDP through UPDATE with SDP passthru |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
ASR CUBE is getting crashed when the endpoint tries to change IP address and media port in an early dialog UPDATE,but for codec change it works fine.
Conditions:
The crash is seen only when SDP passthrough is enabled and IP address and media port are being changed by an early dialog UPDATE.
Workaround:
Without SDP passthrough it works fine.
Further Problem Description:
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: * | 15.1(3)S4, 15.2(2)S |
|
Known Fixed Releases: * | 15.1(3)S5.7, 15.1(3)S6, 15.1(3)S7, 15.2(1.17)S, 15.2(2)S, 15.2(2.7)T, 15.2(3)GC, 15.2(3)GC1, 15.2(3)GCA, 15.2(3)GCA1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtu01172 | Title: | ASR crash due to CUBE HA application config w/o the redundant device. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptoms: The Cisco ASR 1000 series router without an actual redundant router
may crash when configured for CUBE HA based on the document "Cisco Unified
Border Element High Availability(HA) on ASR platform Configuration Example."
Conditions: This symptom is observed with the Cisco ASR 1000 series router.
Workaround: Remove the application configuration, that is, "no application
redundancy".
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S |
|
Known Fixed Releases: * | 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S1.4, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6, 15.1(3)S7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt17785 | Title: | IOS EIGRP Speaker Does Not Install Routes from ASA Peer |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When an IOS EIGRP speaker is peering to an ASA a peering relationship is established and routes are exchanged but the IOS device never installs the routes into the EIGRP topology table.
Conditions:
This issue issue is only seen with IOS EIGRP speakers running EIGRP release 8.0 or later and the ASA speaker does not have the fix for CSCuc92292.
The IOS EIGRP version can be verified with the command show eigrp plugin
IOS-Router#show eigrp plugin
EIGRP feature plugins:::
eigrp-release : 8.00.00 : Portable EIGRP Release
Workaround:
There is no workaround for this issue.
Additional Information:
After the neighbor relationship establishes the output of show ip eigrp neighbor detail on the IOS device will report the ASA as using EIGRP version "0.0/0.0"
IOS-Router#show ip eigrp neighbor detail
EIGRP-IPv4 Neighbors for AS(65535)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.10.80.2 Vl120 12 2d18h 1 3000 0 8
Version 0.0/0.0, Retrans: 1, Retries: 0
Topology-ids from peer - 0
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S |
|
Known Fixed Releases: * | 15.1(1)SY, 15.1(3)MR, 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S2.4, 15.1(3)S3, 15.2(1)E, 15.2(1)E1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtu14409 | Title: | Not able to update a policy with priority to pri + police |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: The "Insufficient bandwidth 2015 kbps for bandwidth guarantee" error
message is displayed when configuring a policy map with "priority level xxx"
and then updating it with "police cir xxx".
Conditions: This symptom occurs when the priority is configured without a
specific rate. This issue is only seen with a Cisco ASR 1000 series router.
Workaround: Configure police before priority.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(2)S |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EX0.5, 15.2(1)EY, 15.2(1.18)S0.10, 15.2(2)E, 15.2(2)E1, 15.2(2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy04962 | Title: | XE317:Ucode Core@l2bd_bfib_ager_timer_init during traffic in Kingpin |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
While testing XE317 image with below 4 features in Kingpin platform, observing fman_fp and cpp_mcplo_ucode core files during traffic.
Features:
++++++++
xe37_urpf_acl
xe37_nbar
xe39_vlan0
xe39_evc
Conditions:
Fman_fp and cpp_mcplo_ucode core files is seen during traffic in Kingpin platform.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts45619 | Title: | ASR: Fax calls through cube enterprise w/ IOS MTP can fail w/ cause 47 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptoms: T.38 Fax calls through the CUBE enterprise on the Cisco ASR
platfrom with the Cisco IOS MTP colocated on the ASR can fail with cause 47
and subsequently leak a structure on the forwarding plane, causing future
call failures.
Conditions: This symptom is observed with T.38 calls through the CUBE
enterprise on the Cisco ASR platform (only) with colocated MTPs in the call
flow.
Workaround: On nonredundant ASR platforms, a reload is required to clear the
hung structures on the forwarding plane.
On the Cisco ASR1006 with redundant RPs and ESPs, you can perform a
switchover of the ESPs (FPs) to clear the problem, as follows:
hw-module slot F0 reload
! confirm via show platform that the F0 is in a ok, standby state, takes some
time for the F0 to reload.
sh platform
! do not execute the below command until F0 is back online
hw-module slot F1 reload
! again, confirm via show platform that the F1 is in a ok, standby state
sh platform
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: * | 15.1(1)S |
|
Known Fixed Releases: * | 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S0.9, 15.1(3)S1, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx15799 | Title: | MTP on ASR sends ORC ACK athough CRC has come for that channel ID |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptoms: An MTP on a Cisco ASR router sends an "ORC ACK" message through CRC
for the channel ID that is just received but does not reply to the ORC for
the next channel.
Conditions: The symptom is observed when there is a very short time lapse
between the ORC and CRC, say 1 msec.
Workaround: There is no workaround.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.0(1)S3 |
|
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.3(0.13)PI21a, 15.3(0.13)T, 15.3(0.20)S0.3, 15.3(1)S, 15.3(1)S1, 15.3(1)S1e, 15.3(1)S2, 15.3(1)T, 15.3(1)T1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv01168 | Title: | SPA-2XCT3/DS0 controller is not coming up on fresh reboot. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
While testing with the mcp_ceop_t3t1_cem_func functionality the serial interface was not able to up..
Conditions:
Issue is seen with asr1k platform
Workaround:
Can Make the serial interface up by giving no shut again to the other end which was already in no shut mode
..
Further Problem Description:
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S1.4, 15.6(0.22)S0.15, 15.6(1.17)S0.10, 16.2(0.195) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz77171 | Title: | Subscriber drops not reported in mod4 accounting |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: Subscriber drops are not reported in mod4 accounting.
Conditions: This symptom is observed on checking policy-map interface for
account QoS statistics on a port-channel subinterface.
Workaround: There is no workaround.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(3)S |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EX0.5, 15.2(1)EY, 15.2(2)E, 15.2(2)S1.5, 15.2(2)S2, 15.2(2.19)S0.7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtt45654 | Title: | Virtual-Access is not deleted when tear down ipsec session |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: In a DVTI IPSec + NAT-t scaling case, when doing session flapping
continually, several Virtual-Access interfaces are "protocol down" and are not
deleted.
Conditions: This symptom can be observed in a DVTI IPSec + NAT-t scenario when
session flapping is done in the spoke side.
Workaround: There is no workaround.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.0(5.2)DPB35, 15.0(5.28)SID, 15.1(1)SG5.222, 15.1(1)SG5.223, 15.1(1)SG5.224, 15.1(1)SY, 15.1(2)SG1.90, 15.1(2)SIV11.1, 15.1(2)STV11.1, 15.1(2)SY |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz73836 | Title: | NHRP crash due to DMVPN event-trace |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: The router crashes.
Conditions: This symptom is observed when the router is running NHRP.
Workaround: There is no workaround.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.1(2)S1 |
|
Known Fixed Releases: * | 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2, 15.1(2)SY3, 15.1(2)SY4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub00822 | Title: | Continuous output of show sbc <sbc> call-stats all current15mins |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Continuous output of show sbc call-stats all current15mins
Conditions:
Adjcencies are more in numbers with running calls.
Workaround:
None.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S |
|
Known Fixed Releases: * | 15.1(3)S4.11, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6, 15.1(3)S7, 15.2(4)S0.1, 15.2(4)S1, 15.2(4)S1c, 15.2(4)S2, 15.2(4)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua56184 | Title: | RP crashes during flexvpn longevity after multiple RP switchovers |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: Multiple RP switchovers occur within a very short span of time.
Conditions: The symptom is observed with multiple RP switchovers on a Cisco ASR
1000 router and it fails to allocate an IPsec SPI.
Workaround: There is no workaround.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2, 15.1(2)SY3, 15.1(2)SY4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud64506 | Title: | HQF failed to clear on misconfigurations with Bandwidth Remaining ratio |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: HQF does not clear up when the bandwidth remaining ratio is
misconfigured on the child policy.
Conditions: This symptom is observed when an incorrect configuration triggers
the policy rejection and fails on the cleanup with the nondefault queue-limit
setting in the class-default class.
Workaround: Apply the configuration with the correct setting.
More Info:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 3.7(0) |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EX0.54, 15.2(1)EY, 15.2(1.1)EY, 15.2(1.1)PSR, 15.2(4)GC, 15.2(4)GC1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud94313 | Title: | CRYPTO-4-RECVD_PKT_INV_SPI during IPSec rekey due to pre-mature DEL msg |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PKI_INV_SPI messages seen on console
Conditions:
FlexVPN setup where i have Virtual-template configured , ipsec drops are seen.
Workaround:
None
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S, 15.3(1.17)S0.4, 15.3(2)S |
|
Known Fixed Releases: * | 15.1(2)IC66.3, 15.2(1)IC273.70, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E, 15.2(2)E1, 15.2(2.2.70)ST, 15.2(2b)E, 15.2(4.0)ST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud30128 | Title: | [AVC]: No FNF records on remove/add monitor to policy-map |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
FNF records are not generated for that monitor
Conditions:
On removing and adding the monitor back to the policy-map
Workaround:
remove the service-policy
add changes needed to the flow monitor then reattach policy
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(2)E, 15.2(2)E1, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud36113 | Title: | Ping fails between CE routers in MPLS VPN Inter-AS IPv4 BGP Label Distri |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: Ping fails between CE routers.
Conditions: This symptom is observed when you configure MPLS VPN Inter-AS IPv4
BGP Label Distribution and flaps "mpls bgp forwarding" in the interface between
ASBRs.
Workaround: Removing and adding (flapping) the static routes between ASBRs resolves the issue.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.2(2.6)S, 15.2(4)S, 15.3(1.17)S0.4 |
|
Known Fixed Releases: * | 15.1(1)IC66.14, 15.1(1)ICA4.16, 15.1(1)ICB40.1, 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(1.1)PSR, 15.2(4)S2.5 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud86082 | Title: | ASR1K XE310: LISP CPUHUG is seen when doing lisp config replace |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: Abnormal CPUHUG is observed when doing "config replace".
Conditions: This symptom is observed with "config replace" in a LISP scaling
configuration.
Workaround: There is no workaround.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)IC273.13, 15.2(1.2.3)PI22, 15.2(4)XB11, 15.3(1)S0.6, 15.3(1)S1, 15.3(1)S1e, 15.3(1)S2, 15.3(1)T0.1, 15.3(1)T1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue05681 | Title: | ISSU XE381->MCP_DEV:Traceback @ fsm_execute_internal after loadversion |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Traceback is observed at fsm_execute_internal after issu load version.
Conditions: This symptom is observed while doing issu loadversion.
Workaround: There is no workaround.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.1(1)SY0.1, 15.1(1)SY1, 15.1(1)SY1.32, 15.1(1)SY1.55, 15.1(1)SY1.57, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(1)SY5, 15.1(1)SY6 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue31774 | Title: | Ethernet cfm CC doesn't work on ASR1002 03.08.00.S |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: Ethernet cfm cc does not work on Cisco IOS Release 03.08.00.S on the Cisco ASR 1002 Router.
Conditions: This symptom is observed when in the setup Cisco ASR 1002----L2switch----Cisco ASR 1002, you change the vlan on L2 switch, Cisco ASR 1002 related interface will not change to down. This symptom is not observed when running Cisco IOS Release 03.07.02.S.
Workaround: There is no workaround.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S |
|
Known Fixed Releases: * | 15.2(1.2.42)PI22, 15.3(1)S1.2, 15.3(1)S2, 15.3(1)T1.1, 15.3(1)T2, 15.3(1)T3, 15.3(1)T4, 15.3(2)S0.2, 15.3(2)S1, 15.3(2)S1b |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue95542 | Title: | linux_iosd Crash after CFM Configured |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * |
Symptom:
A crash was observed after configuring ethernet CFM on the router. The crash occurred in the
linux_iosd process.
Conditions:
The crash was seen on the Cisco ISR4400 and the Cisco CSR1000v.
Workaround:
Do not configure CFM.
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: * | 15.3(2.14)S, 15.3(3)S |
|
Known Fixed Releases: * | 15.2(1.2.42)PI22, 15.3(1)S1.5, 15.3(1)S2, 15.3(1)T1.1, 15.3(1)T2, 15.3(1)T3, 15.3(1)T4, 15.3(2)S0.3, 15.3(2)S1, 15.3(2)S1b |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue69214 | Title: | Memory leak @__be_fmd_get_if_fn_buffer on removing MLPPP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Memory leaks are seen in the metadata after removing a virtual interface.
Conditions: This symptom occurs after removing a virtual interface, if metadata is enabled.
Workaround: There is no workaround.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S |
|
Known Fixed Releases: * | 15.1(1)IB273.63, 15.1(1)SY1.21, 15.1(1)SY1.32, 15.1(1)SY1.55, 15.1(1)SY1.57, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(2)SY, 15.1(2)SY1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue14596 | Title: | mib cfmFlowMetadataAppName truncated |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The mib cfmFlowMetadataAppName value in the SNMP query should not include vendor information.
Conditions: This symptom occurs when the SNMP query is run for mib cfmFlowMetadataAppName and the following value is obtained:
cfmFlowMetadataAppName.2.1 = cisco telepresence-control
The vendor information "cisco" should be removed.
The expected mib value should be as following:
cfmFlowMetadataAppName.2.1 = telepresence-control
Workaround: There is no workaround.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S0.7, 15.3(1)S1.6, 15.3(1.17)S0.13, 15.3(1.17)S0.4, 15.3(2)S0.13, 15.3(2)S0.5, 15.3(3)S, 15.4(0.5)S |
|
Known Fixed Releases: * | 15.1(1)XO2, 15.2(2)E, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(2.12)S, 15.3(2.15.1)XEB, 15.3(2.21)PI23a, 15.3(3)M0.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug37196 | Title: | BFD: Crash observed @__be_bfd_interface_command during basic test |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Execution of "no bfd interval" under an interface results in a router crash.
Conditions: Basic usage of the BFD template on an interface followed by the execution of the "no bfd interval" results in a router crash.
Workaround: There is no workaround.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 12.2(33)SCI, 15.1(1)IC66.49, 15.1(1)ICB29.21, 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(1.1)EY, 15.2(2)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug64957 | Title: | ASR1K: Unable to alter class map after configuring 1k class maps |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: An error occurs on changing the grandchild class rate.
Conditions: This symptom occurs when 1x1000x8 policy maps are configured.
Workaround: There is no workaround.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.1(1)XO0.1, 15.3(1)S, 15.3(2)S, 15.3(3)S |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)IC273.5, 15.2(1.2.43)PI22, 15.2(2)E, 15.2(2)E1, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2, 15.2(2)SNI, 15.2(2b)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue55739 | Title: | MC-BR flap due to learn update while writing to DB |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptoms: PfR MC/BR session may be flapped, if PfR learn is configured with
scale configuration.
Conditions: This symptom may be observed, if PfR traffic-classes are learned by
PfR global learn configuration.
Workaround: Disable PfR global learn by configuring
traffic-class filter access-list pointing to the
deny ip ip any ACL, and configure PfR learn "list".
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S2 |
|
Known Fixed Releases: * | 12.2(33)SXI10, 12.2(33)SXI11, 12.2(33)SXI12, 12.2(33)SXI13, 12.2(33)SXI14, 12.2(33)SXI4, 12.2(33)SXI6, 12.2(33)SXI8a, 12.2(33)SXJ, 12.2(33)SXJ2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy11369 | Title: | Polaris 16.2 : fman_fp crash occurs while configuring mac 128k limit |
|
Status: | Other |
|
Severity: | 2 Severe |
Description: * | Symptom:
fman_fp crash occurs
Conditions:
while configuring mac 128k limit
Workaround:
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj50396 | Title: | Flow Exporter status goes inactive after RP swithover |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The flow exporter status becomes inactive.
Conditions: This symptom occurs after an RP switchover while checking flow monitor information.
Workaround: There is no workaround.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S, 15.4(1)S, 15.4(2)S |
|
Known Fixed Releases: * | 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2, 15.1(2)SY3, 15.1(2)SY4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj52396 | Title: | XE3.11 : PW xconnect goes down on VPLS_OptB |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: In a VPLS Inter-Autonomous System Option B configuration, the virtual
circuits between the Autonomous System Border Router (ASBR) and the PE may
fail to come up.
Conditions: This symptom is observed while initially establishing VCs after the ASBR has reloaded.
Workaround: The clear xconnect exec command can be used to clear
the VCs that are down.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: * | 15.2(4)S4.15, 15.2(4)S5, 15.2(4)S6, 15.3(3)M2.3, 15.3(3)M3, 15.3(3)M4, 15.3(3)S1.10, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S2t |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh62529 | Title: | ASR router crashes for media forking HA feature |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR router crashes for media forking HA feature.
Conditions:
This symptom is observed when media forking feature crashes in B2BHA standby router.
Workaround:
There is no workaround.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(2.19)S0.12, 15.3(2.19)S0.8, 15.3(3)S, 15.4(0.15)S |
|
Known Fixed Releases: * | 15.3(3)M0.2, 15.3(3)M1, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S0.3, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2, 15.3(3)S2a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui32105 | Title: | Standby RP crashes continously on ASR due to corruption on XDR buffers |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: In rare occasions the standby RP on a dual RP system may crash after performing a switchover.
Conditions: This symptom occurs when an invalid message is sent from the RP to the RRP.
Workaround: There is no workaround.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S1 |
|
Known Fixed Releases: * | 15.1(1)IC66.14, 15.1(1)ICB40.1, 15.2(2)E, 15.2(2)E1, 15.2(2a)E1, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(3)S0.6 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh39624 | Title: | PMIPV6 crash when no ipv6 mobile pmipv6-lma lma1 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: PMIPV6 crashes when "no ipv6 mobile pmipv6-lma lma1" is configured.
Conditions: This symptom occurs when "no ipv6 mobile pmipv6-lma lma1" is configured.
Workaround: There is no workaround.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.4(1)S, 15.4(1)S0a, 15.4(1)S0b, 15.4(1)S0c, 15.4(1)S1, 15.4(1)S2, 15.4(1)S3, 15.4(1.3)T, 15.4(1.4)T, 15.4(1.5)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui04262 | Title: | Stby RP reload: %QOS-3-INDEX_DELETE: class-group unable to remove index |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | An error syslog is seen on ASR1K BRAS running XE352.P3 Standby-RP, showing QOS service-policy installation failures:
1. Jun 13 14:43:55.323 CEST: %QOS-6-POLICY_INST_FAILED: Service policy installation failed
2. Jun 13 14:47:10.725 CEST: %QOS-3-INDEX_DELETE: class-group unable to remove index 00B6AA60
3. Jun 13 14:47:10.726 CEST: %QOS-3-UNASSIGNED: A CLASS_REMOVE event resulted in an (un)assigned index for class-group target-input-parent$class-default$IPBSA>ci=3#qu=3#qd=4#co=4#pu=police#ru=200K#pd=police#rd=300K<_IN$class-default
4. Jun 13 14:47:10.727 CEST: %QOS-6-RELOAD: Index removal failed, reloading self
Symptom: An error syslog is seen on ASR1K BRAS running XE352.P3 Standby-RP, showing QOS service-policy installation failures:
1. Jun 13 14:43:55.323 CEST: %QOS-6-POLICY_INST_FAILED: Service policy installation failed
2. Jun 13 14:47:10.725 CEST: %QOS-3-INDEX_DELETE: class-group unable to remove index 00B6AA60
3. Jun 13 14:47:10.726 CEST: %QOS-3-UNASSIGNED: A CLASS_REMOVE event resulted in an (un)assigned index for class-group target-input-parent$class-default$IPBSA>ci=3#qu=3#qd=4#co=4#pu=police#ru=200K#pd=police#rd=300K<_IN$class-default
4. Jun 13 14:47:10.727 CEST: %QOS-6-RELOAD: Index removal failed, reloading self
Conditions: This symptom is observed when on ASR1K BRAS, running Cisco IOS Release XE352.P3, Version 15.2(1)S2, CUST-SPECIAL:V152_1_S2_CSCUA32331_4
When churning PPPoE sessions with 2 unique ISG/Shell map services per session, and after a manual RP Failover is done, after a while the error will be seen.
Workaround: There is no workaround.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S, 15.2(2)S |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.1(1)ICB29.1, 15.2(1)IC273.5, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(3)JA, 15.3(3)JA1m, 15.3(3)JAA, 15.3(3)JAB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj85993 | Title: | SBC RP2 crash when a preserved call is hold resume after a HA fail over |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A Cisco ASR1006 (RP2) running Cisco IOS-XE Version: 03.07.04.S (asr1000rp2-adventerprisek9.03.07.04.S.152-4.S4) will crash after a recent High Availability (HA) fail-over event.
Conditions:
High Availability (HA) fail-over is implemented with RP2 on the Cisco ASR. When a fail-over is initiated to the active RP2 module (for example by removing the active RP2 module), the ASR fails over fine, but once a hold resume is initiated on an existing call (that was preserved from the fail-over), the ASR reboots.
Workaround:
The crash is not observed on IOS-XE version 03.07.03.S
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S4.5 |
|
Known Fixed Releases: * | 15.2(4)S4.8, 15.2(4)S5, 15.2(4)S6, 15.3(3)S2.9, 15.3(3)S3, 15.3(3)S4, 15.4(1)S0.1, 15.4(1)S0.2, 15.4(1)S0e, 15.4(1)S1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj44237 | Title: | GETVPN Suite-B OVERLAPPING IV RANGES: ACL changed back to initial ACL |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: With Suite-B configured, that is, esp-gcm / esp-gmac transform on a GETVPN Key Server (KS), Group Members (GM) will see the "*** SERIOUS ERROR: OVERLAPPING IV RANGES DETECTED ***" un-gated error message on the console when the following is done:
(1) GM registers to KS and downloads ACL1
(2) KS configures ACL2 which is a subset of ACL1
(3) KS issues "crypto gdoi ks rekey" & GM receives rekey successfully, downloading ACL2
(4) KS configures the original ACL1 again
(5) KS issues "crypto gdoi ks rekey" & GM the error message is seen
After this, the GM begins to re-register.
Conditions: Suite-B is configured, that is, esp-gcm / esp-gmac transform on a GETVPN Key Server (KS) with GM's registered
The KS policy ACL is changed from ACL1 to ACL2 (where ACL2 is a subset of ACL1) & a rekey is sent from the KS using "crypto gdoi ks rekey"
The KS policy ACL is reset back from ACL2 to ACL1 & a rekey is sent from the KS using "crypto gdoi ks rekey"
Workaround: If a Key Server (KS) policy ACL1 must be changed to ACL2 & then changed back to the original ACL1 while Group Members (GM) have already registered and downloaded GETVPN Suite-B policy, that is, esp-gcm / esp-gmac transform, do one of the following:
1.) Wait for the TEK's of the original ACL1 to expire after the first rekey before changing back to the original ACL1
2.) Issue "crypto gdoi ks rekey replace-now" instead of "crypto gdoi ks rekey" after changing back to the original ACL1.
3.) If the above two workarounds do not work, issue "clear crypto gdoi" on the GM's with the error or "clear crypto gdoi ks members now" on the KS to reset the entire group.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(3)M, 15.3(3)S, 15.4(0.26)T0.1, 15.4(1)S, 15.4(1.4)T |
|
Known Fixed Releases: * | 15.1(2)IC66.3, 15.2(1)IC273.70, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E, 15.2(2)E1, 15.2(2.2.70)ST, 15.2(2a)E1, 15.2(2b)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj39478 | Title: | ASR1K CUBE crash due to memory corruption on voip rtp port array |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR100x running IOS XE version 15.3(1)S configured as a CUBE Ent has been seen to have segmentation fault in certain rare circumstances. CUBE(Ent) on ASR has gone through really hard performance testing and this bug was not seen.
Exception to IOS:
Frame pointer 0x7F98F04FB980, PC = 0x3A534E6
IOS Thread backtrace:
UNIX-EXT-SIGNAL: Segmentation fault(11), Process = IOSXE-RP Punt Service Process
-Traceback= 1#9821b08208133f5124c039ddebb8173b :400000+36534E6 :400000+203F6E8 :400000+1A9972F :400000+1A2C3B4 :400000+1A52F50 :400000+6487473 :400000+6486359
Conditions:
Trigger of the issue is unknown.
Workaround:
Since the crash is reported when port 26132 was used, by not using this port (udp port 26132 which was corresponding to the index 4874 in port_array). crash can be avoided.
This can be done by changing the port range to something like 26134 to 32767 (currently it is 16384 to 32767) but this will reduce the number of CUBE calls from 4000 to around 1600 calls.
In Cisco IOS XE3.10.1, this port range is 8000 to 48199 by default, so we will have a bigger port range to start with, and in this case the port corresponding to index 4874 is 17748, so we will have to change the port range to 18000 ? 48199 using the configuration. In addition Cisco IOS XE3.10.1 also allows configuration where the packets can be dropped in DP if no session exists in DP. This will not cause any one way audio as the IOSd is not really meant to process the media on ASR, and if there are any media issues those need to be addressed differently.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S |
|
Known Fixed Releases: * | 15.3(3)M1.2, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S0.13, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup91567 | Title: | ASR1001-X boot-loops with CMCC crash and XGM MAC10 block errors |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
An ASR1001-X router may enter a "boot-loop" when its powered ON.
with this defect the CMCC process will crash during system initialization i.e during router bootup.
This might repeat on each subsequent router bootup.
Messages similar to the following may be seen:
*Aug 3 06:13:42.758: %CMCC-0-PLIM_HALT: SIP0: cmcc: A PLIM driver has critical error Ysn-Mac10 - xgm: crc, 0, param 29 param 0
*Aug 3 06:13:42.997: %PMAN-3-PROCHOLDDOWN: SIP0: pman.sh: The process cmcc has been helddown (rc 134)
*Aug 3 06:13:43.021: %PMAN-0-PROCFAILCRIT: SIP0: pvp.sh: A critical process cmcc has failed (rc 134)
Conditions:
This is a corner case. And there is no configuration- or traffic-specific trigger to hit this issue.
This problem might occur in any of the power on of ASR1001-X.
This issue occurs when an error interrupt is recorded by the main forwarding ASIC and due to this defect the interrupts are not cleared on a subsequent reboot.
This problem can happen on any kind of reloads crash reload/software reload/power cycle.
if once it occurs it will keep repeating
Workaround:
Power the router down (switch off power supply, or unplug) for a short time (30 seconds to a minute) and then power it back on. This will clear the spurious interrupt. and subsequent router bootup will succeed,
Further Problem Description:
The interrupts known to trigger this are those which are usually considered transient / "soft" errors: parity errors, internal CRC errors and the like. In software, some of these interrupts are not correctly cleared during the boot process / soft reboot, and so will continue to assert themselves on each subsequent boot. This causes the CMCC process to crash and reload the system repeatedly. Powering down the system fully clears the interrupt(s) and allows the system to boot.
This software fix clears all relevant interrupts correctly on boot, avoiding the issue.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(1)S3, 15.5(2)S2, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.188), 16.2(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv79776 | Title: | Router with Pfr feature crashed at cpp_free_exmem |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A Cisco router may crash and generated a RP core file
Conditions:
Issue is now seen on a ISR4331 with Pfr feature running 15.5(3)S code
Workaround:
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.1(0.1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo95313 | Title: | Duplicate Lcookies in every Access-Request |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Duplicate cookies are observed in every access request.
Conditions: This symptom occurs when multilogon or logoff is performed on the same session.
Workaround: Tear down the session during the logoff event. Do not configure any delay on the account logoff event.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S2.9 |
|
Known Fixed Releases: * | 15.0(1)EZ4, 15.0(1.77)ZSR, 15.0(13.95)EZD, 15.0(14.1)TSR, 15.0(14.18)TTT, 15.0(14.57)EZD, 15.0(2.29)ZSR, 15.2(1)IC273.113, 15.2(2)DB101.101, 15.2(2)DB101.112 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur72779 | Title: | XE314 : B2B NAT : Stale NAT translations observed on Active rtr |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Stale NAT translations may be observed on the router even after the traffic stops.
Conditions:
Translations count as seen in 'show ip nat translations total' is non-zero value.
Workaround:
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.6(1)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun00236 | Title: | OTV MST TCs not sent over port-channel after AED election |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: MST TCNs are not sent over a port-channel access interface after an AED change.
Conditions: This symptom occurs with dual-home AEDs at a site with port-channels used as access links. The join or overlay interface goes down to cause an AED change.
Workaround: Use an EEM script to bounce access interfaces (port-channels). This should cause the access switches to flush their MAC tables and redirect traffic to the new AED.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S1 |
|
Known Fixed Releases: * | 15.3(3)S2.6, 15.3(3)S3, 15.3(3)S4, 15.4(1)S2, 15.4(1)S3, 15.4(2)S0.4, 15.4(2)S1, 15.4(2)S2, 15.4(2.13)PI26a, 15.4(2.15)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv36911 | Title: | ASR1K active CGN ESP200 may crash when the CGN standby realoded |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In a Back-to-Back Carrier Grade NAT configuration using ASR1013 chassis and PAP+BPA configured, active CGN ESP200 crashed while the reloaded standby CGN. Active CGN started to crash when standby CGN reloaded and come back online and started to sync NAT translations.
Conditions:
This has been seen when Carrier Grade NAT (CGN) is deployed
Workaround:
none
Further Problem Description:
NA
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.185) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo72961 | Title: | ASR1K:%FMFP-3-OBJ_DWNLD_TO_CPP_FAILED: F1: fman_fp_image: Batch type |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: An error message is logged in during QoS configuration during an FPM test.
Conditions: This symptom occurs due to a policy with FPM class.
Workaround: There is no workaround.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S, 15.3(3)S, 15.4(1)S |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(1)IC273.77, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw47720 | Title: | ASR1001-X Mgmt port negotation issue with peer device |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When no shutdown ASR1001-X Mgmt port, it links up with 100M/full, which should be 1000M/full
Conditions:
Shut/no shut and interval more than about 30s
Workaround:
Shut/no shut and interval less than about 30s
Further Problem Description:
other ASR1k except ASR1001-X don't have this issue
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 16.3(0.71) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo91745 | Title: | CENT:blackhole should not dropped TC when TC learnt at the beginning |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom: The black hole should not drop TC when TC is learnt at the beginning.
Conditions: This symptom occurs when the black hole is added in the class as follows:
class http sequence 10
match application http policy custom
priority 1 one-way-delay threshold 100
path-preference SP1 fallback blackhole
The HTTP traffic is added. When the TC is learning, it is uncontrolled and hence during this time traffic will be dropped. The dropping will start at the TC learnt and end at the TC controlled. The duration will be a minimum of 30s.
Workaround: There is no workaround.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(3)M, 15.4(3)S, 15.5(1)S |
|
Known Fixed Releases: * | 15.4(2.17)S0.9, 15.4(2.20)M0.1, 15.4(3)S, 15.4(3)SN1a, 15.5(0.11)S, 15.5(0.6)T, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo64915 | Title: | PPP half bridge functionality support in ASR1k |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PPP Half Bridge functionality was not Supported on ASR1k earlier
Conditions:
LATEST code base didnt support PPP Half Bridge Functionality on HW switched platforms like ASR1k
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 15.4(3)S0.2, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a, 15.5(0.16)T, 15.5(0.16.1)CG, 15.5(0.20)PI27a, 15.5(0.7)S, 15.5(0.8)S, 15.5(1.2.1a)GB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux10321 | Title: | ASR1000 CLI hangs on executing the "show platform hardware qfp xxx" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A process in the FP package can deadlock, leading to various symptoms. The most common is an indefinite pause when executing certain CLI commands that start with "show platform hardware qfp" . The "show debug" command will also show this problem. The deadlocked process is predominantly cpp_cp_svr, although it could happen to other processes as well. If cpp_cp_svr is deadlocked, the command "monitor platform sofware process fp active" will persistently show "0.0" in the "%CPU" column for that process.
While the data plane is not directly affected by this problem, any functionality which requires an interaction between the data plane and the control plane may not work. For example, firewall sessions cannot be established, statistics cannot be displayed, forwarding tables cannot be updated, etc.
Conditions:
This only affects ASR1002-X, ASR1001-X, ESP-100, and ESP-200. It requires a very rare combination of conditions that are transient and not visible using show commands.
Note that while a few show commands can trigger the deadlock, there are other events which can trigger the deadlock as well, but are not connected with any operator action. In addition, the show commands which pause indefinitely once the deadlock has happened, are not all possible triggers. For instance, the "show debug" command mentioned under "Symptoms" cannot trigger the deadlock, but it will pause indefinitely if issued after the deadlock has happened.
Workaround:
No workaround exists.
For ASR1002-X and ASR1001-X a reload is required. For ESP-100 and ESP-200 the ESP needs to be reloaded. Forcing a core file for the deadlocked process before a reload will make root cause analysis much simpler. This can be done using "test platform softrware process core qfp-control-process qfp active".
Further Problem Description:
A burst of IPC messages from the QFP to any process on the control processor must temporarily lead to a buffer depletion in that path. This is already a rare condition and does not persist for very long. During this time, a synchronous IPC message must be sent from that same process, which now deadlocks waiting for a reply, which is (erroneously) blocked behind the messages waiting for buffers.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S, 15.2(4)S6 |
|
Known Fixed Releases: * | 15.4(3)S5, 16.2(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq02180 | Title: | crash seen in utah router after the call starts |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Crash is seen after the call starts
Conditions:
the stcapp summary is seen for the voice port.
Workaround:
no workaround
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)M0.3, 15.4(3)M1, 15.4(3)S0.5, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a, 15.5(0.17)T, 15.5(0.18)S0.3, 15.5(0.20)PI27a, 15.5(0.20)PI27b |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup80613 | Title: | iosd crash after issuing 'show lisp all' with clean running-config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Router crashes when issuing "show lisp all" without and LISP configuration.
Conditions:
Issuing "show lisp all" without and LISP configuration.
Workaround:
Configuring "router lisp" will prevent the router from crashing when issuing the show command.
Additional LISP configuration to enable ITR/ETR/MS/MR functionality is not required.
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(2.17)T, 15.4(3)M, 15.4(3)S, 15.5(0.10)T, 15.5(1)S |
|
Known Fixed Releases: * | 15.2(1)IC273.145, 15.4(2.20)M0.12, 15.4(3)M, 15.4(3)M1, 15.4(3)S0.3, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a, 15.5(0.12)T, 15.5(0.15)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo44562 | Title: | ASR1K crash @policymap_inform_child_policymaps |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The Cisco ASR 1000 Series Router crashes.
Conditions: This symptom occurs with duty cycle testing with a lot of negative events.
Workaround: There is no workaround.
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(3.3)S3 |
|
Known Fixed Releases: * | 15.2(1)IC273.77, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2.2.32)EA, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(3)M4, 15.3(3)S2.14 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut17865 | Title: | ASR1K:13RU IOSd crash @PnP Agent Discovery after router reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
IOSd crash occurs at PnP Agent Discovery
Conditions:
after doing write erase and reload
Workaround:
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.2(1)IC273.310, 15.2(1)SY0.4, 15.2(1)SY1, 15.2(2)E2, 15.2(2)ID101.131, 15.2(2)IE101.142, 15.2(3)E1, 15.2(3)E2, 15.2(4.0)ST, 15.2(4.0.64a)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus86120 | Title: | RP1: CLI run slow in new XE313/XE314 image |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A Cisco router that is rebooted may display the following logs repeatedly:
%PNP-6-HTTP_CONNECTING: PnP Discovery trying to connect to PnP server https://devicehelper.cisco.com/pnp/HELLO
%SYS-3-HARIKARI: Process Wait on Autoinstall top-level routine exited
Conditions:
This happens at bootup under some conditions incorrectly.
Workaround:
There is no workaround for the problem.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.2(1)IC273.283, 15.4(3)S, 15.5(2)S |
|
Known Fixed Releases: * | 15.2(1)IC273.310, 15.2(1)SY0.4, 15.2(1)SY1, 15.2(2)E2, 15.2(2)ID101.131, 15.2(2)IE101.142, 15.2(3)E1, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut47195 | Title: | MCP_DEV:Unable to activate capture synack and mss value not seen |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
While testing "xe311_ipv6_tcp_mss" feature with MCP_DEV image in Kingpin platform,Unable to activate capture synack and MSS value is not seen.
Conditions:
Issue is seen in Kingpin platform
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(2.12)T, 15.5(2.14.1)PIH28, 15.5(2.16.5)PIH28, 15.5(2.18)S, 15.5(3)S, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2, 16.1(0.222) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut68925 | Title: | Crash seen in QOS when policy-map without child or turbo svc is used |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Issue happens when there is no child policy attached to the parent policy and the get_bw api is called.
Conditions:
same as symptoms
Workaround:
no work around
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(2.19)T, 15.5(2.21)S0.12, 15.5(2.21)S0.4, 15.5(2.22)S, 15.5(3)S, 15.5(3)S0a, 15.5(3)S1, 15.5(3)S1a, 15.5(3)SN, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu89720 | Title: | crash found when remove ipv6 media pool |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
crash found when remove ipv6 media pool
Conditions:
1. sbc config with ipv6 media-pool
2. remove ipv6 media-pool in sbc
3. crash found
Workaround:
no problem on asr1006 rp1+ esp10
also found on ASR1001
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.4(3)S3.7, 15.4(3)S4, 15.6(0.7)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur45249 | Title: | linktrace fail with two remote mep sessions |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
linktrace fail with two remote mep sessions
Conditions:
pe1---pe2---ce2
|
ce3
pe1 and pe2 establish up mep???pe1 and ce2 establish down mep
pe1 traceroute mep ce2 or pe2 will fail
if only exist one mep??? linktrace is successfull
Workaround:
Further Problem Description:
none
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.5(1.14)S, 15.5(2)S |
|
Known Fixed Releases: * | 15.5(1.12)T, 15.5(1.16)S, 15.5(2)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv21984 | Title: | Fair-queue queue-limit force adjust after change queue-limit. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Fair-queue queue-limit force adjust after change queue-limit.
Conditions:
in case of change queue-limit, the fair-queue queue-limit adjust automatically in spite of manually configure the fair-queue queue-limit.
2nd, apply policy-map which have bandwidth ramaining ratio at last line.
policy-map test10
class class-default
fair-queue
fair-queue queue-limit 64
bandwidth remaining ratio 1
The fair-queue queue-limit become 16.
Workaround:
Reconfigure the fair-queue queue-limit after change queue-limit.
Further Problem Description:
none
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.3(3)S6.4, 15.6(0.13)S, 15.6(0.17)PI30e, 15.6(0.19)T, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw91822 | Title: | vISG not sending COA Response |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Client are not able to browse internet
Conditions:
vISG version 3.16 integrating with Single Digits
Workaround:
Further Problem Description:
None
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S3.16, 16.2(0) |
|
Known Fixed Releases: * | 15.4(3)S4.7, 15.5(2)S2.1, 15.5(3)S1.2, 15.5(3)S2, 15.6(0.22)S0.8, 15.6(1.16)S, 16.2(0.272), 16.3(0.32) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw24373 | Title: | Called-station-id and NAS-ID via account profile satus query |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
sending extra attributes "called-station-id" and "NAS-ID" in accout-status-query for Webauth unauthenticated sessions
Conditions:
NA
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2, 15.6(0.22)S0.13, 15.6(1.12)S, 16.3(0.46) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv86324 | Title: | IOS-XE voice gateway may crash while disabling SCCP |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
An IOS-XE running gateway may reload unexpectedly while disabling SCCP. The output of the "show version" command may display "Critical software exception" as the reload reason.
***Output shortened for brevity
------------------ show version ------------------
Cisco IOS XE Software, Version XX.XX.XX.S - Extended Support Release
Cisco IOS Software, ASR1000 Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version XX.X(X)S, RELEASE
...
System returned to ROM by reload at --Timestamp--
System restarted at --Timestamp--
System image file is "bootflash:IOS_XE_filename.bin"
Last reload reason: Critical software exception, check bootflash:crashinfo_RP_00_00_20XXXXXX-XXXXXX-XXX
....
A core.gz and IOSd crashinfo file will be stored on the "bootflash" or "harddisk" depending on the model of the ASR.
Conditions:
The ASR must be running SCCP. Issuing the "no sccp" command will trigger the crash.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S2.1 |
|
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.8, 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.4, 15.5(3)S2, 15.6(0.17)PI30e, 15.6(0.19)S, 15.6(0.19)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc13564 | Title: | Tracebacks seen on ESP with PFR/PBR causing loss of connectivity |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
Tracebacks relating to fman_fp and cpp_cp seen on the ESP that might cause loss of local connectivity on the router
Conditions:
When using PFR/PBR on the router.
Workaround:
None so far
Further Problem Description:
This is due to low memory on the ESP. This specifically affects ESP5 and ASR1001 which have the same amount of memory. This problem would not be seen on other ESP as they have more memory. A different ESP will be required if this is confirmed.
|
|
Last Modified: | 17-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq66004 | Title: | Peer removed from mka's live peer list but macsec's Rx SC is not updated |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Number of MKA's live peers and macsec installed RX SC do not match.
Conditions:
When peer is offline, ma's live peer list is updated but macsec installed RX SC is not.
Workaround:
No work-around
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.2(5.0.91)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 15.5(1.18)S0.11, 15.5(2)S, 15.5(2)SN, 15.5(2.10)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus23097 | Title: | RX SC's Failed to install with 16 peers after reload |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Traffic may get affected in the interface where RX SC count is not matching the peer count.
Conditions:
Workaround:
Issue "clear mka sessions" to reset SC.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.2(5.0.91)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 15.5(2.22)S, 15.5(3)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo61229 | Title: | ASR1002 Crashed after "show pfr master active running" |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
after performed some pfr commands ASR 1002 crashed
"show pfr master active running" was the last command
Conditions:
use pfr show commands
Workaround:
no use the pfr show commands
Further Problem Description:
N/A
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 15.6(1)T0.1, 15.6(1.20)T, 15.6(1.22.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu37200 | Title: | SC install fails after link re-route |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
SC install fails after link re-route happens in the network
Conditions:
SC install fails after link re-route happens in the network.
Workaround:
issue no macsec/macsec to recover SC's.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.4(3)SS, 15.5(3)S |
|
Known Fixed Releases: * | 15.2(5.0.91)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 15.5(3)S0.7, 15.5(3)S1, 15.5(3)S1a, 15.6(0.17)S, 15.6(1)SN, 15.6(1.4)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu92634 | Title: | ASR1K:FP100: cpp_svr core file seen with uws_wan_xe311 profile |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
The issue crashes the CP process while attempting to applied QOS in hardware. The crash causes service outage on ASR1001-x, ASR1002-x, ESP-100 and ESP-200.
Conditions:
The issue occurs while removing and adding a child service-policy from/to parent tunnel policy. Software failed to collapse the hierarchy when the child policy is removed from the parent policy. This condition results in a bad hierarchy when the policy is re-added. The problem is exposed by an attempt to apply the child in HW before it is placed in the parent node.
The issue can occur manually or a flapping virtual interface.
See attached Failed_Log.txt.
Workaround:
There is no workaround.
The fix is committed to 3.13.5.
Note, CSCuu92634 is available in 3.13.4 but requires CSCuw49798 which is committed to 3.13.5.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: | 15.4(3)S4, 15.5(2)S2, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.187) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv05361 | Title: | cpp_cp_svr crash on AR1K |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
This issue crashes the CP process resulting in service outage. It affects asr1001-x, asr1002-x, esp-100 and esp-200.
Conditions:
The software is not clearing one of the processing flags causing the CP process to crash. The issue only happens when QoS is applied to virtual interface resulting in a logical aggregation node to aggregate the virtual interface with QoS. A virtual interface includes tunnel, session, etc.
The issue requires a QOS policy, flat or hierarchical, on a virtual interface.
Workaround:
There is no working around.
This fix is available in 3.13.4.
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: | 15.4(3)S4, 15.5(2)S2, 15.5(3)S, 16.2(0.170) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux42411 | Title: | ASR1001-X Frame Relay with Fortitude NIM fails due to LMI packet padding |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Serial interfaces with Frame Relay or HDLC encapsulation remain down. Frame Relay LMI timeouts.
Conditions:
NIM-1CE1T1-PRI or NIM-2MFT-T1/E1 in ASR1001-X chassis.
Workaround:
None.
Further Problem Description:
Customers can use SPA-8XCHT1/E1-V2 as an alternative on ASR1001-X.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)SS |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.2(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux57066 | Title: | ASR1K : Lawful Intercept not working as expected for IPv6 traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Lawful Intercept feature not working as expected
Conditions:
Ipv6 traffic going towards the subscriber is not intercepted
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S3.1 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.2(0.260) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux07224 | Title: | ASR1K crash with OTV due to L2BD FIB entry change |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR1K may crash due to a race condition causing L2BD FIB entry modification.
Conditions:
OTV is configured.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S2.1, 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.238), 16.3(0.28) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux44780 | Title: | ASR1K/ISR4K crashes after removing tunnel interface |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
1) Removing a DMVPN tunnel interface with shared tunnel protection from the configuration using the 'no interface tunnel X' command, can cause an ASR1K (or ISR4K) platform to crash
2) Shutting down one mGRE tunnel interface impacts traffic to another tunnel interface sharing the same source
Conditions:
Multiple mGRE tunnels using shared tunnel protection (IPSec)
Workaround:
For symptom 2#, the workaround is:
Clear crypto sessions to the peer(s) or shut/noshut the impacted tunnel
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(1)S, 15.5(2)S, 16.2(0) |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.216) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66787 | Title: | Clear ip nat translation vrf X impacts vrf Y |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The command "clear ip nat translation vrf X *" causes a system wide disruption to NAT. Traffic that is currently subjected to NAT will briefly stop getting NAT applied. Depending on the routing/ACL design, these untranslated packets may be dropped.
Conditions:
The command "clear ip nat translation vrf X *" is used while traffic is subject to NAT configured in a different vrf.
Workaround:
None currently identified
Further Problem Description:
It is not necessary to have any NAT configured in the VRF that the clear ip nat translation command is run against, although it is expected as otherwise there is no need to run the clear command.
When reproduced on an ASR 1000, with a single NAT statement, the disruption lasted for ~150ms. It is unknown how increasing the NAT scale will impact the length of the disruption.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)SS |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.253), 16.3(0.46) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux35719 | Title: | ASR1K QFP crash with SSLVPN |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
An ASR1000 series router may exhibit an unexpected crash in the QFP ucode (cpp-mcplo-ucode) process.
On a modular chassis, this will result in a reload of the active ESP module and a switchover to the standby (if one is present). On an integrated chassis (ASR1001[-X], ASR1002-X) the entire chassis will reload.
Conditions:
This has been observed with the SSLVPN feature configured while running IOS-XE release 03.16.01a.S. The crash appears to occur due to a race condition between threads while processing TCP Selective ACK (SACK) messages from an SSL VPN client.
Further, exact conditions are not currently known.
Workaround:
Not known at this time.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S, 15.5(3)S0.18 |
|
Known Fixed Releases: * | 15.5(3)S2, 16.3(0.6) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu75584 | Title: | cpp ucode crash related to Nat config changes |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
cpp-ucode crash followed by fman-Fp crash
Conditions:
possible NAT configuration changes
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S5.9 |
|
Known Fixed Releases: * | 15.4(3)S4, 15.5(3)S2, 15.6(1)S, 16.2(0.170) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66752 | Title: | "SSM connection manager" high CPU if VAIs under scale have QOS applied |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Constantly High CPU (> 15%) usage by the "SSM connection manager"
Conditions:
ASR1k (rp2) BRAS terminating high (~28,800) number of PPPoE sessions with QOS policies applied to all VAIs
and continuous control-plane churn (session establishment & teardown.
Workaround:
Reduce the scale (frequency of session churn) or or avoid applying QOS policies to all the individual VAIs.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.3(3)S2, 15.3(3)S2a, 15.3(3)S3, 15.3(3)S4, 15.3(3)S5, 15.3(3)S6, 15.4(1)S1, 15.4(1)S2, 15.4(1)S3, 15.4(1)S4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux02656 | Title: | ASR1K: Crash related to collecting NetFlow data for IPv6 flows |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A crash is observed on an ASR1K running 15.5(2)S2.
Conditions:
The crash is known to occur when Flexible NetFlow is configured and IPv6 traffic flows are being processed by the NetFlow engine. The crash appears to be related to the NetFlow processing of IPv6 fragments.
Workaround:
Disable NetFlow collection.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.2(0.193) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus43594 | Title: | rp crash when cleanup vpls scale configuration |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | RP crashed when doing config replace with a cleanup config.
Symptom:
Conditions:
Scale vpls bgp signaling config.
Workaround:
No.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.3(3)S5.1, 15.3(3)S6, 15.4(3)M2.1, 15.4(3)M3, 15.4(3)M3.1, 15.4(3)S2.1, 15.4(3)S3, 15.5(1)S0.10, 15.5(1)S1, 15.5(1)SN1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu85691 | Title: | Under load crash is seen at REFER based scenarios |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Under load crash is seen at REFER based scenarios
Conditions:
Load enclosed configs
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(2.21)S0.6 |
|
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.12, 15.4(3)S5, 15.5(2)S1.7, 15.5(2)S2, 15.5(2)T2, 15.5(3)M0.2, 15.5(3)M1, 15.5(3)S0.7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux29703 | Title: | ASR1000-2T+20X1GE fails to boot on router reload with SPA-3-NULL_BAY_PTR |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Ethernet card ASR1000-2T+20X1GE fails to come up after router reload.
Conditions:
Ethernet card ASR1000-2T+20X1GE fails to come up after router reload.
The following logs start coming on the RP console --->
*Jan 13 12:18:44.246: %IOSXE_SPA-3-NULL_BAY_PTR:
-Traceback= 1#6ab727c0503e68dab277bdb3b2fe4bb8 :7F7ED59A7000+DA24C9F spa_ipc_shim:7F7EB54CC000+360B4 spa_ipc_shim:7F7EB54CC000+360B4
*Jan 13 12:18:44.247: %IOSXE_SPA-3-NULL_BAY_PTR:
-Traceback= 1#6ab727c0503e68dab277bdb3b2fe4bb8 :7F7ED59A7000+DA24C9F spa_ipc_shim:7F7EB54CC000+360B4 spa_ipc_shim:7F7EB54CC000+360B4
*Jan 13 12:18:44.248: %IOSXE_SPA-3-NULL_BAY_PTR:
-Traceback= 1#6ab727c0503e68dab277bdb3b2fe4bb8 :7F7ED59A7000+DA24C9F spa_ipc_shim:7F7EB54CC000+360B4 spa_ipc_shim:7F7EB54CC000+360B4
Even soft OIR of the card does not help in booting of ASR1000-2T+20X1GE.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S0.9, 15.4(3)S3.1, 15.5(3)S1.1, 15.6(1)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu75176 | Title: | Multiple AN values for Rx SA observed in show macsec status |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:Multiple AN values observed in show macsec status during CAK REKEY with P2MP scenario when the peers of the same Secure Connectivity Association are hosted with same keychain on a box.
Conditions:The issue is seen when the peers of the same Secure Connectivity Association are hosted with same keychain on a box and a CAK-rekey is triggered by adding a new valid key.
Workaround:Hosting the P2MP peers of a CA in different boxes.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.2(5.0.91)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 15.5(3)S1.4, 15.5(3)S2, 15.6(0.22)S0.10, 15.6(1.17)S0.4, 15.6(1.17)SP, 16.2(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux19336 | Title: | XE316:cpp_cp_svr core files seen while removing mulitlink interface |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
This is a merge problem that happens when multilink interfaces are removed. The issue crashed the CP process resulting in service outage.
Conditions:
A crash would occur due to accessing invalidated memory while collapsing a node that has shrunk to below 4001 entries. The issue could also occur due to removing QOS configuration that required a hierarchy layer node to be inserted.
Workaround:
There is no workaround other than upgrading to an image with the fix.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.6(2)S |
|
Known Fixed Releases: * | 15.5(3)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux00303 | Title: | Router crash after stopping EPC |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Router configured for EPC may crash after executing the command "monitor capture < > stop".
Conditions:
EPC session is configured using ACL filter. The crash occurs when the capture is stopped.
Workaround:
Not known
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.2(0.261) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux33568 | Title: | ESP crash while reconfiguring FR interface to MFR bundle |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ESP40 crash with ESP core file only generated, no CPP core file on hard disk
Conditions:
reconfiguration of FR interface into MFR bundle with applied QoS
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.257), 16.3(0.52) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux11291 | Title: | OTV adjacency does not come-up with VRF |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
OTV adjacency does not come-up with VRF
Conditions:
join-interface and lan interfaces configured in vrf
Workaround:
No Workaround
Further Problem Description:
NA
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.4(3)S4.5, 15.4(3)S5, 15.5(1)S2.25, 15.5(1)S3, 15.5(2)S2.1, 15.5(3)S1.1, 15.5(3)S2, 15.6(0.22)S0.12 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux43951 | Title: | Packet drops on built-in 1Gig ports of ASR1001-X |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Packet drops is seen when ASR1001-X builtin 1gig ports are connected to third party ONS
Conditions:
This is seen with the built-in 1GIG ports on an ASR1001-X
Workaround:
Adding a switch in between ASR1001-X and the connected device will prevent the issue.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S4.8, 15.4(3)S5, 15.5(3)S1.9, 15.5(3)S2, 15.6(0.22)S0.13, 16.3(0.46) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux55692 | Title: | TCAM Errors in NL11k TCAM of Fixed Ethernet Linecards |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Intermittent packets loss on Fixed Ethernet Linecards[ASR1000-6TGE/ASR1000-2T+20X1GE]
Conditions:
This intermittent packet loss is due to TCAM Mismatch error counters. TCAM mismatch counters can be seen using "test hw-module subslot 0 np4c stat 1" CLI under SPA console of the linecard.
Workaround:
Reload of the linecard using "hw-module slot reload"
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.4(3)S4.10, 15.4(3)S5, 15.5(2)S2.11, 15.5(3)S1.4, 15.5(3)S2, 15.6(0.22)S0.13, 16.2(0.273), 16.3(0.73) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv93130 | Title: | Cisco IOS-XE 3S platforms Series Root Shell License Bypass Vulnerability |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A vulnerability in the way software packages are loaded in the Cisco IOS-XE Operating System for the Cisco IOS-XE 3S platforms could allow an authenticated, local attacker to gain restricted ''root'' shell access.
The vulnerability is due to lack of proper input validation of the file names at the CLI. An attacker could exploit this vulnerability by authenticating to the affected device and crafting specific file names for use when loading packages. An exploit could allow the authenticated attacker to bypass the license required for ''root'' shell access. If the authenticated user obtains the ''root'' shell access further compromise is possible.
Conditions:
The following Cisco products:
* Cisco Aggregation Services (ASR) Routers 1001
* Cisco Aggregation Services (ASR) Routers 1001-X
* Cisco Aggregation Services (ASR) Routers 1002-X
* Cisco Cloud Services Routers (CSR) 1000V
* Cisco Integrated Services Router (ISR) 4451
* Cisco Integrated Services Router (ISR) 4431
* Cisco Integrated Services Router (ISR) 4351
* Cisco Integrated Services Router (ISR) 4331
* Cisco Integrated Services Router (ISR) 4321
are vulnerable when running a Cisco IOS XE 3S software release if they require a license to access the restricted root shell. In order to determine if a license is required issue the show license feature | include internal_service command. If this show license command does not exist or returns empty output than this Cisco IOS XE 3S platform is not vulnerable.
The following is an example of Cisco IOS XE 3S platform that requires a license and is vulnerable:
# show license feature | include internal_service
Feature name Enforcement Evaluation Subscription Enabled RightToUse
internal_service yes no no no no
Workaround:
None.
Further Problem Description:
This vulnerability will be fixed in the following upcoming releases:
15.3(3)S7 / 3.10.7S
15.4(3)S5 / 3.13.5S
15.5(3)S2 / 3.16.2S
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 6.8/5.6:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:L/AC:L/Au:S/C:C/I:C/A:C/E:F/RL:OF/RC:C&version=2.0
CVE ID CVE-2015-6383 has been assigned to document 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: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 12.2(54)SG1, 12.2(58)EZ, 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: | CSCuq77051 | Title: | out of ids when configuring xconnect |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Attempting to create or modify a xconnect context using the command
l2vpn xconnect context command may fail with the
error message:
%IDMGR-3-INVALID_ID: bad id in id_get (Out of IDs!) (id: 0x0)
Conditions:
This symptom has been observed after entering and exiting xconnect
context sub-modes many times (over 65000) over an extended period of
time.
Workaround:
There is no workaround. Once this error occurs, the router must be
reloaded.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.3(3)S4.2, 15.3(3)S5, 15.4(3)M2.1, 15.4(3)M3, 15.4(3)M3.1, 15.4(3)S0.7, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a, 15.5(0.18)S0.6 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux43553 | Title: | XE316: ASR1001X BR ucode crashed at ipv4_input_cent_rc_process |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR10001X Head-end border router might be reloaded unexpectedly when hub MC get powered cycled unexpectely for some special condition with high scaling like 120,000 traffic-classes and 24,000 channels.
Conditions:
This case is not likely to happen and it happens in high scale with negative condition.
Workaround:
No known workaround yet.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S0.2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy19395 | Title: | ASR1006 :crashes after running the "redundancy force-switchover" command |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On the asr1006 device with dual rsp both the rsp reboots on executing the switch-over.
Conditions:
both RSP reboot on executing "redundancy force-switchover"
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.6(0.22)S0.19, 15.6(1.17)S0.13, 16.2(0.303), 16.3(0.101) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy51289 | Title: | childless delete Pending-issue on both ESP's |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
continuously increasing Pending-Issue objects leading to breakdown of PPPoE sessions
Conditions:
Workaround:
reload of both ESP's
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S3 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy50888 | Title: | ASR1k Console is getting stuck while downgrading to 3.13.3 from 3.16.2 |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
-------------------------
Hi Experts,
We have upgraded 3 ASR1002-x devises to the image : asr1002x-universalk9.BLD_V155_3_S_XE316_THROTTLE_LATEST_20160128_130127-ext.SSA.bin and then we tried to downgrade to the image :
asr1002x-universalk9.03.13.03.S.154-3.S3-ext.SPA.bin and then the console gets stuck.
!---- output omitted. Logs Attached in the Enclosure area.
We will get BT to do hard reload on this box but before that can you please let us know if any command to be issued on the box once it comes up.
Regards,
Abhay
Conditions:
While downgrading to IOS XE 3.13.3 from IOS XE 3.16.2. Steps followed are as follows :
1. Log in to the console of the device
2. Boot the ASR1002-x device with 3.16.2 CCO image
3. Change the boot variable to 3.13.3 CCO image (image is already present in bootflash)
4. Delete the 3.16.2 image from bootflash (as the device will be booted up with 3.13.3 image)
5. Issue the reload the command
6. Device gets stuck at the console
Workaround:
None found at the moment. Only way to recover the device is to Hard reload the device.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy13149 | Title: | XE310: bba_taclv6_traffic Packets are not matching with ACL |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: | Symptom:
While testing Broadband feature bba_taclv6 with XE310 image with RP2 platform, ipv6 packets are not matching in show ipv6 access-list.
Conditions:
issue is seen in XE310,XE313 and above releases in RP2 platform.
1. Reload the UUT with XE image :asr1000rp2-adventerprisek9.BLD_V153_3_S_XE310_THROTTLE_LATEST_20160125_230810-ext.bin
2. Apply the configs attached in "Configurations" enclosure.
3. Issue seen during traffic
issue can not be fixed in closed CCO releases like XE311,XE312 and XE314
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv51491 | Title: | dynamic payload type added w/o rtpmap for codec in disabled stream |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
dynamic payload type added w/o rtpmap for codec in disabled stream
Conditions:
if callee add more dynamic codec in sdp answer other than those in sdp offer
Workaround:
use lua script to remove those extra codecs
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S6 |
|
Known Fixed Releases: * | 15.4(3)S3.13, 15.4(3)S4, 15.6(0.18)S, 15.6(1)SN, 15.6(1.2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv74763 | Title: | ASR 1K - SSH Hangs on "Show Logging Count" When SBC Errors Flood Console |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR 1K may experience a hang or crash on the SSH process when running "show log count" if SBC is busy printing out a heavy amount of logs to the console.
Conditions:
SBC is printing many messages to the console at the time "show log count" is issued.
Workaround:
None known.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S4 |
|
Known Fixed Releases: * | 15.4(3)S3.13, 15.4(3)S4, 15.6(0.18)S, 15.6(1)SN, 15.6(1.2)S, 15.6(1.8)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu41857 | Title: | Incorrect GDOI registration backoff timer calculation after crash/reload |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After a crash or a reload an ASR1002-X GETVPN GM running 15.4(3)S1 will incorrectly compute the backing off retry_period to 280 sec for the third registration attempt if the first two fail. The issue is not present if the registration fails and new attempts are made after a "clear crypto gdoi".
Conditions:
Compact ASR1k, GETVPN, 15.4(3)S1, crash or reload
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S1.1 |
|
Known Fixed Releases: * | 15.6(0.10)S, 15.6(0.17)PI30a, 15.6(0.17)T, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu22481 | Title: | ISG sends only encoded name when service is applied through shell map |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Policy name is seen as "ISG-X" in accounting packets and in 'show subscriber session detail' output rather than actual policy name
Conditions:
when sending policy from radius with VSA to add classes
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S1.9 |
|
Known Fixed Releases: * | 15.5(3)M0.2, 15.5(3)M1, 15.5(3)S0.6, 15.5(3)S1, 15.5(3)S1a, 15.6(0.5)S, 15.6(0.7)T, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug45241 | Title: | C3PL:Reload during intf del at policymap_associated_to_multiple_instance |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
router crash when deleting port-channel interface
Conditions:
QoS policy is attached to the port-channel
Delete the port-channel
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 11-FEB-2016 |
|
Known Affected Releases: | 15.2(2)S2, 15.4(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux87381 | Title: | ISR4k crashes in bsess code |
|
Status: | Open |
|
Severity: * | 3 Moderate |
Description: | Symptom:
ISR4k crashes in bsess code
Conditions:
TBD
Workaround:
TBD
Further Problem Description:
|
|
Last Modified: | 13-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S1.2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv12943 | Title: | Add cli support to enable cepThroughputNotif trap |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
To enable cepThroughputNotif trap for the crypto throughput notification for exceeding the threshold and max bandwidth.
Conditions:
Trying to enable the trap using cli, cli is not available.
Workaround:
Use snmp set on cepThroughputNotifEnabled object to enable the trap.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S1.4, 15.5(3)S2, 15.6(0.16)S, 15.6(1.4)S, 16.2(0.187) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01133 | Title: | interface counter stuck on build-in interfaces in ASR1001X |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
On asr1001x, If the build-in interface is shutdown, the p/s counter of show interface does NOT reduce, indefinitely.
Conditions:
When the interface is shutdown, the p/s counters from the show interface command does not reduce.
Workaround:
none
Further Problem Description:
none
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 15.4(3)S4.7, 15.5(3)S1.4, 15.5(3)S2, 15.6(0.22)S0.10, 16.2(0.183) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCth68125 | Title: | ASR1k : Remove unsupported command 'bridge-group' from the parser |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
SNMP MIBS counter for output/input packets/bytes such as ifOutOctets,
ifHCOutOctets, ifHCOutUcastPkts & similar counters will not increment. 'SHOW
VLAN' counter will also not increase.
PS: If large number of sub-if are present under interface then, stat update
will take longer time. This might be from few secs/mins base on number of
sub-if configured & traffic on them in RLS5.
Conditions:
Issue persist when there are multiple sub-if are configured & main interface
went into tunnel/l2-transport mode. This is seen on ASR1000 series.
Workaround:
For RLS5: None
For RLS6 onwards: Configure "hw-module subslot <> ethernet vlan unlimited"
Recovery:
Perform 'Shut/No shut' on main interface, if issue still persist then reload
the SPA.
Note: Above mention both the recovery mechanism will impact traffic.
Further Problem Description
After further investigation, it was found that adding 'bridge-group' puts the
interface in Tunnel mode but that removing 'bridge-group' does not disable the
Tunnel mode (=promiscuous). As bridge-group is unsupported on ASR1k, this fix
removes that command from the parser so it can no longer be configured..
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.1(1)S |
|
Known Fixed Releases: | 15.0(0.13)S0.29, 15.0(1)S2, 15.1(0.18)S0.3, 15.1(1)MR6, 15.1(1)S, 15.1(1.3)S, 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv75254 | Title: | Errors observed when reloading SSL-GW with multi policies with same VRF |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Reloading a SSL-GW with multiple policies using interfaces from the same VRF results in 'ERROR: Two policies cannot have the same ip address, port and vrf configuration' message on the console post reload
Conditions:
SSLVPN headend has multiple SSL policies. Each of these policies use different interfaces, but the interfaces are part of the same VRF. With such a condition, if we reload the router, the router complains when booting up stating: '%ERROR%: Two policies cannot have the same ip address, port and vrf configuration'
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S1.4, 15.5(3)S2, 15.6(0.14)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug56389 | Title: | ASR1k: 24T1E1 %SPA_PLIM-3-HEARTBEAT: Error message while reloading peer |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Error message and connectivity loss from atm interface of ceop spa
Conditions:
Reloading the peer, keeping the router idle
Workaround:
None ; it recovers from the problem state by itself.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | 12.2(33)SRE10, 12.2(33.9.13)SRE, 15.3(3)S0.3, 15.3(3)S1, 15.3(3)S2, 15.4(0.16)S, 15.4(1.9.1)XEB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu19791 | Title: | SIP0/1: Bad enqueue of EED97C20 in queue EE040320 -Process= " |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Below error message is seen on the console
SIP0/0: Bad enqueue of EED97C20 in queue EE040320 -Process= "", ipl= 2, pid= 20
Conditions:
This error message could be seen on RP console, if the links are flapping on some of the EPA ports.
Workaround:
There is no workaround. This issue is fixed in XE3.16.2
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.5(3)S1.2, 15.5(3)S2, 15.6(0.15)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv77117 | Title: | Interface ip address change overrides policy config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The crypto policy state changes from its manually configured shutdown state to 'no shutdown' state automatically if we change the IP address of the interface linked to it
Conditions:
With crypto ssl policy in shutdown state, if I change the IP address to which the policy is linked to, the policy automatically changes to 'no shutdown' state
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S1.5, 15.5(3)S2, 15.6(0.15)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus35015 | Title: | PFR - 'set trigger-log-percentage' not showing in config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When 'set trigger-log-percentage 100' is configured under a pfr-map, the change does not show up in the running configuration
Conditions:
Configure "'set trigger-log-percentage" under a pfr-map, the change does not show up in the running configuration
Workaround:
None.
Further Problem Description:
Switchname#show pfr master policy
Default Policy Settings:
backoff 90 900 90
delay relative 50
holddown 90
periodic 0
probe frequency 56
number of jitter probe packets 100
mode route control
mode monitor fast
loss relative 10
jitter threshold 20
mos threshold 3.60 percent 30
unreachable relative 50
trigger-log percentage 100
oer-map MAP 4
sequence no. 8444249301581824, provider id 1, provider priority 30
host priority 0, policy priority 4, Session id 0
match oer learn list RICHMOND_VOICE_LIST
backoff 90 900 90
delay relative 50
holddown 90
periodic 0
*probe frequency 4
number of jitter probe packets 100
*mode route control
*mode monitor fast
loss relative 10
jitter threshold 20
*mos threshold 4.0 percent 20
*unreachable threshold 100000
next-hop not set
forwarding interface not set
trigger-log percentage 30
*resolve mos priority 1 variance 10
Forced Assigned Target List:
active-probe jitter 10.1.22.1 target-port 2000 dscp ef codec g711ulaw
active-probe jitter 10.1.22.2 target-port 2000 dscp ef codec g711ulaw
oer-map MAP 6
Switchname#show pfr master policy | in log
trigger-log percentage 100
trigger-log percentage 30
trigger-log percentage 30
trigger-log percentage 30
Switchname#show run | in log
service timestamps log datetime localtime show-timezone
logging buffered 10000 informational
logging console errors
aaa authentication login default group tacacs+ line
trigger-log-percentage 100
log config
bgp log-neighbor-changes
deny ip any any log
logging source-interface Loopback129
logging host XX.XX.XX.XX
snmp-server enable traps syslog
privilege exec level 0 show logging
logging synchronous
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
logging synchronous
logging synchronous
Switchname#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switchname#(config)#
Switchname#(config)#
Switchname#(config)#privilege exec level 0 show pfr
Switchname#(config)#pfr-map MAP 4
Switchname#config-pfr-map)# set trigger-log-percentage 100
Switchname#(config-pfr-map)#pfr-map MAP 6
Switchname#(config-pfr-map)# set trigger-log-percentage 100
Switchname#(config-pfr-map)#pfr-map MAP 7
Switchname#(config-pfr-map)# set trigger-log-percentage 100
Switchname#config-pfr-map)#
Switchname#config-pfr-map)#^Z
Switchname#show pfr master policy | in log
trigger-log percentage 100
trigger-log percentage 100
trigger-log percentage 100
trigger-log percentage 100
Switchname#show run | in log
service timestamps log datetime localtime show-timezone
logging buffered 10000 informational
logging console errors
aaa authentication login default group tacacs+ line
trigger-log-percentage 100
log config
bgp log-neighbor-changes
deny ip any any log
logging source-interface Loopback129
logging host XX.XX.XX.XX
snmp-server enable traps syslog
privilege exec level 0 show logging
logging synchronous
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
logging synchronous
logging synchronous
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S, 15.4(2)S |
|
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.4, 15.5(3)S2, 15.6(0.22)S0.14, 15.6(1)T0.1, 15.6(1.12)S, 15.6(1.12)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw43640 | Title: | EPA1x100G: %SYS-2-LINKED: SIP0/0: Bad enqueue error message |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
With EPA1x100G SYS-2-LINKED: SIP0/0: Bad enqueue error message is seen on the router console.
Below is an example of the error message seen for HundredGigE1/0/0 interface of EPA1x100G :
Sep 14 23:53:34.236: %SYS-2-LINKED: SIP1/0: Bad enqueue of 32D1880C in queue 300EEEFC -Process= "", ipl= 2, pid= 58
Conditions:
1. This can be seen during soft/hard OIR of the EPA1x100G
2. It can also be seen during router reload.
3. This error is also seen when the routers at both the ends (in case of a back to back) are reloaded simultaneously.
Workaround:
Once hit on this condition reload may solve the issue, slot and subslot reload doesn't solve the issue.
Further Problem Description:
|
|
Last Modified: | 15-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S, 15.5(3)S0.1 |
|
Known Fixed Releases: * | 15.4(3)S, 15.4(3)S1, 15.4(3)S2, 15.4(3)S3, 15.4(3)S4, 15.4(3)SN1, 15.5(3)S1.1, 15.5(3)S2, 15.6(0.22)S0.14, 16.2(0.176) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy33103 | Title: | incoming frame from AC is punted even though l2tp session is down |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
When l2tp session is down, packets which is coming from AC port is not dropped but punted to cpu.
Conditions:
NA
Workaround:
none so far
Further Problem Description:
This issue does not happen every time in all l2tp sessions.
In our lat setup, the issue was seen in 50-60 sessions when 500 sessions went to down.
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S, 15.6(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy05479 | Title: | XE316:PfRv3 Data Inconsistency causing crash(140K TCs) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
DataInconsistency traceback and crash at uncertain time.
Conditions:
PfRv3 on high scale setup. One VRF 2000 branch sites, 140K TCs.
Using command "clear domain ... vrf ... master traffic-class" to clear all traffic-classes
Workaround:
Reduce the usage of this command "clear domain ... vrf ... master traffic-class"
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)M2, 15.5(3)S1.11, 15.5(3)S2, 15.6(0.22)S0.17, 15.6(1.20)T, 15.6(1.22.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq54538 | Title: | Handle delete of key chain when in use with current macsec session |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a macsec session is using a keychain, a delete of the keychain removes the macsec session.
Conditions:
Have a keychain config.
Use the keychain to bring up a macsec session.
Delete the keychain.
Workaround:
Remove the keychain from the macsec session first and then delete the keychain.
Further Problem Description:
The delete of the keychain should be disallowed if it is in use by a macsec session.
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.2(5.0.91)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 15.5(0.18)S0.7, 15.5(1)S, 15.5(1)SN, 15.5(1.8)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq71259 | Title: | MKA session should re-establish automatically after clear mka session |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When an Active MKA session is present and you issue the command 'clear mka session', the MKA session comes down. However, it doesn't restart unless you manually trigger a config change.
Conditions:
An active MKA session needs to be present and 'clear mka sessions' needs to be issued by the user
Workaround:
Manually trigger a config change.
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.2(5.0.91)E, 15.2(5.5.63)E, 15.2(5.5.64)E, 15.5(0.18)S0.7, 15.5(1)S, 15.5(1)SN, 15.5(1.8)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux01038 | Title: | TCA cannot be reported when MMA report a loss over threshold |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
TCA cannot be reported when MMA report a loss over threshold
Conditions:
When I run the script PfRv3_Timer_and_threshold and PfRv3_verify_CSCut61094 together ,the PfRv3_verify_CSCut61094 will be failed because there is not Loss TCA reported when there is big loss reported by MMA.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.5, 15.5(3)S2, 15.6(0.22)S0.13, 15.6(1)T0.1, 15.6(1.15)T, 15.6(1.22.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw75310 | Title: | ASR1K: abnormal config for cfm offload sampling |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR1K: abnormal config for cfm offload sampling
Conditions:
1. config MEP with 100ms , 2000 offload sampling;
2. modify 100ms to 1s;
3. show cfm config.
4. offload sampling defined with 1s CCM, this is not expected behavior.
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 18-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S, 16.2(0) |
|
Known Fixed Releases: * | 15.6(1.12)T, 15.6(1.17)S, 15.6(1.22.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux47123 | Title: | Polaris: In FIPS mode, router should crash if it can not get HW entropy |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
router should crash if it can not get HW entropy source while FIPS mode is on.
Conditions:
FIPS mode is on
Workaround:
no
Further Problem Description:
router should crash if it can not get HW entropy source while FIPS mode is on.
|
|
Last Modified: | 20-FEB-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.2(5.1.16)E, 15.2(5.5.66)E, 16.2(0.280), 16.3(0.45) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy15137 | Title: | ASR ZBF drops ICMP Type 3 Code 4 message with VASI interfaces |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR with zone-based firewall may drop ICMP Type 3 Code 4 generated by the router
Conditions:
Application doing Path MTU Discovery with TCP
ASR running ZBF with VASI interfaces
Workaround:
Decrease layer 2 MTU on the physical interface on the way into the box
Further Problem Description:
|
|
Last Modified: | 22-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S0.2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut49714 | Title: | GEC:QoS: pkt buff util high after apply/remove flat policy w/ fair-queue |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Packet buffer utilization goes high under oversubscription condition.
Conditions:
When using ASR1001-X, ASR1002-X or ESP100/200 hardware with aggregate port-channel feature. If there has been a QoS policy applied and removed from the port-channel interface which contains the "fair-queue" feature, we might see the packet buffer utilization goes high with oversubscribed traffic condition. If the packet buffers utilization goes really high, then the important control protocols packets might get dropped.
Workaround:
Don't apply and remove the QoS policy-map containing fair-queue feature to aggregate port-channel. If the condition is hit, then resetting ESP or reload router is needed.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(3)S, 16.2(0) |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.3(0.46) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv64111 | Title: | ASR crash at ipv4_nat_destroy_addrport_bind |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR crash at ipv4_nat_destroy_addrport_bind
Conditions:
Router configured for NAT
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S1.9 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 15.6(1)S, 16.2(0.170) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw33451 | Title: | AVC: revert workaround for conversation tool following CSCuv05447 fix |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Due to the workaround applied the server and client byte counts might be incomplete.
Conditions:
IP Packet fragmentation.
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.180) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux53201 | Title: | ASR1K: IPv6 traffic classification issue |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IPv6 traffic is not classified correctly under QoS
Conditions:
class-map with match-any to match both IPv4 and IPv6 traffic.
Workaround:
The following commands can work as a workaround
platform qos marker-statistics
platform qos match-statistics per-filter
platform qos match-statistics per-ace
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.3(0.42) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw79438 | Title: | NAT64: MAP-T 1300-bytes packet drop at high traffic rate |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
NAT64 MAP-T packets bigger than 1280 default IPV6 MTU size may be dropped with high rate
with "nat64 settings fragmentation header disable" is set.
Conditions:
"nat64 settings fragmentation header disable" is set, and high traffic load.
Workaround:
Do not turn on "nat64 settings fragmentation header disable"
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S3.3 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw73226 | Title: | GRE checksum is wrong for Fragmented packets |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
GRE checksum is wrong for Fragmented packets in ASR1k
Conditions:
Hardware :ASR1k
Software :asr1001-universalk9.03.13.02.S.154-3.S2-ext.bin
Topology :
2800-1(Fa0/1)-------------------G0/0/0 ASR1000-2 G0/0/1-------------------Gig0/2 3900-1Gig0/1--------------------Fa0/0 2800-2
GRE is established between 2800-1& 2800-1 with default MTU
IPSEC is established between ASR1000-2 & 3900-1 with MTU1400
ISIS is running on top of the GRE interface.
Workaround:
1, Configure a big mtu to avoid fragment in outgoing interface of the ASR1k. Or,
2, Remove "tunnel checksum" on ASR1K.
Further Problem Description:
This is ASR1K/CSR/ISR G3 tunnel common issue, not ISIS specific.
It will appear if fragment happened on tunnel interface which have "tunnel checksum" configured.
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S2 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 16.2(0.184) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw39062 | Title: | ASR1K: temperature sensor threshold values are showing wrong |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Temperature sensor threshold values are showing wrong for CC slots.
Conditions:
Checking sensors on ASR1K
Workaround:
none
Further Problem Description:
none
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S, 16.2(0) |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.166) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw53543 | Title: | Stale entries for unauthenticated user in ISG dont clear . |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The unauth sessions are configured to expire in 2 mins, but many unauth sessions are showing up for several weeks.
Conditions:
Previous event Account-Logon exited without clearing some flag after some time when the timer expires Timer-expiry event is waiting for previous event to clear the flag, because of this session is in stale state. This happens where Account-logon exited without clearing the flag.
Workaround:
This issue is seen only on HA setup, on single RP this issue will not be seen.
Further Problem Description:
Not all unauth sessions are remaining stale, many others are getting removed from ISG .
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S4.1, 15.4(3)S5, 15.5(2)S2.1, 15.5(3)S1.1, 15.5(3)S2, 15.6(0.22)S0.14, 15.6(1.12)S, 16.2(0.273), 16.3(0.72) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw39613 | Title: | ASR1K fails to perform NAT when flow cache entries are disabled. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
NAT router fails to translate the source ip-address of outside-to-inside packets.
Conditions:
The problem is seen when the following conditions are met.
- "no ip nat create flow-entries" is configured.
- Both source and destination ip-addresses are targeted for translation.
Workaround:
There is no workaround.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S3.1, 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2, 16.2(0.184) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu48458 | Title: | ASR1k/15.4(3)S QinQ frames are dropped under "TCAM Failure Drops" |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
QinQ frames are dropped
Conditions:
QinQ accross EoMPLS pw
Workaround:
unknown yet
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.5(2.2)S |
|
Known Fixed Releases: * | 15.4(3)S4.7, 15.4(3)S5, 15.5(3)S1.2, 15.5(3)S2, 15.6(0.22)S0.8, 16.2(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw71226 | Title: | Call stuck in a deactivating state (CUBE-SP) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR SBC (CUBE-SP) intermittently causes calls to get stuck in a deactivating state. Attempting to abort it via adjacency "no attach force abort" does not clear the call nor does the command "clear sbc sbe call".
Conditions:
Issue occurs on ASR SBC routers configured as CUBE-SP.
Workaround:
Reload the ASR to remove calls in the deactivating state.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.3(0.1) |
|
Known Fixed Releases: * | 15.4(3)S4.1, 15.4(3)S5, 16.2(0.193) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux51271 | Title: | Need to add the attributes 32 and 30 under all status-query related |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Need to add the attributes 32 and 30 under all status-query related
Conditions:
need to add the attributes 30 called-station-id and 30 nas-id under the common attributes , so that it is available under all the user-profile-query status-query and other related query.
Workaround:
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.5(3)S1.4, 15.5(3)S2, 15.6(1.17)S0.9, 15.6(1.17)SP, 16.3(0.50) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu45832 | Title: | STUN packets not handled properly by CPP SBC module in ASR CUBE |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR CUBE detects Looping packet and drops it generating a Traceback, as soon as it receives STUN packets to media ports negotiated for VIDEO comes in to the CUBE.
CUBE generate traceback and log message "%IP-3-LOOPPAK: Looping packet detected and dropped" as below.
015642: Mar 17 15:22:44.264 MET: %IP-3-LOOPPAK: Looping packet detected and dropped -
src=10.38.200.244, dst=10.38.200.163, hl=20, tl=48, prot=17, sport=16460, dport=20908
in=GigabitEthernet0/0/1, nexthop=10.38.200.241, out=GigabitEthernet0/0/1
options=none -Process= "IP Input", ipl= 0, pid= 185
-Traceback= 1#7c528ec8d7d7fe2484c1e2e98fb80561 :7FA0608DE000+7E8DB39 :7FA0608DE000+7E8D928 :7FA0608DE000+DDA65BB :7FA0608DE000+7E8BA18 :7FA0608DE000+7E71EDA :7FA0608DE000+7E71225 :7FA0608DE000+7E70679 :7FA0608DE000+7E703E0
Conditions:
CUBE running in IOS XE-313
Workaround:
Downgrade the IOS to XE 312.
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.6, 15.4(3)S5, 15.6(0.5)T, 15.6(0.7)S, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw54118 | Title: | Unable to apply flow record to flow monitor |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Unable to apply same flow record to monitors with long names. The problem appears when monitor name exceeds 23 characters and first 23 characters are identical.
Conditions:
- multiple flow monitors with long names configured
- running 15.3(3)S1
Workaround:
- define multiple flow records
- define shorter than 23 character names for flow monitors
- or define monitor names where first 23 characters are different
- issue not present in:
Version 15.2(4)S4a
Further Problem Description:
|
|
Last Modified: | 23-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S1.1 |
|
Known Fixed Releases: * | 15.5(3)S1.1, 15.5(3)S2, 15.6(0.22)S0.7, 15.6(1.17)SP, 15.6(1.18)T, 15.6(1.22.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux74788 | Title: | ASR1002-X: Memory leak in IOSD: acl-handle |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR1002-X with 8GB memory running Version 15.1 goes unresponsive within 5-6 days the router crashes with Watchdog. For testing they upgraded to 15.4(3)S4 and then to 15.5(3)s1a as well but same issue.
IOSD memory leak in acl-handle process is noticed.
Logs during issue before crash on Dec 2:
Dec 2 13:31:47.777 EST: %PLATFORM-3-ELEMENT_CRITICAL: SIP0: smand: RP/0: Committed Memory value 115% exceeds critical level 100%
CMD: 'show plat softw status contr br' 14:06:32 EST Wed Dec 2 2015
IOSXE-WATCHDOG: Process = Exec
.Dec 2 14:07:04.115 EST: %SCHED-0-WATCHDOG: Scheduler running for a long time, more than the maximum configured (120) secs.
-Traceback= 1#a3fe01abba2bac2871f0e4442db8a494 ld-linux-x86-64:7FED81E8A000+8A
Conditions:
With PFR on head end master controller and BR
Workaround:
They disabled the PfR on the head end Master Controller and Border Routers (DMVPN Hub routers). The memory looks stable since then.
--------------------------------------------------------------
NADC2-PfR-MC#sh pfr ma
OER state: disabled
NADC2R4-DMVPN-HUB2#sh pfr bo
OER BR 10.220.253.52 DISABLED, MC 172.27.0.186 UP/DOWN: DOWN
Conn Status: CLOSED
OER Netflow Status: ENABLED, PORT: 3949
Version: 3.3 MC Version: 0.0
Nbar Status: Inactive
Exits
NADC1R2-DMVPN-HUB1#sh pfr bo
OER BR 10.220.253.51 DISABLED, MC 172.27.0.186 UP/DOWN: DOWN
Conn Status: RETRY
OER Netflow Status: ENABLED, PORT: 3949
Version: 3.3 MC Version: 0.0
Nbar Status: Inactive
Exits
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw66285 | Title: | ASR1001-X: Counters for Q-in-Q sub interface not working as expected |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Under the show vlan output:
The "Transmitted" is the same/very close to "output".
But "Received" is nowhere near the "input", also customer reports the rate the counter increased/refreshed is very slow.
Conditions:
Interface with service instance and sub-interface configured
Workaround:
Use 'plim ethernet vlan filter disable' on the main interface.
Further Problem Description:
|
|
Last Modified: | 24-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S2.1 |
|
Known Fixed Releases: * | 16.3(0.100) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux42536 | Title: | Polaris: Cannot execute Xconnect with pseudowire force switchover |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The exec command xconnect backup force-switchover or
l2vpn redundancy activate may fail with the message
%Xconnect: manual switchover failed
when attempting to switch over to a backup Any Transport over MPLS (AToM)
pseudowire.
Conditions:
This symptom has been observed on a dual-RP system after a Stateful Switchover
(SSO) has been performed.
Workaround:
Use the exec command clear xconnect or clear
l2vpn service to reset the state of the pseudowire prior after
performing SSO.
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.6(0.22)S0.12, 15.6(1.16)T, 15.6(1.17)S0.7, 15.6(1.17)SP, 15.6(1.22.1a)T0, 16.2(0.245), 16.3(0.35), 7.3(0)D1(0.203), 7.3(0)IZN(0.13), 7.3(0)N1(0.265) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue74708 | Title: | destination-glean recovery not shown in show snoop policy command |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:In ipv6 snooping policy, destination-glean recovery not shown in show ipv6 snooping policy command, while the data-glean recovery is shown in show ipv6 snooping policy command
Conditions:In ipv6 snooping policy, destination-glean recovery not shown in show ipv6 snooping policy command
Workaround:user can check the destination-glean recovery use show running command.
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 15.2(1)E, 15.3(2)S |
|
Known Fixed Releases: * | 15.1(1)IC66.63, 15.1(1)ICA4.122, 15.1(1)ICB29.36, 15.2(2)E, 15.2(2)E1, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(2.13)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuc43160 | Title: | fhs-ask1k dynamic Binding Table number not include dhcp prefix entry |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: dynamic binding table number wrong,dhcp iapd prefix entry not count by dynamic, but by total number
Conditions:enable prefix-glean from dhcpv6-pd,
Workaround:none
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S |
|
Known Fixed Releases: * | 15.1(1)IC66.63, 15.1(1)ICA4.122, 15.1(1)ICB29.36, 15.2(2)E, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(2.13)S, 15.3(2.15.1)XEB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtl81700 | Title: | Delegate registration subscriber config error after clear and re-config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Delegate registration subscriber config error after clear and re-config
Conditions:
Problem coming after clearing the existing config and re-config
Workaround:
None
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(2)S |
|
Known Fixed Releases: * | 15.1(3)MR, 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S0.5, 15.1(3)S1, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts13156 | Title: | Slow Response in Call-Policy in Large SBC B2B Config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:Slow Response in Call-Policy in Large SBC B2B Config
Conditions:B2B redundancy mode active. If redundancy is shut, there is no response isse.
Workaround:shut redundancy, update policy, no shut redundancy application group.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(2)S |
|
Known Fixed Releases: * | 15.2(1)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts10005 | Title: | With large scale subscribers, show running-config takes too long time |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
It also forces some subscribers to go offline due to high cpu usage.
Conditions:
When there're a large scale suberscribers on SBC, issuing will take about 20 mins to complete.
Workaround:
No workaround till now
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S |
|
Known Fixed Releases: * | 15.1(3)MR, 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S1.5, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx13238 | Title: | [XE35] illegal characters in configuration file delivered by phone proxy |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
RTX can not parse configuration file
Conditions:
There's illegal characters in configuration file delivered by phone proxy to endpoint:
Workaround:
N/A
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.2(1)S0.8, 15.2(1)S1, 15.2(1.18)S0.6, 15.2(2)S, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2, 15.2(2)SNG, 15.2(2)SNI, 15.2(2.5)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx13237 | Title: | [XE35]phone proxy does not recogonize device name other than SEP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
phone proxy does not modify key fields in configuration file
Conditions:
phone proxy does not recognize device name other than SEP, as a result, to interwork with RTX which uses CSF (client service framework) as prefix of device name, it is needed to do enhancement to relax the restriction.
Workaround:
use fake device name beginning with SEP
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.2(1)S0.8, 15.2(1)S1, 15.2(1.18)S0.6, 15.2(2)S, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2, 15.2(2)SNG, 15.2(2)SNI, 15.2(2.5)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtr86950 | Title: | CPU HOG with FP reload for FNF |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CPU HOG with FNF for 4k DVTI sessions
Conditions:
Active ESP reload causes CPU hog for 4k DVTI sessions
Workaround:
None
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.1(1)SY, 15.2(0.18)S0.11, 15.2(1)S, 15.2(1)S1, 15.2(1.0.0)IPI2, 15.2(1.17)S, 15.2(2)GC, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCts43931 | Title: | [XE35 SLT] error message generated when make 10 cps TLS-SRTP calls |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
error message was seen when trying to make 10 cps TLS-SRTP interworking calls against XE35 image
Conditions:
30-August-2011, 08:31:22.258 UTC. Log 0x303002F contains more parms than are passed by sckorig2.c, line 1091
Image: asr1000rp1-adventerprisek9.BLD_V152_1_S_XE35_THROTTLE_LATEST_20110826_175307.bin
Test topology:
navtel1---sbc1---sbc2---navtel2
Workaround:
NA
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.2(1)S0.3, 15.2(1)S1, 15.2(1.15)S, 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: | CSCto62900 | Title: | Media after Xfer fails due to low TTL value of RTP pkts rching ATT n/w |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
No voice path after transfer scenario given below
Ph1 -----> CUCM -------> CUBE ---------> AT &T-------> CUBE ------> CUCM -------> Ph2
Ph1 -----> CUCM -------> CUBE ---------> AT &T-------> CUBE ------> CUCM -------> Ph3
Ph1 commits transfer, but there is no voice path between Ph2 and Ph3.
Note
=====
Here the CUCM and CUBE shown on either end of the AT & T trunk are the same. So essentially, each call (for instance from Ph1 to Ph2) has 4 legs on the CUBE.
Conditions:
When the transfer is committed, there is consistently a glare scenario occuring where CUBE is sending Re-INVITE at the same time that the CUCM does. This leads to the media direction not being resolved correctly in the subsequent transactions, and this causes the lack of voice path confirmation.
Workaround:
None. It may work if there is a hold/resume sequence following the transfer, however this has not been tested.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(1)S0.1 |
|
Known Fixed Releases: * | 15.2(0.18)S0.6, 15.2(1)S, 15.2(1)S1, 15.2(1.11)S, 15.2(1.8)S, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2, 15.2(3)GC, 15.2(3)GC1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtr16967 | Title: | XE34:sbc is failed to switchover when background traffic is 15cps call |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
switchover is failed
Conditions:
background traffic is 15cps basic sip call
Workaround:
so far, no workaround was found except to reload these two boxes.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S |
|
Known Fixed Releases: * | 15.1(3)MRA, 15.1(3)MRA1, 15.1(3)MRA3, 15.1(3)MRA4, 15.1(3)S1.4, 15.1(3)S2, 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6, 15.1(3)S7 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx01415 | Title: | Negative value can be used to index into idb table |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Its passed NULL HWIDB or SWIDB.
Conditions:
When IDB is created and its passed NULL argument(SWIDB or HWIDB) to network-infra API's. This issue is happened some rare cases.
Workaround:
There is no workaround for this defect.
|
|
Last Modified: | 01-FEB-2016 |
|
Known Affected Releases: | 15.2(2)S |
|
Known Fixed Releases: * | 15.0(1.33)EZD, 15.0(10.16)EMW, 15.0(9.1)PCD, 15.0(9.50)EMW, 15.1(1)ICB40.1, 15.1(1.23)SID, 15.1(2)SG, 15.1(2)SG1, 15.1(2)SG1.170, 15.1(2)SG2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz59258 | Title: | dsp streams not deleted during in some instances of abnormal disconnect |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Dsp not released when the IP call leg is abnormally disconnected by SIP SPI. This is not reproducible consistently. It is
more of timing issue.
Conditions:
SIP SPI abnormally disconnects the call with out sending 200 ok
Workaround:
Switching over to the secondary to recover dsp resources
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(2)S |
|
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.3(0.12)T, 15.3(0.15)PI21, 15.3(0.8.4)PIH20, 15.3(1)S1, 15.3(1)S1e, 15.3(1)S2, 15.3(1)T, 15.3(1)T1, 15.3(1)T2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub32891 | Title: | ASR1k crash when booting up with a mip configured under Xconnect |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Router is crashing upon bootup if router was configured with CFM MIP under xconnect and subsequently reloaded
Conditions:
Workaround:
None
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S1, 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)S1.9, 15.2(4)S2, 15.2(4)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx81562 | Title: | Validate replay data ethernet ping always fails on ASR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LBM got dropped when validated the replied data is activated on ASR1k
Conditions:
When LBM is initiated with the validation flag.
Workaround:
The issue has been fixed with CSCtx81562. Without the fix, the CFM loopback can still work without turning on the validation option as the workaround.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.3(0.10)S, 15.3(0.8)T, 15.3(1)S, 15.3(1)S1, 15.3(1)S1e, 15.3(1)S2, 15.3(1)T, 15.3(1)T1, 15.3(1)T2, 15.3(1)T3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz32627 | Title: | Phase II does not come up on ASR for DVTI w/VRF and ASA endpoint |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
dVTI tunnel does not come up with ASA
Conditions:
Set up an ASR(running either 3.5.1S or 3.6.0S) with dVTI configuration with multiple VRFs. When an ASA tries to bring up the tunnel, it fails on phase II
Workaround:
use ASR version 3.4.0S, 3.4.3S, 3.5.0S
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S1 |
|
Known Fixed Releases: * | 15.1(1)SY, 15.1(2)SY, 15.2(2)S1.4, 15.2(2)S2, 15.2(2.19)S0.6, 15.2(2.2.70)ST, 15.2(3)GC1, 15.2(3)GCA1, 15.2(3)T2.1, 15.2(3)T3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua22935 | Title: | Montage-2: Issues in ISSU related to SIP from_header |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
There was a issue in ISSU due to change in sip header length.
Conditions:
Issue only in ISSU
Workaround:
No workaround
Further Problem Description:
Upgrade/downgrade function require changes related to SIP from header length.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.3(0.8)S, 15.3(0.8)T, 15.3(1)S, 15.3(1)S1, 15.3(1)S1e, 15.3(1)S2, 15.3(1)T, 15.3(1)T1, 15.3(1)T2, 15.3(1)T3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz21299 | Title: | PfR/PBR/SCALE/ASR1K - re-use of route-map sequence cause Invalid argumen |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PfR MC may show some traffic-classes are uncontrolled due to exit mismatch.
Conditions:
This symptoms is observed when PfR optimize traffic-class with PBR in a scale DMVPN setup and when there is a brownout in one of the links.
Workaround:
None.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(1)S |
|
Known Fixed Releases: * | 15.0(7.15)EMD, 15.0(7.19)EMW, 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(1)SY4, 15.1(1.23)SID, 15.1(2)SG, 15.1(2)SG1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua62927 | Title: | Midcall Codec renegotiation denial |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Mid call codec change is enable.
Conditions:
With Voice class codec config, mid call codec renegotiation will not be disable.
Workaround:
No Workaround
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S |
|
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.2(2.19)S0.13, 15.2(3.16)M0.6, 15.2(4)GC, 15.2(4)GC1, 15.2(4)S, 15.2(4)XB10, 15.3(0.13)S, 15.3(0.5)T, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub02743 | Title: | FP100#lfd_install_local_label_for_key: installation failed Error-stbyRP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
lfd_install_local_label_for_key: installation failed Error on Stby RP
Conditions:
remove the MCPT timer or flapping the ATM cell packed interface
Workaround:
none
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.1(1)IC66.14, 15.1(1)ICA4.16, 15.1(1)ICB29.1, 15.1(1)ICB40.1, 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(1)IC273.1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub16463 | Title: | atm overhead keyword not available with bandwidth remaining ratio |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
bandwidth remaining ratio command does not accept atm keyword for atm cell tax compensation.
Conditions:
This problem is apparent during basic command line configuration.
Workaround:
Use bandwidth remaning percent configuration instead of bandwidth remaining ratio. When converting from ratio to percent take into account that percent configurations are based on a total of 100% and not the sum of the ratios.
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(2)S1 |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(1.2.3)PI22, 15.2(2)E, 15.2(2)E1, 15.2(2b)E, 15.2(4)GC |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua73416 | Title: | Capabilities flag for IKEv2 SA is not set for on-demand DPD |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Capabilities flag under 'Show crypto session detail' output is not set with a value of 'D' when on-demand DPD is enabled for an IKEv2 SA
Conditions:
On-demand DPD should have been configured either under the relevant IKEv2 profile or globally
Workaround:
Use 'show crypto ikev2 sa detailed' CLI to check if DPD is configured for the IKEv2 SA's
|
|
Last Modified: | 02-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.1(2)IC66.3, 15.2(1)IC273.70, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E, 15.2(2.2.70)ST, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud96084 | Title: | Demand circuit neigh's info not synced to Standby |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
OSPF interface DC status is not synced to standby when NSR is configured.
Conditions:
Please refer to "OSPF-DE-Evaluation" enclosure for repro steps.
Workaround:
Configure "ospf demand-circuit" on both routers.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3 |
|
Known Fixed Releases: * | 15.1(1)IC66.17, 15.1(1)ICA4.16, 15.1(1)ICB40.1, 15.2(1.1)PSR, 15.2(2)E, 15.2(2)E1, 15.2(2a)E1, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud94028 | Title: | GLC-GE-100FX PID not shown on ASR1000 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When SFP GLC-GE-100FX is Inserted the following output has problem
1)No PID shown on ID PROM Contents of SFP
2)No environmental sensor data on SFP
Conditions:
Workaround:
Need to add support for SFP GLC-GE-100FX in code
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.3(2)S0.3, 15.3(2)S1, 15.3(2)S1b, 15.3(2)S1c, 15.3(2)S2, 15.3(2.9)S, 15.3(3)S, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue23287 | Title: | ASR1K XE310:lisp control assert @ __be_lisp_mapping_record_build |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A LISP assert syslog message with an associated traceback is issued when a LISP Map-Server is sending a LISP Map-Notify message with a large number of mapping records. No functionality is affected by the displayed message.
Conditions:
A router configured as a Locator ID Separation Protocol (LISP) Map Server having to send a large number of mapping notification records to an ETR. This condition is typically met when a LISP site is registering a large number of prefixes.
Workaround:
There are no workarounds.
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(1)T, 15.3(3)S |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)IC273.13, 15.2(4)XB11, 15.3(2)S0.4, 15.3(2)S1, 15.3(2)S1b, 15.3(2)S1c, 15.3(2)S2, 15.3(2)T1, 15.3(2)T2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud95591 | Title: | CLI's need to be removed from ASR1K |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CLI's need to be removed from ASR1K
Conditions:
The CLI's should be present in ISR Platform
Workaround:
The perfect fix is committed.
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.2(1.1)PSR, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(2.21)PI23a, 15.3(2.8.2)PIB23, 15.3(2.9)S, 15.3(2.9)T, 15.3(3)JA100, 15.3(3)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud56611 | Title: | ASR1K : Loopback ping failing from peer1 to peer3 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traffic flow fails with VRF aware IPSec while using crypto maps
Conditions:
VRF configuration on the "iskamp" or "ikev2" profile has been changed
Workaround:
Remove and re-apply crypto map on interface
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S2.14, 15.3(1)S0.7, 15.3(1)S1.6, 15.3(1.12)S, 15.3(1.16)S, 15.3(1.17)S0.13, 15.3(1.17)S0.4, 15.3(1.17)S0.8, 15.3(2)S |
|
Known Fixed Releases: * | 15.1(2)IC66.3, 15.2(1)IC273.70, 15.2(1)ICA4.30, 15.2(1.2.3)PI22, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E, 15.2(2.2.70)ST, 15.2(2b)E, 15.2(4.0)ST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf05021 | Title: | codec g723 removed from dsp firmware but still available in CLI |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Dsp firmware removed support for codec G723. But it is still configurable in CLI.
dspfarm profile 20 transcode
codec g723r63
codec g723r53
maximum sessions 300
Conditions:
Workaround:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.3(1)T3, 15.3(1)T4, 15.3(2)T1.3, 15.3(2)T2, 15.3(2)T3, 15.3(2)T4, 15.3(2.15.2)XEB, 15.3(2.17)S, 15.3(2.8.2)PIB23, 15.3(2.9)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf21465 | Title: | GETVPN re-registration timers shorter than documented |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
GETVPN Group Members (GM) registration window starts at 3%-5% of the remaining TEK lifetime, rather than at 5%-7%, as documented. This can lead to TEK expiry on some GMs in situations when the registration process is slow.
Conditions:
Cisco ASR running IOS XE 3.7, IOS 15.2S
Workaround:
Extend TEK lifetime (and accordingly the corresponding registration window) to avoid traffic drops due to TEK expiration.
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.2(0.2)S |
|
Known Fixed Releases: * | 15.1(2)IC66.3, 15.2(1)IC273.70, 15.2(1)ICA4.30, 15.2(1.2.10)PI22, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E, 15.2(2)E1, 15.2(2.2.70)ST, 15.2(2a)E1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf65715 | Title: | Call failure seen with ANAT ipv6 and ipv4 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When CUBE received Invalid ANAT offer i.e. it received 2 valid audio mline without having a:mid attribute.
Conditions:
When ANAT is configured on CUBE to handle ipv4 and ipv6 calls.
Workaround:
Disable ANAT
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(2.14)S, 15.3(2.18)S |
|
Known Fixed Releases: * | 15.2(1.2.17)PI22, 15.3(2)T1.3, 15.3(2)T2, 15.3(2)T3, 15.3(2)T4, 15.3(2.15)T, 15.3(2.15.4)XEB, 15.3(2.21)PI23, 15.3(2.21.1)PIH22, 15.3(3)JA |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud42313 | Title: | Montage2-XE3.9: After REFER Consume packet stat showing wrong |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
For CPA based call transfer (REFER Consume) packet stats showing wrong output.
Conditions:
Call transfers with CPA (refer consume) packets are not incrementing.
Workaround:
NA
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S |
|
Known Fixed Releases: * | 15.3(2.12)T, 15.3(2.12.1)PIH22, 15.3(2.15.2)XEB, 15.3(2.19)S, 15.3(2.8.2)PIB23, 15.3(3)JA, 15.3(3)JA100, 15.3(3)JA1m, 15.3(3)JAA, 15.3(3)JAB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud78861 | Title: | [Seawolf] LI0 value exported for Null value interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | The "Null" interface in the cache is being translated to LI0 in the exporter
Symptom:
Conditions:
AVC 2.0 configuration, when injecting traffic that has the output interface as null in the cache, the exporter will replace the value of Null to LI0
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: * | 15.3(1)S, 15.3(2)S |
|
Known Fixed Releases: * | 15.3(2.15.4)XEB, 15.3(2.19)S, 15.3(2.21)PI23a, 15.3(3)S, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S3, 15.3(3)S4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCua95084 | Title: | 'network-clock synch participate' cmd should check presence of 'slot' |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
'network-clock synchronization participate' command does not check presence of slot before configuration.
Conditions:
Configure 'network-clock synchronization participate' for a slot which is not present in the system.
Workaround:
NA
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S, 15.3(3)S |
|
Known Fixed Releases: * | 15.1(3)S5.14, 15.1(3)S6, 15.1(3)S7, 15.2(4)S3.5, 15.2(4)S4, 15.2(4)S4a, 15.2(4)S5, 15.2(4)S6, 15.3(2)S0.9, 15.3(2)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf04906 | Title: | asr crashed @ __be_memcmp when running VZ Inst image with VZ Call flows |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Crash
Conditions:
Crash under load conditions
Workaround:
Fix given.While confId is valid do a hash entry search
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(1)S |
|
Known Fixed Releases: * | 15.2(1.2.7)PI22, 15.3(1)S1.6, 15.3(1)S2, 15.3(1)T1.1, 15.3(1)T2, 15.3(1)T3, 15.3(1)T4, 15.3(2)S0.5, 15.3(2)S1, 15.3(2)S1b |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug00905 | Title: | LISP:%LISP-4-ASSERT: Internal LISP error (vrf 1446) in unconfigure |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
%LISP-4-ASSERT: Internal LISP error (vrf 1446) in unconfigure
Conditions:
lisp unconfig
Workaround:
none
|
|
Last Modified: | 03-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)IC273.13, 15.2(1.2.16)PI22, 15.3(2)S0.4, 15.3(2)S1, 15.3(2)S1b, 15.3(2)S1c, 15.3(2)S2, 15.3(2)T1, 15.3(2)T2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh41597 | Title: | XE 3.11 : Memory leak seen for SRTP Passthrough Call |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Memory leak is seen when SDP passthru is configured.
Conditions:
When SDP passthru is configured.
Workaround:
None
More Info:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: * | 15.3(2.19)S0.12, 15.3(2.19)S0.4, 15.3(2.19)S0.8, 15.4(0.12)T, 15.4(0.12.3)PIH23, 15.4(0.15)S, 15.4(0.5)S, 15.4(0.6)S, 15.4(1)S |
|
Known Fixed Releases: * | 15.3(3)M0.3, 15.3(3)M1, 15.3(3)S0.4, 15.3(3)S1, 15.3(3)S2, 15.4(0.12.6)PIH23, 15.4(0.14)T, 15.4(0.14.1)CG, 15.4(0.16)S, 15.4(0.22.1)PIH23 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh23859 | Title: | GETVPN Suite-B: "SERIOUS ERROR: OVERLAPPING IV "with KS-ACL change |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
With Suite-B configured (i.e. esp-gcm / esp-gmac transform) on a GETVPN Key Server (KS), Group Members (GM) will see the following un-gated error message on the console when the KS policy ACL is changed or edited and a rekey is sent from the KS using "crypto gdoi ks rekey"...
May 31 09:56:49.906 IST: *** SERIOUS ERROR: OVERLAPPING IV RANGES DETECTED ***
When the GM receives the rekey, the policy is installed successfully. However, after this the GM re-registers twice and then these errors are displayed.
Conditions:
Suite-B is configured (i.e. esp-gcm / esp-gmac transform) on a GETVPN Key Server (KS), the KS policy ACL is changed or edited and a rekey is sent from the KS using "crypto gdoi ks rekey"
This issue was seen with at least 50 Group Member (GM) instances using VRF-Lite on a ASR1K GM box and no more than 30 ACE's in the KS policy ACL, however this issue should also be seen on a ISRG2 GM box with less GM instances and less ACE's as well.
Workaround:
If a Key Server (KS) policy ACL must be changed or edited while Group Members (GM) have already registered and downloaded GETVPN Suite-B policy (i.e. esp-gcm / esp-gmac transform), issue "crypto gdoi ks rekey replace-now" instead of "crypto gdoi ks rekey" after changing the KS policy ACL. (NOTE: a very small amount of traffic loss may be expected)
If possible, do not change the KS policy ACL after a GETVPN network using Suite-B is up and running.
NOTE: The fix requires both an upgrade of the KS and GM to properly work.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(1)T1.1, 15.3(3)S, 15.4(0.26)T0.1, 15.4(0.4)T |
|
Known Fixed Releases: * | 15.1(2)IC66.3, 15.2(1)IC273.70, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(2)E, 15.2(2)E1, 15.2(2.2.70)ST, 15.2(2a)E1, 15.2(2b)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue29595 | Title: | h323-h323 calls failing in case of SRTP passthrough |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
SRTP passthrough for h323 calls failing
Conditions:
h323 calls are failing when both the legs are h323 and its SRTP passthrough
Workaround:
none
Further Problem Description:
Path confirmation is failing in case of SRTP-pasdthrough h323-h323 call.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: * | 15.2(4)S5.15, 15.3(2)S0.13, 15.4(0.15)S, 15.4(0.17)S, 15.4(0.19)S0.4, 15.4(0.7)S, 15.4(1.1)STS, 15.4(1.15)S |
|
Known Fixed Releases: * | 15.3(3)M1.7, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S1.9, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S2t, 15.3(3)S3, 15.3(3)S4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj96123 | Title: | Standby ASR1001 router crashed due to SBC related issue |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR1000 crashed with following log in crashinfo file:
UNIX-EXT-SIGNAL: Segmentation fault(11), Process = SBC main process
Conditions:
the ASR1000 router is the standby router in CUBE-SP setup.
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S3 |
|
Known Fixed Releases: * | 15.2(4)S4.8, 15.2(4)S5, 15.2(4)S6, 15.3(3)S2.9, 15.3(3)S3, 15.3(3)S4, 15.4(1)S0.1, 15.4(1)S0.2, 15.4(1)S0e, 15.4(1)S1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui87779 | Title: | Re-config T1/E1 channel-group on PE cause xconnect session down |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
If a xconnect is configured on a channelized serial interface, the
channel group is removed then added back, and then the xconnect is reconfigured,
the xconnect may fail to pass packets.
Conditions:
This symptom has been observed if the no channel-group
command is used to remove the channel group while xconnects are currently
configured on the channelized interfaces.
Workaround:
Remove the xconnects using the no xconnect command
before removing the channel group.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S |
|
Known Fixed Releases: * | 15.2(4)S4.1, 15.2(4)S5, 15.2(4)S6, 15.3(3)M1.5, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S0.7, 15.3(3)S1, 15.3(3)S1a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui59290 | Title: | CUBE crashed when REFER is received without Refer-To header |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
If CUBE received a REFER without Refer-To header , CUBE crashed in some platforms and there were trace backs in others.
Conditions:
When REFER without Refer-To heaer is received.
Workaround:
Refer-To is mandatory header in REFER Request. Hence might not encounter this case.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(0.15)S, 15.4(1.1)STS |
|
Known Fixed Releases: * | 15.1(4)M8, 15.2(4)GC1, 15.2(4)M5.4, 15.2(4)M6, 15.2(4)S4.14, 15.2(4)S5, 15.3(3)M0.4, 15.3(3)M1, 15.3(3)S0.6, 15.3(3)S1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug78227 | Title: | header profile store-rule condition rejected at a special config order |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR1001-5-DEV(config-sbc-sbe-sip-hdr-ele)# sip header-profile hprof2
ASR1001-5-DEV(config-sbc-sbe-sip-hdr)# store-rule entry 1
ASR1001-5-DEV(config-sbc-sbe-sip-hdr-ele-act)# condition request-uri sip-uri-user store-as uname
Error: sip-uri-user is only valid for To, From and Request-Line
Conditions:
this happens if following config is paste into config terminal
or on reading startup-config with following config
----------------------------------------------------------------------------------------------
sip header-profile hprof1
store-rule entry 1
condition header-name Allow header-value store-as Avalue
store-rule entry 2
condition request-uri sip-uri-user store-as uname
Workaround:
exit sbc, re-enter the specified store-rule/condition
----------------------------------------------------------------------------------------------
sip header-profile hprof1
store-rule entry 1
condition header-name Allow header-value store-as Avalue
exit
exit
exit
exit
sbc test
sbe
sip header-profile hprof1
store-rule entry 2
condition request-uri sip-uri-user store-as uname
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.1(3)S4 |
|
Known Fixed Releases: * | 15.2(4)S4.1, 15.2(4)S5, 15.2(4)S6, 15.3(3)S0.7, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S3, 15.3(3)S4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj21502 | Title: | SBC SP only show 191 na-dst-prefix-table out of 200 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
show run only shows 191 na-dst-prefix-table out of 200
Conditions:
configured a lot of na-dst-prefix-table, specially, more than 191
Workaround:
none
Further Problem Description:
na-dst-prefix-table 192 to 200 seem to be working OK,
but cannot be shown and cannot save them into startup-config.
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: * | 15.3(1)S, 15.3(3)S |
|
Known Fixed Releases: * | 15.2(4)S4.4, 15.2(4)S5, 15.2(4)S6, 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 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue52655 | Title: | No Video legs out put for DO-DO with multicodec call |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
No Video legs out put for DO-DO BWcac with multicodec call
Conditions:
No Video legs out put for DO-DO BWcac with multicodec call
Workaround:
NO workaround
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: * | 15.3(1.17)S0.13, 15.3(2)S0.5, 15.3(2.18)S, 15.3(2.19)S0.12, 15.3(2.19)S0.4, 15.4(0.15)S, 15.4(0.17)S |
|
Known Fixed Releases: * | 15.2(1.2.83)PI23, 15.3(2)T1.3, 15.3(2)T2, 15.3(2)T3, 15.3(2)T4, 15.3(3)M1.8, 15.3(3)M2, 15.3(3)M3, 15.3(3)S1.10, 15.3(3)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj69605 | Title: | ASR-ISR/HA: CLI should reject second RG configuration under interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CLI should reject second RG configuration under interface. Presently CLI allows one to configure multiple RGs on one interface.
Conditions:
This was first identified on an ASR running XE 3.10 image
Workaround:
Do not configure 2 redundancy groups under one interface.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.1(3.10)T |
|
Known Fixed Releases: * | 15.3(3)M4, 15.3(3)S5.10, 15.3(3)S6, 15.4(1.10)T, 15.4(1.12)S, 15.4(1.9.2)XEB, 15.4(2)CG, 15.4(2)S, 15.4(2)S1, 15.4(2)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui80093 | Title: | [XE3.11] CUBE not falling to FT mode for srtp-rtp call in no DSP case |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
CUBE not falling to FT mode for srtp-rtp call in no DSP case
Conditions:
This is seen when DSP resources are shoutdown/unavailable in the router.
Workaround:
configure dspfarm profile in the router if available or do not configure "media flow-around" CLI .
Further Problem Description:
This issue is particularly observed when Flow-around is configured for srtp-rtp call and when there are DSP resources in the router
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.3(3)M1.8, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S1.10, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S2t, 15.3(3)S3, 15.3(3)S4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCug73485 | Title: | ASR1k: XE3.10 LISP ISSU traceback for Invalid input IPv6 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
LISP assert error and associated traceback displayed in the log. No other side effects.
Conditions:
ISSU ISSD on a router configured with the Locator ID Separation Protocol (LISP).
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)IC273.13, 15.3(3)XB12, 15.4(0.19)S0.8, 15.4(1)CG1, 15.4(1)S, 15.4(1)S0.2, 15.4(1)S0e, 15.4(1)T1, 15.4(1.0)CG1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj11301 | Title: | ASR1K SBC SNMP queries not blocked on Standby-RP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Standby SBC ASR1k seeing "SNMP-3-INPUT_QFULL_ERR". SNMP input queue never drops, it continues to increase until it gets stuck at 1000, causing SNMP unresponsiveness to the device.
Conditions:
When polling ciscoSbcCallStatsMIB on Standby-RP ASR1k
Workaround:
"default snmp-server" to soft reset the SNMP Engine to make the ASR1K respond again (refresh the input queue); then apply SNMPVIEW configuration to block the MIB.
E.g.
********************************************
snmp-server view cutdown iso included
snmp-server view cutdown ciscoSbcCallStatsMIB excluded
snmp-server community view cutdown RO
snmp-server community view cutdown RW
********************************************
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.2(4)S1 |
|
Known Fixed Releases: * | 15.2(4)S4.4, 15.2(4)S5, 15.2(4)S6, 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 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj73843 | Title: | ASR1K:IOSd crashes @ bfd_interface_command on configuring bfd template |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IOSd crashes @ bfd_interface_command
Conditions:
While configuring bfd template command on Gigabitethernet subinterface and when there are 32 characters or more for a template name.
Workaround:
-
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 15.2(2)E, 15.2(2)E1, 15.2(2.2.70)ST, 15.2(2a)E1, 15.2(2b)E, 15.2(3)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.4(1.8)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh53255 | Title: | [XE310] after session refresh, no media issue encountered |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
no media issue is encountered.
Conditions:
By default, without "asymmetric payload full" configured, there will be no end-to-end PT negotiated.
CUBE should do payload type interworking at RTP level.
But right now, CUBE does not behave correctly, no media issue is encountered.
Workaround:
configure "asymmetric payload full" under voice service voip -> sip
More Info:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.4(1.3)T, 15.4(1.4)T, 15.4(1.8)S, 15.4(1.9.1)XEB, 15.4(2)CG, 15.4(2)S, 15.4(2)S1, 15.4(2)S2, 15.4(2)SN, 15.4(2)SN1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul04900 | Title: | crash@__be_strcmp for hydrogen serviceability Feature |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Hydrogen servicability Feature crash in Xe 311 image
As per crash decode snippet, serviceability/event trace code got crashed
Traceback summary
-----------------
% 0x8a57439 : __be_strcmp
% 0x1372b17 : __be_sympBuffCallingNumCompare
% 0x89884ce : __be_avl_search
% 0x1373a99 : __be_symp_et_search_cover_buffer_in_filt_table
% 0x1373b99 : __be_symp_et_insert_cover_buffer_to_filt_table
% 0x13754fc : __be_symp_upd_event_trace_instance
% 0x10417a9 : __be_ccsip_api_call_setup_ind
% 0xf555a4 : __be_sipSPIContinueNewMsgInvite
% 0xf54cf8 : __be_sipSPIHandlePostPreauthInvite
% 0xf52a20 : __be_sact_idle_new_message_invite
% 0xf523ad : __be_act_idle_new_message
% 0xf5127a : __be_sipSPISipIncomingMsg
% 0xf4f821 : __be_sipSPILocateInviteDialogCCB
% 0xf4e5b5 : __be_ccsip_new_msg_preprocessor
% 0xf4c55a : __be_ccsip_spi_process_event
% 0xf4bedc : __be_ccsip_process_sipspi_queue_event Call flow : srv_dbg_cat_lvl_03 TC execution.
=================================================
Topology
sipp----ASRCUBE----SIPP
Core file path :/auto/tftp-rts/ASR-CUBE_RP_0_linux_iosd-imag_16315_1382531279.core.gz
Passed image :15.4(0.19)S0.4
failed Image :15.4(0.19)S0.8
Conditions:
1. enabled following event trace commands at common_setup section,
monitor event-trace voip ccsip fsm
monitor event-trace voip ccsip msg
monitor event-trace voip ccsip misc
monitor event-trace voip ccsip api
monitor event-trace voip ccsip global
monitor event-trace voip ccsip limit connections 1000
monitor event-trace voip ccsip stacktrace 8
monitor event-trace voip ccsip history enable"
monitor event-trace voip ccsip history clear"
monitor event-trace voip ccsip all enable"
2. By default all feature codes and log level are enabled at particular TC setup section
3. Single audio call is established, after 4 to 5 sec. crash occurred.
Workaround:
Passed image :15.4(0.19)S0.4
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(0.19)S0.8 |
|
Known Fixed Releases: * | 15.3(3)M1.7, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S1.9, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S2t, 15.3(3)S3, 15.3(3)S4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj88292 | Title: | BFD session are not coming up with XE3.11 mcp dev image |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Once you reboot router with XE3.11 BFD is getting disabled.
Conditions:
BFD session showing down
Workaround:
Remove interface BFD config and reapply it
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 12.2(33)SCI, 15.2(2)E, 15.2(2)E1, 15.2(2)EA1.1, 15.2(2.2.32)EA, 15.2(2.2.70)ST, 15.2(2a)E1, 15.2(2b)E, 15.2(3)E, 15.2(4.0)ST |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj82610 | Title: | Issues with VFI clean up if not un-referenced from bridge-domain |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The VFI deletion referenced under a bridge-domain is not allowed even after deleting the bridge-domain and gives an error as follows. The deletion of bridge-domain successfully deletes the bridge-domain as we cannot see in the running configuration, but why this reference error:
PE1-TKK-AP(config-bdomain)#no l2vpn vfi context CustomerFName_400_401
% VFI removal failed. Please remove references to VFI before removal.
Conditions:
The service instance is deleted.
The pseudowire members are removed from under the VFI context.
The seudowire itself is deleted.
The bridge domain is deleted, hence removing all the references to all components.
Finally the L2VPN VFI context is removed which fails and gives the specific error.
Workaround:
Deleting/removing the VFI referenced under the particular bridge-domain, and then trying to delete the VFI context is a work around for the above error.
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: * | 15.4(1.13)S, 15.4(1.9.2)XEB, 15.4(2)S, 15.4(2)S1, 15.4(2)S2, 15.4(2)SN, 15.4(2)SN1, 15.4(2.1.1)S, 15.4(3)S, 15.4(3)S1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo96996 | Title: | CENT:traffic-class BW 0 due to duplicated records in one export interval |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
traffic-class BW used is 0 because of duplicated records in one export interval
Conditions:
this issue happens when the traffic is big ,like 10Mbps
Workaround:
NA
Further Problem Description:
NA
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(3)M, 15.4(3)S, 15.5(1)S |
|
Known Fixed Releases: * | 15.4(2.17)S0.9, 15.4(2.20)M0.7, 15.4(3)M, 15.4(3)M1, 15.4(3)S, 15.4(3)S1, 15.4(3)SN1a, 15.5(0.11)S, 15.5(0.8)T, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul38819 | Title: | ASR1K crash due to PfR |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A Cisco router acting as a PfR master or border may unexpectedly reloads, when TCP connection between PfR master and border is broken or shut down during sending or receiving many packets.
Conditions:
The problem occurs, when a PfR master is controlling a large number of Traffic Classes (TC), and when a master router or a border router is sending a large number of packets to another router, "shut down" command is executed or a link between them is down.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(2)S1 |
|
Known Fixed Releases: * | 15.3(3)M2.4, 15.3(3)M3, 15.3(3)M4, 15.3(3)S3.4, 15.3(3)S4, 15.4(1)T1.2, 15.4(1)T2, 15.4(1)T3, 15.4(1.16)S0.12, 15.4(2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun05121 | Title: | Memory leak at SRTP Keys in Dolby Feature. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Memory leak at SRTP Keys in Dolby Feature.
Conditions:
Memory leak seen in SRTP Call
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(2.5)S |
|
Known Fixed Releases: * | 15.3(3)M3, 15.3(3)M4, 15.3(3)S3.2, 15.3(3)S4, 15.4(1)S2.2, 15.4(1)S3, 15.4(1)T1.2, 15.4(1)T2, 15.4(1)T3, 15.4(2.1.2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun56044 | Title: | "snmp-server enable traps sbc adj-status" on ASR generates extra trap |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When there is a small network flap, ASR sends below traps to the Monitoring tool.
1. When the adjacency goes down;
13.2.2014 04:25:08.430 CISCO-SESS-BORDER-CTRLR-EVENT-MIB Enterprise specific=3 enterprises.cisco.ciscoMgmt.ciscoSessBorderCtrlrEventMIB 47 csbAlarmSubsystem=signaling csbAlarmSeverity=0 csbAlarmID=47 csbAlarmTime=Thu Feb 13 02:25:08 UTC 2014 csbSBCServiceName=lah1-sbc1 csbAdjacencyState=detached csbAdjacencyType=sip csbAdjacencyName=Savonvoima-Lync csbAlarmDescription=This alarm is generated when an adjacency is attached to or detached from the sbe.
2. When it comes back;
13.2.2014 04:28:38.126 CISCO-SESS-BORDER-CTRLR-EVENT-MIB Enterprise specific=3 enterprises.cisco.ciscoMgmt.ciscoSessBorderCtrlrEventMIB 48 csbAlarmSubsystem=signaling csbAlarmSeverity=cleared csbAlarmID=48 csbAlarmTime=Thu Feb 13 02:28:37 UTC 2014 csbSBCServiceName=lah1-sbc1 csbAdjacencyState=attached csbAdjacencyType=sip csbAdjacencyName=Savonvoima-Lync csbAlarmDescription=This alarm is generated when an adjacency is attached to or detached from the sbe.
3.
13.2.2014 04:28:38.376 CISCO-SESS-BORDER-CTRLR-EVENT-MIB Enterprise specific=3 enterprises.cisco.ciscoMgmt.ciscoSessBorderCtrlrEventMIB 49 csbAlarmSubsystem=signaling csbAlarmSeverity=0 csbAlarmID=49 csbAlarmTime=Thu Feb 13 02:28:37 UTC 2014 csbSBCServiceName=lah1-sbc1 csbAdjacencyState=attached csbAdjacencyType=sip csbAdjacencyName=Savonvoima-Lync csbAlarmDescription=This alarm is generated when an adjacency is attached to or detached from the sbe.
Conditions:
ASR Version: asr1000rp1-adventerprisek9.03.11.00.S.154-1.S-std.bin
"snmp-server enable traps sbc adj-status" is added in the ASR configuration.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: * | 15.3(3)S2.9, 15.3(3)S3, 15.3(3)S4, 15.4(1)S2, 15.4(1)S3, 15.4(2)S0.2, 15.4(2)S1, 15.4(2)S2, 15.4(2.1.2)S, 15.4(2.15)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun85284 | Title: | XE3.12 DPSS issues with incompatible actions |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Some ONEP datapath flow action combinations that do not make logical sense are not blocked.
Conditions:
Using the Datapath service set for ONEP and applying flow action combinations (like QoS and drop flow) are not blocked.
Workaround:
Flow actions are applied to the flow in the order that the APIs are called.
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 15.2(1)IC273.41, 15.2(1)ICA4.30, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.4(2)S0.6, 15.4(2)S1, 15.4(2)T1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun43663 | Title: | HA: Multiple switchovers causes onePK process to hang |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After HA switchover, before the application session transitions to Connected state (that is, no reconnect yet), if user does "no onep", then it takes 5 minutes for the onep network element thread to exit. During this 5 minutes period, no new onep sessions can be established.
After this 5 minutes period, new onep sessions can be established again.
Conditions:
After HA switchover, before the application session transitions to Connected state (that is, no reconnect yet), and user does "no onep".
Workaround:
avoid doing "no onep" in the above condition.
one workaround is to do "onep stop session all" first, and then do "no onep".
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.2(1)IC273.37, 15.2(3)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.4(2)S0.6, 15.4(2)S1, 15.4(2)T1, 15.4(2)T1.1, 15.4(2.1.2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv90904 | Title: | ASR1K B2B CGN NAT lost sync in standby IP NAT allocated addresses |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In a Back-to-Back Carrier Grade NAT configuration using ASR1013 chassis and PAP+BPA configured, ESP200 lost sync in standby in NAT entries & IP NAT allocated addresses.
Conditions:
PAP+BPA configured ASR1013 with ESP200 B2B CGN NAT
Workaround:
Redundancy fail over to corrected the issue.Once the standby CGN became active, the IP allocated addresses would be corrected.
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 16.2(0.197) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup25530 | Title: | MC crash and active-probe stuck |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
we keep receiving the following errors. During this test, the MC had learned about 5800 Traffic Classes but only around 900 were able to get INPOLICY. It seems whatever change was made to stop freeing the TC structre may be filling up the memory. These errors don't cause the MC to crash but it is unable to control any more TCs beyond the 900 or so it first learns. I can get more info with this IOS if you need me to.
Mar 31 17:44:41.400: PFR_MC-3-INTERNAL_ERROR oer_dbs_update_act_prefix_perf_hist_rec:Insufficient memory and failed to add active performance history record.
LANT_MC_1#
Mar 31 17:44:41.400: PFR_MC-3-INTERNAL_ERROR oer_dbs_update_act_prefix_perf_hist_rec:Insufficient memory and failed to add active performance history record.
LANT_MC_1#
Mar 31 17:44:58.451: SYS-2-MALLOCFAIL Memory allocation of 65540 bytes failed from 0x4408CD6, alignment 8
Pool: Processor Free: 2666992 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
-Process= "OER Master Controller", ipl= 0, pid= 575
-Traceback= 1#5eca09de9be4e6b6aa886725677b75c7 :400000+3FFE8A7 :400000+3FFA35D :400000+3FF513A :400000+4008CD6 :400000+2D8882C :400000+2D85DEE :400000+2D7EBB2
:400000+2D7E8BA :400000+2D81F90 :400000+2E2DF3F :400000+2E2E438 :400000+2E2F657 :400000+3FCA5B3 :400000+3FCA4C8 :400000+2D5B5B0
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(2.11)S |
|
Known Fixed Releases: * | 15.3(3)M3.2, 15.3(3)M4, 15.3(3)S3.4, 15.3(3)S4, 15.4(1)T2.2, 15.4(1)T3, 15.4(2.17)S0.9, 15.4(2.20)M0.6, 15.4(3)M, 15.4(3)M1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw81487 | Title: | Kahuna RP crash when bringing up PTA sessions with QoS |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Kahuna RP crash when bringing up PTA sessions with QoS.
Conditions:
Egress queues are configured on PPP sessions. This only happens on Kahuna (ASR1002-HX) platform.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.6(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup18179 | Title: | Failed to find any TCA mrv raise and mrv clearr from show logging output |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
While verifying MMA flow monitor with threshold crossing alerts for mrv and collecting traffic, TCA mrv raise and TCA mrv clear is not seen in the output of show logging.
Conditions:
These are the conditions for this scenario :
1) Configure default TCP flow monitoring with threshold-crossing alerts on UUT.
2) Configure traffic stream and packet capture on Pagent with tca_mrv option.
3) Start sending traffic from Pagent to UUT.
4) Check in the output of show logging weather TCA mrv raise and TCA mrv clear is present.
Workaround:
Refer symptoms
Further Problem Description:
Refer Summary
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)M0.3, 15.4(3)M1, 15.4(3)S0.2, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a, 15.5(0.16)T, 15.5(0.16.1)CG, 15.5(0.17)S, 15.5(0.20)PI27a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw21897 | Title: | Traceback seen with ip cef accounting |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Cisco IOS-XE router may show an error message in the logs:
%CPPOSLIB-3-ERROR_NOTIFY: F0: fman_fp_image: fman-fp encountered an error
Conditions:
This issue can be seen when 'ip cef accouting' is configured with fast reroute when a routing protocol flaps.
Workaround:
Disable the function if possible - 'no ip cef accouting'
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S2.1 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S2, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.180), 16.2(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul46066 | Title: | Hung Calls with SIP SPI with Refer Consume Load |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Hung Calls with SIP SPI with Refer Consume Load
Conditions:
Steps to reproduce:
1. Configure max connection with 3 Refer to Dial-peer & outbound dial-peer towards CVP.
2. Run Load with 1000 calls for few hours.
CPS: 10
CHT: 100 secs
Total Number of active calls : 750
Issue observed with max-conn with multiple dial-peers
Workaround:
Use dial-peers without max-conn
Further Problem Description:
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.3(3)M3.2, 15.3(3)M4, 15.3(3)S3.4, 15.3(3)S4, 15.4(2.17)S0.6, 15.4(2.18)T, 15.4(3)S, 15.5(0.1)T, 15.5(0.8)S, 15.5(1.2.1a)GB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv56569 | Title: | incorrect QoS policy on target blocks all subseuqent policies |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In case an invalid QoS policy with explicit queue-limit (asking for more bandwidth via percent based LLQ or Explicit Bandwidth then is available) is applied on target, there might be issue with cleaning up after rejecting the configuration.
Error causes any further installation of QoS policy to fail on the given target. At this point, reload is necessary to clean-up issue.
Conditions:
User applies an invalid QoS policy, with explicit queue-limit and percent base LLQ (priority, priority + police) or percent based Bandwidth.
Workaround:
Do not apply policy with invalid bandwidth reservation.
Problem is not seen with kbps based policy.
Further Problem Description:
|
|
Last Modified: | 06-FEB-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.5(3)S1.7, 15.6(0.21)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy44786 | Title: | Meet crypto recommendations in IKEv2 defaults |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptoms:
This is a modification on the product to adopt new secure code best practices to enhance the security posture and resiliency of the product.
Conditions:
Device configured with default configuration.
Workaround:
Not applicable or available.
Further Problem Description:
This issue was found during an internal security audit of the product. This issue should not be made public as it is an internal hardening issue
to be considered for integration.
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 0/0:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:N/AC:L/Au:N/C:N/I:N/A:N/E:F/RL:U/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: | 29-FEB-2016 |
|
Known Affected Releases: | 16.0(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuf21704 | Title: | GEC QoS: Support HQoS on GEC main interface. |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Enable GEC QoS support for XE platform.
Conditions:
Enable GEC QoS support for XE platform.
Workaround:
feature commit.
More Info:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: * | 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(2.21)PI23c, 15.4(0.1)T, 15.4(0.5)S, 15.4(1)S, 15.6(1)SN |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur59667 | Title: | Cannot delete debug platform condition if ACL is used |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
ACL based conditional platform debugging cannot be disabled
Conditions:
Workaround:
use "clear platform condition all" which will clear all the conditions
Further Problem Description:
|
|
Last Modified: | 04-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S0.12 |
|
Known Fixed Releases: * | 15.5(2.17)S, 15.5(3)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun61219 | Title: | [AVC]Service policy stays in suspended mode on port-channel subinterface |
|
Status: | Other |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Performance monitor configured on Port-channel sub-interface stayed in suspended mode, which is not required for any perf-mon at all, as vad been accepted on the attached thread in enclosures.
Conditions:
Performance monitor configured on Port-channel sub-interface
Workaround:
none
Further Problem Description:
none
|
|
Last Modified: | 05-FEB-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.2(1)IC273.103, 15.2(2)DB101.101, 15.2(2)DB101.112, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.4(3)S0.4, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCui82625 | Title: | ASR1K / Remove OSPFV3 authentication CLI from unsupported versions |
|
Status: | Terminated |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
ASR1K unable to maintain an authenticated OSPFv3 neighbourship
Conditions:
Peering with a neighbour with OSPFv3 ipsec authentication turned on
Workaround:
Disable ipsec authentication for OSPFv3
Further Problem Description:
At the time of this writing OSPFv3 authentication is not supported on ASR1K platform. This DDTS is opened to disable the CLI on unsupported versions of ASR1K
|
|
Last Modified: | 25-FEB-2016 |
|
Known Affected Releases: | 15.2(3)S, 15.2(4)S, 15.3(2)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu56904 | Title: | ASR1K cannot output messages about stby harddisk/bootflash failure |
|
Status: * | Fixed |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
ASR1006 does not generate any syslog messages when Standby RP lost harddisk or bootflash.
Conditions:
Whenever Standby RP lost harddisk or bootflash
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 29-FEB-2016 |
|
Known Affected Releases: | 12.2(33)XNF2 |
|
Known Fixed Releases: | |
|
|
| |
:
没有评论:
发表评论