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.314 ciscoCasIfExtMIB3225 The MIB module is an extension of CISCO-CAS-IF-MIB.
It defines the attributes of a voice interface.
1.3.6.1.4.1.9.9.315 ciscoPortSecurityMIB389 The MIB module for managing Cisco Port Security.
1.3.6.1.4.1.9.9.317 ciscoIscsiGwMIB3145 MIB module for monitoring and configuring iSCSI
gateway functions. An iSCSI gateway represents FC
(Fibre Channel) targets/initiat…
1.3.6.1.4.1.9.9.318 ciscoXgcpMIB3120 This MIB is an enhancement for existing XGCP-MIB.

xGCP is a set of protocols, for example SGCP (Simple
Gateway Control Protocol) …
1.3.6.1.4.1.9.9.319 ciscoPropAtmIfMIB357 This MIB is designed for Propietary ATM (propAtm)
interfaces.
The propAtm interfaces are identified in the ifTable
entries with if…
1.3.6.1.4.1.9.9.321 ciscoMgcMIB343 This MIB is used to support MGC(call agent) and
MGC Group configuration.
The MGC or MGC group configuration is performed
under a s…
1.3.6.1.4.1.9.9.322 ccacSysMIB260 This MIB module provides provisioning and
monitoring Call Admission Control (CAC).
1.3.6.1.4.1.9.9.323 ciscoVoiceAalxProfileMIB387 This MIB defines the objects specific to voice
over ATM or voice over IP. Those objects are
related to the following areas:
1. COD…
1.3.6.1.4.1.9.9.324 ciscoMediaGatewayMIB3107 The MIB module for managing Trunk Media Gateway.

A Media Gateway is a network element that provides conversion
between the audio …
1.3.6.1.4.1.9.9.325 ciscoXgcpExtMIB265 This MIB module is an extension to CISCO-XGCP-MIB.

It defines the parameters related to the following
aspects in xGCP protocols:
*…
1.3.6.1.4.1.9.9.326 ciscoIpLocalPoolMIB357 This MIB defines the configuration and monitoring capabilities
relating to local IP pools.

Local IP pools have the following char…
1.3.6.1.4.1.9.9.329 ciscoFcipMgmtExtMIB375 A MIB module for extending the CISCO-FCIP-MGMT-MIB
to add objects which provide additional information
about FCIP interfaces not …
1.3.6.1.4.1.9.9.330 ciscoSysInfoLogMIB344 This MIB provides the configuration of System Information
Logging feature, which allows a certain number of commands
to be execut…
1.3.6.1.4.1.9.9.331 ciscoCsgMIB386 This MIB supports the Cisco Content Services Gateway
(CSG) product. It includes five traps and four tables
that enable querying C…
1.3.6.1.4.1.9.9.332 ciscoGsp2MIB391 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.333 ciscoGactMIB340 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.334 ciscoGrtMIB3150 This MIB is for managing information required to
route messages transported over Signalling System
No. 7 (SS7) Network via Cisco …
1.3.6.1.4.1.9.9.335 ciscoGsccpMIB3293 The MIB for signalling Connection Control Part(SCCP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP…
1.3.6.1.4.1.9.9.336 ciscoGspMIB3273 The MIB for managing Signalling Points and its
associated messages transported over Signalling
System No. 7 (SS7) Network via Ci…
1.3.6.1.4.1.9.9.339 ciscoSecureShellMIB240 MIB module for displaying and configuring
accounting and Secure Shell (SSH) related
features in a device.

SSH is a program to log …
1.3.6.1.4.1.9.9.340 ciscoLreCpeMIB321 The MIB module for the Cisco Long Reach Ethernet
Customer Premise Equipment device information.

*** ABBREVIATIONS, ACRONYMS, AND …
1.3.6.1.4.1.9.9.341 ciscoCableQosMonitorMIB357 This is the MIB module for subscriber QoS monitoring
for DOCSIS-compliant Cable Modem Termination Systems
(CMTS).

Several subscrib…
1.3.6.1.4.1.9.9.343 ciscoAuthorizationStatsMibModule225 The Cisco User Authorization Statistics MIB models
counters and objects that are of management
interest.
1.3.6.1.4.1.9.9.344 ciscoEntityDisplayMIB221 This MIB module provides information about the
status of display devices such as Light Emitting
Diodes (LEDs) and alphanumeric di…
1.3.6.1.4.1.9.9.350 ciscoEntityDiagMIB3139 This MIB module defines the managed objects that describe the
online diagnostics capabilities supported by the
physical entities …
1.3.6.1.4.1.9.9.351 ciscoAtmTrunkMIB3102 The MIB for voice and Nx64 over ATM Trunking applications.

The following lists the abbreviations used in this MIB:
AAL ATM …
1.3.6.1.4.1.9.9.356 ciscoVoiceToneCadenceMIB330 The MIB defines the attributes of the programmable
tones specified in ITU-T E.180 Supplement 2.

Each country has its own regulati…
1.3.6.1.4.1.9.9.358 ciscoBbsmMIB320 This mib is designed to send BBSM specific
notifications. There are variables that contain detail data
that are bind to a notifi…
1.3.6.1.4.1.9.9.359 ciscoLicenseMIB352 This MIB module provides objects to view the features
and services that are licensed to run on a system (usually
a network entity…
1.3.6.1.4.1.9.9.360 ciscoImageUpgradeMIB3101 This mib provides, objects to upgrade images on modules in the
system, objects showing the status of the upgrade operation,
and o…
1.3.6.1.4.1.9.9.361 ciscoCommonRolesMIB340 MIB module for managing the common roles between
access methods like Command Line Interface (CLI), SNMP
and XML interfaces.
Every …
1.3.6.1.4.1.9.9.362 ciscoPortStormControlMIB343 The MIB module for managing Cisco Port Storm Control.
1.3.6.1.4.1.9.9.363 ciscoFcSpanMIB249 MIB module for displaying and configuring
Switched Port Analyzer(SPAN) related features
in a Fibre Channel device.

SPAN is a featu…
1.3.6.1.4.1.9.9.364 ciscoPsmMIB3213 The MIB module for the management of the
Port Security Manager (PSM). The PSM
consists of 2 aspects: Port binding and
Fabric bindi…
1.3.6.1.4.1.9.9.365 ciscoFCCMIB342 The MIB module for the management of Fibre Channel
Congestion Control(FCC). FCC is a Cisco proprietary
flow control mechanism tha…
1.3.6.1.4.1.9.9.367 ciscoAAAServerExtMIB277 This MIB is an extension to the CISCO-AAA-SERVER-MIB.
This MIB module enhances the 'casConfigTable' to
include other types of Ser…
1.3.6.1.4.1.9.9.368 36800 Cisco Content Services (CSS) switch product, also known as Arrowpoint, for version 7.40 and later
1.3.6.1.4.1.9.9.369 ciscoLicenseMgrMIB3102 The MIB module for a method of managing license files on
the system.
Licensing mechanism provides more flexibility in supporting
v…
1.3.6.1.4.1.9.9.370 ciscoSslProxyMIB3372 This MIB module is for managing a Secure Socket Layer
(SSL) Proxy device which terminates and accelarates
SSL and Transport Layer…
1.3.6.1.4.1.9.9.371 ciscoIvrMIB3192 The MIB module for the management of Inter-VSAN
routing within the framework of Cisco's
Inter-VSAN Routing (IVR) Architecture. IV…
1.3.6.1.4.1.9.9.372 ciscoIsnsClientMIB316 MIB module for monitoring and configuring Internet
Storage Name Service (iSNS) client.
1.3.6.1.4.1.9.9.373 ciscoFdmiMIB347 Fabric Device Management Interface (FDMI) MIB. This MIB
module defines objects for managing the devices such as
HBA (Host Bus Ada…
1.3.6.1.4.1.9.9.374 ciscoDynamicArpInspectionMIB382 The MIB module is for configuration of Dynamic ARP Inspection
feature. Dynamic ARP Inspection is a security mechanism which
valid…
1.3.6.1.4.1.9.9.375 ciscoFiconMIB3176 This is the FICON (FIber CONnection) MIB module.

FICON is an IBM standard of transport mechanism
for communication between the ma…
1.3.6.1.4.1.9.9.376 ciscoSVIAutostateMIB319 The MIB module is for configuration of the switch virtual
interface (SVI) autostate feature. Autostate feature
is a mechanism to …
1.3.6.1.4.1.9.9.377 ciscoFeatureCtrlMIB353 There are two types of features in the system:

- Regular features
- Optional features

The Regular features may or may not need t…
1.3.6.1.4.1.9.9.378 ciscoSvcInterfaceMIB3115 MIB module for displaying and configuring
SVC (SAN Volume Controller) related features
in the Storage Area Network (SAN) switches…
1.3.6.1.4.1.9.9.379 ciscoItpmMIB347 The MIB for providing information related to
monitoring SS7 links.

This information can be used to manage the state
of software u…
1.3.6.1.4.1.9.9.380 ciscoDhcpSnoopingMIB3127 The MIB module is for configuration of DHCP Snooping
feature. DHCP Snooping is a security mechanism which
uses information gleane…
1.3.6.1.4.1.9.9.381 ciscoDiffServExtMIB249 This MIB is a Cisco extension to the
DIFFSERV-MIB, RFC 3289. This MIB defines
a Fibre Channel (FC) Multi Field filter to
be used i…