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.443 ciscoCommonMgmtMIB337 MIB module for integrating different elements of
managing a device. For example, different device access
methods like SNMP, CLI, …
1.3.6.1.4.1.9.9.445 ciscoQinqVlanMIB325 This MIB defines configuration and monitoring capabilities
relating to 802.1QinQ interfaces. QinQ interfaces are capable
of term…
1.3.6.1.4.1.9.9.447 ciscoScsiFlowMIB399 A SCSI Flow is described as a SCSI Initiator
SCSI Target combination. This MIB is used to
configure and monitor SCSI Flows.

Gloss…
1.3.6.1.4.1.9.9.448 ciscoSsmProvMIB226 This MIB is used to provision features
on a Data Path Processor (DPP) of a Storage Service
Module (SSM). A DPP is assigned to a c…
1.3.6.1.4.1.9.9.449 ciscoEigrpMIB3110 Enhanced Interior Gateway Protocol (EIGRP) is a Cisco
proprietary distance vector routing protocol. It is based on
the Diffusin…
1.3.6.1.4.1.9.9.450 ciscoCableAdmCtrlMIB3123 This MIB module defines the managed objects enabling
the management of Cable Modem Termination System
(CMTS) admission control.

CM…
1.3.6.1.4.1.9.9.451 ciscoIpUrpfMIB347 Unicast Reverse Path Forwarding (URPF) is a function
that checks the validity of the source address of IP
packets received on an …
1.3.6.1.4.1.9.9.454 ciscoDot11LbsMIB323 This MIB module supports network management
for Location Based Services on IEEE 802.11 wireless
LAN devices. Location Based Serv…
1.3.6.1.4.1.9.9.455 ciscoImageTc00 ciscoImageTc MODULE-IDENTITY
LAST-UPDATED "200501120000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Custom…
1.3.6.1.4.1.9.9.456 ciscoDot11WidsMIB350 This MIB is intended to be implemented on the
following IOS based network entities for the purpose
of providing network managemen…
1.3.6.1.4.1.9.9.457 ciscoWdsIdsMIB218 This MIB is intended to be implemented on all
IOS based network entities that provide Wireless
Domain Services, for the purpose o…
1.3.6.1.4.1.9.9.458 ciscoApplianceRedundancyMIB347 This mib defines the SNMP objects to report the status of
High Availability (HA) functionality in Cisco network
management applia…
1.3.6.1.4.1.9.9.459 ciscoBitsClockMIB321 This MIB provides information on Building Integrated
Timing Supply(BITS) clocking sources and modes of
operations. It is used to…
1.3.6.1.4.1.9.9.460 ciscoTpcMIB324 The MIB module for Third Party Copy(TPC):
Third Party Copy derives its name from the fact
that there are three entities involved …
1.3.6.1.4.1.9.9.461 ciscoEtherCfmMIB339 This MIB module defines the managed objects
and notifications for Ethernet Connectivity
Fault Management (CFM).

CFM is an end-to-e…
1.3.6.1.4.1.9.9.463 ciscoSanTapMIB330 MIB module to provide information about the SanTap
service configuration.

SanTap is a fibre channel switch based capability that
p…
1.3.6.1.4.1.9.9.466 ciscoEthernetAccessMIB220 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
an edge dev…
1.3.6.1.4.1.9.9.467 ciscoCryptoAcceleratorMIB3107 The MIB module for monitoring the identity, status,
activity and faults of crypto accelerator (CA) modules
used in devices implem…
1.3.6.1.4.1.9.9.468 ciscoContextMappingMIB235 A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple…
1.3.6.1.4.1.9.9.470 ciscoEnhancedSlbMIB3106 The MIB for managing Server Load Balancing
Manager(s), and products supporting Server
Load Balancing(SLB) features.

This MIB exten…
1.3.6.1.4.1.9.9.471 ciscoFlexLinksMIB336 This MIB module is for configuration and status query
of Flex Links feature on the Cisco device.

Flex Links are a pair of Layer 2…
1.3.6.1.4.1.9.9.472 ciscoModuleVirtualizationMIB335 This MIB provides a way to create virtual contexts,
and managing them. A virtual context is logical
partition of a physical devi…
1.3.6.1.4.1.9.9.473 ciscoCcaMIB3200 The Cisco Contact Center Applications (CCCA) Management
Information Base (MIB) module defines management
instrumentation for appl…
1.3.6.1.4.1.9.9.474 ciscoFilterGroupMIB355 The MIB module is for creating and configuring
object groups to support packet filtering and
access control on IP and other proto…
1.3.6.1.4.1.9.9.479 ciscoCableWidebandMIB377 This is the MIB module for the support of Channel Bonding
Protocol for the Cable Modem Termination System (CMTS).

Wideband DOCSIS…
1.3.6.1.4.1.9.9.480 ciscoL4L7moduleResourceLimitMIB4100 The MIB module for managing resource classes
and configuring limits(max/min) to different
resources. The resource referenced in …
1.3.6.1.4.1.9.9.482 ciscoInterfaceTopNExtMIB316 This MIB module is an extension to INTERFACETOPN-MIB.
It provides additional management information for
sorting device interfaces.
1.3.6.1.4.1.9.9.483 ciscoIpRanBackHaulMIB3248 This MIB provides information on the IP-RAN traffic
from cell site to aggregation site in the following
situations. In an GSM en…
1.3.6.1.4.1.9.9.484 ciscoNacNadMIB3157 This MIB module is for the configuration of a Network
Access Device (NAD) on the Cisco Network Admission
Control (NAC) system.

End…
1.3.6.1.4.1.9.9.485 ciscoRttMonTCMIB00 This MIB contains textual conventions used by
CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and
CISCO-RTTMON-ICMP-MIB, but they are not …
1.3.6.1.4.1.9.9.486 ciscoRttMonIcmpMIB37 An extension to the CISCO-RTTMON-MIB for ICMP
operations. The ICMP Jitter operation provides capability
to measure metrics such a…
1.3.6.1.4.1.9.9.487 ciscoRttMonRtpMIB38 An extension to the CISCO-RTTMON-MIB for Cisco IP SLA
RTP operation, Real-Time Transport Protocol(RFC 1889). This
operation provi…
1.3.6.1.4.1.9.9.488 ciscoFirewallTc00 This MIB module defines textual conventions that
are commonly used in modeling management information
pertaining to configuration…
1.3.6.1.4.1.9.9.490 ciscoNetintMIB311 This MIB module is for Network Interrupt information
on Cisco device.
1.3.6.1.4.1.9.9.491 ciscoUnifiedFirewallMIB3360 Overview of Cisco Firewall MIB
==============================
This MIB Module models status and performance
statistics pertaining …
1.3.6.1.4.1.9.9.492 ciscoCefMIB3192 Cisco Express Forwarding (CEF) describes a high speed
switching mechanism that a router uses to forward packets
from the inbound …
1.3.6.1.4.1.9.9.493 ciscoCefTextualConventions00 ciscoCeftextualConventions
1.3.6.1.4.1.9.9.494 ciscoEntityRedunTcMIB00 This module defines the textual conventions used within
Cisco Entity Redundancy MIBs.
1.3.6.1.4.1.9.9.495 ciscoPsdClientMIB344 This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).

This MIB instrumentation is for conf…
1.3.6.1.4.1.9.9.497 cGgsnSAMIB3247 This MIB module manages the service-aware feature of
Gateway GPRS Support Node (GGSN).

This MIB is an enhancement of the CISCO-GG…
1.3.6.1.4.1.9.9.498 ciscoEntityRedunMIB393 This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of c…
1.3.6.1.4.1.9.9.500 ciscoStackWiseMIB3111 This MIB module contain a collection of managed objects
that apply to network devices supporting the Cisco
StackWise(TM) technolo…
1.3.6.1.4.1.9.9.504 ciscoSwitchMulticastMIB3108 This MIB module defines management objects for the
Multicast Switching features on Cisco Layer 2/3
devices.

Definition of some of …
1.3.6.1.4.1.9.9.505 cpkiMIB344 A networking device may provide several security services
and protocols like SSL, SSH, IPSec/IKE etc. which need
identities …
1.3.6.1.4.1.9.9.507 ciscoPolicyGroupMIB335 The MIB module is for configuration of policy and
policy group. A policy group can be described as a set
of entities identified b…
1.3.6.1.4.1.9.9.508 ciscoSlbHealthMonMIB362 An extension to the CISCO-SLB-EXT-MIB for SLB
health monitoring probes.

SLB: Server Load Balancing. Server load balancing
provides…
1.3.6.1.4.1.9.9.509 ciscoWdsInfoMIB3141 This MIB is intended to be implemented on all Cisco
network entities that provide Wireless Domain Services
(WDS). The WDS provide…
1.3.6.1.4.1.9.9.510 ciscoErmMIB, ciscoVoiceLmrMIB3176 This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes …
1.3.6.1.4.1.9.9.511 ciscoCbpTargetTCMIB00 This MIB module defines Textual Conventions for
representing targets which have class based policy
mappings. A target can be any …
1.3.6.1.4.1.9.9.512 ciscoLwappWlanMIB3378 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weigh…