Reference record for OID 1.3.6.1.4.1.9.9.525.1.2.2



parent
1.3.6.1.4.1.9.9.525.1.2 (ciscoLwappTsmDot11Stats)
node code
2
node name
cLTsmDot11UplinkTable
dot oid
1.3.6.1.4.1.9.9.525.1.2.2
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappTsmMIB(525) ciscoLwappTsmMIBObjects(1) ciscoLwappTsmDot11Stats(2) cLTsmDot11UplinkTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappTsmMIB(525) ciscoLwappTsmMIBObjects(1) ciscoLwappTsmDot11Stats(2) cLTsmDot11UplinkTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappTsmMIB(525) ciscoLwappTsmMIBObjects(1) ciscoLwappTsmDot11Stats(2) cLTsmDot11UplinkTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappTsmMIB(525) ciscoLwappTsmMIBObjects(1) ciscoLwappTsmDot11Stats(2) cLTsmDot11UplinkTable(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappTsmMIB(525) ciscoLwappTsmMIBObjects(1) ciscoLwappTsmDot11Stats(2) cLTsmDot11UplinkTable(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappTsmMIB(525) ciscoLwappTsmMIBObjects(1) ciscoLwappTsmDot11Stats(2) cLTsmDot11UplinkTable(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappTsmMIB/ciscoLwappTsmMIBObjects/ciscoLwappTsmDot11Stats/cLTsmDot11UplinkTable
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappTsmMIB/ciscoLwappTsmMIBObjects/ciscoLwappTsmDot11Stats/cLTsmDot11UplinkTable
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappTsmMIB/ciscoLwappTsmMIBObjects/ciscoLwappTsmDot11Stats/cLTsmDot11UplinkTable
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappTsmMIB/ciscoLwappTsmMIBObjects/ciscoLwappTsmDot11Stats/cLTsmDot11UplinkTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappTsmMIB/ciscoLwappTsmMIBObjects/ciscoLwappTsmDot11Stats/cLTsmDot11UplinkTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappTsmMIB/ciscoLwappTsmMIBObjects/ciscoLwappTsmDot11Stats/cLTsmDot11UplinkTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/525/1/2/2

    Description by circitor

    This table represents the statistics received by the
    controller from the associated APs, on the uplink
    traffic ( traffic from the 802.11 wireless client to
    the AP ) observed on the dot11 interfaces of the
    respective APs.

    For example, suppose a client with address
    12:3f:73:99:de:5b connects to the 802.11 radio
    interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours.

    Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig)
    is set to 'true' for the respective type of interface,
    every 90 seconds, AP sends the controller statistical
    data for the client 12:3f:73:99:de:5b associated at the
    interface 13:13:43:de:bb:ff.

    So, after 3 minutes, i.e., 180 seconds, controller would
    have received statistics for the particular client and
    AP combination twice leading to two rows in this table
    as follows.

    1> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    2> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    Now assume that, at 18:33:00, the client moves and
    associates with another AP associated to the same
    controller, at the AP's 802.11 interface
    14:14:43:de:dd:ee.

    After 3 minutes, i.e., 180 seconds (say), controller
    would have again received statistics from the AP, for
    the particular client and new AP combination twice
    leading to two new rows in this table.

    At this point, this table will have entries with
    following references :

    1> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:36:00

    2> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:34:30

    3> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    4> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    The maximum number of entries in this table is
    indicated by cLTsmDot11MaxTsmStatsEntries. When
    the specified limit of entries is reached the oldest
    entries will be removed to make room for new entries.
    However, the controller may remove the entries if it
    encounters memory shortage.

    Parsed from file CISCO-LWAPP-TSM-MIB.mib
    Module: CISCO-LWAPP-TSM-MIB

    Description by cisco_v1

    This table represents the statistics received by the
    controller from the associated APs, on the uplink
    traffic ( traffic from the 802.11 wireless client to
    the AP ) observed on the dot11 interfaces of the
    respective APs.

    For example, suppose a client with address
    12:3f:73:99:de:5b connects to the 802.11 radio
    interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours.

    Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig)
    is set to 'true' for the respective type of interface,
    every 90 seconds, AP sends the controller statistical
    data for the client 12:3f:73:99:de:5b associated at the
    interface 13:13:43:de:bb:ff.

    So, after 3 minutes, i.e., 180 seconds, controller would
    have received statistics for the particular client and
    AP combination twice leading to two rows in this table
    as follows.

    1> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    2> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    Now assume that, at 18:33:00, the client moves and
    associates with another AP associated to the same
    controller, at the AP's 802.11 interface
    14:14:43:de:dd:ee.

    After 3 minutes, i.e., 180 seconds (say), controller
    would have again received statistics from the AP, for
    the particular client and new AP combination twice
    leading to two new rows in this table.

    At this point, this table will have entries with
    following references :

    1> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:36:00

    2> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:34:30

    3> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    4> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    The maximum number of entries in this table is
    indicated by cLTsmDot11MaxTsmStatsEntries. When
    the specified limit of entries is reached the oldest
    entries will be removed to make room for new entries.
    However, the controller may remove the entries if it
    encounters memory shortage.

    Description by mibdepot

    This table represents the statistics received by the
    controller from the associated APs, on the uplink
    traffic ( traffic from the 802.11 wireless client to
    the AP ) observed on the dot11 interfaces of the
    respective APs.

    For example, suppose a client with address
    12:3f:73:99:de:5b connects to the 802.11 radio
    interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours.

    Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig)
    is set to 'true' for the respective type of interface,
    every 90 seconds, AP sends the controller statistical
    data for the client 12:3f:73:99:de:5b associated at the
    interface 13:13:43:de:bb:ff.

    So, after 3 minutes, i.e., 180 seconds, controller would
    have received statistics for the particular client and
    AP combination twice leading to two rows in this table
    as follows.

    1> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    2> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    Now assume that, at 18:33:00, the client moves and
    associates with another AP associated to the same
    controller, at the AP's 802.11 interface
    14:14:43:de:dd:ee.

    After 3 minutes, i.e., 180 seconds (say), controller
    would have again received statistics from the AP, for
    the particular client and new AP combination twice
    leading to two new rows in this table.

    At this point, this table will have entries with
    following references :

    1> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:36:00

    2> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:34:30

    3> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    4> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    The maximum number of entries in this table is
    indicated by cLTsmDot11MaxTsmStatsEntries. When
    the specified limit of entries is reached the oldest
    entries will be removed to make room for new entries.
    However, the controller may remove the entries if it
    encounters memory shortage.

    Parsed from file CISCO-LWAPP-TSM-MIB.my.txt
    Company: None
    Module: CISCO-LWAPP-TSM-MIB

    Description by cisco

    This table represents the statistics received by the
    controller from the associated APs, on the uplink
    traffic ( traffic from the 802.11 wireless client to
    the AP ) observed on the dot11 interfaces of the
    respective APs.

    For example, suppose a client with address
    12:3f:73:99:de:5b connects to the 802.11 radio
    interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours.

    Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig)
    is set to 'true' for the respective type of interface,
    every 90 seconds, AP sends the controller statistical
    data for the client 12:3f:73:99:de:5b associated at the
    interface 13:13:43:de:bb:ff.

    So, after 3 minutes, i.e., 180 seconds, controller would
    have received statistics for the particular client and
    AP combination twice leading to two rows in this table
    as follows.

    1> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    2> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    Now assume that, at 18:33:00, the client moves and
    associates with another AP associated to the same
    controller, at the AP's 802.11 interface
    14:14:43:de:dd:ee.

    After 3 minutes, i.e., 180 seconds (say), controller
    would have again received statistics from the AP, for
    the particular client and new AP combination twice
    leading to two new rows in this table.

    At this point, this table will have entries with
    following references :

    1> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:36:00

    2> Client: 12:3f:73:99:de:5b
    Interface:14:14:43:de:dd:ee Time: 18:34:30

    3> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:33:00

    4> Client: 12:3f:73:99:de:5b
    Interface:13:13:43:de:bb:ff Time: 18:31:30

    The maximum number of entries in this table is
    indicated by cLTsmDot11MaxTsmStatsEntries. When
    the specified limit of entries is reached the oldest
    entries will be removed to make room for new entries.
    However, the controller may remove the entries if it
    encounters memory shortage.

    Information by circitor

    cLTsmDot11UplinkTable OBJECT-TYPE SYNTAX SEQUENCE OF CLTsmDot11UplinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table represents the statistics received by the controller from the associated APs, on the uplink traffic ( traffic from the 802.11 wireless client to the AP ) observed on the dot11 interfaces of the respective APs. For example, suppose a client with address 12:3f:73:99:de:5b connects to the 802.11 radio interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours. Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig) is set to 'true' for the respective type of interface, every 90 seconds, AP sends the controller statistical data for the client 12:3f:73:99:de:5b associated at the interface 13:13:43:de:bb:ff. So, after 3 minutes, i.e., 180 seconds, controller would have received statistics for the particular client and AP combination twice leading to two rows in this table as follows. 1> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 2> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 Now assume that, at 18:33:00, the client moves and associates with another AP associated to the same controller, at the AP's 802.11 interface 14:14:43:de:dd:ee. After 3 minutes, i.e., 180 seconds (say), controller would have again received statistics from the AP, for the particular client and new AP combination twice leading to two new rows in this table. At this point, this table will have entries with following references : 1> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:36:00 2> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:34:30 3> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 4> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 The maximum number of entries in this table is indicated by cLTsmDot11MaxTsmStatsEntries. When the specified limit of entries is reached the oldest entries will be removed to make room for new entries. However, the controller may remove the entries if it encounters memory shortage. " ::= { ciscoLwappTsmDot11Stats 2 }

    Information by cisco_v1

    cLTsmDot11UplinkTable OBJECT-TYPE SYNTAX SEQUENCE OF CLTsmDot11UplinkEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table represents the statistics received by the controller from the associated APs, on the uplink traffic ( traffic from the 802.11 wireless client to the AP ) observed on the dot11 interfaces of the respective APs. For example, suppose a client with address 12:3f:73:99:de:5b connects to the 802.11 radio interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours. Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig) is set to 'true' for the respective type of interface, every 90 seconds, AP sends the controller statistical data for the client 12:3f:73:99:de:5b associated at the interface 13:13:43:de:bb:ff. So, after 3 minutes, i.e., 180 seconds, controller would have received statistics for the particular client and AP combination twice leading to two rows in this table as follows. 1> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 2> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 Now assume that, at 18:33:00, the client moves and associates with another AP associated to the same controller, at the AP's 802.11 interface 14:14:43:de:dd:ee. After 3 minutes, i.e., 180 seconds (say), controller would have again received statistics from the AP, for the particular client and new AP combination twice leading to two new rows in this table. At this point, this table will have entries with following references : 1> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:36:00 2> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:34:30 3> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 4> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 The maximum number of entries in this table is indicated by cLTsmDot11MaxTsmStatsEntries. When the specified limit of entries is reached the oldest entries will be removed to make room for new entries. However, the controller may remove the entries if it encounters memory shortage." ::= { ciscoLwappTsmDot11Stats 2 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-LWAPP-TSM-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    cLTsmDot11UplinkTable OBJECT-TYPE SYNTAX SEQUENCE OF CLTsmDot11UplinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table represents the statistics received by the controller from the associated APs, on the uplink traffic ( traffic from the 802.11 wireless client to the AP ) observed on the dot11 interfaces of the respective APs. For example, suppose a client with address 12:3f:73:99:de:5b connects to the 802.11 radio interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours. Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig) is set to 'true' for the respective type of interface, every 90 seconds, AP sends the controller statistical data for the client 12:3f:73:99:de:5b associated at the interface 13:13:43:de:bb:ff. So, after 3 minutes, i.e., 180 seconds, controller would have received statistics for the particular client and AP combination twice leading to two rows in this table as follows. 1> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 2> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 Now assume that, at 18:33:00, the client moves and associates with another AP associated to the same controller, at the AP's 802.11 interface 14:14:43:de:dd:ee. After 3 minutes, i.e., 180 seconds (say), controller would have again received statistics from the AP, for the particular client and new AP combination twice leading to two new rows in this table. At this point, this table will have entries with following references : 1> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:36:00 2> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:34:30 3> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 4> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 The maximum number of entries in this table is indicated by cLTsmDot11MaxTsmStatsEntries. When the specified limit of entries is reached the oldest entries will be removed to make room for new entries. However, the controller may remove the entries if it encounters memory shortage. " ::= { ciscoLwappTsmDot11Stats 2 }

    Information by cisco

    cLTsmDot11UplinkTable OBJECT-TYPE SYNTAX SEQUENCE OF CLTsmDot11UplinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table represents the statistics received by the controller from the associated APs, on the uplink traffic ( traffic from the 802.11 wireless client to the AP ) observed on the dot11 interfaces of the respective APs. For example, suppose a client with address 12:3f:73:99:de:5b connects to the 802.11 radio interface, 13:13:43:de:bb:ff of an AP at 18:30:00 hours. Assuming that cLTsmDot11aConfig (or cLTsmDot11bConfig) is set to 'true' for the respective type of interface, every 90 seconds, AP sends the controller statistical data for the client 12:3f:73:99:de:5b associated at the interface 13:13:43:de:bb:ff. So, after 3 minutes, i.e., 180 seconds, controller would have received statistics for the particular client and AP combination twice leading to two rows in this table as follows. 1> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 2> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 Now assume that, at 18:33:00, the client moves and associates with another AP associated to the same controller, at the AP's 802.11 interface 14:14:43:de:dd:ee. After 3 minutes, i.e., 180 seconds (say), controller would have again received statistics from the AP, for the particular client and new AP combination twice leading to two new rows in this table. At this point, this table will have entries with following references : 1> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:36:00 2> Client: 12:3f:73:99:de:5b Interface:14:14:43:de:dd:ee Time: 18:34:30 3> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:33:00 4> Client: 12:3f:73:99:de:5b Interface:13:13:43:de:bb:ff Time: 18:31:30 The maximum number of entries in this table is indicated by cLTsmDot11MaxTsmStatsEntries. When the specified limit of entries is reached the oldest entries will be removed to make room for new entries. However, the controller may remove the entries if it encounters memory shortage." ::= { ciscoLwappTsmDot11Stats 2 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.525.1.2.2.1 cLTsmDot11UplinkEntry 12 12 Each entry represents a conceptual row in this table
    and corresponds to the uplink TSM statistics received
    from an AP, in a 90 se…

    Brothers (3)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.525.1.2.1 cLTsmDot11ClientTable 1 3 This table lists those clients for which TSM statistics
    are collected by the controller from the respective
    APs associated with t…
    1.3.6.1.4.1.9.9.525.1.2.3 cLTsmDot11DnlinkTable 1 11 This table represents the statistics received by the
    controller from the associated APs, on the downlink
    traffic ( traffic from t…
    1.3.6.1.4.1.9.9.525.1.2.4 cLTsmDot11CUTable 1 6 This table represents Channel Utilization statistics
    received by the Controller from associated APs observed
    on the dot11 radio i…