OID reference

ciscoLwappCdpMIB

1.3.6.1.4.1.9.9.623

Description

This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about CDP neighbors of LWAPP APs. The MIB provides configuration o…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
623
Node name
ciscoLwappCdpMIB
Numeric OID
1.3.6.1.4.1.9.9.623
URN notation
urn:oid:1.3.6.1.4.1.9.9.623
Type
OBJECT IDENTIFIER
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 9 9 623}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoLwappCdpMIB(623)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/623
  • /ISO/Identified-Organization/6/1/4/1/9/9/623
  • /ISO/3/6/1/4/1/9/9/623
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoLwappCdpMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappCdpMIB
  • Additional combinations skipped.

The displayed source records contain one distinct definition. Compare its source records.

ciscoLwappCdpMIB MODULE-IDENTITY
    LAST-UPDATED    "201704270000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems,
            Customer Service

            Postal: 170 West Tasman Drive
            San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            Email: cs-wnbu-snmcp@cisco.com"
    DESCRIPTION
        "This MIB is intended to be implemented on all those
         devices operating as Central Controllers (CC) that
         terminate the Light Weight Access Point Protocol
         tunnel from Light-weight LWAPP Access Points.

         This MIB provides configuration and status information
         about CDP neighbors of LWAPP APs. The MIB provides  
         configuration of CDP feature on the LWAPP Access Points.
         The MIB can also be used to retrieve the status of the 
         CDP cache information on the various LWAPP access
         points.

         The CDP MIB is also supported by controller and provides
         configuration and status information about CDP neighbors
         of the controller.

         The relationship between CC and the LWAPP APs
         can be depicted as follows:

         +......+     +......+     +......+           +......+
         +      +     +      +     +      +           +      +
         +  CC  +     +  CC  +     +  CC  +           +  CC  +
         +      +     +      +     +      +           +      +
         +......+     +......+     +......+           +......+
         ..            .             .                 .
         ..            .             .                 .
         .  .            .             .                 .
         .    .            .             .                 .
         .      .            .             .                 .
         .        .            .             .                 .
         +......+ +......+     +......+      +......+          +......+
         +      + +      +     +      +      +      +          +      +
         +  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +
         +      + +      +     +      +      +      +          +      +
         +......+ +......+     +......+      +......+          +......+
         .              .             .                 .
         .  .              .             .                 .
         .    .              .             .                 .
         .      .              .             .                 .
         .        .              .             .                 .
         +......+ +......+     +......+      +......+          +......+
         +      + +      +     +      +      +      +          +      +
         +  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +
         +      + +      +     +      +      +      +          +      +
         +......+ +......+     +......+      +......+          +......+


         The LWAPP tunnel exists between the controller and
         the APs.  The MNs communicate with the APs through
         the protocol defined by the 802.11 standard.

         LWAPP APs, upon bootup, discover and join one of the
         controllers and the controller pushes the configuration,
         that includes the WLAN parameters, to the LWAPP APs.
         The APs then encapsulate all the 802.11 frames from
         wireless clients inside LWAPP frames and forward
         the LWAPP frames to the controller.

                            GLOSSARY

         Access Point ( AP )

         An entity that contains an 802.11 medium access
         control ( MAC ) and physical layer ( PHY ) interface
         and provides access to the distribution services via
         the wireless medium for associated clients.  

         LWAPP APs encapsulate all the 802.11 frames in
         LWAPP frames and sends it to the controller to which
         it is logically connected.

         Basic Service Set Identifier (BSSID)

         The identifier for the service set comprising of
         all the 802.11 stations under the control of
         one coordinating Access Point.  This identifier
         happens to be the MAC address of the dot11 radio
         interface of the Access Point.  The wireless
         clients that associate with the Access Point
         get the wired uplink through this particular 
         dot11 interface. 

         Central Controller ( CC )

         The central entity that terminates the LWAPP protocol
         tunnel from the LWAPP APs.  Throughout this MIB,
         this entity also referred to as 'controller'.  

         Light Weight Access Point Protocol ( LWAPP ) 

         This is a generic protocol that defines the 
         communication between the Access Points and the
         central controller. 

         Cisco Discovery Protocol ( CDP )

         Protocol for discovery of neighboring devices.


         REFERENCE

         [1] Part 11 Wireless LAN Medium Access Control ( MAC )
         and Physical Layer ( PHY ) Specifications.

         [2] Draft-obara-capwap-lwapp-00.txt, IETF Light 
         Weight Access Point Protocol."
    REVISION        "201704270000Z"
    DESCRIPTION
            "Updated the description for some objects."
    REVISION        "200911230000Z"
    DESCRIPTION
            "Added the variables clcCdpApCacheDuplex and
            clcCdpApCacheInterfaceSpeed to clcCdpApCacheTable."
    REVISION        "200703280000Z"
    DESCRIPTION
            "This is the initial version of this module."
    ::= { ciscoMgmt 623 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight Access Point Protocol
tunnel from Light-weight LWAPP Access Points.

This MIB provides configuration and status information
about CDP neighbors of LWAPP APs. The MIB provides
configuration of CDP feature on the LWAPP Access Points.
The MIB can also be used to retrive the status of the
CDP cache information on the various LWAPP LWAPP Access
Points.

The CDP MIB is also supported by Controller and provides
configuration and status information about CDP neighbours
of the controller.

The relationship between CC and the LWAPP APs
can be depicted as follows:

+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+


The LWAPP tunnel exists between the controller and
the APs. The MNs communicate with the APs through
the protocol defined by the 802.11 standard.

LWAPP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the LWAPP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside LWAPP frames and forward
the LWAPP frames to the controller.

GLOSSARY

Access Point ( AP )

An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.

LWAPP APs encapsulate all the 802.11 frames in
LWAPP frames and sends it to the controller to which
it is logically connected.

Basic Service Set Identifier (BSSID)

The identifier for the service set comprising of
all the 802.11 stations under the control of
one coordinating Access Point. This identifier
happens to be the MAC address of the dot11 radio
interface of the Access Point. The wireless
clients that associate with the Access Point
get the wired uplink through this particular
dot11 interface.

Central Controller ( CC )

The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs. Throughout this MIB,
this entity also referred to as 'controller'.

Light Weight Access Point Protocol ( LWAPP )

This is a generic protocol that defines the
communication between the Access Points and the
Central Controller.

Cisco Discovery Protocol ( CDP )

Protocol for discovery of neighboring devices.


REFERENCE

[1] Part 11 Wireless LAN Medium Access Control ( MAC )
and Physical Layer ( PHY ) Specifications.

[2] Draft-obara-capwap-lwapp-00.txt, IETF Light
Weight Access Point Protocol.
Sources for this description

Circitor

Parsed from CISCO-LWAPP-CDP-MIB.mib · CISCO-LWAPP-CDP-MIB

Source file: Download CISCO-LWAPP-CDP-MIB.mib

Cisco

Description 2

This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about CDP neighbors of LWAPP APs. The MIB provides configuration of CDP feature on the LWAPP Access Points. The MIB can also be used to retrieve the status of the CDP cache information on the various LWAPP access points. The CDP MIB is also supported by controller and provides configuration and status information about CDP neighbors of the controller. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends it to the controller to which it is logically connected. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the central controller. Cisco Discovery Protocol ( CDP ) Protocol for discovery of neighboring devices. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol.

Sources for this description

CiscoCisco MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; representative source files are shown for each definition.

Records for description 2Cisco, Cisco MIB copies (LibreNMS/Observium Community), and others1 record · 3 sources

Description 2

ciscoLwappCdpMIB · unspecifiedCisco, Cisco MIB copies (LibreNMS/Observium Community), and others3 sources

Status in source: unspecified.

Names: ciscoLwappCdpMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoLwappCdpMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313730343237303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems Inc.\"",
    "CONTACT-INFO",
    "\"Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-snmcp@cisco.com\"",
    "DESCRIPTION",
    "\"This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about CDP neighbors of LWAPP APs. The MIB provides configuration of CDP feature on the LWAPP Access Points. The MIB can also be used to retrieve the status of the CDP cache information on the various LWAPP access points. The CDP MIB is also supported by controller and provides configuration and status information about CDP neighbors of the controller. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends it to the controller to which it is logically connected. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the central controller. Cisco Discovery Protocol ( CDP ) Protocol for discovery of neighboring devices. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol.\"",
    "REVISION",
    [
      "literal",
      "223230313730343237303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated the description for some objects.\"",
    "REVISION",
    [
      "literal",
      "223230303931313233303030305a22"
    ],
    "DESCRIPTION",
    "\"Added the variables clcCdpApCacheDuplex and clcCdpApCacheInterfaceSpeed to clcCdpApCacheTable.\"",
    "REVISION",
    [
      "literal",
      "223230303730333238303030305a22"
    ],
    "DESCRIPTION",
    "\"This is the initial version of this module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "623",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201704270000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-snmcp@cisco.com"
    ],
    [
      "DESCRIPTION",
      "This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about CDP neighbors of LWAPP APs. The MIB provides configuration of CDP feature on the LWAPP Access Points. The MIB can also be used to retrieve the status of the CDP cache information on the various LWAPP access points. The CDP MIB is also supported by controller and provides configuration and status information about CDP neighbors of the controller. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + MN + + MN + + MN + + MN + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ The LWAPP tunnel exists between the controller and the APs. The MNs communicate with the APs through the protocol defined by the 802.11 standard. LWAPP APs, upon bootup, discover and join one of the controllers and the controller pushes the configuration, that includes the WLAN parameters, to the LWAPP APs. The APs then encapsulate all the 802.11 frames from wireless clients inside LWAPP frames and forward the LWAPP frames to the controller. GLOSSARY Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides access to the distribution services via the wireless medium for associated clients. LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and sends it to the controller to which it is logically connected. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communication between the Access Points and the central controller. Cisco Discovery Protocol ( CDP ) Protocol for discovery of neighboring devices. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol."
    ],
    [
      "Revisions",
      [
        [
          "201704270000Z",
          [
            "DESCRIPTION",
            "Updated the description for some objects."
          ]
        ],
        [
          "200911230000Z",
          [
            "DESCRIPTION",
            "Added the variables clcCdpApCacheDuplex and clcCdpApCacheInterfaceSpeed to clcCdpApCacheTable."
          ]
        ],
        [
          "200703280000Z",
          [
            "DESCRIPTION",
            "This is the initial version of this module."
          ]
        ]
      ]
    ]
  ]
}
  • Cisco · Publisher's source file: CISCO-LWAPP-CDP-MIB.my

    Module: CISCO-LWAPP-CDP-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'CISCO-TC': ['CiscoNetworkProtocol', 'CiscoNetworkAddress'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'CISCO-LWAPP-AP-MIB': ['cLApSysMacAddress'], 'CISCO-LWAPP-TC-MIB': ['CLCdpAdvtVersionType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download CISCO-LWAPP-CDP-MIB.my

Historical records

Additional source information

Information from Circitor
ciscoLwappCdpMIB MODULE-IDENTITY
    LAST-UPDATED    "200703280000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems,
            Customer Service

            Postal: 170 West Tasman Drive
            San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            Email: cs-wnbu-snmcp@cisco.com"
    DESCRIPTION
        "This MIB is intended to be implemented on all those
        devices operating as Central Controllers (CC) that
        terminate the Light Weight Access Point Protocol
        tunnel from Light-weight LWAPP Access Points.

        This MIB provides configuration and status information
        about CDP neighbors of LWAPP APs. The MIB provides  
        configuration of CDP feature on the LWAPP Access Points.
        The MIB can also be used to retrive the status of the 
        CDP cache information on the various LWAPP LWAPP Access
        Points.

        The CDP MIB is also supported by Controller and provides
        configuration and status information about CDP neighbours
        of the controller.

        The relationship between CC and the LWAPP APs
        can be depicted as follows:

        +......+     +......+     +......+           +......+
        +      +     +      +     +      +           +      +
        +  CC  +     +  CC  +     +  CC  +           +  CC  +
        +      +     +      +     +      +           +      +
        +......+     +......+     +......+           +......+
        ..            .             .                 .
        ..            .             .                 .
        .  .            .             .                 .
        .    .            .             .                 .
        .      .            .             .                 .
        .        .            .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+
        .              .             .                 .
        .  .              .             .                 .
        .    .              .             .                 .
        .      .              .             .                 .
        .        .              .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+


        The LWAPP tunnel exists between the controller and
        the APs.  The MNs communicate with the APs through
        the protocol defined by the 802.11 standard.

        LWAPP APs, upon bootup, discover and join one of the
        controllers and the controller pushes the configuration,
        that includes the WLAN parameters, to the LWAPP APs.
        The APs then encapsulate all the 802.11 frames from
        wireless clients inside LWAPP frames and forward
        the LWAPP frames to the controller.

                           GLOSSARY

        Access Point ( AP )

        An entity that contains an 802.11 medium access
        control ( MAC ) and physical layer ( PHY ) interface
        and provides access to the distribution services via
        the wireless medium for associated clients.  

        LWAPP APs encapsulate all the 802.11 frames in
        LWAPP frames and sends it to the controller to which
        it is logically connected.

        Basic Service Set Identifier (BSSID)

        The identifier for the service set comprising of
        all the 802.11 stations under the control of
        one coordinating Access Point.  This identifier
        happens to be the MAC address of the dot11 radio
        interface of the Access Point.  The wireless
        clients that associate with the Access Point
        get the wired uplink through this particular 
        dot11 interface. 

        Central Controller ( CC )

        The central entity that terminates the LWAPP protocol
        tunnel from the LWAPP APs.  Throughout this MIB,
        this entity also referred to as 'controller'. 

        Light Weight Access Point Protocol ( LWAPP ) 

        This is a generic protocol that defines the 
        communication between the Access Points and the
        Central Controller. 

        Cisco Discovery Protocol ( CDP )

        Protocol for discovery of neighboring devices.


        REFERENCE

        [1] Part 11 Wireless LAN Medium Access Control ( MAC )
        and Physical Layer ( PHY ) Specifications.

        [2] Draft-obara-capwap-lwapp-00.txt, IETF Light 
        Weight Access Point Protocol."
    REVISION        "200703280000Z"
    DESCRIPTION
        "This is the initial version of this module."
    ::= { ciscoMgmt 623 }
Information from Cisco SMIv1

Source file: Download CISCO-LWAPP-CDP-MIB-V1SMI.my · Publisher's file

Source file: Download CISCO-LWAPP-CDP-MIB-V1SMI.my.txt

ciscoLwappCdpMIB OBJECT IDENTIFIER ::= { ciscoMgmt 623 }
Information from OID Repository
Vendor: Cisco
Module: CISCO-LWAPP-CDP-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot
ciscoLwappCdpMIB MODULE-IDENTITY
    LAST-UPDATED    "200703280000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems,
            Customer Service

            Postal: 170 West Tasman Drive
            San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            Email: cs-wnbu-snmcp@cisco.com"
    DESCRIPTION
        "This MIB is intended to be implemented on all those
        devices operating as Central Controllers (CC) that
        terminate the Light Weight Access Point Protocol
        tunnel from Light-weight LWAPP Access Points.

        This MIB provides configuration and status information
        about CDP neighbors of LWAPP APs. The MIB provides  
        configuration of CDP feature on the LWAPP Access Points.
        The MIB can also be used to retrive the status of the 
        CDP cache information on the various LWAPP LWAPP Access
        Points.

        The CDP MIB is also supported by Controller and provides
        configuration and status information about CDP neighbours
        of the controller.

        The relationship between CC and the LWAPP APs
        can be depicted as follows:

        +......+     +......+     +......+           +......+
        +      +     +      +     +      +           +      +
        +  CC  +     +  CC  +     +  CC  +           +  CC  +
        +      +     +      +     +      +           +      +
        +......+     +......+     +......+           +......+
        ..            .             .                 .
        ..            .             .                 .
        .  .            .             .                 .
        .    .            .             .                 .
        .      .            .             .                 .
        .        .            .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+
        .              .             .                 .
        .  .              .             .                 .
        .    .              .             .                 .
        .      .              .             .                 .
        .        .              .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+


        The LWAPP tunnel exists between the controller and
        the APs.  The MNs communicate with the APs through
        the protocol defined by the 802.11 standard.

        LWAPP APs, upon bootup, discover and join one of the
        controllers and the controller pushes the configuration,
        that includes the WLAN parameters, to the LWAPP APs.
        The APs then encapsulate all the 802.11 frames from
        wireless clients inside LWAPP frames and forward
        the LWAPP frames to the controller.

                           GLOSSARY

        Access Point ( AP )

        An entity that contains an 802.11 medium access
        control ( MAC ) and physical layer ( PHY ) interface
        and provides access to the distribution services via
        the wireless medium for associated clients.  

        LWAPP APs encapsulate all the 802.11 frames in
        LWAPP frames and sends it to the controller to which
        it is logically connected.

        Basic Service Set Identifier (BSSID)

        The identifier for the service set comprising of
        all the 802.11 stations under the control of
        one coordinating Access Point.  This identifier
        happens to be the MAC address of the dot11 radio
        interface of the Access Point.  The wireless
        clients that associate with the Access Point
        get the wired uplink through this particular 
        dot11 interface. 

        Central Controller ( CC )

        The central entity that terminates the LWAPP protocol
        tunnel from the LWAPP APs.  Throughout this MIB,
        this entity also referred to as 'controller'. 

        Light Weight Access Point Protocol ( LWAPP ) 

        This is a generic protocol that defines the 
        communication between the Access Points and the
        Central Controller. 

        Cisco Discovery Protocol ( CDP )

        Protocol for discovery of neighboring devices.


        REFERENCE

        [1] Part 11 Wireless LAN Medium Access Control ( MAC )
        and Physical Layer ( PHY ) Specifications.

        [2] Draft-obara-capwap-lwapp-00.txt, IETF Light 
        Weight Access Point Protocol."
    REVISION        "200703280000Z"
    DESCRIPTION
        "This is the initial version of this module."
    ::= { ciscoMgmt 623 }
Information from Cisco
ciscoLwappCdpMIB MODULE-IDENTITY
    LAST-UPDATED    "200911230000Z"
    ORGANIZATION    "Cisco Systems Inc."
    CONTACT-INFO
            "Cisco Systems,
            Customer Service

            Postal: 170 West Tasman Drive
            San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            Email: cs-wnbu-snmcp@cisco.com"
    DESCRIPTION
        "This MIB is intended to be implemented on all those
        devices operating as Central Controllers (CC) that
        terminate the Light Weight Access Point Protocol
        tunnel from Light-weight LWAPP Access Points.

        This MIB provides configuration and status information
        about CDP neighbors of LWAPP APs. The MIB provides  
        configuration of CDP feature on the LWAPP Access Points.
        The MIB can also be used to retrive the status of the 
        CDP cache information on the various LWAPP LWAPP Access
        Points.

        The CDP MIB is also supported by Controller and provides
        configuration and status information about CDP neighbours
        of the controller.

        The relationship between CC and the LWAPP APs
        can be depicted as follows:

        +......+     +......+     +......+           +......+
        +      +     +      +     +      +           +      +
        +  CC  +     +  CC  +     +  CC  +           +  CC  +
        +      +     +      +     +      +           +      +
        +......+     +......+     +......+           +......+
        ..            .             .                 .
        ..            .             .                 .
        .  .            .             .                 .
        .    .            .             .                 .
        .      .            .             .                 .
        .        .            .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+
        .              .             .                 .
        .  .              .             .                 .
        .    .              .             .                 .
        .      .              .             .                 .
        .        .              .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+


        The LWAPP tunnel exists between the controller and
        the APs.  The MNs communicate with the APs through
        the protocol defined by the 802.11 standard.

        LWAPP APs, upon bootup, discover and join one of the
        controllers and the controller pushes the configuration,
        that includes the WLAN parameters, to the LWAPP APs.
        The APs then encapsulate all the 802.11 frames from
        wireless clients inside LWAPP frames and forward
        the LWAPP frames to the controller.

                           GLOSSARY

        Access Point ( AP )

        An entity that contains an 802.11 medium access
        control ( MAC ) and physical layer ( PHY ) interface
        and provides access to the distribution services via
        the wireless medium for associated clients.  

        LWAPP APs encapsulate all the 802.11 frames in
        LWAPP frames and sends it to the controller to which
        it is logically connected.

        Basic Service Set Identifier (BSSID)

        The identifier for the service set comprising of
        all the 802.11 stations under the control of
        one coordinating Access Point.  This identifier
        happens to be the MAC address of the dot11 radio
        interface of the Access Point.  The wireless
        clients that associate with the Access Point
        get the wired uplink through this particular 
        dot11 interface. 

        Central Controller ( CC )

        The central entity that terminates the LWAPP protocol
        tunnel from the LWAPP APs.  Throughout this MIB,
        this entity also referred to as 'controller'. 

        Light Weight Access Point Protocol ( LWAPP ) 

        This is a generic protocol that defines the 
        communication between the Access Points and the
        Central Controller. 

        Cisco Discovery Protocol ( CDP )

        Protocol for discovery of neighboring devices.


        REFERENCE

        [1] Part 11 Wireless LAN Medium Access Control ( MAC )
        and Physical Layer ( PHY ) Specifications.

        [2] Draft-obara-capwap-lwapp-00.txt, IETF Light 
        Weight Access Point Protocol."
    REVISION        "200911230000Z"
    DESCRIPTION
        "Added the variables clcCdpApCacheDuplex and
        clcCdpApCacheInterfaceSpeed to clcCdpApCacheTable."
    REVISION        "200703280000Z"
    DESCRIPTION
        "This is the initial version of this module."
    ::= { ciscoMgmt 623 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.623.0 ciscoLwappCdpMIBNotifs00
1.3.6.1.4.1.9.9.623.1 ciscoLwappCdpMIBObjects446
1.3.6.1.4.1.9.9.623.2 ciscoLwappCdpMIBConform27

Siblings (706)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.513 ciscoLwappApMIB51009 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.514 ciscoLwappTextualConventions00 This module defines textual conventions used
throughout the Cisco enterprise MIBs
designed for implementation on Central
Controlle…
1.3.6.1.4.1.9.9.515 ciscoLwappWebAuthMIB4133 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.516 ciscoLwappLinkTestMIB357 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.517 ciscoLwappReapMIB3342 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.518 ciscoLwappMfpMIB468 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.519 ciscoLwappIdsMIB328 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.520 ciscoLwappCcxRmMIB345 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.521 ciscoLwappWlanSecurityMIB377 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.522 ciscoLwappDot11ClientCalibMIB355 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.523 ciscoLwappClRoamMIB363 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.524 ciscoLwappQosMIB3491 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.525 ciscoLwappTsmMIB357 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.529 ciscoItpMsuRatesMIB361 This MIB provides information used to manage the number
of MTP3 MSUs transmitted and received per processor. Many
of the higher …
1.3.6.1.4.1.9.9.530 ciscoNacTcMIB00 This module defines the textual conventions for
Cisco Network Admission Control(NAC) system.

The Cisco Network Admission Control …
1.3.6.1.4.1.9.9.532 ciscoNATExtMIB313 This MIB is an extension to the NAT-MIB.
This MIB module includes objects for
providing the NAT related statistics.

Acronyms:

NAT…
1.3.6.1.4.1.9.9.533 ciscoCbpTargetMIB325 This MIB module defines the managed objects for
representing targets which have class-based policy
mappings. A target can be any…
1.3.6.1.4.1.9.9.543 ciscoLicenseMgmtMIB3131 The MIB module for managing licenses on the system.
The licensing mechanism provides flexibility to
enforce licensing for various…
1.3.6.1.4.1.9.9.548 ciscoErrDisableMIB345 This MIB module provides the ability for a Network
Management Station (NMS) to configure and monitor the
error-disable feature vi…
1.3.6.1.4.1.9.9.572 ciscoRttMonIPExtMIB257 This MIB contains extensions to tables in CISCO-RTTMON-MIB
to support IP-layer extensions, specifically IPv6 addresses
and other …
1.3.6.1.4.1.9.9.573 ciscoQosTcMIB00 This module defines the textual conventions used within
Cisco Qos MIBs.
1.3.6.1.4.1.9.9.576 ciscoLwappMobilityMIB3106 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that

terminate the Light Weight…
1.3.6.1.4.1.9.9.577 ciscoLwappAclMIB347 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.578 ciscoRoutePoliciesMIB35 This module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This mod…
1.3.6.1.4.1.9.9.580 ciscoSwitchQosMIB3295 This MIB module extends the CISCO-CLASS-BASED-QOS-MIB
by defining configuration and statistics information
specific to the qualit…
1.3.6.1.4.1.9.9.583 ciscoGslbTcMIB00 This MIB module defines Textual Conventions and
OBJECT-IDENTITIES for use in documents defining
management information base (MIBs…
1.3.6.1.4.1.9.9.584 ciscoEntityDiagTcMIB00 This module defines the textual conventions used within
Cisco Entity Diag MIB.
1.3.6.1.4.1.9.9.585 ciscoIpSlaEthernetMIB3245 This MIB module consists of two parts.

1) Auto-Ethernet-CFM Control:
|
|

2) ethernetJitter Stats:
|
|

The first part defines a mechani…
1.3.6.1.4.1.9.9.586 ciscoNotificationControlMIB228 This MIB provides network management support to regulate
the transmission of notifications generated by a
system providing networ…
1.3.6.1.4.1.9.9.589 ciscoGslbSystemMIB3103 This MIB module defines objects for network and system
information of Global Server Load Balancer(GSLB) as a
network device. A G…
1.3.6.1.4.1.9.9.590 ciscoCvpMIB3255 The Cisco Unified Customer Voice Portal (CVP) application
integrates with both traditional time-division multiplexing
(TDM) and I…
1.3.6.1.4.1.9.9.592 ciscoPrefPathMIB356 The MIB module for the management of
preferred path. This MIB enables managers
to configure and monitor Preferred Path
parameters.
…
1.3.6.1.4.1.9.9.593 ciscoFcSdvMIB328 This MIB instrumentation is for managing Fibre
Channel (FC) SAN Device Virtualization (SDV)
solution on Cisco Fibre Channel devic…
1.3.6.1.4.1.9.9.594 ciscoApplicationAccelerationMIB337 This is a MIB for managing Application Acceleration System(s).
This MIB includes instrumentation for providing the
performance st…
1.3.6.1.4.1.9.9.595 ciscoGslbDnsMIB3165 The MIB defines objects for status and statistics
information of DNS related operations of
Global Server Load Balancer(GSLB). Th…
1.3.6.1.4.1.9.9.597 ciscoContentServicesMIB3349 Content Service is a capability to examine IP/TCP/UDP headers,
payload and enable billing based on the content being provided.

Ab…
1.3.6.1.4.1.9.9.598 ciscoLwappAAAMIB3150 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC), that
terminate the Light Weigh…
1.3.6.1.4.1.9.9.599 ciscoLwappDot11ClientMIB4523 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.600 ciscoGslbHealthMonMIB390 The MIB defines objects related to global keepalive
properties in GSLB devices. It contains the tables
for keep alive configurat…
1.3.6.1.4.1.9.9.601 ciscoResilientEthernetProtocolMIB377 This MIB module defines objects required for managing
Resilient Ethernet Protocol (REP).

Resilient Ethernet Protocol (REP) is a C…
1.3.6.1.4.1.9.9.602 ciscoPacketCaptureMIB3103 The MIB module for the management of packet capture
feature.
1.3.6.1.4.1.9.9.603 ciscoThreatMitigationServiceMIB368 This MIB provides management information about the Threat
Mitigation Service(TMS) entity named 'Consumer'. TMS is part
of Cisco's…
1.3.6.1.4.1.9.9.604 cdot1CfmMIB3166 Connectivity Fault Management module for managing IEEE 802.1ag
1.3.6.1.4.1.9.9.606 ciscoLwappMeshLinkTestMIB346 ciscoLwappMeshLinkTestMIB MODULE-IDENTITY
LAST-UPDATED "200702050000Z"
ORGANIZATION "Cisco Systems Inc."
CONTACT-INFO
"Cisco Sy…
1.3.6.1.4.1.9.9.607 ciscoDot11HtPhyMIB371 This MIB is intended to be implemented on Cisco's
WLAN devices that provide the wired uplink to wireless
clients through the high…
1.3.6.1.4.1.9.9.610 ciscoLwappRogueMIB4134 This MIB is intended to be implemented on all those
devices operating as Central Controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.611 ciscoLwappDot11ClientCCXTextualConventions00 This module defines the textual conventions used
throughout the Cisco enterprise MIBs designed for
implementation on Central Cont…
1.3.6.1.4.1.9.9.612 ciscoLwappDot11MIB3158 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.613 ciscoEvcMIB3156 Metro Ethernet services can support a wide range of
applications and subscriber needs easily, efficiently
and cost-effectively. …
1.3.6.1.4.1.9.9.614 ciscoLwappDot11LdapMIB333 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…