C. Traps and MIBs

Device Diagnostics MIB

Objects supported by the Device Diagnostics MIB, pdn_diag.mib, include the Application Test Input Group (Ping and TraceRoute) and Test Traps, providing an NMS a trigger for a diagnostic test.

To start a test from NMS, you must obtain the Test ID by performing a Get. This Test ID is then used as the index when setting the parameters via objects in the Application Test Table. Refer to the applNewTestId object in Table C-8, Application Test Group Objects.

Table C-8. Application Test Group Objects (1 of 3)

Object

Description

Setting/Contents

 

 

 

applMaxNumberOfTests

The number of application-based

The DSL router only supports one test.

(applTest 1)

tests that can be started on the

 

 

device.

 

 

 

 

applCurrentNumberOfTests

The number of application-based

The DSL router only supports one test at a

(applTest 2)

tests that are currently running on

time.

 

the device.

 

 

 

 

applStopAllTests

Initiates the clearing of all

noOp – No operation.

(applTest 3)

application-based tests.

stop – All tests are stopped and current

 

 

 

 

test results remain available.

 

 

stopAndClear – All tests are

 

 

stopped and all test results are

 

 

cleared.

 

 

 

applNewTestId

To start a test from NMS,

￿nnn – Existing unused test ID.

(applTest 4)

complete a Get on this object to

0 (zero) – A test ID cannot be assigned

 

obtain the test ID. Note that this

 

at this time.

 

invalidates any existing test

 

 

 

information for Ping, TraceRoute,

 

 

and Test Status tables.

 

 

 

 

applTestId

Contains identifiers that allow

Contains applNewTestID after Get.

(testStatusEntry 1)

NMS to find the most recent test.

 

 

 

 

applTestType

Indicates the test type assigned to

1.3.6.4.1795.1.14.5.1.3 – Ping Test

(testStatusEntry 2)

this object.

Type.

 

 

1.3.6.4.1795.1.14.5.1.4 – TraceRoute

 

 

Test Type.

 

 

 

applTestStatus

Indicates the test status.

none(1) – No active test.

(testStatusEntry 3)

 

inProgress(2) – Active test.

 

 

 

 

success(3) – Test completed.

 

 

￿failed(4) – Test failed.

 

 

abort(5) – Test aborted.

 

 

 

6300-A2-GB20-10

November 2003

C-13

Page 127
Image 127
Paradyne 6301, 6341, 6342, 6371, 6351, 6302 manual Device Diagnostics MIB, Ping Test, TraceRoute, InProgress2 Active test