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.181 ciscoWirelessLinkMetricsMIB4141 This is the MIB Module for the Cisco Wireless Radio
Point to MultiPoint interface link metrics
specification.

Glossary

The followin…
1.3.6.1.4.1.9.9.183 ciscoGprsAccPtMIB3338 This MIB module supports access point configuration
for GGSN in a GPRS system. GPRS [1] is a GSM network
providing mobile wireles…
1.3.6.1.4.1.9.9.184 ciscoPimMIB336 This MIB module defines the cisco specific variables
for Protocol Independent Multicast (PIM) management.
These definitions are a…
1.3.6.1.4.1.9.9.185 ciscoBertMIB246 The MIB module to configure and perform Bit Error Rate Testing
(BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces.
Bit error rate…
1.3.6.1.4.1.9.9.187 ciscoBgp4MIB4170 An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Proto…
1.3.6.1.4.1.9.9.188 cGtpMIB3248 This MIB module manages the GPRS Tunnelling Protocol
(GTP) on GGSN and SGSN.

GPRS provides wireless access to packet data network…
1.3.6.1.4.1.9.9.189 ciscoPortQosMIB3114 Cisco PORT QOS MIB - Overview

This MIB module is for the management of Cisco's
per port rate-limiting and traffic shaping on L3
sw…
1.3.6.1.4.1.9.9.190 ciscoVoiceAppsMIB340 The MIB Module for the management of Cisco Voice
Applications. This MIB is designed to work in
conjunction with the SYSAPPL-MIB …
1.3.6.1.4.1.9.9.191 ciscoIpUplinkRedirectMIB311 This MIB module is for the configuration of
Cisco IP Uplink Redirect feature.
1.3.6.1.4.1.9.9.192 ciscoGprsChargingMIB3315 This MIB module manages the charging related
function on the GGSN node of a GPRS system.

The following diagram illustrates a simp…
1.3.6.1.4.1.9.9.194 ciscoPppoeMIB389 Cisco PPPoE sessions management MIB Module.
1.3.6.1.4.1.9.9.195 ciscoEntityExtMIB370 This MIB is an extension of the ENTITY-MIB
specified in RFC2737.

This MIB module contains Cisco-defined extensions
to the entit…
1.3.6.1.4.1.9.9.197 ciscoDistDirMIB3123 Cisco Distributed Director MIB.

The Cisco Distributed Director provides global Internet
scalability and increased performance as …
1.3.6.1.4.1.9.9.198 ciscoRfSupMIB365 This MIB was designed to complement the CISCO-RF-MIB by
providing additional optional status and configuration control
for redund…
1.3.6.1.4.1.9.9.199 ciscoSmFileDownloadMIB323 The MIB module for downloading files to the Service
Modules specifically designed for an architecture
containing a controller car…
1.3.6.1.4.1.9.9.201 ciscoSwitchUsageMIB315 This MIB defines objects related to statistics
for the usage of switch fabric. The switch fabric
is used by the incoming packets …
1.3.6.1.4.1.9.9.202 ciscoOscpMIB352 The MIB module for managing the Cisco Optical
Supervisory Channel Protocol (OSCP). The OSCP is used
to determine and maintain wav…
1.3.6.1.4.1.9.9.204 ciscoXdslLineMIB232 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
different t…
1.3.6.1.4.1.9.9.215 ciscoMacNotificationMIB372 This MIB module is for configuration of the MAC notification
feature. MAC notification is a mechanism to inform monitoring
device…
1.3.6.1.4.1.9.9.216 ciscoContentNetworkMIB334 This MIB module defines objects for Content Network devices.

A Content Network is a collection of devices that optimizes the
deli…
1.3.6.1.4.1.9.9.217 ciscoCat6kCrossbarMIB3210 The Catalyst 6000 Crossbar MIB provides instrumentation for
configuration and operation of the crossbar switching fabric
module, …
1.3.6.1.4.1.9.9.218 ciscoIfThresholdMIB365 ciscoIfthresholdMIB
1.3.6.1.4.1.9.9.219 ciscoVoiceDnisMIB324 The MIB module provides management support for Dialer
Number Information Service (DNIS) mapping. A DNIS
entry is associated with…
1.3.6.1.4.1.9.9.220 ciscoPaeMIB3231 Cisco Port Access Entity (PAE) module for managing
IEEE Std 802.1x.

This MIB provides Port Access Entity information
that are eith…
1.3.6.1.4.1.9.9.221 ciscoEnhancedMemPoolMIB387 New MIB module for monitoring the memory pools
of all physical entities on a managed system.
1.3.6.1.4.1.9.9.222 ciscoEnhancedWredMIB370 Cisco WRED MIB - Overview
Cisco Weighted Random Early Detection/Drop (WRED)
is a method which avoids traffic congestion on an
outp…
1.3.6.1.4.1.9.9.223 ciscoWanNcdpMIB358 This MIB module is intended for the management of network clock
distribution and the Network Clock Distribution Protocol (NCDP)
i…
1.3.6.1.4.1.9.9.224 ciscoDevExcepReportMIB329 This mib defines the SNMP objects to report
exceptions to north-bound NMS.

The devices implementing this MIB monitor
the status of…
1.3.6.1.4.1.9.9.225 ciscoLagMIB356 Cisco Link Aggregation module for managing IEEE Std
802.3ad.

This MIB provides Link Aggregation information that are
either exclud…
1.3.6.1.4.1.9.9.226 ciscoNDEMIB417 The Netflow Data Export (NDE) MIB provides instrumentation for
configuration and operation of the Netflow Data Export feature.

A …
1.3.6.1.4.1.9.9.227 ciscoItpAclMIB345 The MIB for managing access lists that control
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP Trans…
1.3.6.1.4.1.9.9.228 ciscoItpRtMIB347 This MIB is for managing information required to
route messages transported over Signalling System
No. 7 (SS7) Network via Cisco …
1.3.6.1.4.1.9.9.229 ciscoDs1ExtMIB2129 The MIB module to describe DS1/E1 interface objects. This is
an extension to the standard DS1/E1 MIB (RFC 2495).

Unless mentioned…
1.3.6.1.4.1.9.9.230 ciscoItpActMIB329 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.231 ciscoItpTextualConventions00 The defines textual conventions used by to manage
devices related to the SS7 network. The
relevant ITU documents describing this…
1.3.6.1.4.1.9.9.232 ciscoItpSpMIB3384 The MIB for managing Signalling Points and its
associated messages transported over Signalling
System No. 7 (SS7) Network via Ci…
1.3.6.1.4.1.9.9.233 ciscoItpSccpMIB3194 The MIB for Signaling Connection Control Part(SCCP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP …
1.3.6.1.4.1.9.9.234 ciscoWanTopologyMIB383 A management station can use this MIB module for the
maintenance of persistent topology information of the
PNNI network. Previous…
1.3.6.1.4.1.9.9.235 ciscoImaMIB260 The MIB module describes Cisco IMA objects.
This is an extension to the standard of
ATM Forum IMA version 1.1, AF-PHY-0086.001
Spe…
1.3.6.1.4.1.9.9.236 ciscoWanSctMgmtMIB218 MIB module to manage SCT files in a node.

SCTs (Service Class Templates) are nodal configuration files,
which define the traffic …
1.3.6.1.4.1.9.9.237 ciscoNmsApplHealthMIB339 This MIB defines Cisco NMS Application (cna) Health
Status Notifications and the related objects. These
notifications will be sen…
1.3.6.1.4.1.9.9.238 ciscoIGMPFilterMIB245 IGMP Filter configuration MIB. This MIB provides a
mechanism for users to configure the system to intercept
IGMP joins for IP Mul…
1.3.6.1.4.1.9.9.240 cGgsnMIB3389 This MIB module manages the Gateway GPRS Support
Node (GGSN) devices.

A GGSN device provides interworking with external
packet-dat…
1.3.6.1.4.1.9.9.241 cggsnQosMIB289 This MIB module manages the Quality of Service
parameters of GGSN in a GPRS system.

GGSN is the Gateway GPRS Support Node in the …
1.3.6.1.4.1.9.9.242 ciscoCableAvailabilityMIB360 This is the MIB module for management of Hot Standby
Connection to Connection Protocol (HCCP) features. HCCP is
a Cisco proprieta…
1.3.6.1.4.1.9.9.243 ciscoHealthMonitorMIB322 Health Monitor MIB module.

The Health Monitor uses a model based on events of varying
severity and frequency, and predefined rule…
1.3.6.1.4.1.9.9.244 ciscoNbarProtocolDiscoveryMIB384 Cisco NBAR Protocol Discovery MIB

NBAR - Network Based Application Recognition is
an intelligent classification engine that reco…
1.3.6.1.4.1.9.9.245 ciscoGtpDirectorMIB335 This MIB module defines objects that are used to
manage GTP Director Module.

In the GPRS network, the APN is the identifier that
s…
1.3.6.1.4.1.9.9.246 ciscoL2TunnelConfigMIB365 This MIB module is for layer 2 tunneling related configurations
on a device.

Tunneling allows separate local networks to be consi…
1.3.6.1.4.1.9.9.248 ciscoItpSp2MIB330 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signaling System No. 7(SS7) Network.
This …