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.383 ciscoCidsMIB3183 Cisco Intrusion Detection System MIB. Provides
trap definitions for the evAlert and evError
elements of the IDIOM (Intrusion Det…
1.3.6.1.4.1.9.9.384 ciscoDot11AntennaMIB211 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.385 ciscoUnityMIB3101 The MIB Module for the management of Cisco Unity server.
Cisco Unity is a Unified Communications solution that provides
advanced,…
1.3.6.1.4.1.9.9.386 ciscoModuleAutoShutdownMIB336 The CISCO-MODULE-AUTO-SHUTDOWN-MIB is used to configure
the module automatic shutdown feature. Modules will be
reset by the syste…
1.3.6.1.4.1.9.9.387 ciscoNetflowMIB3206 The Netflow MIB provides a simple and easy method
to get NetFlow cache information, current NetFlow
configuration and statistics.…
1.3.6.1.4.1.9.9.388 ciscoVirtualSwitchMIB3128 This MIB module defines the managed objects that support the
virtual switch architecture.

The virtual switch concept combines sev…
1.3.6.1.4.1.9.9.389 ciscoVoiceCasModuleMIB322 This MIB is used to support Programmable
CAS signaling Bit configuration on modules
that support voice traffic.

This MIB will enab…
1.3.6.1.4.1.9.9.390 ciscoCableDiagMIB333 This MIB module defines objects for managing cable
diagnostic test capabilites supported by the Cisco devices.

Cable diagnostic t…
1.3.6.1.4.1.9.9.391 ciscoFcspMIB346 MIB module for managing Fibre Channel Security for the
fibre channel devices.

This MIB is used to configure and monitor the
Fibre-…
1.3.6.1.4.1.9.9.392 ciscoRemoteAccessMonitorMIB3200 Acronyms and Definitions
The following acronyms and terms are used in this
document:

IPSec: Secure IP Protocol

VPN: Virtual Priv…
1.3.6.1.4.1.9.9.393 ciscoVoiceConnectivityMIB344 This MIB module provides connectivity related
information for devices (e.g., 'connectivity between
voice gateway, phones, gatekee…
1.3.6.1.4.1.9.9.394 ciscoIpTapMIB328 This module manages Cisco's intercept feature for IP.

This MIB is used along with CISCO-TAP2-MIB to
intercept IP traffic. CISCO-T…
1.3.6.1.4.1.9.9.395 cisco802TapMIB320 This module manages Cisco's intercept feature for
802 (layer 2) streams.

This MIB is used along with CISCO-TAP2-MIB to
intercept 8…
1.3.6.1.4.1.9.9.396 ciscoMlrMIB3190 The MIB for providing information about Multi-layer
Routing(MLR). This MIB will provide information used to
control and measure S…
1.3.6.1.4.1.9.9.397 ciscoH225MIB1176 Cisco H225 MIB module. This module consists of H225
call signaling and H225 RAS (Registration, Admission
and Status). These are p…
1.3.6.1.4.1.9.9.398 ciscoMauExtMIB323 A MIB module for extending the MAU-MIB (RFC 3636)
to add objects which provide additional management
information about MAU or Jac…
1.3.6.1.4.1.9.9.399 ciscoTap2MIB369 This module manages Cisco's intercept feature.
This MIB replaces CISCO-TAP-MIB. This MIB defines
a generic stream table that cont…
1.3.6.1.4.1.9.9.400 ciscoUserConnectionTapMIB213 This module manages Cisco's intercept feature for
user connections.

This MIB is used along with CISCO-TAP2-MIB to
intercept user t…
1.3.6.1.4.1.9.9.401 ciscoBridgeExtMIB334 A MIB module for extending BRIDGE-MIB specified in RFC 1493.
1.3.6.1.4.1.9.9.402 ciscoPowerEthernetExtMIB383 A MIB module for extending the POWER-ETHERNET-MIB
(RFC3621) to add objects which provide additional
management information about …
1.3.6.1.4.1.9.9.405 ciscoDnsServerMIB3408 The MIB module for entities implementing the server side
of the Domain Name System (DNS) protocol.
P. Mockapetris, 'Domain names …
1.3.6.1.4.1.9.9.407 ciscoAtmTrunkStatMIB3101 The MIB module contains ATM Trunk statistics.

TERMINOLOGY

PVC: Permanent Virtual Circuit
OAM: Operation and Management
CRC: Cyclic…
1.3.6.1.4.1.9.9.408 ciscoSnmpNotificationExtMIB313 This MIB extends the functionality provided
by SNMP-NOTIFICATION-MIB.
This MIB provides for the aging of the
notification filters …
1.3.6.1.4.1.9.9.409 ciscoSnmpVacmExtMIB211 The management information definitions to extend
the View-based Access Control Model (RFC3415) for
SNMP.

This MIB extends the 'SN…
1.3.6.1.4.1.9.9.411 ciscoVlanTranslationMIB327 The MIB module for the management of VLAN translations.

VLAN translation refers to the ability of the device
to translate between…
1.3.6.1.4.1.9.9.412 ciscoSnmpTargetExtMIB230 This MIB is an extension of the SNMP-TARGET-MIB
specified in RFC3413.

This MIB module contains Cisco-defined extension
to the sn…
1.3.6.1.4.1.9.9.413 ciscoDot11SsidSecMIB271 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
devices association and authentication.

ACR…
1.3.6.1.4.1.9.9.414 ciscoPoePdMIB317 This MIB is intended for devices powered by
external power sources, in particular Power
Over Ethernet (PoE or formerly called inl…
1.3.6.1.4.1.9.9.415 ciscoWlanManMIB313 This MIB module provides network management
and configuration support for IEEE 802.11
Wireless LAN devices.

ACRONYMS

HTTP
Hypertext …
1.3.6.1.4.1.9.9.416 ciscoDot11QosMIB349 This MIB module provides network management
support for QoS on wireless LAN devices. The
objects defined in this MIB provide equ…
1.3.6.1.4.1.9.9.420 ciscoUnityExpressMIB3179 The MIB Module for the management of the Cisco Unity
Express (CUE) service. CUE is a voicemail service that
runs in a Cisco rout…
1.3.6.1.4.1.9.9.421 ciscoDpvmMIB355 The MIB module for the management of the
Dynamic Port Vsan Membership (DPVM) module.
DPVM provides the ability to assign (virtual
…
1.3.6.1.4.1.9.9.422 ciscoIPsecTc00 This MIB module defines the textual conventions
used in the IPsec suite of MIBs. This includes
Internet DOI numbers defined in RF…
1.3.6.1.4.1.9.9.423 ciscoIkeConfigMIB393 This is a MIB Module for configuring and viewing IKE
parameters and policies.

Acronyms
The following acronyms are used in this do…
1.3.6.1.4.1.9.9.424 ciscoCableMeteringMIB353 This is the MIB module for Usage Based Metering for the
DOCSIS-compliant Cable Modem Termination Systems (CMTS).

Usage Based Mete…
1.3.6.1.4.1.9.9.426 ciscoLinkErrorMonitorMIB334 The MIB module for managing Link Error Monitoring
Feature on devices.

Link Error Monitoring Feature provides a mechanism
to monito…
1.3.6.1.4.1.9.9.427 ciscoZsExtMIB333 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.428 ciscoIkeFlowExtMIB318 This MIB module is an extension to
CISCO-IKE-FLOW-MIB and contains Cisco Specific
extensions for monitoring IKE.

It is for monito…
1.3.6.1.4.1.9.9.429 ciscoIkeFlowMIB380 This is a MIB module for monitoring the structures
and status of IPsec control flows based on Internet
Key Exchange protocol. The…
1.3.6.1.4.1.9.9.430 ciscoFcDeviceAliasMIB314 The MIB module for the management of Device
Aliases in a Fibre Channel Fabric. A Fibre
Channel fabric consists of devices such as
…
1.3.6.1.4.1.9.9.431 ciscoIPsecProvisioningMIB398 IPSec is the next-generation network layer crypto
framework described in RFC2401-2411.
This MIB defines the IPsec configurations.
…
1.3.6.1.4.1.9.9.432 ciscoEnhancedIpsecFlowMIB3330 This is a MIB Module for monitoring the structures
and status of IPSec-based networks. The MIB has been
designed to be adopted as…
1.3.6.1.4.1.9.9.433 ciscoCFSMIB3102 This MIB applies to one or more of a set of devices
which have connectivity through some kind of 'fabric'.
Many features which ru…
1.3.6.1.4.1.9.9.434 ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB358 MIB to provide the information about the disjoint
IP networks connected to the various gigabit ethernet
interfaces in the 'Fabric…
1.3.6.1.4.1.9.9.435 ciscoFcMulticastMIB314 MIB module for monitoring and configuring
Fibre Channel Multicast feature.
1.3.6.1.4.1.9.9.436 ciscoDNSClientMIB328 The MIB module for entities implementing the client
side of the Domain Name System (DNS) protocol.
1.3.6.1.4.1.9.9.437 ciscoPortTrackMIB218 A MIB to configure the Port-Track feature.

When a link goes down, all the services which depend
on the link are notified of the o…
1.3.6.1.4.1.9.9.438 ciscoIPsecSignalingMIB3140 This MIB Module models status, performance and failures
of a protocol with the generic characteristics of signalling
protocols us…
1.3.6.1.4.1.9.9.439 ciscoCcmeMIB3338 This MIB allows management of Cisco CallManager Express
(CCME) feature in Cisco IOS. CCME is optional software
feature that enabl…
1.3.6.1.4.1.9.9.441 ciscoSrstMIB3149 This MIB allows management of Cisco Survivable Remote
Site Telephony (SRST) feature in Cisco IOS. SRST is
an optional software fe…