The persistence option must be enabled to deploy the Network Management System (NMS).

Matching files (configuration and index files) must have the same filename prefix, such as test123.cfg and test123.ndx, and are created at the same time when a save command is executed. If persistence is required, a matching x.ndx file must be located and successfully processed before the system can become operational. If persistence is not required and the configuration file is successfully processed, the system becomes operational. As a result, a number of system indexes are preserved between reboots, including the interface index, LSP IDs, and path IDs.

During a subsequent boot, the index file is read along with the configuration file. The BOF persist parameter can specify whether the system should preserve system indexes when a save command is executed. The configuration file includes chassis, CSM, adapter card and port configurations, as well as system, routing, and service configurations. If not found, the secondary configuration location is searched, and lastly, the tertiary configuration location is searched. The first location searched is the primary configuration location. Like the runtime image, three locations can be configured for the system to search for the configuration file. If ADP is not enabled, the runtime image attempts to locate the configuration file as configured in the BOF. Any existing primary-config file is backed up, then overwritten. Instead, ADP discovers the node configuration from the network and the primary-config file is generated based on the configuration discovered by ADP. If ADP is enabled, no configuration files are processed at startup. Depending on the options in the BOF file, the runtime image loads the configuration in one of two ways. When the runtime image is successfully loaded, control is passed from the bootstrap loader to the image. If the files cannot be found or loaded, the system enters a console message dialog session prompting the user to enter alternate file locations and file names. If not found, the secondary image location is searched, and lastly, the tertiary image location is searched. The first location searched is the primary image location. Three locations can be configured for the system to search for the files that contain the runtime image. When the system executes the boot.ldr file, the initialization parameters from the BOF are processed. If this happens, the available options depend on the chassis.ДЇor the 7705В SAR-В SAR-18, there are two options: If the system cannot load or cannot find the boot.ldr file on the compact flash memory device (cf3), the system will reboot continuously in an attempt to successfully find and load the file. The default value to initially search for the boot.ldr file on cf3 cannot be modified. The boot.ldr file is the image that reads and executes the system initialization commands configured in the BOF. By default, the system searches the compact flash (cf3) for the boot.ldr file (also known as the boot loader or bootstrap file). Starting a 7705В SAR begins with hardware initialization (a reset or power cycle). Also refer to the appropriate chassis installation guide, вЂњAutomatic Discovery ProtocolвЂќ. Some commands can be given to the node through the ACO/LT button before there is network connectivity. In most cases you must have a console connection in order to access the node when there is no network connectivity to the node.

Baka loader console commands