Cisco Cisco IOS Software Release 12.2(4)YB
24
Release Notes for the Cisco 1700 Series Routers for Cisco IOS Release 12.2(4)YB
OL-2342-07
Caveats
Caveats
Caveats describe unexpected behavior or defects in Cisco IOS software releases. Severity 1 caveats are
the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious
of these three severity levels.
the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious
of these three severity levels.
Caveats in Release 12.2 T are also in Release 12.2(4)YB. For information on caveats in Cisco IOS
Release 12.2 T, refer to the
Release 12.2 T, refer to the
Caveats for Cisco IOS Release 12.2 T
document. For information on caveats
in Cisco IOS Release 12.2, refer to the
Caveats for Cisco IOS Release 12.2
document. These documents
list severity 1 and 2 caveats, and are located on CCO and the Documentation CD.
Note
If you have an account with Cisco.com, you can also use the Bug Toolkit to find select caveats of any
severity. To reach the Bug Toolkit, log in toCisco.com and click Service & Support: Technical
Assistance Center: Tool Index: Bug Toolkit. Another option is to go to
severity. To reach the Bug Toolkit, log in toCisco.com and click Service & Support: Technical
Assistance Center: Tool Index: Bug Toolkit. Another option is to go to
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl
.
Resolved Caveats - Release 12.2(4)YB
This section describes unexpected behavior that is fixed in Release 12.2(4)YB.
Management
CSCdw65903
An error can occur with management protocol processing. Please use the following URL for
further information:
further information:
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
Unresolved Caveats - Release 12.2(4)YB
This section describes unexpected behavior in Release 12.2(4)YB.
Miscellaneous
CSCdv87983
Booting a Cisco 1700 series router using the command boot system tftp might not work due to
insufficient memory. To work around this problem, use the command tftpdnld from the ROM monitor.
insufficient memory. To work around this problem, use the command tftpdnld from the ROM monitor.
Multiservice Applications
CSCdw86539
To properly shutdown MGCP, first shut the voice port associated with MGCPAPP and then issue the
command no mgcp. If the voice port is not shut, issuing the command no mgcp causes MGCP processes
to shut down incorrectly. This has been observed when RQNT with embedded notifications is issued by
the call agent.
command no mgcp. If the voice port is not shut, issuing the command no mgcp causes MGCP processes
to shut down incorrectly. This has been observed when RQNT with embedded notifications is issued by
the call agent.