There are several remote administration commands offered by the AX3000. These commands are launched by using a remote
shell command (rsh for example) which is available in most major operating systems.
The following table lists the available AX3000 administration commands:
| Command |
Description |
| ax_reboot |
Rebooting the AX3000.
Example: rsh ax3000 ax_reboot [password]
|
| ax_sinit |
Resetting an AX3000 resource (screen session or aux. port).
Example: rsh ax3000 ax_sinit [password] sess1
|
| setup_get |
Requesting the AX3000 Set-Up.
Example: rsh
ax3000 setup_get > file
|
| setup_send |
Setting-up the AX3000 through a text file.
Example: rsh
ax3000 setup_send [password] < file
|
| ax_download |
Requesting an AX3000 firmware downloading
Example: rsh
ax3000 ax_download [password] 192.1.1.2 file
|
| ax_version |
Requesting the AX3000 firmware revision
Example: rsh ax3000 ax_version
|
| ax_getstat |
Requesting the AX3000 statistics.
Example: rsh ax3000 ax_getstat
|
Note: these commands are also available with uppercase characters (ax_version and AX_VERSION are the same command).
Top
Downloading Firmware with TFTP ProtocolThe TFTP protocol is a standard protocol for downloading
firmware.
Note: the following describes the TFTP
protocol. This information is only for an expert
user. For other users we strongly advise to use
the AxRM tool.
Click here to get more information about
AxRM.
TFTP is either included in the standard operating system distribution
(Unix/Linux, AS/400...) or available as 3rd party software (Windows). For more information, please read the AX3000 User's Manual or
consult the related FAQ.
The download operation is normally run from terminal setup, or remotely using
the AxRM tool. The following parameters are required:
- filename of the firmware file
- AX3000 IP Address,
-
Name or IP address of the tftp server,
-
Name or IP address of the router to reach the tftp server (optional
parameter).
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 AX3000 can be left without valid firmware.
In this situation BOOTP is needed to load a valid firmware file. Click here for more information about bootp protocol.
Top
Using BOOTP Protocol to Recover
from Failed Download
The BOOTP protocol is used to get information required for
downloading firmware with tftp (tftp host IP address and firmware
filename).
Note: the following describes the
BOOTP protocol. This information is only for an expert
user. For other users we strongly advise to use
the AxRM tool.
Click here to get more information about
AxRM.
BOOTP is provided as either given as a standard protocol
(Unix/Linux...) or available as an additional software (Windows for
example). For more information, please read the AX3000 User's Manual or
consult the related FAQ.
When the AX3000 firmware is invalid, BOOTP requests are automatically sent by
the AX3000. This allows the AX3000 to get information (firmware name, its IP
address and the TFTP server IP address) to download the firmware by TFTP.
The BOOTP protocol can also be run through the AX3000 Set-Up or by the
following remote administration command:
When the bootp request is answered, theAX3000 firmware is downloaded
by using tftp. Click here for more information
about tftp.
Top
Firmware Revision InformationThe AX3000 firmware revision is composed of:
- hardware information (shown here in red)
- a general firmware descriptor (shown here in blue)
- installed emulations (shown here in black)
- possible firmware options (shown here in green)
Examples:
- FK14-BV11f/TCP.FR.0303a:RDP&STD
- FK5-BV12a/TCP.XX.0303a:I52&ANS!NFU
- FK16-BV12a/TCP.XX.0303a:VNC&STD&QVT-SRI!DNS
Note: Click here, for details to find the
hardware information.
1 - Hardware Information
The AX3000 hardware information is FKx-BVyyy
- FKx is the electronic board code (click
here for more information)
- BVyyy is the boot code version (the boot code is the
non-erasable part of the flash memory)
2 - General Firmware Information
The beginning of the firmware version is FCT.NA.yywwi:
- FCT is the AX3000 operating mode:
- TCP stands for both TCP/IP and serial modes,
- SER stands for serial mode.
- NA is the firmware nationality (code is ISO compliant).
The main nationalities are:
- XX: International (all countries except the
following)
- BR: Brazil
- CZ: Czechoslovakia
- EE: Estonia
- FI: Finland
- FR: France
- GR: Greece
- IS: Iceland
- PT: Portugal
- SI: Slovenia
- TR: Turkey
- yywwi is the date code of the firmware creation followed by an alphabetical index (for instance: 0303a).
Note: three functions are dependent of the firmware nationality:
- Set-up message language (FR: French messages, other:
English messages),
- Support of national keyboard and associated
character set. For instance, the Turkish environment (keyboards
and character set) is only available with the 'TR' firmware.
- Default keyboard nationality (FR: France,
XX: North American, TR: Turkey, etc).
3 - Available Emulations
ANSI and VT emulations are provided as standard. This
group of emulation is coded ':STD'. An optional emulation can
be added. In this case the ':STD' code is replaced by the
emulation code:
- STD:
- for models 65C and 75: all the options described below
- for other models: contains ANS, VT2 and WYS
- RDP: graphics
protocol for Windows (models 65 and 75)
- VNC: graphics
protocol for Unix/Linux (models 65 and 75)
- I52: 5250 emulation
- I32: 3270 emulation
- ANS: ANSI-based emulations
- VT2: VT220 emulation
- WYS: Wyse 60/120 emulation
- V52: VT52 emulation
- ATO: ATO300 emulation
- SM9: SM9400/SM9412 emulations
- THE: THEOS emulation
- QVT: QVT 119+ emulation
- TVI: TVI 910 emulation
- SLN: SLNET emulation
- TWS: TWIN SERVER emulation
- I51: 3151 emulation
- R32: REAL32 emulation
- C32: C332 emulation
- PR9: PRISM emulation
4 - Possible Firmware Options
After the emulation specification, firmware option(s) can be
met. A '-' is used as separator between supported emulation (see
above) and these options. A '&' is used as separator between
two options.
Note: all these options (except PFK)
are now included as standard features of models
65C and 75.
The main firmware options are:
- ENH: enhanced colouring mode.
- SRI: login script (Unix only)
- PAL: private
VGA palette for each text session
- BLW: legacy
monitor modes (monochrome, grey-level, monochrome reverse)
- MSE: mouse support (standard for RDP and VNC)
- F24: 24-fctn-keys keyboard (implicit with 5250)
- F20: 20-fctn-keys keyboard (VT)
- 43L: 43-line mode support
- DNL: downloadable font support
- PFK: <F1> to <F4> remapped to the num pad (available for VT2 & WYS)
- HPV: specific value for <F1> to <F4> (available for VT2)
- AGA: alpha-graphics mode with ANSI emulations
(models 65/65E et 75/75E)
- AGV: alpha-graphics mode with VT emulations
(models 65/65E et 75/75E)
- AGW:
alpha-graphics mode with WYSE emulations
(models 65/65E et 75/75E)
- ALG (obsolete option): alpha-graphics mode (models 65/65E)
5 - Negative Firmware Options
When multiple-option firmware is requested, some standard options are
removed due to memory restrictions. Removed options are signified by a '!'. Possible options are:
- DHC: DHCP protocol
- DNS: DNS and DHCP protocols
- NFU: no local windowing support and no continuous underline (for 5250 emulation)
Top
Hardware InformationThe AX3000 hardware is identified by a 'Flash Key' (FK). There
are currently five different generations of hardware in the field,
each requiring specific firmware:
- FK3: former production hardware of models 55, 55E and 56
- FK5: former production hardware of models 55, 55E and 56
- FK11: former production hardware of models 55, 55E and
56
- FK7: former production hardware of models 65
- FK13: former production hardware of models 65 and 65E
- FK14: former production hardware of models 65/65B/65E (PS/2 mouse
port)
- FK15: former production hardware of models 60/60E
- FK16: former production hardware of models 75/75B/75E
- FK17: former production hardware of models 65B (network 10/100)
- FK18:
former production hardware of models 75C (USB ports)
- FK19: former production hardware of models 75C
- FK20: former production hardware of models 65C
- FK30: current production hardware of models 70W
- FK35: current production hardware of models 70F
- FK40: current production hardware of models 75C
- FK45: current production hardware of models 65C
The correct firmware file must be downloaded for your AX3000
hardware. Example: if FK3 firmware file is downloaded into FK5
hardware, the download process will fail (gives error 13).
The AX3000 hardware version is included in the general AX3000
firmware revision (ex.: FK11-BV1.2a/TCP.XX.0303a.STD). Click
here, to find out how to get the hardware information.
Top
Canon LBP-810 Printers
The problem:
These printers cannot be used with an Axel terminal. The printer
fails:
- with the 'printer test' (from the Axel
terminal set-up)
- under the LPD protocol
- with TSE environment (RDP or ICA)
Explanation:
This printer is limited to only
supporting the CAPT
protocol (Canon Advanced Printing Technology)
and does not support the industry standard ASCII
mode.
The Printer Test:
This test sends a string of standard ASCII text to the printer, as the printer does not recognise ASCII the test fails.
The LPD Protocol:
This printer (i.e. the CAPT protocol) uses bi-directional communication. LPD is uni-directional protocol. This makes the printer incompatible with LPD.
In addition no Unix/Linux drivers are provided by Canon. (This printer is only certified for Windows 95/98/NT 4.0/ME/2000).
TSE Environment:
The CAPT protocol is not supported under the TSE environment, so will not work under RDP or ICA.
Top
HP USB Printers: HP LaserJet 1000, 1005, 1018,
1020 and 1505
The problem:
The USB printer is detected by the terminal but
no logical USB port is mapped to the printer
(USB1, USB2...).
Explanation:
The key factor is that these printers don't
contain 'persistent' firmware. (The firmware is
downloaded each time the printer is switched
on).
For PCs the printer firmware is copied onto
the PC when the printer driver is installed, so
is available to be uploaded at any time.
As the driver is not loaded into the Axel
terminal, the firmware is not stored in the
terminal. This makes it impossible to use this
printer.
This explanation can be confirmed by this
simple test:
- connect the printer to a PC
- turn the printer on
- check the printer by
printing a test page
- connect the printer to the
terminal WITHOUT TURNING THE PRINTER OFF
- the printer is detected by
the terminal and now a USB logical port is
available.
Top
