Microcode Release Note For System Software Releases through 9.1(3) This release note describes the latest microcode upgrades for the A- type, M, and C chassis interface cards. Microcode is card-specific firmware that resides on replaceable EPROMs on most interface controller cards. As new software and hardware features are introduced, the microcode for affected cards is updated in order to implement new features, operate with new software, or fix bugs found in earlier versions. The latest version of the microcode is not required; you only need to install new microcode when it is required for a card to be compatible with a new software upgrade, if it enables new features or functions you want to implement, or if it fixes bugs that are causing problems with your current system. This release note specifies both the recommended and the required microcode versions for operation with all currently supported software releases. It is also a historical summary of the microcode versions released for each card. Instructions for replacing microcode are not part of this document; card- and version-specific replacement procedures are included with each microcode upgrade kit. Before software release 9.1, microcode information was included in the Router Software Release Notes. This new Microcode Release Note provides only microcode-specific information. It will be updated as required for microcode updates independent of software releases. The section "Obtaining Additional Information" on page 25, provides instructions for obtaining the latest revision of this release note and a list of related documents and instructions for obtaining them. This release note contains the following sections: * "New Microcode Versions," page 2-Descriptions of each new microcode including the features, functions, and caveats. * "Microcode Interoperability Summary," page 3-Recommended and required microcode for compatibility with system software releases 8.2 through 9.1. * "Microcode Revision History," page 5-Historical summary of previous microcode versions for each card. * "Obtaining Additional Information," page 25-Titles of other documents and instructions for retrieving them. New Microcode Versions New microcode is available with the 9.1(1) system software release for several of the AGS+ cards. Table 1 outlines the microcode versions available with 9.1 and distinguishes between maintenance (bug fix) releases, which do not require 9.1 software, and new feature releases which require 9.1 software for the new features. Subsequent sections describe the features, modifications, and caveats for each microcode version. Table 1 New Microcode Releases Available with System Software Release 9.1 New Microcode Replaces New Features or Requires 9.1 Version Bug Fixes System SW FDDI 10.0 - New Features Yes MEC 10.0 (MEC 5.1 only) - New Features Yes1 HSCI 10.0 - New Features Yes1 CTR 10.0 - New Card Yes FCIT 10.0 - New Card Yes2 FCIT 10.1 FCIT 10.0 Bug Fixes Yes2 ciscoBus2 10.0 - New Card Yes2 FDDI 2.0 FDDI 1.0 New Features Yes Bug Fixes No MEC 2.4 MEC 2.3 Bug Fixes No HSCI 1.1 HSCI 1.0 Bug Fixes No SBEMON 3.1 (R16M) SBEMON 3.0 Bug Fixes No STRMON 1.1 (1R/2R) STRMON 1.0 Bug Fixes No 1. Required version when ciscoBus2 (CCTL2) card is installed. When upgrading from a CCTK card to a CCTL2 card, all ciscoBus cards must be upgraded to this version. 2. These cards only operate with a ciscoBus2 (CCTL2) controller card. 3. See the prerequisites for FDDI 2.0 on page 17. Microcode Interoperability Summary Tables 2 and 3 summarize the compatibility of current microcode versions with system software releases. Some cards can operate with an earlier microcode version, although some features might not be available. Table 3 summarizes the minimum required microcode versions for System Software Releases 8.1(25) and later. New microcode versions are tested for backward compatibility. Table 2 lists the recommended microcode versions for each software release. Using the recommended version ensures that you will obtain maximum performance and reliability. Refer to these version numbers when ordering upgrades. Table 2 Recommended Microcode for System Software Interoperability Card 9.1 w/ 9.1 w/ Name 8.2(4Ð5) 8.2(6Ð8) 8.3(1Ð4) 9.0(2) CCTL CCTL2 CSC-SCI 1.3 1.3 1.3 1.3 1.3 1.3 CSC-MCI 1.9 1.9 1.9 1.9 1.9 1.9 CSC-R 2.2 2.2 2.2 2.2 2.2 2.2 CSC-R16M 2.0 3.0 3.0 3.0 3.1 3.1 CSC-1R Ð Ð Ð 1.0 1.1 1.1 CSC-2R Ð Ð Ð 1.0 1.1 1.1 CSC-ENVM 1.1 1.1 1.1 2.0 2.0 2.0 CSC-CCTL 2.0 2.0 2.0 2.0 2.0 Ð CSC-CCTL2 Ð Ð Ð Ð Ð 10.0 CSC-MEC (5.0) 1.7 1.7 1.7 1.7 1.7 1.7 CSC-MEC (5.1) 2.4 2.4 2.4 2.4 2.4 - CSC-C2MEC (5.1) - - - - - 10.0 CSC-HSCI - - 1.1 1.1 1.1 - CSC-C2HSCI - - - - - 10.0 CSC-FCI 2.0 2.0 2.0 2.0 2.0 - CSC-C2FCI - - - - - 10.0 CSC-C2FCIT - - - - - 10.1 CSC-C2CTR - - - - - 10.0 Table 3 Minimum (Required) Microcode for System Software Interoperability Card Name 8.1 8.2 8.2 8.2 8.3/9.0 8.3/9.0 9.1 w/ 9.1 w/ (25) (1-3) (4-5) (6-8) w/o AS w/ AS CCTL CCTL2 (see 1) (see 2) CSC-SCI 1.1 1.1 1.1 1.1 1.1 1.3 1.3 1.3 CSC-MCI 1.8 1.8 1.8 1.8 1.8 1.9 1.9 1.9 CSC-R 2.2 2.2 2.2 2.2 2.2 2.2 2.2 2.2 CSC-R16M - - 2.0 3.0 3.0 3.0 3.0 3.1 CSC-1R (see 3) - - - - - 1.0 1.0 1.1 CSC-2R (see 3) - - - - - 1.0 1.0 1.1 CSC-ENVM 1.1 1.1 1.1 1.1 1.1 2.0 2.0 2.0 CSC-CCTL 1.0 1.0 1.0 1.0 1.0 2.0 2.0 - CSC-CCTL2 - - - - - - - 10.0 CSC-MEC(5.0) 1.6 1.6 1.6 1.6 1.6 1.7 1.7 - (see 4) CSC-MEC(5.1) 2.1 2.1 2.1 2.1 2.1 2.2 2.2 - CSC-C2MEC(5.1) - - - - - - - 10.0 CSC-HSCI - - - - 1.0 1.0 1.0 - CSC-C2HSCI - - - - - - - 10.0 CSC-FCI 128.43 128.45 128.45 128.45 128.45 1.0 2.0 - CSC-C2FCI - - - - - - - 10.0 CSC-C2FCIT - - - - - - - 10.0 CSC-C2CTR - - - - - - - 10.0 1. System software 8.3 or 9.0 without autonomous switching 2. System software 8.3 or 9.0 with autonomous switching 3. Available only with system software 9.0 and later 4. Users currently using the MEC 5.0 card who wish to upgrade to a CCTL2 card must first upgrade all MEC rev 5.0 cards to MEC rev 5.1. Microcode Revision History The sections that follow describe the microcode revision history for each card. Note: Unless otherwise stated, the system software prerequisites (earliest level required) are the same as listed in Tables 2 and 3 in the previous section, "Microcode Interoperability Summary." CSC-MCI Microcode Revisions This section describes the various revisions of microcode for the multiport communications interface card (CSC-MCI). MCI Microcode Version 1.4 MCI Microcode Version 1.4 was the first officially released version of MCI microcode. It was released in the summer of 1988. Caveats * Ethernet might hang with keepalives turned on in high-collision environments. * Serial line reports DCD transitions when the interface is disabled. This causes the excessive error rate shutdown feature to fail when DCD flapping occurs. * AppleTalk fast routing is not supported. MCI Microcode Version 1.5 Released in March 1989, MCI Microcode Version 1.5 requires replacement of all 13 registered EPROMs. Modifications * Supports the nonvolatile memory cards (CSC-MC and CSC-MT). * Ethernets no longer hang with keepalives turned on in high collision environments. * Serial DCD transition interrupts no longer occur when the interface is disabled. * Supports additional protocols for use with fast switching. The protocol-specific fast-switching support is specified in the "Features" section of the appropriate system software release note. Caveats * Serial interface reports CRC errors as encapsulation failure. * An Ethernet interface, under certain traffic patterns, can receive an errored frame as often as once in 3000 to 4000 frames. MCI Microcode Version 1.6 Released in July 1990, this version only requires replacement of three of the registered EPROMs if MCI Microcode Version 1.5 is currently installed. For more information on the upgrade procedure, refer to the publication Upgrading MCI Cards to Version 1.6 (Part Number 78-0722C) Modifications Serial interface reports of CRC errors as encapsulation failure has been corrected. Caveats * Serial performance with X.25 at rates of 2 Mbps or higher can be impacted by very short (2- to 6-byte) packets. * In extremely rare cases, packets received on Ethernet can have the last byte or word corrupted due to extended dribble bit errors from certain other vendors' equipment. System Software Prerequisites Requires System Software Release 8.1(14) or later. MCI Microcode Version 1.7 Released in July 1990, this version requires replacement of all three of the registered EPROMs. Modifications * In MCI Microcode Version 1.5, an Ethernet interface, under certain traffic patterns, could receive an errored frame as good once in 3000 to 4000 frames. This has been corrected. * Supports additional protocols for use with fast switching. The protocol-specific fast- switching support is specified in the "Features" section of the appropriate system software release note. * Ethernet enhanced to completely receive frames that have framing or dribble bit errors. * The SEEQ Ethernet controller used on the MCI reports framing or dribble errors with certain other vendors' Ethernet interfaces. This behavior has been most prevalent in 10BaseT environments or where Ethernet hub or concentrator equipment is used. With MCI Microcode Version 1.7, in combination with System Software Release 8.1(19) or later, if only framing errors are reported, then frames that have framing or dribble bit errors will be received as good. * In combination with the newer revision (R68561AP) of the Rockwell MPCC integrated circuit, MCI Microcode Version 1.7 now supports sending zero in the first byte. This capability is required for SMDS and Frame Relay. Caveats * An Ethernet interface could experience repeated resets in an environment of late collisions in fiber or broadband Ethernets, and, if keepalives are turned off, it could appear to hang. * Serial performance with X.25 at rates of 2 Mbps or higher can be impacted by very short (2- to 6-byte) packets. * In extremely rare cases, packets received on Ethernet can have the last byte or word corrupted due to extended dribble bit errors from certain other vendors' equipment. System Software Prerequisites Requires System Software Release 8.1(19) or later. MCI Microcode Version 1.8 Released in January 1991, this version only requires replacement of three of the registered EPROMs if MCI Microcode Version 1.7 is currently installed. For more information on the upgrade procedure from version 1.5 to version 1.8, refer to the publication Upgrading MCI Microcode Version 1.5 to Version 1.8 (Part Number 78-0728C). For more information on the upgrade procedure from version 1.7 to version 1.8, refer to the publication Upgrading MCI Microcode Version 1.7 to Version 1.8 (Part Number 78-0766). Modifications Previously, an Ethernet interface could experience repeated resets in an environment of late collisions in fiber or broadband Ethernets, and, if keepalives were turned off, it could appear to hang. This condition has been corrected. Caveats * Serial performance with X.25 at rates of 2 Mbps or higher can be impacted by very short (2- to 6-byte) packets. * In extremely rare cases, packets received on Ethernet can have the last byte or word corrupted due to extended dribble bit errors from certain other vendors' equipment. System Software Prerequisites Requires System Software Release 8.1(25) or later. MCI Microcode Version 1.9 Introduced with System Software Release 9.0 in April 1992, this version requires replacement of all 13 registered EPROMs. For more information on the upgrade procedure from older versions of MCI microcode, refer to the publication Upgrading MCI Cards from Microcode Version 1.5 to 1.9 (Part Number 78-0728D) or Upgrading MCI Cards from Microcode Version 1.7/1.8 to 1.9 (Part Number 78-0766B). Modifications * Improved serial performance with X.25 at rates of 2 Mbps or higher. * Previously, in extremely rare cases, packets received on Ethernet could have the last byte or word corrupted due to extended dribble bit errors from certain other vendors' equipment. This has been corrected. System Software Prerequisites Requires System Software Release 8.1(25) or later. SCI Microcode Revisions This section describes the microcode revisions to the serial-port communications interface card (CSC-SCI). SCI Microcode Version 1.0 Version 1.0 was the first officially released version of SCI microcode. It was released in January 1989. Caveats * Serial interface reports CRC errors as encapsulation failures. This problem is identical to the serial line bug in MCI version 1.5. * Serial performance with X.25 at rates of 2 Mbps or higher can be impacted by very short (2- to 6-byte) packets. SCI Microcode Version 1.1 Released simultaneously with MCI Version 1.6, this version requires the replacement of two of the registered EPROMs if SCI Microcode Version 1.0 is currently installed. For more information on the upgrade procedure from Version 1.0 to 1.1, refer to the publication Upgrading SCI Microcode Version 1.0 to 1.1 (Part Number 78-0733). Modifications Serial interface reports of CRC errors as encapsulation failures has been corrected. Caveats Serial performance with X.25 at rates of 2 Mbps or higher can be impacted by very short (2- to 6-byte) packets. SCI Microcode Version 1.2 Introduced with System Software Release 8.3(1), SCI Microcode Version 1.2 requires replacement of all 12 registered EPROMs. For more information on the upgrade procedure from version 1.0 to 1.2, refer to the publication Upgrading SCI Microcode Version 1.0 to Version 1.2 (Part Number 78-0864-01). For more information on the upgrade procedure from version 1.1 to 1.2, refer to the publication Upgrading SCI Microcode Version 1.1 to Version 1.2 (Part Number 78-0863-01). Modifications * In combination with the newer revision (R68561AP) of the Rockwell MPCC integrated circuit, SCI Microcode Version 1.2 now supports sending a zero in the first byte. This capability is required for SMDS and Frame Relay. * SCI Version 1.2 supports additional protocols for use with fast switching. The protocol-specific fast-switching support is documented in the "New Features" section of the appropriate system software release note. * For environments with heavy line noise, error handling has been improved. * Previously, serial performance with X.25 at rates of 2 Mbps or above could be impacted by very short (2- to 6-byte) packets. This condition has been corrected. SCI Microcode Version 1.3 Released with software Release 9.0 in April 1992, this version contains only manufacturability modifications (that is, no additional capabilities are provided over SCI 1.2). For information on the upgrade procedure from version 1.0 to version 1.3, refer to the publication Upgrading SCI Cards from Microcode Version 1.0 to 1.3 (Part Number 78- 0864-02). For information on the upgrade procedure from version 1.1 to version 1.3, refer to the publication Upgrading SCI Cards from Microcode Version 1.1 to 1.3 (Part Number 78-0863-01). Modifications Manufacturing-related modifications only-no changes in functionality. CSC-R16 Microcode Revisions This section describes the microcode revisions to the CSC-R16 Token Ring interface card. CSC-R16 Microcode Version 2.0 Version 2.0 was the first officially released version of CSC-R16/SBEMON microcode. It was released in June 1991. Caveats If cabling problems exist, the router prints the following error message and does not attempt to restart the interface: %TR-3-WIREFAULT: Unit 1, wire fault: check the lobe cable MAU connection This error occurs to prevent route flapping in the various network layer protocols. This behavior is new as of release 8.2(6). An explicit clear interface command will cause the router to attempt to restart the interface. System Software Prerequisites Requires System Software Release 8.2(4) or later. CSC-R16M Microcode Version 3.0 This version of CSC-R16M microcode contains Madge microcode and requires replacement of the two SBEMON ROMs on the CSC-R16M card. For more information on the upgrade procedure from version 2.0 to version 3.0, refer to the Cisco Systems publication Upgrading the CSC-R16 Token Ring Interface Card to the CSC-R16M and Upgrading Microcode Version 3.0 to Version 3.1 on the CSC-R16M (Part Number 78-0848-02). Modifications Incorporates Madge microcode for significantly improved performance. Caveats * Continued extreme load conditions can result in faulty error counts due to priority lockout of the SBEMON firmware. Sustaining such loads for many seconds increases the potential for ring reset by the interface. * Source routing of IP across a router may not work. * The router may appear twice in a traceroute. * Users running both Novell and source-route bridging may experience the dropping of frames that are both explicitly addressed to the router and match the source- routing criteria. System Software Prerequisites Requires System Software Release 8.2(6) or later. CSC-R16M Microcode Version 3.1 This version of CSC-R16M microcode requires the replacement of the two SBEMON ROMs on the CSC-R16 card. For more information on the upgrade procedure from version 3.0 to 3.1, refer to the publication Upgrading the CSC-R16 Token Ring Interface Card to the CSC-R16M and Upgrading Microcode Version 3.0 to Version 3.1 on the CSC-R16M (Part Number 78- 0848-02). Modifications * Supports setting "early token release." This is a new feature. * Source routing of IP across the router has been made fully operational. * The router will no longer appear twice in a traceroute. * In a router running both Novell and source-route bridging, frames both explicitly addressed to the router and matching the source-routing criteria are no longer dropped. System Software Prerequisites Requires System Software Release 8.2(6) or later; however, System Software Release 9.1(1) or later must be used in order to take advantage of the modifications listed above. CSC-1R/2R Microcode Revisions This section describes the microcode revisions to the CSC-1R/2R dual 16- Mbps Token Ring interface cards. Both cards use the same microcode. CSC-1R/2R Microcode Version 1.0 Introduced with System Software Release 9.0 in April 1992, this is the first officially released version of CSC-1R/2R (STRMON) microcode. System Software Prerequisites Microcode Version 1.0 interoperates with System Software Release 9.0 and later. Note: The CSC-MC and CSC-MC+ (Flash) cards can be connected to the XBus connector on the CSC-1R/2R cards and to newer versions of the CSC-MCI card. Therefore, a CSC-MCI is not required for connection to a CSC-MC or a CSC-MC+ card if a CSC-1R or CSC-2R card is present. However, the format of the data stored on CSC-MC and CSC-MC+ cards connected to CSC-1R/2R cards is different than the format when they are connected to CSC-MCI cards. Therefore, if you move a CSC-MC or CSC-MC+ card XBus cable from a CSC-MCI to a CSC-1R/2R card (or vice versa), you must erase and rewrite the contents of the memory on the CSC-MC or CSC- MC+ card. Caveats * Source routing of IP across a router may not work. * The router may appear twice in a traceroute. * Users running both Novell and source-route bridging may experience the dropping of frames that are both explicitly addressed to the router and match the source- routing criteria. System Software Prerequisites Interoperates with System Software Release 9.0 and later. CSC-1R/2R Microcode Version 1.1 Introduced with System Software Release 9.1, this version of CSC-1R/2R microcode requires the replacement of the STRMON ROM on the CSC-2R card. For more information on the upgrade procedure from version 1.0 to 1.1, refer to the publication Upgrading the Microcode EPROM on the CSC/1R/2R Token Ring Interface Cards (Part Number 78-1050-01). Modifications * Support for setting "early token release" was added. This is a new feature. * Source routing of IP across the router has been made fully operational. * The router will no longer appear twice in a traceroute. * In a router running both Novell and source-route bridging, frames both explicitly addressed to the router and matching the source-routing criteria are no longer dropped. * The ability to support fast switching was added. System Software Prerequisites Requires System Software Release 9.0 or later; however, 9.1 or later is required in order to take advantage of the preceding modifications. CSC-C2CTR Microcode Revisions This section describes the microcode revisions to the CSC-C2CTR 4-port Token Ring card. CSC-C2CTR Microcode Version 10.0 Introduced with System Software Release 9.1, this is the first officially released version of CSC-C2CTR microcode. System Software and Microcode Prerequisites * Requires System Software Release 9.1 or later. * Refer to Tables 1 through 3 for information on the microcode levels required for other cards used in conjunction with the CSC-C2CTR. Environmental Monitor (ENVM) Microcode Revisions This section describes the microcode revisions to the environmental monitor (CSC-ENVM) card. ENVM Microcode Version 1.1 Version 1.1 was the first officially released version of ENVM (ECMON) microcode. ENVM Microcode Version 2.0 Introduced with System Software Release 9.0 in April 1992, ECMON 2.0 provides additional accuracy and functionality to the ENVM card. For information on the upgrade procedure from version 1.1 to 2.0, refer to the publication Installing and Configuring the Environmental Monitor Card (Part Number 78-0899-01). ENVM Microcode Version 2.1 This version contains manufacturing-related enhancements only, no new features or fixes. Modifications * Gives improved accuracy in voltage, temperature, and air-flow sensing, and in warning messages and shutdowns. * Provides a log of previous shutdown history upon subsequent boot. * Provides access to environmental parameters via SNMP queries. For more information on the new features provided with ECMON 2.0, see "Managing and Monitoring the System" in the Router Products Configuration and Reference manual. System Software Prerequisites Requires System Software Release 9.0 or later for SNMP query features. ciscoBus(tm) Controller Microcode Revisions This section describes the microcode revisions to the Cisco proprietary first-generation ciscoBus controller card (CSC-CCTL). ciscoBus Microcode Version 1.0 Version 1.0 of ciscoBus microcode was the first officially released version of ciscoBus microcode. ciscoBus Microcode Version 2.0 Version 2.0 of CiscoBus microcode was introduced with System Software Release 8.3(1) to support IP autonomous switching and the new HSSI interface. Version 2.0 requires replacement of all nine registered EPROMs. For more information on the upgrade procedure from version 1.0 to 2.0, refer to the publication Upgrading the cBus Controller Card Microcode Version 1.0 to Version 2.0 (Part Number 78-0856). Modifications * Support for IP autonomous switching has been added. * Support for the HSCI interface controller has been added. System Software and Microcode Prerequisites * Requires System Software Release 8.3(1) for autonomous switching or HSCI support. * Refer to Tables 1 through 3 for information on the microcode levels required for other cards used in conjunction with the CSC-CCTL. ciscoBus2 Controller Microcode Revisions This sections describes the microcode revisions to the Cisco proprietary ciscoBus2 controller card (CSC-CCTL2). ciscoBus2 Microcode Version 10.0 Version 10.0 of ciscoBus2 microcode was the first officially released version of ciscoBus2 microcode. System Software and Microcode Prerequisites * Requires System Software Release 9.1(1) or later. * Refer to Tables 1 through 3 for information on the microcode levels required for other cards used in conjunction with the CSC-CCTL2. FDDI Microcode Revisions This section describes the microcode revisions to the Fiber Distributed Data Interface controller card (CSC-FCI). Note: With the release of the ciscoBus2 controller (CSC-CCTL2), the microcode for the CSC-FCI must match the ciscoBus controller. In order to use the ciscoBus2 controller (CSC-CCTL2), FCI Microcode Version 10.x is required. To use the older ciscoBus controller (CSC-CCTL), FCI Microcode Version 2.0 or a previous version are required. Note: When using FCI Microcode Version 1.0 or later, the CCTL microcode must be 2.0 or later Note: The revision numbering scheme for the FDDI microcode has been amended to conform with the numbering scheme for other microcode versions. Thus, FDDI Microcode Version 128.43 was the first release, followed by 128.45, then 1.0, then 2.0, and 10.0. FDDI Microcode Version 128.43 FDDI Microcode Version 128.43 was the first officially released version of FDDI microcode. It was released in May 1990. Caveats Routers can hang in high-traffic environments where the FDDI ring is extremely unstable (continual transitions). User-perceived problems include the following: * The router locks up, and a power cycle is the only way to correct the problem. * Performance degrades over time. * High instances of output hangs and ciscoBus controller restarts occur. * Symptoms may include the following error message (traceback information needs to be examined and is release-version-dependent): May 21 15:24:23 145.1.89.254 19: %SYS-2-GETBUF: Bad getbuffer, bytes= 16654 -Process="Virtual Exec", level=4, pid= 41 -Traceback=5014 4510E 66BE 9E380 9B408 A07B8 A1 028 A0100 Performance can degrade significantly due to excessive processor utilization if a MIC connector is pulled from one of the PHY ports. (Both PHY ports erroneously contend to be active.) The problem can be remedied with the cmt disconnect phy {A | B} command when the problem is observed. FDDI Microcode Version 128.45 Released in June 1991, this version requires replacement of all eight EPROMs. Modifications Fixes potential hang condition in high-traffic environments. Caveats Performance can degrade significantly due to excessive processor usage if a MIC connector is pulled from one of the PHY ports. (Both PHY ports erroneously contend to be active.) The problem can be remedied with the cmt disconnect phy {A | B} command when the problem is observed. System Software Prerequisites Does not work with System Software Releases 8.2(1), 8.2(2), or 8.2(3). FDDI Microcode Version 1.0 Released in October 1991, FDDI Microcode Version 1.0 requires replacement of all eight registered EPROMs. For more information on the upgrade procedure from version 128.43 or version 128.45 to version 1.0, refer to the publication Upgrading FDDI Controller Interface (FCI) Cards from Microcode Version 128.43/128.45 to Version 1.0 (Part Number 78- 0857). Modifications * Fixes the excessive processor utilization problem when a MIC connector is pulled from one of the PHY ports. * Performance is improved in excessively "bursty" environments (such as environments with frequent NFS timeouts). * Support has been added to interoperate with most single-mode and multimode converters. Caveats With System Software Releases 8.3 or 9.0, under heavy loads, a transmit logic error can cause the FDDI interface to hang and produce the following error message: Interface fddi 0 output hung, restarting cbus 0 controller - mci_output() System Software and Microcode Prerequisites * For information on the microcode levels required for other cards used in conjunction with the CSC-FCI, refer toTables 1 through 3. The microcode for CSC-CCTL must be version 2.0 or greater. * For FDDI Microcode Version 1.0, System Software Release 8.2(4) or later is required to support the three modifications listed above. FDDI Microcode Version 2.0 FDDI Microcode Version 2.0 requires replacement of all eight registered EPROMs. For more information on the upgrade procedure from a previous version to version 2.0, refer to the publication Upgrading CSC-FCI Cards to Microcode Version 2.0 or 10.0 (Part Number 78-0857-02). Modifications * Fixes potential output hangs under heavy loads. * This version implements interface-based CMT performance enhancements. System Software and Microcode Prerequisites * For information on the microcode levels required for other cards used in conjunction with the CSC-FCI, refer to Tables 1 through 3. The microcode for CSC-CCTL must be version 2.0 or greater. * FDDI Microcode Version 2.0 requires System Software Release 9.1(1) or later to take advantage of the improved CMT performance FDDI Microcode Version 10.0 for the CSC-C2FCI Card FDDI Microcode Version 10.0 requires replacement of all eight registered EPROMs. For more information on the upgrade procedure from a previous version to version 10.0, refer to the publication Upgrading CSC-FCI Cards to Microcode Version 2.0 or 10.0 (Part Number 78-0857-02). Modifications Support for the new ciscoBus2 controller has been added. System Software and Microcode Prerequisites * For information on the microcode levels required for other cards used in conjunction with the CSC-FCI card, refer to Tables 1 through 3. * FDDI Microcode Version 10.0 requires System Software Release 9.1(1) or later and the ciscoBus2 controller. FCIT Microcode Revisions This section describes the microcode revisions to the Fiber Distributed Data Interface controller card (CSC-C2FCIT). FCIT Microcode Version 10.0 for the CSC-C2FCIT Card This was the first officially released version of microcode for the CSC- C2FCIT card. FCIT Microcode Version 10.0 requires replacement of one EPROM. For more information on the upgrade procedure from a previous version to version 10.0, refer to the publication Installing the CSC- C2FCIT Fiber Distributed Data Interface Card and Applique (Part Number 78-0946-01 Rev. A0). Modifications Support for the new ciscoBus2 controller has been added. Caveats * On the CSC-C2FCIT card running Microcode Version 10.0, the system may display the following on power up: bad rxeof vec * On the CSC-C2FCIT card running Microcode Version 10.0, a dual-homing standby link may go active incorrectly. * When configured for translational bridging, the FDDI receive interface may drop packets. System Software and Microcode Prerequisites * For information on the microcode levels required for other cards used in conjunction with the CSC-FCI, refer to Tables 1 through 3. * FCIT Microcode Version 10.0 requires System Software Release 9.1(1) or later and the ciscoBus2 controller. FCIT Microcode Version 10.1 FCIT Microcode Version 10.1 requires replacement of two components on the FCIT card: a microcode EPROM (socket U32) and a serial PROM (socket U34). Both components are included in the 10.1 microcode upgrade kit. Microcode version 10.1 has fixed the caveats for Microcode Version 10.0 on the CSC-C2FCIT card. For more information on the upgrade procedure from a previous version to version 10.1 on the CSC-C2FCIT card, refer to the publication Installing the CSC-C2FCIT Fiber Distributed Data Interface Card and Applique (Part Number 78-0946-02 Rev. A0). System Software and Microcode Prerequisites * For information on the microcode levels required for other cards used in conjunction with the CSC-FCIT card, refer to Tables 1 through 3. * FCIT Microcode Version 10.1 requires System Software Release 9.1(1) or later and the ciscoBus2 controller card. CSC-MEC Microcode Revisions This section describes the microcode revisions to the Multiport Ethernet Controller (CSC-MEC) interface card. The proper version of microcode for use with an MEC card depends on the hardware revision of the card. To determine revision levels and microcode versions in use on a given system, use the show controller cbus command or examine the label on the card edge. Table 4 lists the limitations that apply. Table 4 MEC Hardware/Microcode Prerequisites Controller Type Revision Level Compatible Microcode Versions 5.0 A (1.0) (see 1) 1.1, 1.4 5.0 C, D (1.0) 1.6, 1.7 (see 2) 5.1 E, F (3.0) 2.1, 2.2, 2.3, 2.4, 10.0 1. MEC controller type 5.0, rev A, is not compatible with the new MEC microcode. Users with this revision must upgrade to MEC 5.1 before installing a ciscoBus2 (CCTL2) controller card. 2. Version 1.7 is provided for users with cards of earlier revisions who would like to use autonomous switching. Note: With the release of the ciscoBus2 controller card (CSC-CCTL2), the microcode for the CSC-MEC must be installed to match the microcode on the ciscoBus controller card. In order to use the CSC-CCTL2, MEC Microcode Version 10.x is required. To use the older ciscoBus controller card (CSC-CCTL), MEC Microcode Version 2.4 or a previous version is required. MEC Microcode Version 1.1 MEC Microcode Version 1.1 was the first officially released version of MEC microcode. Caveats Under heavy traffic loads, the ciscoBus controller memory can be corrupted, resulting in a gradual decrease in performance. In extreme cases, an interface can hang. MEC Microcode Version 1.4 Version 1.4 requires replacement of three registered EPROMs if MEC Microcode Version 1.1 is currently installed. Refer to Table 4 for hardware revision prerequisites associated with this version of microcode. Modifications MEC Microcode Version 1.4 fixes the caveat in MEC version 1.1. MEC Microcode Version 1.6 MEC Microcode Version 1.6 was released in February 1991. This version requires the replacement of all 13 registered EPROMs. For hardware revision prerequisites associated with this version of microcode, refer to Table 4. Modifications MEC Microcode Version 1.6 supports the hardware upgrade from 5.0, Revision A to 5.0, Revision C. Caveats MEC Microcode Version 1.6 does not properly support packets that start on odd-byte boundaries. This problem impacts AppleTalk fast switching with some other vendors' software. MEC Microcode Version 1.7 Introduced with System Software Release 8.3(1) in October 1991, this version requires replacement of all 13 registered EPROMs. For more information on the upgrade procedure from version 1.6 to version 1.7, refer to the publication Upgrading MEC Microcode Version 1.6/2.1 to Version 1.7/2.2 (Part Number 78-0858). For hardware revision prerequisites associated with this version of microcode, refer to Table 4. Modifications * Support has been added for autonomous switching. * As a performance improvement for AppleTalk fast switching with System Software Release 8.3(1), support has been added for handling packets that start on odd-byte boundaries. Caveats MEC Microcode Version 1.7 does not properly support packets that start on odd-byte boundaries when used with System Software Releases earlier than 8.2(6). This problem impacts AppleTalk fast switching with some other vendors' software. MEC Microcode Version 2.1 MEC Microcode Version 2.1 was released in February 1991 with the MEC controller type 5.1 card. For hardware revision prerequisites associated with this version of microcode, refer to Table 4. Modifications MEC Microcode Version 2.1 supports the hardware upgrade from Controller Type 5.0 to Revision 5.1. Caveats * MEC Microcode Version 2.1 does not properly support packets that start on odd-byte boundaries. This problem impacts AppleTalk fast switching with some other vendors' software. * In extremely high-collision environments, the transmitter may hang. In rare instances, if the output interface queues are full (due to continued extreme collision rates), the interface may not recover, even when issuing a clear interface command. This condition requires a system reset. MEC Microcode Version 2.2 Introduced with System Software Release 8.3(1) in October 1991, MEC Microcode Version 2.2 requires replacement of all 13 registered EPROMs. For more information on the upgrade procedure from version 2.1 to version 2.2, refer to the publication Upgrading MEC Microcode Version 1.6/2.1 to Version 1.7/2.2 (Part Number 78-0858). Refer to Table 4 for hardware revision prerequisites associated with this version of microcode. Modifications * Support has been added for autonomous switching. * As a performance improvement for AppleTalk fast switching with System Software Release 8.3(1), support has been added for handling packets that start on odd-byte boundaries. Caveats * The MEC Microcode Version 2.2 does not properly support packets that start on odd-byte boundaries when used with System Software Releases earlier than 8.2(6). This problem impacts AppleTalk fast switching with some other vendors' software. * In extremely high-collision environments the transmitter may hang. In rare instances, if the output interface queues are full (due to continued extreme collision rates), the interface may not recover, even when issuing a clear interface command. This condition requires a system reset. MEC Microcode Version 2.3 Introduced with System Software Release 9.0 in April 1992, MEC Microcode Version 2.3 requires replacement of all 13 registered EPROMs. For more information on the upgrade procedure from version 2.1 to 2.3 and from version 2.2 to version 2.3, refer to Upgrading MEC Cards from Microcode Version 2.2 to 2.3 (Part Number 78-0934-01). Refer to Table 4 for hardware revision prerequisites associated with this version of microcode. Modifications Fixes the transmitter hang problem that could occur in extremely high- collision environments. Caveats * The MEC Microcode Version 2.3 does not properly support packets starting on odd-byte boundaries when used with System Software Releases earlier than 8.2(6). This problem impacts AppleTalk fast switching with some other vendors' software. * Under very heavy loads, the MEC will repeat the first portions (12 to 16 bytes) of the packets it sends. MEC Microcode Version 2.4 Introduced with System Software Release 9.1, MEC Microcode Version 2.4 requires the replacement of all 13 registered EPROMs. For more information on the upgrade procedure from version 2.3 to 2.4, refer to the publication Upgrading CSC-MEC Cards to Microcode Version 2.4 or 10.0 (Part Number 78-0934-02). Refer to Table 4 for hardware revision prerequisites associated with this version of microcode. Modifications * Fixes the problem of repeating the first portions of packets it sends. * Version 2.4 improves the ability to detect and filter out errors received in noisy environments. This is especially important in environments such as DECNet and Novell, where there is no IP checksum verification, because it is possible for noise on the physical link to cause data errors. MEC Microcode Version 10.0 MEC Microcode Version 10.0 requires replacement of all 13 registered EPROMs. For more information on the upgrade procedure from a previous version to version 10.0, refer to the publication Upgrading CSC-MEC Cards to Microcode Version 2.4 or 10.0 (Part Number 78-0934-02). * Fixes the repeated sending of packet portions observed in MEC 2.3. Modifications Support for the new ciscoBus2 controller has been added. System Software and Microcode Prerequisites * For information on the microcode levels required for other cards used in conjunction with the CSC-MEC, refer to Table 4. * MEC Microcode Version 10.0 requires System Software Release 9.1(1) or later and the ciscoBus2 controller (CSC-CCTL2). HSCI Microcode Revisions This section describes the microcode revisions to the high-speed serial communications interface (CSC-HSCI), which supports both the HSSI (the High-Speed Serial Interface specification) and UltraNet interfaces. Note: With the release of ciscoBus2 controller (CSC-CCTL2), the microcode for the CSC-HSCI must be installed to match the ciscoBus controller. HSCI Microcode Version 10.x is required for use with the ciscoBus2 controller (CSC-CCTL2). HSCI Microcode Version 1.0 is required for use with the older ciscoBus controller (CSC-CCTL). HSCI Microcode Version 1.0 HSCI Microcode Version 1.0 is the first officially released version of HSCI microcode. System Software and Microcode Prerequisites * HSCI Microcode Version 1.0 requires System Software Release 8.3(1) or later. * Refer to Tables 1 through 3 for information on the microcode levels required for other cards used in conjunction with the HSCI. HSCI Microcode Version 1.1 HSCI Microcode Version 1.1 requires the replacement of all 15 registered EPROMs. For more information on the upgrade procedure from version 1.0, refer to the document Upgrading CSC-HSCI Cards to Microcode Version 1.1 or 10.0 (Part Number 78-1001-01). Modifications * Fixes Ultra Native Mode giants problem. This allows the user to set the MTU size of the UltraNet to any size between 64 and 4500. Previously some common sizes, such as 1500 were not correct. When the MTU was set to 1500, a 1500-byte packet would be interpreted as a giant and discarded. * Fixes heavy traffic problem. Heavy traffic on UltraNet or HSSI could cause buffer losses. This would result in many dropped packets, and became worse over time. * Forces HSSI applique to reset if there is a hardware error. Previously, multiple 256-byte packets may have caused the HSSI interface to pause indefinitely or for a few seconds depending on the serial protocol. Now the microcode recognizes that the interface is paused and resets the interface. This may result in a few dropped packets, but it will not hang the interface. The show interface hssi command displays the error as an "applique" error. System Software and Microcode Prerequisites * HSCI Microcode Version 1.1 requires System Software Release 8.3(1) or later. * Refer to Tables 2 and 3 for information on the microcode levels required for other cards used in conjunction with the HSCI. HSCI Microcode Version 10.0 Introduced with System Software Release 9.1 to support ciscoBus2, HSCI Microcode Version 10.0 requires the replacement of all 15 registered EPROMs. For more information on the upgrade procedure from version 1.0, refer to the publication Upgrading CSC-HSCI Cards to Microcode Version 1.1 or 10.0 (Part Number 78-1001-01). Modifications This version adds support for ciscoBus2. System Software and Microcode Prerequisites * HSCI Microcode Version 10.0 requires System Software Release 9.1(1) or later. * Refer to Tables 2 and 3 for information on the microcode levels required for other cards used in conjunction with the HSCI. Obtaining Additional Information This section lists the titles of other related documents and instructions for obtaining them. Instructions for Microcode Upgrade Kits Each microcode upgrade kit comprises one or more microcode ROMs (and in some cases additional replacement components) and the installation instructions. Table 5 lists the upgrade kits currently available and the titles of the installation instructions. The Document Part Number is an ordering number and is provided for verification. When you receive a document, check the Document Part Number in the upper right corner of the first page to ensure that you have the correct document. Note: To order copies of these documents, or to obtain additional upgrade or compatibility information, contact a service representative or Cisco Systems' Technical Assistance Center (TAC) at 800 553-2447 or tac@cisco.com. Table 5 Installation Instructions for Microcode Upgrade Kits Kit Part No. Title Doc Part No. MC-MCI3-V1.9 Upgrading CSC-MCI Cards from Microcode Version 1.5 to 1.9 78-0728-01 D0 MC-MCI3-V1.9A Upgrading CSC-MCI Cards from Microcode V1.7/1.8 to 1.9 78-0766-01 B0 MC-SCI-V1.3 Upgrading CSC-SCI Cards from Microcode Version 1.0 to 1.3 78-0864-02 MC-SCI-V1.3A Upgrading CSC-SCI Cards from Microcode Version 1.1 to 1.3 78-0863-02 MC-R16M-V3.1 Upgrading the CSC-R16M Card to Microcode Version 3.1 78-0848-02 MC-1R/2R-V1.1 Upgrading Microcode on the 1R/2R Token Ring Cards 78-1050-01 MC-MEC5.0C-V1.7 Upgrading CSC-MECs from Microcode Version 1.6/2.1 to 1.7/2.2 78-0858-01 MC-MEC5.1-V2.4 Upgrading CSC-MEC5.1 Cards to Microcode Version 2.4 or 10.0 78-0934-02 MC-MEC5.1-V10.0 Upgrading CSC-MEC5.1 Cards to Microcode Version 2.4 or 10.0 78-0934-02 MC-FCI-V2.0 Upgrading CSC-FCI Cards to Microcode Version 2.0 or 10.0 78-0857-02 MC-FCI-V10.0 Upgrading CSC-FCI Cards to Microcode Version 2.0 or 10.0 78-0857-02 MC-FCIT-V10.1 Installing and Upgrading the Card and Appliques 78-0942-02 MC-HSCI-V1.1 Upgrading CSC-HSCI Cards to Microcode CSC-C2FCIT Version 1.1 or 10.0 78-1001-01 MC-HSCI-V10.0 Upgrading CSC-HSCI Cards to Microcode Version 1.1 or 10.0 78-1001-01 MC-CCTL-V2.0 Upgrading the CSC-CCTL from Microcode Version 1.0 to 2.0 78-0856-01 MC-ENVM-V2.0 Installing and Configuring the CSC-ENVM in the AGS+ 78-0899-01 MC-MCI3-V1.9 Upgrading CSC-MCI Cards from Microcode Version 1.5 to 1.9 78-0728-01 D0 MC-MCI3-V1.9A Upgrading CSC-MCI Cards from Microcode Version 1.7/1.8 to 1.9 78-0766-01 B0 MC-SCI-V1.3 Upgrading CSC-SCI Cards from Microcode Version 1.0 to 1.3 78-0864-02 Publicly Accessible Files Cisco Systems maintains an online directory of documents that are available to users over the IP Internet via the TCP File Transfer Protocol (FTP). This directory contains current Cisco Systems release notes in PostScript format, and information and comments contributed by Cisco users and engineers. To access these files, use the anonymous login convention. The files are located on host name ftp.cisco.com. Log in as user anonymous. When prompted for a password, enter your own electronic mail address. Cisco's FTP server does not accept directory listing requests from anonymous users; retrieve the README file for a list of available files. For security reasons, Cisco's FTP server will only accept anonymous connections from hosts listed in the reverse mapping database of the Internet domain name system.