Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3925E Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.5.3M2 | Release Date: | 10-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3925E Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.4.3M5 | Release Date: | 11-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
| 3925E Integrated Services Router |
| | | | Suggested  : | | Previously Suggested: | |
|
Software Updates for 3900 Series Integrated Services Routers
Product Name: | 3945 Integrated Services Router | Software Type: | NBAR2 Protocol Packs | Release Version: | 17.0.0
| |
| |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3945E Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.5.3M2 | Release Date: | 10-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3945E Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.4.3M5 | Release Date: | 11-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
| 3945E Integrated Services Router |
| | | | Suggested : | | Previously Suggested: | |
|
Software Updates for 3900 Series Integrated Services Routers
Product Name: | 3925 Integrated Services Router | Software Type: | NBAR2 Protocol Packs | Release Version: | 17.0.0
| |
| |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3925 Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.5.3M2 | Release Date: | 10-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3925 Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.4.3M5 | Release Date: | 11-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
| 3925 Integrated Services Router |
| | | | Suggested : | | Previously Suggested: | |
|
Software Updates for 3900 Series Integrated Services Routers
Product Name: | 3945E Integrated Services Router | Software Type: | NBAR2 Protocol Packs | Release Version: | 17.0.0
| |
| |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3945 Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.4.3M5 | Release Date: | 11-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
Alert Type: | New Release | Product Name: | 3945 Integrated Services Router | Software Type: | IOS Software | Release Version: | 15.5.3M2 | Release Date: | 10-FEB-2016 |
Software Updates for 3900 Series Integrated Services Routers
| 3945 Integrated Services Router |
| | | | Suggested : | | Previously Suggested: | |
|
Software Updates for 3900 Series Integrated Services Routers
Product Name: | 3925E Integrated Services Router | Software Type: | NBAR2 Protocol Packs | Release Version: | 17.0.0
| |
| |
Known Bugs - 3900 Series Integrated Services Routers
| | |
Alert Type: | Updated * | Bug Id: | CSCuc56259 | Title: | Voice Gateway May Crash Due To %VOIP_RTP-6-MEDIA_LOOP: | |
Status: | Fixed | |
Severity: | 1 Catastrophic | Description: | Symptoms: A Cisco IOS router (so far only seen on 15.1 and newer), running as a voice gateway may crash. Just prior to the crash, these messages can be seen:
%VOIP_RTP-6-MEDIA_LOOP: The packet is seen traversing the system multiple times
Delivery Ack could not be sent due to lack of buffers.
and/or
%SYS-6-STACKLOW: Stack for process IP Input running low, 0/12000
Conditions: This happens when a media loop is created (which is due to misconfiguration or some other call forward/transfer scenarios).
Workaround: Check the configurations for any misconfigurations, especially with calls involving CUBE and CUCM.
| |
Last Modified: | 11-FEB-2016 | |
Known Affected Releases: | 15.2(3)T2 | |
Known Fixed Releases: * | 15.1(4)M5.19, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(1)T3.2, 15.2(1)T4, 15.2(1.2.3)PI22, 15.2(2)T2.3, 15.2(2)T3 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv37210 | Title: | SM-X-1T3/E3 show controller serial x/y crashes 3900e | |
Status: | Fixed | |
Severity: | 1 Catastrophic | Description: | Symptom:
Issuing show controller Serial command of the Serial
interface created by SM-X-1T3/E3 card causes router to crash.
Conditions:
Issue is seen only on 3900e router platform with SM-X-1T3/E3
Workaround:
None.
Further Problem Description:
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.6(0.6)T | |
Known Fixed Releases: * | 15.3(3)M6.2, 15.3(3)M7, 15.4(3)M3.2, 15.4(3)M4, 15.5(3)M0.2, 15.5(3)M1, 15.6(0.8)T, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtn83520 | Title: | Traceback seen on VOIP_RTCP | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: VOIP_RTCP related traceback is seen.
Conditions: This symptom is observed when IPIP gateways are involved.
Workaround: There is no workaround.
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.1(1)T2 | |
Known Fixed Releases: * | 12.4(24)MDA13, 12.4(24)T10, 12.4(24)T11, 12.4(24)T12, 12.4(24)T7, 12.4(24)T8, 12.4(24)T9, 15.0(1)M10, 15.0(1)M7.5, 15.0(1)M8 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtr46854 | Title: | PPP multilink between ISR G2 and ASR1K crashes ISR | |
Status: | Fixed | |
Severity: | 2 Severe | Description: * | Symptoms: The PPP multilink between the Cisco ISR G2 router and the Cisco ASR1K
router crashes the Cisco ISR router.
Conditions: This symptom is observed with the Cisco ISR G2 router.
Workaround: Remove authentication on the Serial interface on the Cisco ASR router.
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.2(0.19)T0.4 | |
Known Fixed Releases: * | 15.2(0.18)S0.4, 15.2(1)S, 15.2(1)S1, 15.2(1.10)PI18c, 15.2(1.4)S, 15.2(2)SA, 15.2(2)SA1, 15.2(2)SA2, 15.2(2)SNI, 15.2(2.2)T | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCur16675 | Title: | VXML gateway Crash @ms_handle_stream_timer | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
VXML gateway crashes intermittently
Conditions:
UCCE setup with VXML gateway involved.
Workaround:
There is no workaround
Further Problem Description:
| |
Last Modified: | 24-FEB-2016 | |
Known Affected Releases: | 15.2(4)M6 | |
Known Fixed Releases: * | 15.2(4)M7.1, 15.2(4)M8, 15.2(4)S7, 15.3(3)M4.3, 15.3(3)M5, 15.3(3)S4.13, 15.3(3)S5, 15.4(3)M1.1, 15.4(3)M2, 15.4(3)S1.8 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv34342 | Title: | SVIs stay up after shutdown ISR - SM-ES interconnect | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
When shutdown interconnect interface between router and SM-ES module, related SVIs don't bring down but stay up.
Conditions:
Shutting down the router side interconnect interface, let's say Gi1/1 after doing either of followings;
1)
hw-module sm oir-stop
and then without removing the module,
hw-module sm oir-start
2) reload after entering SM console.
Workaround:
None but reloading the router.
Or explicitly shutting down the SVIs
Further Problem Description:
| |
Last Modified: | 22-FEB-2016 | |
Known Affected Releases: * | 15.2(4)M6, 15.5(3)M1.1, 15.6(1)T0.1, 15.6(1.22)T0.1 | |
Known Fixed Releases: | 15.4(3)M4.1, 15.4(3)M5, 15.6(0.25)T, 15.6(1.1)T, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCui79745 | Title: | Crash @ crypto_engine_packet_callback in IPSEC on ISR Codenomicon | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
A vulnerability in IPSec processing of Cisco IOS Software could allow an authenticated, remote attacker to cause a reload of the affected device.
The vulnerability is due to improper processing of malformed IPSec packets. An attacker could exploit this vulnerability by sending malformed IPSec
packets to be processed by an affected device. An exploit could allow the attacker to cause a cause a reload of the affected device.
Conditions:
Cisco IOS device receiving malformed IPSec packets over an established IPSec SA, may crash.
Workaround:
None
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are
6.8/5.6:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:N/AC:L/Au:S/C:N/I:N/A:C/E:F/RL:OF/RC:C&version=2.0
CVE ID CVE-2014-3299 has been assigned to document this issue.
Additional details about the vulnerability described here can be found at:
http://tools.cisco.com/security/center/content/CiscoSecurityNotice/CVE-2014-3299
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: | 18-FEB-2016 | |
Known Affected Releases: | 15.4(0.12)T | |
Known Fixed Releases: * | 15.2(1)SY1.13, 15.2(2)E, 15.2(2.2.73)ST, 15.2(2.2.93)EA, 15.2(2.3)PSR, 15.2(2.39)PSR, 15.2(2b)E, 15.2(3)E, 15.2(4.0)ST, 15.2(4.0.64a)E | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuu82082 | Title: | Memory corruption crash due to cont_scan_display_session | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
We see a lot of '%AP-1-AUTH_PROXY_AUTH_FAILURES_EXCEEDED' logs prior to the crash.
Not sure if they are related for now.
Conditions:
The crash is observed after the following CLI 'sh cws sess active ip-addr all' was executed.
However the crash is not consistently seen with the above CLI.
Workaround:
None
Further Problem Description:
| |
Last Modified: | 18-FEB-2016 | |
Known Affected Releases: | 15.4(3)M1 | |
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.5(3)M1.1, 15.5(3)M2, 15.6(1)T0.1, 15.6(1.12)T, 15.6(1.22.1a)T0 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCux37497 | Title: | Malloc Issues with chunk manager perf_mon_async_cft_create_fo() | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
MALLOCFAIL and CHUNKEXPANDFAIL syslogs seen:
*Dec 1 19:01:52.764: %SYS-2-MALLOCFAIL: Memory allocation of 32768 bytes failed from 0x11B769, alignment 0
Pool: Processor Free: 597780 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
-Process= "Chunk Manager", ipl= 6, pid= 1
-Traceback= 1E7E64Az 115116z 110ACEz 10D56Ez 11B769z 1076CDz 107593z
*Dec 1 19:01:54.704: %DUAL-6-NBRINFO: EIGRP-IPv4 400: Neighbor 10.103.5.1 (GigabitEthernet0/2.99) is blocked: not on common subnet (10.103.8.1/24)
*Dec 1 19:01:54.724: %SYS-2-CHUNKEXPANDFAIL: Could not expand chunk pool for PM CLS HIER. No memory available -Process= "Chunk Manager", ipl= 6, pid= 1
-Traceback= 1E7E64Az 107650z
*Dec 1 19:02:08.492: %DUAL-6-NBRINFO: EIGRP-IPv4 400: Neighbor 10.103.5.1 (GigabitEthernet0/2.99) is blocked: not on common subnet (10.103.8.1/24)
*Dec 1 19:02:18.836: %SYS-2-CHUNKEXPANDFAIL: Could not expand chunk pool for PM CLS HIER. No memory available -Process= "Chunk Manager", ipl= 6, pid= 1
-Traceback= 1E7E64Az 107650z
Conditions:
PFRv3 is configured and traffic of EMIX pattern is run for long duration with very high CPU of 75%.
Workaround:
None
Further Problem Description:
None
| |
Last Modified: | 18-FEB-2016 | |
Known Affected Releases: | 15.5(3)S | |
Known Fixed Releases: * | 15.5(3)M1.1, 15.5(3)M2, 15.6(0.22)S0.12, 15.6(1.12)T, 15.6(1.17)S0.12, 15.6(1.22.1a)T0 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuj50209 | Title: | Memory leak @ voip_rtp_recv_fs_input | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
Customer router crashing due to memory leak.
Conditions:
Memory leak is observed in @voip_rtp_recv_fs_input function.
Workaround:
Reload the Cisco router.
Further Problem Description:
| |
Last Modified: | 17-FEB-2016 | |
Known Affected Releases: | 15.2(3)T2 | |
Known Fixed Releases: * | 15.4(3)M5, 15.4(3)S4.16, 15.5(1.10.1)GB, 15.5(1.15)S, 15.5(1.8)T, 15.5(2)S, 15.6(1)SN | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuw14948 | Title: | HSRP vip ping failure after power off one side Router with SM module | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
HSRP vip ping failure after power off one side Router with SM module
Conditions:
After power off one side Router with SM module, at other side from SM module,
ping physical ip of router there is no problem, but ping vip at router failed.
Workaround:
Reconfig HSRP of the one with ping issue
Further Problem Description:
| |
Last Modified: | 10-FEB-2016 | |
Known Affected Releases: | 15.3(3)M4 | |
Known Fixed Releases: * | 15.3(3)M6.2, 15.3(3)M7, 15.4(3)M4.1, 15.5(3)M1.1, 15.5(3)M2, 15.6(1.6)T, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv80673 | Title: | TTS play not working and call disconnected abruptly | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
User hears the main menu prompt.
If no action is executed within 18 seconds, the call dropped.
Conditions:
The GW is configured as shown below (as per SRDNs):
ip rtcp report interval 3000
gateway
media-inactivity-criteria all
timer receive-rtcp 6
Workaround:
1- Run the following commands:
no ip rtcp report interval 3000
gateway
no timer receive-rtcp 6
2- Increase the rtcp report interval and the multiplier to a number larger than the main menu play back time.
Further Problem Description:
Calls drop if no action is taken within 18 seconds (this number changes based on the rtcp report interval and the multiplier).
Debugs at the GW side show the following:
Aug 11 16:15:57.642 CDT: RTP silence time from DSP recvd Rx = 18000000 msec, Tx = 18000000 msec
Aug 11 16:15:57.642 CDT: voip_rtcp_stats_req: dstAddr=0. RTCP pkts not sent
Aug 11 16:15:57.642 CDT: voip_rtcp_stats_req: rtcp_interval=1103
Aug 11 16:15:57.642 CDT: voip_rtcp_stats_req:delay=55 rtt=0
Aug 11 16:15:57.642 CDT: voip_rtcp_stats_req: rtp_member ptr=0x20F920FC,
rtp stream: previous lost packets=0, current lost packets=0
total lost packets for the call=0
Aug 11 16:15:57.880 CDT: :voip_rtcp_server: Media inactivity disc timer(18000) expired...
Aug 11 16:15:57.880 CDT: //-1/xxxxxxxxxxxx/VOIPRTP:():voip_rtcp_server:
Aug 11 16:15:57.880 CDT: Media inactivity disc timer(18000) expired for callID:8077
Both RTP-RTCP CLI criteria...RTCP | RTP packet found... restarting full timer for 18000
Aug 11 16:15:57.884 CDT: :voip_rtcp_server: Media inactivity disc timer(18000) expired...
Similar as CSCta22840, however, we are running a fixed version
We upgraded the IOS to version 14.4.3M3 and everything works properly, with no configuration changes.
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | 15.2(4.0.1), 15.2(4.1.1) | |
Known Fixed Releases: * | 15.4(3)M3, 15.6(0.17)PI30e, 15.6(0.19)S, 15.6(0.19)T, 15.6(1)SN, 15.6(1.6)S, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCur01171 | Title: | Memory leak in MRCP_CLIENT in add_to_hoststatus_table | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
SIP calls caused MRCP_CLIENT to leak memory
Conditions:
these 3 processes steadily increase memory holding
C3925MCCUBE1#sh proc mem sorted
PID TTY Allocated Freed Holding Getbufs Retbufs Process
379 0 141675176 3712923352 49236032 0 0 CCSIP_SPI_CONTRO
400 0 53990776 304432952 15530048 0 0 MRCP_CLIENT
295 0 2278473520 1587812972 10569436 0 0 http client proc
Workaround:
none
Further Problem Description:
Engineering believes the fix in CSCur07571 might have addressed this issue. The fix of CSCur07571 now available in 152-4-M6 or newer.
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | 15.2(4)M3.11, 15.2(4)M6 | |
Known Fixed Releases: * | 15.3(3)M5.2, 15.3(3)M6, 15.3(3)S5.17, 15.3(3)S6, 15.4(3)M3.1, 15.4(3)M4, 15.4(3)S3.5, 15.4(3)S4, 15.5(2)S1.7, 15.5(2)S2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCum00643 | Title: | CCSIP cause crash when call is established | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
Router experience several crashes during the day.
UTC: %SIP-3-INTERNAL: Corrupted scb
000160: Dec 7 16:30:31.931 UTC: %SYS-2-INTSCHED: 'suspend' at level 0 , all interrupts disabled -Process= "CCSIP_SPI_CONTROL", ipl= 0, pid= 426
Crash was observed while tryig to free the memory allocated for handling the authentication.
showing it as 0X0D0D0D. So crashing while trying to free this memory.
Conditions:
Here crash was seen during the month end when gw was on heavly load. In crasing case first invite was being sent to which got challenged, then later REFER was being sent, but
no response seen, after 7 retattempts REFER is being challenged, but menawhile on other leg already call is seen in disconnecting state and memory realted to authen being freed so while trying to process REFER challenge crash observed.
Workaround:
None
Further Problem Description:
| |
Last Modified: | 05-FEB-2016 | |
Known Affected Releases: | 15.3(3)M | |
Known Fixed Releases: * | 15.3(3)M4, 15.3(3)S3.6, 15.3(3)S4, 15.4(3)M0.3, 15.4(3)M1, 15.4(3)S0.7, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a, 15.5(0.12)S | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuj14595 | Title: | Memory leak in CCSIP_TCP_SOCKET | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom: A Cisco 3945 voice gateway running Cisco IOS Release 15.2(4)M3 or Cisco IOS Release 15.2(4)M4 may have a processor pool memory leak in the CCSIP_TCP_SOCKET process.
Conditions: This symptom is seen on slow TCP connections, where the response is slow and frequent transmission errors are observed.
Workaround: There is no workaround.
| |
Last Modified: | 05-FEB-2016 | |
Known Affected Releases: | 15.2(4)M4.3 | |
Known Fixed Releases: * | 15.2(4)GC3, 15.2(4)M6.3, 15.2(4)M7, 15.2(4)S5.13, 15.2(4)S6, 15.3(3)M3.2, 15.3(3)M4, 15.3(3)S3.4, 15.3(3)S4, 15.4(2.14)T | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCui88426 | Title: | Cisco IOS Software IKEv2 Denial of Service Vulnerability | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
A vulnerability in the Internet Key Exchange Version 2 (IKEv2) module of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause a reload of the affected device that would lead to a denial of service (DoS) condition.
The vulnerability is due to how an affected device processes certain malformed IKEv2 packets. An attacker could exploit this vulnerability by sending malformed IKEv2 packets to an affected device to be processed. An exploit could allow the attacker to cause a reload of the affected device that would lead to a DoS condition.
Although IKEv2 is automatically enabled on a Cisco IOS Software and Cisco IOS XE Software devices when the Internet Security Association and Key Management Protocol (ISAKMP) is enabled, the vulnerability can be triggered only by sending a malformed IKEv2 packet.
Only IKEv2 packets can trigger this vulnerability.
Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate this vulnerability.
This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20140326-ikev2
Note: The March 26, 2014, Cisco IOS Software Security Advisory bundled publication includes six Cisco Security Advisories. All advisories address vulnerabilities in Cisco IOS Software. Each Cisco IOS Software Security Advisory lists the Cisco IOS Software releases that correct the vulnerability or vulnerabilities detailed in the advisory as well as the Cisco IOS Software releases that correct all Cisco IOS Software vulnerabilities in the March 2014 bundled publication.
Individual publication links are in Cisco Event Response: Semiannual Cisco IOS Software Security Advisory Bundled Publication at the following link:
http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_mar14.html
Conditions:
See published Cisco Security Advisory
Workaround:
See published Cisco Security Advisory
Further Problem Description:
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 7.8/6.4:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:N/AC:L/Au:N/C:N/I:N/A:C/E:F/RL:OF/RC:C&version=2.0
CVE ID CVE-2014-2108 has been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
| |
Last Modified: | 04-FEB-2016 | |
Known Affected Releases: | 15.4(0.12)T, 15.4(2)S | |
Known Fixed Releases: * | 15.0(2)EJ1, 15.0(2)EK, 15.0(2)EK1, 15.0(2)EX5, 15.0(2)SE6, 15.1(1)ICA4.122, 15.1(1)SY2.45, 15.1(1)SY3, 15.1(1)XO1, 15.1(1.0.33)XO1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuj38450 | Title: | E1 DS0 group TX IDLE bits intermittently send as 0000 instead of 0001 | |
Status: | Fixed | |
Severity: | 2 Severe | Description: * | Symptom: The router sends IDLE ABCD of 0000 instead of 0001 under certain situations. Customer needs the IDLE bits to always be 0001 for his set up to work with voice.
Conditions: The issue occurs in the following scenarios
1. When the router is reloaded.
2. When we issue a shutdown and no shutdown command under the E1 controller.
3. When the voice-port is issued a shutdown and no shutdown command.
Workaround: Remove and re-add the following commands to the configuration:
connect BEO-Data E1 0/0/0 0 E1 0/0/1 0
connect MFC#1 voice-port 0/1/0 E1 0/0/0 1
connect MFC#2 voice-port 0/1/1 E1 0/0/0 2
More Info:The 3900 router is connected to a PBX line where the two timeslots are used for voice and the rest for data. The end device to which the E1 is connected requires that the 3900 always send IDLE bits as 0001 in order to function correctly. When the 3900 sends IDLE bits as 0000 instead of 0001; the setup stops working and does not send voice and data.
The fix only applied to E&M
| |
Last Modified: | 04-FEB-2016 | |
Known Affected Releases: | 15.3(3)M | |
Known Fixed Releases: * | 15.1(4)M7.3, 15.1(4)M8, 15.1(4)M9, 15.3(3)M1.3, 15.3(3)M2, 15.3(3)M3, 15.3(3)M4, 15.3(3)S1.7, 15.3(3)S2, 15.3(3)S2a | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCue89532 | Title: | Tracebacks are seen after modem call with stcapp services enabled | |
Status: | Fixed | |
Severity: | 2 Severe | Description: * | Symptoms: Tracebacks are seen after modem call.
Conditions: This symptom occurs after modem call with STCAPP services enabled.
Workaround: There is no workaround.
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.3(2.3)T | |
Known Fixed Releases: * | 15.2(1.2.9)PI22, 15.3(2.11)T, 15.3(2.12.1)PIH22, 15.3(2.15.2)XEB, 15.3(2.18)S, 15.3(2.8.2)PIB23, 15.3(3)JA100, 15.3(3)M, 15.3(3)M1, 15.3(3)M2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuf64333 | Title: | DND doesn't give any notification that it was pressed 6945 | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
DND doesn't show any status update unless you are in a hunt group
Conditions:
6945 phone, running 9.3.3.2 and some earlier loads.
Workaround:
None. DND is functioning, but the user can't tell if it is on or off.
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(4.0.1) | |
Known Fixed Releases: * | 15.3(2.18)T, 15.3(2.19)S0.4, 15.3(2.21)PI23, 15.3(2.21.1)PIH22, 15.3(3)M, 15.3(3)M1, 15.3(3)M2, 15.3(3)M3, 15.3(3)S, 15.3(3)S1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCud78362 | Title: | IOS-GW/VXML-GW drops calls after 350 sim calls are setup | |
Status: | Fixed | |
Severity: | 2 Severe | Description: * | Symptom:
Users may experience "no audio" when the router is supposed to be playing IVR (prompt play).
Conditions:
This symptom occurs on the Cisco 3925E and Cisco 3945E platforms when there are more than 350 concurrent prompt plays.
Workaround:
There is no workaround.
Further Problem Description:
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.0(0.1) | |
Known Fixed Releases: * | 15.1(4)M6.4, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M3.5, 15.2(4)M4, 15.2(4)M5 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCud94248 | Title: | SIP Gateway reloads when it gets 400 error response during Fax upspeed | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom: The IOS Gateway reloads when it gets a 400 error response during protocol based fax up-speed.
Conditions: A fax tone detected on the gateway causes it to send a T.38 Fax offer on the SIP leg. However, the remote SIP device is not configured for fax and hence the gateway receives a 400 Bad Request response for the T.38 Fax offer. When responding with an ACK for the 400 Bad Request response, the gateway reloads.
Workaround: Remove the fax configuration at both global and dial-peer level.
Global:
voice service voip
no fax protocol t38
Dial-peer :
dial-peer voice voip
no fax protocol t38
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.1(4)M4 | |
Known Fixed Releases: * | 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M4.3, 15.2(4)M5, 15.2(4)M6, 15.2(4)M6a, 15.2(4)M6b, 15.2(4)S3.16, 15.2(4)S4, 15.2(4)S4a | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCud95940 | Title: | CPUHOG & Watchdog at Skinny Msg Server while running CME & Skinny | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
A Cisco IOS Software device running Cisco Unified Communications Manager Express and Skinny phones could experience
CPU hogs and a watchdog, resulting in a crash.
%SYS-3-CPUHOG: Task is running for (128000)msecs, more than (2000)msecs
(630/222),process = Skinny Msg Server.
-Traceback= 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX
%SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = Skinny Msg Server.
-Traceback= 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX
Conditions:
This symptom is observed with a device running Cisco Unified Communications Manager Express with Skinny phones and Multilevel Precedence and
Preemption (MLPP) disabled.
This problem affects Cisco IOS Software versions 12.4(24)T and later.
Workaround:
A possible mitigation is to enable MLPP.
<B>More Info:</B>
For this bug to be triggered several sequence of events needs to occur before this issue would be observed.
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: | 03-FEB-2016 | |
Known Affected Releases: | 15.1(4)M4 | |
Known Fixed Releases: * | 15.1(4)M6.3, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M3.9, 15.2(4)M4, 15.2(4)M5 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCug38248 | Title: | Watchdog Crash on "CFT Timer" When Unbinding & Deleting Child Flow | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom: Watchdog crash is observed on "Common Flow Table" timer process. For example:
%SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = CFT Timer Process.
Conditions: Error is raised due to a CPU loop while attempting to unbind and delete a child flow in the "CFT Timer" process.
Workaround: There is no workaround.
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.3(2)T | |
Known Fixed Releases: * | 15.0(11.6)EMW, 15.1(1)ICA4.122, 15.2(1)IC273.5, 15.2(2)E, 15.2(4)JB, 15.2(4)JB1, 15.2(4)JB3, 15.2(4)JB3a, 15.2(4)JB3b, 15.2(4)JB3s | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCue06116 | Title: | mgcp/auto-config support on VG350 should be upto max 160 ports | |
Status: | Fixed | |
Severity: | 2 Severe | Description: * | Symptoms: VG350 gateway crashes when the configuration file is downloaded from
CUCM. This occurs when the VG350 has 144 ports configured.
Conditions: The VG350 supports a maximum of 144 FXS ports. Configure MGCP
control and download configuration from CUCM, gateway crashes.
Workaround: Use no ccm-manager config to stop the
configuration download from CUCM.
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(0.0.4)PIL17 | |
Known Fixed Releases: * | 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M2.8, 15.2(4)M3, 15.2(4)M4, 15.2(4)M5, 15.2(4)M6, 15.2(4)M6a, 15.2(4)M6b | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCue05844 | Title: | 3925 crashes when the IP phones registers to the call manager | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
The Cisco 3925 router running Cisco IOS Release 152-4.M2 reloads
when connecting to a call manager Express.
Conditions:
This symptom is observed with the Cisco 3925 router running Cisco
IOS Release 152-4.M2.
Workaround:
Applying the folowing workaround resolves the issue.
no snmp-server enable traps ccme
snmp-server view cutdown iso included
snmp-server view cutdown 1.3.6.1.4.1.9.9.439.1.2 excluded
snmp-server community public view cutdown RO
snmp-server community private view cutdown RW
Further Problem Description:
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(4)M2 | |
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.2(3)GC1, 15.2(3)GCA1, 15.2(3)T3, 15.2(3)T4, 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M2.10, 15.2(4)M3 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCud33159 | Title: | C3925: MPLS traffic is Process switched over ATM interface | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: Excessive loss of MPLS VPN traffic and high CPU utilization is
observed due to the process switching of MPLS traffic over the ATM interface.
Conditions: This symptom occurs when MPLS is enabled on the ATM interface with
aal5snap encapsulation.
Workaround: There is no workaround.
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.0(1)M8.1 | |
Known Fixed Releases: * | 15.0(1)M10, 15.0(1)M9.15, 15.1(1)SY0.1, 15.1(1)SY1, 15.1(1)SY1.32, 15.1(1)SY1.55, 15.1(1)SY1.57, 15.1(1)SY2, 15.1(1)SY3, 15.1(2)SY | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuc96631 | Title: | incoming calls e1r2 stop working n 152-4.M1 | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: Incoming calls through e1 r2 stop working in Cisco IOS Release 15.2(4)M1.
Conditions: This symptom is observed with incoming calls through e1 r2 in Cisco IOS Release 15.2(4)M1. Outgoing calls work fine.
Workaround: Use Cisco IOS Release 15.2(2)T.
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(4)M1 | |
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M2.8, 15.2(4)M3, 15.2(4)M4, 15.2(4)M5, 15.2(4)M6, 15.2(4)M6a | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCud01502 | Title: | Null pointer crash in sipSPIDtmfRelaySipNotifyConfigd | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
A crash occurs in CME while accessing a stream in
sipSPIDtmfRelaySipNotifyConfigd.
Conditions:
This symptom occurs in CME.
Workaround:
There is no workaround.
Further Problem Description:
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2T | |
Known Fixed Releases: * | 15.1(4)M5.18, 15.1(4)M6, 15.2(1.2.3)PI22, 15.2(2)T3.5, 15.2(2)T4, 15.2(3)GC1, 15.2(3)GCA1, 15.2(3)T2.1, 15.2(3)T3, 15.2(4)GC | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtz15274 | Title: | %FLEXDSPRM-3-UNSUPPORTED_CODEC: codec cisco is not supported on dsp T38 | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: When attempting a T.38 fax call on gateway, you may see the following
in the logs:
006902: %FLEXDSPRM-3-UNSUPPORTED_CODEC: codec cisco is not supported on dsp 0/0
006903: %FLEXDSPRM-5-OUT_OF_RESOURCES: No dsps found either locally or globally.
Conditions: The symptom is observed with a T.38 fax call.
Workaround: There is no workaround.
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.1(4)M | |
Known Fixed Releases: * | 15.1(4)M7.1, 15.1(4)M8, 15.1(4)M9, 15.2(1.2.3)PI22, 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M2.6, 15.2(4)M3, 15.2(4)M4 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCua60785 | Title: | Metadata class-map matches only the first match statement for mediatype | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: Metadata class-map matches only the first of the following filter, if
present, in a class map (the other media-type matches are skipped):
match application attribute [category, sub-category, media-type,
device-class] value-string
match application application-group
value-string
Conditions: Seen in a case where the class map has the aforementioned filters.
Workaround: There is no workaround.
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.2(3.8)T | |
Known Fixed Releases: * | 15.1(1)SY0.1, 15.1(1)SY1, 15.1(1)SY1.32, 15.1(1)SY1.55, 15.1(1)SY1.57, 15.1(1)SY2, 15.1(1)SY3, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCua86620 | Title: | Metadata App-ID for vmware incorrect | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: The vmware-view application is not detected/classified.
Conditions: This symptom is observed when vmware-view applications are used.
Workaround: There is no workaround.
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.2(3.16)T | |
Known Fixed Releases: * | 15.1(1)SY0.1, 15.1(1)SY1, 15.1(1)SY1.32, 15.1(1)SY1.55, 15.1(1)SY1.57, 15.1(1)SY2, 15.1(1)SY3, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCua07791 | Title: | CCSIP_SPI_CONTRO mem leak at sipSPI_ipip_update_forked_dialog_remote_tag | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptom:
A Cisco ISR G2 running Cisco IOS Release 15.2(2)T or later shows a memory leak in the CCSIP_SPI_CONTROL process.
Conditions:
Memory leak was observed when router is configured as a Session Initiation Protocol (SIP) gateway and calls experienced media negotiation failure during call setup.
It could take 3-4 weeks for the memory leak to be apparent.
Workaround:
There is no workaround.
Further Problem Description:
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.2(2)T, 15.2(4)S | |
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.2(2)T1.10, 15.2(2)T3, 15.2(2)T4, 15.2(3)GC, 15.2(3)GC1, 15.2(3)GCA, 15.2(3)GCA1, 15.2(3)T1.1, 15.2(3)T2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCty86111 | Title: | Router crashed after "no ccm-manager falback-mgcp" command was entered. | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: The Cisco ISR G2 router crashes after "no ccm-manager fallback-mgcp"
is configured.
Conditions: This symptom is observed with Cisco ISR G2 router.
Workaround: There is no workaround.
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.1(4)M | |
Known Fixed Releases: * | 15.1(4)GC1, 15.1(4)GC2, 15.1(4)M4.3, 15.1(4)M5, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(2)S1.2, 15.2(2)S2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtz22112 | Title: | VXML gateway crash when trying to access a URL. | |
Status: | Fixed | |
Severity: | 2 Severe | Description: | Symptoms: A VXML gateway may crash while parsing through an HTTP packet that
contains the "HttpOnly" field:
//324809//HTTPC:/httpc_cookie_parse: * cookie_tag=' HttpOnly'
//324809//HTTPC:/httpc_cookie_parse: ignore unknown attribute: HttpOnly
Unexpected exception to CPU: vector D, PC = 0x41357F8
Note: The above log was captured with "debug http client all" enabled to
generate additional debugging output relevant to HTTP packet handling.
Conditions: The symptom is observed when an HTTP packet with the "HttpOnly"
field set is received.
Workaround: There is no workaround.
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.1(3.22)T | |
Known Fixed Releases: * | 15.1(4)M5.14, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(2.19)S0.7, 15.2(3.16)T, 15.2(3.30)PIP, 15.2(4)GC, 15.2(4)GC1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCur47925 | Title: | C3945 hangs after error message "%VC_DMA-3-SR_ERROR:" | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
C3945 Router Hangs with "%VC_DMA-3-SR_ERROR:" message
Conditions:
Happens randomly when the router has SM-X-1T3E3 module inserted in the chassis
Workaround:
Reload the router to recover from hang
Further Problem Description:
This behavior is specific to Freescale based platforms (c2951,c3925, c3945) with SM-X-1T3E3 module combination. Accroding to Freescale specification, when it gets
zero sized packets the DMA error will occur and which will prevent any further transaction on DMA channels.
As a result of DMA channel stuck, the network interfaces dependent respective DMA channels go to halt.
| |
Last Modified: | 10-FEB-2016 | |
Known Affected Releases: | 15.2(4)M6 | |
Known Fixed Releases: * | 15.2(4)M9, 15.3(3)M6, 15.4(3)M3.1, 15.4(3)M4, 15.5(3)M1.1, 15.5(3)M2, 15.6(0.2)T, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtw33375 | Title: | CME-SNR-No ringback generated on transferred calls through AA | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: * | Symptom:
An external caller that calls an Auto-Attendant Pilot number hears complete Silence when trying to reach the extension via dial-via-extension when there is SNR applied on the DN of that phone
1. External caller calls auto-attendant pilot.
2. The auto-attendant pilot answers & requests for an extension
3. The external caller presses 5003
4. Extension 5003 at this time is busy with a call.
5. While the call is being transferred, the extn. 5003 is still busy & the external user hears no ringback & there is silence
6. The external caller hangs up
Conditions:
When there is SNR applied to the DN of that phone
Workaround:
Remove SNR from the DN.
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.1(0.0.3)T | |
Known Fixed Releases: * | 15.1(4)GC1, 15.1(4)GC2, 15.1(4)M3.2, 15.1(4)M4, 15.1(4)M5, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.1(4)XB7 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCue87778 | Title: | PFR config crashes 3900E router every 20 minutes, same works on 3945 | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Customer has 2 3900E routers with PFR configured.
Software versions are 152-4.M2 and 152-4.M1.
The routers crashed every 20 minutes.
Conditions:
none
Workaround:
None
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(4)M1, 15.2(4)M2 | |
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)E, 15.2(1)E1, 15.2(1)E2, 15.2(1)E3, 15.2(1)EX0.54, 15.2(1)EY, 15.2(1)IC273.5, 15.2(1.1)EY, 15.2(2)E | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuw54917 | Title: | LMR port stuck in S_TRUNK_PEND after T1/E1 reports LOF | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
The LMR port will stay in S_TRUNK_PEND state after T1/E1 reported LOF. The LMR port can recover by shutdown and no shutdown the LMR port.
Conditions:
LMR port configured in connection trunk setup
Workaround:
none
Further Problem Description:
| |
Last Modified: | 23-FEB-2016 | |
Known Affected Releases: | 15.1(4)M9 | |
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.6, 15.4(3)S5, 15.5(1)S2.19, 15.5(1)S3, 15.5(1)T2.1, 15.5(1)T3, 15.5(2)S2.1, 15.5(2)T2.1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCus65541 | Title: | SIP Ad-hoc hardware conference creator cannot hear others | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Failed conference:
A, B and C IP phones are all internal SIP IP phone which register to the same CME.
1.A call B
2.B pick up
3.A press conference
4.A call C
5.C pick up
6.A press conference
B & C can hear A and each other.
A cannot hear B & C.
Normal conference:
A & C IP phones are internal SIP IP phone which register to the same CME, B is external phone via PSTN (may cellphone or others).
1.A call B
2.B pick up
3.A press conference
4.A call C
5.C pick up
6.A press conference
A, B and C all can hear each other, there are normal.
Conditions:
All SIP IP phone register to a same CME and create a internal Ad-hoc conference.
Customer use c3945 and SW:c3900-universalk9-mz.SPA.154-3.M1.
Workaround:
Do not use dtmf-relay rtp-nte under SIP-phone pool.
Or use software conference or call to PSTN first.
Further Problem Description:
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | 15.4(3)M1, 15.5(1)T | |
Known Fixed Releases: * | 15.5(2.16)T, 15.5(2.16.1)PIH28, 15.5(2.18)PI29a, 15.5(2.21)S0.12, 15.5(2.21)S0.2, 15.5(2.23)S, 15.5(3)S, 15.5(3)S0a, 15.5(3)S1, 15.5(3)S1a | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCut94062 | Title: | Answering Machine tone not detected during AMD / CPA | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
When the gateway is instructed by the ICM Outbound Dialer to conduct call progress analysis and answering machine detection, it will not always "hear" or "see" the answering machine beep/tone.
Conditions:
SIP call with CPA and answer machine detection enable.
Workaround:
N/A
Further Problem Description:
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | n/a | |
Known Fixed Releases: * | 15.4(3)M2.2, 15.4(3)M3, 15.4(3)M3.1, 15.4(3)S2.14, 15.4(3)S3, 15.5(1)S1.1, 15.5(1)S2, 15.5(1)S2.1, 15.5(1)S2.15, 15.5(1)T1.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCux24258 | Title: | Gateway interprets interdigit timeout as no input timeout | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Let the gateway play the prompt , press 1 digit to interrupt the audio. The gateway should wait for inter digit timeout and return the value to CVP. In this case inter digit timeout was 3 seconds.
In IOS 15.4(3)M3 , the gateway waits for 30 seconds( which is no digit timeout ) and then returns the value to CVP.
The behavior is seen only when 1 digit is entered. The gateway works perfectly fine if 2 or more digits are entered.
Conditions:
Issue seen in IOS 15.4(3)M3
Workaround:
Use IOS 15.2(4) M3.
Further Problem Description:
| |
Last Modified: | 23-FEB-2016 | |
Known Affected Releases: | 15.4(3.0p)M3 | |
Known Fixed Releases: * | 15.4(3)M4.1, 15.4(3)M5, 15.4(3)S4.10, 15.4(3)S5, 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.5, 15.5(3)S2, 15.6(0.22)S0.12, 15.6(1)T0.1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCut61279 | Title: | crash with AFW functions during call clearing | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Crash during call clearing with logs similar to below:
12:07:48.969,cgn:912067098599,cdn:7774821279,frs:0,fid:1816968,fcid:8007783D145E014F7F36B204A275C40,legID:1BC302,bguid:8007783D145E014F7F36B2040A275C40
Feb 27 12:19:45 GMT: %ISDN-6-DISCONNECT: Interface Serial0/0/2:3 disconnected from 7774821279 , call lasted 698 seconds
Feb 27 12:19:45 GMT: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 8007783D145E014F7F36B204A275C40, SetupTime 12:07:49.235 GMT Fri Feb 27 2015, PeerAddress 7774821279, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime 12:08:06.845 GMT Fri Feb 27 2015, DisconnectTime 12:19:45.675 GMT Fri Feb 27 2015, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 34928,
Conditions:
call beeing cleared
Workaround:
none
Further Problem Description:
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | 15.1(100.1) | |
Known Fixed Releases: * | 15.3(3)M5.2, 15.3(3)M6, 15.3(3)S5.18, 15.3(3)S6, 15.4(3)M3.1, 15.4(3)M4, 15.4(3)S3.6, 15.4(3)S4, 15.5(2.13)T, 15.5(2.14.1)PIH28 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCut42920 | Title: | RAI targets in VXML gateway | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
RAI target command on gateway has group index limitation of 5.
This is not sufficient for 4000 build as it has 16 CVP servers.
Conditions:
This is seen when configuring the command
rai target resource-group
Workaround:
No work arounds
Further Problem Description:
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | 15.3(2.12.1)T | |
Known Fixed Releases: * | 15.5(2.13)T, 15.5(2.14.1)PIH28, 15.5(2.16.5)PIH28, 15.5(2.20)S, 15.5(3)S, 15.6(1)SN, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCus67448 | Title: | Router crashing on command "show sip call dtmf-relay sip-info" | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Router crash
Conditions:
Executing sip call dtmf-relay sip-info after show sip call command
Workaround:
none
Further Problem Description:
| |
Last Modified: | 06-FEB-2016 | |
Known Affected Releases: | n/a | |
Known Fixed Releases: * | 15.3(3)M6, 15.3(3)S5.19, 15.3(3)S6, 15.4(3)M2.1, 15.4(3)M3, 15.4(3)M3.1, 15.4(3)S2.11, 15.4(3)S3, 15.5(2.13)S, 15.5(2.5)T | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuf20108 | Title: | MRCP Client crashing due to memory issue after a few hundred calls | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Using MRCPv2 on VXML GW for CVP calls to 3rd party ASR, we have found the MRCP Client process is disappearing after a few hundred calls. This causes all future calls to fail until the VXML GW is rebooted.
A traceback is thrown in the logs at this time, indicating a memory problem.
Feb 28 00:23:23.949 JST: %SYS-2-FREEBAD: Attempted to free memory at B0D0B0D, not part of buffer pool
-Traceback= 18B57F4z 2C60B0Cz 5B120B3z 4BCA9F6z 2BCCA09z 4C7692Ez 4BCAA8Bz 4C8D03Fz 4C8EE4Bz 4C85EF2z 4C85D2Fz 4C75A21z
Running 'show process' after this traceback shows the MRCP Client process is no longer running.
Conditions:
The issue occurs when a Nuance server abnormally tears down MRCPv2 session in the middle of the call. MRCPv2 is needed to trigger the crash. MRCPv1 does not cause a crash.
Workaround:
1) Set all sessionTimeout configurations to -1 on the Nuance server (In the NSSserver.cfg file).
2) Use MRCPv1 instead of MRCPv2
Further Problem Description:
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(3)T1 | |
Known Fixed Releases: * | 15.2(1.2.9)PI22, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M4.2, 15.2(4)M5, 15.2(4)M6, 15.2(4)M6a, 15.2(4)M6b, 15.2(4)M7, 15.2(4)S4 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCup27918 | Title: | Voice port stucks in Clearback for E1 R2-digital signalling | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Symptoms:-
Voice port stuck in clearback E1 R2-digital if the PSTN side disconnects the call.
Version:-
c3900-universalk9-mz.SPA.153-2.T1.
Call flow:-
E1R2 -----3945 ----H323----UCM -- Ip phone.
More details:-
++ Call works fine, but if the pstn user hangs up the call first, voice port stucks in clearbak, never becomes idle and call is not cleared.
++ If the call is hung up from IP side, then voice port is not stuck and TDM call-leg is released.
++ Shut/no shut on the port/controller doesn't clear the status, customer has to reboot the router to restore it back.
++ However it works in IOS 152-3.T3, and voice port is properly released.
++ From the debugs, GW after receiving clear bwd, is supposed to send IDLE message back to the provider, but it is not in the non-working case.
Conditions:
When the call is first released from PSTN side.
Workaround:
Configuring Metering under the cas-custom will alleviate the problem. But defintely not a long time workaround. As once PSTN side hangs up the call, it should automatically hang up the IP side as well. But with metering, port will get stuck in Answering state, until IP side user manually hangs up the call, which is not a desired behavior.
Further Problem Description:
Refer summary & symptoms.
| |
Last Modified: | 05-FEB-2016 | |
Known Affected Releases: | 15.3(0.1) | |
Known Fixed Releases: * | 15.4(2)S1.8, 15.4(2)S2, 15.4(2)T1.1, 15.4(2)T2, 15.4(3)M0.3, 15.4(3)M1, 15.4(3)S0.6, 15.4(3)S1, 15.4(3)S2, 15.4(3)SN1a | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuy10250 | Title: | PIM Register decapsulation failure w/ ZBFW | |
Status: | Open | |
Severity: | 3 Moderate | Description: * | Symptom:After decapsulating first register packet, RP ignores second and subsequent Register packets.
Conditions:
Only when First Hop Router, RP, Last Hop Router are connected using a LAN network ie they are all on same network.
RP has same interface for incoming and outgoing packets.
Workaround:
Expected behavior
| |
Last Modified: | 17-FEB-2016 | |
Known Affected Releases: | 15.5(1.20)T | |
Known Fixed Releases: | | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuq25767 | Title: | Shared-line queue cannot released if call is transferd from CUE | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
call from PSTN to FXO and then plar to CUE AA. then AA transfer the call to shared-line extension. the call can answer the call without problem. but after the call hang up, shared-line queue cannot release. this will result in the phone may not accept any incoming call if queue is full.
Conditions:
mixed shared line configured.
Workaround:
Make sure at least one SIP-phone is registered in the mixed-shared line config.
or
Need to remove the shared line and add it back. or reboot the CME to fix the issue.
Further Problem Description:
none
| |
Last Modified: | 05-FEB-2016 | |
Known Affected Releases: | 15.4(2)T1 | |
Known Fixed Releases: * | 12.4(22)YB8, 12.4(24)GC1, 12.4(24)MD, 12.4(24)MDA13, 12.4(24)MDB13, 12.4(24)MDB14, 12.4(24)MDB15, 12.4(24)MDB16, 12.4(24)MDB17, 12.4(24)MDB18 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCux27284 | Title: | MGCP country depedent caller ID table is not up-today | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
The Hungary and Korea are not using ETSI for caller ID.
The India and Saudi Arabia are not using DTMF for caller ID
Conditions:
for mgcp call only
Workaround:
N/A
Further Problem Description:
| |
Last Modified: | 15-FEB-2016 | |
Known Affected Releases: | 15.5(3.0a)M | |
Known Fixed Releases: * | 15.5(3)M1.1, 15.5(3)M2, 15.5(3)S1.1, 15.5(3)S2, 15.6(1.15)S, 15.6(1.9)T, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuo52113 | Title: | High CPU on Gatekeepers during the GUP un-registration operation | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Redundant Gatekeeper setup and high CPU is experienced from time to time during the GUP un-registeration operation.
Conditions:
Traceback= 0x9434BECz 0x942BEC0z 0x942BFE8z 0x942C03Cz 0x9457E08z 0x93FE7CCz 0x94022F0z 0x4DD7EACz 0x4DBDD18z
Workaround:
None
Further Problem Description:
| |
Last Modified: | 05-FEB-2016 | |
Known Affected Releases: | n/a | |
Known Fixed Releases: * | 15.2(4)GC3, 15.2(4)M6.3, 15.2(4)M7, 15.2(4)S5.15, 15.2(4)S6, 15.3(3)M3.2, 15.3(3)M4, 15.3(3)S3.5, 15.3(3)S4, 15.4(2.16)T | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtz54788 | Title: | Cube Crashes during Bulk Audio or Video Call after SSO | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Cube Crashes during Bulk Audio or Video Call after SSO
Conditions:
Cube Crashes during Bulk Audio or Video Call after SSO
Workaround:
Not Known at this moment of Time
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.3TPI | |
Known Fixed Releases: * | 15.2(1.2.3)PI22, 15.3(0.5)T, 15.3(1)S, 15.6(1)SN | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuh66865 | Title: | PVDM3-256 on 3945 reports wrong DSP utilization stats via SNMP | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Incorrect DSP utilization statistics reported by PVDM3-256 DSP's on 3945 chassis either through "show call resource voice stats dsp" command or SNMP poll using CISCO-DSP-MGMT-MIB. The two OID's affected are:
cdspInUseChannels
cdspActiveChannels
Conditions:
Normal operation.
Workaround:
None
Further Problem Description:
| |
Last Modified: | 04-FEB-2016 | |
Known Affected Releases: | 28.3(8)DSP | |
Known Fixed Releases: * | 12.2(31)SB15, 12.2(31)SB16, 12.2(31)SB17, 12.2(31)SGA10, 12.2(31)SGA11, 12.2(33)IRC, 12.2(33)MRA, 12.2(33)SB14, 12.2(33)SB15, 12.2(33)SB16 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtx76030 | Title: | Gateway is responding with 200 ok without SDP to the invite | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Gateway doesnt respond with SDP in the 200 ok for the re-invite from the SIP server
Conditions:
Call flow
Mobile phone---T1--->Cisco GW--->SIPServer(NLB)----> Polycom SIP Phone
When ever the polycom SIP phone puts a call on hold a re-invite is sent to the GW. However when needed to resume the call back the Gateway does not send SDP in the 200 ok to the re-invite making the call to fail
Workaround:
None
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.3(1)S | |
Known Fixed Releases: * | 15.0(1)M10, 15.0(1)M8.8, 15.0(1)M9, 15.1(4)GC1, 15.1(4)GC2, 15.1(4)M4.12, 15.1(4)M5, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtz38876 | Title: | Rekey SA not created when ipv6 crypto map applied to tunnel interface | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
When crypto map is applied to a tunnel interface, the GM can not register to KS and can not be initialized. This problem is specific to tunnel interface.
Conditions:
The crypto map is applied to a tunnel interface
Workaround:
none
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.2(3.7)T | |
Known Fixed Releases: * | 15.1(1)SY, 15.1(1)SY1, 15.1(1)SY2, 15.1(1)SY3, 15.1(2)SY, 15.1(2)SY1, 15.1(2)SY2, 15.1(2)SY3, 15.2(2)E, 15.2(2.19)S0.6 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtt17490 | Title: | %GDOI-5-COOP_KS_REACH is shown too early | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
GetVPN setup with KS1 and KS2, KS1 shows the following message:
Aug 25 10:44:21.968: %GDOI-5-COOP_KS_REACH: Reachability restored with Cooperative KS 10.30.0.21 in group bw600.
This log message is shown after ISAKMP phase 1 is established, but the GetVPN COOP connectivity has not yet been restored, as KS2 has no GDOI configuration.
Conditions:
In a GetVPN KS-COOP scenario, KS1 is up and KS2 is newly added.
ISAKMP is configured, but the GDOI configuration is still missing on KS2.
KS1 will still show the GDOI-5-COOP_KS_REACH message, what is wrong.
Workaround:
No workaround available.
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 12.4(15)T13 | |
Known Fixed Releases: * | 15.0(2)EJ, 15.0(2)EJ1, 15.0(2)EX, 15.0(2)EX1, 15.0(2)EX3, 15.0(2)EX4, 15.0(2)EX5, 15.0(2)EZ, 15.0(2)SE1, 15.0(2)SE2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCur66196 | Title: | OvrTh value is wrong in enhanced-history distribution stats | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
OvrTh value is wrong in enhanced-history distribution stats
Conditions:
Cisco 3900 running 15.1(3)T4
Workaround:
Verify the over threshold operations using "show ip sla statistics"
Further Problem Description:
| |
Last Modified: | 23-FEB-2016 | |
Known Affected Releases: | 15.1(3)T4 | |
Known Fixed Releases: * | 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.3(1)IE101.187, 15.5(1.13)T, 15.5(2)S, 15.5(2.1)S, 16.1(0.5), 7.0(0)BZ(0.98), 7.0(3)I2(0.47) | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCts38501 | Title: | SSO: OOD Options Ping doesnt work after SSO is committed | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: * | Symptom:
Options Ping is not sent after switchover from Active to Stanby.
Conditions:
- HA Switchover from Active to Standby
Workaround:
No work around
| |
Last Modified: | 02-FEB-2016 | |
Known Affected Releases: | 15.2(4)S | |
Known Fixed Releases: * | 15.1(3)S5, 15.1(3)S5a, 15.1(3)S6, 15.1(3)S7, 15.2(2)S1.2, 15.2(2)S2, 15.2(2.19)S0.7, 15.2(3)GC, 15.2(3)GC1, 15.2(3)GCA | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCty67525 | Title: | ISR-CTS: IP-SGT mapping doesnt take effect after reload in 3945e | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
FW drops the traffic from legitimate ip due to sgt match failure
Conditions:
1. Configure an IP-SGT mapping manually via the cli ''cts role-based sgt-map sgt
'' on a 3945e.
2. Have a firewall (FW) policy to match the security-group tag.
3. Save the configs and reload the router
Workaround:
Unconfigure the sgt mapping and reconfigure it.
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
Further Problem Description:
| |
Last Modified: | 04-FEB-2016 | |
Known Affected Releases: | 15.2(3.2)T | |
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(2)E, 15.2(2b)E, 15.2(4.0)ST, 15.2(4.0.64a)E, 15.2(5.0)ST, 15.4(0.19)S0.6, 15.4(0.24)T, 15.4(1)CG, 15.4(1)CG1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCub63208 | Title: | Memory corruption detected in memory, when allocated for RTCP statistic | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Getting error below
CALL_CONTROL-3-STAT_MEMORY_CORRUPTED: Memory corruption detected in memory=XYZ allocated for RTCP statistic
Conditions:
Call involve trans-coding
Workaround:
None
| |
Last Modified: | 29-FEB-2016 | |
Known Affected Releases: | 15.0(1)M8.1 | |
Known Fixed Releases: * | 15.0(1)M10, 15.0(1)M9.11, 15.1(4)M5.10, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(1.2.3)PI22, 15.2(4)GC, 15.2(4)GC1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuu77844 | Title: | 3945E with EHWIC-1GE-SFP-CU/ GLC-LH-SMD= not suppport DOM | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
3945E with EHWIC-1GE-SFP-CU/ GLC-LH-SMD=
when use 155.2.T will got below:
show int tran detail:
Module 0 doesn't support DOM
Conditions:
HW:3945E/EHWIC-1GE-SFP-CU/ GLC-LH-SMD=
SW:c3900e-universalk9-mz.SPA.155-2.T.bin
Workaround:
no workaround
Further Problem Description:
first time the software is c3900e-universalk9-mz.SPA.153-3.M5.bin<<<
second time the software is c3900e-universalk9-mz.SPA.155-2.T.bin<<<
no other change.
when the cu first time use show interface tran detail got below :
first time
Transmit Power Threshold Threshold Threshold Threshold
Port (dBm) (dBm) (dBm) (dBm) (dBm)
---------- ----------------- ---------- --------- --------- ---------
Gi0/0/0 --2147483648.-2 -0.0 --2147483648.-2 --2147483648.-2 --2147483648.-2 <<<<<< this number is
second time got below :
3F-N5-20-C3945-A#show interfaces Gi0/0/0 transceiver
Module 0 doesn't support DOM
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.5(2)T | |
Known Fixed Releases: * | 15.3(3)M6.2, 15.3(3)M7, 15.4(3)M3.2, 15.4(3)M4, 15.5(2)T2, 15.5(3)M0.2, 15.5(3)M1, 15.6(0.4)T, 15.6(1.9)T0.1, 15.6(1.9)T0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtu16841 | Title: | FAX pass-through the VAD needs to be turned off | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: * |
Symptom:
The vad option displayed under "show voice call summary" output has to be 'n' when the call goes to
FAX Passthrough mode.
Conditions:
Workaround:
This bug does not affect the actual call and the performance.
Further Problem Description:
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: * | 15.1(4)M1 | |
Known Fixed Releases: * | 12.4(24)MDA13, 12.4(24)T10, 12.4(24)T11, 12.4(24)T12, 12.4(24)T7, 12.4(24)T8, 12.4(24)T9, 15.0(1)M10, 15.0(1)M7.14, 15.0(1)M8 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCuv09635 | Title: | H320 gateway strips rtp marker bits | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: | Symptom:
Choppy or pixelated video
Conditions:
H320 call flow when newer mcu code or dx endpoints are used.
Workaround:
run older mcu code, no workaround for dx endpoints
Further Problem Description:
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.4(3) | |
Known Fixed Releases: * | 15.2(4)M9, 15.3(3)M6.2, 15.3(3)M7, 15.4(2)T4, 15.4(3)M3.2, 15.4(3)M4, 15.5(1)T2.1, 15.5(1)T3, 15.5(2)T2, 15.5(3)M0.2 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCtt06317 | Title: | Tracebacks found at ccsip_spi_kpml_notify_callback | |
Status: | Fixed | |
Severity: | 3 Moderate | Description: * | Symptom:
router crashed during debug on live production network. deb voice ccapi all and isdn q931 were turn "On". tracebacks were observed before crash
Conditions:
normal
Workaround:
none
| |
Last Modified: | 01-FEB-2016 | |
Known Affected Releases: | 15.1(3)T | |
Known Fixed Releases: * | 15.1(4)M5.10, 15.1(4)M6, 15.1(4)M7, 15.1(4)M8, 15.1(4)M9, 15.2(1.17)S, 15.2(2)S, 15.2(2.8)T, 15.2(3)GC, 15.2(3)GC1 | |
|
| | | | |
Alert Type: | Updated * | Bug Id: | CSCue32024 | Title: | [Cisco3945E] The sequence of config was automatically changed. | |
Status: | Fixed | |
Severity: | 4 Minor | Description: | Symptom:
[Cisco3945E] Configuration was automatically changed after reload.
Conditions:
Topo:
[C3945E]Gi0/0 -3<>Gi0/0 -3[Router]
SW:
c3900e-universalk9-mz.SPA.152-4.XB9
Chassis:
CISCO3945-CHASSIS
Slot0:
C3900-SPE250/K9
Configuration:
Please see & configure the attached file "config.txt".
Issue:
About the following part in configuration,
If reconfigured after deleted them and reload the device,
The sequence of configuration was automatically changed.
Please check the following info.
1.
Current Situation+++++++++++++++++++++++++++++++
router lisp
security
locator-set WAN
IPv4-interface Port-channel1.602 priority 1 weight 100
IPv6-interface Port-channel1.602 priority 1 weight 100
auto-discover-rlocs
exit
+++++++++++++++++++++++++++++++++++++++++++++
Apply the following config.
------------------------------------------------------------------------
router lisp
security
locator-set WAN
no IPv4-interface Port-channel1.602 priority 1 weight 100
no IPv6-interface Port-channel1.602 priority 1 weight 100
auto-discover-rlocs
exit
router lisp
security
locator-set WAN
IPv4-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
IPv6-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
auto-discover-rlocs
exit
------------------------------------------------------------------------
Current Situation+++++++++++++++++++++++++++++++
router lisp
security
locator-set WAN
IPv6-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
IPv4-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
auto-discover-rlocs
exit
+++++++++++++++++++++++++++++++++++++++++++++
After "write memory"&"reload", use "show run | be router lisp" and confirm the current situation.
Current Situation+++++++++++++++++++++++++++++++
router lisp
security
locator-set WAN
IPv4-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
IPv6-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
auto-discover-rlocs
exit
+++++++++++++++++++++++++++++++++++++++++++++
2.
Apply the following config on the above situation.
------------------------------------------------------------------------
router lisp
security
locator-set WAN
no IPv4-interface Port-channel1.602 priority 1 weight 100
no IPv6-interface Port-channel1.602 priority 1 weight 100
auto-discover-rlocs
exit
router lisp
security
locator-set WAN
IPv6-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
IPv4-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
auto-discover-rlocs
exit
------------------------------------------------------------------------
Current Situation+++++++++++++++++++++++++++++++
router lisp
security
locator-set WAN
IPv4-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
IPv6-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
auto-discover-rlocs
exit
+++++++++++++++++++++++++++++++++++++++++++++
After "write memory"&"reload", use "show run | be router lisp" and confirm the current situation.
Current Situation+++++++++++++++++++++++++++++++
router lisp
security
locator-set WAN
IPv6-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<<
IPv4-interface Port-channel1.602 priority 1 weight 100 <<<<<<<<<&l
| |
Last Modified: | 03-FEB-2016 | |
Known Affected Releases: | 15.2(4)XB9 | |
Known Fixed Releases: * | 15.1(1)ICA4.122, 15.2(1)IC273.13, 15.2(4)XB11, 15.3(3)XB12, 15.4(0.2)S, 15.4(0.5)T, 15.4(1)CG, 15.4(1)CG1, 15.4(1)S, 15.4(1)S0a | |
|
| |
|
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论