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

Alternative description: MIBdepot

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)

OID	Name	Direct children	Descendants
1.3.6.1.4.1.9.9.577.0	ciscoLwappAclMIBNotifs	0	0
1.3.6.1.4.1.9.9.577.1	ciscoLwappAclMIBObjects	3	38
1.3.6.1.4.1.9.9.577.2	ciscoLwappAclMIBConform	2	6

Siblings (692)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.9.9.864	ciscoCapwapScheduledWlanMIB	3	23
1.3.6.1.4.1.9.9.865	ciscoDlrMIB	3	20
1.3.6.1.4.1.9.9.866	ciscoPrpMIB	3	19
1.3.6.1.4.1.9.9.867	ciscoDnacMIB	3	28
1.3.6.1.4.1.9.9.868	ciscoLwappGuestLanMIB	3	60
1.3.6.1.4.1.9.9.869	ciscoAlarmMIB	2	17
1.3.6.1.4.1.9.9.870	ciscoTempMIB	2	12
1.3.6.1.4.1.9.9.942	ciscoVqeSMIB	3	57	This MIB module defines a set of objects for monitoring the Visual Quality Experience Server (VQE-S) operational status. VQE-S re…
1.3.6.1.4.1.9.9.957	ciscoCdmaPdsnCrpMIB	2	29	This MIB is to support the Closed RP feature of CDMA PDSN that supports wireless data communication through 3G CDMA radio access …
1.3.6.1.4.1.9.9.969	ciscoVqeToolsMIB	3	16	This MIB module defines a set of objects for monitoring the VQE Client Channel Configuration Delivery Server (VCDS) operational s…
1.3.6.1.4.1.9.9.987	ciscoLwappTagsMIB	3	88
1.3.6.1.4.1.9.9.995	ciscoSipCallsMIB	2	49	The Cisco Session Initiation Protocol (SIP) Calls MIB module is designed to provide protocol-specific information on SIP calls wh…
1.3.6.1.4.1.9.9.997	cCdmaAhdlcMIB	3	42	This MIB module provides details concerning AHDLC engine state, performance, configuration and notification. An AHDLC channel hand…
1.3.6.1.4.1.9.9.1051	ciscoVisionMIB	4	46
1.3.6.1.4.1.9.9.1053	ciscoFibreChanMIB	3	116
1.3.6.1.4.1.9.9.1056	ciscoUrwb	8	90
1.3.6.1.4.1.9.9.1057	ciscoOpticalOlcMIB	1	63
1.3.6.1.4.1.9.9.1059	ciscoCgwCellMIB	8	224
1.3.6.1.4.1.9.9.1060	ciscoDlepMIB	2	134
1.3.6.1.4.1.9.9.1061	ciscoIgnitionMIB	3	27
1.3.6.1.4.1.9.9.1063	cgwTraps	2	46
1.3.6.1.4.1.9.9.1300	ciscoItpDsmrMIB	3	168	The MIB for providing information about Distributed Short Message Routing for Short Message Service Center. This MIB will provid…
1.3.6.1.4.1.9.9.1301	ciscoItpDsmrSmppMIB	3	50	The MIB for providing information about Distributed Short Message Routing delivery using Short Message Peer-to-Peer protocol. Acr…
1.3.6.1.4.1.9.9.1302	ciscoItpDsmrUcpMIB	3	44	The MIB for providing information about Distributed Short Message Routing delivery using Universal Computer Protocol. Acronyms an…
1.3.6.1.4.1.9.9.3228	ciscoDot11CsMgrMIB	2	17	This MIB is intended to be implemented on IEEE 802.11 Wireless LAN management devices for Access Points and Wireless Bridges part…
1.3.6.1.4.1.9.9.3333	ciscoDot11AntennaMIB	2	11	This MIB is intended to be implemented on 802.11 Access Points and Wireless Bridges to provide information about the antennas con…
1.3.6.1.4.1.9.9.8888	ciscoAnnouncementMIB	3	34	This MIB defines the objects for announcement system supported on media gateway. With announcement system setup, media gateway wi…
1.3.6.1.4.1.9.9.9399	ciscoIfLoopbackMIB	2	13	The MIB module to configure the loopback on certain interfaces in ifTable with ifType ds1/e1, ds3/e3, ds0 etc.
1.3.6.1.4.1.9.9.9968	ciscoIfCallServiceMIB	3	16	The MIB is used to manage call service state for interfaces on media gateway.
1.3.6.1.4.1.9.9.9992	ciscoGprsIsgsnMIB	2	19	The MIB Module for managing the General Packet Radio Service(GPRS) iSGSN protocol on Servicing GPRS Support Node (SGSN). In the Al…
1.3.6.1.4.1.9.9.9993	ciscoGprsL2rlyMIB	3	45	The MIB Module for managing the General Packet Radio Service(GPRS) L2RLY related information on Servicing GPRS Support Node(SGSN)…
1.3.6.1.4.1.9.9.9997	ciscoGtpDirectorMIB	3	35
1.3.6.1.4.1.9.9.9999	ciscoAal5ExtMIB, ciscoAtmConnInfoMIB, ciscoDs0CrossConnectMIB, ciscoFiberChannelTunnelMIB, ciscoCpriMIB	3	163	The MIB module for providing the parameters configured on an ATM interface. Terminologies used: SVC : Switched Virtual Channel SPV…
1.3.6.1.4.1.9.9.99990	ciscoImageCheckMIB	2	22	Initial version of Image Check MIB.
1.3.6.1.4.1.9.9.99996	ciscoWanATMPrefRouteMIB	3	18	This MIB facilitates the maintenance of preferred routes configuration.
1.3.6.1.4.1.9.9.99997	ciscoFcPmMIB	3	78	This MIB module defines 24 hour error statistics for Fibre Channel (FC) and FICON interfaces collected every 15 minutes. Based o…
1.3.6.1.4.1.9.9.99998	ciscoWanAtmPartyMIB	3	23	A management station can use this MIB to provision, manage or delete one or more 'parties' on an ATM point-to-multipoint Soft PVC…
1.3.6.1.4.1.9.9.99999	ciscoMpoaExtMIB, ciscoWanAtmCugMIB, ciscoAuthorizationStatsMibModule	4	52	This MIB module is intended for the management of 'Closed User Group(CUG)' in Cisco ATM switches. This MIB definition is based up…
1.3.6.1.4.1.9.9.193999	ciscoLwappDhcpMIB	1	23	`ciscoLwappDhcpMIB MODULE-IDENTITY LAST-UPDATED "200604051150Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO " Cisco Systems, …`
1.3.6.1.4.1.9.9.199995	ciscoLwappDot11ClientRmMIB	3	54	`ciscoLwappDot11ClientRmMIB MODULE-IDENTITY LAST-UPDATED "200604110000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO " Cisco …`
1.3.6.1.4.1.9.9.300576	ciscoVoiceCard	3	13	The MIB module to configure voice-card specific parameters such as codec complexity in voice- enabled cisco routers.
1.3.6.1.4.1.9.9.999999	ciscoFipsStatsMIB	3	11	The Federal Information Processing Standards (FIPS) power-up self-test status MIB module