QTECH-CAPWAP-DHCP-MIB
This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Access Point Protocol
tunnel from Qtech Light-weight CAPWAP Access Points.
This MIB is used to show and configure Dynamic Host
Configuration Protocol (DHCP) related statistics.
The relationship between CC and the CAPWAP APs
can be depicted as follows:
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
The CAPWAP tunnel exists between the controller and
the APs. The MNs communicate with the APs through
the protocol defined by the 802.11 standard.
CAPWAP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the CAPWAP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside CAPWAP frames and forward
the CAPWAP frames to the controller.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.
CAPWAP APs encapsulate all the 802.11 frames in
CAPWAP frames and sends them to the controller to which
it is logically connected.
Central Controller ( CC )
The central entity that terminates the CAPWAP protocol
tunnel from the CAPWAP APs. Throughout this MIB,
this entity also referred to as 'controller'.
Light Weight Access Point Protocol ( CAPWAP )
This is a generic protocol that defines the
communication between the Access Points and the
Central Controller.
Mobile Node ( MN )
A roaming 802.11 wireless device in a wireless
network associated with an access point. Mobile Node,
Mobile Station(Ms) and client are used interchangeably.
REFERENCE
[1] Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications.
[2] Draft-obara-capwap-capwap-00.txt, IETF Light
Weight Access Point Protocol
- Source file
QTECH-CAPWAP-DHCP-MIB- Last revised
- Identity
qtechCapwapDhcpMIB- Base OID
1.3.6.1.4.1.27514.1.1.10.2.58
Imported Objects
| QTECH-INTERFACE-MIB | qtechIfIndex |
| QTECH-SMI | qtechMgmt |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | DisplayString MacAddress RowStatus TruthValue |
Net-SNMP examples using the qtech 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 'QTECH-CAPWAP-DHCP-MIB' -M '/opt/observium/mibs/qtech:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'QTECH-CAPWAP-DHCP-MIB::qtechCapwapDhcpMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'QTECH-CAPWAP-DHCP-MIB' -M '/opt/observium/mibs/qtech:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'QTECH-CAPWAP-DHCP-MIB::qtechCapwapDhcpMIB'
Objects (63)
Showing 63 of 63 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.27514.1.1.10.2.58 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.0 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.1 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.1.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.1.2 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.1.3 |
||
|
Enumeration
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.1.4 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2 |
||
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.1 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.10 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.11 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.2 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.3 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.4 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.5 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.6 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.7 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.8 |
|
|
packetsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.2.9 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1 |
||
|
Unsigned32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.1 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.10 |
||
|
OctetString
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.11 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.12 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.13 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.14 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.15 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.16 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.17 |
||
|
Enumeration
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.18 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.19 |
||
|
OctetString
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.2 |
|
|
Integer32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.20 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.21 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.22 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.23 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.24 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.25 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.26 |
||
|
Integer32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.3 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.4 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.5 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.6 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.7 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.8 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.3.1.1.9 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.1 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.1.1 |
||
|
Integer32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.1.1.1 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.1.1.2 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.1.1.3 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.2 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.2.1 |
||
|
Integer32
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.2.1.1 |
|
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.2.1.2 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.1.4.2.1.3 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.2 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.2.1 |
||
.1.3.6.1.4.1.27514.1.1.10.2.58.2.2 |
Dependencies (21) 5 direct · 16 transitive 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
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- BRIDGE-MIBrfc
- P-BRIDGE-MIBrfc
- RMON-MIBrfc
- RFC-1212rfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- RFC1271-MIBrfc
- TOKEN-RING-RMON-MIBrfc
- RMON2-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- Q-BRIDGE-MIBrfc
- QTECH-SMIqtech
- QTECH-TCqtech
- QTECH-INTERFACE-MIBqtech
- QTECH-CAPWAP-DHCP-MIBqtechselected
Conformance Groups (4)
Compliance Statements (1)
OID
.1.3.6.1.4.1.27514.1.1.10.2.58.2.1.1The compliance statement for entities which implement
the Qtech Capwap Dhcp MIB
the Qtech Capwap Dhcp MIB
Required groups
| mandatory | qtechCapwapDhcpMIBGroup | |
| mandatory | qtechCapwapDhcpServerConfigGroup | |
| mandatory | qtechCapwapDhcpRelayGlobalConfigGroup | |
| mandatory | qtechCapwapDhcpRelayIntfConfigGroup |
Notifications / Traps (3)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.27514.1.1.10.2.58.0.1 |
This trap is sent when the dhcp pool is full
|
|
.1.3.6.1.4.1.27514.1.1.10.2.58.0.2 |
This trap is sent when the dhcp pool recover from full
|
|
.1.3.6.1.4.1.27514.1.1.10.2.58.0.3 |
This trap is sent when the dhcp client failed to request address
|