CISCO-LWAPP-ACL-MIB

        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.
    
Source file
CISCO-LWAPP-ACL-MIB
Last revised
Identity
ciscoLwappAclMIB
Base OID
1.3.6.1.4.1.9.9.577
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-TC CiscoURLString
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-LWAPP-ACL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-ACL-MIB::ciscoLwappAclMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-ACL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-ACL-MIB::ciscoLwappAclMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (44)
.1.3.6.1.4.1.9.9.577
.1.3.6.1.4.1.9.9.577.0
.1.3.6.1.4.1.9.9.577.1
.1.3.6.1.4.1.9.9.577.1.1
.1.3.6.1.4.1.9.9.577.1.1.1
.1.3.6.1.4.1.9.9.577.1.1.1.1
.1.3.6.1.4.1.9.9.577.1.1.1.1.1
OctetString
.1.3.6.1.4.1.9.9.577.1.1.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.577.1.1.1.1.3
.1.3.6.1.4.1.9.9.577.1.2
.1.3.6.1.4.1.9.9.577.1.2.1
.1.3.6.1.4.1.9.9.577.1.2.1.1
OctetString
.1.3.6.1.4.1.9.9.577.1.2.1.1.1
.1.3.6.1.4.1.9.9.577.1.2.1.1.2
.1.3.6.1.4.1.9.9.577.1.2.2
.1.3.6.1.4.1.9.9.577.1.2.2.1
Unsigned32
.1.3.6.1.4.1.9.9.577.1.2.2.1.2
.1.3.6.1.4.1.9.9.577.1.2.2.1.3
.1.3.6.1.4.1.9.9.577.1.2.3
.1.3.6.1.4.1.9.9.577.1.2.3.1
Unsigned32
.1.3.6.1.4.1.9.9.577.1.2.3.1.1
.1.3.6.1.4.1.9.9.577.1.2.3.1.2
.1.3.6.1.4.1.9.9.577.1.2.3.1.3
.1.3.6.1.4.1.9.9.577.1.2.4
.1.3.6.1.4.1.9.9.577.1.2.4.1
OctetString
.1.3.6.1.4.1.9.9.577.1.2.4.1.1
Enumeration
.1.3.6.1.4.1.9.9.577.1.2.4.1.2
.1.3.6.1.4.1.9.9.577.1.2.4.1.3
.1.3.6.1.4.1.9.9.577.1.2.4.1.4
Enumeration
.1.3.6.1.4.1.9.9.577.1.2.4.1.5
.1.3.6.1.4.1.9.9.577.1.2.5
.1.3.6.1.4.1.9.9.577.1.2.5.1
.1.3.6.1.4.1.9.9.577.1.2.5.1.1
OctetString
.1.3.6.1.4.1.9.9.577.1.2.5.1.2
Enumeration
.1.3.6.1.4.1.9.9.577.1.2.5.1.3
.1.3.6.1.4.1.9.9.577.1.2.5.1.4
.1.3.6.1.4.1.9.9.577.1.2.5.1.5
.1.3.6.1.4.1.9.9.577.1.3
.1.3.6.1.4.1.9.9.577.1.3.1
.1.3.6.1.4.1.9.9.577.1.3.2
.1.3.6.1.4.1.9.9.577.1.3.3
.1.3.6.1.4.1.9.9.577.2
.1.3.6.1.4.1.9.9.577.2.1
.1.3.6.1.4.1.9.9.577.2.2
Dependencies (7) 7 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. CISCO-TCcisco
  5. INET-ADDRESS-MIBrfc
  6. SNMPv2-CONFrfc
  7. SNMP-FRAMEWORK-MIBrfc
  8. CISCO-LWAPP-ACL-MIBciscoselected
Conformance Groups (2)
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.577.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappAclMIB module.
Required groups

OID .1.3.6.1.4.1.9.9.577.2.1.2
The compliance statement for the SNMP entities that
implement the ciscoLwappAclMIB module.
Required groups