Chapter 8
IBM 2108 R03 SAN Data Gateway Router

This information supports FC firmware for the IBM 2108 R03 SAN Data Gateway Router when installed on an IBM xSeries 430 or NUMA-Q server that is running a DYNIX/ptx V4.5.3 Operating System.


ATTENTION

In this documentation, the term "SDG Router" will stand for the formal name IBM 2108 R03 SAN Data Gateway Router.



8.1 New Release V3.42.12

The September 2001 release of V3.42.12 is the initial release of this firmware that is qualified for use on the DYNIX/ptx V4.5.3 Operating System.

This section contains the following information:


8.2 Feature Set At Initial Release

See the hard copy document Installation and User's Guide 2108 R03 that accompanies the SDG Router for detailed descriptions of the features and functions that are summarized in the following list:

The SDG Router is a "pass-through" device to the FC driver of the DYNIX/ptx operating system. The SDG Router will not be present in the operating system's naming database and will not appear in system listings such as dumpconf or showcfg. In a switched configuration, the tape subsystems connected to the Router will be listed as children of the fabric to which the Router is attached. In a direct configuration (two-node arbitrated loop), they will be listed as children of the FC Host Adapter to which the Router is directly attached.


8.2.1 Unused Features, Management Options, and Management Commands

When the SDG Router is used in an x430 or IBM NUMA-Q server system, certain options and certain management commands are not used nor supported, even though they may be documented in the accompanying hard copy manuals and readily available through the Ethernet and serial-port interfaces:


8.2.2 Standards Compliance

The FC interface of the SDG Router is compliant with the following standards:

Fibre Channel-PH, Rev.4.3, June 1, 1994
Fibre Channel AL-2, Rev. 6.4, Aug. 28, 1998
Private Loop (FC-PLDA, Rev 2.1, Sept. 22, 1997) Class 3
Public Loop (FC-FLA, Rev 2.7, Aug. 12, 1997) Class 3
SCSI-Fibre Channel P, Rev. 12, May 30, 1995

The SCSI interfaces of the SDG Router are compliant with the following standards:

ANSI T10/1071D Rev. 6, SCSI-3, Fast-20
ANSI T10/855D Rev. 15A, SCSI-3 Parallel Interfac
ANSI T10/375D Rev. 10t, SCSI-2

8.3 xSeries 430 and IBM NUMA-Q Compatibility

The SDG Router with V3.42.12 firmware is compatible with the following IBM xSeries 430 and NUMA-Q system elements:


8.4 Configuration Limits

  1. Maximum of two tape subsystems on each SCSI bus. In addition, one bus, but not both, can also support one robotic interface connection along with the tape loads.

  2. The SCSI targets cannot be set to SCSI ID 7. That ID is reserved for each of the SCSI ports on the SDG Router.

  3. Disk storage connections are not supported. In an xSeries 430 or IBM NUMA-Q system, the SDG Router is meant to support only DLT8000, DLT7000E, and DLT7000 tape subsystems that require a SCSI interface.


8.5 Known Problems at Release

There are no known critical or severe problems reported against the V3.42.12 firmware when used in the DYNIX/ptx V4.5.3 Operating System.


8.6 Install SDG Router Software on the Host

The software can be installed at anytime.

Use the distribution CD-ROM labeled "DYNIX/ptx V4.5.3 OS and LP Software, Volume 1, 09/01."

  1. Insert the distribution CD-ROM into the CD-ROM drive in the Bootbay connected to quad0 of the host system.

  2. Log into the host as root.

  3. Use the ptx/ADMIN menu system and the ptx/INSTALL utility to load the "FC Bridge IBM 2108R03 FW V3.42.12" software file into the /usr/ssw/fw/fc_bridge/ibm2108r03 directory.

  4. Remove the distribution CD.


8.7 Download to SDG Router Firmware


8.7.1 Required System Information

Before starting the downloading procedure, gather the following information:


8.7.2 Stop all I/O to Devices Connected to the Target SDG Router

  1. For switched-fabric installations, obtain device name information from the target SDG Router about all of its attached devices.

    1. From a telnet session to the SDG Router to be upgraded, determine the port of the FC Switch to which the Router is attached by using the fcLoopReport command:

      sdgr4 > fcLoopReport
      ----------------------------------------------------
      Fibre Channel Controller 1
      ----------------------------------------------------
      Port ID: 0x210513

      In the Port ID listing, the fifth digit from the right identifies the switch domain ID and the third digit from the right identifies the port number of the switch to which the SDG Router is connected. In this example, the Router is connected to port 5 of the switch having the domain ID of 1. The domain ID is useful to determine to which switch of a cascade the Router is cabled.

    2. From the system console, use the DYNIX/ptx dumpconf -m command to return system information about the devices connected to the switch port to which the SDG Router is attached. In the example, you want to determine the names of the tl and mw devices associated with switch port 5.

      $ /etc/dumpconf -m | grep 0x210513
      mw0:mw:0:-:0x2105130000000000000100:-:-:SX:fcp:fabric0
      tl3:tl:3:?:0x2105130000000000000600:-:-:SX:fcp:fabric0
      tl4:tl:4:?:0x2105130000000000000800:-:-:SX:fcp:fabric0
      

      This example shows that the devices mw0, tl3, and tl4 are connected to the SDG Router connected to switch port 5.

      If you have not already obtained the name of the fabric containing the SDG Router, note the name from the dumpconf output.

  2. For loop-fabric installations, use the DYNIX/ptx dumpconf -m command to return information about the devices attached to the SDG Router to be upgraded:

    1. For loop-fabric installations, use the DYNIX/ptx dumpconf -m command to return information about the devices attached to the SDG Router.

      The following example assumes that the SDG Router is part of fabric6. This information could be obtained from a system map or cabling labels.

      $ /etc/dumpconf -m | grep fabric6
      fabric6:fabric:6:-:-:0:0x10000000000000000:SMX:fc:ff4:+fabric3
      tl2:tl:2:?:0xef0000000000000400:-:-:SX:fcp:fabric6:+tl0
      tl3:tl:3:?:0xef0000000000001400:-:-:SX:fcp:fabric6:+tl1
      

      This output indicates that the SDG Router is connected to FC host adapter ff4 and that the tl2 and tl3 devices are connected to the SDG Router.

  3. From the system console, stop all I/Os and deconfigure the existing devices already connected to the SDG Router with the following method:

    1. At the application level, deactivate or deconfigure the tl tape devices and mw library on the SDG Router from backup-software products such as the SAMS:Alexandria product. Additionally, you must stop all processes associated with any affected devices. In some cases, this could require stopping the backup application.

      For details related to SAMS:Alexandria, refer to "SAMS:Alexandria Tasks for Tape Drive Replacement" under "Configure Backup Devices" in the online document Backup Toolkit Administration for SAMS:Alexandria.

    2. At the device-level, deconfigure the tl tape devices and mw library that are connected to the SDG Router. Record the original configuration names.


      ATTENTION

      Except for DLT8000, DLT7000 and DLT7000E tape drives, most tape devices and media changers have no UUIDs, so upon a reconfiguration probe the system cannot identify those kinds of devices as pre-existing. Unless instructed otherwise, it will assign these kinds of devices the next available, unused configuration numbers instead of the original ones. Applications, such as backup software and cron files that already knew these devices by their original names, would not be able to find them anymore.

      Therefore, use the -d option combined with the -D option in the devctl command to both deconfigure a given device and to delete its original name from the database, thus making the original name eligible for reuse. After the reconfiguring probe at the end of this replacement procedure, the temporary names for the "new" tape devices can be reassigned to their previous names so that applications can continue to find and use them.


      Use the devctl -d command to deconfigure each device. For example:

      $ devctl -d tl3
      $ devctl -d tl4
      $ devctl -d -D mw0


8.7.3 Download the New Firmware


ATTENTION

In the following instruction example, the name "Router4" will be used to identify the target SDG Router to be upgraded. In practice, substitute the actual Router name assigned at installation time.


The following procedure is performed from the VCS console command-line interface (CLI) window of the host system and a telnet window.

  1. Open a telnet session to the SDG Router to be upgraded. Use this window to monitor the progress of the downloading and relocation processes.

    $ [Host_name]/usr/ssw/fw/fc_bridge/ibm2108r03> telnet Router4
    Connected to Router4
    Escape character is '^]'
    SAN Router
    login: username
    Password: password
    Router4>

  2. From the CLI window, make sure that you are in the directory containing the software file and then invoke the ftp utility.

    $ cd /usr/ssw/fw/fc_bridge/ibm2108r03
    $ [Host_name]/usr/ssw/fw/fc_bridge/ibm2108r03> ftp
  3. Open the Router, using the username and password previously established:

    ftp> open Router4
    Connected to Router4
    220 VxWorks FTP server (VxWorks 5.3.1) ready.
    Name (Router4): username
    331 Password required
    Password: password
    230 User logged in
    Remote system type is UNIX
    Using binary mode to transfer files
    ftp>

  4. Make sure that the file transfer mode is set to binary:

    ftp> bin
    200 Type set to 1, binary mode
    ftp>

  5. Use the put command to transfer the file from the "local" host directory to the "remote" flash memory of the Router. The first argument to the put command is the file name on the local host. The second argument is the file name for the remote machine.

    The filename in the second argument requires a certain string prepended to it: fwl/. This string tells the Router to direct the firmware file to a preprocessor routine, which strips out the embedded files and locates them properly. Even though the ftp prompt returns, the utility could be busy for up to 30 seconds while the Router processes these files.


    ATTENTION

    Do not interrupt the download during this time. Interrupting the relocation process can disable the Router and require a total reinstallation beginning with initializing the box and redoing all installation configuration steps.


    ftp> put v034212.bin fwl/v034212.bin
    local: v034212.bin  remote: fwl/v034212.bin
    200 Port set okay
    150 Opening BINARY mode data connection
    .
    .
    226 Transfer complete
    1069056 bytes sent in 10 secs (1e+02 Kbytes/sec)
    .
    .
    .
    ftp>
    
  6. When the ftp prompt returns, exit the utility. The host prompt will not return until the downloaded files are properly relocated by the Router. This process could take more than 60 seconds to complete.

    ftp> bye
    .
    .
    .
    $ [Host_name]/usr/ssw/fw/fc_bridge/ibm2108r03>

  7. From the telnet session, reboot the Router to make the new firmware effective.

    Router4> reboot

    During the reboot of the SDG Router, the telnet session will likely timeout.

  8. When the SDG Router reboot has completed and the front-panel Ready light is blinking steadily, reestablish a telnet session and verify that the version of operating firmware is the correct one.

    $ [Host_name]/usr/ssw/fw/fc_bridge/ibm2108r03> telnet Router4
    Connected to Router4
    Escape character is '^]'.
    SAN Router
    login: username
    Password: password
    Router4>
    Router4> version
    SAN Router Version 0342.12 Built June 18 2001, 15:19:46
    VxWorks (for Pathlight (i960RD)) version 5.3.1
    Kernel: WIND version 2.5
    
    value = 26 = 0x1a
    Router4>
    
    

  9. At the application level, reactivate or reconfigure any tape drives and libraries that were deconfigured from backup-software products such as the SAMS:Alexandria product. Restart the backup application after reconfiguring the devices.

This completes the firmware download procedure.