NMS520-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
14
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
14 total| Object Name |
|---|
nms520 OBJECT IDENTIFIER .1.3.6.1.4.1.498.8.2 |
IMPORTS Unknown .1.3.6.1.4.1.498.8.2 |
nms520MIBversionIdentifies the version of the MIB. The format of the version
is x.yzT, where 'x' identifies the major revision number, 'y'
identifies the minor revision number, 'z' identifies the
typographical revision, and T identifies the test revision.
Acceptable values for the individual revision components are
as follows:
x: 1 - 9
y: 0 - 9
z: 0 - 9
T: A - Z
Upon formal release, no designation for the test revision will
be present.ro Unknown .1.3.6.1.4.1.498.8.2.1 |
nms520UnitCfgTableThe NMS520 Unit Configuration table. This table augments the
GDC SC5520 Unit Configuration table, providing unit level configuration
for each NMS520 device installed. For each entry in the GDC SC
Unit Configuration table that represents an NMS520, there is a
corresponding entry here whereby the value of the gdcSCunitCfgIndex
object is equivalent to the value of the nms520unitCfgIndex object. SEQUENCE OF Nms520UnitCfgEntry .1.3.6.1.4.1.498.8.2.2 |
nms520UnitCfgEntryThe NMS520 Unit Configuration table entry. The information in this
entry augments the information in the corresponding entry in the
GDC SC Unit Configuration table and provides unit level configuration
for the installed NMS520. Nms520UnitCfgEntry .1.3.6.1.4.1.498.8.2.2.1 |
nms520UnitCfgIndexThe index value which uniquely identifies the NMS520 to which
this entry is applicable. This has the form of a SCinstance
which defines the slot, line, and drop of the NMS520 with no
sub-identifier value.ro SCinstance .1.3.6.1.4.1.498.8.2.2.1.1 |
nms520Nms510CompatibilityModeThe NMS510 compatibility mode. This mode allows the NMS520 to
behave in a manner compatible with that of the NMS510 in a DDSI
multipoint circuit. If this object has the value enabled(2),
then the device can be used in conjunction with an NMS510. A value
of disabled(1) implies that the device is not backwardly compatible
with the NMS510.rw Enumeration .1.3.6.1.4.1.498.8.2.2.1.2 |
nms520PtToPtSentryTimeThe Point to point sentry time nms520PtToPtSentryTime, is used to
control the amount of time between unsolicited alarm responses from
a remote unit in a point to point application when there are no alarm
conditions to report. This unsolicited response maintains the
management link between the two units. These alarm responses are
intrusive to data. The range is from 1 minute to 127 minutes, with
60 minutes being the default value. The value of 0(zero) minutes will
disable remote alarm sentry reporting.rw INTEGER .1.3.6.1.4.1.498.8.2.2.1.3 |
nms520AlarmHystTimeThe Alarm hysterysis time nms520AlarmHystTime, is used to control the
amount of time a remote must wait between reporting unsolicited alarm
conditions. A remote will send an unsolicited alarm response at the
time of the first alarm. If second alarm occurs the remote will wait
for the time specified by this object before it will send another alarm
response. This time applies for both point to point and multipoint
applications. The range is from 1 second to 127 seconds, with 10
seconds being the default value.rw INTEGER .1.3.6.1.4.1.498.8.2.2.1.4 |
nms520MtpointRmRspIntrvlThe multipoint remote response interval nms520MtpointRmRspIntrvl, is
used to control the amount of time between unsolicited alarm responses
from a remote unit in a multipoint applications when there are no alarm
conditions to report. This unsolicited response maintains the
management link between the two units. The range is from 1 second
to 127 seconds with 10 seconds being the default value. The value
of 0(zero) seconds is disable remote alarm sentry reporting. All
remotes in a multipoint application must be set the same.
These alarm responses are non-intrusive to data.rw INTEGER .1.3.6.1.4.1.498.8.2.2.1.5 |
nms520DtePortTypeThe value auto(3), indicates that the DTE port is automatically
being detected, and set. The rs232(1), will force the DTE port
to EIA/TIA-232-E, and v35(2), will force the DTE port to V.35.rw Enumeration .1.3.6.1.4.1.498.8.2.2.1.6 |
nms520DteCtsDelayRTS/CTS Delay options
ctsOn(1) Forces both RTS and CTS On regardless of the
state of the attached business equipment (the
transmitter is On regardless of the status of
the RTS interface lead). MIB object
nms520DteCtsDelayExt is ignored.
cts0mSec(2) Provides zero bits of delay between active
RTS and CTS being set to active. MIB object
nms520DteCtsDelayExt must be set to ext0mSec(1).
ctsFix3Char(3) Provides three character bits of delay between
active RTS and CTS being set to active. MIB
object nms520DteCtsDelayExt must be set to
ext0mSec(1).rw Enumeration .1.3.6.1.4.1.498.8.2.2.1.7 |
nms520DteCtsDelayExtRTS/CTS Delay options extension
ext0mSec(1) Used to enable options cts0mSec(2) or
ctsFix3Char(3) from MIB object
nms520DteCtsDelay.
ext30mSec(2) Provides 30 msec of delay between active
RTS and CTS being set to active. MIB object
nms520DteCtsDelay must be set for either
cts0mSec(2) or ctsFix3Char(3).
ext60mSec(3) Provides 60 msec of delay between active
RTS and CTS being set to active. MIB object
nms520DteCtsDelay must be set for either
cts0mSec(2) or ctsFix3Char(3).
ext90mSec(4) Provides 90 msec of delay between active
RTS and CTS being set to active. MIB object
nms520DteCtsDelay must be set for either
cts0mSec(2) or ctsFix3Char(3).rw Enumeration .1.3.6.1.4.1.498.8.2.2.1.8 |
nms520FirmwareLevelThe version number of the firmware, to allow products to know which
revision is installed. The released version number is sequenced from
::= { nms520UnitCfgEntry 9}
nms520DaisyChainBps OBJECT-TYPE
SYNTAX INTEGER {
bps75(1),
bps9600(2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTIONro DisplayString .nms520DiagExcEntry.8 |