IBM 7036-P16 User manual

Machine Type Model 7036-P16 LAN attached remote Asynchronous node (RAN) (FC xxxx)
The 7036-P16 is a 16-Port EIA-232 LAN Attached Remote Asynchronous Node (RAN) for use with IBM®eServer™ p5 servers
andIBM Systems. The RAN provides connectivity to asynchronous EIA-232 devices, such as modems, TTY terminals, printers, etc.
The RAN, when used with RealPort® software from Digi-Data Corporation, will convert the serial data stream to and from attached
asynchronous EIA-232 devices into Ethernet TCP/IP traffic. Once the data is on the TCP/IP network, a host system attached to the
same network can treat the attached devices as if the devices were connected directly to the host system.
7036-P16 RAN attached remote asynchronous node specifications
Item Description
Physical Dimensions:
42.7 cm (16.8 in.) x 16.76 cm (6.6 in.) x 4.06 cm (1.6 in.)
Weight: 3.2 kg (7.05 lb.)
Environmental Limits
Operating
•Temperature: 0 to 40 C (Ambient Air Temperature)
•Humidity: 5% to 95% (non-condensing)
•Wet Bulb: 29 C
•Altitude: 0 - 7000 ft
Storage
•Temperature: 1 to 60 C
•Humidity: 5% to 80% (non-condensing)
•Wet Bulb: 29 C
Shipping
•Temperature: -40 to 60 C
•Humidity: 5% to 100% (non-condensing)
•Wet Bulb: 29 C
Power Consumption Table
Voltage Current (amperes) Wattage
Input •100 - 250VAC nominal
•90 - 264VAC maximum
•47 - 63 Hz
•0.8 A Maximum
•40A in rush
•2A fuse
12 watts typical
7036-P16 throughput considerations
The limits on throughput are a function of the network and the server or server partition to which the 7036-P16 ports are configured.
Serial Port Throughput:

The 7036-P16 supports full-duplex operation up to 230K bps for any one port running, with the other fifteen ports running at
speeds not to exceed 115K bps. Operation with all sixteen ports running full-duplex at 115K bps is supported.
Network Throughput:
The 7036-P16 is an Ethernet attached device and as such any number may be attached to given network. However, the user
must realize that attaching more devices to any network reduces the overall network throughput and care must be taken to not
overload any given network.
Testing has shown that as many as eight 7036-P16 devices may be attached to a network without adversely affecting network
throughput. More devices may be attached, but network performance may be adversely affected.
Server Throughput:
Each 7036-P16 provides 16-Ports of asynchronous EIA-232 connectivity over a 10/100 Ethernet port at speeds up to 128 K
bps. Given that any number of 7036-P16 may be attached to a server, a single server, or server partition could in effect have a
large number of asynchronous EIA-232 connections. The user is cautioned that increasing the number of asynchronous EIA-
232 connections beyond 128 is not recommended.
7036-P16 Hardware installation instructions
•Install the 7036-P16 as a rack device.
•Install the 7036-P16 as a desk top device.
Package contents:
•7036-P16
•7036-P16 Software and Documentation CD.
•7036-P16 Quick Setup Guide.
•Brackets to mount 7036-P16 on rack.
•Rubber feet for table top usage.
•Power cord (North American 120 VAC use only).
•RJ45 to DB25 Serial Cable (DB25 wired per EIA-232 Specification).
•RJ45 to DB09 Serial Cable (DB09 matches pin configuration on existing DB09 serial ports on pServers).
•RJ45 Wrap Plug for Diagnostics.
Tools:
Phillips Head Screwdriver
Desk top installation procedure:
1. Unpack hardware.
2. Remove the rubber feet from the packaging.
3. Attach the rubber feet to the bottom of the 7036-P16 in the spots indicated.
4. Attach the power cord. A power cord for use in North America is provided.
5. Use an Ethernet cable to connect the 7036-P16 to the network.
6. Connect serial devices as needed.
Rack mount installation procedure:
1. Unpack hardware.
2. Remove the right angle brackets and screws from the packaging.
3. Use a Phillips head screw to attach the brackets in the pre-drilled holes on the sides of the 7036-P16.
4. Attach the power cord. A power cord for use in North America is provided. Attach the power cord. A power cord for use with
120 VAC is provided. Optional rack power cord feature codes (FC) are available to connect the 7036-P16 to the rack Power
Distribution Unit (PDU). These come in various lengths and may be purchased from IBM as the following features codes:
oFC 6458: Power Cord (14-foot), Drawer to IBM PDU, 250V/10A.
oFC 6672: Power Cord (9-foot), Drawer to IBM PDU, 250V/10A
oFC 6671: Power Cord (5-foot), Drawer to IBM PDU, 250V/10A (Only available for use in racks less than 25U)
5. Use an Ethernet cable to connect the 7036-P16 to the network.
6. Connect serial devices as needed.

7036-P16 Software Installation and Configuration Instructions
The following tasks are covered in this section:
•Install the Digi RealPort® software on the host server from the software packages on the 7036-P16 Software and
Documentation CD that was provided with the product.
•Configure the 7036-P16 as a device on the host server. This in effect binds the 7036-P16 to the host server.
•Configure the 7036-P16 serial ports for use with the Digi RealPort® software.
Software Packages on the 7036-P16 Software and Documentation CD
The following packages are included on the Software and Documentation CD:
•RealPort® Software for AIX Package: 40001927_A.bin
•RealPort® Software for Linux Package: 4002086_k.src.rpm
AIX Levels Supported:
•AIX 5L 5.2.0.75 (and later)
•AIX 5L 5.3.0.30 (and later)
Linux Levels Supported:
•Linux for Power Red Hat Version ______
•Linux for Power SuSE Version _____
Recommended Order of Installation for the RealPort® Software:
1. Install all updates and packages required to bring the operating system to the supported levels (strongly recommended).
2. Install all Linux packages required to compile and create binaries from the RealPort® Software for Linux source code
(strongly recommended). List of Linux Packages that are required to install the RealPort software:
ogcc
ogcc-64bit
ogcc-c++
ogcc-g77-64bit
ogcc-info
ogcc-locale
ogcc-objc
ogcc-objc-64bit
okernel
osources
oglibc-devel-64bit
oncurses-64bit ncurses-devel
3. Install the RealPort® Software.
AIX Installation Procedure
1. Login as root.
2. Insert the 7036-P16 Software and Documentation CD into the CD-ROM drive.
3. Type: smitty install_all.
4. Press: F4.
5. Select: CD-ROM driver and press Enter.
6. Press: F4.
7. Select: digiasync and press Enter.
8. Use the cursor to scroll to ACCEPT new license agreement.
9. Press: F4.
10. Select: Yes and press Enter.
11. Press Enter.
12. Press Enter.

The installation begins, do not interrupt process until the installation is complete. A successful installation returns an OK
message. An unsuccessful installation returns a FAILED message. If the installation fails, study the smit.log file to determine
the cause.
13. Press: F10.
14. After the RealPort® software is successfully installed, the user should configure the 7036-P16 IP address, 7036-P16 Network
Configuration.
Linux SuSE Installation Instructions
These steps move the rpm source file from the 7036-P16 Software and Documentation CD to the server.
1. Login as root.
2. If the 7036-P16 Software and Documentation CD is already inserted and mounted, then proceed to 5.
3. Insert the 7036-P16 Software and Documentation CD into the CD-ROM drive.
4. Type: mount -t auto /dev/cdrom /mnt .
5. This step displays the name of the RealPort® rpm file, which is 40002086_K.src.rpm
Type: ls -l /mnt/linux.
6. Type: cp /mnt/linux/40002086_K.src.rpm /usr/src/packages/SOURCES.
7. Type: umount /mnt .
8. The next steps are required to prepare for the rpmbuild.
Type: uname -a.
This causes the kernel level to be displayed, which is needed in the next step.
9. Type: cd /usr/src/linux <kernel level>.
10. Type: make mrproper.
11. Type: make oldconfig.
12. The next steps perform the rpmbuild.
Type: cd /usr/src/packages/SOURCES.
13. Type: rpmbuild --rebuild 40002086_k.rpm .
14. Type: rpm -i /usr/src/packages/RPMS/ppc64/dgrp-1.9-1.ppc64.rpm.
15. Type: rpm -qa | grep dgr
If the RealPort® Package installed correctly the following is displayed: dgr-1.9.1 .
Once this step is done successfully, the RealPort® installation on SuSE is complete.
16. After the RealPort® software is successfully installed, the user should configure the IP address, go to 7036-P16 IP address,
7036-P16 Network Configuration.
Linux Red Hat Installation Instructions
1. Login as root
2. If the 7036-P16 Software and Documentation CD is already inserted and mounted, then proceed to 5.
3. Insert the 7036-P16 Software and Documentation CD into the CD-ROM drive.
4. Type: mount -t auto /dev/cdrom /mnt
5. Type: ls -l /mnt/linux
This step should reveal the name of the RealPort® rpm file, which should be: 40002086_k.src.rpm
6. Type: cp /mnt/linux/40002086_k.src.rpm /usr/src/packages/SOURCES
7. Type: umount /mnt

8. The next steps perform the rpmbuild.
Type: cd /usr/src/packages/SOURCES
9. Type: rpmbuild --rebuild 40002086_k.rpm
10. Type: rpm -i /usr/src/packages/RPMS/ppc64/dgrp-1.9-1.ppc64.rpm
11. Once this step concludes successfully, the RealPort® installation on Red Hat is complete.
12. After the RealPort® software is successfully installed, the user should configure the IP address, go to 7036-P16 IP address,
7036-P16 Network Configuration.
7036-P16 Network Configuration
This section provides the following:
•Brief discussion of the three principal network configuration methods.
•How to configure the 7036-P16 onto an Ethernet network.
The 7036-P16 is an Ethernet device and as such it must be configured onto the network like any other Ethernet device. Various
network configuration methods are available to the user. The three principle methods are briefly described below.
Dynamic Host Configuration Protocol (DHCP):
The 7036-P16 is configured for DHCP at the factory. If the 7036-P16 is being attached to a network which employs DHCP,
then simply connecting to the network and powering up the will configure the 7036-P16 and the configuration task is
completed. This method is by far the simplest to use, but the 7036-P16 must be connected to a network that supports DHCP.
Ping-ARP:
The address Resolution Protocol (ARP) ties the MAC address from any network device to a unique IP address for that device
on a server. The MAC address and the IP address are kept by each server in an ARP Table. To use this method the user must
manually update the server's ARP Table with the 7036-P16's MAC address and the IP address being assigned to the 7036-
P16. The user would then use this IP address to ping the 7036-P16 and then telnet to the 7036-P16 to complete the
configuration. This method does not require the user to be in the same room as the 7036-P16. This method works equally
well for AIX and Linux installations. This method does not require the 7036-P16 be connected into a network that supports
DHCP.
Direct Terminal Attach:
A regular TTY Terminal or a PC running a terminal emulation program, may be attached directly to any one of the sixteen
ports and commands entered on the 7036-P16 command line to configure the 7036-P16 onto the network.
This method requires the user to be in the same room as the 7036-P16.
This method requires the user to have a tty terminal or a PC available.
This method requires a serial cable to connect the tty terminal or PC to the server.
This method is independent of the operating system installed on the server.
Go to #fcERAN/IPconfigLinux
7036-P16 device IP configuration on an AIX host server
Before beginning this procedure, ensure that the 7036-P16 and the server are configured, attached to the network and the Digi
RealPort® software is installed on the server.
1. Ensure the 7036-P16 and the server are on the network. The user should ping the 7036-P16 by typing the following
command: ping -c 1 [IP address of target 7036-P16]
If the 7036-P16 responds to the ping, then it is on the network and the user may proceed to 2. If the 7036-P16 does not
respond to the ping, then the 7036-P16 is not on the network and the user must go to the 7036-P16 Network Configuration
procedure.
2. Ensure the Digi RealPort® Software is installed on the server. Type the following command lslpp -l | grep digi
The response should be:

digiasync.realport.obj 3.8.0.0 Committed Digi RealPort Driver
digiasync.realport.obj 3.8.0.0 Committed Digi RealPort Driver
If there is any other response, then the Digi RealPort® Software is not installed and the user should go to the AIX Installation
Procedure.
3. Type: smitty devices.
4. Use the cursor to select: Digi Device and Terminal Servers and press Enter.
5. Use the cursor to select: Add a Digi Device and Terminal Servers and press Enter.
6. Use the cursor to select: cts_16 and press Enter.
7. Move the cursor to the IP address box and type: [IP address] and press Enter. This is the IP address of the target 7036-
P16 used in 1.
When the command is entered, the user should see the following on the screen: Command: OK stdout: yes stderr: no
Note: Additional instructions might appear before the command is completed. Perform any instructions if needed. For
example, sa[device number] Available
8. Press F10 to exit from smitty. This concludes the device configuration portion of this process. Once the serial device is
configured, the tty ports need to be configured. Go to 7036-P16 Serial port TTY configuration on an AIX host server.
7036-P16 Serial port TTY configuration on an AIX host server.
This procedure assumes the target 7036-P16 and the server are configured, attached to the network and the Digi RealPort® software is
installed on the server.
1. Ensure the 7036-P16 and the server are on the network. The user should ping the 7036-P16 by typing the following
command: ping -c 1 [IP address of target 7036-P16]. If the 7036-P16 responds to the ping, then it is on the network, go
to 2.
If the 7036-P16 does not respond to the ping, then the 7036-P16 is not on the network and the user must go to the7036-P16
Network Configuration procedure to perform the network configuration.
2. Insure the Digi RealPort® Software is installed on the server. Type the following command lslpp -l | grep digi
and press Enter.
The response should be: digiasync.realport.obj 3.8.0.0 Committed Digi RealPort Driver digiasync.realport.obj 3.8.0.0
Committed Digi RealPort Driver. If there is any other response, then the Digi RealPort® Software is not installed and the
user should go to the AIX Installation Procedure.
3. Type: smitty devices.
4. Use the cursor to select: Add a TTY and press Enter.
5. Use the cursor to select: tty rs232 Asynchronous Terminal
6. Use the cursor to select: sa[device number] Available Digi PortServer TS 16 and press Enter.
7. Enter a port number not already assigned to a tty, for example 1, and press Enter. Upon successful completion of this
command the user should see the following on the screen:
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear. tty[number available]
Note: The [number] is the number assigned by smitty as the next available tty device.
8. Press F10 to exit from smitty.
This concludes the serial port tty configuration on an AIX server.
Configuring the 7036-P16 as a TTY device on a Linux host server

This procedure assumes the target 7036-P16 and the server are configured, attached to the network and the Digi RealPort® software is
installed on the server.
1. Ensure the 7036-P16 and the server are on the network, the user should ping the 7036-P16 by typing the following command:
ping -c 1 [IP address of target 7036-P16]. If the 7036-P16 responds to the ping, then it is on the network
and the user may proceed to 2. If the 7036-P16 does not respond to the ping, then the 7036-P16 is not on the network and the
user must go to the 7036-P16 IP address Configuration Procedure to perform the network configuration procedure.
2. Insure the Digi RealPort® Software is installed on the server. Type: rpm -qa | grep dgr. The response should be: dgr-
1.9.1. If there is any other response, the Digi RealPort® Software is not installed and the user should go to either the Linux
Red Hat Installation Instructions or the Linux SuSE Installation Instructions.
3. Type: dgrp_cfg_node -v init [Device ID] [IP address] [7036-P16 Port(s)] Where: [Device ID] is any two characters
that the user may wish to use to identify the target 7036-P16 [IP address] is the IP address of the target 7036-P16. [7036-P16
Port(s)] is the port number(s) being configured.
Configuration Methods Considerations
If the 7036-P16 is to be used in a network that supports Dynamic Host Configuration Protocol (DHCP), then the configuration will be
performed by simply connecting to the network and powering up the 7036-P16. The 7036-P16 is shipped from the factory with the
DHCP option enabled. If DHCP is not supported on the network, then the user must choose between the ARP-Ping Configuration or
the Direct Terminal Attach methods. The ARP-Ping Configuration method is recommended for the following reasons:
•This method does not require the user to be in the same room as the 7036-P16.
•This method does not require any extra hardware, such as a tty terminal or cabling to attach the 7036-P16 to the tty terminal.
•This method works equally well for AIX and Linux installations.
•This method does not require the 7036-P16 be connected into a network that supports DHCP.
ARP-Ping Network Configuration Method
1. Gather the following information:
oMAC address: [MAC address] (see the MAC address label on the 7036-P16)
oIP address: [IP address]
oDefault gateway: [IP gateway address]
oName server: [name server address]
oSubnet mask: [subnet mask]
oHost name: [host name]
oDomain name: [domain name]
2. Connect the power cord from the 7036-P16 to a power source and power up.
3. Connect the Ethernet cable from the 7036-P16 to an Ethernet network.
4. Login into a server as root, make sure the server is on the same subnet as the 7036-P16.
5. Manually update the server's ARP table. Use the IP address and the 7036-P16's MAC address gathered in 1.
The AIX and the Linux command line entries to update the ARP table are different, use the following examples for reference
when you need to update the server's ARP table:
AIX command: arp -s ether [IP address] [MAC address]
Linux Command:arp -v -H ether -s [IP address] [MAC address]
6. Send a ping command to the 7036-P16 using the IP address. ping -c 1 [IP address]
The ping may time out before there is a response from the 7036-P16. Repeat the ping command until the 7036-P16 responds.
The ping response indicates that the IP address has been configured.
7. Telnet to the 7036-P16, use the IP address from the ping command. telnet [IP address]
8. Login to the 7036-P16 as root, use the default password dbps.
9. After login, the user may choose to change the root password. Type: newpass and follow the prompts.
10. Type: set config and press enter. This allows the user to view the current configuration.
11. Type the following commands on the 7036-P16 command line using the information gathered in 1to complete the IP address
configuration.
oset config ip=[IP address]
oset config submask=[subnet mask]

oset config gateway=[IP gateway address]
oset config dns=[name server address]
oset config dhcp=off
oset config hostname=[host name]
oset config domain=[domain name]
12. As a precaution, the user may choose to deactivate the Ping-ARP and RARP options. To deactivate the Ping-ARP and RARP
options type the following commands:
oset config Ping-ARP=off
oset config RARP=off
13. If the user plans to use the RealPort® software on the host server to control all the 7036-P16 ports, then the serial ports must
be configured for use with the RealPort® software by executing the following command.
oset port range=* dev=rp
14. Type: boot action=reset
15. After the 7036-P16 reboots, the network configuration is complete.
The 7036-P16 may now be accessed through the Ethernet connection. The user can program other features as required. See additional
documentation on the 7036-P16 Software and Documentation CD that was provided with the product.
Direct Attach Configuration Method
1. Gather the following information:
oMAC address: [MAC address] (see the MAC address label on the 7036-P16)
oIP address: [IP address]
oDefault gateway: [IP gateway address]
oName server: [name server address]
oSubnet mask: [Subnet mask]
oHost name: [host name]
oDomain name: [domain name]
2. Connect the power cord from the 7036-P16 to a power source and turn on the power.
3. Connect the serial cable from TTY terminal to the 7036-P16.
4. Login to the 7036-P16 as root, use the default password dbps.
5. After login, the user may choose to change the root pass word. Type: newpass and press Enter. Follow the prompts on your
display.
6. Type: set config This allows the user to view the current configuration.
7. Type the following commands on the 7036-P16 command line using the information gathered in 1to complete the IP address
configuration.
oset config ip=[IP address]
oset config submask=[subnet mask]
oset config gateway=[IP gateway address]
oset config dns=[name server address]
oset config dhcp=off
oset config hostname=[host name]
oset config domain=[domain name]
8. As a precaution, the user may choose to deactivate the Ping-ARP and RARP options. To deactivate the Ping-ARP and RARP
options type the following commands:
oset config Ping-ARP=off
oset config RARP=off
9. If the user plans to use the RealPort® software on the host server to control all the 7036-P16 ports, then the serial ports must
be configured for use with the RealPort® software by executing the following command:
oset port range=* dev=rp
10. Issue the reboot command to the 7036-P16 in order to permanently set the changes. Type: boot action=reset
11. After the 7036-P16 reboots, the network configuration is complete.
The 7036-P16 may now be accessed via the Ethernet connection. The user can program other features as required. See additional
documentation on the 7036-P16 Software and Documentation CD that was provided with the product.
7036-P16 firmware or POST upgrade instructions
Upgrades can be performed from the 7036-P16 command line or the web interface, using TFTP. This section provides instructions
about how to perform the following tasks:

•Upgrade the RealPort® firmware on the 7036-P16.
•Upgrade the RealPort® POST on the 7036-P16.
There are two methods for upgrading the firmware and POST. The user may chose to upgrade by entering commands directly on the
7036-P16 command line, or by using the 7036-P16 web interface.
Upgrading firmware using the command line:
Entering commands directly on the 7036-P16 command line requires the user to access the 7036-P16 command line by either
telneting to the 7036-P16 or by attaching a TTY terminal directly to the 7036-P16. A personal computer running a terminal
emulation program may be used instead of a TTY terminal. Once access to the command line has been established, the
upgrade procedure is essentially the same for either the Telnet or the Direct attach methods. The user is advised to use the
same access method that was used for the network and serial port configuration. The two command line access methods are:
•Command line method using a telnet connection.
•Command line method using a direct-attach device.
Upgrading firmware using the Web:
The web interface method takes advantage of the graphical user interface that is built into the 7036-P16. It requires the use of
a host sever with access to the Web.
Updating firmware using the command line and a telnet connection:
Gather the following information:
•IP address of target 7036-P16: [7036-P16 IP address]
•IP address of host server: [host server IP address]
•Root password of the target 7036-P16.
Hardware requirements:
•AIX or Linux host server with web access.
•7036-P16 fully configured and attached to an Ethernet network.
Do the following:
1. Telnet to the target 7036-P16 from the host server. telnet [7036-P16 IP address]
2. To determine the current firmware level type: set config. The firmware level is displayed on the first line in the response
to the set config command. Make a note of the response. For example: PortServer TS 16 Rack Version 82000684_L
07/08/2005 The firmware level in this example is: 82000684_L.
3. To determine the current POST level, type the following command: show boot. Make a note of the response, which has
the following form: Boot Revision 82000685_E 05/17/2004 . The POST level in this example is: 82000685_E
4. Exit from the target 7036-P16 by typing the following command: exit
5. The next steps are done to determine if the firmware and POST on the 7036-P16 need to be updated. Use the host sever to
access the following web site to check for the latest firmware and boot updates:
http://techsupport.services.ibm.com/server/mdownload/download.html
6. Click on Other Devices
7. Scroll to and click on LAN Attached RAN 16
8. Read the release notes to determine the latest levels of the firmware and POST available on this web site.
9. Compare the latest levels to what was found in steps 2and 3above.
10. If the firmware and POST versions are the same as what was found in steps 2and 3, then the firmware and POST on the
target 7036-P16 are current and nothing more needs to be done. Exit from this procedure by logging out from the IBM
Support Site.
11. If the latest firmware version is not the same as what was found in step 2, then the firmware on the target 7036-P16 is not
current and it needs to be updated. Download a copy of the latest firmware to a directory on the host server and make a note
of the directory and the file name. For example: /tmp/82000684_L.bin
12. If the latest POST version is not the same as what was uncovered in step 3, then the POST on the target 7036-P16 is not
current and it needs to be updated. Download a copy of the latest POST to a directory on the host server and make a note of
the directory and the file name. For example: /tmp/82000685_E.bin
13. Log out from the IBM Support site.
14. The next steps are done only if the firmware or POST needs to be updated. Telnet to the target 7036-P16.
15. Log into the 7036-P16 as root.

16. If the firmware needs to be updated, type the following command: boot load=[host server IP
address]:[/directory/firmware file name]
17. If the POST needs to be updated, type the following command: boot load-post=[host server IP
address]:[/Directory/POST file name]
18. Reboot the 7036-P16 in order for the changes to take effect. Type the following command: boot action=reset
This completes the Telnet method for upgrading the firmware and POST from the command line.
Updating firmware using command line and a direct-attach device
Gather the following information:
•IP address of target 7036-P16: [7036-P16 IP address]
•IP address of host server: [host server IP address]
•Root password of target 7036-P16.
Hardware requirements:
•AIX or Linux host server with web access.
•7036-P16 fully configured and attached to an Ethernet network.
•TTY Terminal or a PC running a terminal emulation program.
•A cable to connect the terminal to any one of the sixteen serial ports on the RAN.
oOne RJ45 to DB25 cable is included with the RAN. The DB25 is wired per the EIA-232 specification. Some
terminals or PCs may require an appropriate modem eliminator, which is not provided with the RAN.
oOne RJ45 to DB09 cable cable is included with the RAN. This cable is wired identically to the DB09 connector of
server serial ports. Some terminals or PCs may require an appropriate modem eliminator, which is not provided with
the RAN. With an appropriate modem eliminator, it may be used with a PC Laptop running the Netterm terminal
emulator software.
Do the following:
1. The next steps are done to determine if the firmware and POST levels on the 7036-P16. Attach the TTY terminal to the target
7036-P16.
2. To determine the current firmware level type: set config The firmware level is displayed on the first line in the response
to the set config command. Make a note of the response. For example: PortServer TS 16 Rack Version 82000684_L
07/08/2005. The firmware level in this example is: 82000684_L.
3. To determine the current POST level, type the following command: show boot Make a note of the response, which has the
following form: Boot Revision 82000685_E 05/17/2004. The POST level in this example is : 82000685_E. The next steps are
used to determine if the firmware and POST on the 7036-P16 need to be updated.
4. Use the host sever to access the following web site to check for the latest firmware and boot updates:
http://techsupport.services.ibm.com/server/mdownload/download.html
5. Click on Other Devices
6. Scroll to and click on LAN Attached RAN 16
7. Read the release notes to determine the latest levels of the firmware and POST available on this web site.
8. Compare the latest levels available on this web site to what was uncovered in steps 2and 3above.
9. If the firmware and POST versions, available on this web site, are the same as what was uncovered in steps 2and 3, then the
firmware and POST on the target 7036-P16 are current and nothing more needs to be done. Exit from this procedure by
logging out from the IBM Support Site.
10. If the firmware version is not the same as what was found in step 2, then the firmware on the target 7036-P16 is not current
and it needs to be updated. Download a copy of the firmware to a directory on the host server and make a note of the
directory and the file name. For example: /tmp/82000684_L.bin
11. If the POST version is not the same as what was found in step 3, then the POST on the target 7036-P16 is not current and it
needs to be updated. Download a copy of the POST to a directory on the host server and make a note of the directory and the
file name. For example: /tmp/82000685_E.bin
12. Log out from the IBM Support site.
13. The next steps are done only if the firmware or POST needs to be updated. If the firmware needs to be updated, type the
following command: boot load=[host server IP address]:[/directory/firmware file name]
14. If the firmware needs to be updated, type the following command: boot load=[host server IP
address]:[/directory/firmware file name]
15. If the POST needs to be updated, type the following command: boot load-post=[host server IP
address]:[/Directory/firmware file name]

16. Reboot the 7036-P16 in order for the changes to take effect. Type the following command: boot action=reset
This completes the Direct Attach method for upgrading the firmware and POST from the command line.
Upgrading firmware using the Web
Gather the following information:
•IP address of target 7036-P16: [7036-P16 IP address]
•IP address of host server: [host server IP address]
•Root password of target 7036-P16.
Hardware requirements:
•AIX or Linux host server with access to the Web.
•7036-P16 fully configured and attached to an Ethernet network.
Do the following:
1. The next steps are used to determine the firmware and POST levels on the 7036-P16. Access the web interface of the target
7036-P16 by entering the IP address in a browser's URL window and login as root.
2. Choose Update Firmware under Administration from the main menu. The current firmware and boot levels will be displayed
as follows: Firmware: Version 82000684_(level) (date of last update), Post: 82000685_(level) (date of last update).
3. The following steps are used to determine if the firmware or POST on the 7036-P16 needs to be updated.
Use the host sever to access the following Web site to check for the latest firmware and boot updates:
http://techsupport.services.ibm.com/server/mdownload/download.html
4. Click on Other Devices.
5. Scroll to and click on LAN Attached RAN 16.
6. Read the release notes to determine the latest levels of the firmware and POST available on this web site.
7. Compare the levels available on this web site to the levels in step 2above.
8. If the firmware and POST versions are the same as in step 2, then the firmware and POST on the target 7036-P16 are current
and nothing more is needed. Complete this procedure by logging out from the IBM Support Site.
9. If the firmware version is not the same as in step 2, then the firmware on the target 7036-P16 is not current and it needs to be
updated. Download a copy of the firmware to a directory on the host server and make a note of the directory and the file
name. For example: /tmp/82000684_L.bin
10. If the POST version is not the same as in step 2, then the POST on the target 7036-P16 is not current and it needs to be
updated. Download a copy of the POST to a directory on the host server and make a note of the directory and the file name.
For example: /tmp/82000685_E.bin
11. Log out from the IBM support Web site.
12. The next steps are done only if the firmware or POST needs to be updated. These steps assume the user did not log out from
7036-P16 after step 2. Browse to the location on the host system where the files from steps 9and 10 are saved, select the
correct file, and click Update.
13. Reboot the 7036-P16 when your are prompted.
14. Access the 7036-P16's Web interface and verify on the Information page that the firmware version has been successfully
updated.

Cabling Guide
Table 1. Cables for use with the 7036-P16
IBM P/N Digi PN IBM FC Length Description
43G0935 76000088 8133 0.61m (2 ft.) Cable Kit consisting of four (4) RJ45 to DB25 (Male) cables. DB25 per EIA-232
Standard.
51G8610 61020024 8133 0.61m (2 ft.) FRU for FC 8133.
21P3740 Not
available
from Digi
None 0.305m (1 ft.) RJ45 to DB09 (Male) cable. DB09 wired the same as pSeries DB09 connectors.
Same as Digi PN 76000239.
Not
available
from IBM
76000238 None 1.23m (4 ft.) RJ45 to DB25 (Male) cable. DB25 wired to allow direct attachment to an IBM
3151 TTY Terminal.
Not
available
from IBM
76000239 None 0.61m (2 ft.) RJ45 to DB09 (Male) cable. DB09 wired the same as pSeries DB09 connectors.
Not
available
from IBM
76000200 None 0.61m (2 ft.) RJ45 to DB09 (Female) cable. DB09 wired the same as pSeries DB09
connectors.
Not
available
from IBM
76000264 None 0.61m (2 ft.) RJ45 to DB09 (Male) cable. DB09 wired as a crossover cable to eliminate the
need for a modem eliminator.
Not
available
from IBM
76000645 None 0.61m (2 ft.) RJ45 to DB09 (Female) cable. DB09 wired as a crossover cable to eliminate the
need for a modem eliminator.
21P3740
43G0935 and 51G8610