136
# Specify file new-config.cfg as the configuration file to be used at the next boot of all members of the
IRF virtual device.
<IRF> startup saved-configuration new-config.cfg main
Please wait ...
Setting the master board ...
... Done!
Setting the slave board ...
Slot 1:
Set next configuration file successfully.
Slot 0:
Set next configuration file successfully.
Slot 1:
Set next configuration file successfully.
# Specify file soft-version2.bin 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 display version.
Hotfix configuration example
Network requirements
• The IRF virtual device in this example comprises two member devices, the master and subordinate switch.
The software running on the member devices are of some problem, and hotfixing is needed.
• The patch file patch_mpu.bin and patch_lpu.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 2 Network diagram for configuring hotfix
To Next Page
Loading...
Need help?
General
