Auto Installation - Motorola WS5100 Series Reference Manual

3. From the WS5100 running either 1.4.x or 2.x, create a configuration and save it on the switch.
WS5100# save <file name> <.cfg>
This is the configuration that will be upgraded to the new 3.x baseline.
NOTE: Motorola recommends saving a copy of the switch configurartion to a secure
location before the upgrade. If an error occurs with the upgrade a viable configuration will
be needed to restore on the switch.
4. Copy the configuration file <.cfg> from the legacy WS5100 to the Windows system where the conversion
utility resides.
Use ftp or tftp to transfer the file.
5. Click on the WS5100 configuration Upgrade
6. Select the config file copied on to the windows system and run it.
A folder having the same name as the config file is created. The folder contains the converted startup-
config file (in the new upgraded format) along with other log files.
7. Copy the startup-config file back to the WS5100 running using either tftp or ftp.
8. Download or copy the image file <WS5100-3.1.0.0-XX.v1> or
<WS5100-3.1.0.0-XX.v2> to the WS5100 running the legacy switch firmware.
9. On the WS5100, type:
WS5100#service
WS5100#password "password"
exec
Upon reboot, the switch runs the 3.x image using startup-config as the running configuration.
10.Repeat the instructions above for additional switch upgrades, ensuring
<WS5100-3.1.0.0-XX.v1> is used for 1.4.x version upgrades, and
<WS5100-3.1.0.0-XX.v2> is used for 2.x version upgrades.

2.4 Auto Installation

The switch auto Install function works via the DHCP server. This requires the definition of a Vendor Class and
four sub-options under option 43 namely:
• Option 186 - defines the tftp/ftp server and ftp username, password information
• Option 187 - defines the firmware path and file name
• Option 188 - defines the config path and file name
• Option 190 - defines the cluster config path and file name.
The individual features (config, cluster-config and image) can be enabled separately using the CLI, SNMP or
Web UI. If a feature is disabled, it is skipped when Auto install is triggered.
For the static case (where the URLs for the configuration and image files are not supplied by DHCP), the URLs
can be specified using the CLI, SNMP or Applet. Use the CLI to define the expected firmware image version.
If the image version is not specified, derive it from the file name. If it can not be derived from the filename,
the system will attempt to load something other than what it is currently running.
Switch Web UI Access and Image Upgrades
icon (from the Windows system).