Total Control MP/16, Operator'S Manual

Page: 50 / 182

3-14 Using Total Control MIBs
will only be able to power up in a “waiting for SDL” mode on its
local console port via the PCSDL.EXE mechanism.
Enabling Chassis Traps
Each of the chassis-level traps has an associated enable object. If
one of these objects is SET to disabled, the proxy agent will not
send traps for that event. SETting one of these objects to enabled
allows the proxy agent to send traps for the associated event. Even
though there are some slot and entity related traps found here,
there is only a single enable for these traps. In order for the NMC
to actually send traps, one or more entries must exist in the trap
destination table in the NMC MIB. See the section titled
The Trap
Destination Table later in this document for further details.
The NMC MIB
Although the MP/16 management module can not be accurately
termed an “NMC,” it uses the Total Control NMC MIB, as it
behaves identically in respect to its implementation of applicable
NMC MIB variables. To remain consistent with NMC MIB table
entries and extensions, the MP/16 management module should be
thought of as the NMC when applying MIBs to the MP/16.
Internet ID
iso.org.dod.internet.private.enterprises.usr.nas.nmc =
1.3.6.1.4.1.429.1.2
NMC-Specific Configuration
Changes to read-write objects found under nmcCfg take effect
immediately upon issuance of the SNMP SET request. Changes to
these objects are made permanent by issuing the saveToNvram
command (see section on NMC Commands). When the NMC
boots from power on or a software reset command, the NMC
always initializes these variables from the values that have last
been saved to the NMC's NVRAM.
Configurable objects found under nmcCfg that are not discussed
below are self-explanatory given the MIB text.