Specifications

Caveats for Cisco IOS Release 12.0

78-6455-12

Resolved Caveats—Cisco IOS Release 12.0(6)

All the caveats listed in this section are resolved in Cisco IOS Release 12.0(6). This section describes

severity 1 and 2 caveats and select severity 3 caveats.

Access Server

• CSCdm42611

MICA Technologies portware parameters are extended to support V110, along with other newly

planned activities. The current Cisco IOS modem management MICA event handler does not

handle event sizes beyond what the current version of Cisco IOS supports. If a new version of

portware is added to an older version of IOS that does not support the new functionality, these event

are dropped. There is no workaround.

• CSCdm50856

The result of the show modem command on a Cisco AS5200 access server is different from the

snmpwalk command of the cmInitialLineConnections variable defined in

CISCO-MODEM-MGMT-MIB. There is no workaround.

Basic System Services

• CSCdk80230

Certain Internetwork Status Monitor (ISM) NetView users can issue non-enable mode commands

without router authentication. Users accessing the router through NetView must be authenticated

through the NetView security methods, that might include RACF and SAF. Mainframe users can be

restricted from issuing any router commands through the restriction of the RUNCMD within

NetView. Users issuing enable mode commands must be authorized to issue this level of command

through ISM, and must possess the enable mode password. If the router is controlled by TACACS+,

the ISM user must have a TACACS+ user ID and password

• CSCdm33841

The entity-physical table on a Cisco 7200 series router does not contain an entry for the network

processing engine (NPE) card. There is no workaround.

• CSCdm41368

A Cisco MC3810 multiservice access concentrator Ethernet output interface might enter a wedged

state during which no traffic is transmitted from the router. This condition only occurs if a series of

multiple or late collisions are detected on the Ethernet connection.

Typically, it is not common to see a high number of late collisions on an ethernet environment. If

you do, this might indicate extreme network utilization, ethernet network exceeding specifications,

or possibly a bad port or cabling.

The condition can be detected by issuing the show interface ethernet 0 command on the Ethernet

port. The symptom is that the output queue appears to be full (40/40), and output queue drops

continue to increment. The following error message is displayed when the excessive collisions are

detected:

3810-analog-4#show interface ethernet 0 Ethernet0 is up, line protocol is up Hardware

is PQUICC Ethernet, address is 0010.7b09.c62a (bia 0010.7b09.c62a) Internet address is

172.16.173.5/26 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255,

txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set ARP type: ARPA, ARP