draft-ietf-capwap-base-mib-05.txt   draft-ietf-capwap-base-mib-06.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft Hangzhou H3C Tech. Co., Ltd Internet-Draft Hangzhou H3C Tech. Co., Ltd.
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: November 30, 2009 SNMPinfo Expires: February 14, 2010 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
May 29, 2009 August 13, 2009
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-05 draft-ietf-capwap-base-mib-06
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 30, 2009. This Internet-Draft will expire on February 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4 5.1. Requirements and Constraints . . . . . . . . . . . . . . . 4
5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5 5.2. Wireless Binding MIB Modules . . . . . . . . . . . . . . . 5
5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5 5.3. Design Objectives . . . . . . . . . . . . . . . . . . . . 5
5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6 5.4. Design Idea . . . . . . . . . . . . . . . . . . . . . . . 6
5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6 5.5. Mechanism of Reusing Wireless Binding MIB Modules . . . . 6
5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7 5.6. CAPWAP Protocol Wireless Binding MIB Module . . . . . . . 7
5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7 5.7. WTP Profile . . . . . . . . . . . . . . . . . . . . . . . 7
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 7 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 8
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9
7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9 7.1. Relationship to SNMPv2-MIB Module . . . . . . . . . . . . 9
7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9 7.2. Relationship to IF-MIB Module . . . . . . . . . . . . . . 9
7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9 7.3. Relationship to ENTITY-MIB Module . . . . . . . . . . . . 9
7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10 7.4. Relationship to Wireless Binding MIB Modules . . . . . . . 10
7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10 7.5. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 10
8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10 8. Example of CAPWAP-BASE-MIB Module Usage . . . . . . . . . . . 10
9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 14
9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 14
9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 17
9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 17
9.3.1. Configuration Status Response Message . . . . . . . . 17 9.3.1. Configuration Status Response Message . . . . . . . . 17
9.3.2. Configuration Update Response Message . . . . . . . . 18 9.3.2. Configuration Update Response Message . . . . . . . . 18
10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 70 11. Security Considerations . . . . . . . . . . . . . . . . . . . 70
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71
12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 71 12.1. IANA Considerations for CAPWAP-BASE-MIB Module . . . . . . 72
12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 71 12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 72
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 71 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 72
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 71 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 72
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
15.1. Normative References . . . . . . . . . . . . . . . . . . . 72 15.1. Normative References . . . . . . . . . . . . . . . . . . . 72
15.2. Informative References . . . . . . . . . . . . . . . . . . 73 15.2. Informative References . . . . . . . . . . . . . . . . . . 73
Appendix A. Appendix A. Changes between -05 and -04 . . . . . . . 74 Appendix A. Appendix A. Changes between -06 and -05 . . . . . . . 74
1. Introduction 1. Introduction
The CAPWAP Protocol [RFC5415] defines a standard, interoperable The CAPWAP Protocol [RFC5415] defines a standard, interoperable
protocol, which enables an Access Controller (AC) to manage a protocol, which enables an Access Controller (AC) to manage a
collection of Wireless Termination Points(WTPs). collection of Wireless Termination Points(WTPs).
This document defines a MIB module that can be used to manage the This document defines a MIB module that can be used to manage the
CAPWAP implementations. This MIB module covers both configuration CAPWAP implementations. This MIB module covers both configuration
and WTP status-monitoring aspects of CAPWAP, and provides a way to and WTP status-monitoring aspects of CAPWAP, and provides a way to
skipping to change at page 5, line 49 skipping to change at page 5, line 49
devices are configured and deployed (centralized, autonomous, or some devices are configured and deployed (centralized, autonomous, or some
mix); mix);
- To be consistent with the CAPWAP protocol; - To be consistent with the CAPWAP protocol;
- To be independent of any wireless technologies and be able to reuse - To be independent of any wireless technologies and be able to reuse
wireless binding MIB modules defined by other SDOs; wireless binding MIB modules defined by other SDOs;
- To enable interoperability between vendors; - To enable interoperability between vendors;
- To meet requirements for the centralized WLAN architecture. - To meet the management requirements for the centralized WLAN
architecture.
5.4. Design Idea 5.4. Design Idea
The basic design idea of the CAPWAP-BASE-MIB module is: The basic design idea of the CAPWAP-BASE-MIB module is:
- The CAPWAP-BASE-MIB module MUST be run on the AC devices and is NOT - The SNMP agent MUST be run on the AC devices and is not REQUIRED on
REQUIRED on the WTP devices. It follows the same model as the CAPWAP the WTP devices. It follows the same model as the CAPWAP protocol:
protocol: Centralized Control; Centralized Control;
- It is designed to accommodate the specific needs of each wireless - It is designed to accommodate the specific needs of each wireless
technology in a standard way. It is independent of any wireless technology in a standard way. It is independent of any wireless
technologies; technologies;
- The ifIndex [RFC2863] is used as a common handler for corresponding - The ifIndex [RFC2863] is used as a common handler for corresponding
interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific interfaces in the CAPWAP-BASE-MIB and the MIB modules of specific
wireless technologies; wireless technologies;
- The operator could manage and control the centralized WLAN - The operator could manage and control the centralized WLAN
skipping to change at page 7, line 30 skipping to change at page 7, line 30
in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in in the scope of IEEE 802.11 [IEEE.802-11.2007]. In such cases, in
addition to the existing wireless binding MIB modules defined by addition to the existing wireless binding MIB modules defined by
other SDOs, a CAPWAP protocol wireless binding MIB module is required other SDOs, a CAPWAP protocol wireless binding MIB module is required
to be defined for a wireless binding, e.g, the CAPWAP Protocol to be defined for a wireless binding, e.g, the CAPWAP Protocol
Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib]. Binding MIB for IEEE 802.11 [I-D.ietf-capwap-802dot11-mib].
5.7. WTP Profile 5.7. WTP Profile
In a centralized WLAN architecture, a WTP profile is used to make In a centralized WLAN architecture, a WTP profile is used to make
configurations such as static IP address for a WTP before and after configurations such as static IP address for a WTP before and after
it connects to the AC. It MUST contain the serial number [RFC5415] it connects to the AC. It MUST contain the Base MAC address
of the WTP because the CAPWAP message received from the WTP contains [RFC5415] of the WTP because the CAPWAP message received from the WTP
its serial number and the AC uses this serial number to find the contains the Base MAC address and the AC uses this Base MAC address
corresponding WTP profile. to find the corresponding WTP profile.
The section 4.6.40 [RFC5415] does not clarify that the WTP's Base MAC
address MUST be included in the WTP Board Data message element. This
is a known errata item and assumed to be fixed in future by the
editors of the RFC5415.
Another important function of WTP profile is to trigger the creation Another important function of WTP profile is to trigger the creation
of WTP Virtual Radio Interfaces on the AC. To implement this of WTP Virtual Radio Interfaces on the AC. To implement this
function, a WTP profile MUST include the WTP's model number function, a WTP profile MUST include the WTP's model number
[RFC5415], which reflects the number of PHY radios on the WTP. In [RFC5415], which reflects the number of PHY radios on the WTP. In
this way, the creation of a WTP profile triggers the AC to this way, the creation of a WTP profile triggers the AC to
automatically create the same number of WTP Virtual Radio Interfaces automatically create the same number of WTP Virtual Radio Interfaces
corresponding to the WTP's PHY radios without manual intervention. corresponding to the WTP's PHY radios without manual intervention.
With the ifIndexes of WTP Virtual Radio Interfaces, the operator With the ifIndexes of WTP Virtual Radio Interfaces, the operator
could configure and manage the WTP's PHY radios through the wireless could configure and manage the WTP's PHY radios through the wireless
skipping to change at page 8, line 16 skipping to change at page 8, line 24
2) capwapBaseMacAclTable 2) capwapBaseMacAclTable
The ACL table is used to configure stations' Access Control The ACL table is used to configure stations' Access Control
List(ACL). List(ACL).
3) capwapBaseWtpProfileTable 3) capwapBaseWtpProfileTable
The WTP profile table is used to configure WTP profiles for WTPs to The WTP profile table is used to configure WTP profiles for WTPs to
be managed before they connect to the AC. An operator could change a be managed before they connect to the AC. An operator could change a
WTP's current configuration by changing the values of parameters in WTP's current configuration by changing the values of parameters in
the corresponding WTP profile. the corresponding WTP profile, then the WTP could get the new
configuration through the CAPWAP control channel.
4) capwapBaseWtpStateTable 4) capwapBaseWtpStateTable
The WTPs status table is used to indicate each WTP's CAPWAP FSM The WTPs status table is used to indicate each WTP's CAPWAP FSM
state, and helps operator to query WTPs' current configuration. state, and helps operator to query WTPs' current configuration.
5) capwapBaseWtpTable 5) capwapBaseWtpTable
The WTPs table is used display properties of WTPs in running state. The WTPs table is used display properties of WTPs in running state.
skipping to change at page 9, line 51 skipping to change at page 10, line 7
and is not required on the WTP. With the ENTITY-MIB module on the and is not required on the WTP. With the ENTITY-MIB module on the
AC, it could keep entity information such as firmware revision and AC, it could keep entity information such as firmware revision and
software revision of the AC and WTPs. From the ENTITY-MIB module's software revision of the AC and WTPs. From the ENTITY-MIB module's
perspective, the overall physical entity (AC) is a 'compound' of perspective, the overall physical entity (AC) is a 'compound' of
multiple physical entities (that is, the WTPs connected to AC), and multiple physical entities (that is, the WTPs connected to AC), and
all entities are each identified by a Physical index. The all entities are each identified by a Physical index. The
capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the capwapBaseWtpTable of the CAPWAP-BASE-MIB module uses the
capwapBaseWtpPhyIndex object to store the mappings of WTP object capwapBaseWtpPhyIndex object to store the mappings of WTP object
between CAPWAP-BASE-MIB and ENTITY-MIB modules. between CAPWAP-BASE-MIB and ENTITY-MIB modules.
By combining the MIB modules, operators could query the status and By querying both the CAPWAP-BASE-MIB and ENTITY-MIB modules,
properties of the AC and WTPs. For example, they could get a WTP's operators could query the status and properties of the AC and WTPs.
current status through the CAPWAP-BASE-MIB module, and a WTP's For example, they could get a WTP's current status through the
software revision information through the ENTITY-MIB module. The CAPWAP-BASE-MIB module, and a WTP's software revision information
CAPWAP-BASE-MIB module does not duplicate those objects defined in through the ENTITY-MIB module. The CAPWAP-BASE-MIB module does not
the ENTITY-MIB module. duplicate those objects defined in the ENTITY-MIB module.
7.4. Relationship to Wireless Binding MIB Modules 7.4. Relationship to Wireless Binding MIB Modules
The wireless binding MIB module of a wireless technology (such as The wireless binding MIB module of a wireless technology (such as
[IEEE.802-11.2007]) is required to be supported on the AC. The [IEEE.802-11.2007]) is required to be supported on the AC. The
CAPWAP-BASE-MIB module is able to support any wireless binding. CAPWAP-BASE-MIB module is able to support any wireless binding.
Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a Through the ifIndexes of WTP Virtual Radio Interfaces, it provides a
consistent and abstract way of reusing MIB objects in the wireless consistent and abstract way of reusing MIB objects in the wireless
binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate binding MIB modules. The CAPWAP-BASE-MIB module does not duplicate
those objects defined in the wireless binding MIB modules. those objects defined in the wireless binding MIB modules.
skipping to change at page 10, line 33 skipping to change at page 10, line 38
FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] and ENTITY-MIB
[RFC4133]. [RFC4133].
8. Example of CAPWAP-BASE-MIB Module Usage 8. Example of CAPWAP-BASE-MIB Module Usage
Here takes IEEE 802.11 binding as an example to show how the MIB Here takes IEEE 802.11 binding as an example to show how the MIB
modules operate. modules operate.
1) Create a WTP profile 1) Create a WTP profile
Suppose the WTP's serial identifier is '12345678'. Create the WTP Suppose the WTP's Base MAC address is '00:01:01:01:01:00'. Create
profile as follows: the WTP profile as follows:
In CapwapBaseWtpProfileTable In CapwapBaseWtpProfileTable
{ {
capwapBaseWtpProfileId = 1, capwapBaseWtpProfileId = 1,
capwapBaseWtpProfileName = 'WTP Profile 12345678', capwapBaseWtpProfileName = 'WTP Profile 123456',
capwapBaseWtpProfileWTPSerialId = '12345678', capwapBaseWtpProfileWtpMacAddr = '00:01:01:01:01:00',
capwapBaseWtpProfileWTPModelNumber = 'WTP123', capwapBaseWtpProfileWtpModelNumber = 'WTP123',
capwapBaseWtpProfileWtpName = 'WTP 12345678', capwapBaseWtpProfileWtpName = 'WTP 123456',
capwapBaseWtpProfileWtpLocation = 'office', capwapBaseWtpProfileWtpLocation = 'office',
capwapBaseWtpProfileWtpStaticIpEnable = true(1), capwapBaseWtpProfileWtpStaticIpEnable = true(1),
capwapBaseWtpProfileWtpStaticIpType = ipv4(1), capwapBaseWtpProfileWtpStaticIpType = ipv4(1),
capwapBaseWtpProfileWtpStaticIp = '192.168.0.100', capwapBaseWtpProfileWtpStaticIp = '192.168.0.100',
capwapBaseWtpProfileWtpNetmask = '255.255.255.0', capwapBaseWtpProfileWtpNetmask = '255.255.255.0',
capwapBaseWtpProfileWtpGateway = '192.168.0.1', capwapBaseWtpProfileWtpGateway = '192.168.0.1',
capwapBaseWtpProfileWtpFallbackEnable = true(1), capwapBaseWtpProfileWtpFallbackEnable = true(1),
capwapBaseWtpProfileWtpEchoInterval = 30, capwapBaseWtpProfileWtpEchoInterval = 30,
capwapBaseWtpProfileWtpIdleTimeout = 300, capwapBaseWtpProfileWtpIdleTimeout = 300,
capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20, capwapBaseWtpProfileWtpMaxDiscoveryInterval = 20,
skipping to change at page 12, line 14 skipping to change at page 12, line 14
In ifTable In ifTable
{ {
ifIndex = 10, ifIndex = 10,
ifDescr = 'WTP Virtual Radio Interface', ifDescr = 'WTP Virtual Radio Interface',
ifType = xxx, ifType = xxx,
RFC Editor - please replace xxx with the value RFC Editor - please replace xxx with the value
allocated by IANA for IANAifType of WTP Virtual Radio Interface allocated by IANA for IANAifType of WTP Virtual Radio Interface
ifMtu = 0, ifMtu = 0,
ifSpeed = 0, ifSpeed = 0,
ifPhysAddress = '000000', ifPhysAddress = '00:00:00:00:00:00',
ifAdminStatus = true(1), ifAdminStatus = true(1),
ifOperStatus = false(0), ifOperStatus = false(0),
ifLastChange = 0, ifLastChange = 0,
ifInOctets = 0, ifInOctets = 0,
ifInUcastPkts = 0, ifInUcastPkts = 0,
ifInDiscards = 0, ifInDiscards = 0,
ifInErrors = 0, ifInErrors = 0,
ifInUnknownProtos = 0, ifInUnknownProtos = 0,
ifOutOctets = 0, ifOutOctets = 0,
ifOutUcastPkts = 0, ifOutUcastPkts = 0,
skipping to change at page 13, line 18 skipping to change at page 13, line 18
This configuration is made on the AC through a specific wireless This configuration is made on the AC through a specific wireless
binding MIB module such as the IEEE 802.11 MIB module. binding MIB module such as the IEEE 802.11 MIB module.
The following shows an example of configuring parameters for a WTP The following shows an example of configuring parameters for a WTP
Virtual Radio Interface with ifIndex 10 through the IEEE 802.11 Virtual Radio Interface with ifIndex 10 through the IEEE 802.11
Dot11OperationTable [IEEE.802-11.2007]. Dot11OperationTable [IEEE.802-11.2007].
In Dot11OperationTable In Dot11OperationTable
{ {
ifIndex = 10, ifIndex = 10,
dot11MACAddress = '000000', dot11MACAddress = '00:00:00:00:00:00',
dot11RTSThreshold = 2347, dot11RTSThreshold = 2347,
dot11ShortRetryLimit = 7, dot11ShortRetryLimit = 7,
dot11LongRetryLimit = 4, dot11LongRetryLimit = 4,
dot11FragmentationThreshold = 256, dot11FragmentationThreshold = 256,
dot11MaxTransmitMSDULifetime = 512, dot11MaxTransmitMSDULifetime = 512,
dot11MaxReceiveLifetime = 512, dot11MaxReceiveLifetime = 512,
dot11ManufacturerID = 'capwap', dot11ManufacturerID = 'capwap',
dot11ProductID = 'capwap' dot11ProductID = 'capwap'
dot11CAPLimit = 2,
dot11HCCWmin = 0,
dot11HCCWmax = 0,
dot11HCCAIFSN = 1,
dot11ADDBAResponseTimeout = 1,
dot11ADDTSResponseTimeout = 1,
dot11ChannelUtilizationBeaconInterval = 50,
dot11ScheduleTimeout = 10,
dot11DLSResponseTimeout = 10,
dot11QAPMissingAckRetryLimit = 1,
dot11EDCAAveragingPeriod = 5
} }
4) Current configuration status report from the WTP to the AC 4) Current configuration status report from the WTP to the AC
According to [RFC5415], before a WTP that has joined the AC gets According to [RFC5415], before a WTP that has joined the AC gets
configuration from the AC, it needs to report its current configuration from the AC, it needs to report its current
configuration status by sending a configuration status request configuration status by sending a configuration status request
message to the AC, which use the message to update MIB objects on the message to the AC, which use the message to update MIB objects on the
AC. For example, for IEEE 802.11 binding, the AC updates data in the AC. For example, for IEEE 802.11 binding, the AC updates data in the
ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the ifTable [RFC2863] and IEEE 802.11 MIB module so on according to the
skipping to change at page 18, line 38 skipping to change at page 18, line 38
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2,
Integer32, Unsigned32, Counter32 Integer32, Unsigned32, Counter32
FROM SNMPv2-SMI FROM SNMPv2-SMI
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
capwapBaseMIB MODULE-IDENTITY capwapBaseMIB MODULE-IDENTITY
LAST-UPDATED "200905290000Z" -- May 29th, 2009 LAST-UPDATED "200908130000Z" -- August 13th, 2009
ORGANIZATION "IETF Control And Provisioning of Wireless Access ORGANIZATION "IETF Control And Provisioning of Wireless Access
Points (CAPWAP) Working Group Points (CAPWAP) Working Group
http://www.ietf.org/html.charters/capwap-charter.html" http://www.ietf.org/html.charters/capwap-charter.html"
CONTACT-INFO CONTACT-INFO
"General Discussion: capwap@frascone.com "General Discussion: capwap@frascone.com
To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap To Subscribe: http://lists.frascone.com/mailman/listinfo/capwap
Yang Shi Yang Shi (editor)
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian Hangzhou H3C Tech. Co., Ltd.
District,Beijing,China(100085) Beijing R&D Center of H3C, Digital Technology Plaza,
Email: young@h3c.com NO.9 Shangdi 9th Street,Haidian District,
Beijing
China(100085)
Phone: +86 010 82775276
EMail: young@h3c.com
David T. Perkins David T. Perkins
228 Bayview Dr 228 Bayview Dr
San Carlos, CA 94070 San Carlos, CA 94070
USA USA
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
Chris Elliott Chris Elliott
Cisco Systems, Inc. Cisco Systems, Inc.
skipping to change at page 19, line 31 skipping to change at page 19, line 35
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2009 The Internet Society. This version of "Copyright (C) 2009 The Internet Society. This version of
the MIB module is part of RFC xxx; see the RFC itself the MIB module is part of RFC xxx; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the CAPWAP Protocol." the CAPWAP Protocol."
REVISION "200905290000Z" REVISION "200908130000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpProfileIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP profile." "Represents the unique identifier of a WTP profile."
SYNTAX Unsigned32 (0..4096) SYNTAX Unsigned32 (0..4096)
CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "32a" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP instance. "Represents the unique identifier of a WTP instance.
As usual, a serial number of WTP is used." As usual, the Base MAC address of WTP is used."
SYNTAX OCTET STRING (SIZE (0..32)) SYNTAX OCTET STRING (SIZE (6))
CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION CapwapBaseStationIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:" DISPLAY-HINT "1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a station instance. "Represents the unique identifier of a station instance.
As usual, the MAC address of the station is used." As usual, the MAC address of station is used."
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION CapwapBaseRadioIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a radio on a WTP." "Represents the unique identifier of a radio on a WTP."
SYNTAX Unsigned32 (1..31) SYNTAX Unsigned32 (1..31)
CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION CapwapBaseTunnelModeTC ::= TEXTUAL-CONVENTION
skipping to change at page 27, line 36 skipping to change at page 27, line 44
-- capwapBaseWtpProfileTable Table -- capwapBaseWtpProfileTable Table
capwapBaseWtpProfileTable OBJECT-TYPE capwapBaseWtpProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry SYNTAX SEQUENCE OF CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that configure WTP profiles for WTPs to "A table of objects that configure WTP profiles for WTPs to
be managed before they connect to the AC. be managed before they connect to the AC.
An operator could change a WTP's configuration by changing An operator could change a WTP's configuration by changing
the values of parameters in the corresponding WTP profile. the values of parameters in the corresponding WTP profile,
then the WTP could get the new configuration through the
CAPWAP control channel.
Values of all read-create objects in this table are Values of all read-create objects in this table are
persistent at restart/reboot." persistent at restart/reboot."
::= { capwapBaseWtps 1 } ::= { capwapBaseWtps 1 }
capwapBaseWtpProfileEntry OBJECT-TYPE capwapBaseWtpProfileEntry OBJECT-TYPE
SYNTAX CapwapBaseWtpProfileEntry SYNTAX CapwapBaseWtpProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that configure and display a WTP profile." "A set of objects that configure and display a WTP profile."
INDEX { capwapBaseWtpProfileId } INDEX { capwapBaseWtpProfileId }
::= { capwapBaseWtpProfileTable 1 } ::= { capwapBaseWtpProfileTable 1 }
CapwapBaseWtpProfileEntry ::= SEQUENCE { CapwapBaseWtpProfileEntry ::= SEQUENCE {
capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC, capwapBaseWtpProfileId CapwapBaseWtpProfileIdTC,
capwapBaseWtpProfileName SnmpAdminString, capwapBaseWtpProfileName SnmpAdminString,
capwapBaseWtpProfileWTPSerialId CapwapBaseWtpIdTC, capwapBaseWtpProfileWtpMacAddr CapwapBaseWtpIdTC,
capwapBaseWtpProfileWTPModelNumber SnmpAdminString, capwapBaseWtpProfileWtpModelNumber SnmpAdminString,
capwapBaseWtpProfileWtpName OCTET STRING, capwapBaseWtpProfileWtpName OCTET STRING,
capwapBaseWtpProfileWtpLocation OCTET STRING, capwapBaseWtpProfileWtpLocation OCTET STRING,
capwapBaseWtpProfileWtpStaticIpEnable TruthValue, capwapBaseWtpProfileWtpStaticIpEnable TruthValue,
capwapBaseWtpProfileWtpStaticIpType InetAddressType, capwapBaseWtpProfileWtpStaticIpType InetAddressType,
capwapBaseWtpProfileWtpStaticIp InetAddress, capwapBaseWtpProfileWtpStaticIp InetAddress,
capwapBaseWtpProfileWtpNetmask InetAddress, capwapBaseWtpProfileWtpNetmask InetAddress,
capwapBaseWtpProfileWtpGateway InetAddress, capwapBaseWtpProfileWtpGateway InetAddress,
capwapBaseWtpProfileWtpFallbackEnable INTEGER, capwapBaseWtpProfileWtpFallbackEnable INTEGER,
capwapBaseWtpProfileWtpEchoInterval Unsigned32, capwapBaseWtpProfileWtpEchoInterval Unsigned32,
capwapBaseWtpProfileWtpIdleTimeout Unsigned32, capwapBaseWtpProfileWtpIdleTimeout Unsigned32,
skipping to change at page 28, line 43 skipping to change at page 29, line 5
::= { capwapBaseWtpProfileEntry 1 } ::= { capwapBaseWtpProfileEntry 1 }
capwapBaseWtpProfileName OBJECT-TYPE capwapBaseWtpProfileName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the name of a WTP profile." "Represents the name of a WTP profile."
::= { capwapBaseWtpProfileEntry 2 } ::= { capwapBaseWtpProfileEntry 2 }
capwapBaseWtpProfileWTPSerialId OBJECT-TYPE capwapBaseWtpProfileWtpMacAddr OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the serial identifier of a WTP. "Represents the Base MAC address of a WTP.
A WTP profile MUST contain the serial number of the WTP A WTP profile MUST contain the Base MAC address of the WTP
because the CAPWAP message received from the WTP contains because the CAPWAP message received from the WTP contains
its serial number and the AC uses the serial number to its Base MAC address and the AC uses the Base MAC address to
find the corresponding WTP profile." find the corresponding WTP profile.
The section 4.6.40 [RFC5415] does not clarify that the WTP's
Base MAC address MUST be included in the WTP Board Data
message element. This is a known errata item and assumed to be
fixed in future by the editors of the RFC5415."
REFERENCE REFERENCE
"Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415." "Section 4.6.40. of CAPWAP Protocol Specification, RFC 5415."
::= { capwapBaseWtpProfileEntry 3 } ::= { capwapBaseWtpProfileEntry 3 }
capwapBaseWtpProfileWTPModelNumber OBJECT-TYPE capwapBaseWtpProfileWtpModelNumber OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the model number of a WTP. "Represents the model number of a WTP.
A WTP profile MUST include the WTP's model number, which A WTP profile MUST include the WTP's model number, which
reflects the number of PHY radios on the WTP. reflects the number of PHY radios on the WTP.
In this way, the creation of a WTP profile triggers the AC In this way, the creation of a WTP profile triggers the AC
to automatically create the same number of WTP Virtual Radio to automatically create the same number of WTP Virtual Radio
Interfaces corresponding to the WTP's PHY radios without Interfaces corresponding to the WTP's PHY radios without
skipping to change at page 65, line 31 skipping to change at page 65, line 45
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to configure "A collection of objects which are used to configure
the stations ACL." the stations ACL."
::= { capwapBaseGroups 4 } ::= { capwapBaseGroups 4 }
capwapBaseWtpProfileGroup OBJECT-GROUP capwapBaseWtpProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpProfileName, capwapBaseWtpProfileName,
capwapBaseWtpProfileWTPSerialId, capwapBaseWtpProfileWtpMacAddr,
capwapBaseWtpProfileWTPModelNumber, capwapBaseWtpProfileWtpModelNumber,
capwapBaseWtpProfileWtpName, capwapBaseWtpProfileWtpName,
capwapBaseWtpProfileWtpLocation, capwapBaseWtpProfileWtpLocation,
capwapBaseWtpProfileRowStatus capwapBaseWtpProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects which are used to configure "A collection of objects which are used to configure
the WTP profile." the WTP profile."
::= { capwapBaseGroups 5 } ::= { capwapBaseGroups 5 }
skipping to change at page 71, line 49 skipping to change at page 72, line 25
12.2. IANA Considerations for ifType 12.2. IANA Considerations for ifType
Require IANA to assign a ifType for the WTP Virtual Radio Interface. Require IANA to assign a ifType for the WTP Virtual Radio Interface.
13. Contributors 13. Contributors
This MIB module is based on contributions from Long Gao. This MIB module is based on contributions from Long Gao.
14. Acknowledgements 14. Acknowledgements
The authors wish to thank David Harrington, Fei Fang, Xuebin Zhu, Hao The authors wish to thank David Harrington, Abhijit Choudhury, Fei
Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. Fang, Xuebin Zhu, Hao Song, Yu Liu, Sachin Dutta, Ju Wang, Yujin
Zhao, Haitao Zhang, Xiansen Cai.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in [RFC2119] Bradner, S., "Key words for use in
RFCs to Indicate Requirement Levels", RFCs to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997. BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., [RFC2578] McCloghrie, K., Ed., Perkins, D.,
skipping to change at page 74, line 4 skipping to change at page 74, line 30
[RFC5416] Calhoun, P., Montemurro, M., and D. [RFC5416] Calhoun, P., Montemurro, M., and D.
Stanley, "Control and Provisioning of Stanley, "Control and Provisioning of
Wireless Access Points (CAPWAP) Wireless Access Points (CAPWAP)
Protocol Binding for IEEE 802.11", Protocol Binding for IEEE 802.11",
RFC 5416, March 2009. RFC 5416, March 2009.
[I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C., [I-D.ietf-capwap-802dot11-mib] Shi, Y., Perkins, D., Elliott, C.,
and Y. Zhang, "CAPWAP Protocol and Y. Zhang, "CAPWAP Protocol
Binding MIB for IEEE 802.11", Binding MIB for IEEE 802.11",
(work in progress), October 2008. draft-ietf-capwap-802dot11-mib-04
(work in progress), May 2009.
Appendix A. Appendix A. Changes between -05 and -04 Appendix A. Appendix A. Changes between -06 and -05
1) To close the issue 68 "Suggest Let Base MIB to Support a WTP All the issues are tracked by
Profile" http://www.capwap.org/cgi-bin/roundup.cgi/MIB/
-------------------------------------------------------------- 1)Issue 70: For Base MIB, some bugs detected post-WGLC but pre-IESG
Add a new section 5.7. WTP Profile, update the section 8, add a new capwapBaseWtpProfileWTPSerialId should be
table of capwapBaseWtpProfileTable and update the related MIB capwapBaseWtpProfileWtpSerialId (second WTP should be Wtp).
objects. capwapBaseWtpProfileWTPModelNumber should be
capwapBaseWtpProfileWtpModelNumber (second WTP should be Wtp).
In the section 5.4, it should say "The SNMP agent MUST be run on the
AC devices" instead of CAPWAP-BASE-MIB.
The editor's address is updated.
2)Issue 72: The WTP id issue in the Base MIB
Updated the section 5.7. WTP Profile and the description of
capwapBaseWtpProfileWtpMacAddr. It clarify that "The section 4.6.40
[RFC5415] does not clarify that the WTP's Base MAC address MUST be
included in the WTP Board Data message element. This is a known
errata item and assumed to be fixed in future by the editors of the
RFC5415."
Also, updated the ID of WTP with Base MAC address instead of the
serial number.
3)Issue 73: For the example section in the Base and Dot11 MIB, the
Dot11OperationTable is incorrect
In the draft version 05, the Dot11OperationTable follows the IEEE
802.11-1999 instead of IEEE 802.11-2007. It is incorrect. The draft
version 06 is updated according to IEEE 802.11-2007.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
Hangzhou H3C Tech. Co., Ltd Hangzhou H3C Tech. Co., Ltd.
Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, Beijing R&D Center of H3C, Digital Technology Plaza,
NO.9 Shangdi 9th Street,Haidian District,
Beijing Beijing
China(100085) China(100085)
Phone: +86 010 82775276 Phone: +86 010 82775276
EMail: young@h3c.com EMail: young@h3c.com
David Perkins (editor) David Perkins (editor)
SNMPinfo SNMPinfo
288 Quailbrook Ct San Carlos, 288 Quailbrook Ct San Carlos,
CA 94070 CA 94070
 End of changes. 38 change blocks. 
68 lines changed or deleted 124 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/