Boot Server (Control Module Only) - Allied Telesis SwitchBlade x3100 Series Manual

Introduction
cfc200_14.2.0.dhays6.20100326. No
tar...........................
ge24poe_14.1.0.dhays4.20100319 No
.tar..........................
ge24poe_14.2.0.dhays1.20100325 No
.tar..........................
ge24poe_14.2.0.dhays1.20100326 No
.tar..........................
matts_config.................. No
results.out................... No
test10.cfg.................... No
vxWorks_cfc200................ No
xe4_14.1.0.GAMMA.20100202.tar. No
xe4_14.1.0.dhays4.20100319.tar No
xe4_14.2.0.dhays1.20100325.tar No
xe4_14.2.0.dhays1.20100326.tar No
---------------------------------------------------------------------------

1.8.3 Boot Server (Control Module Only)

Users of the system have the option of storing secure copies of software release load files on their network
servers. This assists the user in providing optimum network reliability. The boot server should be configured
and the most current control module load file should be stored there. This insures that secure load files are
always available.
Note that boot server functionality is only available for the active control module.
Users can also configure the system to boot from the network servers where the load files are stored using the
SET BOOTSERVER. It permits users to designate a server to be the system boot server. As discussed in 1.7.3,
load files are stored in FLASH memory on the control module. If the FLASH should become corrupted or the
files become unusable for any reason, the system will boot from the secure load files stored on the boot server.
To ensure system recovery back to its normal operating state, the card load files that are stored on the boot
server must be a copy of the card load file designated as PREFLOAD for the control module.
Loading the system from the boot server is not intended to be the primary method for software release deliv-
ery. Rather, it is a backup or secondary method that the system will utilize if the primary method is unusable for
any reason.
To configure the boot server, the flow of commands would be.
Get the preferred load using the GET FILE command.
1.
Set the preferred load using the SET CARD PREFLOAD command.
2.
Make a backup of preferred load using the COPY FILE command.
3.
Make the backup the alternate load using the SET CARD ALTLOAD command.
4.
Set the Bootserver using the SET BOOTSERVER command.
5.
Copy the current control module preferred load files, that are designated as PREFLOAD, onto the boot
6.
server using the PUT FILE command.
The following procedure shows the commands used to configure a boot server's IP address and the path to
where the preferred CFC software load resides on server. In this example, the filename of the preferred CFC
1-116
Software Reference for SwitchBlade x3100 Series Switches (Setting Up the Switch)
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Pass 0xdeadbeef Pass
Boot Server (Control Module Only)
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef
0xdeadbeef