PDN-ADSL-SELT-MIB: View SNMP OID List / Download MIB

This MIB module defines a portion of the management information base (MIB) for managing configuration and monitoring results of SELT (Single Ended Line Test) tests over ADSL interfaces. At the time this MIB was defined, the IETF ADSL MIB Working does not have any work on the 'standard' MIBs planned and/or has not produced a schedule to address G.SELT needs. As a result, these objects may be a `temporary' solution until MIBs/Objects are defined meet the needs of ADSL SELT testing. ===================================================================== == == == Copyright (C) 2005 Paradyne Corporation. == == == =====================================================================

This object permits the selection of the metric unit to be used when reporting SELT test results. (i.e for AWG results are in feet and for metric/metricJapan results are in meters). This configuration parameter applies to all the SELT tests run in the device. Enumeration: 'awg': 1, 'metric': 2, 'metricJapan': 3.

This table allows initiation/termination of SELT Tests.

Each entry represents an instance of a SELT test currently running or ever run (since last system reset) on an ADSL interface. There should be entries in this table for every active running tests and test that are in the process of being stopped or have terminated already. There should be no entries for ADSL interfaces that have not run a test since last since reset; thus, the agent should return NO_SUCH_NAME for those cases.

This object is used to specify the SELT test type that will be initiated. If a SELT Test is already running on the ADSL interface, writing to this object is prohibited by the agent until the previous test is completed or terminated.

This object corresponds to the list of test operations that can be performed. The possible values are noOp(1), start(2), stop(3), or clearResults(4). Reading this object will always return the value 'noOp (1)'. If SELT test is already running on an ADSL interface, the only possible test command is 'stop (1)'. The clearResults(4) command clears test results by removing and entry in the pdnAdslSeltLcTable or the pdnAdslSeltLnfTable. After the execution of this command, the appropriate value for pdnAdslSeltStatus would be resultsCleared(5). Enumeration: 'stop': 3, 'start': 2, 'clearResults': 4, 'noOp': 1.

This object provides status about any SELT test running or ever run (since last reset) on an ADSL interface. This object can be read by NMS managers to determine the status of a test; that is: inProgress (1) - if the test is currently running. stoppedInProgress (2) - if a request to stop the test is still in progress. complete (3) - if the test has been run at least once since system reset and has completed. notStarted (4) - if the test has not been run on this interface since last system reset. resultsCleared (5) - if the entry in the test results table, Lc or Lnf, was removed as the result of the execution of the clearResults(4) pdnAdslSeltCmd. Enumeration: 'resultsCleared': 5, 'inProgress': 1, 'notStarted': 4, 'complete': 3, 'stoppedInProgress': 2.

This object provides the approximate time in Seconds that the SELT test measurement will take. This object should return 0 if no test is actively running on the ADSL interface specified.

This object provides the approximate time left in Seconds for the test running on this ADSL interface. This object should return 0 if no test is actively running on the ADSL interface specified.

This table post results for loop characterization tests completed.

Each entry represents the results of a loop characterization test performed over an ADSL interface.

This object indicates the index of the segment being reported. From no segments to a possible of 10 segments could be identified in the loop topology.

This object indicates an estimate of the segment Length being reported

This object indicates the estimated Gauge of the segment being reported. The gauge reported back is based on the pdnAdslSeltWireSizeWireSize configuration parameter passed when the test is started. Enumeration: 'metricJapan65': 23, 'metric40': 11, 'unknown': 1, 'metricJapan50': 22, 'metric50': 12, 'metric63': 13, 'metricJapan32': 20, 'metric90': 14, 'metricJapan90': 24, 'metricJapan40': 21, 'awg24': 3, 'awg26': 2, 'awg19': 5, 'awg22': 4, 'metric32': 10.

This object indicates the segment type being reported. Enumeration: 'inline': 2, 'notPresent': 1, 'bridgeTap': 3.

This table post results for loop noise floor tests completed.

Each entry represents the results of a Loop Noise Floor test performed over an ADSL interface.

Identifies a row in the table based on a subcarrier. The subcarrier index ranges from 0 to NSCus-1 (NSC is Number of Subcarriers) as specified in G.997.1 where NSCus is the higher subcarrier that can be transmitted in the upstream direction. Please refer to the corresponding ITU recommendation for specific values of NSCus. The `ADSL Values for NSC' comment above lists those recommendations.

This object indicates the peak Psd of the tone indicated by the sub-carrier index. The value returned by the agent for this object is expressed in units of 1/256 dBm.

This object indicates the total Psd of the tone indicated by the sub-carrier index. The value returned by the agent for this object is expressed in units of 1/256 dBm.

This object indicates the signal Psd of the tone indicated by the sub-carrier index. The value returned by the agent for this object is expressed in units of 1/256 dBm.

The compliance statement for the entities which implement the pdnAdslSeltMIB.

General configuration of SELT tests.

Objects related to results posted for Loop Characterization Test.

Objects related to results posted for Loop Signal Floor Test.