Filter
Top Products
Chapter 11 – Upgrading Firmware And Managing Configurations
Chapter 11 – Upgrading Firmware And Managing
Configurations
Introduction
This chapter familiarizes the user with:
• Upgrading firmware using the XModem protocol and Trivial File Transfer
Protocol (TFTP)
• Capturing and restoring the switch configuration using XModem and TFTP
• Using SQL commands to view/change configuration.
Upgrading Firmware
You may be required to upgrade the switch firmware in order to take advantage of
new features or bug fixes.
Your RuggedSwitch™ has two firmware components, the boot binary and the main
application binary. In normal practice only the main application will have to be
upgraded. Your RuggedCom representative will provide you with this file. It will
be of the form RuggedSwitch_Main_v1.x.y.bin.
You may upgrade using either an XModem or TFTP protocol utility. If you will
use XModem you upgrade from the RS232 port or through a Telnet session.
TFTP transfers may be performed in one of two ways. A TFTP client upon a
Unix/Dos workstation can be used to contact the RuggedSwitch™ TFTP server.
This method is very convenient, but will not provide control over who is allowed
to upgrade the switch.
Alternatively, the TFTP client in the RuggedSwitch™ CLI shell can be used to
contact a Unix/Dos host supporting a TFTP server. You must set up a TFTP
server on your network, but only admin level users can then perform upgrades.
Note:
Security during file transfer by XModem and TFTP is established in the following ways.
Transfers from the CLI shell XModem and TFTP clients are determined by the access level of
the user. Downloads may only be performed by administrators while uploads may be performed
by operators and administrators.
TFTP transfers to the RuggedSwitch
™
TFTP Server are controlled by the
IP Services
Configuration Menu, TFTP Server
parameter.
RuggedCom
99