OPTIONAL FULL DUPLEX FUNCTION FOR F/C 2972 (Microcode Update)

Contents

Overview

The IBM RISC System/6000 Auto Token-Ring LANStreamer MC 32 Adapter (Feature Code 2972) has been enhanced to operate in full duplex mode on the selected models listed in Table 1. To enable this optional function, the adapter must be loaded with new microcode and its AIX device driver must be updated. Subject to the dependencies listed below, this function is intended for use on new system installations, as well as on existing ones. 

 Back to Contents 

Dependencies

This new optional full duplex feature for the Auto Token-Ring LANStreamer MC 32 Adapter can be installed only if the following dependencies are met.   
Table 1. List of Suported Machine Types and Models
M/T
Models
7012 380, 390, 39H, 397, G30, G40
7013 580, 58H, 590, 591, 595, 59H, J30, J40, J50
7015 980, 98B, 98E, 98F, 990, 99E, 99F, 99J, 99K, R20, R21, R24, R30, R40, R50
7030 3AT, 3BT, 3CT, 397
   Back to Contents 

To Determine Adapter Part Numbers and Microcode Levels

Before you install the microcode, it is important to determine the Part Number level of the adapter installed in the target system. If the part number read does not match at least one of the numbers above, please contact your IBM service representative to obtain the right level of adapter before proceeding. Use the following instructions to read the part number stored in the adapter's non-volatile memory. 

1)  List the token ring adapters installed in the system by typing: 

lsdev -C | grep 8fa2  

The output should look like: 

tok0       Available 00-03        Token-Ring High-Performance Adapter (8fa2) 
tok1       Available 00-04        Token-Ring High-Performance Adapter (8fa2) 

The Auto Token-Ring LANStreamer MC 32 Adapter(s), if present,  will be identified as tok0, tok1, ...tok(x). 

2) Detach the adapter(s) you want to check using: 

ifconfig tr(x) detach 

3) In order to read the microcode level information from the adapter, it must be set to "autosense" with: 

chdev -l tok(x) -a ring_speed=autosense  

4) To refresh and read the VPD, execute the following three commands: 

rmdev -l tok(x)  
mkdev -l tok(x)  
lscfg -l tok(x) -v 

Your output should be similar to: 

DEVICE       LOCATION       DESCRIPTION 

tok1                00-04                    Token-Ring High-Performance Adapter 
                                                        (8fa2) 

    Loadable Microcode Level.......WW1AD0    <--- Full Duplex Level (after updating) 
    Part Number..................................092G8711     <--- Adapter P/N 
    EC Level.........................................00E43926 
    Serial Number...............................002567LC 
    FRU Number.................................060G1593     <--- FRU P/N 
    Manufacturer................................IBM982 
    Network Address.........................08005A0CBE27 
    Displayable Message..................Token-Ring High-Performance Adapter  
                                                               (8fa2) 
 Back to Contents 

Updating the Adapter's Microcode

To update the microcode on the Auto Token-Ring LANStreamer MC 32 Adapter (Feature Code 2972), please read these instructions completely. It is also recommended that you print them for quick reference. 

With the machine powered ON and AIX operational, perform the following steps to install the FLASH code into your adapter. 

1) Log in as root 

2) Create a directory in /tmp using: 

mkdir /tmp/download 

3) Change directory to this newly created directory: 

cd /tmp/download 

4) Download and unpack the files into this directory, being careful to
     follow the RS/6000 microcode download procedure.

5) Change file permissions to allow their execution: 

chmod 777 *  

6) You are now ready to FLASH the EEPROM in the token ring adapter using the single command: 

./load  

NOTE: The update utility will automatically "walk the bus" searching all of the adapters installed in the system. It will FLASH them, one by one, until done. Since the utility tests, then flashes the adapter, and tests it again, it is not necessary to verify the adapter microcode level. However, if you would like to do so, follow the instructions in the previous section. The MicroCode level should read WW1AD0. 

This concludes the required hardware modification to enable the full duplex function on this adapter.  Now you must update your device driver by installing the appropriate APAR for the AIX level you are currently using. 

 Back to Contents 

APAR Information

The appropriate APAR should now be installed per standard AIX APAR installation procedures for the applicable operating system level. 
 
 
For AIX Level
Install APAR
4.1.5
IX73869
4.2.X
IX72837
4.3.X
IX72862
 
To begin using this new funciton, please reboot your system. 

 Back to Contents 

Important Information about Performance

While this new function for the MCA Token Ring Adapter provides the means for simultaneous data transfers to the local area network (LAN), it must be noted that the MicroChannel bandwidth is still the same. The adapter can communicate more efficiently to the LAN, but it must transfer the data via the same bus interface to the system. Therefore, not all applications can take advantage of this new optional function. Also, for optimal performance, if the adapter is expected to operate in a heavy load environment where a larger number of I/O's are being done to disk(s) and/or other adapter(s), it is recommended that the following system maximums be adhered to. 
 
Table 2.  Recommended Max No of Adapters per Machine Type (M/T)
M/T
Model
Performance
Connectivity
7012
ALL
2
4
7013
JXX
2 per bus
4 per bus
7013
ALL OTHER
4
8
7015
ALL
2 per bus
4 per bus
7030
ALL
2
4
 

In the table above, the Connectivity column specifies the number of adapters that are allowed in a given MicroChannel bus. The Performance column is the recommended maximum number of adapters for optimum system performance in heavy load environments. For machine types 7013 and 7015, these numbers are shown on a per bus basis because some models have more than one MicroChannel bus. 
 

Privacy | Legal | Contact IBM