|
|
April 17, 1998
This document describes the Catalyst 5000 series Token Ring module software release 3.2(1), including a list of problems fixed in this release and a list of 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:
The Catalyst 5000 series Token Ring module software release 3.2(1) 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 ships 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). For more information about accessing CCO, see the "Cisco Connection Online" section.
The following new support has been added to the Catalyst 5000 series Token Ring module software release 3.2(1):
For more information on these new features, see the "Amendments to the Documentation" section of this configuration note.
The following documents are available for the Catalyst 5000 series switch:
The following documents are 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 that was shipped with the Token Ring module.
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 Token Ring Bridge Relay Function [TrBRF] and Token Ring Concentrator Relay Function [TrCRF]). The valid priority range for the logical Token Ring ports is 0 through 7. The default is 4.
The Catalyst 5000 series Token Ring module software release 3.2(1) supports MTUs of up to 17800 bytes. The initial release of the Catalyst 5000 series Token Ring module did not support MTUs greater than 4472. Release 3.2(1) of the Catalyst 5000 series Token Ring module supports MTUs of up to 17800.
When configuring larger MTUs for the ports or TrBRFs on a Token Ring module, remember the following:
If you reduce the MTU for a TrBRF to a value that is less than the MTU currently configured for the individual ports or LECs in the TrBRF, the MTU for the ports or LECs is automatically reduced to a value (1500, 4472, 8144, or 17800) that is less than that specified for the TrBRF.
To aid in network management, the Catalyst 5000 series Token Ring module now allows you to perform active port monitoring. Active port monitoring copies traffic from a Token Ring port or TrCRF to a Token Ring Switched Port Analyzer (SPAN) port within a switch. Forwarding to the SPAN port takes place independently of the normal forwarding.
The Catalyst 5000 series Token Ring module allows you to configure a Switched Port Analyzer (SPAN) port for monitoring port traffic. This SPAN support allows you to perform active monitoring on any of the Token Ring ports or TrCRFs. Active port monitoring allows you to copy the traffic being switched by a source port (Token Ring port or TrCRF) to a Token Ring destination port located in the same switch. Only the logical link control (LLC) traffic that is being switched by the source port is monitored when you configure active port monitoring. The MAC frames are not monitored.
When configuring SPAN, you can configure for a single source, multiple source ports, or you can configure a TrCRF as a source port. However, when configuring SPAN, keep in mind the following:
To configure a SPAN port, issue the following command in privileged mode, specifying the source port (only one source port if you are configuring the SPAN port to monitor information transmitted from a source port), the destination port, and the direction of traffic that you want to monitor that is being switched on the source port.
set span {src_mod/src_port | src_vlan} dest_mod/dest_port [rx | tx | both]After entering the set span command and specifying a source port and destination port, you see a display similar to the following:
Console> (enable) set span 3/2 4/6 tx Enabled monitoring of Port 3/2 transmit traffic by Port 4/6 Console> (enable)
After configuring a SPAN port, ensure that SPAN has been enabled on the switch. If SPAN is not enabled on the switch, you can enable it using the set span command.
To enable SPAN, issue the following command while in privileged mode:
set span enableTo disable SPAN, issue the following command while in privileged mode:
set span disableTo verify the SPAN configuration, issue the following command:
show spanAfter entering the show span command, you see a display similar to the following:
Console> (enable) show span Status : enabled Admin Source: Port 3/2 Oper Source : Port 3/2 Destination : Port 4/6 Direction : transmit Console> (enable)
Table 1 describes the information returned by the show span command.
| Field | Description |
| Status | Status of whether SPAN is enabled or disabled. |
| Admin Source | Source port or TrCRF whose traffic is being monitored. |
| Oper Source | Source port or the ports within a TrCRF whose traffic is being monitored. |
| Destination | Destination port to which the source port traffic is being copied. |
| Direction | Indicates whether transmit, receive, or transmit/receive information is being monitored. |
You can use the following commands to view statistics and status information associated with Token Ring stations that are located on monitored rings.
Use the show station controltable normal command to display a collection of statistics and status information associated with each Token Ring station on the local ring. In addition, this command provides status information for each ring being monitored.
show station controltable [mod_num[/port_num]]| mod_num | Number of the module. |
| port_num | (Optional) Number of the port on the module. |
This command has no default setting.
Switch command
Normal
The following example shows how to display a collection of statistics and status information associated with each Token Ring station on Token Ring module 3:
Console> (enable) show station controltable 3 Port TableSize ActiveStation RingState ----- ----------------- ----------------- ----------------- 3/1 0 0 Normal Operation 3/2 0 0 Normal Operation 3/3 0 0 Normal Operation 3/4 0 0 Normal Operation 3/5 0 0 Normal Operation 3/6 0 0 Normal Operation 3/7 0 0 Normal Operation 3/8 0 0 Normal Operation 3/9 0 0 Normal Operation 3/10 0 0 Normal Operation 3/11 0 0 Normal Operation 3/12 0 0 Normal Operation 3/13 0 0 Normal Operation 3/14 0 0 Normal Operation 3/15 0 2 Normal Operation 3/16 0 0 Normal Operation Port BeaconSender BeaconNAUN OrderChanges ----- ----------------- ----------------- ----------------- 3/1 00:00:00:00:00:00 00:00:00:00:00:00 0 3/2 00:00:00:00:00:00 00:00:00:00:00:00 0 3/3 00:00:00:00:00:00 00:00:00:00:00:00 0 3/4 00:00:00:00:00:00 00:00:00:00:00:00 0 3/5 00:00:00:00:00:00 00:00:00:00:00:00 0 3/6 00:00:00:00:00:00 00:00:00:00:00:00 0 3/7 00:00:00:00:00:00 00:00:00:00:00:00 0 3/8 00:00:00:00:00:00 00:00:00:00:00:00 0 3/9 00:00:00:00:00:00 00:00:00:00:00:00 0 3/10 00:00:00:00:00:00 00:00:00:00:00:00 0 3/11 00:00:00:00:00:00 00:00:00:00:00:00 0 3/12 00:00:00:00:00:00 00:00:00:00:00:00 0 3/13 00:00:00:00:00:00 00:00:00:00:00:00 0 3/14 00:00:00:00:00:00 00:00:00:00:00:00 0 3/15 00:00:00:00:00:00 00:00:00:00:00:00 1 3/16 00:00:00:00:00:00 00:00:00:00:00:00 0 Console> (enable)
Table 2 describes the fields shown in the show station controltable command output.
| Field | Description |
| Port | Module and port number. |
| TableSize | Number of Token Ring station entries in the table associated with this port. |
| ActiveStation | Number of active Token Ring station entries in the table associated with this port. |
| RingState | Current status of the ring. |
| BeaconSender | Address of the sender of the last beacon frame received on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero. |
| BeaconNAUN | Address of the nearest upstream neighbor in the last beacon frame received on this ring. If no beacon frames have been received, this object is equal to six octets of zero. |
| OrderChanges | Number of add and delete events in the table associated with this port. |
show counters
show station ordertable
Use the show station ordertable normal command to display a listing of the order of stations on the monitored rings.
show station ordertable [mod_num[/port_num]]| mod_num | Number of the module. |
| port_num | (Optional) Number of the port on the module. |
This command has no default setting.
Switch command
Normal
The following example shows how to display:
Console> show station ordertable 3
Port OrderIndex Address
----- --------------- -----------------
3/15 1 00:05:77:05:40:63
2 00:00:30:cf:a0:98
Console>
Table 3 describes the fields shown in the show station ordertable command output.
| Field | Description |
| Port | Module and port number. |
| OrderIndex | Location of the station with respect to other stations on the ring. |
| Address | Physical address of the station. |
show counters
show station ordertable
In the event of a corrupted Flash, a Catalyst 5000 series switch can operate in boot mode. However, when the switch is operating in boot mode, a version 3.1 boot ROM is required for the supervisor module to recognize the Token Ring module.
If the Flash becomes corrupted and the supervisor engine module is running a version 3.1 boot ROM, you can download a new image through a Token Ring module while the switch is in boot mode.
If the Flash becomes corrupted and the supervisor engine module is not running a version 3.1 boot ROM, you can download a new Flash image to the switch while in boot mode via either of the following methods:
If you do need to upgrade your boot ROM, please contact the Cisco TAC.
The following is a list of problems that have been resolved in this release.
| Problem Identifier | Problem Description |
|---|---|
| CSCdj47074 | Delays in spanning-tree convergence when a TrCRF is reassigned |
| CSCdj52128 | The NMP TR endstation cannot receive unicast ARE or STEs |
| CSCdj63325 | Show station control fields not updated when a MAU is removed |
| CSCdj63333 | Show station control command does not indicate MAC address of the last beaconing station |
| CSCdj65924 | Set module enable/disable command not supported |
| CSCdj65928 | Multiple module download via TFTP not supported |
| CSCdj68805 | Heavy traffic may result in a packet being directed to the wrong port or ports |
| CSCdj75479 | Clear counters command fails to reset MAC and port counters |
| CSCdj77835 | BDPUs processed as regular explorer traffic and causing unresolved topology and traffic storms |
This section describes possible unexpected behavior and other known problems for Catalyst 5000 series Token Ring software release 3.2(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: 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: 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: 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 downloading an image 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: CSCdj78204
Problem Description: Heavy traffic passing through the ports on the Token Ring module may cause the Spanning-Tree Protocol state to become unstable.
Recommended Action: Reducing the traffic load stabilizes the Spanning-Tree Protocol.
Problem Identifier: CSCdj80899
Problem Description: The Network Management Processor (NMP) can crash or hang if it receives a Token Ring frame larger than 1500 bytes while operating in station mode.
Recommended Action: If the management VLAN (sc0) is a TrCRF (the default TrCRF 1003 or a user-defined TrCRF), do not set the MTU to anything larger than 1500 bytes.
Problem Identifier: CSCdj86580
Problem Description: Heavy traffic from a large number of Token Ring ports at near line rate may cause some frames with known destination addresses to be misdirected to ports in any VLAN. After this failure occurs, some frames will continue to be misdirected even at reduced line rates.
Recommended Action: Reset the Token Ring module.
Problem Identifier: CSCdj92841
Problem Description: During periods of high traffic, frames may not be forwarded or frames may be forwarded by the wrong port. When this conditions occurs, the session command to the Token Ring module fails.
Recommended Action: Reset the Token Ring module.
Problem Identifier: CSCdj94300
Problem Description: The Token Ring RMON extension (RFC 1513) ringStationOrderTables does not return Token Ring endstation information for endstations that are directly attached (not connected via a media access unit) when the show station ordertable command is issued.
Recommended Action: None.
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. 
|
|