Generic-Interface Mib Extensions (Rfc) - Paradyne 3150 Operator's Manual

Generic-Interface MIB
Extensions (RFC 1229)
The generic-interface MIB is an experimental MIB that
provides extensions to the generic interface group defined
in MIB II. This MIB describes three tables:
Generic Interface Extension Table
Generic Interface Test Table
Generic Receive Address Table
Only the generic interface test table is supported by the
CSU. This table is supported for the network interface
only.
Generic Interface Test Table, Generic
Interface MIB
The test table provides access to additional tests
(loopbacks and pattern tests) that are not in the interface
group of MIB II.
Generic Interface Test Table – "ifExtnsTestType"
Object (ifExtnsTestEntry 4)
This object is a control variable used to start and stop
operator-initiated tests on the interface. It provides the
capability to:
Start/stop the Monitor QRSS test pattern on the
network interface.
The following object identifiers are used to control the
tests on the interface.
noTest – Stops the test in progress on the interface.
testMonQRSS – Initiates a Monitor QRSS test on
the interface. Supported for the network interface.
Where these object identifiers are defined as follows:
testMonQRSS – OBJECT IDENTIFIER ::=
[wellKnownTests 3]
Generic Interface Test Table –
"ifExtnsTestResult" Object (ifExtnsTestEntry 5)
This object contains the result of the most recently
requested test. Only the following values are supported by
the CSU.
none(1) – No test currently active.
3150-A2-GB21-80
inProgress(3) – A test is currently in progress.
notSupported(4) – The requested test is not
supported.
unAbleToRun(5) – The requested test cannot run
due to the state of the unit.
Generic Interface Test Table –
"ifExtnsTestCode" Object
(ifExtnsTestEntry 6)
This object contains a code that contains more specific
information on the test result. This object is defined as an
object identifier. Only the following values are supported
by the CSU.
none – No further information is available. Used for
the send pattern/code and loopback tests.
inSyncNoBitErrors – A monitor pattern (QRSS or
511) test has synchronized on the pattern and has
not detected any bit errors.
inSyncWithBitErrors – A monitor pattern (QRSS or
511) test has synchronized on the pattern and has
detected bit errors.
notInSync – A monitor pattern (QRSS or 511) test
has not synchronized on the requested pattern.
Where these object identifiers are defined as follows:
wellKnownCodes – OBJECT IDENTIFIER ::=
[ifExtensions 5]
none – OBJECT IDENTIFIER ::=
[wellKnownCodes 1]
inSyncNoBitErrors – OBJECT IDENTIFIER ::=
[wellKnownCodes 2]
inSyncWithBitErrors – OBJECT IDENTIFIER ::=
[wellKnownCodes 3]
notInSync – OBJECT IDENTIFIER ::=
[wellKnownCodes 4]
February 1998
SNMP MIB Objects
E-13