| |
|
Alert Type: | Updated * |
Bug Id: | CSCub16372 | Title: | Very rarely, ISR-G2 IOS cannot boot up with certain ROMMON versions |
|
Status: | Fixed |
|
Severity: | 1 Catastrophic |
Description: * | Symptoms: In extremely rare cases, an ISR-G2 cannot boot up with certain ROMMON
versions with the error "Signature did not verify". So far, only one image is
found to have this problem: c3900-universalk9-mz.SPA.152-1.T3.bin.
Conditions: The issue will happen when all three conditions are met at the same
time:
1. The platform is affected.
2. The ROMMON version running at the router is within the affected ROMMON
version range.
3. The first calculated hash value is 0 during the IOS image building process.
Since it is extremely rare that the third condition will occur, so far only one
CCO image is found to have this problem.
Workaround: Upgrading ROMMON to the latest version of 15.0(1r)M16 or 151(1r)T5
will fix the issue completely.
The ROMMON upgrade can be done using one single CLI command in the router's
enable mode:
Router# upgrade rom-monitor file flash:
is the ROMMON file name for the specific platform that is
downloadable from CCO. For example, C3900_RM2.srec.SPA.150-1r.M16 is the
latest ROMMON version for C39xx platforms located at CCO download site:
http://www.cisco.com/cisco/software/release.html?
mdfid=282774222&flowid=7437&softwareid=280805687&release=15.0%281r%
29M16&relind=AVAILABLE&rellifecycle=&reltype=latest.
|
|
Last Modified: | 29-JUN-2016 |
|
Known Affected Releases: * | 15.2(1)T3, 15.2(3.16)M0.7 |
|
Known Fixed Releases: | 15.2(4)GC, 15.2(4)GC1, 15.2(4)GC2, 15.2(4)M1.6, 15.2(4)M2, 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: | CSCuy32360 | Title: | Crash after Quiet mode is triggered with login block-for configured |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
A crash is seen on a router that has login block-for configured. The crash occurs after Quiet mode is triggered:
C3900#
*Feb 13 03:37:06.767: %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: cats] [Source: xx.xx.xx.xx [localport: 22] [Reason: Login Authentication Failed] at 03:37:06 UTC Sat Feb 13 2016
*Feb 13 03:37:06.767: %SEC_LOGIN-1-QUIET_MODE_ON: Still timeleft for watching failures is 52 secs, [user: cats] [Source: xx.xx.xx.xx] [localport: 22] [Reason: Login Authentication Failed] [ACL: login] at 03:37:06 UTC Sat Feb 13 2016
*Feb 13 03:37:12.791: %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: cats] [Source: xx.xx.xx.xx] [localport: 22] [Reason: Login Authentication Failed] at 03:37:12 UTC Sat Feb 13 2016
*Feb 13 03:37:12.791: %SEC_LOGIN-1-QUIET_MODE_ON: Still timeleft for watching failures is 0 secs, [user: cats] [Source: 10.24.1.190] [localport: 22] [Reason: Login Authentication Failed] [ACL: 8"d
#G
] at 03:37:12 UTC Sat Feb 13 2016
chunk_diagnose, code = 3
chunk name is MallocLite
Conditions:
SSH authetication failures occur after either using the wrong username or password. If another attempt is made quick enough (around the same time as quiet mode should be triggered) a crash could occur. The issue only seems to occur if the device has not been reloaded since the login block-for configuration has been added.
Workaround:
1) Remove login block-for configurations
2) Save the configs and reload. The issue doesn't seem to occur again after a reload/crash.
Further Problem Description:
When the configs are saved and device is reloaded, the configs are added in a specific order that prevents the issue. We have found that the order of the configs added is what is allowing the issue to occur. As long as the configs are in the following order, the issue will not happen:
ip access-list extended login
deny ip any any
login block-for <#> attempts <#> within <#>
login delay <#>
login quiet-mode access-class login
login on-failure log
login on-success log
|
|
Last Modified: | 16-JUN-2016 |
|
Known Affected Releases: | 15.6(1.22)T |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.6(2)T0.1, 15.6(2.12.1a)T0, 15.6(2.3)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtj34110 | Title: | No precedence ring for phone called by SCCP-analog for 3-way call |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
During three-way call creation, a SCCP-controlled analog endpoint is unable to initiate a precedence call after a hookflash. Precedence digits are accepted, but routine ring and routine ringback is observed.
Conditions:
Call Scenario:
1. Phone1 (IP) calls Phone2 (SCCP-controlled analog).
2. Phone2 performs hookflash, dials a Priority call to Phone3 (IP).
3. Phone3 rings at Routine precedence and Phone2 receives Routine ringback.
Workaround:
No workaround exists.
|
|
Last Modified: | 09-JUN-2016 |
|
Known Affected Releases: | 15.1(1)T1 |
|
Known Fixed Releases: * | 15.1(1)T2.1, 15.1(2)T2.3, 15.1(3)T0.3, 15.1(3)T1, 15.1(3)T2, 15.1(3)T3, 15.1(3)T4, 15.1(3.8)T, 15.1(4)GC1, 15.1(4)GC2 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy43787 | Title: | EHWIC-1GE-SFP auto media type is not working properly |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
A EHWIC-1GE-SFP containing a 1000baseT SFP may result in the link staying down/down and the configured speed/duplex being automatically changed.
Conditions:
The EHWIC-1GE-SFP must not have a media type manually configured and the card must have a 1000baseT SFP installed along with a working ethernet connection on the builtin RJ45 port. The interface must be manually configured for 100/Full duplex. When the problem occurs (normally after a reboot) the running configuration will automatically change to 1000/Full and the link will stay down/down.
Workaround:
Manually set the preferred media type using the command "media-type sfp" or "media-type RJ45".
Further Problem Description:
|
|
Last Modified: | 16-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.6(1)T1.1, 15.6(2)T0.1, 15.6(2.12.1a)T0, 15.6(2.3)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtj33218 | Title: | Three-way call with secure IPv6 EIs has one-way audio after preemption |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
Voice path for IP phone endpoints participating in a three-way call over a T1 PRI is one-directional after an endpoint opposite the PRI is preempted.
Conditions:
This behavior does not occur with analog phones.
Behavior occurs with the following call scenario:
1. Phone1 (remote side of PRI) makes Routine call over PRI to Phone2 (SCCP IP phone registered to CME).
2. Phone2 makes local Priority call to Phone3 (SCCP IP phone registered to CME), then establishes a 3-way call with Phone1 and Phone3.
3. Phone4 (remote side of PRI) makes local Immediate call to Phone1. Phone2 and Phone3 hear conference disconnect, and only have one-way voice after the tone finishes.
Workaround:
No workaround exists.
|
|
Last Modified: | 08-JUN-2016 |
|
Known Affected Releases: | 15.1(1)T1 |
|
Known Fixed Releases: * | 15.1(1)T2.3, 15.1(1)T3, 15.1(1)T4, 15.1(1)T5, 15.1(2)T2.2, 15.1(2)T3, 15.1(2)T4, 15.1(2)T5, 15.1(3)T0.2, 15.1(3)T1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCtj33331 | Title: | BPA doesn't play for call made over T1 PRI to MGCP-controlled gateway |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Blocked precedence announcement (BPA) doesn't play to IP phones registered to CUCME when calling across a PRI.
Conditions:
The cause of the BPA (such as a higher precedence call) must be on the remote side of the PRI. A local CME-controlled phone must then attempt to call the remote phone unable to take the call. BPA should be played to the user, but is not.
Workaround:
No workaround exists.
|
|
Last Modified: | 08-JUN-2016 |
|
Known Affected Releases: | 15.1(1)T1 |
|
Known Fixed Releases: * | 15.1(1)T2.2, 15.1(2)T2.3, 15.1(3)T0.2, 15.1(3)T1, 15.1(3)T2, 15.1(3)T3, 15.1(3)T4, 15.1(3.11)T, 15.1(3.8.7)PIB, 15.1(4)GC1 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz10760 | Title: * | SIP SRST phone registration issues. |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
SIP Phones do not register with the SRST router
Conditions:
+When around 1300 SIP phones failover to SRST, most of them fail to register
+The SRST router shows that (most of the) phones as registered
+When SRST is simulated with only a few phones, all works well
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 30-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz63038 | Title: | Trunk group race condition generates CCAPI IEC software error |
|
Status: * | Other |
|
Severity: * | 3 Moderate |
Description: | Symptom:
gateway generates IEC=1.1.180.1.13.114 system message when trunk group configuration is used
Conditions:
appears when trunk group commands are used
Workaround:
remove trunk group and configure using dial-peer & port configuration
Further Problem Description:
|
|
Last Modified: | 13-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M4.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw24061 | Title: | HWIC-2FE no "%LINK-3-UPDOWN" logs when oir cable or sh/no shu peer port |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
There are no "%LINK-3-UPDOWN" logs output on HWIC-2FE interface , when oir cable or sh/no sh peer interface.
Conditions:
oir cable or sh/no sh peer interface
Workaround:
there is no workaround.
Further Problem Description:
none
|
|
Last Modified: | 16-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M2.2 |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.6(1)T1.1, 15.6(2)T0.1, 15.6(2.1)T, 15.6(2.12.1a)T0 |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuy21368 | Title: | Shaper and interface counters does not take into account L2 PAD field |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: * | Symptom:
"Show interface" may show output utilization level, that does not match real traffic rate on the link.
Real rate may be much higher, then the reported one.
Conditions:
Device is routing tiny L3 payload (less than 42 bytes) and have to add L2 padding to meet minimum frame size requirements (64 bytes).
Workaround:
N/A
Further Problem Description:
|
|
Last Modified: | 29-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M3.2 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux48676 | Title: | 3900e limits the amount of dialer interfaces to 255 |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
The Cisco 3900e platform restricts the amount of dialer interfaces to 255. Other platforms within the ISR-G2 family allow up to 3000 dialer intefaces. The total amount of dialer interfaces allowed can be seen in the "interface dialer" configuration help:
3945E(config)#inter dialer ?
<0-255> Dialer interface number
Conditions:
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 16-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M3.2 |
|
Known Fixed Releases: * | 15.5(3)M2.1, 15.6(2)T0.1, 15.6(2.12.1a)T0, 15.6(2.4)T |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuz63004 | Title: | Trunk group command causes CCAPI race condition |
|
Status: | Open |
|
Severity: * | 4 Minor |
Description: | Symptom:
gateway generates IEC=1.1.180.1.13.114 system message;
Conditions:
Trunk group configuration used
Workaround:
Remove trunk group and use per dial-peer, per port, per destination
Further Problem Description:
|
|
Last Modified: | 30-JUN-2016 |
|
Known Affected Releases: | 15.4(3)M4.1 |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuj29485 | Title: | Informer shows SFP Vender-ID instead of PID when using "show inventory" |
|
Status: * | Other |
|
Severity: | 4 Minor |
Description: | Symptom:
Informer shows SFP Vender-ID instead of PID when using "show inventory"
Conditions:
Informer c3945e loaded with Cisco IOS release 15.3(03)M
Workaround:
None
|
|
Last Modified: | 13-JUN-2016 |
|
Known Affected Releases: | 15.3(3)M |
|
Known Fixed Releases: | |
|
|
| |
:
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论