FAQ-How to delete the configurations of MA5200, and how to recover the configuration files deleted?

Publication Date:  2012-07-27 Views:  91 Downloads:  0
Issue Description
  Q:How to delete the configurations of MA5200, and how to recover the configuration files deleted? 

Alarm Information
No

Handling Process
A:
For MA5200F MA2.10-7xxx release
Method I: execute the following command to delete the startup file directly, and then reboot the system
<MA5200F>
deletevrpcfg.zip
Method II: cleanup the configuration directly by command, and then reboot the system;
<MA5200F>resetsaved-configuration

For MA5200G  VRP3.30-2xxx release
Method I: execute a command to check which file the system is initialized from (shown at last line)
<MA5200G>
displaystartup
MainBoard:
Configedstartupsystemsoftware:hd:/ma5200_2210.bin
Startupsystemsoftware:hd:/ma5200_2210.bin
Nextstartupsystemsoftware:hd:/ma5200_2210.bin
Startupsaved-configurationfile:flash:/vrpcfg.zip
Nextstartupsaved-configurationfile:flash:/vrpcfg.zip


Execute the following command to delete the corresponding startup file directly, and then reboot the system


<MA5200G>deletevrpcfg.zip
Deleteflash:/vrpcfg.zip?[Y/N]:y
%Deletingfileflash:/vrpcfg.zip.......Done!


Method II: cleanup the configurations by command directly, and reboot the system
<MA5200G>resetsaved-configuration


How to recover the configuration files deleted by error?

1) For MA2.10-71xx or VRP3.30-2xxx release
If it is removed by delete command, and the recycle bin is not cleared, execute the undelete command to recover the configurations deleted, and reboot the system;
If it is removed by delete/u or resetsaved-configuration command, or the recycle bin has been cleared, the configuration cannot be recovered directly. If other equipments have the backup, ZIP it to vrpcfg.zip and load it to the system; for MA2.10-71xx, load it to the root directory of flash; for VRP3.30-2xxx, it could be loaded to any directory, and then execute the startup command to recover the data from specified corresponding file, reboot the system at last.


Root Cause
No

END