INSTALLATION OF THE ESCON (PBSA Adapter) PCI FIRMWARE v3.0 Minimum Requirements -------------------- 1.1 The following are the minimum required levels of Channel Drivers required to use this firmware release. ***CAUTION*** Do NOT install this firmware unless you are at these levels, or higher. Novell NetWare: APCA Channel Drivers Version 5.5.0 Microsoft Windows NT: NT Channel Drivers Version 5.5.0 Microsoft Windows 2000: Win2000 Channel Drivers Version 6.1.0 UnixWare: UnixWare Channel Drivers Version 5.5.0 Installation on Novell NetWare Servers -------------------------------------- 2.1 If you are running any Netware NLM's that use the ESCON Adapter, please unload them first before proceeding. If you are running NetWare for SAA, type SAADOWN, CHLDOWN, and then CSDOWN. For TCP/IP Pass-Through, just type CHLDOWN. 2.2 At the Netware Console prompt (:) type LOAD PBXAAPI . The PBXAAPI.NLM will be loaded. 2.3 At the Netware Console prompt (:) type LOAD CHLTOOL . The CHLTOOL NLM will be loaded. 2.4 At the Netware Console prompt (:) type CHLTOOL . The screen will clear and the CHLTOOL> prompt will appear. 2.5 Insert a floppy disk or CD that contains the firmware file named "PBSA.HEX". 2.6 Identify current firmware version and, which ODI slot the ESCON adapter is in, as follows. At the CHLTOOL> prompt type the following line: SHOW ALL Verify the firmware version is indeed downlevel before continuing. NOTE: Slot number can be omitted in the following steps if only one ESCON adapter is in the system. 2.7 At the CHLTOOL> prompt type the following line: LOAD FIRMWARE D:\FIRMWARE\PBSA.HEX SLOT=x (where (x)=the ODI slot number from above) When loading completes (several seconds), the console will display the CHLTOOL command prompt. Repeat this process for each ESCON adapter (ODI slot number) needing this maintenance update. 2.8 Type EXIT to exit CHLTOOL. 2.9 You must now DOWN the SERVER, EXIT to the DOS prompt, and perform a Hardware REBOOT on the SERVER for the changes to take effect. Installation on Microsoft Windows 2000 Servers ---------------------------------------------- 3.1 If you are running Microsoft SNA Server, or IBM Communications Server for Windows NT, stop the SNA Service. 3.2 If you are running a TCP/IP Direct Connect driver, shut down any upper layer applications which may be using the TCP/IP Direct Connect host IP link. Open COMPUTER MANAGEMENT, select the DEVICE MANAGER display, right click and disable each of the TCP/IP Direct Connect devices. 3.3 From an MS-DOS CMD Prompt, change to the directory C:\CHANNEL. 3.4 At the MS-DOS CMD prompt, type: CHLTOOL . The screen will clear and the CHLTOOL> prompt will appear. 3.5 Identify current firmware version and, which encoded slot the ESCON adapter is in, as follows. At the CHLTOOL> prompt type the following line: SHOW ALL Verify the firmware version is indeed downlevel before continuing. NOTE: Slot number can be omitted in the following steps if only one ESCON adapter is in the system. 3.6 Insert the CD (or floppy disk) that contains the firmware file named "PBSA.HEX". 3.7 At the CHLTOOL prompt (>) type the following line: LOAD FIRMWARE D:\FIRMWARE\PBSA.HEX SLOT=x where (x)=the Slot Number of the PBSA Card you wish to load. When loading is complete the console will display the CHLTOOL command prompt. Repeat this process for each ESCON adapter (ENCODED slot number) needing this firmware update. 3.8 Type EXIT to exit CHLTOOL. 3.9 If you were running a TCP/IP Direct Connect driver and disabled it in step 3.3 above, open COMPUTER MANAGEMENT, select the DEVICE MANAGER display, right click and enable each of the TCP/IP Direct Connect devices. 3.10 You must now ShutDown the SERVER and perform a hardware REBOOT on the SERVER for the changes to take effect. Installation on Microsoft Windows NT Servers -------------------------------------------- 4.1 If you are running Microsoft SNA Server, or IBM Communications Server for Windows NT, stop the SNA Service. 4.2 If you are running TCP/IP Pass-Through, open the CONTROL PANEL, open the DEVICES icon, arrow down the list to TCP/IP Pass-Through, click the STOP button. The TCP/IP Pass-Through device should stop. 4.3 If you are running a TCP/IP Direct Connect driver (or VPPA), open the CONTROL PANEL, open the DEVICES icon, arrow down the list to TCP/IP Direct Connect (or VPPA), click the STARTUP button, select the DISABLED box, click OK, and then click CLOSE. Shut down and REBOOT the SERVER. NOTE - Attempting to STOP the TCP/IP Direct Connect (or VPPA) driver (rather than DISABLE it) will result in an error condition, and is not recommended. 4.4 From an MS-DOS CMD Prompt, change to the directory C:\CHANNEL. 4.5 At the MS-DOS CMD prompt, type: CHLTOOL . The screen will clear and the CHLTOOL> prompt will appear. 4.6 Identify current firmware version and, which encoded slot the ESCON adapter is in, as follows. At the CHLTOOL> prompt type the following line: SHOW ALL Verify the firmware version is indeed downlevel before continuing. NOTE: Slot number can be omitted in the following steps if only one ESCON adapter is in the system. 4.7 Insert the CD (or floppy disk) that contains the firmware file named "PBSA.HEX". 4.8 At the CHLTOOL prompt (>) type the following line: LOAD FIRMWARE D:\FIRMWARE\PBSA.HEX SLOT=x where (x)=the Slot Number of the PBSA Card you wish to load. When loading is complete the console will display the CHLTOOL command prompt. Repeat this process for each ESCON adapter (ENCODED slot number) needing this firmware update. 4.9 Type EXIT to exit CHLTOOL. 4.10 If you were running a TCP/IP Direct Connect (or VPPA) driver and disabled it in step 3.3 above, open the CONTROL PANEL, open the DEVICES icon, arrow down the list to TCP/IP Direct Connect (or VPPA), click the STARTUP button, select the AUTOMATIC box, click OK, and click CLOSE. 4.11 You must now ShutDown the SERVER and perform a hardware REBOOT on the SERVER for the changes to take effect. Installation on SCO UnixWare 7 Servers -------------------------------------- 5.1 If you are running IBM Communications Server for UnixWare 7, stop the SNA Service. 5.2 Mount the CD or floppy that contains the firmware file. 5.3 Type /opt/channel/chltool . The CHLTool> prompt will appear. 5.4 Identify current firmware version and, which encoded slot the ESCON adapter is in, as follows. At the CHLTool> prompt type the following line: show all Verify the firmware version is indeed downlevel before continuing. NOTE: Slot number can be omitted in the following steps if only one ESCON adapter is in the system. 5.5 At the CHLTool prompt (>) type the following line: load firmware /pbsa.hex slot=x where (x)=the Encoded Slot Number of the PBSA Card you wish to load. When loading is complete the console will display the CHLTOOL command prompt. Repeat this process for each ESCON adapter (ENCODED slot number) needing this firmware update. 5.6 Type exit to exit CHLTOOL. 5.7 Reboot the UnixWare system or type /opt/channel/chlinit to reboot the firmware and reload the ESCON configuration. PBSA Diagnostic Utilities ------------------------- 6.1 PBSAUP.EXE - Used to gather traces and memory contents from the PBSA, and save it to a DOS file. Execute this file on a DOS PC that is connected, through a Null Modem Cable to the DB9 connector on the PBSA Board. Type PBSAUP for help on this utility. 6.2 PBSADOWN.EXE - Used to transfer data from a DOS file to the PBSA. Normally used for download of new Emulation Firmware. Execute this file on a DOS PC that is connected, through a Null Modem Cable to the DB9 connector on the PBSA Board. Type PBSADOWN for help on this utility. 6.3 FIRMWARE TRACES - Occasionally you may be directed by a Product Support Engineer to retrieve an internal trace of activities in the ESCON board. Traces are retrieved via a PC connected to the DB9 connector on the PBSA Board using a null modem cable. The syntax of the MS-DOS command to upload the trace table is: PBSAUP filename 1000088c 10000 - where filename is the name of the target file to be created on the connected PC. (i.e. PBSATRC1.TRB) The Trace File that is uploaded is a binary trace file. It must be formatted using the MS-DOS Utility BTIFMT.EXE which is supplied with this release. 6.4 BOARD DUMP - You may be directed by Pruduct Support to retrieve all of the internal structures needed to diagnose a problem. This information is retrieved via a PC connected to the DB9 connector on the PBSA Board using a null modem cable. The syntax of the MS-DOS command to upload the trace table is: PBSAUP DMPPBSA.LIS :where DMPPBSA.LIS is a data file supplied with this release. It contains a list of files that will be created as a result of running this command (all files will have a .MEM extension). The file also contains the start address of each memory region, and the number of bytes to dump. All of the .MEM files created should be passed to Product Support for analysis. For NT system users, there is a batch file that can be run on the NT server which uses CHLTOOL to obtain this same information. This does not require a separate PC or a serial port connection. The batch file requires 2 command line parameters when run. The first parameter is the path of where to place the files created. The second parameter is the slot number of the board. The batch file can be run from an MS-DOS prompt window and the syntax is: DMP_PBSA directory slot_number An example using this to dump the data to a floppy in drive A, for a board in slot number 196619 would be: DMP_PBSA a: 196619 This will create several .MEM files, and save a firmware trace to a .TRB file. All of these files should be passed to Product Support for analysis. ADDITIONAL NOTES ---------------- For optimum performance, you should always ensure that the Channel Drivers running on your Server are at the most current revision level. ***End of README.TXT***