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.443 ciscoCommonMgmtMIB337 MIB module for integrating different elements of
managing a device. For example, different device access
methods like SNMP, CLI, …
1.3.6.1.4.1.9.9.445 ciscoQinqVlanMIB325 This MIB defines configuration and monitoring capabilities
relating to 802.1QinQ interfaces. QinQ interfaces are capable
of term…
1.3.6.1.4.1.9.9.447 ciscoScsiFlowMIB399 A SCSI Flow is described as a SCSI Initiator
SCSI Target combination. This MIB is used to
configure and monitor SCSI Flows.

Gloss…
1.3.6.1.4.1.9.9.448 ciscoSsmProvMIB226 This MIB is used to provision features
on a Data Path Processor (DPP) of a Storage Service
Module (SSM). A DPP is assigned to a c…
1.3.6.1.4.1.9.9.449 ciscoEigrpMIB3110 Enhanced Interior Gateway Protocol (EIGRP) is a Cisco
proprietary distance vector routing protocol. It is based on
the Diffusin…
1.3.6.1.4.1.9.9.450 ciscoCableAdmCtrlMIB3123 This MIB module defines the managed objects enabling
the management of Cable Modem Termination System
(CMTS) admission control.

CM…
1.3.6.1.4.1.9.9.451 ciscoIpUrpfMIB347 Unicast Reverse Path Forwarding (URPF) is a function
that checks the validity of the source address of IP
packets received on an …
1.3.6.1.4.1.9.9.454 ciscoDot11LbsMIB323 This MIB module supports network management
for Location Based Services on IEEE 802.11 wireless
LAN devices. Location Based Serv…
1.3.6.1.4.1.9.9.455 ciscoImageTc00 ciscoImageTc MODULE-IDENTITY
LAST-UPDATED "200501120000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Custom…
1.3.6.1.4.1.9.9.456 ciscoDot11WidsMIB350 This MIB is intended to be implemented on the
following IOS based network entities for the purpose
of providing network managemen…
1.3.6.1.4.1.9.9.457 ciscoWdsIdsMIB218 This MIB is intended to be implemented on all
IOS based network entities that provide Wireless
Domain Services, for the purpose o…
1.3.6.1.4.1.9.9.458 ciscoApplianceRedundancyMIB347 This mib defines the SNMP objects to report the status of
High Availability (HA) functionality in Cisco network
management applia…
1.3.6.1.4.1.9.9.459 ciscoBitsClockMIB321 This MIB provides information on Building Integrated
Timing Supply(BITS) clocking sources and modes of
operations. It is used to…
1.3.6.1.4.1.9.9.460 ciscoTpcMIB324 The MIB module for Third Party Copy(TPC):
Third Party Copy derives its name from the fact
that there are three entities involved …
1.3.6.1.4.1.9.9.461 ciscoEtherCfmMIB339 This MIB module defines the managed objects
and notifications for Ethernet Connectivity
Fault Management (CFM).

CFM is an end-to-e…
1.3.6.1.4.1.9.9.463 ciscoSanTapMIB330 MIB module to provide information about the SanTap
service configuration.

SanTap is a fibre channel switch based capability that
p…
1.3.6.1.4.1.9.9.466 ciscoEthernetAccessMIB220 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
an edge dev…
1.3.6.1.4.1.9.9.467 ciscoCryptoAcceleratorMIB3107 The MIB module for monitoring the identity, status,
activity and faults of crypto accelerator (CA) modules
used in devices implem…
1.3.6.1.4.1.9.9.468 ciscoContextMappingMIB235 A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple…
1.3.6.1.4.1.9.9.470 ciscoEnhancedSlbMIB3106 The MIB for managing Server Load Balancing
Manager(s), and products supporting Server
Load Balancing(SLB) features.

This MIB exten…
1.3.6.1.4.1.9.9.471 ciscoFlexLinksMIB336 This MIB module is for configuration and status query
of Flex Links feature on the Cisco device.

Flex Links are a pair of Layer 2…
1.3.6.1.4.1.9.9.472 ciscoModuleVirtualizationMIB335 This MIB provides a way to create virtual contexts,
and managing them. A virtual context is logical
partition of a physical devi…
1.3.6.1.4.1.9.9.473 ciscoCcaMIB3200 The Cisco Contact Center Applications (CCCA) Management
Information Base (MIB) module defines management
instrumentation for appl…
1.3.6.1.4.1.9.9.474 ciscoFilterGroupMIB355 The MIB module is for creating and configuring
object groups to support packet filtering and
access control on IP and other proto…
1.3.6.1.4.1.9.9.479 ciscoCableWidebandMIB377 This is the MIB module for the support of Channel Bonding
Protocol for the Cable Modem Termination System (CMTS).

Wideband DOCSIS…
1.3.6.1.4.1.9.9.480 ciscoL4L7moduleResourceLimitMIB4100 The MIB module for managing resource classes
and configuring limits(max/min) to different
resources. The resource referenced in …
1.3.6.1.4.1.9.9.482 ciscoInterfaceTopNExtMIB316 This MIB module is an extension to INTERFACETOPN-MIB.
It provides additional management information for
sorting device interfaces.
1.3.6.1.4.1.9.9.483 ciscoIpRanBackHaulMIB3248 This MIB provides information on the IP-RAN traffic
from cell site to aggregation site in the following
situations. In an GSM en…
1.3.6.1.4.1.9.9.484 ciscoNacNadMIB3157 This MIB module is for the configuration of a Network
Access Device (NAD) on the Cisco Network Admission
Control (NAC) system.

End…
1.3.6.1.4.1.9.9.485 ciscoRttMonTCMIB00 This MIB contains textual conventions used by
CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and
CISCO-RTTMON-ICMP-MIB, but they are not …
1.3.6.1.4.1.9.9.486 ciscoRttMonIcmpMIB37 An extension to the CISCO-RTTMON-MIB for ICMP
operations. The ICMP Jitter operation provides capability
to measure metrics such a…
1.3.6.1.4.1.9.9.487 ciscoRttMonRtpMIB38 An extension to the CISCO-RTTMON-MIB for Cisco IP SLA
RTP operation, Real-Time Transport Protocol(RFC 1889). This
operation provi…
1.3.6.1.4.1.9.9.488 ciscoFirewallTc00 This MIB module defines textual conventions that
are commonly used in modeling management information
pertaining to configuration…
1.3.6.1.4.1.9.9.490 ciscoNetintMIB311 This MIB module is for Network Interrupt information
on Cisco device.
1.3.6.1.4.1.9.9.491 ciscoUnifiedFirewallMIB3360 Overview of Cisco Firewall MIB
==============================
This MIB Module models status and performance
statistics pertaining …
1.3.6.1.4.1.9.9.492 ciscoCefMIB3192 Cisco Express Forwarding (CEF) describes a high speed
switching mechanism that a router uses to forward packets
from the inbound …
1.3.6.1.4.1.9.9.493 ciscoCefTextualConventions00 ciscoCeftextualConventions
1.3.6.1.4.1.9.9.494 ciscoEntityRedunTcMIB00 This module defines the textual conventions used within
Cisco Entity Redundancy MIBs.
1.3.6.1.4.1.9.9.495 ciscoPsdClientMIB344 This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).

This MIB instrumentation is for conf…
1.3.6.1.4.1.9.9.497 cGgsnSAMIB3247 This MIB module manages the service-aware feature of
Gateway GPRS Support Node (GGSN).

This MIB is an enhancement of the CISCO-GG…
1.3.6.1.4.1.9.9.498 ciscoEntityRedunMIB393 This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of c…
1.3.6.1.4.1.9.9.500 ciscoStackWiseMIB3111 This MIB module contain a collection of managed objects
that apply to network devices supporting the Cisco
StackWise(TM) technolo…
1.3.6.1.4.1.9.9.504 ciscoSwitchMulticastMIB3108 This MIB module defines management objects for the
Multicast Switching features on Cisco Layer 2/3
devices.

Definition of some of …
1.3.6.1.4.1.9.9.505 cpkiMIB344 A networking device may provide several security services
and protocols like SSL, SSH, IPSec/IKE etc. which need
identities …
1.3.6.1.4.1.9.9.507 ciscoPolicyGroupMIB335 The MIB module is for configuration of policy and
policy group. A policy group can be described as a set
of entities identified b…
1.3.6.1.4.1.9.9.508 ciscoSlbHealthMonMIB362 An extension to the CISCO-SLB-EXT-MIB for SLB
health monitoring probes.

SLB: Server Load Balancing. Server load balancing
provides…
1.3.6.1.4.1.9.9.509 ciscoWdsInfoMIB3141 This MIB is intended to be implemented on all Cisco
network entities that provide Wireless Domain Services
(WDS). The WDS provide…
1.3.6.1.4.1.9.9.510 ciscoErmMIB, ciscoVoiceLmrMIB3176 This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes …
1.3.6.1.4.1.9.9.511 ciscoCbpTargetTCMIB00 This MIB module defines Textual Conventions for
representing targets which have class based policy
mappings. A target can be any …
1.3.6.1.4.1.9.9.512 ciscoLwappWlanMIB3378 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weigh…