131
Setting the slave board ...
Chassis 1 Slot 1:
Set next configuration file successfully.
Chassis 2 Slot 0:
Set next configuration file successfully.
Chassis 2 Slot 1:
Set next configuration file successfully.
# Specify the soft-version2.bin file as the boot file to be used at the next boot of all members of the IRF
virtual device.
<IRF> boot-loader file soft-version2.bin slot all main
This command will set the boot file of the specified board. Continue? [Y/N]:y
The specified file will be used as the main boot file at the next reboot on slot 1!
The specified file will be used as the main boot file at the next reboot on slot 2!
# Reboot the device. The software version is upgraded now.
<IRF> reboot
To check if the upgrade is successful after the device reboots, use the display version command.
Hotfix configuration example
Network requirements
• The IRF virtual device in this example comprises two member devices, the master and slave switches.
The software running on the member devices are of some problem, and hotfixing is needed.
• The patch file patch_51s.bin is saved on the TFTP server.
• The IP address of the IRF virtual device is 1.1.1.1/24, and IP address of the TFTP server is 2.2.2.2/24.
The IRF virtual device and TFTP server can reach each other.
Figure 39 Network diagram for configuring hotfix
Configuration procedure
1. Configure the TFTP server. The configuration varies depending on server type, and the
configuration procedure is omitted.
• Enable the TFTP server function.
• Save the patch file patch_51s.bin to the directory of TFTP server.
2. Configure the device.
CAUTION:
Make sure the free Flash space of the device is big enough to store the patch files.
To Next Page
Loading...
Need help?
General