Paradyne 3150 Operator's Manual

Also see for 3151: Quick installation Release note Information guide Quick reference Quick reference

Contents

Paradyne 3150 Operator's Manual Manual pdf 124 page image

SNMP MIB ObjectsE-133150-A2-GB21-80 February 1998Generic-Interface MIBExtensions (RFC 1229)The generic-interface MIB is an experimental MIB thatprovides extensions to the generic interface group definedin MIB II. This MIB describes three tables:• Generic Interface Extension Table• Generic Interface Test Table• Generic Receive Address TableOnly the generic interface test table is supported by theCSU. This table is supported for the network interfaceonly.Generic Interface Test Table, GenericInterface MIBThe test table provides access to additional tests(loopbacks and pattern tests) that are not in the interfacegroup of MIB II.Generic Interface Test Table – “ifExtnsTestType”Object (ifExtnsTestEntry 4)This object is a control variable used to start and stopoperator-initiated tests on the interface. It provides thecapability to:• Start/stop the Monitor QRSS test pattern on thenetwork interface.The following object identifiers are used to control thetests on the interface.• noTest – Stops the test in progress on the interface.• testMonQRSS – Initiates a Monitor QRSS test onthe 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 recentlyrequested test. Only the following values are supported bythe CSU.• none(1) – No test currently active.• inProgress(3) – A test is currently in progress.• notSupported(4) – The requested test is notsupported.• unAbleToRun(5) – The requested test cannot rundue to the state of the unit.Generic Interface Test Table –“ifExtnsTestCode” Object(ifExtnsTestEntry 6)This object contains a code that contains more specificinformation on the test result. This object is defined as anobject identifier. Only the following values are supportedby the CSU.• none – No further information is available. Used forthe send pattern/code and loopback tests.• inSyncNoBitErrors – A monitor pattern (QRSS or511) test has synchronized on the pattern and hasnot detected any bit errors.• inSyncWithBitErrors – A monitor pattern (QRSS or511) test has synchronized on the pattern and hasdetected bit errors.• notInSync – A monitor pattern (QRSS or 511) testhas 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]