Specifications

107
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(4)
Resolved Caveats—Cisco IOS Release 12.0(4)
All the caveats listed in this section are resolved in Cisco IOS Release 12.0(4). This section describes
severity 1 and 2 caveats and select severity 3 caveats.
Access Server
• CSCdk11064
If DTR is low on a line to which a Microcom modem is attached (for example, because
modem dtr-active is configured on the line), CSM nonetheless routes the call to the modem. The
result, given the default Microcom modem configuration of “&D,” is a “ring-no-answer.” Compare
the behavior with MICA modems (if DTR is low), then CSM refrains from routing the call to the
modem. The result is that if no modems are available and have high DTR, the caller wins a busy.
This means that there is no general way to configure Microcom modems for dial-out only. (If the
NAS is connected to the network through ISDN rather than CAS, then you can configure DNIS
modem pooling and put the dial-out-only modems into a pool with an unused DNIS number.
However, this technique does not work for CAS, because DNIS modem pooling is not supported
for Microcom modems.)
Workaround: Use MICA modems instead of Microcom modems.
• CSCdk72998
The following changes have been made to the rs_async_clearoutput() function to prevent the router
shelf from reloading under high load conditions:
– The call to crashdump(0) has been removed.
– Instead of calling crashdump(0), only a warning message is issued for the case that should not
happen. The router shelf should never reload when there is a failure to allocate a particle buffer.
– The particle buffer allocation strategy has also been changed so that instead of returning all
particle buffers and then trying to allocate a new one, not all the particle buffers are returned.
If there were (n) particle buffers, only (n-1) are returned. By keeping the last one, it avoids a
call to rs_async_get_particle(), which could fail to allocate a new particle buffer.
• CSCdk80119
A Cisco AS5200 access server that is configured for pri-group can hang during boot (and only
during boot) if one or both of the T1 and E1 interfaces receives excessive “short frame” errors (also
known as runts) from the lines. This problem might occur where there is an unprovisioned PRI line,
or an incorrectly provisioned PRI line.
Workaround: Disconnect the faulty T1 or E1 line, or configure loopback on the affected T1 or E1
controller.
• CSCdm00811
Malloc failures might be seen on a Cisco AS5300 access server when virtual templates are
configured under heavy stress conditions.
Workaround: Configure the input hold queue size on virtual template to 10.