Reference record for OID 1.3.6.1.4.1.9.9.577

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
577
Node name
ciscoLwappAclMIB
Numeric OID
1.3.6.1.4.1.9.9.577
URN notation
urn:oid:1.3.6.1.4.1.9.9.577
Type
OBJECT IDENTIFIER
ASN.1 notation

{1 3 6 1 4 1 9 9 577}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappAclMIB(577)}
  • ...skipped...
OID-IRI notation
  • /1/3/6/1/4/1/9/9/577
  • /ISO/Identified-Organization/6/1/4/1/9/9/577
  • /ISO/3/6/1/4/1/9/9/577
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/org/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappAclMIB
  • /iso/org/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappAclMIB
  • ...skipped...
All recorded component names

Each component can use any of its recorded names. The examples above show up to eight combinations. ASN.1 names do not necessarily have registered OID-IRI labels.

  • 1: iso
  • 1.3: identified-organization, org, iso-identified-organization, iso-organization
  • 1.3.6: dod
  • 1.3.6.1: internet
  • 1.3.6.1.4: private
  • 1.3.6.1.4.1: enterprise, enterprises, ldap-enterprise, vendor-objects
  • 1.3.6.1.4.1.9: cisco
  • 1.3.6.1.4.1.9.9: ciscoMgmt
  • 1.3.6.1.4.1.9.9.577: ciscoLwappAclMIB

Source records

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 the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. 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. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming through the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.

Status in source: unspecified.

Names: ciscoLwappAclMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoLwappAclMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313730343234303030305a22"
    ],
    "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-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 the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. 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. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming through the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.\"",
    "REVISION",
    [
      "literal",
      "223230313730343234303030305a22"
    ],
    "DESCRIPTION",
    "\"Changed name claAclUrl to claAclUrlName.\"",
    "REVISION",
    [
      "literal",
      "223230313030333034303030305a22"
    ],
    "DESCRIPTION",
    "\"Added claAclTable and claAclRuleTable.\"",
    "REVISION",
    [
      "literal",
      "223230303630383239303030305a22"
    ],
    "DESCRIPTION",
    "\"Moved scalar attributes to claCpuAclTable.\"",
    "REVISION",
    [
      "literal",
      "223230303630373139303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "577",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201704240000Z"
    ],
    [
      "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-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 the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. 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. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming through the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications."
    ],
    [
      "Revisions",
      [
        [
          "201704240000Z",
          [
            "DESCRIPTION",
            "Changed name claAclUrl to claAclUrlName."
          ]
        ],
        [
          "201003040000Z",
          [
            "DESCRIPTION",
            "Added claAclTable and claAclRuleTable."
          ]
        ],
        [
          "200608290000Z",
          [
            "DESCRIPTION",
            "Moved scalar attributes to claCpuAclTable."
          ]
        ],
        [
          "200607190000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • Cisco · Publisher's source file · Archived source file
    Source location: CISCO-LWAPP-ACL-MIB::ciscoLwappAclMIB.
    Source version and references

    Downloaded: 2026-10-19T00:18:11.660025+00:00. SHA-256: c3975cdd4c469b3b81a2d01a75c8567f0cb2514634b009f4f187f2ee1c1a8081

    {'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-ACL-MIB', 'imports': {'CISCO-TC': ['CiscoURLString'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappAclMIB MODULE-IDENTITY\n    LAST-UPDATED    "201704240000Z"\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-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 Light-weight LWAPP Access Points.\n\n        This MIB provides configuration and status information\n        about the ACLs on the controller.\n\n        Particularly this mib covers the CPU ACLs for the wireless\n        controllers.\n\n        Traffic to the controller CPU comes from the NPU (Network\n        Processing Unit).\n\n        Using CPU ACLs, the user can place restrictions on type of\n        traffic reaching the CPU of the controller from the NPU.      \n\n        CPU ACLs introduce an ACL for the traffic to the CPU of\n        controller. With this ACL the type of packets reaching the\n        CPU can be controlled. The mode of operation is as follows.\n\n        The administrator designates one ACL for the traffic to the\n        CPU. The ACL kicks in for packets from the NPU to the CPU.\n        Each ACL is an ordered set of rules. If a rule matches then\n        action for that rule is applied to the packet. The decision\n        to send or drop the packet is taken based on the action\n        parameter of the ACL.\n\n        There will be no ACL for the packets from the CPU to the\n        NPU.\n\n\n                                GLOSSARY                              \n\n        Access Control List ( ACL )\n\n        A list of rules used to restrict the traffic reaching an\n        interface or the CPU.  Each ACL is an ordered set of rules\n        and actions.  If a rule matches then the action for that \n        rule is applied to the packet.\n\n        Access Point ( AP )\n\n        An entity that contains an 802.11 medium access control \n        ( MAC ) and physical layer ( PHY ) interface and provides\n        acess to the distribution services via the wireless medium\n        for associated clients.\n\n        CPU ACL ( CPU ACL )\n\n        The ACL applied to the CPU.  This controls the type of \n        traffic reaching the CPU of the controller.\n\n        Network Processing Unit ( NPU )\n\n        This entity is responsible for forwarding traffic to the\n        CPU. The only exceptions are data coming through the \n        console port and the Service port i.e. these communicate\n        directly with the CPU and not via the NPU.\n\n        Light Weight Access Point Protocol ( LWAPP )\n\n        This is a generic protocol that defines the communciation\n        between the Access Points and the Central Controller.\n\n        REFERENCE\n\n        [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and\n        Physical Layer ( PHY ) Specifications."\n    REVISION        "201704240000Z"\n    DESCRIPTION\n        "Changed name claAclUrl to claAclUrlName."\n    REVISION        "201003040000Z"\n    DESCRIPTION\n        "Added claAclTable and claAclRuleTable."\n    REVISION        "200608290000Z"\n    DESCRIPTION\n        "Moved scalar attributes to claCpuAclTable."\n    REVISION        "200607190000Z"\n    DESCRIPTION\n        "Initial version of this MIB module."\n    ::= { ciscoMgmt 577 }', 'syntax_tree': [['LAST-UPDATED', '201704240000Z'], ['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-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 the ACLs on the controller. Particularly this mib covers the CPU ACLs for the wireless controllers. Traffic to the controller CPU comes from the NPU (Network Processing Unit). Using CPU ACLs, the user can place restrictions on type of traffic reaching the CPU of the controller from the NPU. CPU ACLs introduce an ACL for the traffic to the CPU of controller. With this ACL the type of packets reaching the CPU can be controlled. The mode of operation is as follows. The administrator designates one ACL for the traffic to the CPU. The ACL kicks in for packets from the NPU to the CPU. Each ACL is an ordered set of rules. If a rule matches then action for that rule is applied to the packet. The decision to send or drop the packet is taken based on the action parameter of the ACL. There will be no ACL for the packets from the CPU to the NPU. GLOSSARY Access Control List ( ACL ) A list of rules used to restrict the traffic reaching an interface or the CPU. 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. Access Point ( AP ) An entity that contains an 802.11 medium access control ( MAC ) and physical layer ( PHY ) interface and provides acess to the distribution services via the wireless medium for associated clients. CPU ACL ( CPU ACL ) The ACL applied to the CPU. This controls the type of traffic reaching the CPU of the controller. Network Processing Unit ( NPU ) This entity is responsible for forwarding traffic to the CPU. The only exceptions are data coming through the console port and the Service port i.e. these communicate directly with the CPU and not via the NPU. Light Weight Access Point Protocol ( LWAPP ) This is a generic protocol that defines the communciation between the Access Points and the Central Controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications.'], ['Revisions', [['201704240000Z', ['DESCRIPTION', 'Changed name claAclUrl to claAclUrlName.']], ['201003040000Z', ['DESCRIPTION', 'Added claAclTable and claAclRuleTable.']], ['200608290000Z', ['DESCRIPTION', 'Moved scalar attributes to claCpuAclTable.']], ['200607190000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}

Descriptions may differ between sources. The primary description is shown first.

Primary description: Circitor

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 the ACLs on the controller.

Particularly this mib covers the CPU ACLs for the wireless
controllers.

Traffic to the controller CPU comes from the NPU (Network
Processing Unit).

Using CPU ACLs, the user can place restrictions on type of
traffic reaching the CPU of the controller from the NPU.



CPU ACLs introduce an ACL for the traffic to the CPU of
controller. With this ACL the type of packets reaching the
CPU can be controlled. The mode of operation is as follows.

The administrator designates one ACL for the traffic to the
CPU. The ACL kicks in for packets from the NPU to the CPU.
Each ACL is an ordered set of rules. If a rule matches then
action for that rule is applied to the packet. The decision
to send or drop the packet is taken based on the action
parameter of the ACL.

There will be no ACL for the packets from the CPU to the
NPU.



GLOSSARY


Access Control List ( ACL )

A list of rules used to restrict the traffic reaching an
interface or the CPU. 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.



Access Point ( AP )

An entity that contains an 802.11 medium access control
( MAC ) and physical layer ( PHY ) interface and provides
acess to the distribution services via the wireless medium
for associated clients.


CPU ACL ( CPU ACL )

The ACL applied to the CPU. This controls the type of
traffic reaching the CPU of the controller.



Network Processing Unit ( NPU )

This entity is responsible for forwarding traffic to the
CPU. The only exceptions are data coming thorugh the
console port and the Service port i.e. these communicate
directly with the CPU and not via the NPU.


Light Weight Access Point Protocol ( LWAPP )

This is a generic protocol that defines the communciation
between the Access Points and the Central Controller.



REFERENCE

[1] Part 11 Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications.

Parsed from file CISCO-LWAPP-ACL-MIB.mib
Module: CISCO-LWAPP-ACL-MIB

Source file: Download CISCO-LWAPP-ACL-MIB.mib SHA-256: 369c1d3c6459fe2c7f4bed68dd405264ce896999b1d41496b7f742cf30394783

Alternative description: Cisco

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 the ACLs on the controller.

Particularly this mib covers the CPU ACLs for the wireless
controllers.

Traffic to the controller CPU comes from the NPU (Network
Processing Unit).

Using CPU ACLs, the user can place restrictions on type of
traffic reaching the CPU of the controller from the NPU.



CPU ACLs introduce an ACL for the traffic to the CPU of
controller. With this ACL the type of packets reaching the
CPU can be controlled. The mode of operation is as follows.

The administrator designates one ACL for the traffic to the
CPU. The ACL kicks in for packets from the NPU to the CPU.
Each ACL is an ordered set of rules. If a rule matches then
action for that rule is applied to the packet. The decision
to send or drop the packet is taken based on the action
parameter of the ACL.

There will be no ACL for the packets from the CPU to the
NPU.



GLOSSARY


Access Control List ( ACL )

A list of rules used to restrict the traffic reaching an
interface or the CPU. 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.



Access Point ( AP )

An entity that contains an 802.11 medium access control
( MAC ) and physical layer ( PHY ) interface and provides
acess to the distribution services via the wireless medium
for associated clients.


CPU ACL ( CPU ACL )

The ACL applied to the CPU. This controls the type of
traffic reaching the CPU of the controller.



Network Processing Unit ( NPU )

This entity is responsible for forwarding traffic to the
CPU. The only exceptions are data coming thorugh the
console port and the Service port i.e. these communicate
directly with the CPU and not via the NPU.


Light Weight Access Point Protocol ( LWAPP )

This is a generic protocol that defines the communciation
between the Access Points and the Central Controller.



REFERENCE

[1] Part 11 Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications.

Alternative description: MIBdepot

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 the ACLs on the controller.

Particularly this mib covers the CPU ACLs for the wireless
controllers.

Traffic to the controller CPU comes from the NPU (Network
Processing Unit).

Using CPU ACLs, the user can place restrictions on type of
traffic reaching the CPU of the controller from the NPU.



CPU ACLs introduce an ACL for the traffic to the CPU of
controller. With this ACL the type of packets reaching the
CPU can be controlled. The mode of operation is as follows.

The administrator designates one ACL for the traffic to the
CPU. The ACL kicks in for packets from the NPU to the CPU.
Each ACL is an ordered set of rules. If a rule matches then
action for that rule is applied to the packet. The decision
to send or drop the packet is taken based on the action
parameter of the ACL.

There will be no ACL for the packets from the CPU to the
NPU.



GLOSSARY


Access Control List ( ACL )

A list of rules used to restrict the traffic reaching an
interface or the CPU. 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.



Access Point ( AP )

An entity that contains an 802.11 medium access control
( MAC ) and physical layer ( PHY ) interface and provides
acess to the distribution services via the wireless medium
for associated clients.


CPU ACL ( CPU ACL )

The ACL applied to the CPU. This controls the type of
traffic reaching the CPU of the controller.



Network Processing Unit ( NPU )

This entity is responsible for forwarding traffic to the
CPU. The only exceptions are data coming thorugh the
console port and the Service port i.e. these communicate
directly with the CPU and not via the NPU.


Light Weight Access Point Protocol ( LWAPP )

This is a generic protocol that defines the communciation
between the Access Points and the Central Controller.



REFERENCE

[1] Part 11 Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications.

Source file: Download cisco/CISCO-LWAPP-ACL-MIB.my.txt SHA-256: 369c1d3c6459fe2c7f4bed68dd405264ce896999b1d41496b7f742cf30394783

Information from Circitor

ciscoLwappAclMIB MODULE-IDENTITY
    LAST-UPDATED    "200608290000Z"
    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-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 the ACLs on the controller.

            Particularly this mib covers the CPU ACLs for the wireless
            controllers.

            Traffic to the controller CPU comes from the NPU (Network
            Processing Unit).

            Using CPU ACLs, the user can place restrictions on type of
            traffic reaching the CPU of the controller from the NPU.      



            CPU ACLs introduce an ACL for the traffic to the CPU of
            controller. With this ACL the type of packets reaching the
            CPU can be controlled. The mode of operation is as follows.

            The administrator designates one ACL for the traffic to the
            CPU. The ACL kicks in for packets from the NPU to the CPU.
            Each ACL is an ordered set of rules. If a rule matches then
            action for that rule is applied to the packet. The decision
            to send or drop the packet is taken based on the action
            parameter of the ACL.

            There will be no ACL for the packets from the CPU to the
            NPU.



                                    GLOSSARY                              


            Access Control List ( ACL )

            A list of rules used to restrict the traffic reaching an
            interface or the CPU.  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.



            Access Point ( AP )

            An entity that contains an 802.11 medium access control 
            ( MAC ) and physical layer ( PHY ) interface and provides
            acess to the distribution services via the wireless medium
            for associated clients.


            CPU ACL ( CPU ACL )

            The ACL applied to the CPU.  This controls the type of 
            traffic reaching the CPU of the controller.



            Network Processing Unit ( NPU )

            This entity is responsible for forwarding traffic to the
            CPU. The only exceptions are data coming thorugh the 
            console port and the Service port i.e. these communicate
            directly with the CPU and not via the NPU.


            Light Weight Access Point Protocol ( LWAPP )

            This is a generic protocol that defines the communciation
            between the Access Points and the Central Controller.



            REFERENCE

            [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and
            Physical Layer ( PHY ) Specifications.
            "
    REVISION        "200608290000Z"
    DESCRIPTION
            "Moved scalar attributes to claCpuAclTable."
    REVISION        "200607190000Z"
    DESCRIPTION
            "Initial version of this MIB module."
          ::= { ciscoMgmt 577 }

Information from Cisco SMIv1

Source file: Download CISCO-LWAPP-ACL-MIB-V1SMI.my · Publisher's file SHA-256: 6675a08a9edf224811e0de7f4c787233347d3f535ed42061d0a087e57f47fe7c

Source file: Download cisco/CISCO-LWAPP-ACL-MIB-V1SMI.my.txt SHA-256: baa8042a3e677a2e3d33e90877c140caa8cbbcde97e871711582dce39aad3033

ciscoLwappAclMIB OBJECT IDENTIFIER ::= { ciscoMgmt 577 }

Information from OID Repository

Vendor: Cisco
Module: CISCO-LWAPP-ACL-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

ciscoLwappAclMIB MODULE-IDENTITY
    LAST-UPDATED    "200608290000Z"
    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-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 the ACLs on the controller.

            Particularly this mib covers the CPU ACLs for the wireless
            controllers.

            Traffic to the controller CPU comes from the NPU (Network
            Processing Unit).

            Using CPU ACLs, the user can place restrictions on type of
            traffic reaching the CPU of the controller from the NPU.      



            CPU ACLs introduce an ACL for the traffic to the CPU of
            controller. With this ACL the type of packets reaching the
            CPU can be controlled. The mode of operation is as follows.

            The administrator designates one ACL for the traffic to the
            CPU. The ACL kicks in for packets from the NPU to the CPU.
            Each ACL is an ordered set of rules. If a rule matches then
            action for that rule is applied to the packet. The decision
            to send or drop the packet is taken based on the action
            parameter of the ACL.

            There will be no ACL for the packets from the CPU to the
            NPU.



                                    GLOSSARY                              


            Access Control List ( ACL )

            A list of rules used to restrict the traffic reaching an
            interface or the CPU.  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.



            Access Point ( AP )

            An entity that contains an 802.11 medium access control 
            ( MAC ) and physical layer ( PHY ) interface and provides
            acess to the distribution services via the wireless medium
            for associated clients.


            CPU ACL ( CPU ACL )

            The ACL applied to the CPU.  This controls the type of 
            traffic reaching the CPU of the controller.



            Network Processing Unit ( NPU )

            This entity is responsible for forwarding traffic to the
            CPU. The only exceptions are data coming thorugh the 
            console port and the Service port i.e. these communicate
            directly with the CPU and not via the NPU.


            Light Weight Access Point Protocol ( LWAPP )

            This is a generic protocol that defines the communciation
            between the Access Points and the Central Controller.



            REFERENCE

            [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and
            Physical Layer ( PHY ) Specifications.
            "
    REVISION        "200608290000Z"
    DESCRIPTION
            "Moved scalar attributes to claCpuAclTable."
    REVISION        "200607190000Z"
    DESCRIPTION
            "Initial version of this MIB module."
          ::= { ciscoMgmt 577 }

Information from Cisco

ciscoLwappAclMIB MODULE-IDENTITY
    LAST-UPDATED    "201003040000Z"
    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-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 the ACLs on the controller.

        Particularly this mib covers the CPU ACLs for the wireless
        controllers.

        Traffic to the controller CPU comes from the NPU (Network
        Processing Unit).

        Using CPU ACLs, the user can place restrictions on type of
        traffic reaching the CPU of the controller from the NPU.      



        CPU ACLs introduce an ACL for the traffic to the CPU of
        controller. With this ACL the type of packets reaching the
        CPU can be controlled. The mode of operation is as follows.

        The administrator designates one ACL for the traffic to the
        CPU. The ACL kicks in for packets from the NPU to the CPU.
        Each ACL is an ordered set of rules. If a rule matches then
        action for that rule is applied to the packet. The decision
        to send or drop the packet is taken based on the action
        parameter of the ACL.

        There will be no ACL for the packets from the CPU to the
        NPU.



                                GLOSSARY                              


        Access Control List ( ACL )

        A list of rules used to restrict the traffic reaching an
        interface or the CPU.  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.



        Access Point ( AP )

        An entity that contains an 802.11 medium access control 
        ( MAC ) and physical layer ( PHY ) interface and provides
        acess to the distribution services via the wireless medium
        for associated clients.


        CPU ACL ( CPU ACL )

        The ACL applied to the CPU.  This controls the type of 
        traffic reaching the CPU of the controller.



        Network Processing Unit ( NPU )

        This entity is responsible for forwarding traffic to the
        CPU. The only exceptions are data coming thorugh the 
        console port and the Service port i.e. these communicate
        directly with the CPU and not via the NPU.


        Light Weight Access Point Protocol ( LWAPP )

        This is a generic protocol that defines the communciation
        between the Access Points and the Central Controller.



        REFERENCE

        [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and
        Physical Layer ( PHY ) Specifications."
    REVISION        "201003040000Z"
    DESCRIPTION
        "Added claAclTable and claAclRuleTable."
    REVISION        "200608290000Z"
    DESCRIPTION
        "Moved scalar attributes to claCpuAclTable."
    REVISION        "200607190000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 577 }

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.577.0 ciscoLwappAclMIBNotifs00
1.3.6.1.4.1.9.9.577.1 ciscoLwappAclMIBObjects338
1.3.6.1.4.1.9.9.577.2 ciscoLwappAclMIBConform26

Siblings (692)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.249 ciscoEnhancedImageMIB244 Initial version of the MIB. This MIB has Image table
containing the following information related to the
running IOS image
1. Enti…
1.3.6.1.4.1.9.9.252 cTapMIB380 This module manages Cisco's intercept feature.
1.3.6.1.4.1.9.9.253 ciscoItpXuaMIB3250 The MIB for MTP3 User Adaptation (M3UA) and SCCP User
Adaptation (SUA) for Cisco's IP Transfer Point (ITP)
implementation.

The Cis…
1.3.6.1.4.1.9.9.254 ciscoSlbExtMIB3425 The extended MIB for managing Server Load Balancing
Manager(s). This MIB extends the SLB management
functionality in the CISCO-SL…
1.3.6.1.4.1.9.9.255 ciscoFabricMcastMIB330 Fabric Multicast Resource MIB module.
This MIB module is used for managing/tracking the fabric
multicast resource related informa…
1.3.6.1.4.1.9.9.256 ciscoFabricMcastApplMIB316 Fabric multicast resource MIB module.
This MIB module is used for managing/tracking the fabric
multicast resource application rel…
1.3.6.1.4.1.9.9.257 ciscoFabricHfrMIB390 Cisco Enhanced Benes fabric MIB module.
This MIB module is used for managing/tracking the Ehanced
Benes Fabric entities and/or fa…
1.3.6.1.4.1.9.9.259 ciscoPsaMicrocodeMIB324 Cisco PSA Microcode MIB - Overview

The PSA is the Packet Switching ASIC used
in module like engine 2(E2) line cards in GSR
for IP …
1.3.6.1.4.1.9.9.260 ciscoSsgMIB3218 The MIB Module manages Service Selection Gateway(SSG)
devices.

Service Selection Gateway(SSG) is a switching solution
for service…
1.3.6.1.4.1.9.9.261 ciscoPtopoExtnMIB218 This MIB module contains extensions to the PTOPO-MIB that
provide support to distinguish between bidirectional and
unidirectional…
1.3.6.1.4.1.9.9.262 ciscoVoaMIB214 This MIB module defines objects to configure and manage the
Variable Optical Attenuator (VOA) modules.

VOA modules are typically …
1.3.6.1.4.1.9.9.263 ciscoIgmpSnoopingMIB3286 The MIB module for IGMP Snooping feature.

Internet Group Management Protocol (IGMP) is the protocol used
by IPv4 end hosts to ind…
1.3.6.1.4.1.9.9.264 ciscoOpticalMonitorMIB372 This MIB module defines objects to monitor optical
characteristics and set corresponding thresholds on the
optical interfaces in …
1.3.6.1.4.1.9.9.265 ciscoEntityPfeMib358 The Packet Forwarding Engine technology are Cisco developed
Network Processors, which accelerates certain features in
order to pr…
1.3.6.1.4.1.9.9.268 ciscoWlanVlanMIB341 This MIB module provides network management
support for device VLAN configuration on
IEEE 802.11 wireless LAN.

ACRONYMS
AES
Advanced…
1.3.6.1.4.1.9.9.269 ciscoTBridgeDevIfMIB220 This MIB module provides network management support
for configuration and status information of devices
supporting transparent br…
1.3.6.1.4.1.9.9.270 ciscoSyslogEventExtMIB221 This MIB module extends the Cisco Syslog
MIB and provides network management support
to handle and process Syslog messages as
devi…
1.3.6.1.4.1.9.9.271 ciscoL2DevMonMIB324 This MIB module is for monitoring of active
layer 2 devices by hot standby layer 2 devices
and the configuration of hot standby s…
1.3.6.1.4.1.9.9.272 ciscoDot11IfMIB3212 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
type device (Access Point) radio interface…
1.3.6.1.4.1.9.9.273 ciscoDot11AssociationMIB2107 This MIB module provides network management
information on IEEE 802.11 wireless device
association management and data packet for…
1.3.6.1.4.1.9.9.275 ciscoBcpMIB225 This MIB module describes the Managed Objects for
of Bridge Control Protocol (RFC2878). This MIB is
influenced by RFC1474.
1.3.6.1.4.1.9.9.276 ciscoIfExtensionMIB3147 A MIB module for extending the IF-MIB (RFC2863)
to add objects which provide additional information
about interfaces not availabl…
1.3.6.1.4.1.9.9.277 ciscoDdpIappMIB322 This MIB module describes the management support for
the Inter-Access Point Protocol (IAPP). IAPP is a
Cisco propriety Data Deli…
1.3.6.1.4.1.9.9.278 ciscoIpProtocolMIB363 The MIB module is for management of information
to support packet filtering on IP protocols.

The cippfIpProfileTable allows users…
1.3.6.1.4.1.9.9.279 ciscoAtmQosMIB367 The MIB is created to provide ATM QoS information in
these areas:

1. Traffic shaping on a per-VC basis
2. Traffic shaping on a pe…
1.3.6.1.4.1.9.9.280 ciscoOutageMIB375 This MIB module describes, stores, and reports outage
related information generated by individual hardware
and software component…
1.3.6.1.4.1.9.9.281 ciscoFabricC12kMIB3135 Cisco Fabric MIB module for c12000 series of routers.
This MIB module is used for managing/tracking the c12000
fabric entities an…
1.3.6.1.4.1.9.9.282 ciscoVsanMIB2104 The MIB module for the management of the Virtual Storage
Networks (VSANs) within the frame work of Cisco's VSAN
Architecture. T…
1.3.6.1.4.1.9.9.284 ciscoFcRouteMIB255 The MIB module for configuring and displaying FC (Fibre
Channel) Route Information.
1.3.6.1.4.1.9.9.285 ciscoPortChannelMIB243 The MIB module for management of Port Channel ports.
In addition to this MIB, CISCO-FC-FE-MIB and interface
mib (rfc2863) will al…
1.3.6.1.4.1.9.9.286 ciscoWwnmgrMIB238 The World Wide Name (WWN) in the fibre channel networking
technology is equivalent to the MAC address in Ethernet.
There are six …
1.3.6.1.4.1.9.9.287 ciscoFspfMIB495 Fabric Shortest Path First (FSPF) MIB.
1.3.6.1.4.1.9.9.288 ciscoRadiusMIB396 MIB module for monitoring and configuring
authentication and logging services using RADIUS
(Remote Authentication Dial In User Se…
1.3.6.1.4.1.9.9.289 ciscoFcFeMIB2352 This is the Cisco fibre element management MIB module.
It covers:
- Cisco extension to the interface MIB ( IF-MIB )
- Contains all…
1.3.6.1.4.1.9.9.290 ciscoVirtualNwIfMIB222 The MIB module for management of virtual network
interfaces to VSAN and VLAN.
1.3.6.1.4.1.9.9.292 ciscoRscnMIB267 The MIB module for the management of the Fibre
Channel's Registered State Change Notification
(RSCN) functionality, which is spec…
1.3.6.1.4.1.9.9.293 ciscoNsMIB267 The MIB module for the management of the Cisco
Name Server which realizes the FC-GS3
requirements for Name Server (NS).
1.3.6.1.4.1.9.9.294 ciscoZsMIB2271 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.295 ciscoFcPingMIB237 The MIB module for the management of the
Fibre Channel Ping functionality.
1.3.6.1.4.1.9.9.296 ciscoFcTraceRouteMIB231 The MIB module for the management of the
Fibre Channel Trace Route functionality.
1.3.6.1.4.1.9.9.297 ciscoFcsMIB2122 The MIB module for the management of a Fabric
Configuration Server (FCS). An FCS is defined
by the FC-GS3 standard. This MIB ena…
1.3.6.1.4.1.9.9.299 ciscoExtScsiMIB268 The Cisco extension to CISCO-SCSI-MIB
which is a copy of the Internet draft,
the SCSI-MIB, from the IETF.

Glossary of terms used i…
1.3.6.1.4.1.9.9.300 ciscoCallHomeMIB3327 The MIB module for the management of Call Home feature
within the framework of Cisco's Call Home architecture.
Customers deployin…
1.3.6.1.4.1.9.9.301 ciscoSyslogExtMIB244 MIB module for configuring and monitoring System Log
related management parameters as defined by RFC 3164.
1.3.6.1.4.1.9.9.302 ciscoDmMIB288 The MIB module for the domain management functionality
defined by the Fibre Channel standards (FC-SW2). For the
purposes of this …
1.3.6.1.4.1.9.9.305 ciscoSystemExtMIB3113 MIB module for monitoring High Availability, SNMP SET
errors and bandwidths. This mib module also provides the
information on co…
1.3.6.1.4.1.9.9.309 ciscoIPIfMIB340 The MIB module for configuring IP characteristics
of the interfaces of a device.
1.3.6.1.4.1.9.9.311 ciscoEpmNotificationMIB348 Notifications directly from hardware and software and processed
notifications from various management applications can be furthe…
1.3.6.1.4.1.9.9.312 ciscoDataCollectionMIB384 The MIB module allows a management application to
select a set of MIB object instances whose values need
to be collected on a per…
1.3.6.1.4.1.9.9.313 ciscoL2ControlMIB3113 The CISCO-L2-CONTROL-MIB is used to control some layer 2
functions, including MAC limit function and unicast
flooding. This devi…