This section contains flash memory upgrade instructions, design and
installation notes.
Contents:
Determining the Firmware
Version
To determine an EasyServer's firmware version, perform the following:
Using Web Configuration.
Invoke the Server's setup utility by entering its IP address in a network-connected
web-browser, (i.e. http://123.456.789.001). When the Setup front page
is displayed:
Step 1.
Press the `Setup' button. Specify a valid user name and password,
if prompted.
Step 2.
Select the `Command Line Interface' hyperlink from the main
Setup screen.
Step 3.
Select the `Show' hyperlink, then the `Server'. The
server's firmware details are displayed.
Using Command Line Configuration.
Perform the following:
1. Login to Server.
Telnet to the EasyServer and execute the following command:
SHOW SERVER
The server's firmware details are displayed.
V 6.1.0 Firmware
TruPort requires v 6.1.0 or higher of the EasyServer II and LantraServer.
A flash image of v 6.1.0 is included as part of the TruPort installation.
This image is copied in the following location during TruPort installation:
/usr/lib/easyserver/images/es-6.1.0
Flash Memory upgrading allows the EasyServer's operating software to
be upgraded to newer versions, as they become available.
The upgrade is achieved by a TFTP file transfer from a local network
system to the EasyServer. The EasyServer or LantraServer software is
modified so that it can erase and reprogram its Flash Memory with the
new code image.
Enabling tftp on
your Unix System
Before you can download a new version of the firmware into your EasyServer
II or LantraServer, you need to enable the TFTP service on your system.
Please consult your operating system documentation for details on how
to enable TFTP on your system. Detailed below, as an example, are the
steps required to enable tftp on an SCO Unix system.
The TFTP configuration details are found in the file /etc/inetd.conf.
An extract from this file is listed below.
Enabling this allows public read files to be accessed via TFTP.
tftp dgram udp wait
nouser /etc/tftpd tftpd
This is the more secure method, since only files from /tftpboot can
be accessed via TFTP. This must be root in order to do the chroot to
/tftpboot. /tftpboot must be created by hand.
tftp dgram udp wait
root /etc/tftpd tftpd -s /tftpboot
It is more usual to enable TFTP in secure mode to limit TFTP access
to a specified directory. By default, this is the /tftpboot directory.
This example assumes that TFTP is to be run in secure mode.
Step 1.
Uncomment the appropriate line in /etc/inetd.conf.
Step 2.
Create the directory /tftpboot if it doesn't already exist
and ensure that the appropriate permissions are set on the directory.
This will also allow EasyServer II configurations to be uploaded to
the Unix system.
# mkdir /tftpboot
# chmod 777 /tftpboot
The inetd daemon needs to be made aware of the changes made
to the inetd.conf file. This is done by sending the inetd
process a SIGHUP signal. Firstly, the process id of the inetd
process needs to be determined. Secondly, the signal needs to be issued
to the process.
Step 3.
Determine the process id of the inetd process using the ps
command
# ps -ef | grep inetd
root 358 1 0 Sep 18
? 2:59 inetd
In this case, the process ID of the inetd process is 358.
Step 4.
Send the SIGHUP signal to the inetd process
# kill -1 358
Step 5.
Copy the new EasyServerII firmware image into the /tftpboot directory
# cp /usr/lib/easyserver/images/es-6.1.0
/tftpboot
Step 6.
Ensure that the permissions on the image file are just read permissions.
This will prevent the image being overwritten accidentally.
# chmod 444 /tftpboot/es-6.1.0
Your system is now ready to download the new firmware to the EasyServer
II.
Performing a Flash
Memory Upgrade
To perform a flash memory upgrade, perform the following:
Step 1.
NVRAM. Set the EasyServer II's NVRAM setting for `flashfile'
name and host, as follows:
CHANGE SERVER FLASHFILE {file_name} HOST {host_name} [DIAGNOTICS
ENABLED]
If host_name is not specified, the EasyServer II will use
the server that supplied the IP address using BOOTP or DHCP.
Step 2.
Reboot the EasyServer II. The startup boot code checks the
`flashfile' tag of the NVRAM. If set, the unit boots into the Flash
Memory upgrade process. Otherwise it boots normally and flash upgrade
is aborted.
Step 3.
Poll. The Flash Memory upgrade service will poll the `flashfile'
host every 5 seconds and attempt to TFTP the specified `flashfile'
name. If the TFTP open succeeds, the EasyServer II will load the entire
file and check that its checksum is valid. If it is not, then it will
continue to poll.
Step 4.
Re-TFTP Update File. If the check sum is good the EasyServer
II will again TFTP the entire file. This time, the contents of the
Flash Memory are reprogrammed. If this load is successful the EasyServer
II will reboot into the new operating image.
Step 5.
Reboot to old image if unsuccessful. If the new server image
is unable to be downloaded within two minutes, the EasyServer II will
reboot into its current Flash Memory resident operating image.
Using Web Configuration.
Invoke the Server's setup utility by entering its IP address in a network-connected
web-browser, (i.e. http://123.456.789.001). When the Setup front page
is displayed:
Step 1.
Press the `Setup' button. Specify a valid user name and password,
if prompted.
Step 2.
Select the `Server' (general server setup) hyperlink from the
main Setup screen.
Step 3.
Select the `Flash Memory Server Software Upgrade' hyperlink
from the Setup Server screen. The `Setup Flash Memory Upgrade File'
screen is displayed. You can obtain a flash memory upgrade image file
by selecting the hyperlink on this screen. Once obtained, you can
then upgrade the flash memory using the form on this screen. Alternately,
you can obtain a Windows version of the image from the Stallion web
site (www.stallion.com). Full
instructions are included at the web site.
Step 4.
Specify the update filename and hostname. These define
the location of the flash image on a local server equiped with a TFTP
server.
Step 5.
Press the Configure button when ready. The input parameters
are implemented immediately. The setup program now confirms that the
input has been accepted by displaying the Configuration Results
screen.
Using Command Line Configuration.
Perform the following:
Step 1.
NVRAM. Set the EasyServer's NVRAM setting for `flashfile' name
and host, as follows:
CHANGE SERVER FLASHFILE {file_name} HOST {host_name} [DIAGNOSTICS
ANABLED]
If host_name is not specified, the EasyServer will use the
server that supplied the IP address using BOOTP or DHCP.
Step 2.
Reboot the EasyServer. The startup boot code checks the `flashfile'
tag of the NVRAM. If set, the unit boots into the Flash Memory upgrade
process. Otherwise it boots normally and flash upgrade is aborted.
Step 3.
Poll. The Flash Memory upgrade service will poll the `flashfile'
host every 5 seconds and attempt to TFTP the specified `flashfile'
name. If the TFTP open succeeds, the EasyServer will load the entire
file and check that its checksum is valid. If it is not, then it will
continue to poll.
Step 4.
Re-TFTP Update File. If the check sum is good the EasyServer
will again TFTP the entire file. This time, the contents of the Flash
Memory are reprogrammed. If this load is successful the EasyServer
will reboot into the new operating image.
Step 5.
Reboot to old image if unsuccessful. If the new server image
is unable to be downloaded within two minutes, the EasyServer will
reboot into its current Flash Memory resident operating image.
Installation Notes
TruPort files are placed into /usr/lib/easyserver:
~/bin- support binaries (bccstty, gzip, etc)
~/drivers- TruPort pseudo device driver
~/daemon- TruPort daemon and support files
~/diags- temporary creation of diags device nodes
~/man- manual pages
~/stanza- used by easyadm for easyserver ports
Easyadm package will be installed as for all other easyadm drivers:
/etc/easyadm- easyadm binary
/etc/rc.d/S30easy- easyadm start up script
/etc/rc.d/S86truportd - truport start up script
/usr/lib/easyadm- easyadm support files
