NMS510-MIB
File:
NMS510-MIB.mib (27869 bytes)
Imported modules
Imported symbols
Defined Types
| Nms510UnitCfgEntry |
|
| SEQUENCE |
|
|
|
| |
nms510UnitCfgIndex |
SCinstance |
|
| |
nms510DteCtsDelay |
INTEGER |
|
| |
nms510DteCtsDelayExt |
INTEGER |
|
| |
nms510FirmwareLevel |
DisplayString |
|
| |
nms510AlarmCfgCountWindow |
INTEGER |
|
| |
nms510SoftReset |
INTEGER |
|
| |
nms510FrontPanelInhibit |
INTEGER |
|
| |
nms510FrontPanelEnable |
INTEGER |
|
| |
nms510HdlcInvert |
INTEGER |
|
| |
nms510PiggyBackDetect |
INTEGER |
|
| |
nms510ExtPortCtrlOut1 |
INTEGER |
|
| |
nms510ExtPortCtrlOut2 |
INTEGER |
|
| Nms510AlarmCfgEntry |
|
| SEQUENCE |
|
|
|
| |
nms510AlarmCfgIndex |
SCinstance |
|
| |
nms510AlarmCfgIdentifier |
OBJECT IDENTIFIER |
|
| |
nms510AlarmCfgThreshold |
INTEGER |
|
| Nms510DiagCfgEntry |
|
| SEQUENCE |
|
|
|
| |
nms510DiagCfgIndex |
SCinstance |
|
| |
nms510DiagSendCode |
INTEGER |
|
| |
nms510DiagTestExceptions |
INTEGER |
|
| |
nms510DiagBitErrors |
INTEGER |
|
| |
nms510DiagBlockErrors |
INTEGER |
|
| |
nms510DiagTestReset |
INTEGER |
|
| Nms510DiagExcEntry |
|
| SEQUENCE |
|
|
|
| |
nms510DiagExcIndex |
SCinstance |
|
| |
nms510DiagIntLineloop |
INTEGER |
|
| |
nms510DiagIntDataloop |
INTEGER |
|
| |
nms510DiagEndToEndSelftest |
INTEGER |
|
| |
nms510DiagNetworkDelay |
INTEGER |
|
| |
nms510DiagTestStatus |
INTEGER |
|
| |
nms510DiagExtDataloop |
INTEGER |
|
Defined Values
| nms510 |
1.3.6.1.4.1.498.8.6 |
| OBJECT IDENTIFIER |
|
|
|
| nms510MIBversion |
1.3.6.1.4.1.498.8.6.1 |
| Identifies 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. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(5) |
|
| nms510UnitCfgTable |
1.3.6.1.4.1.498.8.6.2 |
| The NMS510 Unit Configuration table. This table augments the
GDC SC5520 Unit Configuration table, providing unit level configuration
for each NMS510 device installed. For each entry in the GDC SC
Unit Configuration table that represents an NMS510, there is a
corresponding entry here whereby the value of the gdcSCunitCfgIndex
object is equivalent to the value of the nms510unitCfgIndex object. |
| Status: mandatory |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Nms510UnitCfgEntry |
|
| nms510UnitCfgEntry |
1.3.6.1.4.1.498.8.6.2.1 |
| The NMS510 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 NMS510. |
| Status: mandatory |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Nms510UnitCfgEntry |
|
|
| nms510UnitCfgIndex |
1.3.6.1.4.1.498.8.6.2.1.1 |
| The index value which uniquely identifies the NMS510 to which
this entry is applicable. This has the form of a SCinstance
which defines the slot, line, and drop of the NMS510 with no
sub-identifier value. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SCinstance |
|
|
| nms510DteCtsDelay |
1.3.6.1.4.1.498.8.6.2.1.2 |
| RTS/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
nms510DteCtsDelayExt is ignored.
cts0mSec(2) Provides zero bits of delay between active
RTS and CTS being set to active. MIB object
nms510DteCtsDelayExt 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 nms510DteCtsDelayExt must be set to
ext0mSec(1). |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ctsOn(1), cts0mSec(2), ctsFixed3Char(3) |
|
| nms510DteCtsDelayExt |
1.3.6.1.4.1.498.8.6.2.1.3 |
| RTS/CTS Delay options extension
ext0mSec(1) Used to enable options cts0mSec(2) or
ctsFix3Char(3) from MIB object
nms510DteCtsDelay.
ext30mSec(2) Provides 30 msec of delay between active
RTS and CTS being set to active. MIB object
nms510DteCtsDelay 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
nms510DteCtsDelay 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
nms510DteCtsDelay must be set for either
cts0mSec(2) or ctsFix3Char(3). |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ext0mSec(1), ext30mSec(2), ext60mSec(3), ext90mSec(4) |
|
| nms510FirmwareLevel |
1.3.6.1.4.1.498.8.6.2.1.4 |
| The version number of the firmware, to allow products to know which
revision is installed. The released version number is sequenced from
--, A-, ... AA, ... ZZ. Test versions are numerical from 01 to 99. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(2) |
|
| nms510AlarmCfgCountWindow |
1.3.6.1.4.1.498.8.6.2.1.5 |
| The DDS Alarm Threshold Alarm Interval. It specifies the amount of
time in minutes, 1 to 15 minutes, in which the threshold setting is
to be exceeded for the alarm to occur. There is one Alarm Interval
for all alarms that require thresholds: nms510FrameLossAlm. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
1..15 |
|
| nms510SoftReset |
1.3.6.1.4.1.498.8.6.2.1.6 |
| This object will cause software reset in dataset. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), reset(2) |
|
| nms510FrontPanelInhibit |
1.3.6.1.4.1.498.8.6.2.1.7 |
| Inhibits front panel test switch. If a test
switch is activated while inhibited it will simply be ignored.
If enabled via the nms510FrontPanelEnable object the test
switch will function as normal. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
fpInhibited(1), fpEnabled(2), execute(3) |
|
| nms510FrontPanelEnable |
1.3.6.1.4.1.498.8.6.2.1.8 |
| Enables front panel test switch. If a test
switch is activated while inhibited, via the
nms510FrontPanelInhibit object, it will simply be ignored.
If enabled the test switch will function as normal. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
fpInhibited(1), fpEnabled(2), execute(3) |
|
| nms510HdlcInvert |
1.3.6.1.4.1.498.8.6.2.1.9 |
| Primary data invert option. Will enhance the quality of
data when network does not provide B8Z5. Primarily used
with DDS II 56k |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), invert(2) |
|
| nms510PiggyBackDetect |
1.3.6.1.4.1.498.8.6.2.1.10 |
| If set to 2 then either a Data Rate Adadaptor or 530 card is
installed. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
not-installed(1), installed(2) |
|
| nms510ExtPortCtrlOut1 |
1.3.6.1.4.1.498.8.6.2.1.11 |
| This option sets the external output state (on/off) of the
current network element and displays the external output. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
on(1), off(2) |
|
| nms510ExtPortCtrlOut2 |
1.3.6.1.4.1.498.8.6.2.1.12 |
| This option sets the external output state (on/off) of the
current network element and displays the external output. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
on(1), off(2) |
|
| nms510AlarmCfgEntry |
1.3.6.1.4.1.498.8.6.8.1 |
| An entry in the GDC NMS510 alarm Configuration table. |
| Status: mandatory |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Nms510AlarmCfgEntry |
|
|
| nms510AlarmCfgIndex |
1.3.6.1.4.1.498.8.6.8.1.1 |
| This object is the index of the NMS510 Alarm
Threshold Configuration table. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SCinstance |
|
|
| nms510AlarmCfgIdentifier |
1.3.6.1.4.1.498.8.6.8.1.2 |
| The unique alarm identifier assigned to this alarm type. The
format of this identifier is an OBJECT IDENTIFIER that has
the following format: {iso(1) org(3) dod(6) internet(1)
private(4) enterprises(1) gdc(498) xxx(x) alarm(z) yyy(y)
where xxx(x) is the administratively assigned family object
identifier (z) is the object identifier for alarms in the family
defined MIB and yyy(y) is the administratively assigned alarm
type identifier for this alarm. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OBJECT IDENTIFIER |
|
|
| nms510AlarmCfgThreshold |
1.3.6.1.4.1.498.8.6.8.1.3 |
| This function sets/reads the alarm threashold settings criteria.
This threshold is used along with the alarm window to determine
the number of instances in a given time frame for a Frame Loss alarm
to occur before the alarm is considered active. Frame Loss alarm
only reported in DDS-2 line type.
Alarm Table Entry Threshold Range Defaults
------------------ -------------------- -------------- --------
Frame Loss nms510FrameLossAlm 1 to 99 Count 10 |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
0..99 |
|
| nms510DiagCfgEntry |
1.3.6.1.4.1.498.8.6.6.1 |
| The NMS510 Unit Diagonostic table entry. |
| Status: mandatory |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Nms510DiagCfgEntry |
|
|
| nms510DiagCfgIndex |
1.3.6.1.4.1.498.8.6.6.1.1 |
| The index value which uniquely identifies the NMS510 to which
this entry is applicable. This has the form of a SCinstance
which defines the slot, line, and drop of the NMS510 with no
sub-identifier value. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SCinstance |
|
|
| nms510DiagSendCode |
1.3.6.1.4.1.498.8.6.6.1.2 |
| Configures the selftest pattern to be run during any
diagonostic test involving selftest. If option SendOtherPattern is
selected, then pattern will default to 15 bit if unit is set
for 56k-DDS/sc-multi point else pattern will default to 511 bit
for all other conditions |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
sendOtherPattern(1), send511Pattern(2), send2047Pattern(3), send15BitPattern(4) |
|
| nms510DiagTestExceptions |
1.3.6.1.4.1.498.8.6.6.1.3 |
| Indicates exceptions that have occurred that may affect
interpretation of the test results.
The value of this object is a sum. This sum initially take
the value zero. Then, for each exception, the value
associated with the exception is added to the sum.
The exception values are:
value exception
0 No errors
1 bit over range
2 block over range
4 bit and block over range |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
noExceptions(1), blocksOutOfRange(2), bitsOutOfRange(3), blocksAndBitsOutOfRange(4) |
|
| nms510DiagBitErrors |
1.3.6.1.4.1.498.8.6.6.1.4 |
| The bit errors of the last diagnostic test that involved a
Selftest pattern. Reading bit errors while a diagnostic
test in running will cause the unit to drop out of test
and invalidate the bit errors. Bit errors should be read
only after the test is completed. The valid range for bit
errors is 0 to 1,023, 65535 will be returned if for any reason
the test was terminated early. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
0..65535 |
|
| nms510DiagBlockErrors |
1.3.6.1.4.1.498.8.6.6.1.5 |
| The block errors of the last diagnostic test that involved a
Selftest pattern. Reading block errors while a diagnostic
test in running will cause the unit to drop out of test
and invalidate the block errors. Block errors should be read
only after the test is completed. The valid range for block
errors is 0 to 1,023, 65535 will be returned if for any reason
the test was terminated early. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
0..65535 |
|
| nms510DiagTestReset |
1.3.6.1.4.1.498.8.6.6.1.6 |
| This object will halt the execution of any and all
diagnostic test that may be running with the exception
of the Network Delay Test. This should only be used
to terminate the test because reading this object will
terminate the test. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), diagnostic(2), resetTest(3) |
|
| nms510DiagExcEntry |
1.3.6.1.4.1.498.8.6.7.1 |
| The NMS510 Unit Diagonostic table entry. |
| Status: mandatory |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Nms510DiagExcEntry |
|
|
| nms510DiagExcIndex |
1.3.6.1.4.1.498.8.6.7.1.1 |
| The index value which uniquely identifies the NMS510 to which
this entry is applicable. This has the form of a SCinstance
which defines the slot, line, and drop of the NMS510 with no
sub-identifier value. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SCinstance |
|
|
| nms510DiagIntLineloop |
1.3.6.1.4.1.498.8.6.7.1.2 |
| Lineloop (or Analoop) can be either a Bilaterial or Unilaterial
loopback depending on option ddsDteTermaloop. To initiate a
Lineloop with Selftest SET this object and specifiy a
blocksize. The blocksize indicates the number of blocks the
Selftest pattern generator will run. There are 1000 bits/block.
Emuns 3 through 10 are write only. The only valid
responses to a READ are lineloopOn(2) or lineloopOff(1). This test
will terminate after the specified number of blocks have been run.
Reading test results via the nms510DiagBitErrors or nms510DiagBlockErrors
objects while the test is running will cause
the test to terminate prematurely and render the results invalid.
Test results should be only read after the test is completed.
The current Test Status can be obtained by reading this object or the
nms510DiagTestStatus object on the unit under test. This test can
also be terminated by seting the nms510DiagTestReset object. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
lineloopOff(1), lineloopOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) |
|
| nms510DiagIntDataloop |
1.3.6.1.4.1.498.8.6.7.1.3 |
| To initiate a Dataloop with Selftest SET this object and specifiy a
blocksize. The nms510 (the remote) unit will go into Dataloop and
the master (the sc5520) unit will go into Selftest. The blocksize
indicates the number of blocks the Selftest pattern generator will run.
There are 1000 bits/block. Emuns 3 through 10 are write only.
The only valid responses to a READ are dataloopOn(2) or dataloopOff(1).
This test will terminate after the specified number of blocks have been run.
Reading test results via the nms510DiagBitErrors or nms510DiagBlockErrors
objects while the test is running will cause the test to terminate
prematurely and render the results invalid. Test results should be read
only after the test is completed and are available from the master (sc5520)
unit. The current Test Status can be obtained by reading the
sc5520DiagTestStatus object on the master unit, reading test status on the
remote unit may interfere with the diagonostic test pattern and cause errors.
This test can also be terminated by seting the nms510DiagTestReset object. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
dataloopOff(1), dataloopOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) |
|
| nms510DiagEndToEndSelftest |
1.3.6.1.4.1.498.8.6.7.1.4 |
| To initiate an End to End Selftest(Error Rate Test) SET this object
and specifiy a blocksize. Both the remote (nms510)
amd master (sc5520) units will go into Selftest. The blocksize
indicates the number of blocks the Selftest pattern generator will run.
There are 1000 bits/block. Emuns 3 through 10 are write only.
The only valid responses to a READ are selftestOn(2) or selftestOff(1).
This test will terminate after the specified number of blocks have been run.
Reading test results via the nms510DiagBitErrors or nms510DiagBlockErrors
objects while the test is running will cause
the test to terminate prematurely and render the results invalid.
Test results should be read only after the test is completed and are
available from both the remote (nms510) and master (sc5520) units. The
current Test Status can be obtained by reading the sc5520DiagTestStatus
object on the master unit, reading test status on the remote unit may
interfere with the diagonostic test patternand cause errors. This test can
also be terminated by seting the nms510DiagTestReset object. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
endToEndOff(1), endToEndOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) |
|
| nms510DiagNetworkDelay |
1.3.6.1.4.1.498.8.6.7.1.5 |
| To initiate a Network Delay test SET this object and specifiy
runDelayTest. Both the remote (nms510) and master (sc5520) units
will go into a test to measure network delay. Emun 3
is write only. The only valid responses to a READ are delayTestOn(2)
or delayTestOff(1). This test will terminate after 10 seconds.
Test results should be read only after the test is
completed and are available from the master (sc5520) unit. The
current Test Status can be obtained by reading the sc5520DiagTestStatus
object on the master unit, reading test status on the remote unit may
interfere with the test and cause errors. This test can not be
terminated early once it is started. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
delayTestOff(1), delayTestOn(2), runDelayTest(3) |
|
| nms510DiagTestStatus |
1.3.6.1.4.1.498.8.6.7.1.6 |
| This object gives the current diagonostic test status. noTest
indicates that no diagonostic test is currently active. Reading
this object while in a diagonostic test involing two units may
interfere with a selftest pattern and invalidate the test results.
Reading the sc5520DiagTestStatus (master unit) object during
dagonostic tests involing two unit will not disrupt the test
results. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
noTest(1), internalLineloop(2), externalDataloop(3), internalDataloop(4), serviceTestCenterLoop(5), endToend(6) |
|
| nms510DiagExtDataloop |
1.3.6.1.4.1.498.8.6.7.1.7 |
| To initiate a Dataloop test with no Selftest SET this object
and specifiy external, this will allow the data from the DTE attached
to the far end unit (sc5520) to looped back to itself. Emun external(3)
is write only. The only valid response to a READ is dataloopOn(2) or
dataloopOff(1). To halt this test you must SET the nms510DiagTestReset
object. Reading test results via the nms510DiagBitErrors or
nms510DiagBlockErrors objects while the test is running will also cause
the test to terminate. There are no test results associated with this test.
Reading test status on the remote unit via nms510DiagTestStatus may
interfere with the diagonostic test pattern generated from the terminal
equiptment. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
dataloopOff(1), dataloopOn(2), external(3) |
|