#9 Viper_SC_Manual_001-5008-000_Rev12e.docx | Page 764.7.2 CONFIG CONTROLThe Config Control page grants access to User Configuration, Firmware Upgrade and Factory Settings.Figure 60 – Maintenance/Unit Configuration Control4.7.2.1 USER CONFIGURATION SETTINGSSelect Checkpoint User Configuration to create a checkpoint of all the user configurable settings in the Viper. Click Proceedto save these settings into the configuration file (UserCFG_macaddress.drp, where macaddress is equal to the EthernetMAC Address of the Viper). The new configuration set overwrites previously saved settings. The configuration file containsall user settings that can be configured on any of the web pages as well as several additional parameters that can only beconfigured using the CLI.Additionally, portions of the Routing Table and the Neighbor Table are saved into the configuration file as described below.4.7.2.1.1 NEIGHBOR TABLE― Dynamic Neighbors. Not Saved. Dynamic neighbors are created and deleted automatically by the neighbor discoveryalgorithm and are not saved in the configuration file.― Locked Neighbors. Saved and Restored. Locked neighbors are created automatically by the neighbor discoveryalgorithm but are not deleted automatically. These entries are saved into the configuration file.― Static Neighbors. Saved and Restored. Static neighbors are created manually by the user. These entries are saved intothe configuration file.4.7.2.1.2 ROUTING TABLE― Connected Route. Not Saved. These routes point to a direct physical connection on the Ethernet port and are createddynamically based on the Viper SC’s Ethernet IP address.― Proprietary Route. Not Saved. Routes added due to an entry in the neighbor table. These routes will be automaticallyrecreated for each remote Viper SC in the neighbor table.― Static Route. Saved and Restored. Static routes are created manually by the user. These routes are saved into theconfiguration file.