| |
|
Alert Type: | Updated * |
Bug Id: | CSCuo23114 | Title: | packet loss observed when unrelated interface is unshut |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: When an unrelated onboard ISR-G2 GE port is unshut, some packets will be dropped by the ingress interface and marked as "input error" and "overrun" in "show interface"
Conditions: Traffic flows through ISR-G2 onboard GE ports and an unused onboard GE port is unshut. The ingress GE port would drop some packets.
Workaround: Enable Flow Control on peer device connecting to the ingress ISR-G2 port.
Further Problem Description:
|
|
Last Modified: | 06-JUN-2016 |
|
Known Affected Releases: * | 15.1(4)M3, 15.2(2)T, 15.3(3)M3, 15.4(3)M4.1 |
|
Known Fixed Releases: | 15.3(3)M4, 15.4(3)M3.2, 15.4(3)M4, 15.5(0.9)T, 15.5(1.2.1a)GB |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv01607 | Title: | Invalid spi, Attempt to use contiguous buffer as scattered, Full queue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: Traceback & buffer error:
%CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=X.X.X.X, prot=50, spi=0x410D57F3(1091393523), srcaddr=Y.Y.Y.Y, input interface=GigabitEthernet0/1 Jun 16 12:31:00.744: %SYS-2-BADBUFFER: Attempt to use contiguous buffer as scattered src, ptr= 3DE47CB4, pool= 3DE47634 -Process= "", ipl= 1 -Traceback= 300BE43Cz 37116CF8z 37108568z 30402C18z 304037E0z 30406CE4z 37108BDCz 300C04ECz 300BFE30z 3002A23Cz 30F4D278z
Interfaces associated with tunnels get wedged shortly - input queue full.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 16-JUN-2016 |
|
Known Affected Releases: | 15.5(1)T |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.6(1.23)T, 15.6(2)T0.1, 15.6(2.1)T, 15.6(2.12.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz42299 | Title: | Crash when configuring CWS |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom: The device is a CISCO2951/K9 running version 15.4(3)M5 and crash after enable CWS.
Conditions: This is caused after applying CWS configuration
Int cws out
Adding "cws out" to the tunnel interface causes the router to crash.
Workaround: Removing it "no cws out" from the interface fixes the issue.
Further Problem Description:
|
|
Last Modified: | 21-JUN-2016 |
|
Known Affected Releases: | 15.4(3.0j)M5 |
|
Known Fixed Releases: * | 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EY, 15.2(2)E, 15.2(2)E1, 15.2(2)E2, 15.2(2)E3, 15.2(2)E4 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz74337 | Title: | Convert cause value 86 to 16 when using MGCP |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: When the call is disconnected from the PSTN side, the IP Phone plays reorder tone instead of hang up the call.
Conditions: FXO Port is MGCP controlled by CUCM. TELCO use Tone based disconnect.
Workaround: Convert to either H323 or SIP and change the Disconnect Value from 86 to 16:
H323:
application map q850-cause 86 q850-cause 16
SIP:
voice class sip-profiles 1 request BYE sip-header Reason modify "Reason: Q.850;cause=86" "Reason: Q.850;cause=16"
Further Problem Description: 1. The following behavior is observed when the issue occurs:
--snip-- Feb 1 21:19:41.013 UTC: //1134/4561055B822D/DSPAPI/[0/1:2]/dsp_voice_det_status_change: Feb 1 21:19:41.013 UTC: //1134/4561055B822D/DSPAPI/[0/1:2]/dsp_voice_det_status_change: Status=512, Timestamp=0, Tone ID=0, Trigger=TRUE Feb 1 21:19:41.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/vtsp_dsm_media_event_cb: Event=E_DSMP_DSP_SUP_TONE Feb 1 21:19:41.013 UTC: htsp_process_event: [0/1/0, FXOLS_OFFHOOK, E_DSP_SUP_DISCONNECT]fxols_outgoing_sup_disc Feb 1 21:19:41.013 UTC: htsp_timer - 1000 msec Feb 1 21:19:41.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/vtsp_process_event: [state:S_CONNECT, event:E_TSP_PRE_DISC_CAUSE] Feb 1 21:19:42.013 UTC: htsp_process_event: [0/1/0, FXOLS_OFFHOOK, E_HTSP_EVENT_TIMER]fxols_disc_confirm Feb 1 21:19:42.013 UTC: htsp_timer_stop Feb 1 21:19:42.013 UTC: htsp_timer_stop2 Feb 1 21:19:42.013 UTC: htsp_timer_stop3 Feb 1 21:19:42.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/vtsp_process_event: [state:S_CONNECT, event:E_TSP_DISCONNECT_IND] Feb 1 21:19:42.013 UTC: //1134/4561055B822D/VTSP:(0/1/0):-1:1:2/act_generate_disc: Cause Value=86 --snip--
--snip-- Feb 1 21:19:42.013 UTC: MGCP Packet sent to 22.34.64.11:2427---> DLCX 998279287 aaln/S0/SU1/0@SCORTR11001.bfm.com MGCP 0.1 C: A000000009809b17000000F5 I: 22A P: PS=1293, OS=206880, PR=1294, OR=207040, PL=0, JI=5, LA=0 E: 501 <--- --snip--
2. A new CLI was created for this, the command will be available on the coming fixed releases:
voice-port x/x/x supervisory cause-code callclear-to-normaldisconn
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | 15.2(4)M6 |
|
Known Fixed Releases: * | 15.6(2.0.1a)T0, 15.6(2.15)T, 16.3(0.217), 16.4(0.40) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz56429 | Title: | C2900: MGCP ssrc=0/seq=0 in secure call |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: Sporadically CWMS can't decrypt packets from GW
Conditions: MGCP with secure call
Workaround: Using older version , such as 15.2(2)T3
Further Problem Description:
|
|
Last Modified: | 24-JUN-2016 |
|
Known Affected Releases: | 15.6(2)T |
|
Known Fixed Releases: * | 15.4(3)S5.12, 15.5(3)M2.2, 15.5(3)M3, 15.5(3)S2.14, 15.5(3)S3, 15.6(2)T0.1, 15.6(2.0.1a)T0, 15.6(2.13)T, 16.2(1.21), 16.3(0.206) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCur64583 | Title: | %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xE0 |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xE0, offset 0x00000000 on I2C bus 1
Conditions: Steady state operations
Workaround: None
Further Problem Description: None
|
|
Last Modified: | 28-JUN-2016 |
|
Known Affected Releases: | 15.0(1)M7 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCul85304 | Title: | UDI Compliant SFP not showing up correctly in show inventory |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: UDI compliant SFPs are not showing the correct PID in the 'show inventory' output after inserted into a HWIC-1GE-SFP or an EHWIC-1GE-SFP-CU
################################ FROM SHOW INVENTORY OUTPUT ################################ NAME: "1000BASE-LX SFP", DESCR: "1000BASE-LX SFP" PID: SCP6J44-C1-BMH , VID: A , SN: XXXXXXXXXXX
NAME: "1000BASE-SX SFP", DESCR: "1000BASE-SX SFP" PID: FTLF8519P3BNL-CS , VID: A , SN: XXXXXXXXXXX
Here we see UDI SFPs are showing something like FTLF8519P2BCL-CS under the PID which seems like the manufacturer's data. For UDI compliant SFPs, they need to show the actual PID which is GLC-LH-SMD and GLC-SX-MMD in this case.
Conditions: This was seen after inserting the SFPs into a HWIC-1GE-SFP on a 2921. The issue is likely the same on any ISR-G2. I have also noticed this issue on a 2811 which is an ISR-G1
Workaround: None
Further Problem Description:
|
|
Last Modified: | 14-JUN-2016 |
|
Known Affected Releases: * | 15.1(4)M6.10, 15.3(3)M, 15.4(1.15)T |
|
Known Fixed Releases: | 15.3(3)M5.2, 15.3(3)M6, 15.4(3)M1.1, 15.4(3)M2, 15.5(1.11)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz87335 | Title: | ISM-VPN seems as encapsulation failure after tunnel down |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom: ISM-VPN seems as encapsulation failure after tunnel down
Conditions: under investigation
Workaround: unknown
Further Problem Description:
|
|
Last Modified: | 14-JUN-2016 |
|
Known Affected Releases: | 15.4(3) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy90150 | Title: | PA Export stack overflow causing memory corruption |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom: A device may crash due to memory corruption.Sometimes a STACKLOW message would appear in the crashinfo log:
%SYS-6-STACKLOW: Stack for process PA Export running low, 16/6000
Conditions: Flexible NetFlow, IP NAT, ACL are configured on the same interface. Suspected EzPM configuration contributing to the issue.
Workaround: Disabling performance monitor stops the crashes.
Further Problem Description:
|
|
Last Modified: | 19-JUN-2016 |
|
Known Affected Releases: | 15.5(3)M1.1 |
|
Known Fixed Releases: * | 15.6(2.20)T |
|
|
| |
没有评论:
发表评论