| |
|
Alert Type: | New |
Bug Id: | CSCva28875 | Title: | NAT ALG fails on Multipart SIP Header |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
The entire SIP message does not get NATed leading to one way audio issues.
Conditions:
When the SIP message Content-Type is multipart
Workaround:
Further Problem Description:
|
|
Last Modified: | 30-JUN-2016 |
|
Known Affected Releases: | 15.4(3)S3.13 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz86868 | Title: | POLARIS 16.2/16.3:Fman_fp Core@fman_aom_fhs_acl_op during configuration |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
While testing latest Polaris 16.2 image with "xe37_urpf_acl, xe39_ipv6fhs, xe310_gtp_teid" features,observing fman_fp core during configurations.
Conditions:
Fman_fp core is seen in RP2-ESP20/ESP40 platforms.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 30-JUN-2016 |
|
Known Affected Releases: * | 16.2(0), 16.3(0), Denali-16.3.1 |
|
Known Fixed Releases: | 16.2(1.35), 16.3(0.233), 16.4(0.68) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCty26186 | Title: | Enhancement request to capture watchdog reset on asr1k |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
reset did not save any core or crashinfo file. no error log either.
under show version:
"Last reload reason: Watchdog"
under "Reset reason Power On"
watchdog reset
Conditions:
normal operation. reset did not save any core or crashinfo file. no error log either.
Workaround:
this is a code enhancement. not a bug. therefore, no workaround applicable.
Further Problem Description:
This enhancement is specific to the ASR1K.
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | 15.1(2)S, 15.1(2)S2 |
|
Known Fixed Releases: | 15.4(3)S4, 15.5(2)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz64285 | Title: | Cube fails to send the SIP Error code response |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Cube fails to send the SIP Error code response for "SIP Service Shutdown" scenarios.
Conditions:
asr1001x-universalk9.V155_3_S2_SR637314193_2.SPA.bin image
Workaround:
NA
Further Problem Description:
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S, 15.6(0.22)S8, 15.6(2.12)T |
|
Known Fixed Releases: * | 15.5(3)M2.2, 15.5(3)M3, 15.5(3)S2.15, 15.5(3)S3, 15.6(1)S1.2, 15.6(2)T0.1, 15.6(2.0.1a)T0, 15.6(2.14)T, 16.2(1.25), 16.3(0.213) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw47720 | Title: * | 7878082ASR1001-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: | 24-JUN-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: | 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: | 11-JUN-2016 |
|
Known Affected Releases: | 15.4(3)S3.1 |
|
Known Fixed Releases: * | 15.4(3)S5.3, 15.5(3)S2.4, 15.5(3)S3, 15.6(0.22)S2, 16.3(0.121) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz69316 | Title: | MIP100/EPA-1X100GE SCOOBY-5-SERIAL_BRIDGE_BLOCK_EVENT messages |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The following console message may be displayed constantly from MIP100/EPA-1X100GE line card:
%SCOOBY-5-SERIAL_BRIDGE_BLOCK_EVENT: SIP{X}: cmcc: Block qfdh-data_fifo/5 of serial bridge 0 had I/O event 0x10
* {X} is the LC slot number
Conditions:
Normal operation particularly during high throughput conditions.
Workaround:
None.
Further Problem Description:
N/A
|
|
Last Modified: | 28-JUN-2016 |
|
Known Affected Releases: * | 15.5(3)S, 15.6(1)S, 16.2(0) |
|
Known Fixed Releases: | 16.3(0.238), 16.4(0.76) |
|
|
| |
| |
|
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: | 24-JUN-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, 15.6(1.29)SP, 15.6(2)T0.1, 15.6(2.0.1a)T0, 15.6(2.17)T, 16.2(0.363), 16.3(0.178) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz50434 | Title: | ISSU:XE314<->XE316 : IOSd Core@cfm_ha_issu_db_to_msg_pre_mpdb_transport |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
While testing ISSU from XE314<->XE316/XE317 with "cfm" feature in Kingpin platform, observing crash followed by linux_iosd core after RP switchover.
Conditions:
Core and crash is seen in both upgrade and downgrade in Kingpin, Nightster and RP2 platforms.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 04-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2.14, 15.6(1)S1.1, 15.6(1.17)S0.26, 15.6(1.32)SP, 16.3(0.223), 16.4(0.49) |
|
|
| |
| |
|
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: | 09-JUN-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2.16, 15.6(0.22)S0.19, 15.6(1.17)S0.13, 15.6(1.19)SP, 15.6(2)S, 16.2(0.303), 16.3(0.101) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCva19654 | Title: | ASR 1K LACP PortChannel Flapped during high CPU caused by BGP |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
When CPU high by BGP task, LACP flap:
HKIX#
*Jun 22 05:46:37.896: TenGigabitEthernet0/3/0 added as member-2 to port-channel1
*Jun 22 05:46:38.710: TenGigabitEthernet0/3/0 taken out of port-channel1
HKIX#
*Jun 22 05:46:49.391: TenGigabitEthernet0/3/0 added as member-2 to port-channel1
*Jun 22 05:46:50.859: TenGigabitEthernet0/2/0 taken out of port-channel1
*Jun 22 05:46:51.025: TenGigabitEthernet0/2/0 added as member-2 to port-channel1
Conditions:
Workaround:
Change to mode on
Further Problem Description:
|
|
Last Modified: | 23-JUN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy90440 | Title: | Performance monitor crashes with RTP traffic |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Router reloaded on its own. Showing Last reload reason: critical process fault, fman_fp_image, fp_0_0, rc=13.
Conditions:
Performance monitor config in place, specifically related to media:
performance monitor context profile application-experience
exporter destination source Loopback0 transport udp port 9991
traffic-monitor application-traffic-stats
traffic-monitor conversation-traffic-stats ipv4
traffic-monitor application-response-time ipv4
traffic-monitor media ipv4 ingress
traffic-monitor media ipv4 egress
traffic-monitor url ipv4 class-replace sampling-rate 50
Workaround:
Disabling performance monitor could be a potential workaround. Yet to be confirmed.
Further Problem Description:
|
|
Last Modified: | 13-JUN-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.4(3)M, 15.4(3)M1, 15.4(3)M2, 15.4(3)M3, 15.4(3)M4, 15.4(3)M5, 15.4(3)S, 15.4(3)S1, 15.4(3)S2, 15.4(3)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz72439 | Title: | Mark XE3.17.2/15.6(1)S2 as MDR break release for ASR1000-2T+20X1GE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | Symptom:
XE3.17.2/15.6(1)S2 is MDR incompatible release for ASR1000-2T+20X1GE ethernet line card which hosts fixed BUILT-IN-2T+20X1GE.
Below combinations are MDR incompatible :
(From Image) XE3.16.3 ------> XE3.17.2 (To Image) is MDR incompatible.
Conditions:
When the From image is XE3.16.3 MDR issu upgrade to XE3.17.2 is not allowed for ASR1000-2T+20X1GE ethernet line card which hosts fixed BUILT-IN-2T+20X1GE
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 22-JUN-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux91300 | Title: | Polaris 16.2: Traceback@be_ace_send_ikea with gre configs |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Router may hit the following traceback, without any other functionality issue:
%PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT: IOS thread disabled interrupt for 25 msec
Conditions:
Observed traceback at router bootup time, and when crypto configuration is added.
Workaround:
none
Further Problem Description:
Note that mcp_dev/xe image can also hit this traceback, just not nearly as frequent as polaris_dev image.
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | 15.6(1)S, 16.1(0), 16.2(0), 16.3(0), 16.3(1), 16.3.1, Denali-16.3.1 |
|
Known Fixed Releases: * | 15.5(3)S2.8, 15.5(3)S3, 15.6(0.22)S3, 16.2(0.348), 16.3(0.119) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz84796 | Title: | NBAR does not support dialer interface support on IOS-XE |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: * | NBAR not supported on dialer interface
Symptom:
NBAR not supported on dialer interface
Conditions:
NBAR not supported on dialer interface
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 20-JUN-2016 |
|
Known Affected Releases: | 15.5(3) |
|
Known Fixed Releases: | 15.5(3)S2.16, 15.5(3)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv94186 | Title: | SNMPWALK crash at ipsmIPSec_policyOfTunnel |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
The device crashes due to a segmentation fault during polling:
UNIX-EXT-SIGNAL: Segmentation fault(11), Process = SNMP ENGINE
Conditions:
The device encounters this crash when polled or during an SNMPWALK operation.
Workaround:
Workaround: Configure SNMP view to exclude
"snmp-server view iso included"
"snmp-server view ipSecPolMapTable excluded"
"snmp-server community view RO"
Further Problem Description:
|
|
Last Modified: | 29-JUN-2016 |
|
Known Affected Releases: | 15.3(3)S2, 15.3(3)S4, 15.4(3.0m)M4, 16.2(0) |
|
Known Fixed Releases: * | 15.2(1)SY1.107, 15.2(1)SY2, 15.2(4)EA1, 15.2(4.1.60)EA1, 15.2(4.2.1)EA2, 15.2(4.3.1)EC, 15.2(4.3.32)EC, 15.2(4.7.1)EC, 15.2(4.7.2)EC, 15.2(5.1.16)E |
|
|
| |
| |
|
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: | 21-JUN-2016 |
|
Known Affected Releases: | 15.5(2)S |
|
Known Fixed Releases: * | 15.4(3)S5.8, 15.5(3)M2.1, 15.5(3)S2.10, 15.5(3)S3, 15.6(0.22)S7, 15.6(1)T1.1, 15.6(2.20)T, 16.3(0.232), 16.4(0.76) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo16316 | Title: | 1NG: Nightster explicit QinQ entry hitting QinAny entry in VLAN TCAM |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
On ASR1001-X, for the fixed ports under BUILT-IN-2T+6X1GE, Packets will hit the QIN-ANY entry if configured first, rather than explicitly configured QINQ entry and pick up the classification policy for QIN-ANY entry.
Conditions:
This problem only occurs on ASR1001-X on BUILT-IN-2T+6X1GE ports, if Customer configures 'QINAny' entry followed by explicit QINQ entry.
Eg.
encap dot1q 50 second-dot1q any
encap dot1q 50 secnd-dot1q 10
encap dot1q 50 secnd-dot1q 50
So all the packet having outer vlan tag as 50 will always hit the hardware entry corresponding to entry '50-any' which will
cause the classification policy of '50-any' to be applied to entry '50-10' and '50-50' as well
Workaround:
Configure explicit QINQ tagged entries first followed by QINAny entry.
Eg.
encap dot1q 50 secnd-dot1q 10
encap dot1q 50 secnd-dot1q 50
encap dot1q 50 second-dot1q any
Further Problem Description:
|
|
Last Modified: | 22-JUN-2016 |
|
Known Affected Releases: | 15.4(2)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCva09426 | Title: | ASR crash @ avl_tree_free_object |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR router crash
Conditions:
This has been seen on ASR running 3.16.2 code
Workaround:
Not known
Further Problem Description:
The issue looks like some kind of memory corruption or double free.
|
|
Last Modified: | 23-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S2.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCva20050 | Title: | Polaris: RP crash occurred during the RP switchover |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Active RP crashed during the RP switchover when the "redundancy force-switchover" is issued.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | Denali-16.2.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw91797 | Title: | Traceback@lisp_client_eid_watch_mapping_msg_recv when unconfiguring LISP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traceback and error message similar to:
%LISP-4-ASSERT: Internal LISP error (client eid watch 1827 Failed to locate mapping to delete for 192.168.1.0/24)
may appear in the log when removing "router lisp" from the configuration.
Conditions:
Multicast is enabled on LISP interfaces.
Workaround:
System will automatically recover from the failure condition, no workaround is necessary.
Further Problem Description:
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: * | 15.4(1)IA1.72, 15.6(2.0.1a)T0, 15.6(2.17)T, 16.3(0.206), 16.4(0.4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCue44587 | Title: | ASR Missing RRI routes is with active SAs |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:After the L2L tunnel has been up for some time, the route created by RRI will be removed from the ASR routing table, even though there is still a valid IPSec SA built for the destination subnet.
Conditions:ASR configured with L2L tunnel and RRI is enabled.
Workaround:Configure a static route for the destination subnet on the ASR.
More Info:
|
|
Last Modified: | 28-JUN-2016 |
|
Known Affected Releases: | 15.1(2.0), 15.2(1)S2 |
|
Known Fixed Releases: | 15.1(1)IB273.6, 15.1(1)SY2.3, 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, 15.2(2)E |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCva10549 | Title: | 16.2:Kahuna:R0/0: kernel: FAT-fs (sda1): error seen while booting. |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
R0/0: kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt error seen
Conditions:
booting the image[mounting the USB].
Workaround:
Further Problem Description:
|
|
Last Modified: | 17-JUN-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz30182 | Title: | ASR1013: Fails to detect power supply at startup |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
An ASR1013 router may fail to detect a power supply for either power supply 2 or power supply 3 when first coming online. Syslogs will report this for example:
%CMRP-3-PFU_OIR: R0/0: cmand: Failed to handle a vacant oir event for PEM in slot 2, Invalid argument
%CMRP-3-PFU_MISSING: R0/0: cmand: The platform does not detect a power supply in slot 2
Conditions:
This is only seen on the ASR1013 router. Not all routers will exhibit the problem.
Workaround:
There is no workaround.
Further Problem Description:
There is no functional impact when the logs are generated as the router is booting. The logs are due to a delay in the detecting of the power supply in question. When the power supply is polled later it will be detected correctly.
|
|
Last Modified: | 17-JUN-2016 |
|
Known Affected Releases: | 16.3(0) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
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: | 16-JUN-2016 |
|
Known Affected Releases: | 16.2(0) |
|
Known Fixed Releases: * | 15.2(1)SY1.123, 15.2(1)SY2, 15.2(5.1.16)E, 15.2(5.5.66)E, 15.3(0.1.12)SY, 15.3(1)IE101.355, 15.5(3)M2.1, 15.5(3)S2.8, 15.5(3)S3, 15.6(0.22)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu80859 | Title: | ASR1001-X cpp_driver process high CPU with INT_DRAM_SBE in packet buf |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
In the output of "show processes cpu platform monitor", you would find that cpp_driver process is causing 95-100% cpu utilization.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
25657 root 20 0 987m 43m 22m R 100 0.6 19044:41 cpp_driver
18906 root 20 0 41880 31m 5032 R 43 0.4 4720:51 hman
And cpp_driver logs will contains below warning messages:
[cpp-drv]: (warn): COMP0053/lukehwdpe/6A1C: QFP0.0 - 'DPE3_CSR32_DPE_ERR_MISC_LEAF_INT__INT_DRAM_SBE' - detected in packet buffer memory at 0x0000c0937193f0 in DPE3
[cpp-drv]: (warn): COMP0053/lukehwdpe/6A08: QFP0.0 - Handling 'DPE3_CSR32_DPE_ERR_MISC_LEAF_INT__INT_DRAM_SBE'
Conditions:
Only applies to ASR1001-X
Workaround:
None
Further Problem Description:
None
|
|
Last Modified: | 14-JUN-2016 |
|
Known Affected Releases: | 15.5(1)S |
|
Known Fixed Releases: | 15.4(3)S4, 15.5(3)S1, 15.5(3)S1a, 15.6(1)S, 16.2(0.170) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCte51715 | Title: | %IOSXE-4-PLATFORM: R0/0: kernel: EXT2-fs warning checktime reached |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Logs will be bombarded with the following error message
%IOSXE-4-PLATFORM: R0/0: kernel: EXT2-fs warning: checktime reached, running
e2fsck is recommended
Conditions:
No service impact on the router, only logs are generated frequently.
ASR running any image before XNF1 release. XNF1 has the fix.
Workaround:
1. Drop into Linux shell
2. Issue following set of commands
"/sbin/tune2fs -c 0 -i 0 /dev/sda1"
"/sbin/tune2fs -c 0 -i 0 /dev/sda2"
"/sbin/tune2fs -c 0 -i 0 /dev/sdb1"
"/sbin/tune2fs -c 0 -i 0 /dev/sdb2"
Further Problem Description:
The stated workaround is only good for 6 months. A reboot is required to get past this problem after applying the stated workaround. However, anytime there is a filesystem mount or reformat, the problem may resurface. The ultimate fix to this problem has been integrated into CSCuz33638.
|
|
Last Modified: | 13-JUN-2016 |
|
Known Affected Releases: | 12.2XN |
|
Known Fixed Releases: | 12.2(33)XNF1, 15.0(1)S |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy59471 | Title: | erspan supports configure flexible mac for the wan interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
erspan supports configure flexible mac for the wan interface
Conditions:
erspan supports configure flexible mac for the wan interface
Workaround:
Further Problem Description:
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | 15.3(3)S3.16 |
|
Known Fixed Releases: * | 15.5(3)S2.5, 15.5(3)S3, 15.6(0.22)S1, 16.2(1.9), 16.3(0.145) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy86578 | Title: | ASR1k: abnormal d-mac show running even pseudo d-mac not defined |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
ASR1k: abnormal d-mac show running even pseudo d-mac not defined
Conditions:
only define pseudo s-mac in ERSPAN. then show running config
abnormal d-mac show running even pseudo d-mac not defined
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2.6, 15.5(3)S3 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy26377 | Title: | Memory leak observed after upgrade to XE 3.13.4 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RP process memory leak on SSS/AAA due to "aaa_req_alloc" and "check_username_password"
Conditions:
Leak happens when ISG sends a authorization request to AAA server and there is a delay in receiving a response from AAA server. ISG sends out a retry request to next AAA server configured. When we get response from both servers, internally second request sent was not freed.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | 15.4(3)S4.2 |
|
Known Fixed Releases: * | 15.4(3)S5.1, 15.5(2)S2.15, 15.5(2)S3, 15.5(3)S2.3, 15.5(3)S3, 15.6(0.22)S0.23, 16.3(0.117) |
|
|
| |
| |
|
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: | 11-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2.7, 15.5(3)S3, 15.6(0.22)S4, 16.3(0.127) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux66017 | Title: | ASR1K crash due to "SNMP engine" when polling ifEntry on sonet interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
RP2 crash due to SNMP ENGINE. decoder crashinfo.
0x784c1df strlen ---> ../VIEW_ROOT/cisco.comp/system-infra/libc/src/string/strlen.c:42
2. 0x641a030 sonet_vt_get_ifAlias ---> ../hes/sonet_ifmib.c:773
3. 0x6419e5a sonet_vt_update_ifAlias ---> ../hes/sonet_ifmib.c:818
4. 0x6dce46a update_cim_rsp_data_for_subiab ---> ../snmp/legacy_ifmib_driver.c:3312
5. 0x6dcd49f legacy_get_gen_stats ---> ../snmp/legacy_ifmib_driver.c:3399
6. 0x6dcd2bb legacy_if_get_data ---> ../snmp/legacy_ifmib_driver.c:4251
7. 0x796ef15 reg_invoke_im_driver_if_data_get_callback ---> ../if_mgr/im_driver_registry.ios.regc:1503
8. 0x6cbf9a9 im_client_if_data_get ---> ../if_mgr/common/im_client_api.c:382
9. 0x7976a69 reg_invoke_im_client_if_data_get ---> ../if_mgr/im_client_registry.ios.regc:631
10. 0x1bebf75 k_ifEntry_get ---> ../snmp/sr_ifmib.c:2871
11. 0x1beb341 ifEntry_get ---> ../snmp/sr_ifmib.c:352
12. 0x32a68f6 GetExactObjectInstanceCore ---> ../snmp/SR/snmpd/shared/objectdb.c:709
13. 0x327051a do_response ---> ../snmp/SR/snmpd/shared/snmpresp.c:220
14. 0x325a1a4 SrDoSnmp ---> ../snmp/SR/snmpd/shared/dosnmpv3.c:484
15. 0x3292c3e local_snmp_engine ---> ../snmp/snmp_dispatcher.c:218
Conditions:
polling ifEntry/ifAlias on sonet interface
Workaround:
snmp-server view excludeifXEntry iso included
snmp-server view excludeifXEntry ifXEntry excluded
snmp-server view excludeifXEntry ifEntry excluded
snmp-server community view excludeifXEntry RO 99
Further Problem Description:
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | n/a |
|
Known Fixed Releases: * | 15.3(3)S7.2, 15.4(3)S5.5, 15.5(3)S2.8, 15.5(3)S3, 15.6(0.22)S3, 16.3(0.147) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux89723 | Title: | Error when service-policy at sub-interface/pvc/service-group is applied |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Customer has ADSL connections arriving through Gi0/0/1 , once these connections are authenticated QOS policies are assigned via RADIUS dynamically.
The error message is noticed when neighbor 57.7.26.162 which is a peer authenticated via ADSL comes up and RADIUS tries to push QOS policy for the user :
%BGP-5-ADJCHANGE: neighbor 57.7.26.162 vpn vrf EC-LYO Up user-defined classes with queueing features are not allowed in a service-policy at sub-interface/pvc/service-group
%QOS-3-ATLEAST_ONE_FAILOVER_ERR: Fail-over of dynamic interface GigabitEthernet0/0/1 failed
Conditions:
Once the connection is authenticated a QOS policy is pushed based on their plan like in the following example :
ex -
"AMPAB003@lyo.amplivia.fr" Cleartext-Password := "xxxxxxxxxxxxx"
Service-Type = Framed-User,
Framed-Protocol = PPP,
Class = 4,
Tunnel-Type:1 += 3,
Tunnel-Type:2 += 3,
Tunnel-Preference:2 += 20,
Tunnel-Client-Auth-ID:1 += gre,
Tunnel-Client-Auth-ID:2 += gre,
Cisco-Avpair += "ip:sub-qos-policy-out=COS-OUT-SHAPED-ADSL-14M", ---> QOS policy Assigned.
Cisco-Avpair += "ip:vrf-id=REC-LYO",
Cisco-Avpair += "ip:ip-unnumbered=Loopback1019",
Framed-IP-Address = 57.7.2.18,
Policy-Map :
policy-map COS-OUT-SHAPED-ADSL-14M
class class-default >>> Parent policy but it only has class default so no restrictions here.
shape average 14000000
service-policy PLATINIUM-ADSL >>> Child policy does not have any shaper configured.
policy-map PLATINIUM-ADSL
class OUT-BBE
bandwidth remaining percent 40
class OUT-BE
bandwidth remaining percent 40
class OUT-LBE
bandwidth remaining percent 5
class OUT-NC
bandwidth remaining percent 14
class OUT-PREMIUM
priority percent 10
Workaround:
(1) Reload the box
(2) Do not use the Virtual-Access (VA) for the session which has seen the error. Other VAs are fine.
Further Problem Description:
Customers will hit the issue when QoS policy comes from radius and there is already a QoS policy installed on the same VA. Also they may see issues with session flaps, queue-move, etc.
This is a functional issue. QoS policy won't get installed after the error happens. No new policy can be attached from then onwards at the same VA where the error happens (till a reload).
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2.8, 15.5(3)S3, 15.6(0.22)S5, 15.6(1.17)S0.20, 15.6(1.26)SP, 16.2(1.23), 16.3(0.191), 16.4(0.18) |
|
|
| |
| |
|
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: | 11-JUN-2016 |
|
Known Affected Releases: | 15.3(3)S5.1 |
|
Known Fixed Releases: * | 15.5(3)S2.8, 15.5(3)S3, 15.6(0.22)S3, 16.2(0.352), 16.3(0.149) |
|
|
| |
| |
|
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: | 11-JUN-2016 |
|
Known Affected Releases: | 15.4(3)S |
|
Known Fixed Releases: * | 15.4(3)S5.1, 15.5(3)S2.7, 15.5(3)S3, 15.6(0.22)S4, 15.6(1.17)S0.25, 15.6(1.33)SP, 16.3(0.158) |
|
|
| |
| |
|
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: | 11-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S |
|
Known Fixed Releases: * | 15.5(3)S2.7, 15.5(3)S3, 15.6(0.22)S3, 16.2(0.355), 16.3(0.101) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy60338 | Title: | l2tp crashes during failover preceeded by a kernel panic |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Standby RP crashes on l2tp code during failover.
Conditions:
The crash has been seen during failover preceeded by a kernel panic
Workaround:
None known
Further Problem Description:
|
|
Last Modified: | 11-JUN-2016 |
|
Known Affected Releases: | 15.2(2)S1 |
|
Known Fixed Releases: * | 15.5(3)S2.6, 15.5(3)S3, 15.6(0.22)S3, 15.6(1.17)S0.21, 15.6(1.28)SP |
|
|
| |
| |
|
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: | 11-JUN-2016 |
|
Known Affected Releases: | 15.4(3)S, 15.6(1)S |
|
Known Fixed Releases: * | 15.5(3)S2.6, 15.5(3)S3, 16.3(0.151) |
|
|
| |
| |
|
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: | 19-JUN-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.5(3)S3, 15.6(0.22)S5, 15.6(1)T1.1, 15.6(1.17)S0.24, 15.6(1.31)SP, 15.6(2)T0.1, 15.6(2.15)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz76293 | Title: | ASR1001x cpp_cp_svr core |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
ASR1001x crash with cpp_cp_svr core generated.
Conditions:
this is seen on a ASR1001x running code 3.16.02.S(155-3.S2)
Problem occurs when QoS configuration is applied to a link within a port channel and a subsequent change in the link state occurs.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 30-JUN-2016 |
|
Known Affected Releases: | 15.5(3)S2.1 |
|
Known Fixed Releases: | 16.4(0.89) |
|
|
| |
| |
|
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
Conditions:
Router running Nat
Workaround:
Na
Further Problem Description:
Na
|
|
Last Modified: | 29-JUN-2016 |
|
Known Affected Releases: | 15.6(1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCva27117 | Title: | ASR1001X Power Supply Module Status Stuck in Critical |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Power supply module in ASR1001-X stuck in "ciritcal" in "show facility-alarm status".
Conditions:
none
Workaround:
None at the moment.
Further Problem Description:
the power supply is still working properly in "show environment all".
|
|
Last Modified: | 29-JUN-2016 |
|
Known Affected Releases: | 15.4(3)S2.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuz70797 | Title: | AOR: extracted fields local memory initialization |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Illegal memory access on 2KP and 1NG platforms, might cause crash.
Conditions:
Performance-monitor configuration, including AOR for extracted fields with DMVPN, when performance-monitor policy is attached to both Tunnel interface and physical output interface.
Workaround:
Remove performance monitor service-policy from physical output interface.
Further Problem Description:
|
|
Last Modified: | 29-JUN-2016 |
|
Known Affected Releases: | 16.3(0) |
|
Known Fixed Releases: | 16.4(0.49) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz93166 | Title: | route-map match tag limit |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
We are seeing an odd behavior with route-map match tag, where the entries are truncated and replaced with 0 after entry #31
ASR-1(config-route-map)# match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
ASR-1(config-route-map)#do sh run | s route-map
route-map testing permit 10
match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 0
We noticed this behavior after moving from 15.1(3).S5 to 15.3(3)S6, we also noticed this behavior in the 15.6(1)S1
Conditions:
match tag entries must surpass 31
Workaround:
Remove the tag 0, and add the tags that were truncated
ASR-1(config-route-map)#match tag 32 33 34 35 36
ASR-1(config-route-map)#do sh run | s route-map
route-map testing permit 10
match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 0 32 33 34 35 36
ASR-1(config-route-map)#
ASR-1(config-route-map)#no match tag 0
ASR-1(config-route-map)#do sh run | s route-map
route-map testing permit 10
match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
Further Problem Description:
We are seeing an odd behavior with route-map match tag, where the entries are truncated and replaced with 0 after entry #31. However it allows you to add more entries after and even remove the truncated 0.
ASR-1(config-route-map)# match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
ASR-1(config-route-map)#do sh run | s route-map
route-map testing permit 10
match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 0
ASR-1(config-route-map)#
ASR-1(config-route-map)#match tag 32 33 34 35
ASR-1(config-route-map)#no match tag 0
ASR-1(config-route-map)#do sh run | s route-map
route-map testing permit 10
match tag 1 2 3 4 5 6 7 8 9 10 11 12 13 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 34
ASR-1(config-route-map)#
|
|
Last Modified: | 06-JUN-2016 |
|
Known Affected Releases: | 15.6(0.1)S |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy56721 | Title: | xconnect PVC also up even through PW type not same on both side |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
ASR9K use PW type ip ,ASR1K use PW type eth the xconnect PVC can aslo up?but no traffic can pass PVC.
Conditions:
ASR9K didn't support PW type eth command
Workaround:
exchange the both side PW type to IP?everything is ok
Further Problem Description:
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | none |
|
Known Fixed Releases: * | 15.6(1.17)S0.22, 15.6(1.28)SP, 15.6(2.0.1a)T0, 15.6(2.13)T, 16.3(0.137), 2.2(7b)TS10, 7.3(0)LDV(0.8) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus38022 | Title: | Fair-queue with tunnel QoS should use the original pkt header for flows |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Not traffic fairness when fair-queue feature is used with tunneled traffic.
Conditions:
When QoS service-policy containing "fair-queue" feature and applied to tunneled traffic, all the traffic would be sent out via a single flow queue. it's because only the tunnel's outer header information would be seen by "fair-queue" feature, hence considered as the same flow.
Workaround:
No workaround.
Further Problem Description:
|
|
Last Modified: | 26-JUN-2016 |
|
Known Affected Releases: | 15.5(2)S, 16.3(0) |
|
Known Fixed Releases: * | 15.6(2.20)T, 16.3(0.243), 16.4(0.57) |
|
|
| |
:
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论