Reference record for OID 1.3.6.1.4.1.9.9.848

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 local mobility anchor to which the controller has the joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. 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. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Gateway Service provider node which assigns IP and maintains the tunneled clients. Tunnel Connection from Wireless LAN controller to the Gateway. Tunnel establishment from WLC and TGW(Tunnel Gateway), in case of Flex-AP, tunnel establishment between AP and TGW. 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.

Status in source: unspecified.

Names: ciscoLwappTunnelMIB

{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoLwappTunnelMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313930363033303030305a22"
    ],
    "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-snmp@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 local mobility anchor to which the controller has the joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. 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. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Gateway Service provider node which assigns IP and maintains the tunneled clients. Tunnel Connection from Wireless LAN controller to the Gateway. Tunnel establishment from WLC and TGW(Tunnel Gateway), in case of Flex-AP, tunnel establishment between AP and TGW. 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",
      "223230313930363033303030305a22"
    ],
    "DESCRIPTION",
    "\"Created: - ciscoLwappTunnelMIBComplianceRev5 - cLTunnelConfigGroupRev3 - cLGatewayTunnelSourceInterface - clGatewayDomainAdminStatus - clGatewayDomainRedundancyModel - clGatewayProfileAdminStatus - clGatewayProfileAAAOverride Added to clGatewayTunnelEntry and cLTunnelConfigGroupRev3: - cLGatewayTunnelSourceInterface - clGatewayDomainAdminStatus - clGatewayDomainRedundancyModel - clGatewayProfileAdminStatus - clGatewayProfileAAAOverride Added cLTunnelConfigGroupRev3 to ciscoLwappTunnelMIBComplianceRev5\"",
    "REVISION",
    [
      "literal",
      "223230313830393036303030305a22"
    ],
    "DESCRIPTION",
    "\"Added a new module-compliance ciscoLwappTunnelMIBComplianceRev4, new object groups cLGatewayAAAProxyConfigGroup, a new table cLGatewayAAAProxyConfigTable with cLGatewayAAAProxyKey, cLGatewayAAAProxyKeyType, cLGatewayAAAProxyPort, cLGatewayAAAProxyRowStatus to allow for new configuration model of AAA Proxy on gateways. Added a new field clGatewayRuleRealm in CLGatewayRuleTable.\"",
    "REVISION",
    [
      "literal",
      "223230313830373031303030305a22"
    ],
    "DESCRIPTION",
    "\"Added a new module-compliance ciscoLwappTunnelMIBComplianceRev3, new object groups clApGatewayTunnelStatsGroup, clGatewayWlanProfileConfigGroup and cLTunnelConfigGroupRev2, a new table cLGatewayWlanProfileConfigTable with cLGatewayWlanProfileTunnelProfile to match new configuration model and clApGatewayTunnelStatsTunnelRxBytes64, clApGatewayTunnelStatsTunnelTxBytes64, clApGatewayTunnelStatsTunnelRxPkts64, clApGatewayTunnelStatsTunnelTxPkts64 in clApGatewayTunnelStatsTable\"",
    "REVISION",
    [
      "literal",
      "223230313830323035303030305a22"
    ],
    "DESCRIPTION",
    "\"Added a new table -cLGatewayWlanConfigTable\"",
    "REVISION",
    [
      "literal",
      "223230313730393230303030305a22"
    ],
    "DESCRIPTION",
    "\"Added clApGatewayTunnelMtu and clApGatewayTunnelFlapCount in ClApGatewayTunnelTable and clGatewayTunnelAdminStatus, clGatewayTunnelMtu and clGatewayTunnelFlapCount clGatewayTunnelTable.\"",
    "REVISION",
    [
      "literal",
      "223230313730353236303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "848",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201906030000Z"
    ],
    [
      "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-snmp@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 local mobility anchor to which the controller has the joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. 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. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Gateway Service provider node which assigns IP and maintains the tunneled clients. Tunnel Connection from Wireless LAN controller to the Gateway. Tunnel establishment from WLC and TGW(Tunnel Gateway), in case of Flex-AP, tunnel establishment between AP and TGW. 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",
      [
        [
          "201906030000Z",
          [
            "DESCRIPTION",
            "Created: - ciscoLwappTunnelMIBComplianceRev5 - cLTunnelConfigGroupRev3 - cLGatewayTunnelSourceInterface - clGatewayDomainAdminStatus - clGatewayDomainRedundancyModel - clGatewayProfileAdminStatus - clGatewayProfileAAAOverride Added to clGatewayTunnelEntry and cLTunnelConfigGroupRev3: - cLGatewayTunnelSourceInterface - clGatewayDomainAdminStatus - clGatewayDomainRedundancyModel - clGatewayProfileAdminStatus - clGatewayProfileAAAOverride Added cLTunnelConfigGroupRev3 to ciscoLwappTunnelMIBComplianceRev5"
          ]
        ],
        [
          "201809060000Z",
          [
            "DESCRIPTION",
            "Added a new module-compliance ciscoLwappTunnelMIBComplianceRev4, new object groups cLGatewayAAAProxyConfigGroup, a new table cLGatewayAAAProxyConfigTable with cLGatewayAAAProxyKey, cLGatewayAAAProxyKeyType, cLGatewayAAAProxyPort, cLGatewayAAAProxyRowStatus to allow for new configuration model of AAA Proxy on gateways. Added a new field clGatewayRuleRealm in CLGatewayRuleTable."
          ]
        ],
        [
          "201807010000Z",
          [
            "DESCRIPTION",
            "Added a new module-compliance ciscoLwappTunnelMIBComplianceRev3, new object groups clApGatewayTunnelStatsGroup, clGatewayWlanProfileConfigGroup and cLTunnelConfigGroupRev2, a new table cLGatewayWlanProfileConfigTable with cLGatewayWlanProfileTunnelProfile to match new configuration model and clApGatewayTunnelStatsTunnelRxBytes64, clApGatewayTunnelStatsTunnelTxBytes64, clApGatewayTunnelStatsTunnelRxPkts64, clApGatewayTunnelStatsTunnelTxPkts64 in clApGatewayTunnelStatsTable"
          ]
        ],
        [
          "201802050000Z",
          [
            "DESCRIPTION",
            "Added a new table -cLGatewayWlanConfigTable"
          ]
        ],
        [
          "201709200000Z",
          [
            "DESCRIPTION",
            "Added clApGatewayTunnelMtu and clApGatewayTunnelFlapCount in ClApGatewayTunnelTable and clGatewayTunnelAdminStatus, clGatewayTunnelMtu and clGatewayTunnelFlapCount clGatewayTunnelTable."
          ]
        ],
        [
          "201705260000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}

• Cisco · Publisher's source file · Archived source file
  Source location: CISCO-LWAPP-TUNNEL-MIB::ciscoLwappTunnelMIB.
  Source version and references

  Downloaded: 2026-10-19T00:18:11.713327+00:00. SHA-256: b8c6678d1299bf0222825d06b0ce7dd976fed3d0c21acdbe83b6cc42539c90bd

  {'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-TUNNEL-MIB', 'imports': {'CISCO-TC': ['Unsigned64'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'MacAddress', 'RowStatus', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'CISCO-LWAPP-AP-MIB': ['cLApIfMacAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'CISCO-LWAPP-WLAN-MIB': ['cLWlanIndex'], 'CISCO-LWAPP-WLAN-POLICY-MIB': ['cLWlanWlanPolicyName']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappTunnelMIB MODULE-IDENTITY\n    LAST-UPDATED    "201906030000Z"\n    ORGANIZATION    "Cisco Systems Inc."\n    CONTACT-INFO\n            "Cisco Systems,\n            Customer Service\n\n            Postal: 170 West Tasman Drive\n            San Jose, CA  95134\n            USA\n\n            Tel: +1 800 553-NETS\n\n            Email: cs-snmp@cisco.com"\n    DESCRIPTION\n        "This MIB is intended to be implemented on all those\n        devices operating as Central Controllers (CC) that\n        terminate the Light Weight Access Point Protocol\n        tunnel from Light-weight LWAPP Access Points.\n\n        This MIB provides configuration and status information\n        about local mobility anchor to which the controller has\n        the joined.\n\n        The relationship between CC and the LWAPP APs\n        can be depicted as follows:\n\n        +......+     +......+     +......+           +......+\n        +      +     +      +     +      +           +      +\n        +  LMA +     + LMA  +     + LMA  +           + LMA  +\n        +      +     +      +     +      +           +      +\n        +......+     +......+     +......+           +......+\n        ..            .             .                 .\n        ..            .             .                 .\n        .  .            .             .                 .\n        .    .            .             .                 .\n        .      .            .             .                 .\n        .        .            .             .                 .\n        +......+ +......+     +......+      +......+          +......+\n        +      + +      +     +      +      +      +          +      +\n        +  WLC + + WLC  +     + WLC  +      + WLC  +          + WLC  +\n        +      + +      +     +      +      +      +          +      +\n        +......+ +......+     +......+      +......+          +......+\n        .              .             .                 .\n        .  .              .             .                 .\n        .    .              .             .                 .\n        .      .              .             .                 .\n        .        .              .             .                 .\n        +......+ +......+     +......+      +......+          +......+\n        +      + +      +     +      +      +      +          +      +\n        +  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +\n        +      + +      +     +      +      +      +          +      +\n        +......+ +......+     +......+      +......+          +......+\n        .              .             .                 .\n        .  .              .             .                 .\n        .    .              .             .                 .\n        .      .              .             .                 .\n        .        .              .             .                 .\n        +......+ +......+     +......+      +......+          +......+\n        +      + +      +     +      +      +      +          +      +\n        +  MN  + +  MN  +     +  MN  +      +  MN  +          +  MN  +\n        +      + +      +     +      +      +      +          +      +\n        +......+ +......+     +......+      +......+          +......+\n\n\n        The LWAPP tunnel exists between the controller and\n        the APs.  The MNs communicate with the APs through\n        the protocol defined by the 802.11 standard.\n\n        LWAPP APs, upon bootup, discover and join one of the\n        controllers and the controller pushes the configuration,\n        that includes the WLAN parameters, to the LWAPP APs.\n        The APs then encapsulate all the 802.11 frames from\n        wireless clients inside LWAPP frames and forward\n        the LWAPP frames to the controller.\n\n                           GLOSSARY\n\n        Access Point ( AP )\n\n        An entity that contains an 802.11 medium access\n        control ( MAC ) and physical layer ( PHY ) interface\n        and provides access to the distribution services via\n        the wireless medium for associated clients.\n\n        LWAPP APs encapsulate all the 802.11 frames in\n        LWAPP frames and sends it to the controller to which\n        it is logically connected.\n\n        Central Controller ( CC )\n\n        The central entity that terminates the LWAPP protocol\n        tunnel from the LWAPP APs.  Throughout this MIB,\n        this entity also referred to as \'controller\'.\n\n        Light Weight Access Point Protocol ( LWAPP )\n\n        This is a generic protocol that defines the\n        communication between the Access Points and the\n        Central Controller.\n\n        Mobile Node ( MN )\n\n        A roaming 802.11 wireless device in a wireless\n        network associated with an access point.\n\n        Gateway\n\n        Service provider node which assigns IP and maintains the\n        tunneled clients.\n\n        Tunnel\n\n        Connection from Wireless LAN controller to the Gateway.\n        Tunnel establishment from WLC and TGW(Tunnel Gateway),\n        in case of Flex-AP, tunnel establishment between\n        AP and TGW.\n\n\n        REFERENCE\n\n        [1] Part 11 Wireless LAN Medium Access Control ( MAC )\n        and Physical Layer ( PHY ) Specifications.\n\n        [2] Draft-obara-capwap-lwapp-00.txt, IETF Light\n        Weight Access Point Protocol."\n    REVISION        "201906030000Z"\n    DESCRIPTION\n        "Created:\n        - ciscoLwappTunnelMIBComplianceRev5\n        - cLTunnelConfigGroupRev3\n        - cLGatewayTunnelSourceInterface\n        - clGatewayDomainAdminStatus\n        - clGatewayDomainRedundancyModel\n        - clGatewayProfileAdminStatus\n        - clGatewayProfileAAAOverride\n        Added to clGatewayTunnelEntry and cLTunnelConfigGroupRev3:\n        - cLGatewayTunnelSourceInterface\n        - clGatewayDomainAdminStatus\n        - clGatewayDomainRedundancyModel\n        - clGatewayProfileAdminStatus\n        - clGatewayProfileAAAOverride\n        Added cLTunnelConfigGroupRev3 to\n        ciscoLwappTunnelMIBComplianceRev5"\n    REVISION        "201809060000Z"\n    DESCRIPTION\n        "Added a new module-compliance ciscoLwappTunnelMIBComplianceRev4,\n        new object groups cLGatewayAAAProxyConfigGroup,\n        a new table cLGatewayAAAProxyConfigTable with\n        cLGatewayAAAProxyKey, cLGatewayAAAProxyKeyType,\n        cLGatewayAAAProxyPort, cLGatewayAAAProxyRowStatus to\n        allow for new configuration model of\n        AAA Proxy on gateways.\n        Added a new field clGatewayRuleRealm in CLGatewayRuleTable."\n    REVISION        "201807010000Z"\n    DESCRIPTION\n        "Added a new module-compliance ciscoLwappTunnelMIBComplianceRev3,\n        new object groups clApGatewayTunnelStatsGroup,\n        clGatewayWlanProfileConfigGroup and cLTunnelConfigGroupRev2,\n        a new table cLGatewayWlanProfileConfigTable with\n        cLGatewayWlanProfileTunnelProfile to match new configuration\n        model and clApGatewayTunnelStatsTunnelRxBytes64,\n        clApGatewayTunnelStatsTunnelTxBytes64,\n        clApGatewayTunnelStatsTunnelRxPkts64,\n        clApGatewayTunnelStatsTunnelTxPkts64 in\n        clApGatewayTunnelStatsTable"\n    REVISION        "201802050000Z"\n    DESCRIPTION\n        "Added a new table\n        -cLGatewayWlanConfigTable"\n    REVISION        "201709200000Z"\n    DESCRIPTION\n        "Added clApGatewayTunnelMtu and clApGatewayTunnelFlapCount in\n        ClApGatewayTunnelTable and clGatewayTunnelAdminStatus,\n        clGatewayTunnelMtu and clGatewayTunnelFlapCount\n        clGatewayTunnelTable."\n    REVISION        "201705260000Z"\n    DESCRIPTION\n        "Initial version of this MIB module."\n    ::= { ciscoMgmt 848 }', 'syntax_tree': [['LAST-UPDATED', '201906030000Z'], ['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-snmp@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 local mobility anchor to which the controller has the joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. 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. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Gateway Service provider node which assigns IP and maintains the tunneled clients. Tunnel Connection from Wireless LAN controller to the Gateway. Tunnel establishment from WLC and TGW(Tunnel Gateway), in case of Flex-AP, tunnel establishment between AP and TGW. 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', [['201906030000Z', ['DESCRIPTION', 'Created: - ciscoLwappTunnelMIBComplianceRev5 - cLTunnelConfigGroupRev3 - cLGatewayTunnelSourceInterface - clGatewayDomainAdminStatus - clGatewayDomainRedundancyModel - clGatewayProfileAdminStatus - clGatewayProfileAAAOverride Added to clGatewayTunnelEntry and cLTunnelConfigGroupRev3: - cLGatewayTunnelSourceInterface - clGatewayDomainAdminStatus - clGatewayDomainRedundancyModel - clGatewayProfileAdminStatus - clGatewayProfileAAAOverride Added cLTunnelConfigGroupRev3 to ciscoLwappTunnelMIBComplianceRev5']], ['201809060000Z', ['DESCRIPTION', 'Added a new module-compliance ciscoLwappTunnelMIBComplianceRev4, new object groups cLGatewayAAAProxyConfigGroup, a new table cLGatewayAAAProxyConfigTable with cLGatewayAAAProxyKey, cLGatewayAAAProxyKeyType, cLGatewayAAAProxyPort, cLGatewayAAAProxyRowStatus to allow for new configuration model of AAA Proxy on gateways. Added a new field clGatewayRuleRealm in CLGatewayRuleTable.']], ['201807010000Z', ['DESCRIPTION', 'Added a new module-compliance ciscoLwappTunnelMIBComplianceRev3, new object groups clApGatewayTunnelStatsGroup, clGatewayWlanProfileConfigGroup and cLTunnelConfigGroupRev2, a new table cLGatewayWlanProfileConfigTable with cLGatewayWlanProfileTunnelProfile to match new configuration model and clApGatewayTunnelStatsTunnelRxBytes64, clApGatewayTunnelStatsTunnelTxBytes64, clApGatewayTunnelStatsTunnelRxPkts64, clApGatewayTunnelStatsTunnelTxPkts64 in clApGatewayTunnelStatsTable']], ['201802050000Z', ['DESCRIPTION', 'Added a new table -cLGatewayWlanConfigTable']], ['201709200000Z', ['DESCRIPTION', 'Added clApGatewayTunnelMtu and clApGatewayTunnelFlapCount in ClApGatewayTunnelTable and clGatewayTunnelAdminStatus, clGatewayTunnelMtu and clGatewayTunnelFlapCount clGatewayTunnelTable.']], ['201705260000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}