InfoBlast Home

Table of Contents

Release Notes for Cisco IOS Release 11.1

Release Notes for Cisco IOS Release 11.1

Release Notes for Cisco IOS Release 11.1

October 28, 1996

These release notes describe the features and caveats for Cisco Internetwork Operating System (Cisco IOS) Release 11.1, up to and including Release 11.1(7). They include all routing and access server features.


Introduction

These release notes discuss the following topics:


Documentation

For Cisco IOS Release 11.1, we combined the Access Server software documentation set with the Router software documentation to reduce duplication and make information easier to access. Furthermore, we divided the Cisco IOS documentation set into six modules, each module consisting of a configuration guide and a command reference. The books and chapter topics are as follows:

Books Chapter Topics
· Configuration Fundamentals Configuration Guide
· Configuration Fundamentals Command Reference 		Access Server and Router Product Overview
User Interface
Loading System Images and Configuration Files
Setup Command
Interfaces
System Management
· Access Services Configuration Guide
· Access Services Command Reference 		Terminal Lines and Modem Support
AppleTalk Remote Access
SLIP and PPP
XRemote
LAT
Telnet
TN3270
Protocol Translation
· Wide-Area Networking Configuration Guide
· Wide-Area Networking Command Reference 		ATM
Dial-on-Demand Routing (DDR)
Frame Relay
ISDN
LANE
SMDS
X.25
· Network Protocols Configuration Guide, Part 1
· Network Protocols Command Reference, Part 1 		AppleTalk
IP
IP Routing
Novell IPX
· Network Protocols Configuration Guide, Part 2
· Network Protocols Command Reference, Part 2 		Apollo Domain
Banyan VINES
DECnet
ISO CLNS
XNS
· Bridging and IBM Networking Configuration Guide
· Bridging and IBM Networking Command Reference 		Transparent Bridging
Source-Route Bridging
Remote Source-Route Bridging
DLSw+
STUN and BSTUN
LLC2 and SDLC
IBM Network Media Translation
DSPU and SNA Service Point Support
SNA Frame Relay Access Support
APPN
IBM Channel Attach
· Cisco IOS Software Command Summary
· Cisco Management Information Base (MIB) User Quick Reference
· System Error Messages
· Debug Command Reference
· Cisco Access Connection Guide

These documents are available as printed manuals or electronic documents.

For electronic documentation of Release 11.1 router and access server software features, available on the Cisco Connection Documentation, Enterprise Series CDs, refer to the Cisco IOS Release 11.1 configuration guides and command references, which are located in the Cisco IOS Release 11.1 database.

You can also access Cisco technical documentation on the World Wide Web at http://www.cisco.com .


Platform Support

Cisco IOS Release 11.1(7) supports the following router platforms:

Table 1 and Table 2 summarize the LAN interfaces supported on each platform.

Table 3 and Table 4 summarize the WAN data rates and interfaces supported on each platform.

Table 1 LAN Interfaces Supported by Router Platforms, Part 1
Interface Cisco 7500 Series Cisco 7200 Series Cisco 7000 Series Cisco 4000 Series Cisco 3000 Series1 Cisco 2500 Series
Ethernet (AUI) Yes Yes Yes Yes Yes Yes
Ethernet (10BaseT) Yes Yes Yes Yes No Yes 2
Ethernet (10BaseFL) Yes Yes Yes3
Fast Ethernet (100BaseTX) Yes Yes Yes3 No No No
Fast Ethernet (100BaseFX) Yes Yes Yes No No No
4-Mbps Token Ring Yes Yes Yes Yes Yes Yes
16-Mbps Token Ring Yes Yes Yes Yes Yes Yes
FDDI DAS Yes Yes Yes Yes No No
FDDI SAS Yes No Yes Yes No No
FDDI multimode Yes Yes Yes Yes (DAS/
SAS) 		No No
FDDI single-mode Yes Yes Yes Yes No No
ATM Interface Yes No Yes Yes No No
Channel Interface Yes No Yes No No No
Second-Generation Channel Interface 4 Yes No Yes No No No
Parallel Channel Adapter (Bus and Tag) Yes No Yes No No No
ESCON Channel Adapter (ECA) Yes No Yes No No No
Versatile Interface Yes No Yes No No No
Second-Generation Versatile Interface 2 Yes No Yes No No No
MultiChannel Interface (Channelized E1/T1) Yes No Yes Yes No No
Packet-Over-SONET OC-3 Interface2 Yes No Yes Yes No No
Synchronous Serial Yes Yes Yes Yes Yes Yes

1 Except the Cisco 3202.
2 Cisco2505, Cisco2507, Cisco2516, Cisco2518, and Cisco2520 Cisco2525 only.
3 May require the 7000 series Route Switch Processor (RSP7000).
4 In the Cisco 7000 series routers (Cisco 7000 and Cisco 7010), these interfaces require the 7000 series Route Switch Processor (RSP7000) and the 7000 series chassis interface (RSP7000CI).

Table 2 LAN Interfaces Supported by Router Platforms, Part 2
Interface Cisco 1003/
1004 		Cisco 1005 Cisco 1000 LAN Extender Access-
Pro PC Card 		Cisco AS5100 Cisco AS5200
Ethernet (AUI) No No Yes No Yes Yes
Ethernet (10BaseT) Yes Yes Yes Yes No No
Ethernet (10BaseFL) No
Fast Ethernet (100BaseTX) No No No No No No
Fast Ethernet (100BaseFX) No No No No No No
4-Mbps Token Ring No No No Yes No No
16-Mbps Token Ring No No No Yes No No
FDDI DAS No No No No No No
FDDI SAS No No No No No No
FDDI multimode No No No No No No
FDDI single-mode No No No No No No
ATM Interface No No No No No No
Channel Interface No No No No No No
Second-Generation Channel Interface No No No No No No
Parallel Channel Adapter (Bus and Tag) No No No No No No
ESCON Channel Adapter (ECA) No No No No No No
Versatile Interface No No No No No No
Second-Generation Versatile Interface No No No No No No
MultiChannel Interface (Channelized E1/T1) No No No No No Yes
Packet-Over-SONET OC-3 Interface No No No No No No
Synchronous Serial No No No No Yes Yes

Table 3 WAN Data Rates and Interfaces Supported by Router Platforms, Part 1
Cisco 7500 Series Cisco 7200 Series Cisco 7000 Series Cisco 4000 Series Cisco 3000 Series1 Cisco 2500 Series
Data Rate
48/56/64 kbps Yes Yes Yes Yes Yes Yes
1.544/2.048 Mbps Yes Yes Yes Yes Yes Yes
34/45/52 Mbps Yes Yes No No No
Interface
EIA/TIA-232 Yes Yes Yes Yes Yes Yes
X.21 Yes Yes Yes Yes Yes Yes
V.35 Yes Yes Yes Yes Yes Yes
EIA/TIA-449 Yes Yes Yes Yes Yes Yes
EIA-530 Yes Yes Yes Yes Yes Yes
EIA/TIA-613 (HSSI) Yes No Yes No No No
ISDN BRI No No No Yes Yes Yes
ISDN PRI Yes No Yes Yes No No
E1-G.703/G.704 Yes No Yes Yes No No

1 Except the Cisco 3202.

Table 4 WAN Data Rates and Interfaces Supported by Router Platforms, Part 2
Cisco 1003/
1004 		Cisco 1005 Cisco 1000 LAN Extender Access-Pro PC Card Cisco AS5100 Cisco AS5200
Data Rate
48/56/64 kbps Yes Yes Yes Yes Yes Yes
1.544/2.048 Mbps No Yes Yes Yes Yes Yes
34/45/52 Mbps No No No No No No
Interface
EIA/TIA-232 No Yes No Yes Yes Yes
X.21 No Yes Yes Yes Yes Yes
V.35 No Yes Yes Yes Yes Yes
EIA/TIA-449 No Yes No Yes Yes Yes
EIA-530 No Yes No Yes Yes Yes
EIA/TIA-613 (HSSI) No No No No No No
ISDN BRI Yes Yes No Yes No No
ISDN PRI No No No No No Yes
E1-G.703/G.704 No No No No No Yes


Cisco IOS Packaging

The Cisco IOS software is available in different feature sets depending upon the platform. Table 5 lists the feature sets and optional licenses for the Cisco 7500 series. Table 6 lists the feature sets for the Cisco 7200 series. Table 7 lists the feature sets and optional licenses for the Cisco 7000 series. Table 8 and Table 9 list the feature sets for the Cisco 2500 series and AS5100. Table 10 lists the feature sets for the Cisco AS5200. Table 11 lists the features sets for the Cisco 4000 series, which includes the Cisco 4000, Cisco 4000-M, Cisco 4500, Cisco 4500-M, and Cisco 4700 routers. Table 12 lists the feature sets for the Cisco 3000 series. Table 13 lists the software for the Cisco 1003 and Cisco 1004 ISDN routers. Table 14 lists the software for the Cisco 1005 router.

Table 5 Cisco 7500 Series Software
Feature IP IP/IPX/
IBM 		IP/IPX/
IBM/
APPN 		Desktop/
IBM 		Enter-
prise 		Enter-
prise/
APPN 		IP/VIP IP/IPX/
IBM/
VIP 		IP/IPX/
IBM/
APPN/VIP 		Desktop/IBM/VIP Enter-
prise/
VIP 		Enter-
prise/
APPN/
VIP
SNMP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RMON (events and alarms) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Asynchronous support (SLIP) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Frame Relay Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
SMDS Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
X.25 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
ISDN Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
PPP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
HDLC Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
IP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIPv2 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
OSPF Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
BGP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
EGP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
PIM Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
NHRP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
ES-IS Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
IS-IS Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Snapshot routing Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
NTP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Transparent bridging Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Translational bridging Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Multiring Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
LAN extension host Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
IPX --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
NLSP --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
IPXWAN 2.0 --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
AppleTalk Versions 1
and 2 		--- --- --- Yes Yes Yes --- --- --- Yes Yes Yes
AURP --- --- --- Yes Yes Yes --- --- --- Yes Yes Yes
DECnet IV --- --- --- Yes Yes Yes --- --- --- Yes Yes Yes
DECnet V --- --- --- --- Yes Yes --- --- --- --- Yes Yes
Apollo Domain --- --- --- --- Yes Yes --- --- --- --- Yes Yes
Banyan VINES --- --- --- --- Yes Yes --- --- --- --- Yes Yes
ISO CLNS --- --- --- --- Yes Yes --- --- --- --- Yes Yes
XNS --- --- --- --- Yes Yes --- --- --- --- Yes Yes
Lock-and-Key Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
MD5 routing authentication Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Kerberized login --- --- --- --- Yes Yes --- --- --- --- Yes Yes
TACACS+ --- --- --- --- Yes Yes --- --- --- --- Yes Yes
RADIUS --- --- --- --- Yes Yes --- --- --- --- Yes Yes
V.120 --- --- --- --- Yes Yes --- --- --- --- Yes Yes
SRB --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
RSRB --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
APPN --- --- --- --- --- Yes --- --- --- --- --- Yes
FRAS BAN --- --- --- --- Yes Yes --- --- --- --- Yes Yes
DLSw (RFC 1795) --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
DLSw+ --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
SDLC --- --- Yes --- Yes Yes --- --- Yes --- Yes Yes
SDLLC --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
SRT bridging --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
STUN --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
TG/COS --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
QLLC --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
DSPU --- Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
NetView Native Service Point --- --- --- --- Yes Yes --- --- --- --- Yes Yes
Protocol translation --- --- --- --- Yes Yes --- --- --- --- Yes Yes
Telnet Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
PAD --- --- --- --- Yes Yes --- --- --- --- Yes Yes
AutoInstall --- --- Yes Yes Yes Yes --- --- Yes Yes Yes Yes
Router monitoring --- --- --- --- Yes Yes --- --- --- --- Yes Yes
High System Availability (HSA) --- --- --- --- --- --- Yes Yes Yes Yes Yes Yes
DHCP --- --- --- --- Yes Yes --- --- --- --- Yes Yes

Table 6 Cisco 7200 Series
Feature Network Layer 3 Switching Desktop/IBM Enterprise Enterprise/APPN
SNMP Yes Yes Yes Yes
RMON (events and alarms) Yes Yes Yes Yes
Asynchronous support (SLIP) Yes Yes Yes Yes
Frame Relay --- Yes Yes Yes
SMDS Yes Yes Yes Yes
X.25 Yes Yes Yes Yes
ISDN --- Yes Yes Yes
PPP --- Yes Yes Yes
HDLC --- Yes Yes Yes
IP Yes Yes Yes Yes
RIP Yes Yes Yes Yes
RIPv2 Yes Yes Yes Yes
IGRP Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes
OSPF Yes Yes Yes Yes
BGP Yes Yes Yes Yes
EGP Yes Yes Yes Yes
PIM Yes Yes Yes Yes
NHRP Yes Yes Yes Yes
Policy-based routing Yes Yes Yes Yes
ES-IS --- --- Yes Yes
IS-IS --- --- Yes Yes
DDR --- Yes Yes Yes
Snapshot routing --- Yes Yes Yes
NTP Yes Yes Yes Yes
Transparent bridging Yes Yes Yes Yes
Translational bridging Yes Yes Yes Yes
Concurrent routing and bridging Yes Yes Yes Yes
Multiring Yes Yes Yes Yes
LAN extension host Yes Yes Yes Yes
ISL Yes --- --- ---
GRE --- Yes Yes Yes
IPX Yes Yes Yes Yes
NLSP Yes Yes Yes Yes
IPX RIP Yes Yes Yes Yes
RTMP Yes Yes Yes Yes
IPXWAN 2.0 --- Yes Yes Yes
AppleTalk Versions 1
and 2 		--- Yes Yes Yes
AURP Yes Yes Yes Yes
SMRP Yes Yes Yes Yes
SRTP --- --- Yes Yes
DECnet IV --- Yes Yes Yes
DECnet V --- --- Yes Yes
OSI --- --- Yes Yes
Apollo Domain --- --- Yes Yes
Banyan VINES --- --- Yes Yes
ISO CLNS --- --- Yes Yes
XNS --- --- Yes Yes
Lock-and-Key Yes Yes Yes Yes
MD5 routing authentication Yes Yes Yes Yes
Kerberized login --- --- Yes Yes
TACACS+ Yes Yes Yes Yes
RADIUS Yes Yes Yes Yes
V.120 --- --- Yes Yes
SRB1 --- Yes Yes Yes
RSRB --- Yes Yes Yes
APPN --- --- --- Yes
FRAS BAN --- Yes Yes Yes
DLSw (RFC 1795) --- Yes Yes Yes
DLSw+2 --- Yes Yes Yes
SDLC --- Yes Yes Yes
SDLLC --- Yes Yes Yes
SRT bridging --- Yes Yes Yes
STUN --- Yes Yes Yes
TG/COS --- --- Yes Yes
QLLC --- Yes Yes Yes
DSPU --- --- Yes Yes
NetView Native Service Point --- Yes Yes Yes
Protocol translation --- --- Yes Yes
Telnet Yes Yes Yes Yes
Modem auto-configuring Yes Yes Yes Yes
PAD --- --- Yes Yes
AutoInstall Yes Yes Yes Yes
Router monitoring --- --- Yes Yes
DHCP --- --- Yes Yes

1 SRB over FDDI is not supported in this release.
2 DLSw+ over TCP/IP is supported.

Table 7 Cisco 7000 Series
Feature IP IP/IPX/
IBM 		IP/IPX/
IBM/
APPN 		Desk-
top/
IBM 		Enter-
prise 		Source
Route
Switch1 		Enter-
prise/
APPN2 		IP/VIP IP/IPX/
IBM/
VIP 		IP/IPX/
IBM/
APPN/VIP 		Desk-
top/
IBM/
VIP 		Enter-
prise/
VIP 		Enter-
prise/
APPN/
VIP
SNMP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RMON (events and alarms) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Asynchronous support (SLIP) Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
Frame Relay Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
SMDS Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
X.25 Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
ISDN Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
PPP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
HDLC Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
IP Yes Yes Yes Yes Yes Yes (host only) Yes Yes Yes Yes Yes Yes Yes
RIP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
RIPv2 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
IGRP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
OSPF Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
BGP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
EGP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
PIM Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
NHRP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
ES-IS Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
IS-IS Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
Snapshot routing Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
NTP Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
Transparent bridging Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Translational bridging Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
Multiring Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
LAN extension host Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
IPX --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
NLSP --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
IPXWAN 2.0 --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
AppleTalk Versions 1 and 2 --- --- --- Yes Yes --- Yes --- --- --- Yes Yes Yes
AURP --- --- --- Yes Yes --- Yes --- --- --- Yes Yes Yes
DECnet IV --- --- --- Yes Yes --- Yes --- --- --- Yes Yes Yes
DECnet V --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
Apollo Domain --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
Banyan VINES --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
ISO CLNS --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
XNS --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
Lock-and-
Key 		Yes Yes Yes Yes Yes Yes Yes --- --- --- Yes Yes Yes
MD5 routing authentication Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Kerberized login --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
TACACS+ --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
RADIUS --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
V.120 --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
SRB Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RSRB Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
APPN --- --- --- --- --- --- Yes --- --- --- --- --- Yes
FRAS BAN --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
DLSw
(RFC 1795) 		--- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
DLSw+ --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
SDLC --- --- Yes --- Yes --- Yes --- --- Yes --- Yes Yes
SDLLC --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
SRT bridging --- Yes Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes
STUN --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
TG/COS --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
QLLC --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
DSPU --- Yes Yes Yes Yes --- Yes --- Yes Yes Yes Yes Yes
NetView Native Service Point --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
Protocol translation --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
Telnet Yes Yes Yes Yes Yes --- Yes Yes Yes Yes Yes Yes Yes
PAD --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes
AutoInstall --- --- Yes Yes Yes --- Yes --- --- Yes Yes Yes Yes
Router monitoring --- --- --- --- Yes Yes Yes --- --- --- --- Yes Yes
DHCP --- --- --- --- Yes --- Yes --- --- --- --- Yes Yes

1 The Source-Route Switch feature set applies to the Cisco 7000 and Cisco7010 only
2 The Enterprise/APPN feature set applies to the Cisco 7000 and Cisco 7010 only.

Table 8 Cisco 2500 Series and AS5100 Software Feature Sets, Part 1

Feature 		Feature Set
IP IP/RMON IP/IBM
Base 		IP/IBM/
RMON 		IP/IPX IP/IPX/
RMON 		IP/IPX/
IBM Base 		IP/IPX/IBM/RMON IP/IPX/IBM/
APPN
SNMP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RMON1 --- Yes --- Yes --- Yes --- Yes ---
Asynchronous support (SLIP) Yes Yes Yes Yes Yes Yes Yes Yes Yes
CSLIP Yes Yes Yes Yes Yes Yes Yes Yes Yes
ARAP --- --- --- --- --- --- --- --- ---
Frame Relay Yes Yes Yes Yes Yes Yes Yes Yes Yes
SMDS Yes Yes Yes Yes Yes Yes Yes Yes Yes
X.25 Yes Yes Yes Yes Yes Yes Yes Yes Yes
ISDN Yes Yes Yes Yes Yes Yes Yes Yes Yes
PPP Yes Yes Yes Yes Yes Yes Yes Yes Yes
CPPP Yes Yes Yes Yes Yes Yes Yes Yes Yes
HDLC Yes Yes Yes Yes Yes Yes Yes Yes Yes
IP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIPv2 Yes Yes Yes Yes Yes Yes Yes Yes Yes
IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
OSPF Yes Yes Yes Yes Yes Yes Yes Yes Yes
BGP Yes Yes Yes Yes Yes Yes Yes Yes Yes
EGP Yes Yes Yes Yes Yes Yes Yes Yes Yes
PIM Yes Yes Yes Yes Yes Yes Yes Yes Yes
NHRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
ES-IS --- --- --- --- --- --- --- --- ---
IS-IS --- --- --- --- --- --- --- --- ---
Snapshot routing Yes Yes Yes Yes Yes Yes Yes Yes Yes
NTP Yes Yes Yes Yes Yes Yes Yes Yes Yes
Bridging (transparent and translational) Yes Yes Yes Yes Yes Yes Yes Yes Yes
Multiring Yes Yes Yes Yes Yes Yes Yes Yes Yes
LAN extension host Yes Yes Yes Yes Yes Yes Yes Yes Yes
IPX --- --- --- --- Yes Yes Yes Yes Yes
NLSP --- --- --- --- Yes Yes Yes Yes Yes
IPXWAN 2.0 --- --- --- --- Yes Yes Yes Yes Yes
RTMP --- --- --- --- --- --- --- --- ---
SMRP --- --- --- --- --- --- --- --- ---
SRTP --- --- --- --- --- --- --- --- ---
AppleTalk Versions 1 and 2 --- --- --- --- --- --- --- --- ---
AURP --- --- --- --- --- --- --- --- ---
DECnet IV --- --- --- --- --- --- --- --- ---
DECnet V --- --- --- --- --- --- --- --- ---
Apollo Domain --- --- --- --- --- --- --- --- ---
Banyan VINES --- --- --- --- --- --- --- --- ---
ISO CLNS --- --- --- --- --- --- --- --- ---
XNS --- --- --- --- --- --- --- --- ---
Lock-and-Key Yes Yes Yes Yes Yes Yes Yes Yes Yes
MD5 routing authentication Yes Yes Yes Yes Yes Yes Yes Yes Yes
Kerberized login --- --- --- --- --- --- --- --- ---
V.120 --- --- --- --- --- --- --- --- ---
SRB --- --- Yes Yes --- --- Yes Yes Yes
RSRB --- --- Yes Yes --- --- Yes Yes Yes
APPN --- --- --- --- --- --- --- --- Yes
FRAS BAN --- --- Yes Yes --- --- Yes Yes Yes
DLSw (RFC 1795) --- --- Yes Yes --- --- Yes Yes Yes
DLSw+ --- --- Yes Yes --- --- Yes Yes Yes
SDLC --- --- Yes Yes --- --- Yes Yes Yes
SDLLC --- --- Yes Yes --- --- Yes Yes Yes
STUN --- --- Yes Yes --- --- Yes Yes Yes
TG/COS --- --- --- --- --- --- --- --- ---
QLLC --- --- Yes Yes --- --- Yes Yes Yes
Bisync --- --- Yes Yes --- --- Yes Yes Yes
DSPU --- --- --- --- --- --- --- --- ---
NetView Native Service Point --- --- Yes Yes --- --- --- Yes Yes
Protocol translation --- --- --- --- --- --- --- --- ---
TN3270 --- --- --- --- --- --- --- --- ---
LAT --- --- --- --- --- --- --- --- ---
SRT Bridging --- --- Yes Yes --- --- Yes Yes Yes
XRemote --- --- --- --- --- --- --- --- ---
Telnet Yes Yes Yes Yes Yes Yes Yes Yes Yes
PAD Yes Yes Yes Yes
AutoInstall Yes Yes Yes Yes Yes Yes Yes Yes Yes
Modem auto- configuring --- --- --- --- --- --- --- --- ---
Router monitoring Yes Yes Yes Yes Yes Yes Yes Yes Yes
DHCP Yes Yes Yes Yes Yes Yes Yes Yes Yes
NASI --- --- --- --- --- --- --- --- ---
NetBEUI over PPP --- --- --- --- --- --- --- --- ---

1 All feature sets include RMON alarm and events groups. Full, nine-group RMON support is included in the feature sets indicated.

Table 9 Cisco 2500 Series and AS5100 Software Feature Sets, Part 2

Feature 		Feature Set
Desktop Desktop/
IBM Base 		Enterprise Enterprise/RMON Enterprise/APPN CFRAD Remote Access Server ISDN LAN
FRAD
SNMP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RMON1 --- --- --- Yes --- None --- ---
Asynchronous support (SLIP) Yes Yes Yes Yes Yes Yes Yes Yes Yes
CSLIP Yes Yes Yes Yes Yes Yes Yes Yes Yes
ARAP Yes Yes Yes Yes Yes --- Yes --- ---
Frame Relay Yes Yes Yes Yes Yes Yes Yes --- Yes
SMDS Yes Yes Yes Yes Yes --- --- --- ---
X.25 Yes Yes Yes Yes Yes --- Yes --- ---
ISDN Yes Yes Yes Yes Yes --- --- Yes ---
PPP Yes Yes Yes Yes Yes Yes Yes Yes Yes
CPPP Yes Yes Yes Yes Yes Yes Yes Yes Yes
HDLC Yes Yes Yes Yes Yes --- Yes --- Yes
IP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIPv2 Yes Yes Yes Yes Yes Yes Yes Yes
IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
OSPF Yes Yes Yes Yes Yes --- --- Yes ---
BGP Yes Yes Yes Yes Yes --- Yes Yes ---
EGP Yes Yes Yes Yes Yes --- --- Yes ---
PIM Yes Yes Yes Yes Yes --- Yes Yes ---
NHRP Yes Yes Yes Yes Yes --- --- Yes ---
ES-IS --- --- Yes Yes Yes --- --- --- ---
IS-IS --- --- Yes Yes Yes --- --- --- ---
Snapshot routing Yes Yes Yes Yes Yes --- Yes Yes ---
NTP Yes Yes Yes Yes Yes --- Yes --- ---
Bridging (transparent and translational) Yes Yes Yes Yes Yes --- --- Yes Yes
Multiring Yes Yes Yes Yes Yes --- Yes Yes Yes
LAN extension host Yes Yes Yes Yes Yes --- --- --- ---
IPX Yes Yes Yes Yes Yes --- Yes Yes Yes
NLSP Yes Yes Yes Yes Yes --- --- --- ---
IPXWAN 2.0 Yes Yes Yes Yes Yes --- Yes --- Yes
RTMP Yes Yes Yes Yes Yes --- Yes --- ---
SMRP Yes Yes Yes Yes Yes --- Yes --- ---
SRTP --- --- Yes Yes Yes --- Yes --- ---
AppleTalk Versions 1 and 2 Yes Yes Yes Yes Yes --- Yes Yes ---
AURP Yes Yes Yes Yes Yes --- Yes Yes ---
DECnet IV Yes Yes Yes Yes Yes --- --- --- ---
DECnet V --- --- Yes Yes Yes --- --- --- ---
Apollo Domain --- --- Yes Yes Yes --- --- --- ---
Banyan VINES --- --- Yes Yes Yes --- --- --- ---
ISO CLNS --- --- Yes Yes Yes --- --- --- ---
XNS --- --- Yes Yes Yes --- --- --- ---
Lock-and-Key Yes Yes Yes Yes Yes Yes Yes Yes
MD5 routing authentication Yes Yes Yes Yes Yes Yes Yes Yes
Kerberized login --- --- Yes Yes Yes --- --- ---
V.120 --- --- Yes Yes Yes --- --- ---
SRB --- Yes Yes Yes Yes --- --- --- Yes
RSRB --- Yes Yes Yes Yes Yes --- --- Yes
APPN --- --- --- --- Yes --- --- --- ---
FRAS BAN --- Yes Yes Yes Yes Yes --- ---
DLSw
(RFC 1795) 		--- Yes Yes Yes Yes Yes --- --- Yes
DLSw+ --- Yes Yes Yes Yes --- --- --- ---
SDLC --- Yes Yes Yes Yes Yes --- --- Yes
SDLLC --- Yes Yes Yes Yes Yes --- --- Yes
STUN --- Yes Yes Yes Yes Yes --- --- Yes
TG/COS --- --- Yes Yes Yes --- --- --- ---
QLLC --- Yes Yes Yes Yes --- --- --- ---
Bisync --- Yes Yes Yes Yes Yes --- --- Yes
DSPU --- --- Yes Yes Yes --- --- --- ---
NetView Native Service Point --- Yes Yes Yes Yes Yes --- ---
Protocol translation --- --- Yes Yes Yes --- Yes --- ---
TN3270 --- --- Yes Yes Yes --- Yes --- ---
LAT --- --- Yes Yes Yes --- Yes --- ---
SRT Bridging --- Yes Yes Yes Yes --- --- ---
XRemote --- --- Yes Yes Yes --- Yes --- ---
Telnet Yes Yes Yes Yes Yes Yes Yes Yes Yes
PAD Yes Yes Yes Yes
AutoInstall Yes Yes Yes Yes Yes Yes Yes --- Yes
Modem auto configuration --- --- Yes Yes Yes --- Yes ---
Router monitoring Yes Yes Yes Yes Yes Yes Yes Yes Yes
DHCP Yes Yes Yes Yes Yes --- Yes Yes ---
NASI --- --- --- --- --- --- Yes ---
NetBEUI over PPP --- --- --- --- --- --- Yes ---

1 All feature sets except CFRAD include RMON alarm and events groups. Full, nine-group RMON support is included in the feature sets indicated.

Table 10 Cisco AS5200 Software Feature Sets

Feature 		Feature Set
IP/Managed Modems Desktop/
Managed Modems 		Enterprise/RMON/
Managed Modems
SNMP Yes Yes Yes
RMON1 --- --- Yes
Asynchronous support (SLIP) Yes Yes Yes
CSLIP Yes Yes Yes
ARA Protocol --- Yes Yes
Frame Relay Yes Yes Yes
SMDS Yes Yes Yes
X.25 Yes Yes Yes
ISDN Yes Yes Yes
PPP Yes Yes Yes
CPPP Yes Yes Yes
HDLC Yes Yes Yes
IP Yes Yes Yes
RIP Yes Yes Yes
RIPv2 Yes Yes Yes
IGRP Yes Yes Yes
Enhanced IGRP Yes Yes Yes
OSPF Yes Yes Yes
BGP Yes Yes Yes
EGP Yes Yes Yes
PIM Yes Yes Yes
NHRP Yes Yes Yes
ES-IS --- --- Yes
IS-IS --- --- Yes
Snapshot routing Yes Yes Yes
NTP Yes Yes Yes
Bridging (transparent and translational) Yes Yes Yes
Multiring Yes Yes Yes
LAN extension host Yes Yes Yes
IPX --- Yes Yes
NLSP --- Yes Yes
IPXWAN 2.0 --- Yes Yes
RTMP --- Yes Yes
SMRP --- Yes Yes
SRTP --- --- Yes
AppleTalk Versions 1 and 2 --- Yes Yes
AURP --- Yes Yes
DECnet IV --- Yes Yes
DECnet V --- --- Yes
Apollo Domain --- --- Yes
Banyan VINES --- --- Yes
ISO CLNS --- --- Yes
XNS --- --- Yes
Lock-and-Key Yes Yes Yes
MD5 routing authentication Yes Yes Yes
Kerberized login --- --- Yes
V.120 --- --- Yes
SRB --- --- Yes
RSRB --- --- Yes
APPN --- --- ---
FRAS BAN --- --- Yes
DLSw (RFC 1795) --- --- Yes
DLSw+ --- --- Yes
SDLC --- --- Yes
SDLLC --- --- Yes
STUN --- --- Yes
TG/COS --- --- Yes
QLLC --- --- Yes
Bisync --- --- Yes
DSPU --- --- Yes
NetView Native Service Point --- --- Yes
Protocol translation --- --- Yes
TN3270 --- --- Yes
LAT --- --- Yes
SRT bridging --- --- Yes
XRemote --- --- Yes
Telnet Yes Yes Yes
PAD Yes Yes Yes
AutoInstall Yes Yes Yes
Modem autoconfiguring --- --- Yes
Router monitoring Yes Yes Yes
DHCP Yes Yes Yes
NASI --- --- ---
NetBEUI over PPP --- --- ---
RADIUS Yes Yes Yes
Modem Management Yes Yes Yes

1 All feature sets include RMON alarm and events groups. Full, nine-group RMON support is included in the feature sets indicated.

Table 11 Cisco 4000 Series Software Feature Sets

Feature 		Feature Set
IP IP/IBM Base IP/IPX IP/IPX/
IBM Base 		IP/IPX/
IBM/
APPN 		Desktop Desktop/
IBM Base 		Enterprise Enterprise/APPN
SNMP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RMON (events and alarms) Yes Yes Yes Yes Yes Yes Yes Yes Yes
Asynchronous support (SLIP) Yes Yes Yes Yes Yes Yes Yes Yes Yes
ARAP --- --- --- --- --- Yes Yes Yes Yes
Frame Relay Yes Yes Yes Yes Yes Yes Yes Yes Yes
SMDS Yes Yes Yes Yes Yes Yes Yes Yes Yes
X.25 Yes Yes Yes Yes Yes Yes Yes Yes Yes
ISDN Yes Yes Yes Yes Yes Yes Yes Yes Yes
PPP Yes Yes Yes Yes Yes Yes Yes Yes Yes
HDLC Yes Yes Yes Yes Yes Yes Yes Yes Yes
IP Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIP Yes Yes Yes Yes Yes Yes Yes Yes Yes
IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
OSPF Yes Yes Yes Yes Yes Yes Yes Yes Yes
BGP Yes Yes Yes Yes Yes Yes Yes Yes Yes
EGP Yes Yes Yes Yes Yes Yes Yes Yes Yes
PIM Yes Yes Yes Yes Yes Yes Yes Yes Yes
NHRP Yes Yes Yes Yes Yes Yes Yes Yes Yes
ES-IS --- --- --- --- --- --- --- Yes Yes
IS-IS --- --- --- --- --- --- --- Yes Yes
Snapshot routing Yes Yes Yes Yes Yes Yes Yes Yes Yes
NTP Yes Yes Yes Yes Yes Yes Yes Yes Yes
Bridging (transparent and translational) Yes Yes Yes Yes Yes Yes Yes Yes Yes
Multiring Yes Yes Yes Yes Yes Yes Yes Yes Yes
LAN extension host Yes Yes Yes Yes Yes Yes Yes Yes Yes
IPX --- --- Yes Yes Yes Yes Yes Yes Yes
NLSP --- --- Yes Yes Yes Yes Yes Yes Yes
RTMP --- --- --- --- --- Yes Yes Yes Yes
SMRP --- --- --- --- --- Yes Yes Yes Yes
SRTP --- --- --- --- --- --- --- Yes Yes
IPXWAN 2.0 --- --- Yes Yes Yes Yes Yes Yes Yes
AppleTalk Versions 1 and 2 --- --- --- --- --- Yes Yes Yes Yes
AURP --- --- --- --- --- Yes Yes Yes Yes
DECnet IV --- --- --- --- --- Yes Yes Yes Yes
DECnet V --- --- --- --- --- --- --- Yes Yes
Apollo Domain --- --- --- --- --- --- --- Yes Yes
Banyan VINES --- --- --- --- --- --- --- Yes Yes
ISO CLNS --- --- --- --- --- --- --- Yes Yes
XNS --- --- --- --- --- --- --- Yes Yes
V.120 --- --- --- --- --- --- --- Yes Yes
SRB --- Yes --- Yes Yes --- Yes Yes Yes
RSRB --- Yes --- Yes Yes --- Yes Yes Yes
APPN --- --- --- --- Yes --- --- --- Yes
FRAS BAN --- Yes --- Yes Yes --- Yes Yes Yes
DLSw (RFC 1795) --- Yes --- Yes Yes --- Yes Yes Yes
DLSw+ --- Yes --- Yes Yes --- Yes Yes Yes
SDLC --- Yes --- Yes Yes --- Yes Yes Yes
SDLLC --- Yes --- Yes Yes --- Yes Yes Yes
STUN --- Yes --- Yes Yes --- Yes Yes Yes
TG/COS --- --- --- --- --- --- --- Yes Yes
QLLC --- Yes --- Yes Yes --- Yes Yes Yes
Bisync --- Yes --- Yes Yes --- Yes Yes Yes
DSPU --- --- --- --- --- --- --- Yes Yes
NetView Native Service Point --- Yes --- --- Yes Yes Yes
Protocol translation --- --- --- --- --- --- --- Yes Yes
TN3270 --- --- --- --- --- --- --- Yes Yes
LAT --- --- --- --- --- --- --- Yes Yes
XRemote --- --- --- --- --- --- --- Yes Yes
Telnet Yes Yes Yes Yes Yes Yes Yes Yes Yes
PAD Yes Yes Yes Yes Yes Yes Yes Yes Yes
AutoInstall Yes Yes Yes Yes Yes Yes Yes Yes Yes
Modem auto configuration --- --- --- --- --- --- --- Yes Yes
Router monitoring Yes Yes Yes Yes Yes Yes Yes Yes Yes
DHCP Yes Yes Yes Yes Yes Yes Yes Yes Yes
SRT Bridging --- Yes --- Yes Yes --- Yes Yes Yes

Table 12 Cisco 3000 Series Software
Feature Enterprise
SNMP Yes
RMON (events and alarms) Yes
Asynchronous support (SLIP) Yes
ARAP Yes
Frame Relay Yes
SMDS Yes
X.25 Yes
ISDN Yes
PPP Yes
HDLC Yes
IP Yes
RIP Yes
IGRP Yes
Enhanced IGRP Yes
OSPF Yes
BGP Yes
EGP Yes
PIM Yes
NHRP Yes
ES-IS Yes
IS-IS Yes
Snapshot routing Yes
NTP Yes
Transparent bridging Yes
Translational bridging Yes
Multiring Yes
LAN extension host Yes
IPX Yes
NLSP Yes
IPXWAN 2.0 Yes
AppleTalk Versions 1 and 2 Yes
AURP Yes
DECnet Yes
Apollo Domain Yes
Banyan VINES Yes
ISO CLNS Yes
XNS Yes
V.120 Yes
SRB Yes
RSRB Yes
SRT Bridging Yes
APPN ---
FRAS BAN Yes
DLSw (RFC 1795) Yes
DLSw+ Yes
SDLC Yes
SDLLC Yes
STUN Yes
TG/COS Yes
QLLC Yes
Bisync Yes
DSPU Yes
AutoInstall Yes
Telnet Yes
Protocol translation Yes
TN3270 Yes
LAT Yes
XRemote Yes
DHCP Yes
Router monitoring Yes

Table 13 Cisco 1003 and Cisco 1004 ISDN Routers Software Feature Sets

Feature 		Feature Set
IP IP/AT IP/IPX IP/IPX/AT
SNMP Yes Yes Yes Yes
Asynchronous support (SLIP) --- --- --- ---
ARAP --- --- --- ---
Frame Relay --- --- --- ---
SMDS --- --- --- ---
X.25 --- --- --- ---
ISDN Yes Yes Yes Yes
PPP Yes Yes Yes Yes
HDLC Yes Yes Yes Yes
IP Yes Yes Yes Yes
RIP Yes Yes Yes Yes
IGRP Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes
OSPF --- --- --- ---
BGP --- --- --- ---
EGP --- --- --- ---
PIM --- --- --- ---
NHRP --- --- --- ---
ES-IS --- --- --- ---
IS-IS --- --- --- ---
Snapshot routing Yes Yes Yes Yes
NTP --- --- --- ---
Bridging (transparent) Yes Yes Yes Yes
Multiring --- --- --- ---
LAN extension host --- --- --- ---
IPX --- --- Yes Yes
NLSP --- --- --- ---
IPXWAN 2.0 --- --- Yes Yes
AppleTalk Versions 1 and 2 --- Yes --- Yes
AURP --- --- --- ---
DECnet IV --- --- --- ---
DECnet V --- --- --- ---
Apollo Domain --- --- --- ---
Banyan VINES --- --- --- ---
ISO CLNS --- --- --- ---
XNS --- --- --- ---
V.120 --- --- --- ---
SRB --- --- --- ---
RSRB --- --- --- ---
DLSw (RFC 1795) --- --- --- ---
DLSw+ --- --- --- ---
SDLC --- --- --- ---
SDLLC --- --- --- ---
STUN --- --- --- ---
TG/COS --- --- --- ---
QLLC --- --- --- ---
DSPU --- --- --- ---
Protocol translation --- --- --- ---
TN3270 --- --- --- ---
LAT --- --- --- ---
XRemote --- --- --- ---
Telnet Yes Yes Yes Yes
AutoInstall --- --- --- ---
ClickStart Yes Yes Yes Yes
Router monitoring Yes Yes Yes Yes
DHCP --- --- --- ---
Lock-and-Key --- --- --- ---

Table 14 Cisco 1005 Router Software Feature Sets

Feature 		Feature Set
IP IP/AT IP/AT/
X25 		IP/IPX IP/IPX/
X25 		IP/IPX/
AT 		IP/IPX/
AT/X25 		IP/OSPF/
PIM 		IP/IPX/
Async 		IP/
Async
SNMP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Asynchronous support (SLIP) --- --- --- --- --- --- --- --- Yes Yes
ARAP --- --- --- --- --- --- --- --- --- ---
Frame Relay Yes Yes --- Yes --- Yes --- Yes --- ---
SMDS Yes Yes --- Yes --- Yes --- Yes --- ---
X.25 Yes --- Yes --- Yes --- Yes Yes --- ---
ISDN --- --- --- --- --- --- --- --- --- ---
PPP Yes Yes --- Yes --- Yes --- Yes Yes Yes
HDLC Yes Yes --- Yes --- Yes --- Yes Yes Yes
IP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
RIPv2 --- --- --- --- --- --- --- --- --- ---
IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Enhanced IGRP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
OSPF --- --- --- --- --- --- --- Yes --- ---
BGP --- --- --- --- --- --- --- --- --- ---
EGP --- --- --- --- --- --- --- --- --- ---
PIM --- --- --- --- --- --- --- Yes --- ---
NHRP --- --- --- --- --- --- --- --- --- ---
ES-IS --- --- --- --- --- --- --- --- --- ---
IS-IS --- --- --- --- --- --- --- --- --- ---
Snapshot routing Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
NTP --- --- --- --- --- --- --- --- --- ---
Bridging (transparent) Yes Yes Yes Yes Yes Yes Yes Yes --- ---
Multiring --- --- --- --- --- --- --- --- --- ---
LAN extension host --- --- --- --- --- --- --- --- --- ---
IPX --- Yes --- Yes Yes Yes Yes --- Yes ---
NLSP --- --- --- --- --- --- --- --- --- ---
IPXWAN 2.0 --- Yes --- Yes Yes Yes Yes --- Yes ---
AppleTalk Versions 1 and 2 --- Yes Yes --- --- Yes Yes --- --- ---
AURP --- --- --- --- --- --- --- --- --- ---
DECnet IV --- --- --- --- --- --- --- --- --- ---
DECnet V --- --- --- --- --- --- --- --- --- ---
Apollo Domain --- --- --- --- --- --- --- --- --- ---
Banyan VINES --- --- --- --- --- --- --- --- --- ---
ISO CLNS --- --- --- --- --- --- --- --- --- ---
XNS --- --- --- --- --- --- --- --- --- ---
Source-route bridging/
remote source-route bridging 		--- --- --- --- --- --- --- --- --- ---
DLSw (RFC 1795) --- --- --- --- --- --- --- --- --- ---
DLSw+ --- --- --- --- --- --- --- --- --- ---
SDLC --- --- --- --- --- --- --- --- --- ---
SDLLC --- --- --- --- --- --- --- --- --- ---
STUN --- --- --- --- --- --- --- --- --- ---
TG/COS --- --- --- --- --- --- --- --- --- ---
QLLC --- --- --- --- --- --- --- --- --- ---
DSPU --- --- --- --- --- --- --- --- --- ---
Protocol translation --- --- --- --- --- --- --- --- --- ---
TN3270 --- --- --- --- --- --- --- --- --- ---
LAT --- --- --- --- --- --- --- --- --- ---
XRemote --- --- --- --- --- --- --- --- --- ---
Telnet Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
AutoInstall Yes Yes Yes Yes Yes Yes Yes Yes --- ---
ClickStart Yes Yes --- Yes --- Yes --- Yes Yes Yes
Router monitoring Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
DHCP --- --- --- --- --- --- --- --- --- ---
Lock-and-Key --- --- --- --- --- --- --- --- --- ---


Boot ROM Requirements

Boot ROM versions and system images are independent of each other. Table 15 lists the default boot ROM levels that ship with Cisco platforms. These levels contain the latest features and support all current hardware and software features. If you require newer boot ROMs, refer to Table 16, which lists the available upgrades.

Table 15 Boot ROM Levels of New Cisco Platforms
Platform Boot ROM Level
Cisco 1003 and Cisco 1004 ISDN routers 10.3(9)
Cisco 1005 10.3(9)
Cisco 2500 series 10.2(8a)
Cisco 3000 series 9.14(6)
Cisco 4000-M 9.14(7)
10.2(11a) if you order an NP-4B or NP-8B
Cisco 4500-M 10.3(7)
Cisco 4700 10.3(7)
Cisco AS5200 11.1(474)

Table 16 : Available Boot ROM Upgrades

Platform Order Number Current Level
Cisco 2500 series BOOT-2500= 10.2(8a)
Cisco 3000 series BOOT-3000= 9.14(9b)
Cisco 4000 series BOOT-4000= 10.2(11a)


Memory Requirements

Beginning with Cisco IOS Release 10.3, some software image sizes exceed 4 MB and, when compressed, exceed 2 MB. Also, some systems now require more than 1 MB of main system memory for data structure tables.

For Cisco routers to take advantage of the Release 11.1 features, you must upgrade the code or main system memory as listed in Table 17. Some platforms have specific chip or architecture requirements that affect what can be upgraded and in what increments.

Note For the Cisco 7000 and Cisco 7010 routers to recognize Flash memory cards, 11.0 boot ROMs (or later) are required.

Table 17 Release 11.1 Memory Requirements
Router Minimum Required Code Memory Required Main Memory Release 11.1 Runs from
Cisco 1003 and Cisco 1004 ISDN Routers1
IP Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/AT Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/IPX Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/IPX/AT Set 2/4/8 MB optional Flash 8 MB RAM RAM
Cisco 1005 Router1
IP Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/AT Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/AT/X25 Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/IPX Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/IPX/AT/X25 Set 2/4/8 MB optional Flash 8 MB RAM RAM
IP/IPX/AT Set 2/4/8 MB optional Flash 8 MB RAM RAM
IP/IPX/X25 Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/IPX/Async Set 2/4/8 MB optional Flash 4 MB RAM RAM
IP/Async Set 2/4/8 MB optional Flash 4 MB RAM RAM
Cisco 2500 Series
IP Set 4 MB Flash 2 MB RAM2 Flash
IP/RMON Set 4 MB Flash 4 MB RAM Flash
IP/IBM Set 8 MB Flash 4 MB RAM Flash
IP/IBM/RMON Set 8 MB Flash 4 MB RAM Flash
IP/IPX Set 8 MB Flash 4 MB RAM Flash
IP/IPX/RMON Set 8 MB Flash 4 MB RAM Flash
IP/IPX/IBM Set 8 MB Flash 4 MB RAM Flash
IP/IPX/IBM/RMON Set 8 MB Flash 4 MB RAM Flash
IP/IPX/IBM/APPN Set 8 MB Flash 8 MB RAM Flash
Desktop Set 8 MB Flash 4 MB RAM Flash
Desktop/IBM Set 8 MB Flash 4 MB RAM Flash
Enterprise Set 8 MB Flash 6 MB RAM Flash
Enterprise/RMON Set 8 MB Flash 6 MB RAM Flash
Enterprise/APPN Set 16 MB Flash 8 MB RAM Flash
Cisco Frame Relay Access Device (CFRAD) Set 4 MB Flash 2 MB RAM2 Flash
Remote Access Server 4 MB Flash 4 MB RAM Flash
ISDN Set 4 MB Flash 2 MB RAM Flash
LAN FRAD Set 4 MB Flash 4 MB RAM Flash
Cisco 2501 - Cisco 2508
IP Set 4 MB Flash 2 MB RAM Flash
Cisco 2509 - Cisco 2512
IP Set 4 MB Flash 4 MB RAM Flash
Cisco 2513 - Cisco 2519
IP Set 4 MB Flash 2 MB RAM Flash
Cisco AS51003
IP Set 4 MB Flash per card 6 MB RAM per card Flash
IP/RMON Set 4 MB Flash 6 MB RAM Flash
IP/IBM Base Set 8 MB Flash 6 MB RAM Flash
IP/IBM/RMON Set 8 MB Flash 6 MB RAM Flash
IP/IPX Set 8 MB Flash per card 6 MB RAM per card Flash
IP/IPX/RMON Set 8 MB Flash 6 MB RAM Flash
IP/IPX/IBM Base Set 8 MB Flash 6 MB RAM Flash
IP/IPX/IBM/RMON Set 8 MB Flash 6 MB RAM Flash
Desktop Set 8 MB Flash per card 6 MB RAM per card Flash
Desktop/IBM Base Set 8 MB Flash 6 MB RAM Flash
Enterprise Set 8 MB Flash per card 6 MB RAM per card Flash
Enterprise/RMON Set 8 MB Flash 6 MB RAM Flash
Remote Access Server 4 MB Flash per card 6 MB RAM per card Flash
Cisco AS5200
IP/Managed Modems Set 8 MB Flash 8 MB RAM Flash
Desktop/Managed Modems Set 8 MB Flash 8 MB RAM Flash
Enterprise/RMON/
Managed Modems Set 		8 MB Flash 8 MB RAM Flash
Cisco 3101,
Cisco 3102,
Cisco 3103 		8 MB Flash 4 MB RAM Flash
4 MB Flash 16 MB RAM RAM
Cisco 3104,
Cisco 3204 		8 MB Flash 4 MB RAM Flash
4 MB Flash 8 MB RAM RAM
Cisco 4000/4000-M
Cisco 4000
Cisco 4000-M
IP Set 4 MB Flash 16 MB RAM 8 MB RAM RAM
IP/IBM Set 4 MB Flash 16 MB RAM 8 MB RAM RAM
IP/IPX Set 4 MB Flash 16 MB RAM 8 MB RAM RAM
IP/IPX/IBM Set 4 MB Flash 16 MB RAM 8 MB RAM RAM
IP/IPX/IBM/APPN Set 4 MB Flash 16 MB RAM 16 MB RAM RAM
Desktop Set 4 MB Flash 16 MB RAM 8 MB RAM RAM
Desktop/IBM Set 4 MB Flash 16 MB RAM 8 MB RAM RAM
Enterprise Set 4 MB Flash 16 MB RAM 16 MB RAM RAM
Enterprise/APPN Set 4 MB Flash 16 MB RAM 16 MB RAM RAM
Cisco 4500/4500-M
Cisco 4500
Cisco 4500-M
IP Set 4 MB Flash 8 MB RAM 8 MB RAM4 RAM
IP/IBM Set 4 MB Flash 32 MB RAM 16 MB RAM RAM
IP/IPX Set 4 MB Flash 8 MB RAM 8 MB RAM4 RAM
IP/IPX/IBM Set 4 MB Flash 32 MB RAM 16 MB RAM RAM
IP/IPX/IBM/APPN Set 4 MB Flash 32 MB RAM 16 MB RAM RAM
Desktop Set 4 MB Flash 32 MB RAM 16 MB RAM RAM
Desktop/IBM Set 4 MB Flash 32 MB RAM 16 MB RAM RAM
Enterprise Set 4 MB Flash 32 MB RAM 16 MB RAM RAM
Enterprise/APPN Set 8 MB Flash 32 MB RAM 16 MB RAM RAM
Cisco 4700
IP Set 4 MB Flash 16 MB RAM RAM
IP/IBM Set 4 MB Flash 16 MB RAM RAM
IP/IPX Set 4 MB Flash 16 MB RAM RAM
IP/IPX/IBM Set 4 MB Flash 16 MB RAM RAM
IP/IPX/IBM/APPN Set 4 MB Flash 16 MB RAM RAM
Desktop Set 4 MB Flash 16 MB RAM RAM
Desktop/IBM Set 4 MB Flash 16 MB RAM RAM
Enterprise Set 4 MB Flash 16 MB RAM RAM
Enterprise/APPN Set 8 MB Flash 16 MB RAM RAM
Cisco 70005,
Cisco 7010
IP Set 8 MB Flash 16 MB RAM RAM
IP/IPX/IBM Set 8 MB Flash 16 MB RAM RAM
IP/IPX/IBM/APPN Set 8 MB Flash 16 MB RAM RAM
Desktop/IBM Set 8 MB Flash 16 MB RAM RAM
Enterprise Set 8/16 MB Flash memory card 16 MB RAM RAM
Enterprise/APPN Set 8 MB Flash 16 MB RAM RAM
IP/VIP Set 8 MB Flash 16 MB RAM RAM
IP/IPX/IBM/VIP Set 8 MB Flash 16 MB RAM RAM
IP/IPX/IBM/APPN/VIP Set 8 MB Flash 16 MB RAM RAM
Desktop/IBM/VIP Set 8 MB Flash 16 MB RAM RAM
Enterprise/VIP Set 8/16 MB Flash memory card 16 MB RAM RAM
Enterprise/APPN/VIP Set 8 MB Flash 16 MB RAM RAM
Source-Route Switch 4 MB Flash 16 MB RAM RAM
Cisco 7200
Enterprise Set 8/16/20 MB Flash memory card 16 MB RAM Flash
Enterprise/APPN Set 8/16/20 MB Flash memory card 24 MB RAM Flash
Desktop/IBM Set 8/16/20 MB Flash memory card 16 MB RAM Flash
Network Layer 3 Switching Set 8/16/20 MB Flash memory card 16 MB RAM Flash
Cisco 7505, Cisco 7507, Cisco 7513, Cisco 7000 with RSP7000

Cisco 7513 only

All Others
IP Set 8 MB Flash 16 MB RAM 16 MB RAM RAM
IP/IPX/IBM Set 8 MB Flash 16 MB RAM 16 MB RAM RAM
IP/IPX/IBM/APPN Set 8 MB Flash 16 MB RAM 16 MB RAM RAM
Desktop/IBM Set 8 MB Flash 16 MB RAM 16 MB RAM RAM
Enterprise Set 8 MB Flash memory card 24 MB RAM 16 MB RAM RAM
Enterprise/APPN Set 8 MB Flash memory card 32 MB RAM 24 MB RAM RAM
IP/VIP Set 8 MB Flash 24 MB RAM6 24 MB RAM7 RAM
IP/IPX/IBM/VIP Set 8 MB Flash 24 MB RAM6 24 MB RAM7 RAM
IP/IPX/IBM/APPN/VIP Set 8 MB Flash 24 MB RAM6 24 MB RAM7 RAM
Desktop/IBM/VIP Set 8 MB Flash 24 MB RAM6 24 MB RAM7 RAM
Enterprise/VIP Set 8/16/20 MB Flash memory card 32 MB RAM6 24 MB RAM7 RAM
Enterprise/APPN/VIP Set 8/16/20 MB Flash memory card 32 MB RAM6 32 MB RAM RAM

1 If you need to upgrade the main memory for your Cisco1003, Cisco1004, or Cisco1005 router, be sure to order the upgrade specific to your router.
2 For Cisco2509 through Cisco 2512 access servers, and the Cisco 2522 and Cisco 2523 routers, 4 MB DRAM is the minimum recommended.
3 Memory requirements listed are per card. Each AS5100 supports up to three cards, so that the maximum memory needed for any AS5100 is three times the listed number.
4 The Cisco4500 requires 16 MB DRAM when two NP-CT1 or two NP-CE1 Network Processor Modules are installed in the chassis.
5 Except the Cisco7000 with RSP7000. For a Cisco7000 with an RSP7000 card, refer to the memory requirements for Cisco75xx platforms.
6 To use the HSA feature, 32 MB DRAM is the minimum recommended memory (per RSP).
7 To use the HSA feature, 24 MB DRAM is the minimum recommended memory (per RSP).


Microcode Software

Table 18 lists the current microcode versions for the Cisco 7000 series. Table 19 lists the current microcode versions for the Cisco 7500 series. Note that for the Cisco 7000 and Cisco 7500 series, microcode software images are bundled with the system software image---with the exception of the Channel Interface Processor (CIP) microcode (all system software images) and Versatile Interface Processor (VIP) microcode (certain system software images). Bundling eliminates the need to store separate microcode images. When the router starts, the system software unpacks the microcode software bundle and loads the proper software on all the interface processor boards. Versatile Interface Processor (VIP and VIP2) microcode is bundled only in the feature sets indicated in Table 17.

Note For the Cisco 7000 series, all boards must use the Level 10 (or greater) microcode that is bundled (except CIP) with the system image.

Table 18 Current Microcode Versions for the Cisco 7000 Series
Processor or Module Current Bundled Microcode Version Minimum Version Required
AIP (ATM Interface Processor) 10.16 10.12
EIP (Ethernet Interface Processor) 10.1 10.1
FEIP (Fast Ethernet Interface Processor) 10.4 10.2
FIP (FDDI Interface Processor) 10.2 10.2
FSIP (Fast Serial Interface Processor) 10.18 10.12
HIP (HSSI Interface Processor) 10.2 10.2
MIP (MultiChannel Interface Processor) 12.0 11.4
SP (Switch Processor) 11.15 11.14
SSP (Silicon Switch Processor) 11.15 11.14
TRIP (Token Ring Interface Processor) 10.3 10.3
VIP (Versatile Interface Processor)1 21.40 21.9

1 VIP microcode resides within the CiscoIOS software; it is not "bundled" in.

Table 19 Current Microcode Versions for the Cisco 7500 Series
Processor or Module Current Bundled RSP Microcode Version Minimum Version Required
AIP (ATM Interface Processor) 20.9 20.5
EIP (Ethernet Interface Processor) 20.2 20.1
FEIP (Fast Ethernet Interface Processor) 20.3 20.1
FIP (FDDI Interface Processor) 20.1 20.1
FSIP (Fast Serial Interface Processor) 20.4 20.1
HIP (HSSI Interface Processor) 20.0 20.0
MIP (MultiChannel Interface Processor) 22.0 20.3
POSIP (Packet over SONET OC-3 Interface Processor) 20.0 20.0
RSP2 (Route Switch Processor)1 20.0 200.0
TRIP (Token Ring Interface Processor) 20.0 20.0
VIP (Versatile Interface Processor)1 21.40 21.9
VIP2 (Second-Generation Versatile Interface Processor)1 21.40 21.40

1 RSP2, VIP, and VIP2 microcode reside within the CiscoIOS software; they are not "bundled" in.

Note RSP2 microcode was introduced in Release 11.1(2).

Note POSIP and VIP2 microcode were introduced in Release 11.1(5).


Channel Interface Processor (CIP) Microcode

Beginning with Cisco IOS Release 11.1, the CIP microcode is no longer bundled with the Cisco IOS software image. You must have Flash memory installed on the Route Processor (RP) card and 8 MB RAM installed on your CIP card to use the IBM channel attach features in Cisco IOS Release 11.1 and later. See the "Important Notes" section for more information about CIP microcode.


New Features in Release 11.1(7)

There are no new features in Release 11.1(7). There are no new features or platform support planned for any subsequent releases of Cisco IOS Release 11.1. Release 11.1(5) was the last maintenance release to add new features and platform support.


New Features in Release 11.1(6)

There are no new features in Release 11.1(6).


New Features in Release 11.1(5)

Note The first few maintenance releases of each new Cisco IOS software release may deliver additional new features. When determining whether to deploy a new release, you should weigh the importance you place on maximizing product capability versus maximizing operational stability. An early release of software should always be tried in a test network before being deployed in a production network.

The following software enhancements have been added to Release 11.1(5):


Support for Second-Generation Channel Interface (CIP2)

The CIP2 card is the follow on product to the original CIP card, and provides increases in performance, capacity, reliability, and serviceability.

The CIP2 card includes the following improvements over the original CIP:

  • A secondary processor cache (providing a 50% performance increase)

  • Increased memory options (CIP2 memory configurations come in 32 MB, 64 MB, and 128 MB)

  • An on-board boot flash, which is software upgradable (allowing upgrades to the boot microcode without physical replacement of parts)

The CIP2 card operates with the CxBus in the Cisco 7000 series routers with either of the following processor types:

  • Router Processor (RP) and Switch Processor (SP) (or Silicon Switch Processor [SSP]) combination

  • Cisco 7000 series Route Processor (RSP7000) and Cisco 7000 series chassis interface (RSP7000CI) combination

CIP microcode is required if you will be using the CIP2 card. See the "Important Notes" section for more information about CIP microcode.


Cisco 7200 Series

The Cisco 7200 series is a new series of multiprotocol routers that delivers the high-performance, high port density, and availability features typically associated with high-end systems. The Cisco 7200 series supports Cisco's Inter-Switch Link (ISL) Protocol for transporting virtual LANs (VLANs) across Fast Ethernet. VLANs enable the logical definition of bridge groups that can be overlaid on the physical network.

The Cisco 7206 router can be configured with up to 48 Ethernet ports, 24 Token Ring ports, 24 serial ports, 7 Fast Ethernet ports, and 6 FDDI ports.

Four feature sets are available in Cisco IOS Release 11.1(5) to support the Cisco 7200 series:

  • Network Layer 3 Switching

  • Desktop/IBM

  • Enterprise

  • Enterprise/APPN

Refer to Table 6 for a list of features included in each of these sets.


Cisco AS5200

The Cisco AS5200 Universal Access Server provides mixed asynchronous and ISDN line service to accommodate both mobile users and telecommuters with one server. This new line of access servers contains channel service units (CSUs), channel banks, communication servers, switches, routers, and 48 modems in one standalone chassis that accommodates up to 48 users dialing-in simultaneously.

The following feature sets are available for the Cisco AS5200. Refer to Table 10 for a complete list of the features provided in these sets.

  • IP/Managed Modems

  • Desktop/Managed Modems

  • Enterprise/RMON/Managed Modems


Cisco Web Browser Interface

A Web browser interface is available on any Cisco product running Cisco IOS Release 11.1(5) software, or later. This Web interface allows you to log in to a router or access server and execute Cisco IOS software commands. It operates much like the command line interface (CLI) on a terminal. To execute commands using the Web interface, click on the "Monitor the Router" link from the router's home page. All Cisco products running Cisco IOS Release 11.0(10) or 11.1(5) software or later have a home page.


ClickStart Enhancements

ClickStart, which allows you to use a standard Web browser to configure and monitor a Cisco router, has been enhanced. You can now use it to configure a Cisco 1005 router that has one Ethernet and either one Frame Relay or one asynchronous serial interface. For additional information about ClickStart, see the section "New Software Features in Release 11.1(2)".


DLSw+ Enhancements

In Release 11.1(5), DLSw+ can be used as a "virtual" data-link control for other SNA features in the Cisco IOS software, including:

  • LAN Network Manager (LNM) over DLSw+

LNM over DLSw+ allows DLSw+ to be used in Token Ring networks that are managed by IBM's LNM software. Using this feature, LNM can be used to manage Token Ring LANs, control access units, and Token Ring attached devices over a DLSw+ network. All management functions continue to operate as they would in a source-route bridged network or an RSRB network.

  • Downstream physical unit (DSPU) over DLSw+

DSPU over DLSw+ allows Cisco's DSPU feature to operate in conjunction with DLSw+ in the same router. DLSw+ can be used either upstream (toward the mainframe) or downstream (away from the mainframe) of DSPU. DSPU concentration consolidates the appearance of multiple physical units (PUs) into a single PU appearance to VTAM, minimizing memory and cycles in central site resources (VTAM, NCP, and routers) and speeding network startup.

  • SNA service point support over DLSw+

SNA service point over DLSw+ allows Cisco's SNA service point feature to be used in conjunction with DLSw+ in the same router. Using this feature, SNA service point can be configured in remote routers, and DLSw+ can provide the path for the remote service point PU to communicate with NetView. This allows full management visibility of resources from a NetView 390 console, while concurrently offering the value-added features of DLSw+ in an SNA network.


Fast Ethernet---100E NIM for Cisco 4500 and Cisco 4700

Support for the FastEthernet network interface module (NIM) is added in Release 11.1(5). The Cisco 4500 series (Cisco 4500, Cisco 4500-M, Cisco 4700, and Cisco 4700-M) routers support a FastEthernet network interface module (NIM) with a PCI bus interface to its DEC21140 controller chip. The FastEthernet NIM for Cisco 4500 and Cisco 4700 provides a single full-duplex, 100-Mbps Ethernet interface.


MIP Flow Control

Custom queuing and priority queuing are now available for the MultiChannel interface in RSP systems (Cisco 7500 series and Cisco 7000 series with RSP7000).


NetFlow Switching

NetFlow Switching brings the benefits of connection-oriented switching to network layer devices. With NetFlow Switching, routers become network switches able to combine quality-of-service and security capabilities with high performance. Coupled with the large bandwidth capacity of Cisco's new 7500 series, NetFlow Switching allows customers to provide many of the capabilities associated with ATM on their existing routed infrastructure.

NetFlow Switching operates at the network and transport layers so it can incorporate user and application oriented information to make switching decisions such as allowing access and providing specific quality of service. NetFlow Switching achieves high performance by operating on connection-like flows between source/destination IP addresses. Cisco LAN Switches such as the Catalyst 5000, will be able to take advantage of NetFlow Switching with the incorporation of support for multilayer switching and Cisco IOS.


Optimum Switching

Optimum Switching is quite similar to fast switching from a high level. The optimum switching cache is a separate cache using a more efficient data structure than the fast switching cache to achieve better performance. In addition, the data caching at the processor is optimized to boost performance further. Optimum Switching requires the architecture of the Cisco 7500 series Route Switch Processor (RSP).


Packet OC-3 Interface

Support for the Packet OC-3 interface on the Packet over SONET Interface Processor (POSIP) is added in Release 11.1(5). The POSIP for Cisco 7500 and Cisco RSP/7000 routers provides a single 155.520-Mbps, OC-3 physical layer interface for packet-based traffic. This OC-3 interface is fully compatible with SONET and Synchronous Digital Hierarchy (SDH) network facilities and is compliant with RFC 1619, "PPP over SONET/SDH," and RFC 1662, "PPP in HDLC-like Framing."

To support this interface, Packet over SONET Interface Processor microcode is also added to this release.


New Software Features in Release 11.1(4)

The following software enhancements have been added to Release 11.1(4):


New Feature Sets for Cisco 1005

Cisco IOS Release 11.1(4) supports two new Cisco 1005 feature sets:

  • IP/Async

  • IP/IPX/Async

Refer to Table 14 for a list of features included in each of these sets.


High System Availability (HSA)

HSA is an advanced software feature of the Cisco 7500 architecture. HSA increases the availability and uptime of the Cisco 7507 and Cisco 7513 routers. This increase is accomplished through a master/slave relationship between two RSPs. If the slave RSP detects an error condition, it automatically takes control and reboots the system without user intervention. This automatic action minimizes network interruption and increases system availability.

Note HSA requires a ROM Monitor upgrade. See the "Important Notes" section for more information.

HSA can be used in the following situations:

  • Hardware backup. Protects against single processor failure.

  • Software error protection. Protects against critical software errors by keeping different software images on each RSP.

  • Configuration switching. Enables users to store different configurations in each RSP. If the new feature configuration on the master causes a system failure, the slave RSP takes over the routing function after a system reboot.

HSA is only supported in feature set images that include a "v" in the name, such as the RSP subset image rsp-jv-mz.111-4.

See the "Important Notes" section for more information.


New Software Features in Release 11.1(3)

The following software enhancements have been added to Release 11.1(3):


Channel Service Unit/Data Service Unit (CSU/DSU) Management Information Base (MIB)

This new Cisco-proprietary MIB for integrated CSU/DSU is available in Release 11.1(3) and later. This MIB is available for use with the Cisco 2524 and Cisco 2525 products, and is for T1 and switched 56-kbps interfaces. It enables network managers to retrieve line statistics and CSU/DSU configuration data.


Cisco 2524 and Cisco 2525

The Cisco 2524 and Cisco 2525 routers eliminate the need for a separate terminal adapter on an ISDN line, or separate channel service unit/data service units (CSU/DSUs) on synchronous serial WAN interfaces.

These platforms support a removable BRI or BRI with integrated NT1 interface, a LAN interface (either Ethernet or Token Ring), and two WAN interface slots.

New commands have been added to the Cisco IOS software to support the Cisco 2524 and Cisco 2525.

The Cisco 2524 and Cisco 2525 support RFC 1406, Definitions of Managed Objects for the DS1 and E1 Interface Types.

Cisco IOS Release 11.0(5) also supports the Cisco 2524 and Cisco 2525 routers.

Note The Cisco 2524 and Cisco 2525 require a minimum 11.0(5)-level boot ROM.


Cisco 2520, Cisco 2521, Cisco 2522, and Cisco 2523

The Cisco 2520 through Cisco 2523 models merge router and communication server features to serve access and telecommuting requirements in a single platform. WAN aggregation, telecommuting, branch office, and IBM protocol applications are well-suited to these new Cisco devices.

The interfaces available in each model are shown below.

Cisco 2520 1 Ethernet, 2 high-speed synchronous serial, 2 low-speed synchronous/asynchronous serial, 1 ISDN BRI
Cisco 2521 1 Token Ring, 2 high-speed synchronous serial, 2 low-speed synchronous/asynchronous serial, 1 ISDN BRI
Cisco 2522 1 Ethernet, 2 high-speed synchronous serial, 8 low-speed synchronous/asynchronous serial, 1 ISDN BRI
Cisco 2523 1 Token Ring, 2 high-speed synchronous serial, 8 low-speed synchronous/asynchronous serial, 1 ISDN BRI

The low-speed serial interfaces (maximum speed 115.2 kbps) are capable of supporting both synchronous and asynchronous protocols.


LAN Frame Relay Access Device (FRAD) Feature Set

The LAN FRAD feature set is supported on the Cisco 2501, Cisco 2502, Cisco 2520, Cisco 2521, Cisco 2522, and Cisco 2523 routers.


IP/Open Shortest Path First (OSPF)/Protocol Independent Multicast (PIM) Feature Set

This feature set for the Cisco 1005 router contains the functionality of the IP feature set, but includes support for OSPF and PIM.


New Software Features in Release 11.1(2)

The following software enhancements have been added to Release 11.1(2):


New Configuration Tool---ClickStart

ClickStart allows you to use a standard Web browser, such as Netscape or Mosaic, to configure and monitor a Cisco router. You can use ClickStart to configure a Cisco 1003 or Cisco 1004 router that has one Ethernet and one ISDN Basic Rate Interface (BRI). You configure the router to dial your Internet service provider, and your Internet service provider supplies an ISDN connection to the Internet. You can also use ClickStart to monitor any Cisco router that is running Cisco IOS Release 11.1(2), Release 11.0(6), or later.

If you have a Cisco 1003 or Cisco 1004 router, you can automatically use ClickStart to monitor your router.

If you have any other Cisco router, you must enable ClickStart before you can use it to monitor your router. To do this, follow this procedure:

  1. To enable ClickStart, use the ip http server global configuration command.

  2. By default, ClickStart uses port 80 to communicate with the router. If you want to configure a different port, use the ip http port number global configuration command. number is the number of the port you want to use for ClickStart.


Virtual LAN (VLAN) Routing

Release 11.1(2) supports IP and IPX routing and transparent 802.1d bridging between Inter-Switch Link (ISL)-encapsulated VLANs on Cisco 7000 and Cisco 7500 series routers with RSPs. This functionality is also supported on the Cisco 7000 with Route Processors (RPs) and Switch Processors (SPs) and/or Silicon Switch Processors (SSPs), with limited performance.

VLAN allows you to logically segment end-user ports into autonomous virtual workgroups. Logical segmentation provides benefits in address administration, security, and management of network broadcast activity across the enterprise. To communicate between VLANs, a routing function is required (or bridging, in the case of nonroutable protocol types). Cisco IOS software offers two alternatives for communication between VLANs: dedicated VLAN ports and VLAN subinterfaces.

  • Dedicated VLAN ports allow you to assign a physical interface to each VLAN group. This is a cost-effective approach if you run high-bandwidth applications between VLANs.

  • VLAN subinterfaces enable multiple VLANs to be configured on a single physical interface. A VLAN interface, referred to as a trunk interface, logically transports multiple VLANs across Fast Ethernet by encapsulating with Cisco Inter-Switch Link (ISL). Trunked VLAN subinterfaces conserve router or switch physical ports and are a cost-effective solution for environments where the majority of traffic is within a VLAN.

Security access lists for controlling the type of access within or outside of a VLAN can be configured using subinterfaces within Cisco routers. This control provides an additional layer of security when VLANs are interconnected.

VLAN routing

  • Enables communications between logically defined VLAN groups, while maintaining the integrity of VLAN firewalls (security, traffic isolation, and common logical addressing)

  • Performs a central role in planning and configuring VLANs within a switched internetwork

  • Conserves router and switch physical interfaces

  • Provides VLAN communications within workgroups, across the campus, and across WANs

  • Allows bridging mode (Layer 2) for end-station protocols that function only at Layer 2 (for example, NetBIOS and LAT)

  • Enables security access lists for controlling the type of access within or outside of a VLAN

  • Provides a wide range of VLAN configuration options with concurrent routing and VLAN forwarding where both Layer 2 and Layer 3 applications reside within the network


New Software Features in Release 11.1(1)

This section describes new features and enhancements in the initial Cisco IOS Release 11.1 of the router products software.


Platform Support

This section describes new platforms and interfaces supported by the initial release of Cisco IOS Release 11.1.


Cisco 1005

The Cisco 1005 synchronous serial router connects small, remote Ethernet LANs to WANs over leased lines, Frame Relay, Switched Multimegabit Data Service (SMDS), Switched-56, and X.25. The Cisco 1005 is already supported on Releases 11.0(4), 10.3(6), and higher.


AAL3/4 E3/DS3 for Cisco 4500 and Cisco 4700 ATM NIM

Asynchronous Transfer Mode (ATM) is supported on the Cisco 4500 and Cisco 4700 routers, using the Cisco ATM Network Interface Module (NIM) cards. The ATM adaptation layer 3/4 (AAL3/4), and additional NIM variants for use with E3/DS3 services are supported in Release 11.1. (Support is also available in Cisco IOS Release 11.0(5).) ATM on the Cisco 4500 and Cisco 4700 routers is configured differently from that on the Cisco 7000 routers. Refer to the Wide-Area Networking Configuration Guide for configuration information.


Backbone Protocol Routing Features

This section describes the backbone protocol routing features that are new in the initial release of Cisco IOS Release 11.1.


TCP/IP Features

The following features have been added to the Cisco IOS TCP/IP software:

  • Next Hop Resolution Protocol (NHRP) Enhancements for IPX---NHRP allows routers to dynamically discover data-link addresses for other routers on a WAN cloud, eliminating the need to configure network layer- and data link layer-addresses for all neighbors on a WAN cloud.

NHRP has been enhanced to support IPX in addition to the IP support introduced in Cisco IOS Release 10.3. With NHRP, you can dynamically resolve IPX addresses in large-scale WAN environments in addition to resolving IP addresses. NHRP will operate using ATM, SMDS, or GRE tunneling.

  • Fast Install for Static Routes---Floating static routes are static routes that have a higher administrative distance than other dynamic or static routes, and are often used to back up a leased-line or Frame Relay service in conjunction with the Cisco IOS software dial-on-demand routing (DDR) functionality.

Fast Install ensures that the floating static route is installed as soon as either the routing protocol or interface reports a connectivity loss. This enables faster convergence when using dial-on-demand circuits to back up, for example, a leased-line or Frame Relay service.

  • Fast-Switched Generic Route Encapsulation (GRE)---GRE provides the ability to handle multiple network protocols in the same tunnel. In addition, GRE includes optional sequencing and an optional security key. This feature enables fast switching for GRE tunnels. Previously, encapsulation and de-encapsulation were process switched. The increased performance of GRE tunnels aids Cisco 2500, Cisco 4000, and Cisco 7500 series users.

  • Routing Information Protocol Version 2 (RIPv2)---While RIPv2 shares the same basic algorithms as RIPv1, it supports several new features:

    • Authentication: RIPv2 offers two modes of authentication, a plain-text password or MD5 authentication.

Note MD5 authentication in RIPv2 is not supported in Release 11.1(1) or Release 11.1(2).

    • Subnet Masks: Subnet mask information makes RIP more useful in a variety of environments and allows the use of variable subnet masks on the network. Subnet masks are also necessary for implementation of "classless" addressing, such as classless interdomain routing (CIDR).

    • Multicasting: RIPv2 packets can be multicast instead of being broadcast. Using an IP multicast address reduces the load on hosts that do not support routing protocols. It also allows RIPv2 routers to share information that RIPv1 routers cannot hear. This is useful since a RIPv1 router may misinterpret route information because it cannot apply the supplied subnet mask.

    • External Route Tags: The route tag field may be used to propagate information acquired from an Exterior Gateway Protocol (EGP).

If you implement RIP you can now make more efficient use of allocated address space by implementing variable-length subnet masks (VLSM) within networks.

RIPv2 adds to the choices of classless routing protocols supported by Cisco IOS software. This is the primary mechanism to improve scaling of the Internet routing system as a whole.

Note Care must be taken when combining RIPv2 routers and RIPv1-compatible hosts. Because it cannot apply the supplied subnet mask, a RIPv1 host may misinterpret route information.

In some multi-homed environments, hosts listen to RIPv1 broadcasts to enable them to switch their traffic to a new router, should the main router or connection fail. Cisco recommends the choice of alternative technologies such as RFC 792 ICMP Router Discovery Protocol, or Hot Standby Router Protocol (HSRP) as alternatives for hosts.


Transparent Bridging Features

The following feature will be added to Cisco's transparent bridging software in Cisco IOS Release 11.1(2):

  • Virtual LAN (VLAN) Routing---Communication between switched VLANs is enhanced by Cisco IOS software VLAN services with the introduction of IP and IPX routing and transparent 802.1d bridging between Cisco ISL-encapsulated switched VLANs.


Desktop Protocols

This section describes the desktop protocol features that are new in the initial release of Cisco IOS Release 11.1.


AppleTalk Features

The following features have been added to Cisco's AppleTalk software:

  • Simple Multicast Routing Protocol (SMRP) Fast Switching---Fast switching of the AppleTalk multicast routing protocol, SMRP, is supported for Cisco 2500, Cisco 4000, Cisco 4500, Cisco 7000, and Cisco 7500 series routers.

SMRP optimizes Apple Computer's Quicktime Conferencing (QTC) traffic flow of audio, video, and shared data over AppleTalk-based routed networks. QTC is a powerful multimedia application that enables multiple end stations to participate in multipoint, collaborative, multimedia operations. SMRP is the networking complement of QTC. SMRP optimizes communication among QTC end systems with reduced CPU utilization by eliminating the duplicate transmission of identical packets to multiple receivers. SMRP streamlines network throughput by eliminating duplicate and unnecessary traffic propagation. It dynamically establishes unique shortest-path distribution trees to restrict traffic propagation to only those parts of the network that contain receiving end stations. SMRP provides just-in-time packet duplication upon encountering a branch in the distribution tree.

Cisco routers have been SMRP-enabled since Cisco IOS Release 11.0. New in this release is enhanced performance through fast switching on the Cisco 4000 and Cisco 7500 series routers.


ISO CLNS Features

  • Target Identifier Address Resolution Protocol (TARP) Support---TARP is an address resolution protocol for mapping Synchronous Optical Network (SONET) identifiers to OSI NSAPs (much like a DNS, which will return an NSAP given a name string, or the reverse). Some applications that run on SONET devices identify these devices by a target identifier (TID). Cisco TARP-enabled routers cache TID-to-network address mapping. Because these applications usually run over OSI, the network addresses are OSI NSAPs.

The benefits for TARP include:

  • Implementing the Bellcore TARP specification for Intermediate Systems.

  • Networking support for applications (typically used by telephone companies) running on SONET devices.

  • Mapping SONET identifiers (for example, TID) to OSI NSAPs (much like a DNS, which will return an NSAP given a name string, or the reverse).

  • Propagating TARP PDUs not destined for the router.


Novell Features

The following features have been added to Cisco's Novell software:

  • Enhanced IGRP to NLSP Route Redistribution---Enhanced IGRP to NLSP Route Redistribution is the method by which routing information is passed between Enhanced IGRP and NLSP routing domains in IPX networks. While route redistribution between Enhanced IGRP and IPX RIP is automatic by default (as is redistribution between NLSP and IPX RIP), this new Cisco IOS software feature adds comprehensive tools for enabling the direct flow of routing information between Enhanced IGRP and NLSP networks.

Enhanced IGRP to NLSP route redistribution provides unparalleled flexibility to users of large IPX networks. Previously, when IPX networks grew to the point where RIP and SAP were no longer able to adequately support them, users were forced to upgrade to either Enhanced IGRP or NLSP to gain the scalability benefits inherent to these protocols. Through the use of Enhanced IGRP to NLSP route redistribution, users may now select the routing protocol, or combination of routing protocols, that meets their needs. For example, an IPX network can now be built that uses a combination of RIP and NLSP on the NetWare servers and uses Enhanced IGRP as the single backbone protocol.

  • IPX Input Access Lists---This is a security enhancement feature that provides the capability of applying access lists to incoming router interfaces and the added flexibility in building secure IPX networks. The IPX input access lists can be used to validate user information at the borders of networks and to build more sophisticated firewalls. By moving the filter process from an outgoing to an incoming interface, IPX Input Access Lists enhance security and reduce processor overhead by denying packets before they transit the router. They also provide the capability of filtering traffic at the originating end of GRE-tunneled networks.

Note IPX Input Access Lists can be fast switched, but cannot be enabled on a cBus-based router configured for autonomous or SSE switching.

  • IPX Per-host Load Sharing---This load-sharing process transmits successive packets (or a traffic stream) for a given end host over the same path when multiple equal-cost paths are present. Load sharing is achieved when traffic streams for different end hosts use different paths.

Other implementations of load sharing rely on a round-robin algorithm that transmits successive packets over alternate, equal-cost paths without regard to the end host. Round-robin load sharing increases the likelihood of packets being received out of order at the destination host. Out-of-order packets must often be retransmitted in IPX environments, leading to much higher application delay and network congestion.

Because per-host load sharing sends all packets destined for an end host over the same media interface, the likelihood of packets being received out of order is greatly reduced and minimizes retransmissions and network overhead.

  • NetWare Link Services Protocol (NLSP) Route Aggregation---NLSP is the link-state routing protocol for IPX networks. Cisco IOS software now includes additional functionality for NLSP that permits multiple NLSP areas to directly and succinctly share information without using IPX RIP between groups. NLSP route aggregation is designed to be compatible with the NetWare Link Services Protocol (NLSP) Specification, Revision 1.1, from Novell.

NLSP route aggregation provides several important benefits to users of large IPX networks:

  • Ability to divide IPX networks into multiple NLSP areas.

It is recommended that large IPX networks (conservatively estimated as those containing over 400 network addresses according to Novell design guidelines) be split into smaller NLSP areas. Previously, NLSP was specified as a single-area routing protocol, meaning that individual NLSP areas had to use IPX RIP to communicate routing information. Cisco's new implementation of NLSP allows multiple instances of NLSP to run on the same router, and allows routing information to be redistributed between areas. This allows much larger NLSP networks to exist.

  • Routing information is shared more efficiently in properly designed hierarchically addressed networks.

When possible, ranges of addresses within an area can be aggregated (or summarized) into a single route entry. Because the number of these entries in the routing databases is minimized and update traffic is reduced, aggregation results in a much more efficient routing process.

Note To derive the maximum benefit from NLSP route aggregation it is important that network addresses be assigned properly in IPX environments. Network addresses should be assigned in a structured, hierarchical manner. Additionally, since other IPX routing protocols cannot interpret summarized route entries, the use of NLSP route aggregation in a Cisco router that is also using IPX RIP or Enhanced IGRP must be carefully planned and implemented.

  • Raw FDDI IPX Encapsulation---Support for an additional IPX encapsulation on FDDI media is added. Cisco now supports routing of FDDI_RAW along with two standard FDDI encapsulations: FDDI_SNAP and FDDI_802.2. FDDI_RAW encapsulation is most often encountered when bridges or switches connect Ethernet-based Novell networks using the 802.3_Ethernet encapsulation to FDDI-based networks. The FDDI_RAW encapsulation is not currently supported by Novell networking standards, but is becoming more common with the deployment of switched networks.

Without routing support for FDDI_RAW IPX encapsulation, packets of this format are recognized only by switches or bridges on the FDDI ring. Neither clients, servers, nor routers directly connected to the ring can recognize this type of packet. By implementing FDDI_RAW encapsulation, it is possible to recognize and route these packets, either to other LAN or WAN media, or back onto FDDI in one of the Novell-approved FDDI formats. Routing support for FDDI_RAW can eliminate the requirement of changing Ethernet encapsulation on servers and clients when deploying switched internetworks.

  • IPX Header Compression---IPX header compression permits the compression of IPX packet headers over various WAN media. IPX header compression (CIPX) is described in RFC 1553, Compressing IPX Headers Over WAN Media. CIPX is based on Van Jacobson's TCP/IP header compression. CIPX will operate over PPP WAN links using either the IPXCP or IPXWAN communications protocols.

IPX header compression can reduce header information size from 30 bytes to as little as 1 byte. This can save bandwidth and reduce costs associated with IPX routing over WAN links. In addition, the use of CIPX is negotiated automatically on WAN links using the IPXWAN protocol, which reduces the complexity of implementing these circuits.


Wide-Area Networking Features

This section describes the wide-area networking features that are new in the initial release of Cisco IOS Release 11.1:


ISDN/DDR Enhancements

The following feature has been added to Cisco's ISDN and DDR software:

  • Asynchronous ISDN Access (V.120 Support)---Asynchronous ISDN access allows an ISDN terminal adapter (TA) connected to the serial port of a personal computer to call an ISDN BRI or PRI hub router and be recognized as if it were connected to a Cisco access server.


SMDS

The following features have been added to Cisco's SMDS software:

  • Fast-Switched Transparent Bridging over SMDS---Transparent bridging over SMDS can be fast switched using IEEE 802.6i encapsulation, allowing for better bridging performance and enhanced bridged media support.

Only IEEE 802.3, IEEE 802.5, and FDDI with or without frame check sequence (FCS) frames will be supported in the fast-switched and process-switched modes. Previously, only IEEE 802.3 frames were process-switched.

  • Fast-Switched IPX over SMDS---Fast-switching of Novell IPX packets over SMDS provides better performance for IPX over SMDS. This feature is enabled by default. The existing ipx route-cache commands work for SMDS interfaces.


ATM Enhancements

The following features have been added to Cisco's Asynchronous Transfer Mode (ATM) software:

  • Classic IP over ATM Enhancements---The Classic IP over ATM client software has been enhanced to support the configuration of multiple independent ATM ARP servers. When used with other clients that support similar functionality, this feature eliminates the single point of failure associated with having only one server.

  • Bridged Emulated LANs---Bridging between emulated LANs is now supported.

  • LANE MIBs---Three new Cisco MIBs are now available for LAN Emulation (LANE):

    • Cisco LANE Broadcast-and-Unknown Server MIB: Used to manage LANE broadcast-and-unknown servers.

    • Cisco LANE Configuration MIB: Used to manage LANE configuration servers in Cisco devices.

    • Cisco LANE Service MIB: Used to manage LANE service in Cisco devices.


Core Enhancements

The following features have been added to the Cisco 7000 series and Cisco 7500 series routers:

  • VIP-1FE, VIP-1FE/1FE, VIP-1FE/4E, VIP-4E/4T, and VIP-4R/4T Support---The Versatile Interface Processor (VIP) is a new class of interface processor for the Cisco 7000 series and Cisco 7500 series routers. The VIP is a modular, RISC-based, intelligent interface processor that accepts up to two port adapters. Port adapters provide the media-specific interface, while the VIP motherboard provides support for high-performance switching and other value-added features.

The VIP-1FE is based on a single one-port Fast Ethernet port adapter. The VIP-1FE/1FE is based on two one-port Fast Ethernet port adapters. Both the VIP-1FE and VIP-1FE/1FE support IEEE 802.3u Fast Ethernet specifications for half- and full-duplex operation.

The VIP-1FE/4E is based on a one-port Fast Ethernet port adapter that supports distributed IP switching for the FEIP and a four-port (10BaseT) Ethernet port adapter. VIP distributed IP switching can switch to these output interfaces: VIP-FE/4E, VIP-FE, EIP, FIP, and FSIP, HIP, and MIP with HDLC encapsulations. (VIP distributed IP switching is not available in Release 11.1(1). It will be available in a future maintenance release of Cisco IOS Release 11.1.)

Each Fast Ethernet port has an RJ-45 connector (100BaseTX, two-pair category 5 UTP), and an MII connector that provides connectivity to 100BaseFX and 100BaseT4 through customer-provided external transceivers. The Fast Ethernet port adapters can be configured for Inter-Switch Link (ISL), which supports VLANs between Catalyst 5000 high-performance switches and IEEE 802.1000 TB-VLAN for transparently bridging VLANs. (ISL is not supported in Release 11.1(1), but will be supported in Release 11.1(2) for RSP and RSP7000 processors with the FEIP and VIP cards.)

Because of its modular design, the VIP can be configured to support mixed media. Because this version of the VIP supports both Ethernet and Fast Ethernet, customers can now realize much better slot utilization in either the Cisco 7000 series or the Cisco 7500 series.

For full-duplex operation, the VIP-1FE is recommended.

  • VIP Distributed IP Flow Switching---VIP Distributed IP Switching enables the new VIP to make its own switching decisions. With this release, the VIP can be configured to support distributed IP switching. This feature is not available in Release 11.1(1). It will be available in a future maintenance release of Cisco IOS Release 11.1.

The primary goal of distributed IP switching is to provide scalable switching performance for the Cisco 7500 series of high-end multiprotocol routers. With the introduction of distributed IP switching, Cisco 7500 switching performance scales as more VIPs are introduced into the system. VIP distributed IP switching can switch to these output interfaces: VIP-FE/4E, VIP-FE, EIP, FIP, and FSIP, HIP, and MIP with HDLC encapsulations.

VIP Distributed Switching requires the architecture of the Cisco 7500 series Route Switch Processor (RSP). VIP distributed IP flow switching is not available for VIPs installed in Cisco 7000 series platforms.

  • High System Availability (HSA)

HSA is an advanced software feature of the Cisco 7500 architecture. HSA increases the availability and uptime of the Cisco 7507 and Cisco 7513 routers. This increase is accomplished through a master/slave relationship between two RSPs. If the slave RSP detects an error condition it automatically takes control and reboots the system without user intervention. This automatic action minimizes network interruption and increases system availability.

HSA can be used in the following situations:

  • Hardware backup. Protects against single processor failure.

  • Software error protection. Protects against critical software errors by keeping different software images on each RSP.

  • Configuration switching. Enables users to store different configurations in each RSP. If the new feature configuration on the master causes a system failure, the slave RSP takes over the routing function after a system reboot.

This feature became available in Cisco IOS Release 11.1(4).

Note HSA requires a ROM Monitor upgrade. See the "Important Notes" section for more information.

  • Standard Serial Interface Processor (SSIP) and Service Provider Multichannel Interface Processor (SMIP)---The SSIP is an 8-port serial card and supports the same physical interfaces and port speeds as the FSIP8.

The SMIP is a 2-port channelized interface processor that supports T1 and E1 interfaces and offers the same port configuration options as the MIP.

In conjunction with the Cisco 1000 series, the SSIP and SMIP provide the capability to cost-effectively network even the smallest branches. For Internet service providers, the SSIP, SMIP, and Cisco 1000 series significantly reduce the cost of adding customers, which allows Internet services to be profitably provided to a larger market.

The SSIP and SMIP do not currently support full Cisco IOS software functionality. Please refer to Product Bulletin 397, which details the Cisco IOS software functionality supported by the SSIP and SMIP.

Although these features are included in Cisco IOS Software Release 11.1, the SSIP and SMIP are already supported in Release 10.3(6), Release 11.0(4), and later.

  • Source-Route Bridging (SRB) over FDDI on Cisco 7500---Supports SRB from Token Ring to Token Ring over FDDI on the Cisco 7500 series. Previously, the only way to transport SNA and NetBIOS over FDDI was with remote source-route bridging (RSRB), which is process switched. With SRB over FDDI, traffic is autonomously switched, greatly improving performance for SRB traffic that uses FDDI as a backbone and eliminating the need for RSRB peer definitions.

Note Cisco routers do not support SRB over FDDI when the router is an end station on an FDDI LAN.

  • Flash Management Information Base (MIB) on Cisco 7500---The Cisco 7500 supports the new Cisco Flash MIB. This feature enables various SNMP operations on system Flash devices that normally require manual console access to the router.

The Flash MIB enables a user to use network management stations and CiscoWorks to manage and upgrade router software. With MIB support, this feature is now SNMP-manageable.

  • Cisco RSP7000---The RSP7000 provides an upgrade in the Cisco 7000 series routers to an integrated Route/Switch Processor (RSP), which was previously only available with Cisco 7500 series routers. RSP combines the switched routing and high-speed switching functions of the separate Route Processor (RP) and Switch Processor (SP), obsoleting the need for two separate processor units.

RSP7000 functionality is similar to a Cisco 7505 with RSP1, except that CyBus is not supported. CIP, FEIP, and VIP (CyBus interface processors) operate in CxBus mode.


Access and Communication Servers

  • Media Access Control (MAC) Security for Hublets (Cisco 2505, Cisco 2507, and Cisco 2516)---MAC security for Hublets goes down a layer in the OSI model to provide security detection and protection at the MAC layer. Each repeater port on the hub can be assigned an acceptable source MAC address. The hublet detects if the source address is different from the legal source address. If there is a violation, the port will be shut down (partitioned) for 1 minute. This capability currently exists.

In Cisco IOS Release 11.1, the network manager can have a trap message sent when the source MAC address violation occurs. The SNMP trap message may be sent once, or at a decaying rate. The decaying rate option provides the first SNMP trap message immediately, the second trap at 2 minutes, the third trap at 4 minutes. This continues until 32 minutes have passed. The decaying trap messages can be terminated by the NMS by using the MIB variable TrapAcked.

Additional MIB variables are provided in the agent to allow the NMS to query the violation. MAC security MIB variables provide information such as last illegal source address, timestamp of the first violation, timestamp of the last violation, and number of violation frames.

Because SNMP uses UDP, a single trap notification might get lost. It is possible to configure the router to send multiple traps at a decaying rate. This ensures that the trap message will be received by the NMS.

  • LANE on the Cisco 4500---The LANE feature emulates an Ethernet segment over ATM that allows higher-layer protocols and their applications to operate without modification. LANE features service components---LANE configuration server (LECS), LANE server (LES) and broadcast and unknown server (BUS)---as well as a client component called the LANE client (LEC). LANE includes a connectionless broadcast that can support important protocol mechanisms such as ARP. This service is not available in other ATM networks. In LANE, LE_ARP requests resolve MAC addresses to ATM addresses. LECS, LES, BUS, and LEC are supported on the router ATM interfaces.

LANE is also the underlying technology that supports virtual LANs (VLANs) over ATM networks. By providing the needed Layer 3 routing connection between Layer 2 VLANs, a Cisco 4500 or Cisco 4700 router with an NP-1A ATM network processor module and LANE technology provides standards-based routing between VLANs over ATM.

LANE requires Interim Local Management Interface (ILMI) and point-to-multipoint signaling capabilities on the switches on which it operates (VP tunneling is acceptable where signaling is not offered, such as a ATM WAN). The LANE services on the router ATM interfaces interoperate with Cisco LECs, including Cisco's ATM NICs and the Catalyst 5000. Cisco is pursuing interoperability with other third-party ATM LECs.


IBM Functionality Features

This section describes the IBM network software features and support that are new in the initial release of Cisco IOS Release 11.1.


New Features

The following new IBM software features are available:

  • Downstream Physical Unit (DSPU) Network Management Events---DSPU has been enhanced to support six new network management events. These events are mapped to SNMP traps and SNA messages and are used to notify network management when:

    • an upstream PU changes state

    • a downstream PU changes state

    • an upstream LU changes state

    • a downstream LU changes state

    • DSPU is unable to activate a downstream PU

    • DSPU is unable to activate a downstream LU

This feature simplifies network management by providing additional visibility of SNA network resources and by sending notifications about problems with PU and LU connectivity. When a downstream PU changes state, a DSPU is unable to activate a downstream PU, or a DSPU is unable to activate a downstream LU, it is mapped to an SNA message sent to a host operator, which generally appears in a NetView or NetMaster log. To minimize unnecessary noise across the network and in SNMP and NetView or NetMaster logs, there are four configurable notification levels (off, low, medium, and high).

  • Advanced Peer-to-Peer Networking (APPN) Enhancements---APPN enhancements include data link layer enhancements and enhanced logging and debugging functions.

Data link layer enhancements include:

  • APPN over Asynchronous Transport Mode (ATM) using RFC 1483.

  • APPN over the Point-to-Point Protocol (PPP) using RFC 1661.

APPN over PPP also allows APPN to be transported over an Integrated Switched Digital Network (ISDN).

  • APPN over Switched Multimegabit Digital Services (SMDS) using a Cisco-proprietary encapsulation.

Enhanced logging and debugging functions enable debug output that is more meaningful and useful, including better documentation of the error and debug output, more user control of the type and amount of debug output generated, and more descriptive information in the messages.

Because there is no standard way for transporting APPN over SMDS, a Cisco-proprietary method is used.

Note In some cases, APPN over SMDS may not interoperate with other vendors' SMDS implementations, because a proprietary method is being implemented.

  • Frame Relay Access Server (FRAS) Boundary Access Node (BAN) Support---BAN provides a way of connecting remote SNA offices over Frame Relay directly into a front-end processor. Unlike the FRAS boundary network node (BNN) feature supported in Cisco IOS Release 10.3, BAN includes the MAC address in every frame, eliminating the need to do SAP multiplexing if there are multiple SNA physical units (PUs) sharing a single PVC. BAN uses the RFC 1490 bridged-frame format.

BAN simplifies configuration in an environment where multiple remote SNA devices need to share a single PVC, and where there are no central site routers for SNA. It offers load balancing and provides the flexibility to build a redundant path to the NCPs.

Note BAN only applies to SNA devices on Ethernet or Token Ring. It does not apply to SDLC-attached devices. BAN requires NCP 7.3 at the central site. BNN and BAN can share the same DLCI to the NCP.


Data Link Switching+ (DLSw+) Features and Enhancements

The following features have been added to Cisco's DLSw+ software:

  • DLSw+ LNM Support---DLSw+ has been enhanced to support IBM's LAN Network Manager (LNM), enabling LNM to communicate to a remote DLSw+ router, and manage or monitor any Token Ring connected to a Cisco router.

LNM support includes configuration report services, ring error monitor, and the ring parameter server. In addition, the DLSw+ router notifies LNM of certain events that might occur on a Token Ring, such as notification of a new station joining the Token Ring, or that the ring has entered failure mode known as beaconing.

This feature will be available in a future Cisco IOS 11.1 software maintenance release.

  • DLSw+ Support on Cisco 7500---Support for DLSw+ Fast-Sequenced Transport (FST) and Direct on the Cisco 7500 series routers is added, increasing network design flexibility of Cisco 7500 series routers.

  • DLSw+ Management Information Base (MIB)---DLSw+ now offers a MIB for faster problem determination. In addition, the DLSw+ MIB is the basis for DLSw+ Logical Maps.

  • DLSw+ Multidrop PU 2.0/2.1 Support---Multidrop PU 2.0 and PU 2.1 support enables multiple PU 2.1 devices to share the same SDLC line. In addition, PU 2.0 and PU 2.1 devices can also now share the same SDLC line.

  • 80D5 (Ethernet version 2) Support---80D5 (Ethernet version 2) is now supported by DLSw+. This support extends DLSw+ to environments that have not converted to IEEE 802.3.

  • Local DLC Conversion over DLSw+---DLSw+ now supports local conversion between SDLC or QLLC and LLC2. With local conversion, only one DLSw+ router is required for conversion of a link-level protocol. Previously, a remote peer was required to perform this conversion.

  • DLSw+ Backup Peer Enhancements---DLSw+ allows you to specify a backup peer to use in the event that a primary peer fails. Previously, when the primary peer recovered, the backup peer connection terminated along with any sessions using that peer. The backup peer feature has been enhanced to allow the backup peer to remain active after the primary recovers, to prevent disrupting SNA and NetBIOS sessions a second time. Once the primary peer is active, all new sessions are established using the primary peer. The backup peer connection remains active until there are no active LLC2 connections on it or after a user-configurable idle time.

  • DLSw+ Enhancements for ISDN/Switched Environments---DLSw+ has been enhanced to allow more effective use of ISDN/switched lines:

    • ISDN links are allowed to terminate during idle periods, but still maintain SNA sessions.

    • The router can be configured to activate a peer dynamically under certain conditions (for example, when there is an SNA test frame or a NetBIOS Name Query for a preconfigured device). When there is no traffic on that peer, the peer connection is disabled.

These enhancements minimize WAN costs in switched environments. In addition, peer connections are only established when needed, maximizing scalability and minimizing cost.


Access and Communication Server Features

This section describes the access and communication server features that are new in the initial release of Cisco IOS Release 11.1.

  • NetBEUI over Point-to-Point Protocol (PPP)---Microsoft has published a draft RFC that defines a protocol for passing NetBEUI over PPP. Application of this RFC allows remote PCs with remote access client software to dial into network access servers connecting into NetBEUI networks. The protocol used in these connections is a PPP Network Control Protocol (NCP) called NetBIOS Frames Control Protocol (NBFCP).

NBFCP:

  • Supports both asynchronous and ISDN interfaces.

  • Is compatible with Microsoft's remote access client with NBFCP.

  • Supports NetBIOS name caching.

  • Supports NetBIOS name filtering.

With NBFCP:

  • PCs with NetBIOS applications and NBFCP-capable remote access clients can dial into Cisco access servers for access into NetBEUI networks.

  • Microsoft's remote access clients with NBFCP can dial into Cisco access servers for access into NetBEUI networks.

  • Modem Auto-Configuring---Modem auto-configuring allows Cisco access servers to discover and identify an attached modem and configure it with the appropriate modem command strings. Identification and configuration are performed for each line reset. Modem strings are kept in an internal database that administrators can add to.

With modem auto-configuring, no direct configuration of modems is required. All modems with a modem database entry are automatically recognized, and modems not found in the modem database can be defined clearly and quickly as the access server prompts for specific modem command strings.

  • Novell Asynchronous Services Interface (NASI) Support---Novell Connection Services (NCS) server uses NASI to provide outgoing serial line access for PCs with NASI client drivers. This function is generally used to provide dial-out modem services to PCs on SPX/IPX networks. Cisco access servers can now function as NCS servers providing dial-out over IPX for PCs. This allows Cisco access servers to:

    • Advertise their Novell Connection Services via SAPs.

    • Support NASI out-of-band, encrypted username and password authentication.

    • Support Cisco SAP filters and management controls.

Using the NCS server network, network managers can offer IPX dial-in and dial-out services on the same Cisco access server.

Note Because of Novell split-horizon rules it is necessary to disable all other NCS servers on the same network where the Cisco access server is deployed for NASI outbound connections.

  • Identification Protocol Support---Identification Protocol (also called "ident" or "the Ident Protocol"), specified in RFC 1413, is a protocol for reporting the identity of a TCP connection initiator to the connection-receiving host.

This feature allows the identification of a username associated with a TCP connection.

The Identification Protocol support is not useful for securing access servers. It is a protocol for identifying the other end of a TCP connection. It does not authenticate or authorize the connection.

  • Kerberos Authentication---Kerberos is an authentication protocol developed by the Massachusetts Institute of Technology (MIT). Its primary use is to authenticate users and the network services they use. This is accomplished by the issuance of "tickets" to both services and users by a "trusted" Kerberos server. These tickets have a limited life span and can be used in place of the standard user/password authentication mechanism if a service trusts the Kerberos server from which the ticket was issued. Cisco's implementation of Kerberos is based on code developed by CyberSafe, which was derived from the MIT code.

Cisco is implementing a two-phased approach to the implementation of Kerberos. Phase 1, delivered in Cisco IOS Release 11.1, permits authentication on the router using Kerberos. (Phase 2, which will be available in another major Cisco IOS software release, will allow a user to carry credentials to other services, such as Telnet, without having to re-authenticate.)

A Cisco white paper explaining Kerberos in more detail can be found on the World Wide Web (you need to be a registered CCO user) at: 
http://cio.cisco.com/warp/customer/106/1.html

  • Remote Authentication Dial-In User Service (RADIUS)---RADIUS is an access server authentication, authorization, and accounting protocol developed by Livingston, Inc. It is a distributed security system that protects remote access to networks and network services against unauthorized access. RADIUS has three components: a protocol with a frame format that utilizes UDP/IP, a server, and a client.

The server resides on a central computer typically at the user's site. The clients reside in the dial-up access servers and can be distributed throughout the network. The RADIUS client is available in Cisco IOS Release 11.1.

Cisco's implementation of RADIUS is currently defined in draft documents at ftp.livingston.com:pub/radius/draft-ietf-radius-radius-02.txt . Cisco's implementation is based on this version of the draft. Cisco will attempt to keep current with any newer drafts issued. A sample RADIUS server can be obtained from Livingston's FTP site.

RADIUS is configured on the network access server much like TACACS+.


Network Management Features

This section describes the network management feature that is new in the initial release of Cisco IOS Release 11.1.

  • Remote Monitoring (RMON) Support---The RMON MIB (RFC 1757) is added as an option to several Cisco IOS software feature sets for use on Cisco 2500 series routers. Full, 9-group Ethernet support is available and includes:

    • statistics: Tracks segment usage, errors, and frame-size distribution information.

    • history: Logs historical snapshots of RMON statistics at user-defined time intervals.

    • alarms: Detects changes in network behavior based on increasing and decreasing thresholds of performance and error statistics.

    • hosts: Provides basic traffic statistics, such as packets and octets in and out, broadcast, and total error counts for each network node or device based on MAC addresses.

    • hostTopN: Keeps a sorted list of top "talkers" by node-level statistics.

    • matrix: Tracks basic traffic information between physical source and destination pairs.

    • filter: Allows focused analysis by selectively reducing the number of packets to be captured remotely based on address, protocol, and user-defined data patterns.

    • capture: Acquires and buffers complete or partial packets for protocol decoding and detailed analysis with a console application.

    • event: Logs alarms and generates SNMP traps as a result of thresholds being crossed or capture buffers being filled.

Note As a security precaution, the packet capture group captures only useful packet header information; data payloads are not captured.

All Cisco IOS software images that do not explicitly include full RMON support include RMON alarm and events groups. These groups can be coupled with existing Cisco MIB variables and allow customers to set thresholds and alarms on any MIB variables supported by Cisco.

RMON not only provides visibility of individual nodal activity, it allows the monitoring of all nodes and their interaction on a LAN segment. RMON used specifically as an agent in the router allows network managers to view either only traffic that flows through the router or all Ethernet segment traffic not necessarily destined for the router.

An RMON console application such as Cisco Traffic Director or NETscout ManagerTM by Frontier Software Development, Inc., is required to take full advantage of the embedded RMON's network management capabilities.


Security Features

This section describes the security feature that is new in the initial release of Cisco IOS Release 11.1.

  • Lock-and-Key Access---Lock-and-Key access allows you to set up dynamic IP access lists that grant access per user to a specific source or destination host through a user authentication process.

Before Lock-and-Key access, IP access lists were created and maintained by manually defining lists on a router and distributing them to all other routers in the network. In networks with many hosts, this task could consume time and resources. Access lists do not provide any challenge mechanism beyond a static network address, making it possible for an unauthorized user to access network resources through any authorized network address. The Lock-and-Key access feature is an ideal solution for the proliferation of remote networks. Lock-and-Key access supports various WAN technologies such as ISDN, Frame Relay, X.25, dial-on-demand routing (DDR), and Point-to-Point Protocol (PPP).

When a user Telnets to a router configured with Lock-and-Key access, the software challenges the user to respond to a login and password prompt before placing a temporary entry in the dynamic access list. The network administrator can dictate an idle time-out or an absolute period for authorization and reauthorization.

Lock-and-Key access provides the following benefits:

  • Allows per-user authorization and authentication in a shared-media environment.

  • Authenticates a user beyond an IP network address.

  • Maintains authentication information at a central network access server such as TACACS, XTACACS, TACACS+, and RADIUS.

  • Provides application independence---Lock-and-Key access does not require modification to user applications.

  • Supports one-time password token cards.

  • Provides a flexible policy mechanism to require remote reauthorization during periods of inactivity.

  • Understands the concept of organizational templates, which allow the network administrator to create an access list for a group of users with similar access requirements, but provides unique authentication challenges to each user.

    fig_2.gif

Warning Lock-and-Key allows an external event to place an opening in the firewall. Once this opening is placed, the router is susceptible to source-address spoofing. To prevent this, you need to provide encryption support using IP authentication or encryption.

Lock-and-Key access requires Telnet. Standard Telnet is the required application on the host platform that activates a Lock-and-Key session.

Further information on Lock-and-Key access can be found on the World Wide Web in the Cisco IOS Lock and Key white paper (Product Bulletin 308) at (you need to be a registered CCO user): http://www.cisco.com/warp/customer/417/66.html


Important Notes

This section describes warnings and cautions about using the Cisco IOS Release 11.1 software. It discusses the following topics:


BSC and SDLC Commands in Release 11.1(2)

In Release 11.1(2), the bsc fdx and sdlc hdx commands were deprecated and replaced by the full-duplex and half-duplex commands, respectively. The deprecated commands continue to be supported in Release 11.1(2) and later, but might not be supported in the next major release of Cisco IOS software.


Upgrading to a New Software Release

If you are upgrading to Cisco IOS Release 11.1 from an earlier Cisco IOS software release, you should save your current configuration file before installing Release 11.1 software on your router.


Channel Interface Processor (CIP) Microcode

CIP microcode is now available as a separate image, unbundled from the Cisco IOS image. CIP microcode (for the CIP or Second-Generation (CIP2) card) resides only in router Flash memory as multiple files. The router loads a "kernel" to the CIP (based upon hardware revision), and the CIP selectively loads and relocates the software it requires from the router's Flash memory. The CIP image is available on pre-loaded Flash memory cards, on floppy diskette, or via FTP from Cisco. Every version of Cisco IOS Release 11.1 has a corresponding version of CIP microcode. Refer to the Channel Interface Processor (CIP) Microcode Release Note and Microcode Upgrade Requirements publication (Document Number 78-2958-xx) for information about the recommended pairs of Cisco IOS Release 11.1 and CIP microcode.

The CIP loader has the following effect on the router's system memory requirements:

  • DRAM utilization decreases by 0.5 MB to 1 MB

  • Bundled image sizes decrease by 0.5 MB to 1 MB

  • Flash memory utilization increases by 1 MB to 1.5 MB

Consider the following before you use the CIP loader:

  • If you have a router with Release 11.1 and a Release 11.1 CIP image on a Flash memory card, no action is required. The CIP microcode will load automatically upon booting the router.

  • If you have an existing router with Release 11.1 in Flash memory or ROM and a pre-11.1 Flash memory card, either:

    • Replace the Flash memory card with a Release 11.1 pre-loaded Flash memory card, or

    • Boot the router with Release 11.1 software (CIP load will fail), then copy the Release 11.1 CIP image to the Flash memory card, and reboot the router.

When the CIP image is copied to an existing Flash memory card, the existing flash copy commands are used, just as before. If a CIP image other than the default for the release is being used, then the microcode cip flash configuration command must be issued.

The show microcode command has been expanded to display the default CIP image name for the Cisco IOS release.

Note The router must already be running Cisco IOS Release 11.1 before performing a copy of the CIP image to Flash memory, because the CIP image must be "exploded" from the single image file on the TFTP server to multiple files in Flash memory. This capability is added in Release 11.1.

There are a number of ways to determine what is loaded on each CIP:

  • The CIP MIB has been enhanced to show the segments loaded on each CIP and their version and compilation information.

  • The show controller cbus command has been expanded to include segments loaded and their version and compilation information.

Multiple CIP cards of different hardware revisions can run in the same router.


Cisco 7500 Series High System Availability (HSA)

To successfully use the HAS feature, you should take note of the following:

  • The HSA feature available on the Cisco 7500 series routers requires a ROM monitor upgrade to ROM monitor version 11.1(2), or later.

  • For spare RSP2 cards to function with HSA, they must also be upgraded. Spare Flash cards require Release 11.1(4) or higher boot or system images.

  • HSA installation requires the both RSP2s have the same amount of DRAM (24 MB minimum each RSP2).

  • To use the HSA feature, you must use a Cisco IOS feature set image that contains a "v," such as the RSP subset image rsp-jv-mz.111-4.

  • You should also note the following HSA-related caveats:

    • The BOOTDLR variable of the slave RSP is incorrectly set to NVRAM by default. This could cause a netbooting of the slave to fail if the master RSP were to crash. [CSCdi48170]

    • On-line insertion and removal (OIR) of an HSA slave RSP (removing an HSA slave RSP with the router online) causes the router to reload. [CSCdi57076]

    • The HSA feature does not work if a Versatile Interface Processor (VIP) or Second-Generation VIP (VIP2) is installed in the router. If you install a VIP or VIP2 in an HSA-configured system, or if you install a second RSP2 into a system containing a VIP or VIP2, the system will crash with the following error message: 
%RSP-3-INVRSP_IPC: Slave RSP slot x not supported with VIP slot y, crashing router

[CSCdi60891]


VLAN Routing

Support for VLAN routing is not available in Release 11.1(1). Support for this feature is available in Release 11.1(2). VLAN routing allows Inter-Switch Link (ISL)-encapsulated IP, IPX, and transparently bridged traffic to be routed or bridged to any other VLAN or native interface.


Netbooting from VIP

To netboot from Ethernet or Fast Ethernet ports on a VIP card the system must contain version 11.1 boot ROMs. If the system contains version 11.0 boot ROMs, you can work around this requirement by using the boot bootldr device:filename global configuration command to load a bootstrap image from Flash memory.


Source-Route Bridging (SRB) over FDDI

This feature supports forwarding of source-route bridged traffic between Token Ring and FDDI interfaces on the Cisco 7000, Cisco 7010, and Cisco 7500 series routers. Previously, the only way to transport SNA and NetBIOS over FDDI was with remote source-route bridging (RSRB), which is either fast switched (direct or Fast-Sequence Transport (FST) encapsulation) or process-switched (TCP encapsulation). With SRB over FDDI, traffic can be autonomously switched, greatly improving performance for SRB traffic that uses FDDI as a backbone. This feature eliminates the need for RSRB peer definitions to connect Token Ring networks over the FDDI backbone.

Note SRB over FDDI does not support RSRB traffic forwarded to RSRB peers. Routers that have connections to local Token Ring networks as well as RSRB connections to remote networks cannot use this feature. The work around is to move the RSRB connections to routers that are not connected to the FDDI backbone.


Enabling IPX Routing

The Token Ring interface is reset whenever IPX routing is enabled on that interface.


Using AIP Cards

Cisco 7000 series ATM Interface Processor (AIP) cards that support E3, DS3, or Transport Asynchronous Transmitter/Receiver Interface (TAXI) connections and that were shipped after February 22, 1995, require Cisco IOS Release 10.0(9), 10.2(5), 10.3(1), or later.


Booting Cisco 4000 Routers

You must use the Release 9.14 rxboot image for Cisco 4000 routers because the Release 11.0 rxboot image is too large to fit in the ROMs. (Note that rxboot image size is not a problem for Cisco 4500 routers.) However, because the Release 9.14 rxboot image does not recognize new network processor modules, such as the Multiport Basic Rate Interface (MBRI), its use causes two problems:

  • You cannot boot from a network server over BRI lines. Instead, you can boot either from a network server over other media or use the copy tftp flash command to copy images over BRI or other media to Flash memory. If you use the copy tftp flash command over a BRI interface, you must be running the full system image.

  • If you use the rxboot image on a Cisco 4000 router that is already configured, the following error messages are displayed, with one pair of messages for each BRI interface configured: 
Bad interface specification
No interface specified -- IP address
Bad interface specification
No interface specified -- IP address


Using LAN Emulation (LANE)

Note the following information regarding the LAN Emulation (LANE) feature:

  • LANE is available for use with Cisco 4500, 4700, 7000, and 7500 series routers connected to either an LS100 or LS1010 switch. LANE requires at least version 3.1(2) of the LS100 software, which requires a CPU upgrade if you are currently running software prior to version 2.5. Send email to lane-info@cisco.com for further information on obtaining the supported configuration.

  • Interoperability testing with other switches and LANE implementations has been done at industry-sponsored interoperability events, and is an ongoing effort. For the most current information, send email to lane-info@cisco.com .

  • The LS2020 cannot be used for LANE because it does not support UNI 3.0 and point-to-multipoint SVCs.

  • Routing of IP, IPX, and AppleTalk is supported.

  • LANE does not support

    • DECnet, CLNS, VINES, and XNS

    • LANE over PVCs

    • HSRP

  • AppleTalk Phase 1 cannot be routed to AppleTalk Phase 2 via LANE.


Forwarding of Locally Sourced AppleTalk Packets

Our implementation of AppleTalk does not forward packets with local-source and destination network addresses. This behavior does not conform to the definition of AppleTalk in Apple Computer's Inside AppleTalk publication. However, this behavior is designed to prevent any possible corruption of the AppleTalk Address Resolution Protocol (AARP) table in any AppleTalk node that is performing MAC-address gleaning.


Using Source-Route Transparent Bridging (SRT) and Source-Route Bridging (SRB) on Cisco 2500 and Cisco 4000 Routers

Certain products containing the Texas Instruments TMS380C26 Token Ring controller do not support SRT. SRT is the concurrent operation of SRB and transparent bridging on the same interface. The affected products, shipped between March 30, 1994, and January 16, 1995, are the Cisco 4000 NP-1R, Cisco 4000 NP-2R, Cisco 2502, Cisco 2504, Cisco 2510, Cisco 2512, Cisco 2513, and Cisco 2515.

Units shipped before March 30, 1994, or after January 16, 1995 are not affected. They use the Texas Instruments TMS380C16 Token Ring controller, which supports SRT.

SRT support is necessary in two situations. In one, Token Ring networks are configured to SRB protocols such as SNA and NetBIOS, and they transparently bridge other protocols, such as IPX. In the other situation, SNA or NetBIOS uses SRB and Windows NT is configured to use NetBIOS over IP. Certain other configuration alternatives do not require SRT (contact the Technical Assistance Center for more information).

As of Release 10.3(1), SRB in the following Cisco IOS features sets is no longer supported: IP, IP/IPX, and Desktop. To use SRB, you need one of the following feature sets: IP/IBM base, IP/IPX/IBM base, IP/IPX/IBM/APPN, Desktop/IBM base, Enterprise, or Enterprise/APPN. In most non-IBM Token Ring environments, the multiring feature in IP, IP/IPX, and Desktop eliminates the need for IP/IBM base, IP/IPX/IBM base, IP/IPX/IBM/APPN, Desktop/IBM base, Enterprise, or Enterprise/APPN.


Release 11.1(5a)

After the release of Cisco IOS Release 11.1(5), a caveat was discovered within the Cisco IOS rsp- images. It was determined that this caveat was significant enough to merit a rebuild of the rsp- images. The rebuild includes the caveat fix and is renumbered to 11.1(5a).

This defect is bug CSCdi66673 and is described as follows:

When Ethernet runt packets are received by Cisco 7500 series router processors (RSP1, RSP2, or RSP7000), a Reserved Exception crash or a QAERROR error will occur. When either of these problems happens, a switching complex restart is forced. The Reserved Exception crash has the following output: 

Queued messages:
Aug 14 10:44:16: %RSP-3-ERROR: memd write exception, addr 08000000
Aug 14 10:44:16: %RSP-3-ERROR:   RSP alignment error on write to QA, addr 080000
00
*** System received a reserved exception ***
signal= 0x9, code= 0x0, context= 0x60c72fd0
PC = 0x60107514, Cause = 0x2020, Status Reg = 0x34008702
DCL Masked Interrupt Register = 0x000000ff
DCL Interrupt Value Register = 0x00000000
MEMD Int 6 Status Register = 0x00000000

The QAERROR error has the following output: 

Jun 17 10:50:23.329: %RSP-2-QAERROR: reused or zero link error, write at addr 03
08 (QA)
  log 260308C0, data A816FFFF 00000000

Release 11.1(5a) and all subsequent releases of Cisco IOS software, including Release 11.1(6), include the fix for this caveat.


Release 11.1(7) Caveats

This section describes possibly unexpected behavior by Release 11.1(7). Unless otherwise noted, these caveats apply to all 11.1 releases up to and including 11.1(7). The caveats listed here describe only the serious problems. For the complete list of caveats against this release, use the Cisco Connection Documentation, Enterprise Series CDs or access CCO as described in the section "Cisco Connection Online" later in this document.


Basic System Services

  • When multiprotocol traffic such as IP, DECnet, XNS, AppleTalk, and IPX is passed to the Cisco 2500 or the Cisco 4500 router through a Token Ring interface, the router is unable to accept all the traffic. This sometimes results in a Token Ring interface reset and dropped packets. [CSCdi44793]

  • On Cisco 7000 series routers, online replacement of one interface processor card (for example a TRIP or an FSIP) with a different type causes the output for both the show ip interface brief and show interface commands to display information for both the old and new cards. On rare occasions, this procedure also results in the continual reinitialization of the newly inserted card.

The only known workaround is to completely unconfigure the old card before replacing it with the new card. In extreme cases, it may be necessary to issue a write erase command, reboot the router, and then redefine the existing interfaces to completely remove all configuration traces of the old card. Once the information that is displayed by the show commands is self-consistent, the newly inserted card behaves normally. [CSCdi49800]

  • The boot config nvram: configuration command which was added for the RSP platform interacts improperly when the service compress-config command is enabled. This causes the NVRAM to become locked, and the router must be rebooted to free the NVRAM. [CSCdi52587]

  • On Cisco 7000 series routers, a system reload may occur when copying a configuration from Flash memory to the unsupported target name "nvram:". [CSCdi57005]

  • Interrupt-level IP fragmentation is not supported. [CSCdi60461]

  • Release 11.1(471) had a build error, possibly caused by a mishap in the build execution. The follow-up build of 11.1(472) resolved this issue. If you are now using 11.1(471), do not reformat the boot-flash or PC/MCIA Flash cards, and upgrade to 11.1(472) or later as soon as possible. [CSCdi61255]

  • In cases where a complex queuing strategy is desired that uses rules based on interfaces intermixed with rules based on protocols, the desired strategy cannot be recovered from a saved configuration. The order that the rules are entered is the order that the rules are applied. This works as desired. However, the order of entry is currently not maintained when the rules are stored in a sorted order in the configuration. Hence upon reboot, the behavior is different because the order of the rules has changed. This does not affect homogeneous rule systems; for example, systems where all the rules are based on interfaces or on protocols. It affects only more complex strategies where the rules are intermingled. [CSCdi63068]

  • The router might reset and indicate memory corruption when the configuration is modified via SNMP. [CSCdi66587]

  • There is a problem with the console component of the Cisco 2517, Cisco 2518, and Cisco 2519 hub routers.

Under certain conditions the console port locks up, and it appears that the router has ceased functioning. This occurs when attempting to display several lines of output in a short period of time. Issuing a show memory command after entering term length 0 at the prompt will slmost always cause the console to lock up.

Using debugging features that display several lines of output (for example, using the debug ip packet command after entering the term length 0 command at the prompt) also causes the console to lock up.

If the console locks, the router is still operational. It is possible to Telnet to the router and continue managing it in a normal manner.

There two ways to deal with this problem:

  • Press the reset button on the hub. This will restart the hub management code and the console function. The hub will still pass packets between devices connected to it and to the router that is attached to the hub as well. Any management stations monitoring the HUB will report a temporary outage.

  • Slow the speed that the AccessPro presents data to the hub's console port. This can be done in two ways:

A temporary method (not saved when the router is rebooted): 
Router#terminal speed 2400 
Router#^Q 
<<C>>ttt -c4 -q17 -b2400 
Router#

A permanent method (saved after the router is rebooted):

Instead of using the interactive terminal speed setting from the Router# prompt, you can permanently set the AccessPro's console speed to 2400 baud by altering the config register settings.

The config registers are a two-byte field that control various aspects of a router's behavior when it boots.

See the virtual register configuration settings in any router hardware and installation guide for more information on this subject.

Bits 11 and 12 control the console speed. Setting them both to 1 will result in a permanent 2400 baud setting. 
15                 0
 1111.1111.1111.1111
    - - 
   12 11 

Router#conf t 
Router-config#conf 0x3902 
Router-config#^Z 
Router#write mem 
Router#show version 
.
.
.
Configuration registers is 0x2102 (will be 0x3902 at next reload). 
.
Router#reload 
Proceed with reload? (confirm) y

The configuration sequence shown above will set the config registers to ignore the break sequence, boot from ROM if network boot fails, boot from Flash memory, and use 2400 baud as the console speed. [CSCdi68382]

  • On some devices, SNMP GetNext requests performed on the Cisco Discovery Protocol (CDP) MIB can cause the device to pause for an extended length of time. [CSCdi69892]

  • In cases where an accountable task has a duration shorter than the time is takes to contact the TACACS+ accounting server, the stop record may be discarded without being transmitted to the server. [CSCdi70312]

  • A MIP interface with more than 64 kbps (more than 2 time slots) may need to be tuned with more tx-limit than the default if the interface is experiencing output stuck. The tx-limit can be tuned using the tx-queue-limit interface configuration command. In general, the tx-limit should be tuned just to support the interface line rate. This normally can be achieved by the formula:

r -- tx-limit = (default tx-limit) * (number of time slots).

After the tx-limit is tuned, it is recommended that the router be reloaded. [CSCdi70535]


EXEC and Configuration Parser

  • The router might crash in response to the command no boot system flash in config mode if a filename is not specified. To work around, use the full name of file when removing this line from the configuration (no boot system flash filename). [CSCdi70404]


IBM Connectivity

  • IPX All Stations Broadcasts Explorers are not fast switched when source-route bridging for IPX is configured. [CSCdi41043]

  • The Find Name NetBIOS broadcast is sent from the Token Ring interfaces even though the proxy-explorer and NetBIOS name caches are configured on the interface. To work around, run back-level software. [CSCdi41972]

  • After you configure a LAN Network Manager (LNM) PC with a bridge definition that contains the target interface MAC addresses on the router, be cautious of the following behavior: If a no source-bridge local-ring bridge-number target-ring command is subsequently entered for one of the interfaces previously configured on the LNM PC, and a Link Bridge command is then entered on the LNM PC, the router will halt with a bus error indication. The only workaround is to ensure that no source-bridge local-ring bridge-number target-ring commands are not executed on the router after you define the target LNM server bridge on the LNM PC. [CSCdi41997]

  • QLLC devices that are connected through a router using QLLC/LLC2 conversion might occasionally experience poor response time. [CSCdi44923]

  • When using APPN/DLUR on a Cisco 4500, Cisco 4700, or Cisco 7500 router, DLUR may accept only one downstream PU for dependent session activation at a time. [CSCdi47584]

  • On Cisco 2500 series routers, RSRB fails using FST encapsulation on PPP or HDLC. The workaround is to use TCP encapsulation when bridging over ISDN links. [CSCdi48888]

  • The router might crash when an SNMP Get is issued for ciscoDlswIfSapList from a management station. [CSCdi49400]

  • OID is returned on an SNMP GetNext message for ciscoDlswIfRowStatus, and ciscoDlswIfVirtualSegment is not incremented. This may cause the application on the management station issuing this command to go into an infinite loop. [CSCdi49401]

  • The Cisco DLSw MIB returns an incorrect value for ciscoDlswVersions, which is inconsistent with the Cisco DLSw MIB definition. [CSCdi49426]

  • The Cisco DLSw MIB returns an incorrect value for ciscoDlswVendorID, which is inconsistent with the Cisco DLSw MIB definition. [CSCdi49430]

  • OID returned on an SNMP GetNext command for ciscoDlswCircuit is not incremented. This may cause the application on the management station issuing this command to go into an infinite loop. [CSCdi49437]

  • Explorers incoming from RSRB to the local Token Ring on low-end platforms might not be forwarded. [CSCdi50509]

  • The dlsw remote-peer frame-relay interface serial command does not work on a point-to-point subinterface. The workaround is to use multipoint and do LLC mapping. [CSCdi55085]

  • QLLC cannot use X.25 PVCs for DLSw+. The workarounds are to use RSRB or to use X.25 SVCs. [CSCdi58735]

  • When RSRB is run on a Cisco 7000 series router, the router fails to see a response to ARE frames put on a Token Ring interface. [CSCdi60824]

  • If source-route bridging is configured on a Token Ring interface, the router may continuously reload itself. This bug first appeared in Release 11.1(4). The workaround is to go back to Release 11.1(3.4) or earlier. [CSCdi65481]

  • The global source-bridge largest-frame command does not properly set the largest frame size when using source-route bridging. [CSCdi65918]

  • When SRS is run on a Cisco 7010 router, the router fails to source-route-bridge nonbroadcast VINES frames with "bcbc" SAP. The workaround is to downgrade to Release 10.3. [CSCdi66460]

  • For STUN virtual multidrop configurations running local acknowledgment and STUN quick-response to accommodate AS/400 polling requirements, an AS/400 NPR timeout occurs if a remote PU T2.1 or T1 controller fails to activate when responding to the initial XID poll. The workaround is to disable STUN quick-response, issue the sdlc k 1 command on all SDLC interfaces, and place an idle-character mark on the SDLC lines to the AS/400. [CSCdi66681]

  • In environments that include a Cisco 7500 router and Cisco 4000 series combination, connection establishment and data transfer may suffer severe performance degradation with some configurations involving SDLLC and RSRB/FST over X.25. [CSCdi68442]

  • The mid-range and low-end FDDI SRB implementation does not work over DLSw or RSRB. The problems involve Layer 2 MAC address adjustments and checksum validity. [CSCdi70118]

  • If SRB explorer traffic is so low that no explorer is forwarded on a Token Ring interface for 25 days, the interface stops forwarding SRB explorers. The symptoms from the show source command are that the "flushed" count increments for every explorer received while no "expl_gn" explorers are counted to the remote peers.

This problem causes connectivity loss without apparent reason. A short-term workaround is to reload the affected router. [CSCdi70559]

  • When segmentation or reassembly is involved in a DLUR-managed LU-LU session (that is, the MTU for the downstream link to the PU is smaller than the MTU for the upstream link toward the host) and the RU size is larger than can be transmitted in a single frame (most common with IND$FILE transfers from a PU to the host), the router may reload with an "intermediate_reassembly" or a memory corruption stack trace. [CSCdi72260]

  • On a Cisco 7000 router running an RSP7000 with Release 11.1(6), CIP microcode cannot be read if it has been loaded into Bootflash. The workaround is to load the CIP microcode into Flash. [CSCdi72463]

  • A defect introduced by the fix for defect CSCdi69231 may cause NSP to stop working. The releases affected are 11.0(11.2), 11.1(6.2), and 11.2(1.1). The following messages may be displayed when NSP stops working: "SNA: Connection to Focal Point SSCP lost." and "SNA: MV_SendVector rc = 8001". [CSCdi72696]

  • Token Ring interfaces configured for IBM automatic spanning tree might not insert into the ring. The workaround is to configure source-bridge spanning. [CSCdi72867]


Interfaces and Bridging

  • The serial interface on Cisco 2500 series routers enters a looped state if it is configured as a backup DTE interface and if the cable is disconnected and reconnected a few times. A clear interface command fixes the problem. [CSCdi32528]

  • The show diagnostic command does not display Fast Ethernet Interface Processor (FEIP) port adapter information. [CSCdi33967]

  • Issuing the ip-cache optimum command on an FDDI interface and then rebooting might add the no ip-cache optimum command to the configuration instead. [CSCdi50778]

  • Version 1.6 Rev C0 EIP cards may cause cache parity errors on all Cisco 7500 series and RSP7000 systems. The cache parity errors may cause system reloads. The hardware revision and version can be determined by issuing the show diagnostic command. This problem is resolved in EIP microcode rsp_eip20-2 or above. [CSCdi52082]

  • In Cisco 7000 and Cisco 7010 routers, the hotswap code preallocates interface structures for use by hotswap. These interface structures are then unavailable for other purposes, such as configuring subinterfaces, thus decreasing the total number of interfaces that the router can support. [CSCdi57893]

  • Under a sudden burst of moderate load, MIP controllers cycle, taking all attached interfaces down. This behavior is sporadic, and the router recovers within a few minutes without any user intervention. [CSCdi65044]

  • A Cisco 7500 router in a transparent bridging environment might suffer memory fragmentation such that the largest available memory block is 120k. [CSCdi67513]

  • The Fast Ethernet card might fail to see incoming traffic. A reboot of the system is required to restore functionality. Note that a shut / no shut command sequence does not fix the problem. [CSCdi70386]

  • When an ARP packet is received from an ATM interface, the router might send out a total of two ARP packets to the Ethernet interface. [CSCdi70533]

  • Routers are responding to packets not destined to them because of a problem in ISL encapsulation. This creates routing loops. [CSCdi71152]

  • Weighted fair queuing, custom queuing, and priority queuing should not be enabled on a MIP interface. In addition, the MIP tql should be no smaller than 32. Note that the T1 controller does not need to be reset when outhung is cycling. [CSCdi73106]


IP Routing Protocols

  • OSPF fails to form adjacencies over an ATM point-to-point interface. [CSCdi54579]

  • snmpwalk for ospfLsdbTable on a router running Release 11.1(3.2) results in the message "no MIB object contained under subtree." [CSCdi69097]

  • The most efficient way to clear an IP host route learned by OSPF from the IP routing table (for example, 10.1.1.1/32) is to clear the network route (for example, 10.1.1.0/24). [CSCdi70175]

  • When a primary active router that has gone down comes back up, it is possible that both routers might forward packets instead of just the primary. [CSCdi70693]

  • The system suffers a gradual loss of free memory whenever ip sd listen or ip sdr listen are enabled. [CSCdi72863]

  • It is possible for use of the DNS Name Service for alias lookups to cause the router to reload. Lookups of canonical names do not exhibit this problem. [CSCdi73022]


ISO CLNS

  • If secondary addresses are configured on an interface that is otherwise configured unnumbered, the interface routes corresponding to these addresses are not advertised in IS-IS. A workaround is to number the interface. [CSCdi60673]


Novell IPX, XNS, and Apollo Domain

  • Some SAPs may not be seen when the interface is flapping running IPX Enhanced IGRP. The workaround is to clear the IPX Enhanced IGRP neighbors. [CSCdi72438]


Wide-Area Networking

  • TCP header compression does not work over Point-to-Point Protocol (PPP), ISDN, and asynchronous dialer interfaces. To work around, turn off ip tcp header-compression. Note that "non-dialer" asynchronous interfaces used for dial-in PPP access are not affected. [CSCdi19199]

  • Both the one-word connect feature and the EXEC connect command fail without printing any error indication. This only occurs in Enterprise software images. [CSCdi41547]

  • If you have a VIP controller and you are using a Cisco 7000 series with a silicon switching engine (SSE), be aware that the SSE cannot access the second port adapter when the VIP is installed in slot 4. To work around, install the VIP in slots 0 through 3. [CSCdi41639]

  • If you enter a dialer string dial-string command on an ISDN interface instead of a dialer map command, the router may crash. [CSCdi42764]

  • The AIP cannot be configured to issue idle cells instead of unassigned cells. [CSCdi48069]

  • When configuring IPX over multiple paths, and one of the interfaces is an ISDN interface, the router may reload. To avoid this, disable fast switching on the ISDN interface using the no ipx route-cache command. [CSCdi50325]

  • Cisco 7000 series routers may reload themselves and display the following output: 
ILMI: system restart; bus error at PC 0xBC552, address 0xDEADBEEF

A show stacks command will display: 
Stack trace from system failure: FP: 0x9B80D8, RA: 0x3A7FB6 FP: 0x9B811C, RA: 0x3A78E4 
FP: 0x9B8128, RA: 0x172E74

[CSCdi53915]

  • Under very rare circumstances, when using software flow control on the AUX port under heavy load, the line may end up in a hung 0 state. The output of a show line command indicates "Status: Ready, Connected, Active, Waiting for XON, Sent XOFF." If XOFF has been sent and the device is waiting for XON, issue a clear line command to recover. [CSCdi56432]

  • Input hung (input queue 76/75) might be observed in an ATM network. Blocked packets appear to be RFC 1577 related. [CSCdi60007]

  • On lines running software flow control without modem control, attached devices may get stuck in a flow-controlled state if the Cisco TTY is reset while it is flow-controlling the attached device. [CSCdi60204]

  • In certain circumstances, the router might reload if a dialer interface (ISDN/Serial/Async) is used for load-backup or failure-backup along with an IPX routing protocol like RIP/Enhanced IGRP and the primary and the backup interface are active. This is usually noticed immediately after the dialer interface connects. [CSCdi61504]

  • PPP callback over ISDN using a PRI line sometimes fails. This appears to happen only when the originating call is received by the PRI on channel 31. The PRI router then terminates the call, initiates PPP callback, then returns the error messages "callback timer expired" and "no interface available." [CSCdi65216]

  • When configuring PVCs on the AIP, the router may experience a failure to create more PVCs when the number of VCCs configured is well below the maximum allowed. This failure occurs when the number of VPI values used exceeds a limit.

The messages that occur due to this type of failure include: 
15:06:19: %AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Setup VC command (error 
code 0x0008) 

15:06:19: %ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1500, VPI=10, VCI=257) on 
Interface ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC)

The limit to the number of VPI values used depends on the configuration of the VC-per-VP configuration parameter. When VC-per-VP is 1024 (the default), 33 VPI values may be used. To workaround this limitation, implement the atm vc-per-vp command on the particular ATM interface, lowering the number of VCs per VP. This results in a corresponding increase in the number of VPI values that can be used. [CSCdi67839]

  • A Cisco 4500 might crash after encapsulation ppp is configured under int Sx:15 of PRI. [CSCdi68946]

  • In Cisco 2500 series devices, it it possible that upon receipt of INFORMATION from a switch, ISDN calls are cleared, following a SETUP_ACK. [CSCdi69230]

  • Using TACACS+ with dialback over a rotary group causes the authorization to fail for the user when the callback script aborts or finishes incorrectly, so failover to another line of the rotary occurs. The call is made, but an internal error occurs when debugging TACACS+. [CSCdi70549]

  • A software-forced reset might occur when a serial interface running PPP loses connection. Upon re-establishment, the PPP stack might overflow, causing memory violation. [CSCdi72248]

  • If the encapsulation on a BRI line is changed from HDLC to PPP while the interface is shutdown, the line will reset every 30 seconds when the line is brought up. A reload is required to fix this problem if it occurs. The workaround is to use the no shut config command to bring the line up before changing the encapsulation on the line. [CSCdi72290]

  • An AIP in a Cisco 7500 series router might drop a virtual circuit (VC) when a sustained 54000 packets per second are switched from other interfaces in the router to the AIP. In this situation, if a network address is mapped to the VC, the map will remain, despite the fact that the VC has died. Note that this problem was detected in a test environment using multi interface traffic generators.

To make the mapping and VC available again, remove the map statement from the router configuration and re-add it. [CSCdi73226]


Release 11.1(6) Caveats/Release 11.1(7) Modifications

This section describes possibly unexpected behavior by Release 11.1(6). Unless otherwise noted, these caveats apply to all 11.1 releases up to and including 11.1(6). For additional caveats applicable to Release 11.1(6), see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 11.1(7).


AppleTalk

  • When ARAP is configured, the message "%SYS-2-INPUTQ: INPUTQ set, but no idb, ptr=xxxxx %SYS-2-LINKED: Bad enqueue of xxxxx in queue yyyyy" might appear and the router might reload. [CSCdi63635]

  • There has been a request for additional debugging messages for the arap logging command. The requested command is arap logging debug-extensions, which enables seven advanced debugging messages in addition to the traditional ARAP logging messages. [CSCdi68276]

  • AppleTalk domains do not operate correctly when configured on subinterfaces. The domain properties will be applied to the main interface rather than its subinterface(s). The workaround is to disable AppleTalk fast switching. [CSCdi69886]


Basic System Services

  • If a microcode reload command is issued over a Telnet connection, the router may enter an infinite loop or display the message "%SYS-3-INTPRINT: Illegal printing attempt from interrupt level." whenever microcode is downloaded. [CSCdi47580]

  • Multiple simultaneous copy operations to the Flash devices on a Cisco 7500 router (bootflash:, slot0:, and slot1:) will cause the router to crash. This only happens when more than one user is logged in to the router (for example, one at the console, and one via Telnet) and both are trying to perform a copy tftp flash at the same time. This is true even if the two users are trying to write to different devices. [CSCdi50888]

  • When service compress-config is configured, accessing the configuration stored in NVRAM from simultaneous Exec sessions might leave the NVRAM locked and inaccessible. The only recourse is to reload the software. [CSCdi68092]

  • A Cisco 2511 may reset with the error message "System restarted by bus error at PC 0x30B65F4, address 0xD0D0D29." [CSCdi69068]

  • The debug chat line x command and parser do not display the chat script components correctly if the octal 7 or 8 bit \xxx format is used to specify a byte greater than 0x7f. [CSCdi69149]

  • If a new MIP channel group is added after a microcode reload has been performed, the system must be rebooted to ensure correct operation. [CSCdi70909]


DECnet

  • DECnet may fail to work properly when using an area number of 63 for L2 routers. The symptoms are being unable to ping (DECnet) between two area routers, one of which is using area 63.x, and having the show dec command report that the "attached" flag is false even though the show dec route command shows routes to it. The workaround is to use the decnet attach override command to force the router into an attached state. This command is available in Releases 10.2(7.3), 10.3(4.4), 11.0(0.13), and all versions of Release 11.1 and higher. [CSCdi69247]


EXEC and Configuration Parser

  • Under some circumstances, a Cisco AS5200 may run low on memory or may run out of memory after processing more than 11,000 calls. A small amount of memory may be lost under two conditions, only when aaa new-model is configured: when a user hangs up at the "Username:" prompt, or when a user successfully autoselects with the autoselect during-login command configured. [CSCdi67371]


IBM Connectivity

  • Some IBM LLC2 implementation devices send an RNR when they run out of buffers and drop the frame. This causes data traffic flow to halt for 30 seconds. Non-IBM LLC2 devices using IEEE LLC2 send REJ rather than RNR, thus no delay occurs. [CSCdi49447]

  • With Release 11.0 and a direct Escon-attached CIP, the host may "box" the CIP if the router is reloaded without the CIP being varied offline. This problem has not been seen with CIPs connected through a director or if the CIP is taken offline before the router is reloaded. The workaround is to vary the device offline before reloading the router. [CSCdi59440]

  • When the PS/2 Link Station Role is configured as Negotiable, the XID(3) Negotiation may not complete. The workaround is to configure the PS/2 Link Station Role as Secondary. [CSCdi60999]

  • When running CIP SNA over DLSw, the LLC2 control blocks may not get freed even when the LLC2 session is lost and the DLSw circuit is gone. The workaround is to reload the router. [CSCdi62627]

  • When source-bridge sdllc-local-ack is enabled, the router stays in disconnect after the SDLC PUs are inactivated in VTAM. The workaround is to remove the sdllc-local-ack. [CSCdi64640]

  • LSAP filters and NetBIOS host filters that are applied to the DLSw remote-peer statements do not work on DLSw border routers. [CSCdi66251]

  • If the Channel Interface Processor (CIP) card on a Cisco 7000 router is in a hung state, the Cisco IOS software may enter a loop trying to reset it. The following messages will be repeated: 
%CBUS-3-CIPRSET: Interface Channelslot/port, Error (8010) disable - cip_reset() 
%CBUS-3-INITERR: Interface decimal, Error (8004), idb hex decimal cmd_select - 
cbus_init() %CBUS-3-INITERR: Interface decimal, Error (8004), idb hex decimal cmd_select 
-cbus_init() %CBUS-3-CTRLRCMDFAIL1: Controller decimal, cmd (128 hex) failed 
(0x8010)count (16) %CBUS-3-FCICMDFAIL1: Controller decimal, cmd (32 0x00000001) failed 
(0x8010) count (1)

Looping may be severe enough to require a router reboot.

The looping messages may overrun the logging buffer and thus obviate the reason for the initial attempt to reset the CIP. [CSCdi66420]

  • The router may crash with the message "Illegal access to low address" if it is running low on memory and RSRB is configured. [CSCdi67879]

  • The router crashes when NSP is configured and is trying to connect back to the owning host. [CSCdi69231]

  • A router interface operating in an SDLC secondary role will not respond to TEST P. [CSCdi70562]

  • When using DLSw FST, end-user sessions may not switch over to an alternate LAN or peer path after a connectivity failure. [CSCdi70709]


Interfaces and Bridging

  • When you perform buffer changes on a serial interface with SMDS encapsulation, the changes are not recognized after a reload. [CSCdi62516]

  • The source-bridge ring-number command allows you to configure a ring-number mismatch. The workaround is to make sure that all bridge devices on a ring use the same ring number. [CSCdi63700]

  • In Cisco 7500 series routers, the following error message might be displayed while booting the system image from TFTP or Flash memory, or when changing the serial encapsulation (for example, from HDLC to SMDS): 
%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF50, slot x, cmd code 0

The show diagnostics x command reports that the board is disabled, the show version command does not show the card in the specified slot, the write terminal command does not show the configuration for the card in the slot. A possible workaround is to issue a microcode reload command or load a new system image that has the fix for this bug. [CSCdi66450]

  • Using 802.10 encapsulation on an FDDI trunk port, a Cisco 4700 router cannot form OSPF neighbor adjacencies with other routers on the other side of a Catalyst switch connected via 10BaseT. The workaround is to configure bridge-group under the FDDI subinterface.

  • Small and middle buffers leak when transparent bridging on ATM is enabled. [CSCdi69237]

  • When using the custom-queuing feature in conjunction with payload compression on HDLC or Frame Relay encapsulations, traffic regarded as "low-priority" by custom-queuing might be passed uncompressed. This results in lower than expected compression ratios. [CSCdi71367]


IP Routing Protocols

  • If the router is reloaded when the OSPF dead-interval setting is the same as the original default (40 for broadcast networks and 120 for nonbroadcast networks) and the hello-interval is not the default, the router does not retain the OSPF dead-interval setting, even though the configuration in NVRAM shows the dead-interval set properly. The router sets a default value to the dead-interval instead of what is set in the NVRAM config.

The workaround is to not set the dead-interval the same as the original default.

When the fixed image is first loaded, the problem still happens. To resolve the problem, reconfigure the dead-interval again and perform a write memory operation. [CSCdi62640]

  • The match keyword is not working with the redistribute command. The workaround is to use the route-map keyword. [CSCdi64310]

  • IPX Enhanced IGRP updates do not propagate if the MTU size is less than the IPX Enhanced IGRP packet size. [CSCdi65486]

  • Processing of input offset lists in Enhanced IGRP was disabled erroneously, so offset list processing is not available. There is no workaround. [CSCdi65889]

  • If you have neighbor statements pointing to a subnet broadcast address, it may fail to send updates to that broadcast address. [CSCdi67411]


Novell IPX, XNS, and Apollo Domain

  • After upgrading Cisco IOS software, a show processor memory command might indicate that the IPX SAP table memory usage has grown by almost 300%. [CSCdi65740]

  • Using IPX-Enhanced IGRP can cause a memory leak when a link with an Enhanced IGRP neighbor is flapping. The SAP updates are queued and backed up, thus taking increasing amounts of memory. [CSCdi66169]

  • If SPX spoofing fails to send a keepalive, a traceback message will be display on the system console. [CSCdi69062]


TCP/IP Host-Mode Services

  • RSH commands executed to the router without a controlling shell return only the first 1608 bytes of data. [CSCdi69424]

  • The fix of defect CSCdi66910 introduced this defect, and CSCdi71158: the system may reload when doing DNS name validation. There is no workaround. [CSCdi70707]


Wide-Area Networking

  • Dialing into an asynchronous line and starting a SLIP/PPP session may fail even though the same IP address was previously allocated successfully for the particular user. [CSCdi63143]

  • Setting a group range on a pre-11.2 group-async interface while calls are active causes all asynchronous modem calls to be disconnected. [CSCdi66297]

  • The command no interface atm#/0.# does not remove PVCs configured on the subinterface. The workaround is to use the no atm pvc command to remove the PVCs, and then remove the subinterface using the no interface atm#/0.# command. [CSCdi66774]

  • A Cisco 2511 may reload at _bridge_enq when no bridging is configured. [CSCdi67157]

  • The error message "%UTIL-3-TREE: Data structure error--received" might occur when using NHRP in Release 11.1(4). [CSCdi67350]

  • The VIP/VIP2 IPC overlaps some TX accumulators and makes those accumulators spurious. Those accumulators are not used until the number of interfaces is more than 20. [CSCdi67842]

  • When parallel, nonmultilink connections exist in a dialer group, the loss of one connection will remove the route to the peer address even though one or more connections exist to forward packets to the destination. This defect occurred as a result of fixing CSCdi59425. [CSCdi67844]

  • Using ATM PVC and bridging, the number of ARP requests sent out depends on the number of subinterfaces created under the ATM interface. [CSCdi67980]

  • Memory corruption (and subsequent reload of the router) may occur if AAA authorization is enabled and there is no DNS server configured on the router. Enabling no ip domain-lookup will decrease the chances of memory corruption. If you are running an Enterprise image, you may enable to command kerberos local-realm kerberos-realm as a workaround for this problem. [CSCdi68041]

  • When dialing into a Cisco AS5200 from an I-Courier modem over synchronous ISDN and then starting a PPP session, the router might crash. This occurs only when login is performed on a non-asynchronous interface and when extended TACACS is enabled. A workaround for non-asynchronous interfaces is to use AAA/TACACS+. [CSCdi68257]

  • If multiple, parallel connections to the same peer are made and one connection drops, the remaining connections may be unusable as packets will not be forwarded over them. [CSCdi68456]

  • On certain platforms, entering an ip address configuration command while the interface is connected to a SLIP or PPP peer may cause a software-forced reload. [CSCdi69809]

  • A neighbor route is not installed for PPP connections over an asynchronous or a vty-asynchronous connection. This defect was introduced by the fix for CSCdi50490, and only affects Releases 11.1(6.0.2) through 11.1(6) and 11.2(0.25) through 11.2(1). [CSCdi69919]

  • Some IPX clients, including Windows 95, change their IPX node number on every connection. This means in a DDR environment it is impossible to create a static dialer map for a dialin Windows 95 IPX client. The workaround is to create a dynamic dialer map for IPX when a client authenticates and provides their IPX node number. [CSCdi70873]

  • ISDN BRI routers may have problems bringing up multiple B-channels to the same destination. The router and PBX may also get into a Layer 3 state mismatch and continuously exchange Layer 3 messages. [CSCdi71333]


Release 11.1(5) Caveats/Release 11.1(6) Modifications

This section describes possibly unexpected behavior by Release 11.1(5). Unless otherwise noted, these caveats apply to all 11.1 releases up to and including 11.1(5). For additional caveats applicable to Release 11.1(5), see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 11.1(6).

Additionally, one caveat was resolved in a special release prior to Release 11.1(6), as well as in Release 11.1(6). This special release was named 11.1(5a) and is described in the following paragraphs.


Cisco IOS Release 11.1(5a)

The Cisco IOS Release 11.1(5) rsp- images were rebuilt to include a single defect fix, and were renumbered to 11.1(5a). The defect is bug CSCdi66673 and is described as follows:

When Ethernet runt packets are received by Cisco 7500 series router processors (RSP1, RSP2, or RSP7000), a Reserved Exception crash or a QAERROR error will occur. When either of these problems happens, a switching complex restart is forced. The Reserved Exception crash has the following output: 

Queued messages:
Aug 14 10:44:16: %RSP-3-ERROR: memd write exception, addr 08000000
Aug 14 10:44:16: %RSP-3-ERROR:   RSP alignment error on write to QA, addr 080000
00
*** System received a reserved exception ***
signal= 0x9, code= 0x0, context= 0x60c72fd0
PC = 0x60107514, Cause = 0x2020, Status Reg = 0x34008702
DCL Masked Interrupt Register = 0x000000ff
DCL Interrupt Value Register = 0x00000000
MEMD Int 6 Status Register = 0x00000000

The QAERROR error has the following output: 

Jun 17 10:50:23.329: %RSP-2-QAERROR: reused or zero link error, write at addr 03
08 (QA)
  log 260308C0, data A816FFFF 00000000


Access Server

  • If an unprovisioned or incorrectly provisioned T1 is attached to a Cisco AS5200, the router becomes unresponsive. [CSCdi64205]


AppleTalk

  • A router configured with AppleTalk Enhanced IGRP takes too long to age-out routes even when the link is down, causing a long convergence time for features such as backup interface. [CSCdi62796]

  • In Release 11.1(4), the Cisco IOS software displays the appletalk domain global configuration command after all the interfaces. This causes the appletalk domain-group interface configuration command to be invalid. If the router reloads, the network remapping does not work automatically and causes major network conflicts in AppleTalk. [CSCdi63707]

  • IPTalk does not function correctly. IPTalk-speaking CAP servers cannot communicate and are not recognized on the network. [CSCdi64165]


Basic System Services

  • On RSP-bases systems, the following message may appear: 
%DBUS-3-DBUSINTERR: Slot 0, Internal Error

The message may also be accompanied by the following: 
%CBUS-3-CMDTIMEOUT: Cmd time out, CCB 0xXXXXXXXX slot n, cmd code n


%DBUS-3-WCSLDERR: Slot n, error loading WCS, status 0xXX cmd/data 0xXX pos n

If the WCSLDERR error occurs, the board is effectively disabled and is not displayed when you issue a write terminal command. Issue a microcode reload command to take the card out of the disabled state. [CSCdi49854]

  • Cisco 7500 series routers cannot fast switch packets whose size is greater than 8192. These packets are switched at process level which is a slower performance path. [CSCdi60295]

  • HSA and VIPs now can coexist in Cisco 7500 series routers. [CSCdi60891]

  • RADIUS passwords are limited to 16 bytes and are truncated if longer. [CSCdi62518]

  • When installing HSA, both RSPs must have an equal amount of DRAM, and the slave and master RSPs must both have a minimum of 24 MB of DRAM. [CSCdi62683]

  • Control characters are not interpreted properly in chat scripts. [CSCdi62960]

  • In some cases the snmp-server party and snmp-server context configuration commands may cause a system reload. Neither of these commands verifies that the configured OID is not already in use, so it permits multiple records to be configured with the same OID, violating the rule that each record must have a unique OID. A common occurrence is to attempt to configure an initialPartyIdentity or initialContextIdentity that conflicts with the OIDs that are automatically preconfigured per RFC 1447. A workaround is to not configure OIDs that conflict with the initial party and context OIDs specified in RFC 1447. [CSCdi63694]

  • Cisco routers with Motorola 68000 microprocessors (such as the Cisco 7000 and Cisco 2500 series) cannot fast switch packets larger than 8192 bytes. These packets are switched at process level, a slower performance path. [CSCdi63695]

  • Using RADIUS for PPP authentication causes a slow memory leak. A periodic reload of the router will prevent this from becoming a problem. [CSCdi63788]

  • The remote file system (RFS) (a Cisco IOS facility that allows interface processors the ability to access the RSP Flash file system) can fail on RSPs with RAM configurations less than or equal to 16 MB. Since the Channel Interface Processor relies upon the RFS to download run-time code dynamically, it is unusable. Either the CIP must be removed from the configuration, or the RSP RAM must be increased. [CSCdi64706]

  • When Ethernet runt packets are received by Cisco 7500 series router processors (RSP1, RSP2, or RSP7000), a Reserved Exception crash or a QAERROR error will occur. When either of these problems happens, a switching complex restart is forced. The Reserved Exception crash has the following output: 
Queued messages:
Aug 14 10:44:16: %RSP-3-ERROR: memd write exception, addr 08000000
Aug 14 10:44:16: %RSP-3-ERROR:   RSP alignment error on write to QA, addr 080000
00
*** System received a reserved exception ***
signal= 0x9, code= 0x0, context= 0x60c72fd0
PC = 0x60107514, Cause = 0x2020, Status Reg = 0x34008702
DCL Masked Interrupt Register = 0x000000ff
DCL Interrupt Value Register = 0x00000000
MEMD Int 6 Status Register = 0x00000000

The QAERROR error has the following output: 
Jun 17 10:50:23.329: %RSP-2-QAERROR: reused or zero link error, write at addr 03
08 (QA)
  log 260308C0, data A816FFFF 00000000

[CSCdi66673]

  • -fin- images do not support RIP, but should. [CSCdi67269]


IBM Connectivity

  • A Cisco 4500 or Cisco 4700 series router running RSRB might restart with the error message "%ALIGN-1-FATAL: Illegal access to a low address." [CSCdi35905]

  • An SDLLC secondary router fails to respond to SNRM input frames. This problem was introduced by CSCdi51341. [CSCdi56398]

  • Valid multicast explorers that should be handed to the protocol stack are instead being diverted to the SRB module and are being flushed by the SRB explorer control mechanism.

This problem was introduced by some changes to the Token Ring interrupt handler in Release 11.0 and later.

There is no workaround for the diversion, though the flushing can be avoided by raising the explorer maxrate value to some high number. However, this may cause instability in the network. [CSCdi59090]

  • A FRAS BNN-to-SDLC link does not restart when Frame Relay is power-cycled. After the CSU is powered off, the "fras backup rsrb" kicks to put the SDLLC traffic across the RSRB peers. When the CSU is powered back on and the Frame Relay DLCI comes back up, the FRAS BNN connection to the SDLC nodes does not reactivate, although connections to Token Ring nodes do restart. [CSCdi61156]

  • If the vmac parameter is not specified in the qllc dlsw command, a Cisco 4500, Cisco 4700, or Cisco 7500 router may crash in the function QLLCTestStnReq(). [CSCdi61562]

  • QLLC may try to initiate a connection in the middle of activating a connection. [CSCdi62155]

  • Using DLSw+ local switching and QLLC, the LF field in the RIF of Test Responses sent on Token Ring are not consistent. A workaround is to configure an MTU size of 4500 on the X.25 interface. [CSCdi62416]

  • DLSW NetBIOS cannot connect to Windows NT. [CSCdi62784]

  • A race condition when one DLSw peer has come up while another is in the process of coming up results in the error message "IBM: Unknown L3 PID, fr_doencap failed." This is a warning message that does not prevent the DLSw peers from coming up. [CSCdi63658]

  • A memory leak in QLLC can result in buffer starvation on the serial interface, and may cause LAPB on the serial interface to become stuck in the RNRSENT state. [CSCdi64333]

  • Configuring the dlsw remote-peer cost command has no effect on peer selection. All peers displayed in the show dlsw capabilities command show equal costs. [CSCdi64537]

  • A router running remote source-route bridging where the input explorer queue overflows may crash with the message "%ALIGN-1-FATAL: Illegal access to low address from srb_enq." [CSCdi65489]

  • DLSw FST on the RSP was broken by CSCdi58658, which was integrated into 11.001(004.005). This problem results in a buffer leak in the RSP's Token Ring interface buffer pool. The Token Ring interface eventually hangs when it runs out of buffers. The output of a show controller cbus command shows the number of buffers the interfaces thinks are still available.

The following error messages occur: 
*Aug 7 11:48:33 mst: %SYS-2-LINKED: Bad enqueue of 60AE6FC0 in queue 60B0EB60 -Process= 
"<interrupt level>", ipl= 5 -Traceback= 60110530 6016901C 60169070 60211C8C 600F2E70 
600F2B70 600F06D4 601B78E0 60188EB0 

boxer% rsym rsp-j-mz.111-5.0.1.symbols Reading rsp-j-mz.111-5.0.1.symbols 
rsp-j-mz.111-5.0.1.symbols read in Enter hex value: 60110530 
0x60110530:p_enqueue(0x601104d0)+0x60 Enter hex value: 6016901C 
0x6016901C:process_enqueue_common(0x60168fb4)+0x68 Enter hex value: 60169070 
0x60169070:process_enqueue_pak(0x6016905c)+0x14 Enter hex value: 60211C8C 
0x60211C8C:ip_simple_enqueue(0x60211c74)+0x18 Enter hex value: 600F2E70 
0x600F2E70:dlsw_lan2fst(0x600f2c1c)+0x254 Enter hex value: 600F2B70 
0x600F2B70:dlsw_srb_input(0x600f2ab0)+0xc0 Enter hex value: 600F06D4 
0x600F06D4:fs_srb_to_vring(0x600f054c)+0x188 Enter hex value: 601B78E0 
0x601B78E0:rsp_process_rawq(0x601b673c)+0x11a4 Enter hex value: 60188EB0 
0x60188EB0:rsp_qa_intr(0x60188dec)+0xc4

Also, DLSw FST needs to be allowed over a Channel Interface Processor (CIP) LAN interface. [CSCdi65603]

  • DLSw may crash when using FST or Direct peer encapsulations on an RSP system and using a CIP interface as a LAN port. The crash will occur due to an access to address 0x00. [CSCdi66239]

  • SNA sessions using QLLC over X.25 PVCs do not become active. The following tracebacks are a symptom of this problem: 
%SYS-2-LINKED: Bad enqueue of 9600E8 in queue 88380. SNA: Alert xxxxx not sent, Focal 
point buffer overflowed.

[CSCdi66340]

  • The router may reload when the second device tries to connect for reverse QLLC with DLSw+ local-switching. [CSCdi67189]


Interfaces and Bridging

  • Incoming packets to the Hot Standby Router Protocol (HSRP) MAC address are process-switched, regardless of the route cache status on the interface. [CSCdi44437]

  • Serial interfaces may occasionally show the following symptom when the interface cable is changed or the remote end dies and comes back: 
PC2PR2#sh int s 4/1 
Serial4/1 is down, line protocol is down 
     Hardware is cyBus Serial. 
     0 output buffer failures, 0 output buffers swapped out 0 carrier transitions 
     RTS up, CTS up, DTR up, DCD up, DSR up

Note that router reload is not necessary; two workarounds are known. If the first workaround is not successful at bringing up the interface, try the second.

  • This workaround was discovered while attempting to observe this problem. It can permit the problem interface to be bought on line without resetting every interface in the cBus complex.

Enter the cBus test mode and select the interface having the problem. Read a portion of the interface processor memory.

This example is for an FSIP interface at 2/0: 
Router#test cb
RSP diagnostic console program
Enter slot number: [0x0]: 2
Enter interface number: [0x0]: 
Command queue for slot 2 is 0x12.  CCB is 0xFF50
RSP (? for help) [?]: ri
Enter FSIP Mem starting address [0x0]: 
Enter FSIP Mem ending address [0x20000]: 0x20

FSIP Mem 00000:  0001 FFFC
FSIP Mem 00004:  0000 01C6
FSIP Mem 00008:  0000 049A
FSIP Mem 0000C:  0000 049A
FSIP Mem 00010:  0000 049A
FSIP Mem 00014:  0000 049A
FSIP Mem 00018:  0000 049A
FSIP Mem 0001C:  0000 049A
FSIP Mem 00020:  0000 049A

This example is for the HIP at 1/0: 
Router#test cb
RSP diagnostic console program
Enter slot number: [0x2]: 1
Enter interface number: [0x0]: 
Command queue for slot 1 is 0x11.  CCB is 0xFF40
RSP (? for help) [?]: ri
Enter IP Mema starting address [0x0]: 
Enter IP Mema ending address [0x10000]: 0x20
IP Mema 0000:  7FA2 7FA0 7FA4 0044  0005 0000 0000 0000
IP Mema 0008:  0000 0098 00D0 0080  0032 0000 0000 0000
IP Mema 0010:  FFFF 0001 0000 0003  0000 7EA0 7E98 7E90
IP Mema 0018:  0000 0000 0000 0000  0000 0003 0000 00DD

    • This workaround will reset all the interfaces in the cBus complex. 
Router(config)#mic rel

[CSCdi57573]

  • A router running Frame Relay crashes at bridge_enq even when bridging is not configured. [CSCdi63140]

  • When passing compressed bridged traffic on HDLC WAN links, many errors of the type "Decompression size error" occur. The router sometimes crashes when processing these packets. This fix causes compressed bridged traffic not to be compressed. The fix is considered temporary until process-level bridging can be made compatible with payload compression. [CSCdi63245]

  • In DCE mode, FSIP looks for DCD and DSR up before declaring the Line UP. FSIP should only look for DCD. [CSCdi64735]

  • The MIP interface will not come up automatically after a reload. A workaround is to issue a clear controller t1/e1 command to manually reset the T1/E1 controller. [CSCdi67143]


IP Routing Protocols

  • A problem introduced in Releases 10.3(11.1), 11.0(7.3), 11.1(2.3), and 11.2(0.5) causes OSPF to crash when an OSPF external LSA with a nonzero forwarding address exists and the router has a non-OSPF route for the forwarding address. If the non-OSPF route is removed, OSPF crashes when it reprocesses the external LSA. There is no workaround for the problem. However, in general, no more than one routing protocol should be run over the same topology. If you follow this guideline, no non-OSPF route for forwarding address will exist and the router will not crash. [CSCdi61864]

  • Shutdown interfaces with IP addresses or static routes that point to down next-hops or other interfaces may cause the IP cache to be partially invalidated more frequently than necessary. This is particularly evident when there are multiple paths. The workaround is to remove IP addresses from down interfaces or remove static routes through down interfaces, or both. [CSCdi62877]

  • A problem introduced in Releases 11.0(9.3), 11.1(4.2), and 11.2(0.14) might cause OSPF to fail to install an external route that has no forwarding address. This occurs if the next hop of the path to the ASBR changes and its cost increases. The workaround is to create an external LSA with forwarding address set. [CSCdi64208]

  • A directly connected route may disappear from the IPX Enhanced IGRP topology table if the interface that is configured for IPX Enhanced IGRP goes down and comes back up in brief period of time, on the order of 2 seconds. The workaround is to issue the shut and no shut commands on the interface. [CSCdi65345]


Novell IPX, XNS, and Apollo Domain

  • In rare circumstances, NLSP may not report information learned from RIP and SAP. There is no workaround to this problem. [CSCdi45425]

  • CSCdi63412 introduced an alignment error, in particular for IPX frames routed from Token Ring networks with multiring enabled. Alignment errors occur in process-switched and certain fast-switched paths. [CSCdi63741]

  • CSCdi58363 introduced a problem where NLSP-learned services and SAP-learned services overwrite one another, causing unstable service table information. This is particularly a problem in networks with redundant paths. There is no workaround. [CSCdi63771]

  • The SPX spoofing code does not automatically age out old entries from the SPX spoofing table. Over time, this table can grow very large. Some customer sites have reported that when the table is very large, the routers cease to send SPX keepalive acknowledgment spoof packets. At that time, reloading the router is the only way for SPX spoofing to function again. The workaround is to issue the command clear ipx spx spoof on a regular basis to clear the SPX spoofing table. [CSCdi64010]


Protocol Translation

  • On PAD-TCP and TCP-PAD translations, changes in PAD parameter settings can incorrectly cause Telnet option messages to be sent on the corresponding TCP connection even if the stream option is set. [CSCdi62987]


VINES

  • VINES time server service may get out of synch when the system runs more than 49 days. This is because only the low 32 bits of the internal clock counter are used when VINES computes network time. When network time is out of synch, it is recommended that you either disable VINES time server service for devices running Cisco IOS Releases 10.2 or 10.3, or upgrade to Cisco IOS Release 11.0(11) or 11.1(6). [CSCdi58105]

  • VINES clients running an Oracle application program cannot make connection to a server due to packet reordering when vines route cache is enabled. A suggested workaround is to use process switching for those applications that cannot process out-of-sequence packets. [CSCdi59059]


Wide-Area Networking

  • Bridging IP between two routers through an SMDS network may not work correctly if the IP session originates or terminates in the router, such as in the case of remote source-route bridging or data-link switching. If IP routing is turned on, this is not a problem. [CSCdi61364]

  • An RSP-based system running Cisco IOS software that contains the defect documented as CSCdi55969 may start dropping all packets incoming to the input queue of a AIP interface.

The error message "%SYS-2-INPUTQ: INPUTQ set, but no idb, ..." will appear.

A temporary workaround is configuring the interface level command: hold-queue 750 in until you are able to reload the router. Remove this configuration after upgrading the software. [CSCdi61629]

  • RFC 1577 and LANE applications get blocked due to a difference between VCD known by different parts of the software. This problem has been reported with both applications (LANE, RFC 1577) in Releases 11.0(8) and 11.1(4). [CSCdi61979]

  • Error messages similar to the following may appear in devices that contain ATM interfaces: 
%SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level

%SYS-2-MALLOCFAIL: Memory allocation of 52 bytes failed from 0x60298EF4, pool Processor, 
alignment 0

These messages most often show up in Cisco 4000 series routers when the routers are being reloaded. The workaround is to put the ATM interfaces in the shutdown state before reloading. [CSCdi62194]

  • An error in the AIP microcode introduced in aip177-2/rsp_aip205-2 causes a race condition in the microcode and commands from the RP/RSP are rejected. When this happens, the following console messages are logged: 
%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1011, VPI=0, VCI=262) on Interface 
ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC) 
%AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Teardown VC command (error code 
0x8000)

[CSCdi62445]

  • The printer printer-name line number global command uses the newline-convert option as the default. There is no way to get the router to work without either the newline-convert or formfeed option. [CSCdi63342]

  • If a Cisco 7000 router is forwarding a NetBIOS or NetBEUI packet from the ATM (LANE) cloud, the packet might be dropped. This occurs only with protocols that cannot be routed. [CSCdi63540]

  • Part of the fix for CSCdi63245 broke bridging on HDLC links. This fix returns the broken code to its original state. [CSCdi64710]

  • On the Cisco AS5200, the performance does not scale well when additional asynchronous interfaces are deployed. The symptoms include the Ethernet interface showing input drops and frequent throttles. [CSCdi65706]

  • PAP authentication fails when using TACACS+ as an authentication method for PPP. [CSCdi66077]

  • LANE does not set up the data direct again after it has been established the first time. This problem was introduced as a result of the fix for CSCdi61979.

Any release containing this bug should not be used in sites using LANE. The following releases are affected: 11.0(10.3), 11.1(5.3), 11.1(5.4), 11.2(0.23), and 11.2(0.24).

Note that for Release 11.0, only the Cisco 7000 images (gs7-) will be affected, as the Cisco 4500 and RSP-based systems do not run LANE using Release 11.0. [CSCdi68089]


Release 11.1(4) Caveats/Release 11.1(5) Modifications

This section describes possibly unexpected behavior by Release 11.1(4). Unless otherwise noted, these caveats apply to all 11.1 releases up to and including 11.1(4). For additional caveats applicable to Release 11.1(4), see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 11.1(5).


AppleTalk

  • MacIP server will not give an IP address to a MacIP client if the next address to give out is currently being use by a genuine IP device. The problem is that the MacIP server does not skip over that IP address and assign the next available address. This causes the process to get stuck. [CSCdi61526]

  • According to Inside AppleTalk, 2nd Edition, page 8-18, the router should convert NBP BrRq to NBP FwdReq packets. Instead, the router sends NBP LkUp packets for nonextended networks.

Note: For routers that are directly connected to a Phase 1 (non-Phase 2) router in compatibility mode, the appletalk proxy-nbp network zone command must be used. This will allow the router to convert the NBP FwdReq to NBP LkUp to the Phase 1 router. [CSCdi61668]


Basic System Services

  • Under some conditions, the SEEQ will incorrectly pass up runt Ethernet packets. Previously, these were not checked for, resulting in incorrectly received Ethernet runt packets. [CSCdi55978]

  • The error message "RSP-3-RESTART: interface Serialx/y, output stuck" might affect output interfaces on an RSP-based platform. This is seen when bursty traffic is optimum-switched to an output interface with either fair queue or transmit-buffers backing-store being enabled. A workaround is to disable optimum switching. [CSCdi56782]

  • In rare instances, a system might reload during online insertion or removal of slave RSP. [CSCdi57076]

  • User should turn backing store ON for slow interface processors. Routers without slow interface processors suffer performance degradation during peak activity. [CSCdi57740]

  • An RSP router (Cisco 7500 series or Cisco 7000 with RSP7000) can crash with a "reserved exception" error due to a software error, or else due to an error in the microcode for an interface processor.

More than one problem can generate a similar error message and stack trace, which can make this problem hard to trace. See also CSCdi58999, CSCdi60952, and CSCdi60921. [CSCdi58658]

  • AutoInstall does not work in RSP. This is reported only in serial media but the problem exists in LAN media as well. There is no workaround. [CSCdi59063]

  • A Cisco 7507 router might reload and indicate SegV exception after receiving a serial interface RSRB explorer. [CSCdi59082]

  • HSA (dual RSP in the Cisco 7507 or Cisco 7513) can now coexist with CIP interface processors. [CSCdi60833]

  • Use of the show rmon filter command in Release 11.1 can cause a router core dump. A workaround is to only use SNMP gets to retrieve the information in the RMON filterTable and channelTable. [CSCdi61957]


DECnet

  • A router running DECnet might present "ALIGN-3-SPURIOUS" error messages. This condition occurs only if the adjacency between neighbors expires. [CSCdi60716]


IBM Connectivity

  • In extremely rare circumstances the router may crash while removing RSRB peers. This might occur only when running an AGS+ and the CSC1r/CSC2r Token Ring boards. [CSCdi39270]

  • When automatic spanning tree (AST) is configured on multiple routers in a high-redundancy topology, a bridge protocol data unit (BPDU) broadcast storm might be triggered. [CSCdi41851]

  • A Cisco 4700 router running DLSw+ and SDLC might crash in the SDLC process. [CSCdi48414]

  • ACTPU RSP never received by the host in a parallel SDLLC network [CSCdi55142]

  • The APPN DLUR router may unbind LU sessions with the DLUS and the downstream node if fixed pacing was enabled on the session bind request from the DLUS. If this is the case, when the user attempts to logon from the downstream device, the USS message 7 with a sensec code of 0835 0009 may be displayed. [CSCdi57729]

  • On rare occasions, CSNA Virtual Port X/2 may hang in down/down state following a shut / no shut command sequence or microcode reload of the channel interface. The workaround is to reload the router. [CSCdi58517]

  • A router might crash and display the message "System restarted by bus error at PC 0xD0D0D0D, address 0x0." The crash happens when using promiscuous TCP peers. The crash occurs when peer structures are deleted (for example, due to transmission line problems or peer routers reloads) while still being used by TCP.

The work around is to define static peers.

Note: CSCdi61278 is a follow-on fix to this problem. [CSCdi58842]

  • LNM Resync does not work with Release 10.3(10.2) on a Cisco 7000 if the router is configured for IBM automatic spanning tree support. [CSCdi59890]

  • The QLLC features, npsi-poll, and proxy XID do not operate correctly for DLSw+. [CSCdi60002]

  • DLSw LLC Ethernet 80d5 bad frames are observed after an LLC retransmission. [CSCdi60102]

  • The command stun schema cnt offset 0 length 1 format hexidecimal must be entered as stun schema cnt offset 0 length 1 format hexadecimal but is saved as stun schema cnt offset 0 length 1 format hexidecimal. When the router is reloaded the following error is printed: 
d7c#conf mem
stun schema cnt offset 0 length 1 format hexidecimal 
                                            ^ 
% Invalid input detected at '^' marker.

[CSCdi60992]

  • The router crashes and displays the message "System restarted by bus error at PC 0xD0D0D0D, address 0x0." The crash happens when using promiscuous TCP peers. The crash occurs when peer structures are deleted (for example, due to transmission line problems or peer routers reloads) while still being used by TCP. The work around is to define static peers. If there is a stack trace, action_b() will be one of the entries.

This bug fix is a follow-on fix to CSCdi58842. [CSCdi61278]

  • This software fix enables DSPU/FDDI support for end-stations attached directly to FDDI media [CSCdi61351]

  • Connections cannot be established when using IBM process-switched features (for example, RSRB/TCP or DLSw+/TCP) because of dropped packets.

The symptom is that "dropped Routed protocol" messages are output when debug source-bridge error is enabled. [CSCdi62738]


Interfaces and Bridging

  • Turning on ipx route-cache sse with microcode version SSP10-12 or SSP10-13 produces a mismatch between the frame length on odd-byte 802.3 IPX packets and the 802.3 length. Novell devices might not recognize these packets, resulting in communication timeouts.

The following three workarounds can be used:

  • Turn off padding on process-switched packets via the command:

no ipx pad-process-switched-packets

  • Configure the router for autonomous switching instead of SSE switching via the commands:

no ipx route-cache sse

ipx route-cache cbus

  • Turn off SSE switching:

no ipx route-cache sse

[CSCdi42802]

  • If a Cisco 7000 series router or Route Switch Processor (RSP) has a serial interface on an FSIP that receives several "giant" packets, you might get the error "%DBUS-3-CXBUSERR: Slot x, CBus Error." Issuing the show interface command for the affected slot will show giants occurring. To work around this problem, load an image that contains new microcode: fsip 1-15 or later microcode for the Cisco 7000 series router, and rsp_fsip202-5 or later microcode for the RSP. [CSCdi58194]

  • Cisco 7500 (RSP systems) performance is degraded with ISL, fast switching, and access lists applied. The work around is to disable fast-switching on the main interface. [CSCdi59825]

  • This defect was introduced in 11.1 (4.0.2) by CSCdi44333. It prevents a channel group on the MIP being created on a Cisco 700 series router in which approximately 32 ports are loaded (plugholes). The router becomes nonresponsive after a channel group is created. [CSCdi64153]


IP Routing Protocols

  • If there is a very large set of IP cache entries created because of the same IP route, for example, the default route, a CPUHOG message occurs for the routing protocol when the original route changes and the router clears the related cache entries. Although the cause of the CPUHOG is the IP cache invalidation, the CPUHOG indicates the routing protocol as the guilty one. [CSCdi55725]

  • During show ip ospf, if OSPF is unconfigured (for example through a different session), the router will crash. [CSCdi58092]

  • A router running Enhanced IGRP with Appletalk, IPX, or IP that has input route filters configured may improperly filter routes that it should install. Additionally, if a router running IPX-Enhanced IGRP receives an update containing an external route that was originated by the router itself, the rest of the update will be ignored. There is no workaround to this problem. [CSCdi61491]

  • Input queues may become full running IP multicasts. The only way to clear them is to reload the router. [CSCdi61826]

  • OSPF corrupts memory and might cause the system to reload. [CSCdi61956]

  • A problem introduced in Releases 10.3(12.4), 11.0(9.3), 11.1(4.2) and 11.2(0.14) causes OSPF to crash if there are parallel intra-area paths. [CSCdi62870]


ISO CLNS

  • A router running IS-IS will not clean up its adjacency database properly when switched from being a level-1/level-2 router to being level-1 only. A workaround is to manually clear the adjacency database using the clear clns neighbors command on the reconfigured router and on all of its neighboring routers. [CSCdi58953]


Novell IPX, XNS, and Apollo Domain

  • IPX SPX spoofing might fail when using RPRINTER across a spoofing interface. [CSCdi42806]

  • Configuring no ipx router eigrp autonomous-system-number may cause the router to reload if there are many SAPs in the router and the SAP table is changing. [CSCdi60174]

  • A Cisco 7500 fast-switching IPX traffic might demonstrate excessive CPU utilization in the 90-100% range though forwarding a moderate amount of traffic (less than 5000 pps). Alignment errors in the fast switching path occurring on some specific IPX frames cause this incorrect behavior. [CSCdi61334]

  • Defining a static IPX route using the peer address of an IPXWAN neighbor may fail with a message about multicast addresses. The workaround is to avoid using 8-digit IPX internal network numbers which have an odd numbered first byte. A 7-digit or fewer length IPX internal address also will not give this error message. [CSCdi61993]

  • Under certain conditions, an IPX packet may be received that has an incorrect IPX length in the IPX header, the CRC is good, and the router processes this packet. However, the system incorrectly pads the packet to the length specified in the IPX header instead of throwing the malformed packet away. [CSCdi63412]

  • CSCdi63412 introduced an alignment error for IPX frames routed from Token Rings with multiring enabled. This alignment error is in both process-switched and certain fast-switched paths. [CSCdi63741]

  • CSCdi58363 introduced a problem where NLSP learned service and SAP learned services overwrite one another, causing unstable Service Table Information. This is particularly a problem in networks with redundant paths. There is no workaround. [CSCdi63771]


VINES

  • VINES clients running Oracle application program can not make connection to a server due to packet reordering when vines route cache is enabled. A suggested workaround is to use process switching for those applications that cannot handle out-of-sequence packets. [CSCdi59059]


Wide-Area Networking

  • When authentication is not configured and different phone numbers are dialed to add bandwidth for dialer load balancing or multilink PPP, additional links may not be added to the correct group or bundle. This can result in lower than expected performance for dialer load balancing. The result for multilink PPP is no data transfer at all. The workaround is to configure authentication and put the name of the remote system in the dialer map name field. [CSCdi46872]

  • Multilink bundles do not disconnect during a low or idle period if more than one link is in the bundle. The load must drop below the threshold for links to disconnect. When the bundle contains only one link, the link may disconnect when the load is low or the link is idle. However, if you configure dialer load-threshold 1, links will never disconnect because of idle or low load.

To cause links to disconnect earlier during a low-load or idle period, increase the load threshold. [CSCdi48263]

  • IP route configuration commands accept Group-Async interfaces as an interface parameter. This causes crashes in the asynchronous dialer. [CSCdi58223]

  • When configuring on a LANE interface a bridge group, the system will not be able to discover Enhanced IGRP neighbors on these emulated LANs. To work around, remove the bridge group. This will allow the router to find neighbors. [CSCdi60268]

  • Serial lines with SMDS encapsulation may take SegV catastrophic failures when enabled after reboot. There is no workaround. [CSCdi60761]

  • Asynchronous lines on a Cisco AS5200 may become hung and cannot be cleared using the clear line command. Only a reload wan restores the lines to service. [CSCdi62565]

  • RFC 1483 transit bridging is broken. [CSCdi62961]

  • The amount of free system memory may decrease when using the command dialer hold-queue over an ISDN interface. [CSCdi63716]


Release 11.1(3) Caveats/Release 11.1(4) Modifications

This section describes possibly unexpected behavior by Release 11.1(3). Unless otherwise noted, these caveats apply to all 11.1 releases up to and including 11.1(3). For additional caveats applicable to Release 11.1(3), see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.1(4).


Access Server

  • Asynchronous lines may become stuck in "Carrier Dropped" state when running TACACS+ against a slow TACACS+ server. Only a reload can make the lines usable again. [CSCdi54618]


AppleTalk

  • SMRP packets coming in to FDDI interface are dropped. To work around this problem, disable SMRP fast switching on FDDI interface using no smrp mroute-cache. [CSCdi57119]


Basic System Services

  • Reloading the microcode from ROM on an Interface processor board in a Cisco 7500 series router can cause the system to enter a rebooting loop that requires a system reload for recovery. The ROM-based microcode on the interface processors is only compatible with Cisco 7000 series routers. [CSCdi44138]

  • A Cisco 7500 series router can crash if Frame Relay interfaces are active at the same time as MIP channel groups. [CSCdi49868]

  • On late model 11.0 and 11.1 RSP system images, Optimum Switching will be disabled upon router reboot. [CSCdi54567]

  • A memory leak can occur in some circumstances while running Release 10.3 on a Cisco 7000 series router. The symptoms include small buffers that are created but are not trimmed. This is linked to RSRB and explorers being received with a wrong SNAP type value. [CSCdi54739]

  • When using Kerberos authentication for dial-in, the router will crash any time the second dial-in connection is initiated if the userid contains a slash. It should be noted that it appears that Microsoft prepends the domain information to the userid and separates the domain and userid with two slashes. [CSCdi55541]

  • Configuring custom/priority queueing on an MBRI interface causes performance degradation. [CSCdi56473]


DECnet

  • When DECnet conversion is enabled, discard routes are inserted into the Connectionless Network Service (CLNS) routing table. [CSCdi40503]


EXEC and Configuration Parser

  • The terminal download privileged EXEC command is omitted from the configuration after it is configured. [CSCdi52164]

  • The write memory and copy running-config startup-config commands now work at privilege level 15. The remaining write and copy running-config commands still operate at the current privilege level for security considerations. [CSCdi55809]


IBM Connectivity

  • When a Synchronous Data Link Control (SDLC) device is reloaded, the connection is not automatically reestablished. To reestablish the connection, issue the configuration commands shut and no shut. [CSCdi42369]

  • A Cisco 4700 router may report intermittent "SYS-2-LINKED" error messages, even though there is no memory shortage. [CSCdi52327]

  • Automatic Spanning Tree (AST) in affected in some mixed vendor bridge environments. A hidden option has been added to the source-bridge spanning command: message-age-increment. This option assists message age count manipulation. This hidden command may be needed in environments where the existing max_age is insufficient for network diameter and max_age is not configurable by vendor bridges. [CSCdi53651]

  • Some NetBIOS applications that require a UI frame in response to Add Name Query will not be able to connect using a DLSw peer on demand if the NetBIOS circuit is the initial circuit that triggers the peer-on-demand to connect.

The software fix for this problem passes UI frames through the border peer relay network. [CSCdi54796]

  • If two Token Ring interfaces are attached to the same physical Token Ring and either an all routers explorer is generated on that ring or a packed is received with a RIF that indicates that the packet should go back onto the Token Ring it originated on, a bridge loop will be created causing router CPU to rise and ring utilization to increase. The workaround is to issue a clear rif command. [CSCdi55032]

  • A bug prevents multiple qllc dlsw commands from being configured. [CSCdi55749]

  • Issuing a no source-bridge remote-peer command may cause the router to reload. [CSCdi55919]

  • If frames between Token Rings or to or from Ethernet are handled by SRB/SRTLB and one of the local ports is configured for local switching, frames between the local switch port and other LAN ports are handled by DLSw. But when a test frame from a nonlocal switch port is retried, the frame is sent incorrectly to all ports (including nonlocal switch ports) instead of being sent only to local switch ports. Note that when a frame is received from a local switch port, the correct behavior for retries is to send to all ports. [CSCdi56281]

  • Connection to DLU (DSPU or APPN) across RSRB may fail when the remote SAP address is not enabled at the destination router. The workaround is to enable the remote SAP address. [CSCdi56660]

  • A problem has been discovered with the Cisco 2520, 2521, 2522, and 2523 routers where the router can experience poor Synchronous Data Link Control (SDLC) performance on the low speed asynchronous/synchronous serial ports (interfaces serial 2 through serial 9). The low speed asynchronous/synchronous serial interface has trouble maintaining clock synchronization when configured for all of the following parameters at the same time:

    • encapsulation sdlc-primary or encapsulation sdlc-secondary

    • nrzi-encoding

    • The interface is configured as a DCE

The low speed asynchronous/synchronous serial interface may drop SDLC frames with this configuration. The symptoms of this problem are poor performance and excessive Cyclic Redundancy Check (CRC) errors on the interface (as seen via the show interface command).

The fix for this problem requires: hardware version 00000002 and a software fix for this defect, which is incorporated into Cisco IOS Release 11.0(9) and 11.1(4), and later.

All Cisco 2520, 2521, 2522, and 2523 routers manufactured before May 24, 1996 are subject to this problem.

To identify whether your router is affected, issue a show version command. The hardware revisions that are subject to the problem are "00000000" and "00000001." Hardware revision "00000002" contains the hardware fix that resolves this problem [CSCdi57040]: 
cisco 2520 (68030) processor (revision E) with 4096K/2048K bytes of memory. 
Processor board ID 02351913, with hardware revision 00000002

  • DLSw FST encapsulation does not work over a WAN Token Ring or FDDI. [CSCdi57207]

  • An APPN router may unbind an LU6.2 session after receiving an unsolicited IPM with a nonzero next-window size. [CSCdi57730]

  • Directed source-route bridge frames with control field of 010 instead of the more usual 000 are dropped. [CSCdi59100]


Interfaces and Bridging

  • The MIP T1 and E1 interfaces do not support enhanced online insertion and removal (EOIR/OIR). There is no workaround. This bug is fixed in Releases 11.0(8) and 11.1(4) and later, and requires a minimum of MIP hardware version 1.1 (73-0903-08 Rev A0).

In addition to the hardware requirement, the fix for this bug that is in Release 11.0(8) and 11.1(4) and later releases requires that you allow a minimum of 15 seconds to elapse between OIR events. Removal of one interface counts as one event, and insertion of one interface counts as one event.

If your MIP hardware isn't at least hardware version 1.1, it will not EOIR or OIR correctly!

Failure to provide this time for the router to stabilize between OIR events can result in the reset performed for one event corrupting the reset performed for another event, which could require interfaces to be reconfigured or reinitialized manually. This reset requires even more time if additional channel-groups are defined within the router. The time between OIR events should be increased to as much as 30 seconds if three or more MIP cards are fully channelized in the router. While the corruption of this reset activity might occur only occasionally if OIR events are too closely timed, it is mandatory to allow the correct interval to guarantee the benefits of EOIR/OIR. [CSCdi46137]

  • If you run a MIP EIOR-capable software release with a non-EOIR capable 1.0 hardware version MIP, you will notice that a controller reset is necessary on the MIP for it to work again after adding or removing another card. This controller reset should not be necessary. [CSCdi49807]

  • On a Cisco 7000 router with a Silicon Switch Processor, access lists used for packet filtering that contain an entry matching all IP packets followed by two or more entries can cause the router to reload. As a workaround, remove all access list entries following the entry that matches all packets. Doing so will not change the behavior of the access list. [CSCdi50886]

For example, change:

access-list 116 permit ip any any
access-list 116 permit tcp any any gt 1023
access-list 116 permit tcp any any eq smtp

to:

access-list 116 permit ip any any

[CSCdi50886]

  • While booting a Cisco 7500 router, the FIP FDDI interface might momentarily beacon the ring, causing ring instability. [CSCdi54444]

  • If a Token Ring Interface Processor (TRIP) is present in a Cisco 7000 series router, Token Rings that beacon frequently may cause router performance to be degraded. This is not a problem on Cisco 7500 series routers. [CSCdi55758]


IP Routing Protocols

  • There is a small delay between the time OSPF marks an LSA as deleted and the time the LSA is actually removed. Within this small window, if OSPF receives an old copy of the LSA which has a higher sequence number, probably from some new neighbors through database exchange, OSPF will be confused and not able to remove the LSA. Customer will observe self-originated LSA stuck in the database. The stuck LSA would be removed automatically when the router regenerate a new instance of the LSA. [CSCdi48102]

  • OSPF put incorrect information in the source field for stub route. It prevents BGP to advertize this stub route to peer as the route will not be synchronized. This fix put the advertising router in the source field for stub route and avoid the problem. [CSCdi49377]

  • The system may fail when a no router eigrp as-number command is issued and there are summary routes present. A workaround is to turn off auto-summary and deconfigure all manual summaries before deconfiguring Enhanced IGRP. [CSCdi57814]

  • Attempting to copy an empty startup configuration to the network will cause the router to reload. [CSCdi58040]

  • Disabling Optimum Switching on an RSP system has no effect. [CSCdi59203]

  • If an Enhanced IGRP candidate default route is overwritten by another protocol, the Enhanced IGRP topology table may be left in a state where the candidate default route will not return to the routing table. A workaround to this problem is to clear all Enhanced IGRP neighbors. [CSCdi59276]


ISO CLNS

  • There is no method for altering the transmission rate of IS-IS link state packets in cases where the rate would add undue load to the receiving system. There is no workaround for this problem. [CSCdi54576]

  • If IS-IS is running, and a CLNS static route is configured that points to a point-to-point interface on which IS-IS is not configured, and the static route is removed, the system may crash.

A workaround is to either disable IS-IS before removing the static route or enable IS-IS on the interface before removing the static route. [CSCdi56815]

  • A router reload may occur when CLNS traffic is fast-switched. This defect affects Releases 10.3(12) and 11.0(9). [CSCdi57629]

  • Under situations of extreme load, IS-IS and NLSP may cause packets to be dropped unnecessarily. There is no workaround to this problem. [CSCdi58433]

  • If a non-Cisco router running IS-IS on a level-1-only circuit is also sending ES-IS End System Hello (ESH) messages, it is possible for the Cisco router to not recognize the other router for IS-IS.

A workaround is to filter out the ESH packets using the clns adjacency-filter es configuration command in conjunction with an appropriate filter set (which should specify a wildcard [**], in the last byte of the address). [CSCdi58621]


Novell IPX, XNS, and Apollo Domain

  • If there are more than 42 neighbors on a single LAN interface, IS-IS and NLSP will be unable to establish neighbor adjacencies. The workaround is to limit the number of neighbors to 42 or less. [CSCdi56547]

  • IPX SAP table may not accurately reflect SAP entries learned locally if IPX Enhanced IGRP and IPX RIP/SAP is configured at the same time. Some of the SAP entries may show up on the SAP table as Enhanced IGRP derived rather than RIP/SAP derived even when the local LAN where the problem SAP sourced, is not running Enhanced IGRP. [CSCdi56588]

  • IPX SNMP request sent to the router accumulate in the input queue and are not processed. This can result in full input queues. [CSCdi57589]

  • The router may reload if an interface running IPX is turned off and on immediately thereafter. [CSCdi57683]

  • The router may reload when running IPX Enhanced IGRP due to illegal access to memory. [CSCdi57728]

  • Under obscure circumstances, some IS-IS and NLSP link-state packets (LSPs) may not be transmitted on some point-to-point interfaces. There is no workaround to this problem. [CSCdi58613]


Protocol Translation

  • When doing large file transfers on VTY-asynchronous interfaces that must cross an X.25 network with large RTT, an aggressive TCP implementation can cause return traffic on the VTY-asynchronous interface to be delayed. [CSCdi54905]


Wide-Area Networking

  • If the cell burst size is a multiple of 64, the AIP may reset with the error CBUS-3-OUTHUNG: ATM3/0: tx0 output hung (800E = queue full). This incurs a short temporary interruption of the ATM traffic. [CSCdi45984]

  • Groups of four ports on Cisco 2511 may have DSR behaving in unison on a single stimulus. Reloading the router is the only workaround. [CSCdi49127]

  • When authenticating to a peer using Password Authentication Protocol (PAP), the username password might be sent to a peer that is not authenticated. Currently there is no mechanism to disable outbound PAP. This problem may represent a security risk. [CSCdi49278]

  • Frame Relay switching across an IP tunnel does not work if one of the Frame Relay serial interfaces is configured to be frame-relay intf-type dte.

In addition, when the serial line is configured to be frame-relay intf-type dce or frame-relay intf-type nni, if a frame-relay intf-type command is entered after the desired PVCs have been configured, then the router will fail to send the correct LMI Full Status message. [CSCdi52339]

  • The number of packet descriptors is hard-coded to 256. Rx count is 192 and Tx count is 64, which can lead to problems with configurations of up to 20 Emulated LANs or many virtual circuit (VC) connections. The router shows normal CPU usage. To view the Pktdescriptor-miss, issue a sho cont atm 0 command. [CSCdi54770]

  • With ILMI-resolution of the switch portion of ATM NSAP addresses, an attempt to place a multipoint call to a destination can occur (and with PIM, always will occur) before the switch part of the address is discovered. This leaves the router in a state where it will never place calls to that static map again. To work around this problem, do not use ILMI negotiation. [CSCdi55904]

  • In a Cisco 7500 series router running LANE, with approximately 50 emulated LANs configured with bridging, some packets in the incoming queue can be blocked. After some time, the ATM interface will not accept new data. [CSCdi56897]

  • If the router receives an incoming ATM SVC call with an SDU size incompatible with the configured MTU on the ATM interface, the router may crash. This problem is present in Releases 11.0(8.3), 11.0(8.4), 11.1(3.1), and 11.1(3.2). If the router is generating the following warning messages in earlier releases, it is likely that the defect will affect them if the images from the releases listed earlier are installed: 
%ATM-4-MTUCALLMISMATCH: Incoming call has mismatched maximum transmission unit

To workaround, reconfigure the remote device with the correct SDU size. [CSCdi57676]


Release 11.1(2) Caveats/Release 11.1(3) Modifications

This section describes possibly unexpected behavior by Release 11.1(2). Unless otherwise noted, these caveats apply to all 11.1 releases up to and including 11.1(2). For additional caveats applicable to Release 11.1(2), see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in release 11.1(3).


Access Server

  • A busy access server sometimes pauses indefinitely, which indicates an invalid address error. This is usually seen in environments where a number of short-duration modem calls are answered. A workaround is to configure modem answertimeout 10. [CSCdi48100]


AppleTalk

  • Adding the command appletalk virtual-net network-number zone-name to the configuration of a Cisco 4000 router running Release 11.0(5) can cause the router to reload. [CSCdi51787]


Basic System Services

  • When trying to set the MTU on an interface in an RSP chassis (Cisco 7500 series or RSP7000) larger than 8192, the MTU change will fail and report the error message "can't carve anything." [CSCdi50133]

  • When using the RMON events feature---either through the command line interface, or through SNMP sets---to create rows in the RMON MIB eventTable, the effectiveness of the alarmTable is limited. As long as there are no eventTable entries in the MIB, the rest of the RMON MIB can be used from those feature sets where it is available. [CSCdi50963]

  • A router using TACACS+ accounting will experience a slow reduction in the amount of available system memory. A show memory command will show many small pieces of memory allocated to AAA AV Last. Eventually (usually over several weeks), the system will become unusable. A workaround is to periodically reboot the router. [CSCdi51197]

  • A router containing a CIP card does not become fully operational when Cisco IOS software is loaded. [CSCdi51441]

  • Transparent bridging with Cisco 7500 series routers may fail if a frame crosses the HDLC link. [CSCdi52360]

  • An attempt to use the RADIUS Access-Challenge feature (used for authentication with some smart-card access systems) will cause a Cisco router running RADIUS to spontaneously reload, indicating a memory allocation failure. [CSCdi55467]

  • Under some conditions SNMP queries of the CISCO-ENVMON-MIB can cause the system to reload. This occurs when an SNMP get-request is received that tries to retrieve instance 0 of an object in the ciscoEnvMonSupplyStatusTable. Since the instances of this table start with 1, the correct processing is to return a noSuchName error (or noSuchInstance if SNMPv2 is used). A workaround is to not use SNMP get-requests that specify instance 0 for objects in the CISCO-ENVMON-MIB. Instead, applications should either use SNMP get-requests starting with instance 1, or else use SNMP get-next-requests or get-bulk-requests. [CSCdi55599]


IBM Connectivity

  • A router running RFC 1490 support over Frame Relay does not properly swap the direction bit in the RIF frame. [CSCdi36042]

  • When stopping and starting APPN or deactivating links when sessions exist on those links, a bus error may occur. [CSCdi45190]

  • When the dlsw icanreach mac-exclusive and dlsw icanreach mac-address mac-addr commands are issued to specify a single MAC address to be filtered, all traffic is filtered instead. [CSCdi45773]

  • An incorrect timer reference causes explorer frames to be flushed on interfaces, even though the maximum data rate for explorers on any interface does not exceed the maximum data rate for explorers. [CSCdi47456]

  • Low-end platforms will cache invalid RIF entries when using any form of the multiring command. This can also be seen in the DLSw reachability cache and possible loops with LNM. [CSCdi50344]

  • RSRB will not declare that a peer is dead until keepalive times out. Therefore, for RSRB to detect the dead peer so that the ring list can be cleaned up properly, the keepalive value should be set as small as possible. [CSCdi50513]

  • Removing DLSw configuration by configuring no dlsw local-peer and adding the DLSw configuration back can cause a memory leak in the middle buffer. [CSCdi51479]

  • Applying a source-bridge output-lsap-list to a Token Ring interface when source-bridge explorer-fastswitch is enabled may cause packets permitted by the output-lsap-list to be dropped. The workaround is no source-bridge explorer-fastswitch. [CSCdi51754]

  • When a very large number of I-frames is sent by an end station to a DLSw router at the same instant, the following message may appear on the console: 
DLSW:CPUHOG in CLS background, PC=0x60549f3c

Because the CPU is being occupied by the CLS background process for a period of time, protocols that involve polling may lose their connections because of poll starvation. [CSCdi52382]

  • Ethernet sessions do not come up or drop. The LLC frames are bad after a retransmission. [CSCdi52934]

  • The LAN Network Manager (LNM) fails to link to the router's source bridge after the Token Ring interface is shut down on the remote router. The show lnm bridge command continues to display active link to the LNM. This problem does not occur when bridges are linked locally to the LNM.

The workaround is to remove the source-bridge command from the Token Ring interface and configure it back in. [CSCdi53954]

  • When configured to use the DSPU feature, the router may crash during deactivation of multiple downstream physical units. [CSCdi54114]

  • A router may crash when DSPU debugging is enabled on a Cisco 4500 or Cisco 7500 router. [CSCdi54277]

  • Very small SRB bridged frames on a large FDDI ring are not properly stripped from the ring and continue to loop indefinitely. [CSCdi54594]


Interfaces and Bridging

  • The concurrent routing and bridging (CRB) feature does not bridge IP traffic if the destination IP address is internal to the router. Also, IP packets with a destination IP address internal to the router are not responded to. [CSCdi48117]

  • Transparent bridge ports in the blocking state do not respond to ARP broadcasts. This problem is acute only when there is no other IP route to the blocking port. A workaround is available in the form of a static ARP entry in the host. [CSCdi51444]

  • A problem in the MEMD carve code on the Cisco 7000 can cause bandwidth considerations to be ignored. This might result in nonoptimal MEMD carving. [CSCdi52227]

  • A router may pause indefinitely when the configuration command encapsulation ppp is entered for Async-Group Interfaces. The configuration command async mode dedicated has the same effect. [CSCdi53185]

  • Asynchronous TTY lines on Cisco 2509 through Cisco 2512 devices sometimes stop answering new modem calls. The show line x command output shows the line with modem state in Idle and Hanging-up. A workaround is to configure sessiontimeout 0 for asynchronous lines. [CSCdi54196]


IP Routing Protocols

  • Running multiple Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) autonomous systems might consume all available memory in the router. [CSCdi36031]

  • Multicast fast-switching is not functional for ATM subinterfaces. A workaround is to configure no ip mroute-cache on the incoming subinterface. [CSCdi51178]

  • Unconfiguring OSPF can cause the router to reload. [CSCdi51283]

  • If two IP-Enhanced IGRP autonomous systems are configured, and an interface address is changed so that the interface moves from one autonomous system to the other, Enhanced IGRP will fail to operate on that interface. The workaround is to delete the IP address (using the no ip address command) before configuring the new address. [CSCdi52078]

  • Under certain conditions, Enhanced IGRP may stop transmitting packets. This may manifest itself as large numbers of routes repeatedly Stuck-In-Active. The workaround is to unconfigure and restart Enhanced IGRP, or reload the system. [CSCdi53466]

  • Regular expressions longer than 59 characters in the ip as-path access-list configuration command will cause the router to reload. [CSCdi53503]

  • Enhanced IGRP will stop working on an interface if the interface goes down for some reason and then comes back up. There is no workaround to this problem. [CSCdi53903]

  • Because of an uninitialized variable, multipoint GRE tunnels in Releases 10.3 and 11.0 may allow non-IP network protocols to be forwarded to all endpoints of the tunnel. This can lead to the perception that non-IP protocols are capable of being routed over the multipoint tunnel in these versions. Only IP multipoint tunnels are supported in these versions. In Release 11.1, routing IPX over GRE multipoint tunnels does not function. [CSCdi54192]

  • When booting a Cisco 7000 series router with a Release 11.1(2.2) or 11.1(2.3) software image, the router will crash. To work around, deconfigure ip sd listen on the interfaces.[CSCdi55369]


ISO CLNS

  • If two routers running Intermediate System-to-Intermediate System protocol (IS-IS) are connected via multiple point-to-point links and one of the links fails in only one direction, it is possible for traffic to be sent down the failing link and subsequently lost. This is because of a deficiency in the IS-IS protocol specification. There is no workaround to this problem. [CSCdi48351]

  • ISO-IGRP fails to install parallel routes into the CLNS prefix table under certain conditions. [CSCdi50714]


Novell IPX, XNS, and Apollo Domain

  • A Cisco 4000 router running Enhanced IGRP for IPX may generate CPU-HOG messages for the IPX SAP process. [CSCdi39057]

  • Clearing the SPX spoofing table with either the clear ipx spx-spoof command or by removing the ipx spx-spoof command from the last interface left spoofing may cause a system reload. [CSCdi53070]

  • The system may reload if NLSP is enabled and SNMP queries are done of the NLSP neighbor table. [CSCdi54546]

  • The default for ipx eigrp-sap-split-horizon needs to be changed to off. [CSCdi55576]


Wide-Area Networking

  • Under certain conditions, the router can reload with the message "System was restarted by error - Illegal Instruction, PC 0x300D646." This problem is related to ISDN. There currently is no workaround. [CSCdi45085]

  • With synchronous dial-on-demand routing (DDR) the dialer does not respect the enable-timeout before trying a second dialer map. The dial command is lost when the modem is initializing. [CSCdi46421]

  • Systems using the ATM Interface Processor (AIP) card may restart with the error message "System was restarted by error - Illegal Instruction, PC 0x0." [CSCdi47523]

  • A Cisco 7000 with two ATM interfaces running RFC 1577 ARP server will not register its own IP address. There are two workarounds:

    • Specify the full NSAP address of the ARP Server interface, using the atm nsap-address nsap-address command, instead of just the ESI portion.

    • After boot-up, issue a no atm arp-server command and then reissue the atm arp-server command. [CSCdi50592]

  • The dialer fails to bring up an additional BRI interface when both BRI B-channels are active and the dialer load-threshold load is exceeded. [CSCdi50619]

  • Under some unknown circumstances, a Cisco 4000 series router with MBRI will stop transmitting on an ISDN interface. Only a reload of the router can correct this. [CSCdi50628]

  • When bridging between a Cisco 7500 and an ISDN router running Cisco IOS software, data is not successfully passed if multilink PPP is used. [CSCdi51813]

  • If the LAN Extender (LEX) interface in a router running Cisco IOS Release 11.1(1) or 11.1(2) is shut down, and a no shutdown command is issued on the interface, the LEX interface will not come up. To recover, reboot the router or run Release 11.0. [CSCdi52515]

  • Using multidrop lines on a 5ESS ISDN switch is not recommended. If used, they will have SPIDs. SPIDs are sent out BRI0 only, so on a router equipped with an MBRI, lines other than BRI0 will not be able to place calls. The workaround is to get point-to-point lines from the telco. [CSCdi53168]

  • The DEC Spanning Tree protocol does not function properly in a LANE environment. To work around, use IEEE Spanning Tree protocol. [CSCdi53442]

  • A heavily loaded X.25 link that is experiencing congestion can, under rare conditions, enter a state where it oscillates between sending a RNR and a REJ. [CSCdi55677]


Release 11.1(1) Caveats/Release 11.1(2) Modifications

This section describes possibly unexpected behavior by Release 11.1(1). For additional caveats applicable to Release 11.1(1), see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.

All the caveats listed in this section are resolved in Release 11.1(2).


Access Server

  • The service hide-telnet-address command does not hide the telnet address in a connection closing message. The busy-message command does not suppress a connection closing message. [CSCdi47740]


Basic System Services

  • Available memory will slowly decrease on a router that is bridging IP and that has more than one interface with the same IP address. [CSCdi44023]

  • A Cisco 7500 that is fast switching source-route bridging (SRB) explorers, fast switching IP multicasts, or bridge-flooding packets might crash with a SegV exception error message and a stack trace that ends in the rsp_fastsend().

A workaround is to disable fast switching of IP multicasting, or fast switching of SRB fast explorers by using the no source explorer-fastswitch command. Another possible workaround is to remove or add an IP card, particularly of a different media type. [CSCdi45887]

  • Under heavy load conditions, a Cisco 2509 through Cisco 2512 access server might pause indefinitely and report a bus error. [CSCdi47190]

  • The alarmValue RMON MIB object always returns the sampled value at the end of the sampling period. This is incorrect behavior when the alarmSampleType is deltaValue(2). [CSCdi48677]

  • After some time running with RADIUS configured, the router will no longer successfully receive Ethernet packets, and communication will stop. A show interface command indicates that the interface on which RADIUS responses are received has a full input queue. [CSCdi49072]

  • RADIUS only works 255 times, after which it fails to recognize responses to the requests that the router sends. [CSCdi49412]


DECnet

  • DECnet Phase IV-to-Phase V conversion might introduce incorrect area routes into the ISO Interior Gateway Routing Protocol (IGRP), if DECnet L2 routes exist on the DECnet side. These area routes appear as "AA00" and are propagated to other routers. [CSCdi47315]


IBM Connectivity

  • When source-route transparent (SRT) bridging is configured on the router, calls to management functions related to source-route bridging (SRB) may not work correctly. [CSCdi42298]

  • When a front-end processor (FEP) initiates a Qualified Logical Link Control (QLLC) connection, a virtual circuit is established, but the exchange identification (XID) negotiation never proceeds to completion. The router sends XID responses as commands, rather than as responses. [CSCdi44435]

  • When two or more routers are connected to the same Token Rings, and each uses source-route bridging (SRB), a station on one of the rings might choose a non-optimal route with a path through both routers. In typical (large) networks, this behavior might result in explorer storms as well as suboptimal routes. [CSCdi45116]

  • A router might crash if running QLLC and using remote source-route bridging (RSRB) over a serial line to provide the Logical Link Control, type 2 (LLC2) connection from QLLC to an end station or host. The crash only occurs if multiple changes are made to the encapsulation type on the RSRB serial line. [CSCdi45231]

  • A router might report inaccurate traffic statistics. In particular, nonbroadcast frame counts might be incorrect if the router is acting as a source bridge on a Token Ring. [CSCdi46631]

  • Explorers are not forwarded to the CIP CSNA feature from DLSw+. [CSCdi47239]

  • When an IP peering protocol is in use in the router (for example, RSRB, STUN, or BSTUN), CLS DLUS (such as APPN and DSPU) may have difficulty establishing LLC2 sessions over RSRB virtual interfaces when the LLC2 path is bridged SRB only and does not traverse an IP cloud local to this router. [CSCdi47301]

  • Using a CIP with CSNA configured in a Cisco 7500 series router causes cBus complex restarts and output stuck messages for the CIP virtual interface. [CSCdi47536]

  • If a router receives a source-route bridging (SRB) packet with bit 2 of the routing control field set, the router might send back a bridge path trace report frame to a group address, instead of to the source of the original frame. This behavior may cause congestion. [CSCdi47561]

  • When using APPN/dependent LU requestor (DLUR) on a Cisco 4500, Cisco 4700, or Cisco 7500 router, a DLUR may accept only one downstream PU for dependent session activation at a time. [CSCdi47584]

  • A downstream physical unit (DSPU) sometimes retries connecting to the host too rapidly, with as many as sixty tries per second, flooding the host with exchange identification (XID) packets. This problem causes the NetView log to get congested and run out of storage, which might bring down the host. [CSCdi47803]

  • If DLSw with FST is configured, an LLC2 session should not be set up. [CSCdi47888]

  • The DLSw SDLC ABM bit is not turned off in the first exchange identification (XID) packet sent to an SDLC station. [CSCdi47942]

  • When proxy explorer and proxy NetBIOS are configured, looped RIFs might be created. The only workaround is to disable the feature. [CSCdi48577]

  • During cross-domain file transfers via Data Link Switching Plus (DLSw+) on a Logical Link Control (LLC) connection, frames might be sent out of sequence. This problem can cause a receiving Physical Unit 4 (PU 4) or Physical Unit 5 (PU 5) to disconnect. [CSCdi48915]

  • When a router running DSPU over Frame Relay in communication with a frame device breaks the session, it does not try to reconnect after a disconnect mode response is received. [CSCdi49044]

  • When attempting to run APPN over Frame Relay, the router may generate the following error and traceback messages: "APPN-6-APPNSENDMSG," "APPN-7-APPNETERROR," and "SYS-2-BADSHARE." [CSCdi49162]

  • On Cisco 7000 series routers installed with a CIP, the commands csna, llc2, offload, and show extended channel tcp-stack fail after a router reload or reboot. To recover, reboot the microcode. [CSCdi49312]

  • The router crashes when a get many command is issued for the ciscoDlswTConn MIB object from a management station. [CSCdi49393]

  • Accessing the object ciscoDlswVirtualSegmentLFSize returns a value of 17800 instead of the valid value of 17749 defined in the MIB. [CSCdi49435]

  • Zero is returned for SNMP get commands on ciscoDlswActiveCircuits and ciscoDlswCircuitCreates, even though circuits are open through DLSw. [CSCdi49441]

  • The number of downstream PUs that the Cisco IOS software supports should be increased from 256 to 1024. [CSCdi49448]

  • Sessions using an APPN Connection Network over FDDI that also use the router as a member of the FDDI connection network will fail to activate. [CSCdi49560]

  • Connections to a host cannot be established from a DSPU using virtual telecommunications access method (VTAM) through an IBM 3172 Channel Interface Processor (CIP). [CSCdi49872]

  • If peer A and peer B are DLSw priority peers (the keyword priority is on the remote peer definition), and peer A is reloaded, peer B may crash. [CSCdi50155]

  • Peer-on-Demand peers (peers that learn of each other through Border Peers) do not connect. The Cisco IOS software should be enhanced to add the options inactivity timeout and lf lfsize to the dlsw peer-on-demand-defaults command. [CSCdi50574]


Interfaces and Bridging

  • On a Cisco 4500 router, if you issue the no shutdown command on a Fiber Distributed Data Interface (FDDI) interface, the router will reboot. [CSCdi42429]

  • The Versatile Interface Processor (VIP) does not support enhanced online insertion and removal (EOIR) in Release 11.1(1). Do not online insert or remove any card on a Cisco 7000 or Cisco 7500 router if it has VIP installed and is running Cisco IOS Release 11.1(1). VIP EOIR is supported in Release 11.1(2). [CSCdi45136]

  • When a Cisco 7000 router Ethernet interface is the root of a spanning tree and UDP flooding is configured with turbo flooding, packet loops occur. The workaround is to disable turbo flooding. [CSCdi45659]

  • Transparent bridging and the Hot Standby Router Protocol (HSRP) cannot be simultaneously enabled on Fast Ethernet interfaces. Random crashes occur, which can result in image or memory corruption. [CSCdi48646]

  • Bridging from a Token Ring through an ATM cloud via RFC 1483 AAL5-SNAP encapsulation back to a Token Ring does not function because of an incorrect CTL/OUI. There is no workaround. [CSCdi49151]


IP Routing Protocols

  • If a router is incorrectly configured with an autonomous system (AS) placed in a confederation it is not part of, the confederation information within the AS path will be incorrectly propagated. The workaround is to configure the router correctly. [CSCdi46449]

  • Next Hop Resolution Protocol (NHRP) may cause memory corruption when attempting to send an NHRP purge packet. Specifically, if the network layer route to the destination no longer would cause the purge packet to be transmitted out the nonbroadcast multiaccess (NBMA) interface, NHRP attempts to modify low memory. On some systems, this behavior can cause the system to reload. [CSCdi47623]

  • Packet corruption can occur when IP packets are fast-switched from ATM interfaces to Token Ring interfaces configured with the multiring command. [CSCdi49734]

  • Multicast fast switching is not functional for ATM subinterfaces. A workaround is to configure no ip mroute-cache on the incoming subinterface. [CSCdi51178]


ISO CLNS

  • ISO Interior Gateway Routing Protocol (IGRP) will not work when interoperating between Motorola processor-based Cisco routers (older routers such as MGS, AGS+, or Cisco 7000) and millions of instructions per second (mips) processor-based Cisco routers (later routers such as the Cisco 4500, Cisco 4700, or Cisco 7500). [CSCdi44688]

  • Issuing a CLNS ping to one of the router's own address will cause the router to reload if debug clns packet is on. The workaround is to not have this particular debug on if you need to ping to one of the router's own addresses. [CSCdi50789]


Novell IPX, XNS, and Apollo Domain

  • Cisco 1003, Cisco 1004, and Cisco 1005 routers advertise all IPX services with a SAP hop count of zero. Both dynamically learned and static SAPs are sent out every interface with a zero hop count, which makes remote services invisible to Novell servers connected directly to the router (for example, on the LAN interface).

Clients on LANs with no server can connect correctly, because the router answers the GetNearestServer request. However, whenever a Novell server resides on the same LAN as the client, the client will not be able to connect to any remote services.

Use the show ipx servers command to determine whether any SAPs are being seen with zero hop count from the neighboring router. [CSCdi46488]

  • When an Enhanced IGRP route is advertised back into RIP, the delay within the Enhanced IGRP cloud is not taken into account properly in the tics value of the route when it is redistributed into RIP. The RIP-advertised route appear to be closer than it really is. [CSCdi49360]

  • When an interface goes down, services that are not learned over that interface are marked as down. This behavior might cause excessive SAP packet generation because packets are flooded first as down, are then learned, and are finally flooded again as new. [CSCdi49369]

  • If IPX Enhanced IGRP is running, the command sequence interface serial / no ipx network / no ipx routing may cause the router to reload. [CSCdi49577]


TCP/IP Host-Mode Services

  • Under unknown circumstances, random lines on an ASM will pause indefinitely in Carrier Dropped state. The only way to clear the line is to reload the ASM. [CSCdi44663]

  • Opening hundreds of simultaneous Telnet connections from a TTY or VTY can cause the software to reload with a watchdog timeout error. [CSCdi47841]


VINES

  • VINES servers located downstream might unexpectedly lose routes that were learned via Sequenced Routing Update Protocol (SRTP). This behavior results from improper handing of network sequences numbers by the system. Issuing a clear vines neighbor * command or disabling SRTP are suggested workarounds. [CSCdi45774]

  • The system reloads when it receives badly formatted Interprocess Communications Protocol (IPC) packets from the VINES application software Streetprint. Streetprint uses reliable messages that can span up to four VINES IP packets. The VINES IPC length field should contain the number of bytes that follow the long IPC header in a data packet, but Streetprint sets the IPC length in each IPC message to the total number of bytes of all IPC messages. The Streetprint vendor is working to resolve this problem. A workaround that validates the IPC length and drops IPC packets if they are longer than the maximum allowed IPC length (5800 bytes) should be available in an early 11.1 maintenance release. [CSCdi47766]


Wide-Area Networking

  • An X.25 interface might hang if the Link Access Procedure, Balanced (LAPB) layer gets stuck in the RNRsent state. This might occur if virtual circuits (VCs) receive encapsulated datagram fragments that are held for reassembly, and the number of these fragments approaches the interface input queue count. The LAPB protocol will not exit the RNRsent state until the number of held buffers decreases. This condition can be cleared if a shut /no shut is performed on the interface, or if the other end of the LAPB connection resets the protocol. [CSCdi41923]

  • If a new permanent virtual circuit (PVC) is defined on an ATM Interface Processor (AIP) when existing switched virtual circuits (SVCs) and PVCs are already defined, an interface reset might occur with a subsequent restart of all SVCs. [CSCdi43779]

  • When IP traffic is fast-switched from an AIP onto an FDDI interface, an extra byte added to the end of the packets. [CSCdi44580]

  • When ATM is running on a Cisco 7000, memory corruption may occur. [CSCdi45540]

  • Running X.25 Defense Data Network (DDN) encapsulation on a Cisco 2500 serial port might cause the router to reload. This problem appears to be the result of mixing X.25 switching and X.25 DDN. A workaround is to shut down the serial interface. [CSCdi45673]

  • Under certain conditions XOT data might be delayed by the router. [CSCdi45992]

  • Routers with ISDN BRI interfaces that use the isdn switch-type basic-net3 command may experience BRI port failures dues to all network layer control blocks (NLCBs) being used and never released. Once all NLCBs and call control blocks (CCBs) are used and hung, a reload of the router is required to use the BRI interface. The problem does not apply to ISDN Primary Rate interfaces (PRIs).

A possible workaround is to set the dialer idle-timeout value on the BRI routers connected to NET3 switches higher than the timeout value of the other router or routers connecting via ISDN. This workaround assumes the other router or routers do not have BRIs connected to NET3 switches, because they would have the same problem. This workaround also requires knowledge of the dialer idle-timeout value configured on the other router or routers.

The problem does not occur if the call hangup is initiated by the ISDN network rather than the BRI router connected to a NET3 switch.

Releases 11.0(2.1), 10.3(6.1) and 10.2(8.5) were the first software versions to exhibit the problem. [CSCdi46668]

  • A Cisco 4000 series router with ISDN BRI interfaces can run out of timer blocks and crash. Use the show isdn memory command to see if memory is not being freed. [CSCdi47302]

  • In some failed CHAT script operations over asynchronous interfaces, data can be left in an inconsistent state, sometimes causing a reload to occur during later operations. [CSCdi47460]

  • Under some unknown conditions, an ISDN B Channel may fail to disconnect. The PPP keepalive feature detects the partially disconnected link and repeatedly reports "exceeded max retries taking LCP down" every few minutes. This defect was introduced in software version 11.0(3.2). [CSCdi48111]

  • When packets are lost because of hold queue overflow or line errors, multilink PPP may incorrectly discard packets that were properly received.

To prevent this behavior, remove the cause of the line errors or increase the hold-queue size. [CSCdi48424]

  • If parallel connections are made to a dialer group or ISDN interface that use the same IP address and a neighbor route is necessary, then the neighbor route is added for the first connection only. Subsequent connections will detect that a route already exists and do not add another route. This situation works until the first connection closes and its neighbor route is removed. The other connections remain but no neighbor route is installed for them. This problem applies to parallel connections not to multilink bundles. [CSCdi49007]

  • When booting a router on which all ATM interfaces are in a no shut state, you need to issue a shutdown and no shutdown command sequence on one of the ATM interfaces to make Service-Specific Connection-Oriented Protocol (SSCOP) fully initialized and to allow ATM signaling to function properly. [CSCdi49275]

  • If Cisco's enhanced Terminal Access Controller Access Control System (TACACS+) is enabled, you cannot specify inbound authentication on the Point-to-Point Protocol (PPP) authentication configuration line. [CSCdi49280]

  • Nondefault IPX encapsulation on an ATM subinterface using the ipx encaps xxx command does not work. To configure the nondefault encapsulation, use the ipx network network encapsulation encapsulation-type command. [CSCdi49729]

  • Cisco IOS Release 11.0(6), Release 11.1(2), and Catalyst 5000 ATM software release 2.1 and later contain a fix for an Emulated LAN defect. If you deploy Release 11.0(6), Release 11.1(2), or Catalyst 5000 ATM software release 2.1 or later releases in your network, and you use Emulated LAN bridging features, you must upgrade the Cisco IOS software in all routers and Catalyst 5000 switches in your network to use a version of Cisco IOS software that contains the fix. Failure to upgrade all devices in a particular Emulated LAN will result in interoperability problems between Cisco devices.

If you choose to continue to use Cisco IOS Release 11.0(5), Release 11.1(1) or earlier releases, the Catalyst 5000 requires ATM software release 1.1. [CSCdi49790]

  • IPX packets fast switched by a Cisco 4500, Cisco 4700, or Cisco 7500 series router to an Emulated LAN (LANE) subinterface using SAP, SNAP, or Novell-Ethernet encapsulation may be dropped by the receiving IPX server or client because of a mismatch between the length indicated in the Ethernet packet header and the actual packet length. To work around, disable IPX fast switching on the ATM interface with the no ipx route-cache command. [CSCdi50312]

  • If a backup interface is brought up, a floating static route points through the backup interface to the remote node and network. When the original interface comes back up, the floating static route is removed. The backup interface will not see any traffic, and an idle timeout will bring down the backup connection.

If, however, the original interface comes back up before the backup connection is complete, the floating static route will have been removed and a neighbor route will be added to the peer address. This route will carry routing updates to the peer over the backup connection and thus reset the idle timeout with each packet. As a result, the backup interface will never disconnect. This behavior was added with Release 11.0(3). [CSCdi50489]

  • Fast switching IP traffic may fail from an ATM Interface Processor (AIP) onto an FDDI with RIF presence. [CSCdi50609]

  • International calls placed using the Australian Primary Rate switch type of primary-ts014 do not tag the format of the called address field correctly. As a result, calls to locations outside of Australia are rejected as unassigned. [CSCdi50927]

  • Cisco LANE clients do not interoperate with non-Cisco broadcast-and-unknown servers (BUSs) that deliver data to the client on Multicast Send virtual channel connections (VCCs). Packets sent to the client on the Multicast Send VCC are discarded. In addition, the error message "%LINK-2-NOSOURCE: Source idb not set" may appear when these packets arrive. There is no workaround. [CSCdi50945]


Microcode Revision History

The following sections describe each revision of microcode for the:

    • Cisco 7000 series routers using a route processor/silicon switch processor (RP/SSP) or route processor/switch processor (RP/SP) combination

    • Cisco 7500 series routers and Cisco 7000 series using an RSP7000 (see the section "Route Switch Processor (RSP) Microcode Revision History")


ATM Interface Processor (AIP) Microcode Revision Summary


AIP Microcode Version 10.13


Modification

AIP Microcode Version 10.13 fixes the following:

  • Ping between two routers fails intermittently with SMDS configuration. [CSCdi45807]


AIP Microcode Version 10.14


Modifications

AIP Microcode Version 10.14 fixes the following:

  • The AIP cannot be configured to issue idle cells instead of unassigned cells. [CSCdi48069]

  • The ATM Interface Processor (AIP) used with a RSP processor may stop receiving data if OAM cells are inserted in the incoming cell flow. [CSCdi55512]

  • New AIP microcode in 11.1(4.0.1) (aip177-1 and rsp_aip205-1) breaks ATM on RSP. [CSCdi60561]


AIP Microcode Version 10.15


Modification

AIP Microcode Version 10.15 fixes the following:

  • Sometimes a race condition occurs, and commands from a Route Processor (RP) or Route Switch Processor (RSP) are rejected. When this condition occurs, the following console messages are logged [CSCdi62445]: 
%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1011, VPI=0, VCI=262) on Interface 
ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC) 
%AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Teardown VC command (error code 
0x8000)


AIP Microcode Version 10.16


Modifications

AIP Microcode Version 10.16 fixes the following:

  • AIP microcode version 20.8 may cause the AIP card to lock into a state where it transmits corrupted packets, causing debug atm error showing "ATM(ATM9/0.1): VC(1) Bad SAP ..." at the receive side of the ATM VC. The transmission of data is usually affected in one direction only. The problem may occur when the input traffic exceeds the average rate configured on the ATM VC, when the bandwidth of the incoming interfaces exceeds the average rate on the outgoing VC or SVC.

A workaround is either to downgrade the AIP microcode to aip20-6 or to upgrade the AIP microcode to rsp_aip205-5, or aip20-9 when available. A short term workaround is clear int atm 5/0 on the transmit side. [CSCdi67812]

The same problem applies for aip10-15 on RP based platforms.

  • ATM traffic is lost during an online insertion or removal (OIR) event of an RSP4 card. [CSCdi66076]


Fast Ethernet Interface Processor (FEIP) Microcode Revision Summary


FEIP Microcode Version 10.3


Modification

FEIP Microcode Version 10.3 fixes the following:

  • Serial interfaces that are down but not administratively disabled (downed) may periodically reset with error "8010 - disable fsip_reset." [CSCdi49431]


FEIP Microcode Version 10.4


Modifications

FEIP Microcode Version 10.4 fixes the following:

  • The FX port adapter is not supported.

  • FEIP's keepalive will not detect line protocol down (disconnected cable) when configured for full duplex, so reliance on this feature to detect cable faults is inaccurate. The only known workaround is to periodically track successful transmissions and reception on the suspect interface. [CSCdi48337]


Fast Serial Interface Processor (FSIP) Microcode Revision Summary


FSIP Microcode Version 10.13


Modification

FSIP Microcode Version 10.13 fixes the following:

  • Serial interfaces that are down but not administratively disabled (downed) may periodically reset with error "8010 - disable fsip_reset." [CSCdi49431]


FSIP Microcode Version 10.14

FSIP Microcode Version 10.14 was never released.


FSIP Microcode Version 10.15

FSIP Microcode Version 10.15 was never released.


FSIP Microcode Version 10.16


Modifications

FSIP Microcode Version 10.16 fixes the following:

  • Using FSIP might cause a CiscoBus restart. [CSCdi58194]

  • Transmitter-delay does not work on FSIP DCE interfaces. [CSCdi58196]


FSIP Microcode Version 10.17


Modification

FSIP Microcode Version 10.17 fixes the following:

  • FSIP does not recognize CDE leads during a cutover from a Cisco 2501 serial port. [CSCdi64735]


FSIP Microcode Version 10.18


Modification

FSIP Microcode Version 10.18 fixes the following:

  • In DCE mode, FSIP looks for DCD and DSR up before declaring the line UP. FSIP should only look for DCD. [CSCdi64735]


MultiChannel Interface Processor (MIP) Microcode Revision Summary


MIP Microcode Version 12.0


Modification

MIP Microcode Version 12.0 fixes the following:

  • Non-FIFO queuing is not supported on MIP. [CSCdi44333]


Switch Processor (SP) Microcode Revision Summary


SP Microcode Version 11.15


Modification

SP Microcode Version 11.15 fixes the following:

  • Turning on ipx route-cache sse with microcode version SSP10-12 or SSP10-13 produces a mismatch between the frame length on odd-byte 802.3 IPX packets and the 802.3 length. Novell devices might not recognize these packets, resulting in communication timeouts.

The following three workarounds can be used:

  • Turn off padding on process-switched packets via the command:

no ipx pad-process-switched-packets

  • Configure the router for autonomous switching instead of SSE switching via the commands:

no ipx route-cache sse

ipx route-cache cbus

  • Turn off SSE switching:

no ipx route-cache sse

[CSCdi42802], [CSCdi45139], [CSCdi46156]


Silicon Switch Processor (SSP) Microcode Revision Summary


SSP Microcode Version 11.15


Modification

SSP Microcode Version 11.15 fixes the following:

  • Turning on ipx route-cache sse with microcode version SSP10-12 or SSP10-13 produces a mismatch between the frame length on odd-byte 802.3 IPX packets and the 802.3 length. Novell devices might not recognize these packets, resulting in communication timeouts.

The following three workarounds can be used:

  • Turn off padding on process-switched packets via the command:

no ipx pad-process-switched-packets

  • Configure the router for autonomous switching instead of SSE switching via the commands:

no ipx route-cache sse

ipx route-cache cbus

  • Turn off SSE switching:

no ipx route-cache sse

[CSCdi42802], [CSCdi45139], [CSCdi46156]


Versatile Interface Processor (VIP) Microcode Revision Summary


VIP Microcode Version 20.18


Modifications

VIP Microcode Version 20.18 fixes the following:

  • If you are connected to the VIP card by the unsupported RVIP console interface, the Cisco 7000 will crash if you remove the VIP card. This problem does not exist on Cisco 7500 series routers. [CSCdi45132]

  • The 4R ports on the VIP card do not support fast switching. Use process switching as a workaround. [CSCdi51744]


VIP Microcode Version 20.23

The next major release of VIP microcode after Version 20.18 is Version 20.23.

For modifications related to VIP, refer to the section "Release 11.1(2) Caveats/Release 11.1(3) Modifications" earlier in this document.


VIP Microcode Version 20.31

The next major release of VIP microcode after Version 20.23 is Version 20.31.

For modifications related to VIP, refer to the section "Release 11.1(3) Caveats/Release 11.1(4) Modifications" earlier in this document.


VIP Microcode Version 20.40

The next major release of VIP microcode after Version 20.31 is Version 20.40.

For modifications related to VIP, refer to the section "Release 11.1(4) Caveats/Release 11.1(5) Modifications" earlier in this document.


Route Switch Processor (RSP) Microcode Revision History

The following sections describe each revision of RSP microcode for each Cisco 7500 series interface processor.


ATM Interface Processor (AIP) Microcode Revision Summary


AIP Microcode Version 20.6


Modification

AIP Microcode Version 20.6 fixes the following:

  • Ping between the two routers fails intermittently with SMDS configuration. [CSCdi45807]


AIP Microcode Version 20.7


Modifications

AIP Microcode Version 20.7 fixes the following:

  • AIP sends out incorrect idle cells. [CSCdi48069]

  • VINES encapsulation errors cause an AIP outhung condition. [CSCdi50568]

  • Configuring the AIP microcode might cause a race condition to occur. [CSCdi54829]

  • ATM fails when used on a Route Switch Processor (RSP). [CSCdi60561]


AIP Microcode Version 20.8


Modification

AIP Microcode Version 20.8 fixes the following:

  • Sometimes a race condition occurs, and commands from a Route Processor (RP) or Route Switch Processor (RSP) are rejected. When this condition occurs, the following console messages are logged [CSCdi62445]: 
%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=1011, VPI=0, VCI=262) on Interface 
ATM5/0, (Cause of the failure: Failed to have the driver to accept the VC) 
%AIP-3-AIPREJCMD: Interface ATM5/0, AIP driver rejected Teardown VC command (error code 
0x8000)


AIP Microcode Version 20.9


Modifications

AIP Microcode Version 20.9 fixes the following:

  • AIP microcode version 20.8 may cause the AIP card to lock into a state where it transmits corrupted packets, causing debug atm error showing "ATM(ATM9/0.1): VC(1) Bad SAP ..." at the receive side of the ATM VC. The transmission of data is usually affected in one direction only. The problem may occur when the input traffic exceeds the average rate configured on the ATM VC, when the bandwidth of the incoming interfaces exceeds the average rate on the outgoing VC or SVC.

A workaround is either to downgrade the AIP microcode to aip20-6 or to upgrade the AIP microcode to rsp_aip205-5, or aip20-9 when available. A short term workaround is clear int atm 5/0 on the transmit side. [CSCdi67812]

The same problem applies for aip10-15 on RP based platforms.

  • ATM traffic is lost during an online insertion or removal (OIR) event of an RSP4 card. [CSCdi66076]


Ethernet Interface Processor (EIP) Microcode Revision Summary


EIP Microcode Version 20.2


Modification

EIP Microcode Version 20.2 fixes the following:

  • Version 1.6 Rev C0 EIP cards may cause cache parity errors on all Cisco 7500 series and RSP7000 systems. The cache parity errors may cause system reloads. Hardware revision and version levels can be determined by using the show diag command. The problem is resolved in EIP microcode rsp_eip20-2 or above. [CSCdi52082]


Fast Ethernet Interface Processor (FEIP) Microcode Revision Summary


FEIP Microcode Version 20.2


Modification

FEIP Microcode Version 20.2 fixes the following:

  • Serial interfaces that are down but not administratively disabled (downed) may periodically reset with error "8010 - disable fsip_reset." [CSCdi49431]


FEIP Microcode Version 20.3


Modifications

FEIP Microcode Version 20.3 fixes the following:

  • The FX port adapter is not supported.

  • FEIP's keepalive will not detect line protocol down (disconnected cable) when configured for full duplex, so reliance on this feature to detect cable faults is inaccurate. The only known workaround is to periodically track successful transmissions and reception on the suspect interface. [CSCdi48337]


Fast Serial Interface Processor (FSIP) Microcode Revision Summary


FSIP Microcode Version 20.2


Modifications

FSIP Microcode Version 20.2 fixes the following:

  • When using the X.21 protocol, DTE devices erroneously send data when Control is OFF. [CSCdi45512]

  • Using FSIP might cause a CiscoBus restart. [CSCdi58194]

  • Transmitter-delay does not work on FSIP DCE interfaces. [CSCdi58196]


FSIP Microcode Version 20.3


Modifications

FSIP Microcode Version 20.3 fixes the following:

  • Serial interfaces and their line protocols might occasionally go down if the interface cable is changed or the remote end dies and comes back. Issuing a show interface serial command produces the following: 
Serialx/y is down, line protocol is down
  Hardware is cyBus Serial
.
.
.
  0 output buffer failures, 0 output buffers swapped out
    0 carrier transitions
    RTS up, CTS up, DTR up, DCD up, DSR up

The serial interface will stay down if the remote side toggles. [CSCdi57573]

  • FSIP does not recognize CDE leads during a cutover from a Cisco 2501 serial port. [CSCdi64735]


FSIP Microcode Version 20.4


Modification

FSIP Microcode Version 20.4 fixes the following:

  • In DCE mode, FSIP looks for DCD and DSR up before declaring the line UP. FSIP should only look for DCD. [CSCdi64735]


MultiChannel Interface Processor (MIP) Microcode Revision Summary


MIP Microcode Version 22.0


Modification

MIP Microcode Version 22.0 fixes the following:

  • Non-FIFO queuing is not supported on MIP. [CSCdi44333]


Route Switch Processor 2 (RSP2) Microcode Revision Summary

The next major release of RSP2 microcode after Version 200.0 is Version 20.0.

For modifications related to RSP2, refer to the section "Release 11.1(4) Caveats/Release 11.1(5) Modifications" earlier in this document.

Note The initial release of RSP2 microcode was version 200.0, in Cisco IOS Release 11.1(2).


Versatile Interface Processor (VIP) Microcode Revision Summary

The VIP microcode for the RSP is the same as the Cisco 7000 VIP microcode.


Cisco Connection Online

Cisco Connection Online (CCO), formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously---a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

  • WWW: http://www.cisco.com.

  • Telnet: cco.cisco.com.

  • Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact ccohelp@cisco.com. For additional information, contact ccoteam@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or csrep@cisco.com.


Cisco Connection Documentation

The complete caveats against this release are available on the Cisco Connection Documentation, Enterprise Series CDs---formerly UniverCD---which is the Cisco library of product information on CD-ROM. On CD, access the Cisco IOS 11.1 caveats in the Cisco IOS Release 11.1 database.

The CD is updated and shipped monthly so it might be more current than printed documentation. To order the Cisco Connection Documentation, Enterprise Series CDs, contact your local sales representative or call Customer Service. The CDs are available individually, by month, and as an annual subscription.You can also access Cisco technical documentation on the World Wide Web URL http://www.cisco.com .

Copyright 1988-1996 © Cisco Systems Inc.


InfoBlast Homepage