|
|
January 12, 1998
This document describes what is new in this release, including a list of the new features and the known (open) problems for this release. This document is available on the Cisco Connection Documentation CD-ROM or in print.
Sections in this document include the following:
This release includes support for the Catalyst 5000 series Token Ring module, which is a 16-port module that provides Token Ring connectivity for the Catalyst 5000 series of switches. For more information about the Token Ring module, see the Catalyst 5000 Series Token Ring Module Configuration Note that is shipped with each Token Ring module.
The CiscoView support for the Catalyst 5000 has been updated to include options for configuring and managing the Catalyst 5000 series Token Ring module. To upgrade to the latest release of the CiscoView Catalyst 5000 device package, download the device package from the Cisco Connection Online (CCO).
The following documents are available for the Catalyst 5000 series switch:
The following document is available for the Catalyst 5000 series switch Token Ring module:
Cisco documentation and additional literature are available on a CD called Cisco Connection Documentation, Enterprise Series. The CD is updated and shipped monthly, so it might be more up to date than printed documentation. To order the Cisco Connection Documentation, Enterprise Series CD, contact your local sales representative or call Customer Service. The CD is available both as a single CD and as an annual subscription. You can also access Cisco technical documentation on the World Wide Web URL http://www.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the tool bar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
This section contains information that has changed from what is documented in the Catalyst 5000 Series Token Ring Module Configuration Note.
The Catalyst 5000 Series Token Ring Module Configuration Note documents that the possible priority range for physical and logical ports is 0 through 255 (decimal) and that the default is 128.
While this information is correct for the physical Token Ring ports, it is incorrect for the logical ports (the connection between the TrBRF and TrCRF). The valid priority range for the logical Token Ring ports is 0 through 7. The default is 4.
This section describes possible unexpected behavior and other known problems for Catalyst 5000 series Token Ring software release 3.1(1).
Problem Identifier: CSCdj38286
Problem Description: While learning new MAC addresses under higher frame rates, the switch may drop a frame as the new address is being learned. This would be seen, for example, if 20 frames with the same unknown destination address were sent to the switch at a high rate (thousands of frames per second). The switch may only forward 19 of those frames (one may get dropped). Once the address is learned by the switch, the switch will forward all frames.
Recommended Action: None.
Problem Identifier: CSCdj45517
Problem Description: After downloading an image to the Token Ring module, messages indicating that the module has been removed and inserted appear. These messages are not significant and do not affect the image download process.
Recommended Action: None.
Problem Identifier: CSCdj46233
Problem Description: When a switch port is in the Inactive state and a lobe cable is connected to the port, the show mac command will show that the InOctet counter is increasing. This could occur if VTP V2 is not enabled.
Recommended Action: Ignore the InOctet counter for ports in the Inactive state or unplug the cable for Inactive ports.
Problem Identifier: CSCdj47074
Problem Description: When a TrCRF is moved from one TrBRF to another, the BDPUs generated by the new TrBRF are not received until approximately 30 seconds after the TrCRF BDPUs are observed. This could lead to slower convergence and an additional delay may be detected in the convergence of the TrBRF spanning tree.
Recommended Action: None.
Problem Identifier: CSCdj52128
Problem Description: The Token Ring endstation cannot receive unicast all-routes explorer or spanning-tree explorer frames on the management VLAN. Any unicast all-routes explorer or spanning-tree explorer frames received will be dropped.
Recommended Action: None.
Problem Identifier: CSCdj54910
Problem Description: The data in the Rcv-Frms field returned with the output of the show mac command reflects two times the number of frames that were actually received when the traffic being counted is non source-route with the unknown destination address and the source address being learned.
Recommended Action: None.
Problem Identifier: CSCdj63325
Problem Description: The data in the ActiveStation and OrderChanges fields returned by the show station control command retain their previous values after the attached MAU or concentrator is removed from the port. If a MAU or concentrator is reattached to the port, the ActiveStation field will report the correct number of active stations on the attached token ring. The OrderChanges field will, however, include the old value incremented by one.
Recommended Action: None.
Problem Identifier: CSCdj63333
Problem Description: The data in the BeaconSender field returned with the output of the show station control command does not reflect the MAC address of the station that caused the last Beacon condition on the Token Ring.
Recommended Action: None.
Problem Identifier: CSCdj65766
Problem Description: At least one port of the Token Ring module must be enabled when downloading a image to the Token Ring module.
Recommended Action: Do not disable ports on the Token Ring module before initiating a module download.
Problem Identifier: CSCdj65924
Problem Description: Enabling and disabling the Token Ring module using the set module enable/disable command is not supported in this release.
Recommended Action: To achieve similar functionality issue the set port disable mod_num/1-16 command, where mod_num is the slot in which the Token Ring module is installed.
Problem Identifier: CSCdj65928
Problem Description: Downloading images to multiple Token Ring modules in the same chassis using the multiple module download command is not supported in this release.
Recommended Action: To download module images to the Token Ring module, use the download server filename slot_num command where slot_num is the slot in which the Token Ring module is installed.
Problem Identifier: CSCdj66141
Problem Description: IPX clients that are directly attached to a Token Ring module port may not be able to open and insert on the ring because it times out before the spanning tree has resolved and moved the Token Ring port into a forwarding state. However, since the IPX client is directly attached, spanning tree does not need to run on that port.
Recommended Action: Use the set spantree portfast enable command to accelerate the initialization of the port in the spanning tree.
Problem Identifier: CSCdj67357
Problem Description: If the configuration of a system is cleared or if the system is booted with VTP Version 2 disabled, after enabling VTP V2 (which is a requirement for running DRiP) DRiP will not be initialized.
Recommended Action: Disable then re-enable DRiP using the following of commands:
set tokenring reduction disableProblem Identifier: CSCdj67515
Problem Description: When utilization on the Token Ring module is 20 percent or greater (for example, three or more ports are receiving and transmitting traffic), TFTP downloads of new images for the Token Ring module may fail.
Recommended Action: Before performing an image download to the Token Ring module, stop traffic passing through the module. The Token Ring module will reset immediately upon completion of the download.
Problem Identifier: CSCdj67755
Problem Description: Issuing the command show drip statistics while a Token Ring module is initializing will cause the console to hang while the module comes online.
Recommended Action: Do not issue the command show drip statistics until the Token Ring module is online.
Problem Identifier: CSCdj68432
Problem Description: The Catalyst 5000 NMP Token Ring endstation application RIF cache can be filled with gratuitous route entries. Any source MAC address on the management VLAN that initiates an ARP containing a valid RIF will cause the NMP Token Ring endstation to cache an entry with that route.
Recommended Action: Use the clear arp all command to clear the Token Ring ARP and RIF caches.
Problem Identifier: CSCdj68494
Problem Description: Under certain conditions, configuring the IEEE spanning tree multicast address for a TrBRF can cause a broadcast storm. For example, this can happen when a TrBRF is using one multicast address in some switches, while using a different address in other switches.
Recommended Action: Upgrade the NMP software to Release 3.1(202). To obtain Release 3.1(202) of the NMP, contact the Cisco Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com.
Problem Identifier: CSCdj68514
Problem Description: Ports that remain assigned to a TrCRF that has been deleted will also remain disabled after that exact same TrCRF is recreated. If a port is assigned to a TrCRF that has been deleted and the port is not reassigned to a new TrCRF, then the port will remain disabled if that same TrCRF is recreated.
Recommended Action: Ensure that you reassign the ports of a TrCRF that you delete.
Problem Identifier: CSCdj68520
Problem Description: When a TrCRF is suspended, the ports assigned to the TrCRF are shown as inactive in the Status field of the show port command output, yet the ports continue to be enabled and open and inserted on the ring. Re-activating the TrCRF will allow normal operation to continue. However, while the TrCRF is suspended, the associated Token Ring ports should be administratively disabled.
Recommended Action: Disable the Token Ring ports assigned to a suspended TrCRF. When the TrCRF is reactivated, you can re-enable the ports.
Problem Identifier: CSCdj68694
Problem Description: Currently, there are known problems with using autosensing mode for port speed and operation mode. Problems can occur for ports configured for autosensing when they are opening and closing or inserting and deinserting.
Recommended Action: Use the set port speed and set tokenring portmode commands to manually configure the speed and operation mode of the ports.
Problem Identifier: CSCdj69889 and CSCdj69548
Problem Description: When multiple Token Ring modules exist in one switch and the majority of the ports on the Token Ring modules are in the default TrCRF (1003), a reset of one of the Token Ring modules causes several minutes of instability in the default TrBRF (1005) and default TrCRF (1003) spanning tree. At the end of this period of instability, the Token Ring module that was reset returns a status of OK when the show module command is issued. All of the port LEDs, however, are orange, and approximately 20 minutes after the reset, a failure message is displayed.
Recommended Action: Upgrade the NMP software to Release 3.1(202). To obtain Release 3.1(202) of the NMP, contact the Cisco Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com.
Problem Identifier: CSCdj70264
Problem Description: The Catalyst 5000 series Token Ring module does not support the set span command. Issuing the set span command to configure Token Ring ports as SPAN (Switch Port Analyzer) ports may cause port connectivity problems.
Recommended Action: Do not issue the set span command against the Token Ring module ports.
Problem Identifier: CSCdj70705 and CSCdj67138
Problem Description: When a port is added or deleted (or enabled/disabled) in a TrCRF, the logical connection between the TrCRF and its parent TrBRF reconfigures (goes through the Spanning-Tree Protocol states). This reconfiguration occurs only for an SRT TrCRF with a parent TrBRF that is running the IEEE Spanning Tree Protocol or an SRB TrCRF with a parent TrBRF that is running the IBM Spanning Tree Protocol. The configuration process causes traffic disruption from that bridge-ring (TrCRF/TrBRF) for 30 seconds if the TrBRF is running the IEEE Spanning Tree Protocol or 4 seconds if TrBRF is running the IBM Spanning Tree Protocol.
Recommended Action: Recommended Action: Upgrade the NMP software to Release 3.1(202). To obtain Release 3.1(202) of the NMP, contact the Cisco Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com.
When changes are made to the Catalyst 5000 software, the new image is posted to CCO. You can then obtain a copy of the image and download it to your switch.
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
For service and support for a product purchased directly from Cisco, use CCO.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information 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, product documentation, 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, and Internet e-mail, and it 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:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Documentation for Cisco products is available in three forms: in a CD-ROM package, printed books, and on the World Wide Web. You have the option of subscribing to the CD ROM package through an update service. Or you can order printed documentation at an additional cost. Refer to the information packet included with the router for detailed ordering information. You can also access Cisco documentation on the World Wide Web URL http://www.cisco.com. 
|
|