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.
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."
]
]
]
]
]
}
{'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.
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.
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 }
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)