Total Control MP/16, Operator'S Manual

Page: 76 / 182

3-40 Using Total Control MIBs
Command Description
testRom(18) The ROM test is basically a CRC test to verify the
integrity of the operating code that is programmed
into the Flash memory on the modem.
testNVRAM(19) The NVRAM test on a modem verifies the ability for
the modem to read from and write to NVRAM.
v54LocalAnalog
Loopback(20) This test is similar to the localAnalogLoopback test,
but in addition, it generates a specific data pattern
and checks the looped-back data for errors. The
test can be terminated by expiration of the time
specified in mdmTfTestTime, or manually by issuing
the terminateTest command. Upon termination a
count of errors detected can be found in
mdmTfV54Errors.
v54RemoteDigital
Loopback(21) This test is similar to the remoteDigitalLoopback
test, but in addition, it generates a specific data
pattern and checks the looped-back data for errors.
The test can be terminated by expiration of the time
specified in mdmTfTestTime, or manually by
issuing the terminateTest command. Upon
termination a count of errors detected can be found
in mdmTfV54Errors.
idlePhoneLine(22) The idle phone line test checks for loop current and
dial tone. Upon failure of this test, the exact reason
for failure can be retrieved from mdmCdCode.
Trap Enable Table
As with all NMC-generated SNMP Traps, a trap enable object
exists for all modem-related Traps. As is the case with all of the
modem MIB tables, a row exists for each modem entity in the
chassis, so it is possible to have complete control over which
modems generate which kind of Traps. In general, it is a good idea
to limit NMC-generated Traps to exception cases. Commonly
occurring events like Connection Established and Terminated
should usually only be turned on for a modem for a short time as a
debugging aid to avoid flooding the network with SNMP Traps in
a heavily loaded chassis.