|
|
|
 AX4000
Office Server |
|
 |
|
Last Update:
14/12/2007 |
|
 DOWNLOADING FIRMWARE |
| |
Downloading Firmware by TFTP protocol
Unix TFTP Protocol
Windows TFTP Protocol
Using BOOTP Protocol in Event of Problem
How Can I Get Axel Firmware Files?
What do FK21, FK22 and FK23 mean?
|
| CONTROLLING SERIAL DEVICES |
| |
Printers: LPD Protocol or TTY Protocol?
Dumb Terminals: TELNET Protocol or TTY
Protocol?
Connecting Modems
UNIX: Associating a TTY with an Office Server
Serial Port
WINDOWS: Associating a COM with an Office
Server Serial Port
|
| ADMINISTRATION |
| |
Using a Script to Set-Up an Office Server
Setting the Office Server IP Address without a
Dumb Terminal
Remotely Rebooting an Office Server, or resetting
an Office Server Serial Port
|
| TROUBLESHOOTING |
| |
On AIX, the LPD Printer is Disabled When
Jobs are Printed
On SCO, Some LPD Print Jobs are Truncated
Printers Controlled by the TTY Protocol
Don't Work When the SCO Box is Rebooted
Windows LPD Print Jobs can be Delayed for
Several Minutes
|
Downloading Firmware by TFTP ProtocolThe tftp protocol is the standard protocol for downloading
firmware. This protocol is provided as a standard protocol on
Unix (click here for more information).
This is not the case for other operating systems (click
here for information about Windows).
The download operation is generally run from the Office Server
Set-Up. The following parameters must be given:
- File Name: pathname and filename of the firmware file,
- IP Address: Office Server IP Address,
- Server IP Addr./Name: name or IP address of the tftp server,
- Router IP Addr./Name (optional parameter): name or IP address
of the router to reach the tftp server.
Note: the download operation can also be remotely run
by using the rsh command (or rcmd for SCO UNIX):
|
rsh axname ax_download filename tftpserver tftprouter |
IMPORTANT: if an error occurs during the stage when
firmware is erased, the Office Server will be without valid firmware.
The use of BOOTP protocol is needed to get valid a firmware. Click here for more information about bootp protocol.
Top
Unix TFTP Protocol
The tftp protocol is available as a standard feature on Unix.
But this protocol is not enabled by default.
Setting-Up the TFTP Protocol
Modify the file /etc/inetd.conf by removing the '#' comment
character, from the beginning of the line associated with tftp.
For information, please find below typical tftp lines according
to the used Unix system:
SCO OpenServer
|
tftp dgram udp wait nouser /etc/tftpd tftpd |
AIX 4.x
|
tftp dgram udp nowait nobody /usr/sbin/tftpd tftpd -n |
LINUX
|
tftp dgram udp wait root /usr/sbin/tcpd in.tftpd / |
UNIXWARE 7
|
tftp dgram udp wait nobody /usr/sbin/in.tftpd in.tftpd |
Note: we advise the tftp public mode (no username checking
and no pre-defined tftp directory).
Enabling the TFTP Protocol
These modifications take effect after rebooting the UNIX host
or sending the signal 1 to the inetd process (kill -1 pid).
Top
Windows TFTP Protocol
TFTP protocol is not provided as a standard
feature by Windows 95/98 and NT4. Third party
software is needed. For more information please
contact us.
Top
Using BOOTP Protocol in
Event of Problem
The bootp protocol is used to get information required for
downloading firmware with tftp (tftp host IP address and firmware
filename). This protocol is available on Unix as a standard feature
. This is not the case for other operating systems (Windows NT
for example).
Setting-Up and Enabling BOOTP protocol: Modify the file
/etc/inetd.conf by removing the '#' comment character, from the
beginning of the line associated with bootp. These modifications
take effect after rebooting the UNIX host or sending the signal
1 to the inetd process (kill -1 pid).
Setting BOOPT environment: the bootp protocol is based
on a file parameter: /etc/bootptab. This file describes the network
and attached TCP/IP devices. and gives all device information
needed for tftp (firmware filename, IP addresses, etc).
Example of /etc/bootptab (the first line describes network and
the second line describes the Office Server):
default:hn:df=/etc/btdump:ht=ethernet:sa=192.168.1.252:to=auto:
axel1:tc=default:ht=ethernet:ha=00A034100001:ip=192.168.1.242:bf=/tmp/axel: |
Note: the main capabilities are as follows:
- sa: tftp host IP address
- ha: Office Server Ethernet address
- ip: Office Server IP address
- bf: firmware filename
Running BOOTP: a bootp request can be run from both
the Office Server interactive set-up or by an rsh command (or
rcmd for SCO UNIX):
When the bootp request is answered, the Office Server firmware
is downloaded by using tftp. Click here for more
information about tftp.
Top
How Can I Get Axel
Firmware Files ?The Axel firmware files are free
of charge and are available on request. Contact
us and the requested firmware will be sent either by email.
Note: firmware files are not available on our Web site.
Top
What do FK21, FK22 and FK23
mean?
The Office Server hardware is identified by a 'Flash Key' (FK).
There are currently three different generations of hardware in
the field, each requiring specific firmware:
- FK21: AX4010 former production hardware
- FK22: AX4010 current production hardware
- FK23: AX4020 current production hardware
The correct firmware file must be downloaded for your Office
Server hardware. Example: if FK21 firmware file is downloaded
into FK22 hardware, the download process will fail.
The Office Server hardware version is included in the general
Office Server firmware revision (ex.: FK22-BV1.2a/9926f.STD).
To get the Office Server firmware revision and the hardware revision,
use one of the following:
- Enter the Office Server interactive set-up, the revision
is shown in the general menu,
- Get the Office Server set-up by issuing the rcmd (or rsh)
command (the revision is included in the text file banner):
rsh axname setup_get > file
- Use the following rcmd (or rsh) command to get the revision
directly:
rsh axname ax_version
Top
Printers: LPD Protocol or TTY Protocol?
Printers connected to an Office Server can be handled by:
- lpd
- tty
The following tables list operational characteristics for each
protocol .Select the one most suited to your needs.
LPD Protocol:
|
BENEFITS |
DRAWBACKS |
- This protocol is available as a standard feature for major
operating systems (Unix, Windows NT, AS/400, etc).
- The printer port is locked by LPD only during the printing.
That means several hosts can print on a single Office Server
serial port.
- The LPD printer is a standard system printer (controlled by
the spooler). |
- On Unix, an LPD printer can only used by its spooler name.
No tty is associated with an LPD printer.
- On SCO Unix, it is not possible to associate a driver with
an LPD printer. That means the application must create a print
file preformatted for the LPD printer. |
TTY Protocol:
|
BENEFITS |
DRAWBACKS |
- A port controlled by the tty protocol is seen as a local port
(as a multi I/O board)
- A printer can be accessed either by its spooler name or by
its tty. |
- This protocol is additional Unix software designed by Axel.
It must be installed and set up on the Unix box.
- A serial port controlled by the tty protocol can only be addressed
by a single Unix box. |
Top
Dumb Terminals: TELNET
Protocol or TTY Protocol?
Dumb terminals connected to an Office Server can be handled
by:
- telnet
- tty
The following tables list operational characteristics for each
protocol. Select the one most suited to your needs.
TELNET Protocol:
|
BENEFITS |
DRAWBACKS |
- On Unix, the telnetd daemon is available as a standard
feature
- No special Unix setting is needed. |
- The ptty associated with the dumb terminal is dynamically given
by telnetd |
TTY Protocol:
|
BENEFITS |
DRAWBACKS |
- A port controlled by the tty protocol is seen as a local
port (as a multi I/O board)
- The axttyd daemon (handling tty connections) is available for
all Unix flavours. |
- This protocol is additional Unix software designed by Axel.
It must be installed and set up on the Unix box. |
Top
Connecting Modems
There are many combinations for connecting modems to the Office
server, please select the environment that best suites your use
below.
1 - A Dumb Terminal (or a PC Emulator) Connected to the Office
Server via a Modem
The Office Server modem is used for incoming calls.
The Office Server locally handles the modem. That means the
modem is invisible to Unix. The dumb terminal is seen as a dumb
terminal directly connected to the Office Server
The Office Server must be set as follows:
- LINE PARAMETERS:
Set the line type to 'telecom'.
Set communication parameters (baud rate, handshake, etc.)
The "Reset Seq. Modem" parameter is the HAYES sequence
for loading default factory settings (example: AT&F)
The "Init Seq. Modem" parameter is the HAYES sequence
for setting the modem (no echo, handshake, etc.).
- NETWORK SERVICE:
Select telnet or tty (click here for
more information).
2 - The Modem is Used for Out-Going Calls (fax, remote administration,
etc)
Chose the operating system:
- UNIX:
Associate the tty protocol to the Office Server serial port (click here for more information). The Unix application
addresses the modem as a tty.
Note: the tty protocol doesn't support the signal control
(DCD, DSR...)
- Windows:
Associate the telnet server protocol to the Office Server serial
port and use DialOut/IP to add COMs to Windows (click
here for more information).
Top
UNIX: Associating a TTY with
an Office Server Serial Port
The tty protocol allows a Unix pseudo-terminal (ptty) to be
associated to an Office Server serial port. Effectively the Office
Server serial port is seen as multi I/O board channel.
Setting-Up the Office Server
Enter the Office Server Set-Up and set the "Network Service"
parameters as follows:
- Service Mode: enter the keyword 'client'
- Service Type : enter the keyword 'tty'
- Host Name / IP Address: UNIX host name (or IP address) to which
the serial peripheral will be connected
- TCP Port: numeric value associated with the tty service on the
selected UNIX host (generally 2048).
- ID string: enter 'y'
- Auto Conn.: enter 'y'
- Time-out: if the line is inactive for a predefined number of
minutes, the Office Server automatically closes the connection.
If the number of minutes is '0', this feature is disabled.
- Backup Host Used: option to automatically connect to a secondary
host if the primary host fails
- TCP Keepalive Timeout : the keepalive mechanism allows the
Office Server to regularly check its TCP/IP connection status.
Installing axttyd on Unix
Copy the following onto Unix:
|
File |
Destination |
Comment |
|
axttyd |
/etc |
Daemon (tty server) |
|
axfile |
/etc |
Association File |
|
S91axel |
/etc/rc2.d |
Unix Boot Script |
Setting-Up axttyd
The AXEL tty server uses a configuration file, which lists
all authorised associations between Office Server ports and UNIX
pttys. Example:
#AX4000
axel1
axel1
axel2
axel2 |
Resource
ch1
ch4
ch2
ch8 |
Master
/dev/ptyp12
/dev/ptmx
/dev/ptyp1
/dev/ptyp2 |
Slave
/dev/ttyp12
/dev/pts/13
/dev/ttyp1
/dev/ttyp2 |
Each entry in this file contains four parameters:
- Office Server hostname (see /etc/hosts)
- Office Server resource: ch1, ch2, ..., ch8
- the master file of the ptty: /dev/ptypx ou /dev/ptmx
- the slave file of the ptty: /dev/ttypx ou /dev/pts/x
Running axttyd
The command to start the AXEL tty server is:
Using Ptty
The Office Server serial ports can be addressed by the ptty
slave part: /dev/ttypx.
Note: when a dumb terminal is attached to an Office
Server serial port the following line must be added to /etc/inittab
to initiate a login prompt:
|
px:234:respawn:/etc/getty ttypx m |
Top
WINDOWS: Associating
a COM With an Office Server Serial Port
The Axel Office Server serial ports can be seen as Windows
COM ports. So, any software can use standard O.S. commands:
- to set serial line parameters (baud rate, parity, etc),
- to set serial output signals (DTR and RTS),
- to get serial input signal status (DSR, CTS and CD).
1 - Setting-Up the Office Server
Enter the Office Server Set-Up and set the serial port as follows:
- LINE PARAMETERS:
|
- |
Set line type to 'direct'. |
|
- |
Other parameter values (Baud Rate, Data Format, etc) are not
important |
- NETWORK SERVICE:
|
- |
Service Mode: enter the keyword 'server' |
|
- |
Service Type: enter the keyword 'telnet' |
|
- |
TCP port : a numeric identifier. This identifier will be
use by Windows to address each serial port |
|
- |
TCP Keepalive Timeout : the keepalive mechanism allows the
Office Server to regularly check its TCP/IP connection status. |
2 - Setting-Up Windows
On Windows, the COM network redirection is performed by the
DialOut/IP driver. This driver has to be installed on the Windows
machine.
Note: the DialOut/IP driver is released by Tactical
Software (www.tactical-sw.com).
After DialOut/IP has been installed, a remote COM is described
by:
- a name (COM5, COM6...)
- the Office Server IP address
- a port number: this identifier is the 'TCP Port' associated with
the 'telnet server' during the Office Server setting
- a protocol: use the 'telnet' protocol. Other protocols must be
disabled (for example, Unimodem protocol is enabled by default).
Note: To test the connection, click the <Wizard Configuration>
button
Top
Using a Script to Set-Up an Office Server
The Office Server can also be set up with a script. The remote
set-up functions are performed by a rsh command (or rcmd for SCO
UNIX):
Setting-Up an Office Server
Use the following command to set-up an Office Server:
|
rsh axname setup_send < file |
Note: axname is the Office Server name (listed
in /etc/hosts), setup_send is the remote set-up command and file
is the Office Server configuration file (this configuration file
can be created using a text editor or obtained using the command
'rsh setup_get').
The Office Server must read this new set-up before it will
take effect. This can be achieved either by power-cycling the
Office Server or by issuing a remote reboot
command.
Obtaining a Configuration
To obtain an Office Server configuration, use the rsh command
together with the setup_get option:
|
rsh axname setup_get > file |
The created configuration file lists each Office Server set-up
parameter.
Top
Setting the Office Server
IP Address without a Dumb Terminal
If the Office Server IP address is unknown, it is impossible
to use the interactive set-up (except with a serial terminal connected
to the admin. port).
The procedure described below overwrites the current (unknown)
IP address with a new (known) one. The Office Server has a special
protocol built in: if 8 ping requests are received, with an IP
address different to the current one, the Office Server IP is
updated and the Office Server is rebooted.
Updating ARP Table:
Run the following command to associate the Office Server's Ethernet
address xx:xx:xx:xx:xx:xx with the IP address yyy.yyy.yyy.yyy:
On Unix
|
# arp -s yyy.yyy.yyy.yyy xx:xx:xx:xx:xx:xx |
On Windows
|
c:\> arp -s yyy.yyy.yyy.yyy xx-xx-xx-xx-xx-xx |
Updating IP Address:
Run the ping command (Unix automatically re-pings until contact
is made, NT will give up after 5 pings, so the ping command must
be re-entered):
After 10 seconds the Office Server should answer. The Office
Server IP address is now yyy.yyy.yyy.yyy.
Entering the Office Server Set-Up:
Run the following telnet command:
|
telnet yyy.yyy.yyy.yyy 4096 |
Top
Remotely Rebooting an
Office Server, or Resetting an Office Server Serial PortThese remote administration commands are performed by using
a rsh command (or rcmd for SCO UNIX):
Rebooting the Office Server
Resetting an Office Server Serial Line
Notes:
- for these two commands, axname is the Office Server name
(listed in /etc/hosts)
- for the second command, chx is the serial port name (ch1,
ch2, ch3...ch8).
Top
On AIX, the LPD Printer is Disabled When Jobs are Printed
On AIX, the LPD Printer is Disabled When Jobs are Printed
Normally printing functions are performed well, but occasionally
print jobs are truncated and the printer is disabled by AIX.
To fix this, a timer value must be increased (1 minute by default).
Use a text editor to modify /etc/qconfig. Seek the entry dedicated
to the Office Server printer. Add the '-T xx' option (where xx
is a number of minutes). Example:
axel:
/usr/lib/lpd/rembak -T 5 |
Top
On SCO, Some LPD Print
Jobs are Truncated
On SCO, long LPD print jobs can be stopped before reaching
the end. This is due to a SCO default setting which doesn't allows
print jobs greater than 1 Mb.
To fix this, modify the /etc/printcap file which describes
SCO LPD printer. Add the mx#0 capability (no size limit) to the
printer description. Example:
prnaxel:\
:lp=:rm=ax3002:ex:rp=prnaxel:sd=/usr/spool/lpd/prnaxel:mx#0: |
Top
Printers Controlled by the TTY Protocol Don't Work When the SCO Box is Rebooted
The following problem has been reported when printers are controlled
by the tty protocol:
When the SCO box is powered off with the shutdown command
and if the Office Server hosting the printer is not powered off,
at the next SCO boot the printer won't work.
This is caused by the shutdown command not closing open TCP/IP
connections (this is not the case with haltsys). There are two
ways to resolve this problem:
- Power cycle the Office Server
- Adding a boot script to reboot Office Server at each SCO
boot time. Contact us to get this script.
Top
Windows LPD Print Jobs
can be Delayed for Several Minutes
- Subject: LPD printer problems
- Operating Systems: Windows (NT4 or 2000)
- Description: when several LPD print jobs are spooled,
the first batch (about 10) are correctly processed but the others
may remain spooled for a few minutes before being processed.
This problem is due to the Window's "socket" management
(a socket is a TCP/IP connection).
Notes about LPD and TCP/IP:
- A TCP/IP connection (i.e. a socket) is established for each
LPD print job. When the LPD print job is completed, this TCP/IP
connection is closed (i.e. the socket is released).
- A socket is composed by 4 parameters:
local IP address / local TCP port / remote IP
address / remote TCP port
The local IP address is the Windows address , the remote IP address
is the Axel address and the remote TCP port is 515 (Axel LPD
service). The local TCP port value is given by Windows.
Note: to list the sockets in use invoke the netstat command
- When a TCP/IP connection is closed, the associated socket
is not immediately released. This socket is set in an intermediate
status (TIME_WAIT) for 3 minutes. During this TIME_WAIT status,
the socket is not available for another TCP/IP connection.
The problem is due to the "remote TCP port" socket
parameter. Only 11 TCP ports are available to process LPD print
jobs: from 721 to 731. When 11 print jobs are processed in less
than 3 minutes, the 11 associated sockets are locked (status ESTABLISHED
or TIME_WAIT). So the next print job will be delayed until a TCP
port is released.
The Windows default is for 11 ports (721-731) to be used. To
avoid this limitation, Windows must be set-up to use any TCP ports
greater than 1024.
Setting-up Windows depends on both the Operating System and
the installed Service Pack. For information on changing this
setting please read the article "Updated TCP/IP Printing
Options for Windows NT 4.0 SP3 and Later" on the Microsoft
site (or on the Axel archive page).
Top
|
|
