IBM 8270 AND 8272 LAN SWITCH RELEASE NOTES - VERSION 5.2.3
Edited 23-AUG-2000
This set of release notes provides specific information for software release 5.2.3 for the IBM 8270 and 8272 LAN Switch Products. It documents important operating environment considerations.
Release 5.2.3A supports the following products:
IBM 8272 LAN Switch Module Planning and Installation Guide (GA27-4163-02)
IBM 8272 Nways Token-Ring LAN Switch Model 108 and Model 216 Planning and Installation Guide (GA27-4982-02)
8270 Publications CD-ROM (SK2T-0434-00)
8270 Publications are also available online at the following World Wide Web URL:
The Main Image (previously the .GZ file) and the Token-ring Port Microcode (previously the .SOL file) are now contained in one single load image to simplify code updates. This image is the TR_A52.GZ file or the TR_B52.GZ file.
The 8270 has the ability to store two copies of the main code and configuration. One copy of the main code is referred to as the Primary Image. The second copy of the code, if it exists, is referred to as the Alternate Image. The Primary Image will load by default.
Both main images must be Release 5.2 or later. If an earlier release is loaded all dual image support will be wiped out.
The Manage Primary/Alternate Images menu provides you with choices for controlling your main code images. If both images exist, you can choose to swap images thus making the image which was previously the Primary Image now the Alternate Image and vice-versa. When the main images are swapped the associated configuration data is also swapped. Swapping the images has no effect on the currently executing image.
You can delete the Alternate Image if it exists and if it is not the active (currently executing) image. The Primary Image can not be deleted.
The Alternate Image can be loaded by choosing the Alternate Image when prompted from the Reset Switch/Diagnostics menu.
If the target main image fails to load the boot code will automatically look to see if another image exists, and load that image if possible.
Clearing Non-Volatile RAM will clear NVRAM for the active (currently executing) image. Clearing NVRAM from the boot menu will clear NVRAM for the target image to be loaded. The NVRAM for the other image is preserved.
You can save the configuration data to an external file of your choice by choosing Upload from Switch from the Main Menu and filling in the required fields. If there are any ATM UFCs installed the configuration data for these UFCs is included in the switch configuration data.
This configuration file can be loaded into a switch that has an identical hardware configuration. Failure to abide by this rule will result in loss of configuration data. The downloaded configuration data replaces the stored configuration data associated with the active code image.
Note that a successful switch configuration download will cause an immediate reset of the switch. The currently executing image will be reloaded regardless.
Note that switch configurations can not be serially downloaded. They must be downloaded via tftp.
You should not download switch configuration data which was created with a release newer than the currently executing image.
You should not edit the uploaded configuration files.
Starting with Release 5.2, the code images have headers with File IDs. The code will now validate the File ID of the download image before saving it on the switch.
Note that previous versions of boot code are not compatible with version 5.2 of the Main Image. You must download version 5.2 of the boot code. See Loading the Latest Software for download procedures.
Release 5.2A has limited File ID checking:
Release 5.2B has improved File ID checking:
The recommended procedure for loading back-level code is:
This function was added to prevent the spread of invalid frames in the network, and to help identify the source of invalid frames. An FC field is considered invalid if the frame type is neither LLC nor MAC, or if the frame type is LLC and the reserved bits (b3-b5) are non-zero. When a frame with an invalid FC field is first seen by the switch, it creates a filter for both the source and destination address contained within that frame such that any subsequent frames addressed to either address are discarded. The initial frame will still be sent out all ports of the switch. At the time the filter is created, an error message is added to the switch message log containing the addresses to be filtered, and the incoming port. These "learned" filters will age normally, based on the port's aging parameters.
This function allows the switch to be managed from a single IP address within the set of domains enabled for Source-Route Bridging. Prior to this release, frames arriving from one domain (segment) could not access the IP address of a different domain (segment), even though the domains were bridged together. For some network configurations this limitation required you to administer several IP addresses (one for each bridged domain) to ensure manager access from any port on any domain. Also, as a result of this limitation, management stations in different places in the network may have needed to use different IP addresses for the same switch. The addition of this function removes those limitations.
The Read Only Password function provides users a way to monitor the status of 8270/8272 lines and LECs, including traffic counters, while preventing Read Only users from making any changes in the switch. Due to security considerations, much of the 8270/8272 configuration information is hidden from Read Only users.
Manual Spanning Tree provides a mechanism to place individual ports directly into forwarding state. Such ports will not participate in the 802.1d spanning tree algorithm. This feature is particularly useful when servers are directly attached to a switch port. Such servers will often fail to connect during the time it takes for a port to reach forwarding state under the normal spanning tree process.
Note: Ports should only be configured to be manually forwarding when there is no possibility of creating a loop in the network from such a configuration. Otherwise the port should be configured as automatic.
Support has been added for 802.5j mode for the 2-port Fiber UFC.
The ATM UFC Code Release listed is compatible with the Switch Code Release(s) listed below:
ATM UFC Release | 8270/8272 Release |
1.15.5 | 5.2 - 5.2.3 |
1.15.4 | 5.2, 5.2.1 |
1.15.3 | 5.2 |
1.15.3 | 5.1.1 |
1.15.1 | 5.1.1 |
1.15.0 | 5.1 |
1.14.2 | 5.01 |
1.14.2 | 4.03 |
1.12.3 | 3.6.1 |
1.11.0 | 3.2.3 |
1.10.0 | 3.2.2 |
IMPORTANT: Software for the 8270/8272 and ATM UFC must always be upgraded simultaneously. For example, a user currently running code versions 3.6.1 for the base switch and 1.12.3 for the ATM UFC should upgrade to 4.03 and 1.14.2. A mixture of code levels (3.2.3 and 1.14.2 for instance) is not supported.
The IBM 8272 port logic copies all frames on a ring in making the decision to forward or not forward a frame. The default settings will cause the IBM 8272 to SET the frame status bits on all data frames that it copies. This will avoid the need to update the protocol drivers that are expecting these bits to be set. However, this default may cause some devices to report and/or log excessive soft errors.
If your network management applications indicate an increase in soft error reports when the 8272 switch is installed, please contact an IBM service representative at 1-800-426-7299, call path 4, 6, 3 (In Canada, call 1-800-565-3344.) The problem can be resolved through configuration options.
If you want to have switch ports that are attached to shared media set the ring speed, you must change the default configuration of Auto-RSA16 to either Auto-Fix16, Auto-Fix4, or force the configuration to Adapter mode with Fix16 or Fix4 speed. If you use the 8272's Ring Speed Adjust feature you will need to set the ring speed for segmented rings.
This can affect the following objects:
8272 Private MIB OCTET STRINGs
DTRC MIB OCTET STRINGs:
RFC1213 OCTET STRINGs
RFC1231 OCTET STRINGs
RFC1493 OCTET STRINGs
RFC1573 OCTET STRINGs
RFC1695 OCTET STRINGs
LEC MIB OCTET STRINGs
DISCOVERY MIB OCTET STRINGs
8272 Private MIB
MAC filter entries can be created by a native SNMP SET request, network management application such as the IBM Nways Manager, a console session or a Telnet session.
When you WRITE, the configuration is changed.
When you READ, the data returned is the current operational state of the CRF Port, not the configuration.
File Name | Contents | Notes |
TR_A523.GZ | Main image and Token Ring port microcode | 1 |
TR_A523.BT | Boot image | 1 |
TR_A523.DEF | MIB Compiler Object Definition | 2 |
TR_A523.MIB | MIB definitions for private MIB | 2 |
TR_A523.TRP | MIB definitions for traps | 2 |
DTRCA523.MIB | MIB definitions for source routing | 2 |
README.TR | 8270/8272 Release Notes, Version 5.2.3 | |
READ_TR.HTM | 8270/8272 Release Notes, Version 5.2.3, html format |
NOTES
File Name | Contents | Notes |
TR_B523.GZ | Main image and Token Ring port microcode | 1 |
TR_B523.BT | Boot image | 1 |
TR_B523.DEF | MIB Compiler Object Definition | 2 |
TR_B523.MIB | MIB definitions for private MIB | 2 |
TR_B523.TRP | MIB definitions for traps | 2 |
DTRCB523.MIB | MIB definitions for source routing | 2 |
README.TR | 8270/8272 Release Notes, Version 5.2.3 | |
READ_TR.HTM | 8270/8272 Release Notes, Version 5.2.3, html format |
NOTES
IMPORTANT NOTICE |
CAUTION: YOU MUST ENSURE THAT YOU LOAD THE PROPER IMAGES ON THE 8270 AND 8272. LOADING THE 8270 FILES ON AN 8272, OR THE REVERSE, WILL DAMAGE YOUR SWITCH. IT WILL BE NECESSARY TO CONTACT YOUR SERVICE REPRESENTATIVE TO HAVE THE SWITCH REPAIRED. |
IMPORTANT NOTICE |
CAUTION: IF YOU ARE UPGRADING FROM A VERSION 2.X LEVEL OF CODE TO A 3.X VERSION OR HIGHER, THEN YOU MUST SERIALLY DOWNLOAD THE CODE THE FIRST TIME. AFTER YOU RESET THE SWITCH WITH THE NEW CODE THEN YOU MAY USE TFTP FOR FUTURE CODE UPGRADES. ALSO IF YOU ARE UPGRADING TO A VERSION BETWEEN 3.2.0 AND 5.1.1, THE .SOL IMAGE MUST ALSO BE DOWNLOADED IN ADDITION TO THE .GZ FILE. FOR VERSIONS 5.2 AND LATER, THE .SOL IMAGE IS INCLUDED IN THE .GZ FILE. |
IMPORTANT NOTICE |
CAUTION: For switches running ATM UFC code version 1.10 or higher, there is no requirement to upgrade all 827x's attached to an ATM network at the same time. Those networks running versions of the ATM UFC code prior to 1.10 MUST upgrade all switches at the same time. |
To load the latest software, the following procedure is recommended:
To load the latest software from the System Request Menu, follow the procedure below:
Some older levels of code only support download of the .gz file from the main menu. In this case, the System Request (SR) Menu should be used to download the new code. Access the SR menu by pushing the recessed SR button, which is located next to the Reset button. NOTE: The SR button has no label. Also, be aware that the SR menu will not appear until you release the SR button. |
IMPORTANT NOTICE |
CAUTION: After loading a previous level of code, if you do not clear NVRAM, the configuration files will still be for the current release and your results will be unpredictable. |
If you attempt to migrate to a previous level of code (from 4.x to 3.x for example) you must do the following:
If you attempt to migrate from version 5.2 or later to version 5.1.1 or earlier you will
need to DISABLE File ID Checking in the Download menu first. Versions 5.2 or later will
not allow code without headers to be downloaded. Versions 5.1.1 or earlier do not have
headers and do not support File ID Checking.
Other Download Considerations
Invoke the TFTP daemon using the following command:
tftp -t 30
The tables below correlate internal port number to external port names.
Internal Port | 8270-600 | 8270-800 | 8272-108 | 8272-216 | 8272 LAN Switch Modules |
1 | --- | 1-1 | 1 | 1 | 1 |
2 | --- | 1-2 | 2 | 2 | 2 |
3 | --- | 2-1 | 3 | 3 | 3 |
4 | --- | 2-2 | 4 | 4 | 4 |
5 | --- | 2-3 | 5 | 5 | 5 |
6 | --- | 2-4 | 6 | 6 | 6 |
7 | 1-1 | 3-1 | 7 | 7 | 7 |
8 | 1-2 | 3-2 | 8 | 8 | 8 |
9 | 1-3 | 3-3 | --- | 9 | --- |
10 | 1-4 | 3-4 | --- | 10 | --- |
11 | 2-1 | 4-1 | --- | 11 | --- |
12 | 2-2 | 4-2 | --- | 12 | --- |
13 | 2-3 | 4-3 | --- | 13 | 1-1 |
14 | 2-4 | 4-4 | --- | 14 | 1-2 |
15 | 3-1 | 5-1 | --- | 15 | 1-3 |
16 | 3-2 | 5-2 | --- | 16 | 1-4 |
17 | 3-3 | 5-3 | --- | 1-1 | 2-1 |
18 | 3-4 | 5-4 | --- | 1-2 | 2-2 |
19 | 4-1 | 6-1 | --- | 1-3 | 2-3 |
20 | 4-2 | 6-2 | --- | 1-4 | 2-4 |
21 | 4-3 | 6-3 | 1-1 | 2-1 | 3-1 |
22 | 4-4 | 6-4 | 1-2 | 2-2 | 3-2 |
23 | 5-1 | 7-1 | 1-3 | 2-3 | 3-3 |
24 | 5-2 | 7-2 | 1-4 | 2-4 | 3-4 |
25 | 5-3 | 7-3 | 4-1 | ||
26 | 5-4 | 7-4 | 4-2 | ||
27 | 6-1 | 8-1 | 4-3 | ||
28 | 6-2 | 8-2 | 4-4 | ||
29 | 6-3 | 8-3 | LATM | ||
30 | 6-4 | 8-4 |
Internal Port | LEC |
32 | X01 |
. | . |
. | . |
. | . |
63 | X32 |
64 | Y01 |
. | . |
. | . |
. | . |
95 | Y32 |
Note: X is the slot number of the first ATM UFC and Y is the slot number of the second ATM UFC
END OF RELEASE NOTES