Total Control MP/16, Operator'S Manual

Page: 55 / 182

The NMC MIB 3-19
NMC Commands
Configuration-related Commands
Before discussing each of the configuration-related NMC
commands, there are a number of items that need to be addressed.
First is the issue of NVRAM. Each NAC has its own NVRAM. In
addition, the NMC has its own NVRAM. The two are completely
independent.
Here are two basic ways that the Network Manager might use the
NVRAM in the chassis.
♦
Configure each device and save the settings to each NAC's
NVRAM. Set those NACs to boot from their own NVRAM
(ignoring the NMC NVRAM, except for NMC-specific
parameters). Disable the parameter
nmcPowerUpAutoCfgEnable so the NMC does not
automatically configure the NACs, either upon install of the
NAC, install of the NMC, or power up of the chassis.
♦
Configure each device and save all settings to the NMC's
NVRAM (ignoring each NAC's NVRAM). Enable
nmcPowerUpAutoCfgEnable so the NMC automatically
configures each device upon install of the NAC, install of the
NMC, or power up of the chassis.
The advantage of the first approach is that it minimizes the effort of
the NMC. However, it also opens up the possibility of local
configuration changes that the NMC does not know about. Some
of this can be minimized, for example by disabling configuration-
related AT commands on the modems.
Because of the difficulties associated with attempting to keep the
NMC in sync with configuration changes that are made via local
interfaces on the various NACs, the concept of a configuration
cache was born in the NMC. This cache operates as follows.
1 Upon power up, as the NMC begins discovering cards in the
chassis, the NMC loads the cache for each of the sixteen slots
from the values previously saved in NVRAM.
2 The cache values for any slots for which there is no
configuration in the NMC's NVRAM are set to defaults.