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.383 ciscoCidsMIB3183 Cisco Intrusion Detection System MIB. Provides
trap definitions for the evAlert and evError
elements of the IDIOM (Intrusion Det…
1.3.6.1.4.1.9.9.384 ciscoDot11AntennaMIB211 This MIB is intended to be implemented on 802.11
Access Points and Wireless Bridges to provide
information about the antennas con…
1.3.6.1.4.1.9.9.385 ciscoUnityMIB3101 The MIB Module for the management of Cisco Unity server.
Cisco Unity is a Unified Communications solution that provides
advanced,…
1.3.6.1.4.1.9.9.386 ciscoModuleAutoShutdownMIB336 The CISCO-MODULE-AUTO-SHUTDOWN-MIB is used to configure
the module automatic shutdown feature. Modules will be
reset by the syste…
1.3.6.1.4.1.9.9.387 ciscoNetflowMIB3206 The Netflow MIB provides a simple and easy method
to get NetFlow cache information, current NetFlow
configuration and statistics.…
1.3.6.1.4.1.9.9.388 ciscoVirtualSwitchMIB3128 This MIB module defines the managed objects that support the
virtual switch architecture.

The virtual switch concept combines sev…
1.3.6.1.4.1.9.9.389 ciscoVoiceCasModuleMIB322 This MIB is used to support Programmable
CAS signaling Bit configuration on modules
that support voice traffic.

This MIB will enab…
1.3.6.1.4.1.9.9.390 ciscoCableDiagMIB333 This MIB module defines objects for managing cable
diagnostic test capabilites supported by the Cisco devices.

Cable diagnostic t…
1.3.6.1.4.1.9.9.391 ciscoFcspMIB346 MIB module for managing Fibre Channel Security for the
fibre channel devices.

This MIB is used to configure and monitor the
Fibre-…
1.3.6.1.4.1.9.9.392 ciscoRemoteAccessMonitorMIB3200 Acronyms and Definitions
The following acronyms and terms are used in this
document:

IPSec: Secure IP Protocol

VPN: Virtual Priv…
1.3.6.1.4.1.9.9.393 ciscoVoiceConnectivityMIB344 This MIB module provides connectivity related
information for devices (e.g., 'connectivity between
voice gateway, phones, gatekee…
1.3.6.1.4.1.9.9.394 ciscoIpTapMIB328 This module manages Cisco's intercept feature for IP.

This MIB is used along with CISCO-TAP2-MIB to
intercept IP traffic. CISCO-T…
1.3.6.1.4.1.9.9.395 cisco802TapMIB320 This module manages Cisco's intercept feature for
802 (layer 2) streams.

This MIB is used along with CISCO-TAP2-MIB to
intercept 8…
1.3.6.1.4.1.9.9.396 ciscoMlrMIB3190 The MIB for providing information about Multi-layer
Routing(MLR). This MIB will provide information used to
control and measure S…
1.3.6.1.4.1.9.9.397 ciscoH225MIB1176 Cisco H225 MIB module. This module consists of H225
call signaling and H225 RAS (Registration, Admission
and Status). These are p…
1.3.6.1.4.1.9.9.398 ciscoMauExtMIB323 A MIB module for extending the MAU-MIB (RFC 3636)
to add objects which provide additional management
information about MAU or Jac…
1.3.6.1.4.1.9.9.399 ciscoTap2MIB369 This module manages Cisco's intercept feature.
This MIB replaces CISCO-TAP-MIB. This MIB defines
a generic stream table that cont…
1.3.6.1.4.1.9.9.400 ciscoUserConnectionTapMIB213 This module manages Cisco's intercept feature for
user connections.

This MIB is used along with CISCO-TAP2-MIB to
intercept user t…
1.3.6.1.4.1.9.9.401 ciscoBridgeExtMIB334 A MIB module for extending BRIDGE-MIB specified in RFC 1493.
1.3.6.1.4.1.9.9.402 ciscoPowerEthernetExtMIB383 A MIB module for extending the POWER-ETHERNET-MIB
(RFC3621) to add objects which provide additional
management information about …
1.3.6.1.4.1.9.9.405 ciscoDnsServerMIB3408 The MIB module for entities implementing the server side
of the Domain Name System (DNS) protocol.
P. Mockapetris, 'Domain names …
1.3.6.1.4.1.9.9.407 ciscoAtmTrunkStatMIB3101 The MIB module contains ATM Trunk statistics.

TERMINOLOGY

PVC: Permanent Virtual Circuit
OAM: Operation and Management
CRC: Cyclic…
1.3.6.1.4.1.9.9.408 ciscoSnmpNotificationExtMIB313 This MIB extends the functionality provided
by SNMP-NOTIFICATION-MIB.
This MIB provides for the aging of the
notification filters …
1.3.6.1.4.1.9.9.409 ciscoSnmpVacmExtMIB211 The management information definitions to extend
the View-based Access Control Model (RFC3415) for
SNMP.

This MIB extends the 'SN…
1.3.6.1.4.1.9.9.411 ciscoVlanTranslationMIB327 The MIB module for the management of VLAN translations.

VLAN translation refers to the ability of the device
to translate between…
1.3.6.1.4.1.9.9.412 ciscoSnmpTargetExtMIB230 This MIB is an extension of the SNMP-TARGET-MIB
specified in RFC3413.

This MIB module contains Cisco-defined extension
to the sn…
1.3.6.1.4.1.9.9.413 ciscoDot11SsidSecMIB271 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
devices association and authentication.

ACR…
1.3.6.1.4.1.9.9.414 ciscoPoePdMIB317 This MIB is intended for devices powered by
external power sources, in particular Power
Over Ethernet (PoE or formerly called inl…
1.3.6.1.4.1.9.9.415 ciscoWlanManMIB313 This MIB module provides network management
and configuration support for IEEE 802.11
Wireless LAN devices.

ACRONYMS

HTTP
Hypertext …
1.3.6.1.4.1.9.9.416 ciscoDot11QosMIB349 This MIB module provides network management
support for QoS on wireless LAN devices. The
objects defined in this MIB provide equ…
1.3.6.1.4.1.9.9.420 ciscoUnityExpressMIB3179 The MIB Module for the management of the Cisco Unity
Express (CUE) service. CUE is a voicemail service that
runs in a Cisco rout…
1.3.6.1.4.1.9.9.421 ciscoDpvmMIB355 The MIB module for the management of the
Dynamic Port Vsan Membership (DPVM) module.
DPVM provides the ability to assign (virtual
…
1.3.6.1.4.1.9.9.422 ciscoIPsecTc00 This MIB module defines the textual conventions
used in the IPsec suite of MIBs. This includes
Internet DOI numbers defined in RF…
1.3.6.1.4.1.9.9.423 ciscoIkeConfigMIB393 This is a MIB Module for configuring and viewing IKE
parameters and policies.

Acronyms
The following acronyms are used in this do…
1.3.6.1.4.1.9.9.424 ciscoCableMeteringMIB353 This is the MIB module for Usage Based Metering for the
DOCSIS-compliant Cable Modem Termination Systems (CMTS).

Usage Based Mete…
1.3.6.1.4.1.9.9.426 ciscoLinkErrorMonitorMIB334 The MIB module for managing Link Error Monitoring
Feature on devices.

Link Error Monitoring Feature provides a mechanism
to monito…
1.3.6.1.4.1.9.9.427 ciscoZsExtMIB333 The MIB module for the management of zoning within
the framework of Cisco's Zoning Server (ZS) Archi-
tecture which realizes the …
1.3.6.1.4.1.9.9.428 ciscoIkeFlowExtMIB318 This MIB module is an extension to
CISCO-IKE-FLOW-MIB and contains Cisco Specific
extensions for monitoring IKE.

It is for monito…
1.3.6.1.4.1.9.9.429 ciscoIkeFlowMIB380 This is a MIB module for monitoring the structures
and status of IPsec control flows based on Internet
Key Exchange protocol. The…
1.3.6.1.4.1.9.9.430 ciscoFcDeviceAliasMIB314 The MIB module for the management of Device
Aliases in a Fibre Channel Fabric. A Fibre
Channel fabric consists of devices such as
…
1.3.6.1.4.1.9.9.431 ciscoIPsecProvisioningMIB398 IPSec is the next-generation network layer crypto
framework described in RFC2401-2411.
This MIB defines the IPsec configurations.
…
1.3.6.1.4.1.9.9.432 ciscoEnhancedIpsecFlowMIB3330 This is a MIB Module for monitoring the structures
and status of IPSec-based networks. The MIB has been
designed to be adopted as…
1.3.6.1.4.1.9.9.433 ciscoCFSMIB3102 This MIB applies to one or more of a set of devices
which have connectivity through some kind of 'fabric'.
Many features which ru…
1.3.6.1.4.1.9.9.434 ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB358 MIB to provide the information about the disjoint
IP networks connected to the various gigabit ethernet
interfaces in the 'Fabric…
1.3.6.1.4.1.9.9.435 ciscoFcMulticastMIB314 MIB module for monitoring and configuring
Fibre Channel Multicast feature.
1.3.6.1.4.1.9.9.436 ciscoDNSClientMIB328 The MIB module for entities implementing the client
side of the Domain Name System (DNS) protocol.
1.3.6.1.4.1.9.9.437 ciscoPortTrackMIB218 A MIB to configure the Port-Track feature.

When a link goes down, all the services which depend
on the link are notified of the o…
1.3.6.1.4.1.9.9.438 ciscoIPsecSignalingMIB3140 This MIB Module models status, performance and failures
of a protocol with the generic characteristics of signalling
protocols us…
1.3.6.1.4.1.9.9.439 ciscoCcmeMIB3338 This MIB allows management of Cisco CallManager Express
(CCME) feature in Cisco IOS. CCME is optional software
feature that enabl…
1.3.6.1.4.1.9.9.441 ciscoSrstMIB3149 This MIB allows management of Cisco Survivable Remote
Site Telephony (SRST) feature in Cisco IOS. SRST is
an optional software fe…