Network Topology
Null
Problem Description
When Udisk is used to configure a router automatically, the configuration file cannot be read and the device cannot be automatically configured.[Zero Touch Provisioning].
But sometimes, the Udisk is recognized as USB:3/ rather than USB:0/
Process Analysis
After obtaining a configuration file, the device compares the file with its main startup configuration file. If the two files have the same settings, the device loads its main startup configuration file. If the two files have different settings, the device performs the following operations:
1. Identifies whether its main startup configuration file is using the same name as the obtained configuration file.
¡ If yes, the device renames its main startup configuration file by adding _bak to the base name of the file, and copies the obtained configuration file.
¡ If not, the system uses the obtained configuration file to overwrite its main startup configuration file.
2. Loads the obtained configuration file.
¡ If all commands in the obtained configuration file are successfully loaded, the device sets the obtained configuration file as the main startup configuration file.
¡ If a command in the obtained configuration file fails, the device removes all loaded settings
and searches for a local configuration file.
- If a configuration file is found, the device loads the configuration file.
- If no configuration file is found, the device finishes the automatic configuration process without loading any configurations.
Solution
When the U disk is identified as usba3, the automatic configuration of the U disk is unsuccessful;
The situation that the U disk is recognized as usba3 should be caused by the hidden partition of the U disk, which can be solved by re-partitioning or replaing the U disk.
