Configuration and Image Loading
Page 132 7210 SAS M, T, X, R6 Basic System Configuration Guide
Persistence
The following displays an example of BOF output for 7210 SAS devices.
A:7210-SAS>show# bof
===============================================================================
BOF (Memory)
===============================================================================
primary-image ftp://*:*@xx.xxx.x.xx/./images/x-both.tim
primary-config cf1:\cpuqos_4.0.cfg
primary-dns xx.xx.xx.xx
secondary-dns xx.xx.xx.xx
----------- output snipped ----------
#System Settings:
wait 3
persist on
console-speed 115200
uplink-mode network
no console-disabled
===============================================================================
A:7210-SAS>show#
Optionally, the BOF
persist
parameter can specify whether the system should preserve system
indexes when a save command is executed. During a subsequent boot, the index file is read along
with the configuration file. As a result, a number of system indexes are preserved between reboots,
including the interface index. If persistence is not required and the configuration file is
successfully processed, then the system becomes operational. If persist is required, then a
matching
x.ndx
file must be located and successfully processed before the system can become
operational. 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. Note that the persistence option must be enabled to deploy the Network
Management System (NMS). The default is off.
Traps, logs, and console messages are generated if problems occur and SNMP shuts down for all
SNMP gets and sets, however, traps are issued.
To Next Page
Loading...
