In some situations when you may be recommended by Support to perform a factory reset and reload the configuration. However, depending on the issue, you may use different methods to backup/restore configuration or sometimes not even use the backup configuration.
1. In some situation, you need backup the PacketShaper configuration, perform a factory reset, and restore the configuration.
2. If the configuration is corrupt, you may not want to backup the configuration and load the corrupted configuration back.
3. It may be recommended to use config.cmd file instead of config.ldi to restore the configuration. 'config.cmd' file has a list of commands to rebuild the configuration so if some part of the config.cmd or some commands don't work are is in conflict with others then that part of the configuration will be omitted (this could help clear any configuration issues).
A. Using config.cmd file (this option is preferred unless your configuration is too big with several thousand classes and lots of policies and partitions - it could take some time to reload the configuration).
Back up the current PacketShaper configuration
Steps to perform a Factory Reset of your PacketShaper
Restore PacketShaper configuration
After PacketShaper has rebooted, answer "NO" for Guided Setup as below:
PacketShaper not yet configured. Do you wish to be
guided through initial setup of the PacketShaper? (yes): no
B. Using config.ldi file (this method may be faster as it does not have to run one command at a time as in config.cmd method but if there is some issue with the configuration, it will carry over to the restored configuration whereas config.cmd method will omit errored or conflicting configuration).
Back up the current PacketShaper configuration
Steps to perform a Factory Reset of your PacketShaper
Restore PacketShaper configuration
After PacketShaper has rebooted, answer "NO" for Guided Setup as below:
PacketShaper not yet configured. Do you wish to be
guided through initial setup of the PacketShaper? (yes): no