| |
|
Alert Type: | Updated * |
Bug Id: | CSCte89787 | Title: | Segment Switch manager Error followed by crash at 'sw_mgr_sm_cm_send_msg |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: A Cisco ASR 1000 crashes after the Segment Switch Manager (SSM)
reports that an invalid segment has been detected:
%SW_MGR-3-INVALID_SEGMENT: Segment Switch Manager Error - Invalid segment - no
segment class.
The crash follows this message.
Conditions: The symptom is observed on a Cisco ASR 1002 that is running Cisco
IOS Release 12.2(33)XND1. The crash is caused by a NULL pointer de-reference
following the "no segment class" error. The error itself is not fatal and the
crash should have been avoided.
Workaround: There is no workaround.
|
|
Last Modified: | 02-APR-2016 |
|
Known Affected Releases: | 12.2(33)XND |
|
Known Fixed Releases: * | 12.2(32.8.11)SX349, 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 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtb01505 | Title: | Router crashes with ospf_build_net_lsa |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: A Cisco router may crash when building an OSPF Network LSA.
Conditions: This symptom is observed while unconfiguring ospf configurations.
Workaround: There is no workaround.
|
|
Last Modified: | 02-APR-2016 |
|
Known Affected Releases: | 12.2(33)SXH, 12.2(33)XND, 15.0(1)M |
|
Known Fixed Releases: * | 12.2(32.8.11)SX300, 12.2(32.8.11)XJC273.18, 12.2(32.8.29)REC186, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE12, 12.2(33)SRE13, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsv73721 | Title: | ISSU ERP tracebacks on active RP during router bootup |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: The following tracebacks appeared on the active RP console during router boot up:
000131: *Nov 12 16:16:43.075 EST: %ISSU-3-FAILED_TO_ALLOC_UNDER_ENDPOINT: Can not allocate
transport id(131072) control block.
-Traceback= 1#04182c093c3bf3fa21a9ef089770e5a6 :10000000+5179E0 :10000000+518294
:10000000+515F3C :10000000+200F5DC :10000000+200E5C4 :10000000+1F78A0C
000132: *Nov 12 16:16:43.077 EST: %ISSU-3-ERP_CLIENT: For context ID 131072, Current context
for ERP isn't available
-Traceback= 1#04182c093c3bf3fa21a9ef089770e5a6 :10000000+5179E0 :10000000+518294
:10000000+515F3C :10000000+200E898 :10000000+1F78A0C
000133: *Nov 12 16:16:43.078 EST: %IPC-3-ISSU_ERROR: ISSU register peer failed failed with error
code 0 for seat 20000
-Traceback= 1#04182c093c3bf3fa21a9ef089770e5a6 :10000000+5179E0 :10000000+518294
:10000000+515F3C :10000000+1F78D5C
Conditions: The symptom will show up at boot up if the box has more than 10 ISSU endpoints.
ISSU aware RP, SP, linecards all count as endpoints.
Workaround: There is no workaround.
|
|
Last Modified: | 03-APR-2016 |
|
Known Affected Releases: | 12.2(33)XN, 12.2(33)ZZ |
|
Known Fixed Releases: * | 12.2(32.8.10)REC154, 12.2(32.8.11)REC154, 12.2(32.8.11)SX227, 12.2(32.8.12)REE154, 12.2(32.8.9)YCA206.8, 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsm82551 | Title: | MCP hit watchdog in diff processes as Pool Mgr, CDP while booting |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: |
Symptom:
You may see ASR1000-WATCHDOG: Process = IP Background followed by
Traceback message during system bootup.
Conditions:
This happens when L2VPN is configured. It may be likely to occurr when
many interfaces are configured.
Workaround:
There is no known workaround available.
|
|
Last Modified: | 03-APR-2016 |
|
Known Affected Releases: | 12.2XN |
|
Known Fixed Releases: * | 12.2(32.8.1)REE177, 12.2(32.8.10)REC154, 12.2(32.8.11)YCA246.10, 12.2(32.8.12)REE154, 12.2(32.8.3)YCA206.8, 12.2(33)XNB, 12.2(33)XND, 12.4(21.14.14)PIC1, 15.0(1)SY, 15.1(1)SG1.3 |
|
|
| |
| |
|
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: | 03-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.1(0.1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsx32049 | Title: | CC: ESM logger cause tracebacks and RP reload at boot |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptoms: Traceback is observed and the system may reboot, depending on the
platform.
Conditions: The symptom is observed when the ESM filter is configured and
contains an ios_config statement.
Workaround: Remove ios_config statements from ESM filter.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 12.2XN, 3.4 |
|
Known Fixed Releases: * | 12.2(32.8.10)REC186, 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)XND, 12.2(33)XNE |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv25212 | Title: | ucode crashes with Fair Queue and FNF export is configured |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ucode crashes when there is a dropped packet with Fair Queue and FNF export is configured
Conditions:
ucode crashes when there is a dropped packet with Fair Queue and FNF export is configured
Workaround:
Either remove Fair Queue configuration or FNF export, until there is an image available with a fix
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.3(3)S7, 15.4(3)S4, 15.5(1)S3, 15.5(2)S2, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.170) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.3(3)S7, 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: | CSCuv02537 | Title: | ASR1K ESP200 reload in a B2B CGN NAT scenario with PAP+BPA |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The ESP may reload in an ASR1000 chassis.
Conditions:
This has been seen when Carrier Grade NAT (CGN) and B2B redundancy are deployed.
Workaround:
There is no workaround.
Further Problem Description:
NA
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S, 15.4(2)S1 |
|
Known Fixed Releases: * | 15.3(3)S7, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.194) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv52648 | Title: | ESP memory leak under cpp_cp_svr due to BFD feature |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR1K ESP memory leak:
From "show platform software status control-proc brief":
we see ESP memory utilization(committed field) is going up over time:
Memory (kB)
Slot Status Total Used (Pct) Free (Pct) Committed (Pct)
RP0 Healthy 3874504 1769324 (46%) 2105180 (54%) 2414216 (62%)
ESP0 Healthy 969088 897480 (93%) 71608 ( 7%) 680672 (70%) <<<
SIP0 Healthy 471832 268616 (57%) 203216 (43%) 235364 (50%)
From "show platform software process list f0 sort mem" we see cpp_cp_svr holding more and more memory over time
From a breakdown view, from "show platform software memory qfp-control-process qfp active brief"
we see the leak is under the following chunk:
CPP AEM SUB-TASK CHUNK
CPP AEM TASK CHUNK
CPP HASH CHUNK
Conditions:
The leak is seen when BFD feature is enabled.
Workaround:
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S3.1 |
|
Known Fixed Releases: * | 15.3(3)S7, 15.4(3)S4, 15.5(1)S3, 15.5(2)S2, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.170) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtz61014 | Title: | f Linux kernel NTP leap second handling could cause deadlock |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
There are periodic leap second events which can add or delete a second to global time.
When the leap second update occurs the system will crash when adding or deleting NTP leap second in NTP
master mode.
Conditions:
The leap second update will be propagated via Network Time Protocol (NTP) or via manually setting the clock.
Workaround:
To prevent an issue when the leap second update is received do not configure the system as NTP master.
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.0(1)S |
|
Known Fixed Releases: * | 15.1(3)S4, 15.2(2)S1, 15.2(4)S8, 15.3(3)S7, 15.4(2)S4, 15.4(3)S4, 15.5(1)S3, 15.5(2)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv57459 | Title: | ASR1K Kernel crash at pidns_get() - part 2 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR1K kernel crash
Conditions:
This has been seen on ASR1K running 3.10.2 code.
Workaround:
Not known
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S2 |
|
Known Fixed Releases: * | 15.2(4)S8, 15.3(3)S7, 15.4(2)S4, 15.4(3)S4, 15.5(1)S3, 15.5(2)S2, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S3.1 |
|
Known Fixed Releases: * | 15.3(3)S7, 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 16.2(0.260), 16.3(0.57) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux52451 | Title: | VRF Domain half open counter increments when aggressive aging occurs |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
VRF domain level half open counters (current count) continue to increment.
This may eventually result in the denial of flow creation.
# show platform hardware qfp active feature firewall runtime
VRF Global Action Block
L7 Inspection disable flags: 0x0
Total Sessions:
max limit: 4294967295, current count: 0, exceed: 0
aggr-age high watermark: 4294967295, low watermark: 0
num of times enter aggr-age: 0, aggr-age period: off
TCP SYN Cookie:
max limit: 4294967295, current count: 0, exceed: 0
Total Half Open Sessions:
max limit: 200000, current count: 0, exceed: 0
aggr-age high watermark: 150000, low watermark: 100000
num of times enter aggr-age: 0, aggr-age period: off
TCP Half Open Sessions:
max limit: 250000, current count: 0, exceed: 0
UDP Half Open Sessions:
max limit: 50000, current count: 0, exceed: 0
ICMP Half Open Sessions:
max limit: 1000, current count: 0, exceed: 0
or
# platform hardware qfp active feature firewall datapath vrf
VRF:(id=)
VRF Action Block
L7 Inspection disable flags: 0x0
Total Sessions:
max limit: 4294967295, current count: 0, exceed: 0
aggr-age high watermark: 4294967295, low watermark: 0
num of times enter aggr-age: 0, aggr-age period: off
TCP SYN Cookie:
max limit: 4294967295, current count: 0, exceed: 0
Total Half Open Sessions:
max limit: 200000, current count: 0, exceed: 0
aggr-age high watermark: 150000, low watermark: 100000
num of times enter aggr-age: 0, aggr-age period: off
TCP Half Open Sessions:
max limit: 250000, current count: 0, exceed: 0
UDP Half Open Sessions:
max limit: 50000, current count: 0, exceed: 0
ICMP Half Open Sessions:
max limit: 1000, current count: 0, exceed: 0
Conditions:
The parameter maps use a default session rate parameters that may cause the aggressive
aging to kick in without being configured. Setting the session rate in the parameter map may
exacerbate the issue.
Workaround:
Set the session rate to a very high value
Further Problem Description:
None.
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via normal resolution channels.
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another evaluation.
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S5.1 |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.226), 16.3(0.2) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.257), 16.3(0.52) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw47720 | Title: | ASR1001-X/ISR4k Mgmt port negotation issue with peer device |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
When no shutdown ASR1001-X/ISR4k 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
ISR4k series also are affected by this defect.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.2(0.271), 16.3(0.71) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)SS |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.213) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.193) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.261), 16.3(0.57) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.6(2)S |
|
Known Fixed Releases: * | 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux40633 | Title: | ISR 4451 Continuous Crash/ Core Crash File generated with WAAS/Appnav |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Crash might be seen when WAAS/AppNav enabled ISR-4451; is configured with HSRP.
Conditions:
Currently crash is seen while adding HSRP configuration; when WAAS/AppNav is running in ISR-4451.
Workaround:
Removing the WAAS/AppNav with HSRP still running; has solved the issue.
Further Problem Description:
Crash is seen in Branch ISR-4451 while HSRP is configured; when already WAAS/AppNav is running.
As a first step; WAAS/AppNav was removed then issues seems to have stopped.
Issue not reproduced after re-adding the WAAS/AppNav back.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.5(3)S1.4 |
|
Known Fixed Releases: * | 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.255), 16.3(0.48) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.3(3)S7, 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S, 16.2(0.67) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw73223 | Title: | Polaris : cpp_cp_svr crash when the interface goes down |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR1001X, ASR1002X and ASR1Ks equipped with ESP100 or ESP200 crashes.
Conditions:
When ATM VC w/ QoS policy map is deleted and there are no other VCs configured on the COS node for the VC being deleted.
Workaround:
None
Further Problem Description:
Anything that triggers the deletion of VC that has policy map attached causes ESP (FP) to crash if this is the only VC currently on the COS node.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.2(0.211) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux14860 | Title: | ASR1K:Packet Tracing failed with FW,NAT&FW enabled. |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Packet Tracing causes the system to crash.
Conditions:
when FW feature is enabled.
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.6(1)S, 16.2(0) |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.2(0.201) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy57879 | Title: | 6XGE-BUILT-IN module crashed in ASR1002-X router |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
6XGE-BUILT-IN module crashes in ASR1002-X router, when the below command is executed from the IPC console mode:
sh hw-module subslot 0 drops-rx mac 0
Conditions:
When bad crc packets are pushed to one of the Gig interface belonging to this module "6XGE-BUILT-IN" then it causes the increment in Input error or CRC counters. And once the counter is increasing then executing the below command causes the crash in this module 6XGE-BUILT-IN.
ROLO#ipc-con 0 0
Slot-0-0>
Slot-0-0>en
Slot-0-0#sh hw-module subslot 0 drops-rx mac 0
This issue is seen to 6XGE-BUILT-IN and SPA-2X1GE-SYNCE, which uses the same Tempo FPGA
SPA-2X1GE-SYNCE supporting routers:
7600 and ASR1k
6XGE-BUILT-IN supporting router:
ASR1002-X
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 15.4(3)S3.1 |
|
Known Fixed Releases: * | 15.4(3)S5.3, 15.5(3)S2.4, 15.6(0.22)S2, 16.3(0.121) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy20489 | Title: | ASR experiences ucode crashes on 15.6(1)S due to sipvicious |
|
Status: | Terminated |
|
Severity: | 2 Severe |
Description: * | Symptom:
ASR experiences ucode core crashes.
Conditions:
The issue is suspected to be caused by L2 multicast code with BDI interface and NAT. NAT is not a supported feature listed in the BDI configuration guide.
http://www.cisco.com/c/en/us/td/docs/routers/asr1000/configuration/guide/chassis/asrswcfg/bdi.html
Workaround:
Configure BDI as subinterfaces if possible. NAT is not supported on BDI.
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux41920 | Title: | PAP issue in B2B A/R setup |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
false pool exhaustion
Conditions:
with pap in a/r scenario
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 06-APR-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: | CSCuy61296 | Title: | polaris: 16.2 throttle: Memory leaks @ IsVoiceHuntGrpSIPLocalDN |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Memory leaks are seen at IsVoiceHuntGrpSIPLocalDN at the end of dynamo2 call parking script execution.
Conditions:
After hunt group is configured if CLI "no voice register global"
is executed, only dynamically joined voice hunt group members were deleted.
Statically tied voice hunt group DNs were not deleted.
Workaround:
In config_voice_register_global , before calling remove_voice_reg_dn_tag to remove all the existing DNs.
setting vhg_info->ties_voice_huntgrp to 0, so that DN will be deleted.
Further Problem Description:
|
|
Last Modified: | 11-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.6(2.7)T, 16.3(0.161) |
|
|
| |
| |
|
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: | 19-APR-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S1.4, 15.5(3)S2, 15.6(0.22)S0.15, 15.6(1.17)S0.10, 15.6(1.19)SP, 15.6(2)S, 15.6(2.8)T, 16.2(0.195) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun13772 | Title: | NHRP: CPUHOGs seen when many child entries expire simultaneously |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
CPUHOG messages and watchdog timeout crashes are observed on an ASR1000 series router running DMVPN.
Conditions:
This has been observed on a router with a very large NHRP table (10-20k individual entries) with a very high number (thousands) of child entries per parent entry.
Workaround:
Reduce the number of child entries per parent entry through the use of supernetting.
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 15.2(4)S1 |
|
Known Fixed Releases: * | 15.2(1)SY1.13, 15.2(1)SY2, 15.2(4.0)ST, 15.2(4.0.21)E, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(1)IE101.170, 15.3(3)M4.1, 15.3(3)M5, 15.3(3)S4.10 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun25912 | Title: | IKEv2 auto-reconnect: some virtual-access dynamic configs are lost |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Configurations dynamically applied to the virtual-access interface might be lost over the reconnection while using the autoreconnect feature on Cisco Anyconnect on the ASR platform.
For example, the interface after initial connection establishment would have a QOS service policy applied:
ROUTER#sh derived-config int virtual-access 1
!
interface Virtual-Access1
ip unnumbered GigabitEthernet0/0/1
tunnel source 10.1.1.1
tunnel mode ipsec ipv4
tunnel destination 10.10.1.100
tunnel protection ipsec profile ipsec-profile
no tunnel protection ipsec initiate
service-policy input INPUT-POLICY
end
After reconnection the INPUT-POLICY is missing:
ROUTER#sh derived-config int virtual-access 1
!
interface Virtual-Access1
ip unnumbered GigabitEthernet0/0/1
tunnel source 10.1.1.1
tunnel mode ipsec ipv4
tunnel destination 10.10.1.100
tunnel protection ipsec profile ipsec-profile
no tunnel protection ipsec initiate
end
Conditions: This symptom is observed with configurations being applied from the user AAA profile over radius authentication. Affected parameters observed are QOS service policies and access-group.
Workaround: 1. Do not use the reconnect feature.
or
2. Apply the configurations directly to the virtual-template (if this is an option).
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 15.4(1)S |
|
Known Fixed Releases: * | 15.2(1)SY1.13, 15.2(1)SY2, 15.2(4.0)ST, 15.2(4.0.21)E, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(1)IE101.209, 15.4(1)IA1.1, 15.4(1)S1.8, 15.4(1)S2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq86382 | Title: | FLEXVPN IKEv2 auto reconnect | virtual-access | VRF lost | anyconnect |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR/FLEXVPN
ANYCONNECT
Conditions:
On client side, AnyConnect is used. Pings are sent in the VPN during all the tests.
The reconnect feature is activated with timeout = 600
An outage is simulated by blackholing the trafic on an intermediate router: the source IP and the destination IP are sent to null 0. When doing this, the client starts the reconnect process and the PE brings the Virtual-Access interface after a short period.
If the connectivity is restored before the Vi interface goes down, the reconnect feature works fine.
If the connectivity is restored after the Vi interface goes down, the client reconnects but something is broken in the installation of the route into the VRF. As a result, the VPN is up but the client connectivity is still down.
Workaround:
NONE
Further Problem Description:
NONE
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.2(1)SY1.13, 15.2(1)SY2, 15.2(4.0)ST, 15.2(4.0.21)E, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(1)IE101.209, 15.4(1)IA1.1, 15.4(3)M0.3, 15.4(3)M1 |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz13399 | Title: | ISSU XE316 ->XE317: ATMoMPLS ip ping failed CEoP link for port mode conf |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ATMoMPLS with Port Mode configured via CEoP link failed end to end ping after ISSU upgrade of active RP (switchover) from XE3.16 to XE3.17
Conditions:
Only happens in sub-package upgrade.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 15.5(3)S2.7 |
|
Known Fixed Releases: | 15.5(3)S2.9, 15.6(0.22)S4, 16.4(0.1) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux32911 | Title: | 2KP: Router crash at ptpd_mcp_rp while removing PTP clock config |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Crash at ptpd_mcp_rp on ASR1002-X with Multiple config/unconfig events
Conditions:
Multiple config/unconfig events continuously without delay
Workaround:
None.
Further Problem Description:
Issue seen consistently with script. Manual repro is difficult.
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 16.3(0) |
|
Known Fixed Releases: | 16.3(0.182) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCud37408 | Title: * | PerfMon entries not idle timing out |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
Flows in performance-history are not aged out under certain conditions. Which eventually leads to high memory usage. Also this leads to the perfmon flows not getting updated since the old flows still arent aged out.
Conditions:
When sum of counters from all history buckets overflow. For example, if byte count is 4,000,000,000 in one bucket and 3,000,000,000 in another bucket then sum of bytes across all buckets overflows. When that happens flows are not aged out.
Workaround:
Use the history size of 1 if the problem is observed. In case the perfmon data is not seen on the collector side, then removing and applying the performance monitor will resolve the issue temporarily.
Further Problem Description:
Issue is also seen on 3850 series of switches running on release upto 3.6.4.
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 15.3(99)S |
|
Known Fixed Releases: | 15.3(2.14)S, 15.3(2.15.1)XEB, 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: | New |
Bug Id: | CSCuz39721 | Title: | ASR1K/RP2/SW 15.4(3)S4 crash |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Router crash
Conditions:
Upgrade from 15.1(3)S3 to 15.4(3)S4
ASR1K/RP2 configured as BRAS (L2TP sessions)
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 28-APR-2016 |
|
Known Affected Releases: | 15.5(2)S, 15.5(3)S0.18 |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.371), 16.3(0.6) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz10855 | Title: | ASR1002x crash in crypto_pstate_dequeueue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
ASR1002x could crash in CPP because of a issue with packet processing in crypto engine.
Conditions:
ASRs with Octeon processor
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: * | 16.3(0.192), 16.4(0.7) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy64412 | Title: | ISSU:Polaris 16.2 ISO1->ISO2:Traceback@lisp_os_ios_if_handle after RV |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:Error message
%LISP-4-ASSERT: Internal LISP error (os ios if 673)
and a traceback may be seen in the syslog of router running Cisco IOS.
Conditions:LISP is enabled in the configuration.
Workaround:No actions is necessary, router automatically recovers from the error condition.
More Info:Up until now the problem was seen only on redundant systems at the time whem Standby RP becomes Active. But the problem is not specific to this situation and may be seen in other scenarios such as interface OIR or removing an interface from router's configuration.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.4(1)IA1.31, 15.4(1)IA1.35, 15.6(1.17)S0.21, 16.2(0.363), 16.3(0.178) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsx73290 | Title: | Rework CSCsu73842 - RP2 ERROR: no error set by session Trbk@l2tp_avp_pro |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
Symptom:
Traceback seen on configuring tunnel and session establishment
Conditions:
This symptom is observed on a Cisco ASR1000 router with RP2 processor
Workaround:
No Workaround
|
|
Last Modified: | 02-APR-2016 |
|
Known Affected Releases: | 12.2XN |
|
Known Fixed Releases: * | 12.2(32.8.1)REC186, 12.2(32.8.11)XJC206.42, 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)SXI10 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz03703 | Title: | EPA-10x10GE: interface CRC errors are seen |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
EPA-10X10GE could exhibit intermittent CRC errors
Conditions:
Issue is seen with 16.2.1 Release at very high or very low temperatures.
Workaround:
No workaround.
This is fixed in next16.2.2 and 16.3.1 releases
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 16.2(1.3), 16.3(0.153) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsz23139 | Title: | NBAR PD mib is not able to collect details from the Gigi sub-interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | None
Symptom:
NBAR PD mib is not able to collect details from the Gigi sub-interface
Conditions:
While doing getmany on cnpdStatusPdEnable SNMP manager is not able to collect the PD information
from the sub-interface
Workaround:
Further Problem Description:
|
|
Last Modified: | 02-APR-2016 |
|
Known Affected Releases: | 12.2(33)SRD2, 12.2XN |
|
Known Fixed Releases: * | 12.2(32.8.11)REC186, 12.2(33)SRD4, 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)XNE |
|
|
| |
| |
|
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: | 03-APR-2016 |
|
Known Affected Releases: | 15.6(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsr40394 | Title: | Delete small buffer pool causes %ASR1000_INFRA-5-IOS_INTR_OVER_LIMIT TB. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Delete small buffer pool causes %ASR1000_INFRA-5-IOS_INTR_OVER_LIMIT traceback.
Conditions:
When the small buffer pool is configured with a user defined value, a traceback is generated when this buffer pool is deleted. This happens only in ASR routers.
Workaround:
None.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 12.2(33)XN, 12.2(33)XNB1, 12.2(33)XND, 12.2XN |
|
Known Fixed Releases: * | 12.2(32.8.1)REE186, 12.2(32.8.2)REC186, 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)XNC0b |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCsw87700 | Title: | sonetMediumLoopbackConfig returns incorrect values on SPA-1XOC48 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: |
None
Symptom:
when the loop back is configured on POS interface, the
sonetMediumLoopbackConfig doesnt reflect the value set through CLI.
It will populate the correct value only after the reload of SPA.
Conditions:
Workaround:
spa reload
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 12.2XN |
|
Known Fixed Releases: * | 12.2(32.8.7)REC186, 12.2(33)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)XNC1, 12.2(33)XND |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz03040 | Title: | NAT outside add-route randomly even though add-route was not configured |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:Extra /32 host outside-global routes are added for Outside->Inside (ip nat source outside ...) w/o add-route options.
Conditions:
With Overlap NAT configuration, such that "ip nat inside source ..." + "ip nat outside source ..." are used for overlap address ranges.
The /32 static routes created by NAT would point to the "inside" direction, even though it was coming out of "outside-pool" because it use the "outside-global" to follow the routing table ("inside-local"), therefore the return traffic back to outside interface gets forwarded to inside.
Workaround:There is no workaround at this time.
Temporary workaround:
"clear ip nat trans *" will clear those /32 static routes.
Extra effort workaround:
add a physical loop between global and VRF, and then do "inside-outside" with global routing table + "inside-outside" with VRF
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)SS, 15.5(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: * | 15.3(3)S7, 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.2(0.197) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw94014 | Title: | cpp_cp crashes with BB profile #6 48k PTA |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:The CP process may crash when bringing up PPPoE sessions on PTA with hierarchical QoS. When single-queue leaf nodes being are deleted, the software is decrementing the counter in the parent node more than necessary which causes the processing code to skip the hierarchy layer collapse logic.
The problem is specific to the asr1001-x, asr002-x, esp-100 and esp-200 and it causes service outage. This issue is also noticed on cBR8 platform with no PPPoE feature.
Conditions:This issue occurs when bringing up highly scaled PTA sessions with hierarchical QoS. It occurs when there is a combination of add and deletion events of the same object in the same transaction. This issue also occurs on cBR8 with no PPPoE feature.
Workaround:None
More Info:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.6(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.2(0.196) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.3(0.42) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.5(3)S, 16.2(0) |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.271), 16.3(0.46) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S2 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.184) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.180) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S, 16.2(0) |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 16.2(0.166) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw41346 | Title: | ESP packets discarded during re-key with static NAT on ASR1k |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traffic loss through IPSEC tunnels (at the time of Phase-2 rekey). After the re-key, the NatIN2out drop counter is seen to increment on the router performing the ESP NAT:
BGL.I.06-ASR1000-1#sh plat hardware qfp active statistics drop
-------------------------------------------------------------------------
Global Drop Stats Packets Octets
-------------------------------------------------------------------------
NatIn2out 5 670 <<<<<<<<< NatIN2out drops
Conditions:
NAT is implemented in such a way that the Tunnel end points are not aware of it, therefore, NAT-T does not come into picture and the VPN endpoints do not encapsulate ESP into UDP\4500.
Workaround:
Deploy NAT in a way that the tunnel end points detect the NAT in between using NAT-Detection and hence encapsulate the ESP into UDP\4500 to avoid NAT ESP processing on the NAT routers.
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S4 |
|
Known Fixed Releases: * | 15.5(3)S1.4, 15.5(3)S2, 15.5(3)S2a, 15.6(1.10)S, 15.6(2)S, 16.2(0.177), 16.2(1) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S3.1, 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.2(0.184) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux62928 | Title: | IOS-XE IKE over 4500 & IKE nat-t keepalive drop with certain possibility |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
IKE over 4500 and IKE NAT-T keepalive packets drop with certain possibility.
Conditions:
DMVPN NAT-T setup error could be seen with some specific tunnel source and tunnel destination.
In details, by chance IKE packets will be recognized as IPSEC NATT UDP packets, and get dropped later after found there is no inner IPv4 or IPv6 header. This is caused by the characteristic pattern of IKE packets happen to be the same as IPSEC NATT UDP tunnel packets.
Workaround:
Change the tunnel configuration with a different tunnel source or different tunnel destination for the problematic VPN.
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.3(3)S1.16, 15.4(1)S |
|
Known Fixed Releases: * | 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.3(0.59) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv52997 | Title: | /32 static route added without add-route enabled for outside dynamic nat |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Static route incorrectly added by NAT into the RIB.
Conditions:
Outside dynamic NAT configured without add-route option & inbound connection initiated from an outside host.
Workaround:
None
Further Problem Description:
When using Outside dynamic NAT we are seeing /32 route added for outside local ip address.
This should be injected into the RIB only when we have add-route option enabled in the nat statement.
Issue is observed in 15.4(3)S3.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: * | 15.4(3)SS, 15.5(3)S, 16.2(0) |
|
Known Fixed Releases: | 15.6(2)S, 16.2(0.193) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux16182 | Title: | ECFM cannot work on EFP with VPWS interworking vlan |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ECFM packets cannot be sent out of ASR1K
Conditions:
EFP with VPWS interworking vlan
Workaround:
none
Further Problem Description:
ECFM packets are dropped by asr1k internally.
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 16.2(0.193) |
|
|
| |
| |
|
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: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S3.3 |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(3)S2, 15.5(3)S2a, 15.6(2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw95617 | Title: | QFP crash in NAT ALG after ipv4_nat_destroy_session |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR1k might experience a QFP microcode crash :
%CPPHA-3-FAULT: F0: cpp_ha: CPP:0.0 desc:INFP_INF_SWASSIST_LEAF_INT_INT_EVENT0 det:DRVR(interrupt) class:OTHER sev:FATAL id:2121 cppstate:RUNNING res:UNKNOWN flags:0x7 cdmflags:0x8
%CPPHA-3-FAULTCRASH: F0: cpp_ha: CPP 0.0 unresolved fault detected, initiating crash dump.
%CPPHA-3-FAULTCRASH: F0: cpp_ha: CPP 0.0 unresolved fault detected, initiating crash dump.
%CPPDRV-6-INTR: F0: cpp_driver-0: CPP10(0) Interrupt : 15-Sep-23 15:36:03.561809 UTC+0600:INFP_INF_SWASSIST_LEAF_INT_INT_EVENT0
%CPPDRV-3-LOCKDOWN: F0: cpp_ha: CPP10(0) CPP Driver LOCKDOWN due to fatal error.
As a result the cpp-mcplo-ucode_xxxxxxx.core.gz file is generated.
Conditions:
NAT ALG enabled.
The crash might occur when a NAT session expires.
Workaround:
unknown yet
Further Problem Description:
|
|
Last Modified: | 04-APR-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S5, 15.5(2)S3, 15.5(3)S2, 15.5(3)S2a, 15.6(1)S1, 15.6(2)S, 16.3(0.68) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw88491 | Title: * | show inventory shows suffix 1 for SN of CPAK-100G-SR10 shipped in 2014 |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
show inventory and other CLIs shows suffix of 1 for Serial Number of CPAK-100G-SR10 modules.
Conditions:
CPAK modules inserted in the EPA-1X100GE in ASR1000-MIP100 card on ASR 1000 platform.
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 05-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux94913 | Title: | Changing bridge-domain number under Overlay interface not taking effect |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Changing bridge-domain number under overlay service instance doesn't get reflected in the 'show otv vlan' till reload
Conditions:
Simple bridge-domain number change under the overlay service instance configuration does not get reflected in the 'show otv vlan' till we reload the router
Workaround:
reload the router
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtg37296 | Title: | PIM J/P timer stuck after RPSO |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
MC (zenkoku stream) Packet losses 800sec or more after RPSO.
The reproducibility of this issue is very low.
Conditions:
Workaround:
|
|
Last Modified: | 02-APR-2016 |
|
Known Affected Releases: | 12.2(33)XN |
|
Known Fixed Releases: * | 12.2(32.0.36)SRE, 12.2(33)SRE10, 12.2(33)SRE11, 12.2(33)SRE2, 12.2(33)SRE5, 12.2(33)SRE8, 12.2(33)SRE9, 12.2(33)SRE9a, 12.2(33)XNF2, 12.2(58)EZ |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy06618 | Title: | DMVPN Phase 3 Hub is not sending NHRP redirect with Shared IPsec profile |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR 1k is configured as DMVPN Phase 3 Hub. "nhrp redirect" and "nhrp shortcut" commands are configured appropriately. Intermittently, ASR DMVPN Hub may stop sending NHRP Redirect / Traffic indication messages to DMVPN spokes. When this happens, spoke-to-spoke tunnels are not built, and the spoke-to-spoke traffic is going through the Hub. Also, in this state the Hub is not producing any NHRP debugs when spoke-to-spoke traffic is sent through it.
Conditions:
- ASR is DMVPN Phase 3 Hub
- On the Hub, p2p GRE tunnel interface and mGRE tunnel interface have the same tunnel source interface and the same SHARED ipsec profile applied for tunnel protection
Workaround:
1. Use different tunnel sources for p2p GRE and mGRE tunnel interfaces, and different ipsec profiles
-or-
2. Keep the same tunnel source, but create separate tunnel profiles for p2p GRE and mGRE tunnel interfaces.
Note: 2nd workaround assumes that you create two ipsec profiles without the keyword "shared". This configuration works. But, if there are multiple mGRE tunnels usning the same tunnel source, you will need to apply 1st ipsec profile without "shared" to p2p GRE tunnel, and apply 2nd ipsec profile with "shared" keyword to all mGRE tunnels with common tunnel source. But, the bug CSCuu54392 may prevent you from making last configuration, and upgrade may be needed.
-or-
3. Downgrade ASR to 03.10.05.S / 15.3.3S5, where the problem was not exist
Further Problem Description:
Issue is intermittent. Its appearance may depend on the order in which p2p GRE and mGRE tunnels are enabled and coming up. It seems to appear when p2p GRE is coming up first, and mGRE is coming up second. It does not seem to appear when mGRE is coming first, and p2p GRE - second.
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: * | 16.3(0.192), 16.4(0.3) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz04378 | Title: | ICMP Time exceed dropped due to uRPF on the MPLS PE (per-ce label) |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Packets are dropped due to uRPF
Conditions:
MPLS label mode per-ce, no issue when we are using per-prefix mode
Workaround:
Use per-prfix label allocation mode or disable uRPF
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.4(1)IA1.32, 15.4(1)IA1.35, 15.5(3)S2.10, 15.6(0.22)S5, 16.3(0.176) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy61888 | Title: * | With static network NAT, ASR1K fails to NAT first two packets |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
NAT fails to process First two TCP / ICMP packets whenever a new entry needs to be created in the NAT database.
Conditions:
Issue seen with nat inside source static network is configured. The behavior is not seen with plain static NAT or with dynamic NAT.
Workaround:
none.
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 15.6(1.17)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux87741 | Title: | OTV router retains ARP ND cache after it becomes non-AED |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
OTV router retains ARP neighbor discovery cache even after it becomes non-AED
and keep responding to ARP requests received on internal interfaces.
Conditions:
ARP neighbor discovery cache is not disabled.
Workaround:
Disable ARP neighbor discovery cache.
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 15.4(3)S4.1 |
|
Known Fixed Releases: * | 16.4(0.8) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy38110 | Title: | EPA-10X10GE: Interface Input errors are seen |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
EPA-10X10GE could exhibit CRC or interface input errors
Conditions:
Issue is seen with 16.2.1 Release
Workaround:
No workaround.
Further Problem Description:
This is fixed in future 16.2 and 16.3 releases
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 16.3(0) |
|
Known Fixed Releases: | 16.2(1.1), 16.3(0.103) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz44452 | Title: | EPA-10X10GE: Packet drops and CRCS are seen at very cold temperatures |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
EPA-10x10GE EPA showed packet drops and interface CRCs.
Conditions:
Cold temperatures at (-5/-10 degrees)
Workaround:
No Workaround.
This is fixed in upcoming 16.2.2 and 16.3.1 releases.
Further Problem Description:
|
|
Last Modified: | 29-APR-2016 |
|
Known Affected Releases: | 16.2.0 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw11097 | Title: | ASR one way audio due to incorrect provision by FMAN-RP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR one way audio, and not streaming the RTP packets which it received in Local interface to Service provider interface.
Conditions:
In this specific instance, it is contact center call flow, where CVP enagged VXML gateway to play prompts, ringback and more prompts. So when there is multiple sip re-invites with different media details within span of few hundred ms, this issue is seen, which will result in one way audio at middle of the call. Intermittent issue.
Workaround:
In this case we increased the duration of the prompts, so ASR will not run into race. So ideally if there is enough gap between multiple sip transactions, then we may not see this issue.
Further Problem Description:
Refer summary.
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.4(3)S5.8, 15.5(3)S2.10 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz28604 | Title: * | L3-EoGRE:DHCPv4 clients over GREv6 tunnel get ip failed on Polaris |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
L3-EoGRE:DHCPv4 clients over GREv6 tunnel get ip failed on Polaris
Conditions:
DHCPv4 client over GREv6 tunnel
Workaround:
N/A
Further Problem Description:
N/A
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: * | 16.4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz28770 | Title: | L3-EoGRE:Priority !=0 in inner vlan header will result in dhcpv4 failed |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
L3-EoGRE:Priority !=0 in inner vlan header will result in dhcpv4 failed
Conditions:
Priority value rather than 0 in inner vlan header
Workaround:
Make the Priority value =0 in inner vlan header
Further Problem Description:
N/A
|
|
Last Modified: | 27-APR-2016 |
|
Known Affected Releases: * | 15.6(1)S, 16.4 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz21435 | Title: | IOS-XE: 'ACE event' process watchdog crash. |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A router could encounter a watchdog with the following logs preceding the crash:
IOSXE-WATCHDOG: Process = ACE event
The device could also generate a 0 byte core dump from the crash.
Conditions:
This issue coincided while pushing ACL configs via CSM on an ISR4k
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 15.4(3)S1.9 |
|
Known Fixed Releases: * | 15.5(3)S2.9, 15.6(0.22)S5, 16.3(0.178) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz40148 | Title: | ASR1K Crashed after changing to CGN mode |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR1K Crashed after changing to CGN mode
Conditions:
NAT mode changed from default to CGN.
Workaround:
Further Problem Description:
Software Version
================
03.16.00.S
*************************
** Decoded Stack Trace **
*************************
1: ipv4_nat_ha_upd_alg_sess_to ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/dplane/feature/nat/ipv4_nat_ha.c:2466
2: 0x40418e99 time_process_timer_ev ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/infra/time.c:593
3: 0x4041a15c process_recycle_control ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/infra/control_rx.c:101
4: 0x40811d75 mpass_restart_processing ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/infra/multipass.c:1242
5: 0x40822de0 infra_main ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/infra/packet.c:373
6: 0x40823515 pal_main ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/platform/mcp/mcp.c:77
7: 0x40823522 main ---> /auto/mcpbuilds21/release/03.16.00.S/BLD-V03_16_00_S_FC6/cpp/dp/hardware/cpp/common/hal_init.c:330
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux73951 | Title: | fman fp crash with 500k translations with bpa enabled |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
fman fp crash with 500k translations
Conditions:
fman fp crash with 500k translations
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy33103 | Title: | incoming frame from AC is punted even though l2tp session is down |
|
Status: | Fixed |
|
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:
shutdown/no shut the AC interface will recover
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: | 07-APR-2016 |
|
Known Affected Releases: | 15.4(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2.6, 16.3(0.151) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum04472 | Title: | ASR1K: Pb-free Patriot Prowler: IDB errors on scaling ds0 channels |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
After did a scaled config, remove an existing channel and adding a new one leads to trace back
Conditions:
On b-b Patriot/Prowler setup , configure more than maximum allowed ds0 channels. Once the maximum no of channels are created , delete couple of them and recreate new ones
Workaround:
None.
Further Problem Description:
|
|
Last Modified: | 12-APR-2016 |
|
Known Affected Releases: * | 15.2(2)S, 15.4(2)S |
|
Known Fixed Releases: | 15.2(4)S5.13, 15.2(4)S6, 15.3(3)S3.2, 15.3(3)S4, 15.4(1)S1.12, 15.4(1)S2, 15.4(1)S3, 15.4(1.16)S0.6, 15.4(1.16)S0.7, 15.4(2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut63804 | Title: | CPP crashed when device in pair became active |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When the active asr1k failed due to a parity error, almost at the same time, standby device was also crashed with following logs
Mar 28 14:31:56.511 EDT: %RG_PROTOCOL-5-ROLECHANGE: RG id 1 role change from Active to Init
Mar 28 14:31:56.512 EDT: %CPPDRV-3-LOCKDOWN: F0: cpp_ha: CPP10(0) CPP Driver LOCKDOWN due to fatal error.
Mar 28 14:31:56.515 EDT: %CPPHA-3-FAULT: F0: cpp_ha: CPP:0.0 desc:INFP_INF_SWASSIST_LEAF_INT_INT_EVENT0 det:DRVR(interrupt) class:OTHER sev:FATAL id:2121 cppstate:RUNNING res:UNKNOWN flags:0x7 cdmflags:0x8
Mar 28 14:31:56.516 EDT: %CPPHA-3-FAULTCRASH: F0: cpp_ha: CPP 0.0 unresolved fault detected, initiating crash dump.
Mar 28 14:31:56.516 EDT: %CPPHA-3-FAULTCRASH: F0: cpp_ha: CPP 0.0 unresolved fault detected, initiating crash dump.
Mar 28 14:31:56.516 EDT: %CPPDRV-6-INTR: F0: cpp_driver-0: CPP10(0) Interrupt : 15-Mar-28 14:31:56.509130 UTC-0400:INFP_INF_SWASSIST_LEAF_INT_INT_EVENT0
Mar 28 14:31:56.521 EDT: %CPPDRV-3-LOCKDOWN: F0: fman_fp_image: CPP10(0) CPP Driver LOCKDOWN due to fatal error.
Mar 28 14:31:57.145 EDT: %IOSXE_OIR-6-OFFLINECARD: Card (fp) offline in slot F0
Mar 28 14:31:57.145 EDT: %IOSXE_RP_ALARM-6-INFO: ASSERT MAJOR module F0 Unknown state
Mar 28 14:31:57.145 EDT: %IOSXE_RP_ALARM-2-ESP: ASSERT CRITICAL module R0 No Working ESP
Mar 28 14:31:57.542 EDT: %CPPCDM-3-ERROR_NOTIFY: F0: cpp_cdm: QFP 0 thread 143 encountered an error -Traceback= 1#dbab8adbe0e71d7303480441c1e031fc 805F9A1C 805ABD61 80020708 80351FD6 80623E6C
Mar 28 14:31:57.784 EDT: %IOSXE-3-PLATFORM: F0: cpp_cdm: CPP crashed, core file /tmp/corelink/cgn2.wsf.prnynj_ESP_0_cpp-mcplo-ucode_032815143157.core.gz
Mar 28 14:32:00.815 EDT: %CPPDRV-3-LOCKDOWN: F0: cpp_cp: CPP10(0) CPP Driver LOCKDOWN due to fatal error.
Mar 28 14:32:15.560 EDT: %CPPHA-3-FAULT: F0: cpp_ha: CPP:0.0 desc:CPP Client process failed: FMAN-FP det:HA class:CLIENT_SW sev:FATAL id:1 cppstate:RUNNING res:UNKNOWN flags:0x0 cdmflags:0x0
Conditions:
Device becoming active
Workaround:
Further Problem Description:
|
|
Last Modified: | 12-APR-2016 |
|
Known Affected Releases: | 15.3(3)S2.1 |
|
Known Fixed Releases: * | 15.3(3)S6, 15.4(3)S4, 15.5(3)S, 16.2(0.67) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw31230 | Title: | ASR1K B2B CGN NAT ASR1K ESP200 crashed with clear ip nat translation |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
In a Back-to-Back Carrier Grade NAT configuration using ASR1013 chassis and PAP+BPA configured, ESP200 may crash when execute the "clear ip nat translation .
Conditions:
ESP200 will not crash immediately when execute the "clear ip nat translation " but it appeared that when the ip nat translation hit the "0" count, that was when the ESP200 crashed.
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 12-APR-2016 |
|
Known Affected Releases: * | 15.3(3)S, 15.3(3)S6.10, 15.4(2)S1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw97986 | Title: | LLDP not working between ios-xe and ios-xr on subinterfaces |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR9K does not process all LLDP packets sent by ASR1K for subinterfaces.
Conditions:
ASR1K sends LLDP packets which include a VLAN tag.
Workaround:
In order for ASR9K to process LLDP packets, they must not have a VLAN tag. If ASR1K can be configured not to do VLAN tagging for LLDP, then this will work.
Further Problem Description:
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 15.3(3)S5.1 |
|
Known Fixed Releases: * | 15.5(3)S2.8, 15.6(0.22)S3, 16.2(0.352), 16.3(0.149) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux36675 | Title: | VLAN Unlimited not working in certain case with port-channel |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
All the TAG(s) should gets programmed into FP, SPA should not received any of the tag configuration on tcam.
Conditions:
In case of VLAN-unlimited mode, when we configure
port-channel with sub-interface all the TAG(s) should gets programmed into FP
instead of SPA.
Workaround:
Further Problem Description:
|
|
Last Modified: | 14-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2.7, 15.6(0.22)S3, 16.2(0.355), 16.3(0.101) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux81971 | Title: | 637488237: ASR1k crash in nat_alg_create_session |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Router running NAT crashes at nat_alg_create_session
hal_abort ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/hardware/cpp/common/hal_logger.c:81
2. 0x40337dd1 ipv4_nat_sess_getindex ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/infra/hash.c:100
3. 0x4034c534 ipv4_nat_find_session_entry_second ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/fw_nat_common/sessiondb.c:119
4. 0x403465e4 ipv4_nat_alg_create_session ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat_alg_common.c:1461
5. 0x40348025 ipv4_nat_process_token ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat_alg_common.c:2052
6. 0x4034854c ipv4_nat_alg_common_action_handler ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat_alg_common.c:2168
7. 0x40349880 ipv4_nat_alg_invoke ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat_alg_common.c:2475
8. 0x4034a4ac ipv4_nat_tcp_fixup ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat_tcp_fixup.c:522
9. 0x4034b030 ipv4_nat_l3_fixup ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat_fixup.c:209
10. 0x40357b71 ipv4_nat_translate ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat.c:3505
11. 0x4034f19d ipv4_nat_translate_out2in ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/dplane/feature/nat/ipv4_nat.c:6930
12. 0x4092ba5b ??
13. 0x40802478 infra_main ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/hardware/cpp/common/hal_feature_invoke.c:80
14. 0x40802944 pal_main ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/platform/mcp/mcp.c:77
15. 0x4080294e main ---> /auto/mcpbuilds24/release/03.17.00.S/BLD-V03_17_00_S_FC4/cpp/dp/hardware/cpp/common/hal_init.c:330
Conditions:
Router running Nat
Workaround:
Na
Further Problem Description:
Na
|
|
Last Modified: | 15-APR-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuh72756 | Title: | Traceback on RP1 with 3.10+ PP 6.0 and PP 6.1 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
When loading protocol-pack 6.0 or 6.1 a traceback might occur.
There is no functionality impact.
Conditions:
When loading protocol-pack 6.0 or 6.1 on top of version 15.3(3)S with RP1 platform.
Workaround:
Currently there is no workaround.
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 15.3(3)S |
|
Known Fixed Releases: | 15.3(3)S0.6, 15.3(3)S1, 15.3(3)S1a, 15.3(3)S2, 15.3(3)S2a, 15.3(3)S3, 15.3(3)S4, 15.4(1)S, 15.4(1)S0a, 15.4(1)S0b |
|
|
| |
| |
|
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: | 19-APR-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S5.1, 15.5(3)S2.7, 15.6(0.22)S4, 16.3(0.158) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux23929 | Title: | DL RPC timeout during FPD upgrade of CEOP SPAs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When using "upgrade hw-module subslot fpd file force" to upgrade the firmware of the CEOP SPA, the DL RPC Timeout message is seen and the fpd upgrade fails. Even if the upgrade fails, there will be no issues with the state of the SPA and it will work as it was before the upgrade was tried.
Conditions:
This is intermittent and seen only with CEOP SPAs.
The FPD upgrade works fine most of the times.
Workaround:
No workaround. Only suggestion is to keep some time gap between 2 successive fpd upgrades.
Further Problem Description:
|
|
Last Modified: | 19-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2.7, 15.6(0.22)S4, 16.3(0.127) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus55505 | Title: | ASRNAT: Static PAT commands are lost from the config after reboot |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
It is possible to configure static PAT to router interface (or interface IP) and dynamic PAT to router interface (or interface IP) at the same time. This is a valid and supported configuration used by many customers which have single public IP address. Example:
ip nat inside source static tcp 10.1.75.2 23 interface GigabitEthernet0/0/1.99 5000
ip nat inside source list 100 interface GigabitEthernet0/0/1.99 overload
In this case, static PAT command will be lost after router reload, because we put commands into the running-config and startup-config in reverse order. Dynamic PAT command is processed first during bootup, NAT allocates dynamic TCP portblock 4096 - 5119 for dynamic PAT and static PAT command is rejected, because TCP/5000 is within the 4096 - 5119 range.
So, the requirement is: we need to place static NAT/PAT commands into configuration before dynamic NAT/PAT commands and process them first after reboot.
Conditions:
IOS-XE versions have this defect.
Workaround:
Do not use router interfaces or router IPs for either static or dynamic PAT if possible. Use pools instead. The pools should not include any of router IPs.
Further Problem Description:
|
|
Last Modified: | 20-APR-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: * | 15.4(3)S5.7, 15.5(2.16)S, 15.5(3)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCup01088 | Title: | CPUHOG and crash on 'clear dmvpn session' with large NHRP cache |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
On an ASR 1000 Series Aggregation Services Router configured with DMVPN, CPUHOG messages may be observed after 'clear dmvpn session' is invoked.
In certain cases, this may lead to a watchdog timeout and an unexpected reboot of the router.
Conditions:
This issue is observed when a router has a very large NHRP table (10-20k entries or more) with a large number (thousands) of child entries per parent entry.
Workaround:
Reduce the size of the NHRP database through supernetting or similar.
Further Problem Description:
|
|
Last Modified: | 21-APR-2016 |
|
Known Affected Releases: | 15.2(4)S1 |
|
Known Fixed Releases: * | 15.2(1)SY1.13, 15.2(1)SY2, 15.2(4.0)ST, 15.2(4.0.21)E, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(1)IE101.170, 15.3(3)M4.1, 15.3(3)M5, 15.3(3)S4.10 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy99510 | Title: | ASR 1000 crash due to memory corruption - chunk magic overwritten. |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Unexpected reload due to memory corruption. In crashinfo information about bad magic number in chunk header .
Conditions:
No special conditions. No known traffic attribute which can causes the issue.
Workaround:
No None Workaround
Further Problem Description:
Suggest to Upgrade to a later long lived release.
|
|
Last Modified: | 22-APR-2016 |
|
Known Affected Releases: | 15.2(4)S3 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCub14611 | Title: | %IOSXE-3-PLATFORM: R0/0: kernel: physmap-flash.0: Chip not ready |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
%IOSXE-3-PLATFORM: R0/0: kernel: physmap-flash.0: Chip not ready
Conditions:
When the flash is updated, such as ROMMON upgrade or card reboot.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 25-APR-2016 |
|
Known Affected Releases: | 15.2(4)S, 15.3(1)S |
|
Known Fixed Releases: | 15.2(4)S5, 15.3(3)S1, 15.4(1)S |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz28483 | Title: | After OIR the power, power state shows "ps, fail" at ASR1001 |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: | Symptom:
After OIR the power, power state shows "ps, fail" at ASR1001/ASR1001-X
Conditions:
when OIR the power module
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 15.6(0.1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux28792 | Title: | ASR1K PIM Register process memory leak in processor pool |
|
Status: | Other |
|
Severity: | 3 Moderate |
Description: * | Symptom:
IOS-XE memory leak in PIM Register Process
Conditions:
This has been see on ASR1K running 3.10.2 code.
Potential triggers: with auto-rp config.
When PIM register creates a PIM encap and PIM decap tunnels upon leaning RP via auto-rp group-rp mapping.
seems like when router loss RP and learned again it will create new tunnels but won't free the memory for old ones.
Workaround:
Not known
Further Problem Description:
|
|
Last Modified: | 26-APR-2016 |
|
Known Affected Releases: | 15.3(3)S2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy62083 | Title: | If the Upgrade package is missing a desired package the box gets hold up |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom:
If ROMMON release 16.2(1r) is used to upgrade ESP40, the upgrade progress will fail. ESP40 will display "upgrade in progress" even it has failed.
16.2(1r) ROMMON package does not include older ESP40's ROMMON.
ROMMON upgrade on ESP40 will fail.
Conditions:
Use IOS command "upgrade rommon file [all | F0 | F1]" where FP are older (such as ESP40).
Workaround:
Use hw-module to reload the ESP40 to bring it back on line.
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux59083 | Title: | ASR1K: Error-objects after reloading scale DOWN MEP routed mode |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
ASR1K: Error-objects after reloading scale DOWN MEP routed mode
Conditions:
define down mep over subinterface,
reloading uut.
Workaround:
reloading EFP.
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw10240 | Title: | traceback @cpp_ipc_stats_check_pending_requests during sslvpn scale |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Scaling the SSLVPN configuration followed by clearing all the sessions abruptly and re connecting results in a traceback
Conditions:
With 5000 sslvpn sessions scaled, if we bring them all down abruptly, then, start re-connecting one client, but at the authentication prompt cancel the connection, we happen to see a traceback on the SSLVPN gateway
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 15.6(1)S, 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw81845 | Title: | "dir harddisk:" doesn't display files post loading incorrect image 4RU |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Loading incorrect image leads to kernal core
Conditions:
Loading incorrect image on 4RU
Workaround:
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj84864 | Title: | dev_pluggable_optics_selftest attribute table internally inconsistent |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:The following message is seen while booting the router with XE311 image:
dev_pluggable_optics_selftest attribute table internally inconsistent @ 0x121
Conditions:if router will be booted with XE311 image
Workaround:
none
|
|
Last Modified: | 25-APR-2016 |
|
Known Affected Releases: * | 15.4(1)S, 16.3(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuy84247 | Title: | Platform hardware throughput showing 2.5G on ASR1002-HX |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: | Symptom:
Platform hardware throughput showing 2.5G on ASR1002-HX
Conditions:
Platform hardware throughput showing 2.5G on ASR1002-HX and the crypto throughput showing 40G when the configured crypto throughput license is 8g-25g
Workaround:
Further Problem Description:
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 16.3(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtx17869 | Title: | Actual IPv6 Traffic Path doesn't Match sh ipv6 cef exact-route(+ASR Bug) |
|
Status: | Other |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
The command sh ipv6 cef exact-route does not show the correct egress interface for traffic
Conditions:
In a network with multiple parallel paths the commad sh ipv6 cef exact-route does not show the correct egress interface for traffic streams. This happens when using any of the cef load sharing
algorithms:
ipv6 cef load-sharing algorithm include-ports source
ipv6 cef load-sharing algorithm include-ports destination
ipv6 cef load-sharing algorithm include-ports source destination
Workaround:
No known workaround.
|
|
Last Modified: | 06-APR-2016 |
|
Known Affected Releases: | 15.1(3)S1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz12624 | Title: | IOS-XE: ENH: Match-in-vrf should support interface overloading |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
This is an enhancement defect filed to bring in interface overloading support in the match-in-vrf scenario
Conditions:
Router must be running IOS-XE. ISR routers running IOS are not affected.
Workaround:
Use another available routable IP address for PAT overload
Further Problem Description:
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/xe-2/nat-xe-2-book/iadnat-match-vrf.html#GUID-C3DA78F1-231C-4C7C-B57E-53B1EF32B385
Presently in the match-in-vrf scenario where the inside and outside interfaces both belong to the same f-vrf, then interface overloading is not supported. This enhancement defect is filed to bring in the support so, our customers do not have to purchase an additional IP address from their ISPs.
|
|
Last Modified: | 08-APR-2016 |
|
Known Affected Releases: | 15.1(1.13.17)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux59115 | Title: | ASR1002-X Crash with dpidb_tableid_params_initialize |
|
Status: | Open |
|
Severity: * | 6 Enhancement |
Description: | Symptom:
1. Memory increased gradually since the BB virtual interface grew up
QoS database objects are created by BB in tdl context, so we can observe the undeleted object rising up when virtual interface is created due to subscriber coming in.
TDL name 11/03 11/04 11/05 11/06 11/09
[cce_comm] type cce_classinfo 6545 6930 7000 8150 5660
[cce_comm] type cce_parent_info 1309 1386 1400 1630 1132
[mcp_comm] type if_handle 1309 1386 1400 1630 1132
[qos_defs] type hqf_node_id 1309 1386 1400 1630 1132
[qos_hqf] type tdl_hqf_queue_params 1308 1385 1399 1080 979
[qos_hqf] type tdl_hqf_priority_params 186 197 199 202 140
[qos_hqf] type tdl_hqf_shape_params 185 196 198 202 139
[qos_hqf] type tdl_hqf_reparent_params 1309 1386 1400 1630 1132
[qos_hqf] type hqf_node 1309 1386 1400 1630 1132
[qos_hqf] type hqf_nodelist 1309 1386 1400 1630 1132
The different value day-to-day
TDL name 11/04-11/03 11/05-1104
[cce_comm] type cce_classinfo 385 70
[cce_comm] type cce_parent_info 77 14
[mcp_comm] type if_handle 77 14
[qos_defs] type hqf_node_id 77 14
[qos_hqf] type tdl_hqf_queue_params 77 14
[qos_hqf] type tdl_hqf_priority_params 11 2
[qos_hqf] type tdl_hqf_shape_params 11 2
[qos_hqf] type tdl_hqf_reparent_params 77 14
[qos_hqf] type hqf_node 77 14
[qos_hqf] type hqf_nodelist 77 14
VA interface numbers
11/03 11/04 11/05 11/06 11/09
173 184 186(include one deleted) 377(280 deleted) 426(307 deleted)
So we can see 11/03-11/04, 11 new VA interfaces come into box, and 2 among 11/04-11/05. They match the tdl statistics in the above table.
When the subscribers of BB increase, VA increase at the same time, the memory grow up gradually. Looks like it is expected behavior.
2. VA interfaces accumulated more than 11/05 included many interfaces in state 'deleted' at 11/06.
Conditions:
We see the following logs in the syslog :
Oct 1 16:39:31 asr-lotim-1 124543: Oct 1 16:40:38: %PLATFORM-3-ELEMENT_CRITICAL: SIP0: smand: RP/0: Committed Memory value 119% exceeds critical level 100%
Oct 1 16:39:31 asr-lotim-1 124544: Oct 1 16:40:43: %CPPOSLIB-3-ERROR_NOTIFY: SIP0: cpp_cp: cpp_cp encountered an error -Traceback= 1#d7cb43846ce742756d3c512c783a19d5 errmsg:7F176F8B7000+121D cpp_common_os:7F1772D39000+DA3C cpp_common_os:7F1772D39000+1B5AE cpp_ifdb:7F178656D000+82CE cpp_ifdb:7F178656D000+15E3B cpp_qos_ea_lib:7F17879E8000+72F4A cpp_qos_ea_lib:7F17879E8000+72289 cpp_common_os:7F1772D39000+11C20 cpp_common_os:7F1772D39000+12306 evlib:7F1771AB0000+B937 evlib:7F1771AB0000+E200 cpp_common_os:7F1772D39000+13E42 :400000+5D26 c:7
Oct 1 16:39:33 asr-lotim-1 124549: Oct 1 16:40:53: %CPPOSLIB-3-ERROR_NOTIFY: SIP0: cpp_cp: cpp_cp encountered an error -Traceback= 1#d7cb43846ce742756d3c512c783a19d5 errmsg:7F176F8B7000+121D cpp_common_os:7F1772D39000+DA3C cpp_common_os:7F1772D39000+1B5AE cpp_ifdb:7F178656D000+82CE cpp_ifdb:7F178656D000+15E3B cpp_qos_ea_lib:7F17879E8000+72F4A cpp_qos_ea_lib:7F17879E8000+72289 cpp_common_os:7F1772D39000+11C20 cpp_common_os:7F1772D39000+12306 evlib:7F1771AB0000+B937 evlib:7F1771AB0000+E200 cpp_common_os:7F1772D39000+13E42 :400000+5D26 c:7
Traceback summary for these logs :
-----------------
% 0x7f176f8b821d : errmsg
% 0x7f1772d46a3c : cpp_vbuginf_flags_error
% 0x7f1772d545ae : cpp_buginf_flags_internal_error
% 0x7f17865752ce : cpp_ifdb_if_read_validate
% 0x7f1786582e3b : cpp_ifdb_feature_read
% 0x7f1787a5af4a : cpp_qos_ea_stats_query_intf
% 0x7f1787a5a289 : cpp_qos_ea_stats_query_n_async_handler_cmn
% 0x7f1772d4ac20 : smc_invoke_msg_callback
% 0x7f1772d4b306 : smc_msg_read_internal..1
% 0x7f1771abb937 : __evDispatch
% 0x7f1771abe200 : __evMainLoop
%
|
|
Last Modified: | 12-APR-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz43804 | Title: | ENH: FlexVPN Anyconnect-EAP Dual Authorization for dual-auth |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
This enhancemnet is about having about having clear authorization scheme for dual authentication.
Conditions:
dual-authorization
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 28-APR-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCum12999 | Title: * | Tunnel QoS Rooted from Port-Channel Interface |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: * | Symptom:
There is currently no support for QoS configuration on a tunnel interface which is sourced from a port-channel.
Conditions:
The commands to configure QoS on a port-channel rooted tunnel are available but the QoS polices will not be applied properly.
Workaround:
No workaround as this feature is not supported. It may be possible to configure QoS on a different interface to accomplish the same functionality.
Further Problem Description:
|
|
Last Modified: | 18-APR-2016 |
|
Known Affected Releases: | 15.2(4.1.1) |
|
Known Fixed Releases: | 15.5(0.1)S |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz46362 | Title: | Monitoring ASR1000 hardware TCAM usage |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
This is an enhancement to provide a tool for monitoring hardware TCAM of ASR1000
Such possibility is not available in any release as of May 2016. At this time, there is no plan to provide such tool.
Conditions:
Workaround:
Use command:
show platform hardware qfp active tcam resource-manager usage
Further Problem Description:
|
|
Last Modified: | 30-APR-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: | |
|
|
| |
没有评论:
发表评论