This table is used to initiate linktests between
an AP and one of its associated clients. CCX
linktests are done on clients that support CCX. For
all non-CCX clients, ping test is done. Note that
ping test is also done when the CCX linktests fail.
With CCX LinkTest support, the controller can test
the link quality in downstream (direction of
traffic from AP to client) direction by issuing
LinkTest requests towards the client and let client
record in the response packet the RF parameters
like received signal strength, signal-to-noise
etc., of the received request packet.
With ping test only those RF parameters that are
seen by the AP are measured.
User initiates one run of linktest by adding a
row to this table through explicit management
action from the network manager. A row is created
by specifying cLLtClientLtIndex,
cLLtClientLtMacAddress and setting the RowStatus
object to 'createAndGo'. This indicates the
the request made to start the linktest on the
client identified by cLLtClientLtMacAddress.
cLLtClientLtIndex identifies the particular
instance of the test.
The added row is deleted by setting the corresponding
instance of the RowStatus object to 'destroy'. In
case if the agent finds that the time duration
represented by cLLtTestPurgeTime has elapsed since
the completion of the linktest, it proceeds to
delete the row automatically, if the row exists at
that point of time.
The results of the linktest identified by
cLLtClientLtIndex can be obtained from the
queries to cLLtClientLtResultsTable.
Parsed from file CISCO-LWAPP-LINKTEST-MIB.mib
Module: CISCO-LWAPP-LINKTEST-MIB
This table is used to initiate linktests between
an AP and one of its associated clients. CCX
linktests are done on clients that support CCX. For
all non-CCX clients, ping test is done. Note that
ping test is also done when the CCX linktests fail.
With CCX LinkTest support, the controller can test
the link quality in downstream (direction of
traffic from AP to client) direction by issuing
LinkTest requests towards the client and let client
record in the response packet the RF parameters
like received signal strength, signal-to-noise
etc., of the received request packet.
With ping test only those RF parameters that are
seen by the AP are measured.
User initiates one run of linktest by adding a
row to this table through explicit management
action from the network manager. A row is created
by specifying cLLtClientLtIndex,
cLLtClientLtMacAddress and setting the RowStatus
object to 'createAndGo'. This indicates the
the request made to start the linktest on the
client identified by cLLtClientLtMacAddress.
cLLtClientLtIndex identifies the particular
instance of the test.
The added row is deleted by setting the corresponding
instance of the RowStatus object to 'destroy'. In
case if the agent finds that the time duration
represented by cLLtTestPurgeTime has elapsed since
the completion of the linktest, it proceeds to
delete the row automatically, if the row exists at
that point of time.
The results of the linktest identified by
cLLtClientLtIndex can be obtained from the
queries to cLLtClientLtResultsTable.
This table is used to initiate linktests between
an AP and one of its associated clients. CCX
linktests are done on clients that support CCX. For
all non-CCX clients, ping test is done. Note that
ping test is also done when the CCX linktests fail.
With CCX LinkTest support, the controller can test
the link quality in downstream (direction of
traffic from AP to client) direction by issuing
LinkTest requests towards the client and let client
record in the response packet the RF parameters
like received signal strength, signal-to-noise
etc., of the received request packet.
With ping test only those RF parameters that are
seen by the AP are measured.
User initiates one run of linktest by adding a
row to this table through explicit management
action from the network manager. A row is created
by specifying cLLtClientLtIndex,
cLLtClientLtMacAddress and setting the RowStatus
object to 'createAndGo'. This indicates the
the request made to start the linktest on the
client identified by cLLtClientLtMacAddress.
cLLtClientLtIndex identifies the particular
instance of the test.
The added row is deleted by setting the corresponding
instance of the RowStatus object to 'destroy'. In
case if the agent finds that the time duration
represented by cLLtTestPurgeTime has elapsed since
the completion of the linktest, it proceeds to
delete the row automatically, if the row exists at
that point of time.
The results of the linktest identified by
cLLtClientLtIndex can be obtained from the
queries to cLLtClientLtResultsTable.
Parsed from file CISCO-LWAPP-LINKTEST-MIB.my.txt
Company: None
Module: CISCO-LWAPP-LINKTEST-MIB
This table is used to initiate linktests between
an AP and one of its associated clients. CCX
linktests are done on clients that support CCX. For
all non-CCX clients, ping test is done. Note that
ping test is also done when the CCX linktests fail.
With CCX LinkTest support, the controller can test
the link quality in downstream (direction of
traffic from AP to client) direction by issuing
LinkTest requests towards the client and let client
record in the response packet the RF parameters
like received signal strength, signal-to-noise
etc., of the received request packet.
With ping test only those RF parameters that are
seen by the AP are measured.
User initiates one run of linktest by adding a
row to this table through explicit management
action from the network manager. A row is created
by specifying cLLtClientLtIndex,
cLLtClientLtMacAddress and setting the RowStatus
object to 'createAndGo'. This indicates the
the request made to start the linktest on the
client identified by cLLtClientLtMacAddress.
cLLtClientLtIndex identifies the particular
instance of the test.
The added row is deleted by setting the corresponding
instance of the RowStatus object to 'destroy'. In
case if the agent finds that the time duration
represented by cLLtTestPurgeTime has elapsed since
the completion of the linktest, it proceeds to
delete the row automatically, if the row exists at
that point of time.
The results of the linktest identified by
cLLtClientLtIndex can be obtained from the
queries to cLLtClientLtResultsTable.
cLLtClientLinkTestTable OBJECT-TYPE SYNTAX SEQUENCE OF CLLtClientLinkTestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is used to initiate linktests between an AP and one of its associated clients. CCX linktests are done on clients that support CCX. For all non-CCX clients, ping test is done. Note that ping test is also done when the CCX linktests fail. With CCX LinkTest support, the controller can test the link quality in downstream (direction of traffic from AP to client) direction by issuing LinkTest requests towards the client and let client record in the response packet the RF parameters like received signal strength, signal-to-noise etc., of the received request packet. With ping test only those RF parameters that are seen by the AP are measured. User initiates one run of linktest by adding a row to this table through explicit management action from the network manager. A row is created by specifying cLLtClientLtIndex, cLLtClientLtMacAddress and setting the RowStatus object to 'createAndGo'. This indicates the the request made to start the linktest on the client identified by cLLtClientLtMacAddress. cLLtClientLtIndex identifies the particular instance of the test. The added row is deleted by setting the corresponding instance of the RowStatus object to 'destroy'. In case if the agent finds that the time duration represented by cLLtTestPurgeTime has elapsed since the completion of the linktest, it proceeds to delete the row automatically, if the row exists at that point of time. The results of the linktest identified by cLLtClientLtIndex can be obtained from the queries to cLLtClientLtResultsTable. " ::= { ciscoLwappLinkTestRun 1 }
cLLtClientLinkTestTable OBJECT-TYPE SYNTAX SEQUENCE OF CLLtClientLinkTestEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table is used to initiate linktests between an AP and one of its associated clients. CCX linktests are done on clients that support CCX. For all non-CCX clients, ping test is done. Note that ping test is also done when the CCX linktests fail. With CCX LinkTest support, the controller can test the link quality in downstream (direction of traffic from AP to client) direction by issuing LinkTest requests towards the client and let client record in the response packet the RF parameters like received signal strength, signal-to-noise etc., of the received request packet. With ping test only those RF parameters that are seen by the AP are measured. User initiates one run of linktest by adding a row to this table through explicit management action from the network manager. A row is created by specifying cLLtClientLtIndex, cLLtClientLtMacAddress and setting the RowStatus object to 'createAndGo'. This indicates the the request made to start the linktest on the client identified by cLLtClientLtMacAddress. cLLtClientLtIndex identifies the particular instance of the test. The added row is deleted by setting the corresponding instance of the RowStatus object to 'destroy'. In case if the agent finds that the time duration represented by cLLtTestPurgeTime has elapsed since the completion of the linktest, it proceeds to delete the row automatically, if the row exists at that point of time. The results of the linktest identified by cLLtClientLtIndex can be obtained from the queries to cLLtClientLtResultsTable. " ::= { ciscoLwappLinkTestRun 1 }
Vendor: Cisco
Module: CISCO-LWAPP-LINKTEST-MIB
[Automatically extracted from oidview.com]
cLLtClientLinkTestTable OBJECT-TYPE SYNTAX SEQUENCE OF CLLtClientLinkTestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is used to initiate linktests between an AP and one of its associated clients. CCX linktests are done on clients that support CCX. For all non-CCX clients, ping test is done. Note that ping test is also done when the CCX linktests fail. With CCX LinkTest support, the controller can test the link quality in downstream (direction of traffic from AP to client) direction by issuing LinkTest requests towards the client and let client record in the response packet the RF parameters like received signal strength, signal-to-noise etc., of the received request packet. With ping test only those RF parameters that are seen by the AP are measured. User initiates one run of linktest by adding a row to this table through explicit management action from the network manager. A row is created by specifying cLLtClientLtIndex, cLLtClientLtMacAddress and setting the RowStatus object to 'createAndGo'. This indicates the the request made to start the linktest on the client identified by cLLtClientLtMacAddress. cLLtClientLtIndex identifies the particular instance of the test. The added row is deleted by setting the corresponding instance of the RowStatus object to 'destroy'. In case if the agent finds that the time duration represented by cLLtTestPurgeTime has elapsed since the completion of the linktest, it proceeds to delete the row automatically, if the row exists at that point of time. The results of the linktest identified by cLLtClientLtIndex can be obtained from the queries to cLLtClientLtResultsTable. " ::= { ciscoLwappLinkTestRun 1 }
cLLtClientLinkTestTable OBJECT-TYPE SYNTAX SEQUENCE OF CLLtClientLinkTestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is used to initiate linktests between an AP and one of its associated clients. CCX linktests are done on clients that support CCX. For all non-CCX clients, ping test is done. Note that ping test is also done when the CCX linktests fail. With CCX LinkTest support, the controller can test the link quality in downstream (direction of traffic from AP to client) direction by issuing LinkTest requests towards the client and let client record in the response packet the RF parameters like received signal strength, signal-to-noise etc., of the received request packet. With ping test only those RF parameters that are seen by the AP are measured. User initiates one run of linktest by adding a row to this table through explicit management action from the network manager. A row is created by specifying cLLtClientLtIndex, cLLtClientLtMacAddress and setting the RowStatus object to 'createAndGo'. This indicates the the request made to start the linktest on the client identified by cLLtClientLtMacAddress. cLLtClientLtIndex identifies the particular instance of the test. The added row is deleted by setting the corresponding instance of the RowStatus object to 'destroy'. In case if the agent finds that the time duration represented by cLLtTestPurgeTime has elapsed since the completion of the linktest, it proceeds to delete the row automatically, if the row exists at that point of time. The results of the linktest identified by cLLtClientLtIndex can be obtained from the queries to cLLtClientLtResultsTable. " ::= { ciscoLwappLinkTestRun 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.516.1.2.1.1 | cLLtClientLinkTestEntry | 3 | 3 | Each entry in this table represents one instance of the linktest initiated by the user through a network manager. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.516.1.2.2 | cLLtClientLTResultsTable | 1 | 26 | This table populates the results of the linktests initiated by the user through the cLLtClientLinkTestTable. This table has a spar… |