Reference record for OID 1.3.6.1.4.1.9.9.856

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 Cisco Light-weight LWAPP Access Points. This MIB helps to manage the RLANs on 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 RLAN 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 to. 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 controllers. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU or RLAN. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. 802.1x The IEEE ratified standard for enforcing port based access control. This was originally intended for use on wired LANs and later extended for use in 802.11 RLAN environments. This defines an architecture with three main parts - a supplicant (Ex. an 802.11 wireless client), an authenticator (the AP) and an authentication server(a Radius server). The authenticator passes messages back and forth between the supplicant and the authentication server to enable the supplicant get authenticated to the network. Temporal Key Integrity Protocol ( TKIP ) A security protocol defined to enhance the limitations of WEP. Message Integrity Check and per-packet keying on all WEP-encrypted frames are two significant enhancements provided by TKIP to WEP. Cisco Key Integrity Protocol ( CKIP ) A proprietary implementation similar to TKIP. CKIP implements key permutation for protecting the CKIP key against attacks. Other features of CKIP include expansion of encryption key to 16 bytes of length for key protection and MIC to ensure data integrity. Wired Equivalent Privacy ( WEP ) A security method defined by 802.11. WEP uses a symmetric key stream cipher called RC4 to encrypt the data packets. Wi-Fi Protected Access ( WPA ) Wi-Fi Protected Access (WPA and WPA2) are security systems created in response to several serious weaknesses found in Wired Equivalent Privacy (WEP). WPA implements the majority of the IEEE 802.11i standard, and was intended as an intermediate measure to take the place of WEP while 802.11i was prepared. WPA is designed to work with all wireless network interface cards, but not necessarily with first generation wireless access points. RLAN Layer 2 Security RLAN layer 2 (MAC) security defines the encryption and authentication approaches such as 802.1x, WPA, WPA2, CKIP and WEP. POE (Power Over Ethernet) Power over Ethernet or PoE describes any of several standardized or ad-hoc systems which pass electrical power along with data on Ethernet cabling. This allows a single cable to provide both data connection and electrical power to devices such as wireless access points or IP cameras. Multicast Domain Name System (mDNS) This is the underlying protocol that is used for Service advertisement and discovery in technologies like Bonjour, Zero Touch Configuration REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol [3] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, 2.4 GHz RF and IR standard.

Status in source: unspecified.

Names: ciscoLwappRlanMIB

{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoLwappRlanMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313931303137303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems Inc.\"",
    "CONTACT-INFO",
    "\"Cisco Systems, Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-wnbu-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 Cisco Light-weight LWAPP Access Points. This MIB helps to manage the RLANs on 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 RLAN 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 to. 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 controllers. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU or RLAN. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. 802.1x The IEEE ratified standard for enforcing port based access control. This was originally intended for use on wired LANs and later extended for use in 802.11 RLAN environments. This defines an architecture with three main parts - a supplicant (Ex. an 802.11 wireless client), an authenticator (the AP) and an authentication server(a Radius server). The authenticator passes messages back and forth between the supplicant and the authentication server to enable the supplicant get authenticated to the network. Temporal Key Integrity Protocol ( TKIP ) A security protocol defined to enhance the limitations of WEP. Message Integrity Check and per-packet keying on all WEP-encrypted frames are two significant enhancements provided by TKIP to WEP. Cisco Key Integrity Protocol ( CKIP ) A proprietary implementation similar to TKIP. CKIP implements key permutation for protecting the CKIP key against attacks. Other features of CKIP include expansion of encryption key to 16 bytes of length for key protection and MIC to ensure data integrity. Wired Equivalent Privacy ( WEP ) A security method defined by 802.11. WEP uses a symmetric key stream cipher called RC4 to encrypt the data packets. Wi-Fi Protected Access ( WPA ) Wi-Fi Protected Access (WPA and WPA2) are security systems created in response to several serious weaknesses found in Wired Equivalent Privacy (WEP). WPA implements the majority of the IEEE 802.11i standard, and was intended as an intermediate measure to take the place of WEP while 802.11i was prepared. WPA is designed to work with all wireless network interface cards, but not necessarily with first generation wireless access points. RLAN Layer 2 Security RLAN layer 2 (MAC) security defines the encryption and authentication approaches such as 802.1x, WPA, WPA2, CKIP and WEP. POE (Power Over Ethernet) Power over Ethernet or PoE describes any of several standardized or ad-hoc systems which pass electrical power along with data on Ethernet cabling. This allows a single cable to provide both data connection and electrical power to devices such as wireless access points or IP cameras. Multicast Domain Name System (mDNS) This is the underlying protocol that is used for Service advertisement and discovery in technologies like Bonjour, Zero Touch Configuration REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol [3] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, 2.4 GHz RF and IR standard.\"",
    "REVISION",
    [
      "literal",
      "223230313930363231303030305a22"
    ],
    "DESCRIPTION",
    "\"Added below entry to cLRlanTable - cLRlanMdnsMode Added below entry to cLRlanPolicyEntry table - cLRlanMdnsPolicy Rearranged value for cLRlanHostMode Deprecated the following compliance group - ciscoLwappRlanComplianceRev1 Added following compliance group - ciscoLwappRlanComplianceRev2\"",
    "REVISION",
    [
      "literal",
      "223230313930343233303030305a22"
    ],
    "DESCRIPTION",
    "\"Deprecated following objects - cLRlanRadiusHttpProfiling - cLRlanRadiusDhcpProfiling - cLRlanLocalHttpProfiling - cLRlanLocalDhcpProfiling\"",
    "REVISION",
    [
      "literal",
      "223230313830373230303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "856",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201910170000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems, Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-wnbu-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 Cisco Light-weight LWAPP Access Points. This MIB helps to manage the RLANs on 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 RLAN 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 to. 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 controllers. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU or RLAN. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. 802.1x The IEEE ratified standard for enforcing port based access control. This was originally intended for use on wired LANs and later extended for use in 802.11 RLAN environments. This defines an architecture with three main parts - a supplicant (Ex. an 802.11 wireless client), an authenticator (the AP) and an authentication server(a Radius server). The authenticator passes messages back and forth between the supplicant and the authentication server to enable the supplicant get authenticated to the network. Temporal Key Integrity Protocol ( TKIP ) A security protocol defined to enhance the limitations of WEP. Message Integrity Check and per-packet keying on all WEP-encrypted frames are two significant enhancements provided by TKIP to WEP. Cisco Key Integrity Protocol ( CKIP ) A proprietary implementation similar to TKIP. CKIP implements key permutation for protecting the CKIP key against attacks. Other features of CKIP include expansion of encryption key to 16 bytes of length for key protection and MIC to ensure data integrity. Wired Equivalent Privacy ( WEP ) A security method defined by 802.11. WEP uses a symmetric key stream cipher called RC4 to encrypt the data packets. Wi-Fi Protected Access ( WPA ) Wi-Fi Protected Access (WPA and WPA2) are security systems created in response to several serious weaknesses found in Wired Equivalent Privacy (WEP). WPA implements the majority of the IEEE 802.11i standard, and was intended as an intermediate measure to take the place of WEP while 802.11i was prepared. WPA is designed to work with all wireless network interface cards, but not necessarily with first generation wireless access points. RLAN Layer 2 Security RLAN layer 2 (MAC) security defines the encryption and authentication approaches such as 802.1x, WPA, WPA2, CKIP and WEP. POE (Power Over Ethernet) Power over Ethernet or PoE describes any of several standardized or ad-hoc systems which pass electrical power along with data on Ethernet cabling. This allows a single cable to provide both data connection and electrical power to devices such as wireless access points or IP cameras. Multicast Domain Name System (mDNS) This is the underlying protocol that is used for Service advertisement and discovery in technologies like Bonjour, Zero Touch Configuration REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol [3] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, 2.4 GHz RF and IR standard."
    ],
    [
      "Revisions",
      [
        [
          "201906210000Z",
          [
            "DESCRIPTION",
            "Added below entry to cLRlanTable - cLRlanMdnsMode Added below entry to cLRlanPolicyEntry table - cLRlanMdnsPolicy Rearranged value for cLRlanHostMode Deprecated the following compliance group - ciscoLwappRlanComplianceRev1 Added following compliance group - ciscoLwappRlanComplianceRev2"
          ]
        ],
        [
          "201904230000Z",
          [
            "DESCRIPTION",
            "Deprecated following objects - cLRlanRadiusHttpProfiling - cLRlanRadiusDhcpProfiling - cLRlanLocalHttpProfiling - cLRlanLocalDhcpProfiling"
          ]
        ],
        [
          "201807200000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}

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

  Downloaded: 2026-10-19T00:18:11.704961+00:00. SHA-256: 0f2c108bedbac6dc9ba5746aec4b3365a1859d5d1b4b99721365c772246264df

  {'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-RLAN-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappRlanMIB MODULE-IDENTITY\n    LAST-UPDATED    "201910170000Z"\n    ORGANIZATION    "Cisco Systems Inc."\n    CONTACT-INFO\n            "Cisco Systems,\n            Customer Service\n\n            Postal: 170 W Tasman Drive\n               San Jose, CA  95134\n               USA\n\n               Tel: +1 800 553-NETS\n\n            E-mail: cs-wnbu-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 Cisco Light-weight LWAPP Access Points.\n\n        This MIB helps to manage the RLANs on the controller.\n\n        The relationship between CC and the LWAPP APs\n        can be depicted as follows:\n\n        +......+     +......+     +......+           +......+\n        +      +     +      +     +      +           +      +\n        +  CC  +     +  CC  +     +  CC  +           +  CC  +\n        +      +     +      +     +      +           +      +\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        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 RLAN 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 to.\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        controllers.\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        Access Control List ( ACL )\n\n        A list of rules used to restrict the traffic reaching \n        an interface or the CPU or RLAN.  Each ACL is an ordered\n        set of rules and actions.  If a rule matches then the \n        action for that rule is applied to the packet.\n\n        802.1x\n\n        The IEEE ratified standard for enforcing port based\n        access control.  This was originally intended for\n        use on wired LANs and later extended for use in\n        802.11 RLAN environments.  This defines an\n        architecture with three main parts - a supplicant\n        (Ex. an 802.11 wireless client), an authenticator\n        (the AP) and an authentication server(a Radius\n        server).  The authenticator passes messages back\n        and forth between the supplicant and the\n        authentication server to enable the supplicant\n        get authenticated to the network.\n\n        Temporal Key Integrity Protocol ( TKIP )\n\n        A security protocol defined to enhance the limitations\n        of WEP.  Message Integrity Check and per-packet keying\n        on all WEP-encrypted frames are two significant\n        enhancements provided by TKIP to WEP.\n\n        Cisco Key Integrity Protocol ( CKIP )\n\n        A proprietary implementation similar to TKIP.  CKIP\n        implements key permutation for protecting the CKIP\n        key against attacks.  Other features of CKIP include\n        expansion of encryption key to 16 bytes of length for\n        key protection and MIC to ensure data integrity.\n\n        Wired Equivalent Privacy ( WEP )\n\n        A security method defined by 802.11. WEP uses a\n        symmetric key stream cipher called RC4 to encrypt the\n        data packets.\n\n        Wi-Fi Protected Access ( WPA )\n\n        Wi-Fi Protected Access (WPA and WPA2) are security\n        systems created in response to several serious\n        weaknesses found in Wired Equivalent Privacy (WEP).\n        WPA implements the majority of the IEEE 802.11i\n        standard, and was intended as an intermediate\n        measure to take the place of WEP while 802.11i was\n        prepared. WPA is designed to work with all wireless\n        network interface cards, but not necessarily with\n        first generation wireless access points.\n\n        RLAN Layer 2 Security\n\n        RLAN layer 2 (MAC) security defines the encryption and \n        authentication approaches such as 802.1x, WPA, \n        WPA2, CKIP and WEP.                \n\n        POE (Power Over Ethernet)\n\n        Power over Ethernet or PoE describes any of \n        several standardized or ad-hoc systems which \n        pass electrical power along with data on \n        Ethernet cabling. This allows a single cable \n        to provide both data connection and electrical \n        power to devices such as wireless\n        access points or IP cameras.\n\n        Multicast Domain Name System (mDNS)\n\n        This is the underlying protocol that is used for Service advertisement  \n        and discovery in technologies like Bonjour, Zero Touch Configuration \n\n        REFERENCE\n\n        [1] Wireless LAN Medium Access Control ( MAC ) and\n        Physical Layer ( PHY ) Specifications.\n\n        [2] Draft-obara-capwap-lwapp-00.txt, IETF Light \n        Weight Access Point Protocol \n\n        [3] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, \n        2.4 GHz RF and IR standard."\n    REVISION        "201906210000Z"\n    DESCRIPTION\n        "Added below entry to cLRlanTable\n        - cLRlanMdnsMode\n        Added below entry to cLRlanPolicyEntry table\n        - cLRlanMdnsPolicy\n        Rearranged value for cLRlanHostMode\n        Deprecated the following compliance group\n        - ciscoLwappRlanComplianceRev1                                       \n        Added following compliance group\n        - ciscoLwappRlanComplianceRev2"\n    REVISION        "201904230000Z"\n    DESCRIPTION\n        "Deprecated following objects\n        - cLRlanRadiusHttpProfiling\n        - cLRlanRadiusDhcpProfiling\n        - cLRlanLocalHttpProfiling\n        - cLRlanLocalDhcpProfiling"\n    REVISION        "201807200000Z"\n    DESCRIPTION\n        "Initial version of this MIB module."\n    ::= { ciscoMgmt 856 }', 'syntax_tree': [['LAST-UPDATED', '201910170000Z'], ['ORGANIZATION', 'Cisco Systems Inc.'], ['CONTACT-INFO', 'Cisco Systems, Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-wnbu-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 Cisco Light-weight LWAPP Access Points. This MIB helps to manage the RLANs on 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 RLAN 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 to. 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 controllers. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU or RLAN. Each ACL is an ordered set of rules and actions. If a rule matches then the action for that rule is applied to the packet. 802.1x The IEEE ratified standard for enforcing port based access control. This was originally intended for use on wired LANs and later extended for use in 802.11 RLAN environments. This defines an architecture with three main parts - a supplicant (Ex. an 802.11 wireless client), an authenticator (the AP) and an authentication server(a Radius server). The authenticator passes messages back and forth between the supplicant and the authentication server to enable the supplicant get authenticated to the network. Temporal Key Integrity Protocol ( TKIP ) A security protocol defined to enhance the limitations of WEP. Message Integrity Check and per-packet keying on all WEP-encrypted frames are two significant enhancements provided by TKIP to WEP. Cisco Key Integrity Protocol ( CKIP ) A proprietary implementation similar to TKIP. CKIP implements key permutation for protecting the CKIP key against attacks. Other features of CKIP include expansion of encryption key to 16 bytes of length for key protection and MIC to ensure data integrity. Wired Equivalent Privacy ( WEP ) A security method defined by 802.11. WEP uses a symmetric key stream cipher called RC4 to encrypt the data packets. Wi-Fi Protected Access ( WPA ) Wi-Fi Protected Access (WPA and WPA2) are security systems created in response to several serious weaknesses found in Wired Equivalent Privacy (WEP). WPA implements the majority of the IEEE 802.11i standard, and was intended as an intermediate measure to take the place of WEP while 802.11i was prepared. WPA is designed to work with all wireless network interface cards, but not necessarily with first generation wireless access points. RLAN Layer 2 Security RLAN layer 2 (MAC) security defines the encryption and authentication approaches such as 802.1x, WPA, WPA2, CKIP and WEP. POE (Power Over Ethernet) Power over Ethernet or PoE describes any of several standardized or ad-hoc systems which pass electrical power along with data on Ethernet cabling. This allows a single cable to provide both data connection and electrical power to devices such as wireless access points or IP cameras. Multicast Domain Name System (mDNS) This is the underlying protocol that is used for Service advertisement and discovery in technologies like Bonjour, Zero Touch Configuration REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol [3] IEEE 802.11 - The original 1 Mbit/s and 2 Mbit/s, 2.4 GHz RF and IR standard."], ['Revisions', [['201906210000Z', ['DESCRIPTION', 'Added below entry to cLRlanTable - cLRlanMdnsMode Added below entry to cLRlanPolicyEntry table - cLRlanMdnsPolicy Rearranged value for cLRlanHostMode Deprecated the following compliance group - ciscoLwappRlanComplianceRev1 Added following compliance group - ciscoLwappRlanComplianceRev2']], ['201904230000Z', ['DESCRIPTION', 'Deprecated following objects - cLRlanRadiusHttpProfiling - cLRlanRadiusDhcpProfiling - cLRlanLocalHttpProfiling - cLRlanLocalDhcpProfiling']], ['201807200000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}