draft-ietf-capwap-base-mib-02.txt   draft-ietf-capwap-base-mib-03.txt 
Internet Engineering Task Force Y. Shi, Ed. Internet Engineering Task Force Y. Shi, Ed.
Internet-Draft H3C Tech. Co., Ltd Internet-Draft H3C Tech. Co., Ltd
Intended status: Standards Track D. Perkins, Ed. Intended status: Standards Track D. Perkins, Ed.
Expires: April 30, 2009 SNMPinfo Expires: May 5, 2009 SNMPinfo
C. Elliott, Ed. C. Elliott, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
Y. Zhang, Ed. Y. Zhang, Ed.
Fortinet, Inc. Fortinet, Inc.
October 27, 2008 November 1, 2008
CAPWAP Protocol Base MIB CAPWAP Protocol Base MIB
draft-ietf-capwap-base-mib-02 draft-ietf-capwap-base-mib-03
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 April 30, 2009. This Internet-Draft will expire on May 5, 2009.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular, it for use with network management protocols. In particular, it
describes managed objects for modeling the Control And Provisioning describes managed objects for modeling the Control And Provisioning
of Wireless Access Points (CAPWAP) Protocol. of Wireless Access Points (CAPWAP) Protocol.
Table of Contents Table of Contents
skipping to change at page 2, line 24 skipping to change at page 2, line 24
6.2. The capwapBaseConformance Subtree . . . . . . . . . . . . 6 6.2. The capwapBaseConformance Subtree . . . . . . . . . . . . 6
6.3. The capwapBaseNotifications Subtree . . . . . . . . . . . 6 6.3. The capwapBaseNotifications Subtree . . . . . . . . . . . 6
6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 6 6.4. Brief Description of MIB Objects . . . . . . . . . . . . . 6
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7
7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 8 7.3. Relationship to the ENTITY-MIB . . . . . . . . . . . . . . 8
7.4. Relationship to MIB standards of other SDOs . . . . . . . 9 7.4. Relationship to MIB standards of other SDOs . . . . . . . 9
7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 7.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
8. Example of CAPWAP-BASE-MIB Usage . . . . . . . . . . . . . . . 9 8. Example of CAPWAP-BASE-MIB Usage . . . . . . . . . . . . . . . 9
9. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. CAPWAP Message Element Extension . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 54 9.1. CAPWAP Protocol Timers . . . . . . . . . . . . . . . . . . 12
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 9.2. CAPWAP Protocol Variables . . . . . . . . . . . . . . . . 15
11.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 55 9.3. CAPWAP Messages for CAPWAP Control Message Extension . . . 15
11.2. IANA Considerations for ifType . . . . . . . . . . . . . . 55 9.3.1. Configuration Status Response Message . . . . . . . . 15
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 55 9.3.2. Configuration Update Response Message . . . . . . . . 16
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 56 10. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 16
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56 11. Security Considerations . . . . . . . . . . . . . . . . . . . 64
14.1. Normative References . . . . . . . . . . . . . . . . . . . 56 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65
14.2. Informative References . . . . . . . . . . . . . . . . . . 57 12.1. IANA Considerations for CAPWAP-BASE-MIB . . . . . . . . . 65
12.2. IANA Considerations for ifType . . . . . . . . . . . . . . 65
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 65
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66
15.1. Normative References . . . . . . . . . . . . . . . . . . . 66
15.2. Informative References . . . . . . . . . . . . . . . . . . 67
Appendix A. Appendix A. Changes from -02 . . . . . . . . . . . . 67
1. Introduction 1. Introduction
The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines The CAPWAP Protocol [I-D.ietf-capwap-protocol-specification] defines
a standard, interoperable protocol, which enables an Access a standard, interoperable protocol, which enables an Access
Controller (AC) to manage a collection of Wireless Termination Controller (AC) to manage a collection of Wireless Termination
Points(WTPs) Points(WTPs)
This document defines a MIB module that can be used to manage CAPWAP This document defines a MIB module that can be used to manage CAPWAP
implementations. This MIB module covers both configuration and WTP implementations. This MIB module covers both configuration and WTP
skipping to change at page 12, line 5 skipping to change at page 12, line 5
For example, operator could query the statistics data of For example, operator could query the statistics data of
WLAN service through 802.11 binding MIB and IEEE 802.11 MIB. WLAN service through 802.11 binding MIB and IEEE 802.11 MIB.
In the CAPWAP 802.11 binding MIB draft, it will give more explain. In the CAPWAP 802.11 binding MIB draft, it will give more explain.
7) Query other properties of WTP 7) Query other properties of WTP
Operator could query MIB objects in the ENTITY-MIB by Operator could query MIB objects in the ENTITY-MIB by
capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB. capwapBaseWtpPhyIndex in the capwapBaseWtpTable of CAPWAP-BASE-MIB.
The properties of WTP such as software version, hardware version The properties of WTP such as software version, hardware version
and so on are available in the ENTITY-MIB. and so on are available in the ENTITY-MIB.
9. Definitions 9. CAPWAP Message Element Extension
This section describes the CAPWAP control message extension for
CAPWAP protocol to support CAPWAP-BASE-MIB.
To enable CAPWAP protocol timers and variables[I-D.ietf-capwap-
protocol-specification] manageable through CAPWAP protocol, the
following capwap message element extensions are defined using Vendor
Specific Payload message element in this section. These message
elements are used by WTP to report extra configuration information to
AC.
CAPWAP Message Element Vendor Identifier Element ID
CAPWAP Protocol Timers Id assigned by IANA 1
CAPWAP Protocol Variables Id assigned by IANA 2
9.1. CAPWAP Protocol Timers
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Element ID | DataChannelKeepAlive |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DataChannelDeadInterval | DiscoveryInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DTLSSessionDelete | EchoInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IdleTimeout |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ImageDataStartTimer | MaxDiscoveryInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ReportInterval | RetransmitInterval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SilentInterval | StatisticsTimer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WaitDTLS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Type: 37 for Vendor Specific Payload
Length: 34
Vendor Identifier: The Vendor Identifier field is assigned by IANA.
Element ID: The Element ID field is set to 1 for CAPWAP Protocol
Timers.
DataChannelKeepAlive: A 16-bit value representing the time,
in seconds, that is used by the WTP to determine the next
must transmit the Data Channel KeepAlive. (see [I-D.ietf-capwap-
protocol-specification]).
DataChannelDeadInterval: A 16-bit value representing the minimum
time, in seconds, a WTP MUST wait without having received a Data
Channel Alive packets may be considered dead. The value of this
timer MUST be no less than 2*DataChannelKeepAlive seconds and
no greater that 240 seconds (see [I-D.ietf-capwap-protocol-
specification]).
DiscoveryInterval: A 16-bit value representing the minimum time, in
seconds, that a WTP MUST wait after receiving a Discovery Response
message, before initiating a DTLS handshake (see [I-D.ietf-capwap-
protocol-specification]).
DTLSSessionDelete: A 16-bit value representing the minimum time, in
seconds, a WTP MUST wait for DTLS session deletion (see [I-D.ietf-
capwap-protocol-specification]).
EchoInterval: A 16-bit value representing the minimum time, in
seconds, between sending Echo Request messages to the AC with
which the WTP has joined (see [I-D.ietf-capwap-protocol-
specification]).
IdleTimeout: A 32-bit value representing the idle timeout value that
the WTP SHOULD enforce for its active station. The default Idle
Timeout is 300 seconds (see [I-D.ietf-capwap-protocol-
specification]).
ImageDataStartTimer: A 16-bit value representing the number of
seconds the WTP will wait for its peer to transmit the Image
Data Request (see [I-D.ietf-capwap-protocol-specification]).
MaxDiscoveryInterval: A 16-bit value representing the maximum time
allowed between sending Discovery Request messages, in seconds.
This value MUST be no less than 2 seconds and no greater than 180
seconds (see [I-D.ietf-capwap-protocol-specification]).
ReportInterval: A 16-bit value representing the time, in seconds,
that is used by the WTP to determine the interval the WTP uses
between sending the Decryption Error message elements to inform
the AC of decryption errors (see [I-D.ietf-capwap-protocol-
specification]).
RetransmitInterval: A 16-bit value representing the minimum time,
in seconds, in which a non-acknowledged CAPWAP packet will be
retransmitted (see [I-D.ietf-capwap-protocol-specification]).
SilentInterval: The minimum time, in seconds, a WTP MUST wait before
it MAY again send Discovery Request messages or attempt to
establish DTLS session (see [I-D.ietf-capwap-protocol-
specification]).
StatisticsTimer: A 16-bit value representing the time, in seconds,
that is used by the WTP to determine the interval the WTP uses
between the WTP Events Requests it transmits to the AC to
communicate its statistics (see [I-D.ietf-capwap-protocol-
specification]).
WaitDTLS: A 16-bit value representing the maximum time, in seconds,
a WTP MUST wait without having received a DTLS Handshake message
from an AC. This timer MUST be greater than 30 seconds (see
[I-D.ietf-capwap-protocol-specification]).
9.2. CAPWAP Protocol Variables
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Element ID | MaxDiscoveries |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MaxFailedDTLSSessionRetry | MaxRetransmit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 37 for Vendor Specific Payload
Length: 12
Vendor Identifier: The Vendor Identifier field is assigned by IANA.
Element ID: The Element ID field is set to 2 for CAPWAP Protocol
Variables.
MaxDiscoveries: A 16-bit value representing the maximum number of
Discovery Request messages that will be sent after a WTP boots
(see [I-D.ietf-capwap-protocol-specification]).
MaxFailedDTLSSessionRetry: A 16-bit value representing the maximum
number of failed DTLS session establishment attempts before the
CAPWAP device enters a silent period (see [I-D.ietf-capwap-
protocol-specification]).
MaxRetransmit: A 16-bit value representing the maximum number of
retransmissions for a given CAPWAP packet before the link layer
considers the peer dead (see [I-D.ietf-capwap-protocol-
specification]).
9.3. CAPWAP Messages for CAPWAP Control Message Extension
For CAPWAP Control Message Extension, the following CAPWAP messages
will be used.
9.3.1. Configuration Status Response Message
The following message elements MAY be included in the CAPWAP
Configuration Status Response Message.
- CAPWAP Protocol Timers, see Section Section 9.1
- CAPWAP Protocol Variables, see Section Section 9.2
9.3.2. Configuration Update Response Message
The following message elements MAY be included in the CAPWAP
Configuration Update Response Message.
- CAPWAP Protocol Timers, see Section Section 9.1
- CAPWAP Protocol Variables, see Section Section 9.2
10. Definitions
CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN CAPWAP-BASE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
PhysAddress, TEXTUAL-CONVENTION, TruthValue, PhysAddress, TEXTUAL-CONVENTION, TruthValue,
DateAndTime, RowStatus DateAndTime, RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndex InterfaceIndex
FROM IF-MIB FROM IF-MIB
skipping to change at page 12, line 29 skipping to change at page 16, 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 "200810270000Z" -- Oct 27th, 2008 LAST-UPDATED "200811010000Z" -- Nov 01th, 2008
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
H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian H3C, Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian
District,Beijing,China(100085) District,Beijing,China(100085)
skipping to change at page 13, line 22 skipping to change at page 17, line 31
USA USA
Email: yzhang@fortinet.com" Email: yzhang@fortinet.com"
DESCRIPTION DESCRIPTION
"Copyright (C) 2008 The Internet Society. This version of "Copyright (C) 2008 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 "200810270000Z" REVISION "200811010000Z"
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxx" "Initial version published as RFC xxx"
::= { mib-2 xxx } ::= { mib-2 xxx }
-- Textual Conventions -- Textual Conventions
CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION CapwapBaseWtpIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "128a" DISPLAY-HINT "128a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 16, line 5 skipping to change at page 20, line 14
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the total number of WTPs which are connecting to "Represents the total number of WTPs which are connecting to
AC." AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 1 } ::= { capwapBaseAc 1 }
capwapBaseMaxWtpSessionsConfig OBJECT-TYPE capwapBaseWtpSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of WTP sessions configured for "Represents the maximum number of WTP sessions configured for
the AC." the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 2 } ::= { capwapBaseAc 2 }
skipping to change at page 16, line 27 skipping to change at page 20, line 36
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the total number of stations which are accessing "Represents the total number of stations which are accessing
the wireless service provided by the AC." the wireless service provided by the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 3 } ::= { capwapBaseAc 3 }
capwapBaseMaxStationSessionsConfig OBJECT-TYPE capwapBaseStationSessionsLimit OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum number of station sessions configured for "Represents the maximum number of station sessions configured
the AC." for the AC."
REFERENCE REFERENCE
"Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.1. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseAc 4 } ::= { capwapBaseAc 4 }
capwapBaseDataChannelSecOptions OBJECT-TYPE capwapBaseDataChannelSecOptions OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
other(0), other(0),
clear(1), clear(1),
dtls(2) dtls(2)
} }
skipping to change at page 20, line 22 skipping to change at page 24, line 33
"A set of objects that configure station Access Control "A set of objects that configure station Access Control
List (ACL). List (ACL).
Values of all read-create objects in this Values of all read-create objects in this
table are persistent at AC restart/reboot." table are persistent at AC restart/reboot."
INDEX { capwapBaseMacAclId } INDEX { capwapBaseMacAclId }
::= { capwapBaseMacAclTable 1 } ::= { capwapBaseMacAclTable 1 }
CapwapBaseMacAclEntry ::= SEQUENCE { CapwapBaseMacAclEntry ::= SEQUENCE {
capwapBaseMacAclId Unsigned32, capwapBaseMacAclId Unsigned32,
capwapBaseMacAclStationId CapwapBaseStationIdTC, capwapBaseMacAclStationId CapwapBaseStationIdTC,
capwapBaseMacAclsRowStatus RowStatus capwapBaseMacAclRowStatus RowStatus
} }
capwapBaseMacAclId OBJECT-TYPE capwapBaseMacAclId OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a unique id for a ACL." "Represents a unique id for a ACL."
::= { capwapBaseMacAclEntry 1 } ::= { capwapBaseMacAclEntry 1 }
capwapBaseMacAclStationId OBJECT-TYPE capwapBaseMacAclStationId OBJECT-TYPE
SYNTAX CapwapBaseStationIdTC SYNTAX CapwapBaseStationIdTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a station's MAC address which WTPs will no longer "Represents a station's MAC address which WTPs will no longer
provides service to it." provides service to it."
REFERENCE REFERENCE
"Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.6.7. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseMacAclEntry 2 } ::= { capwapBaseMacAclEntry 2 }
capwapBaseMacAclsRowStatus OBJECT-TYPE capwapBaseMacAclRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row "This variable is used to create, modify, and/or delete a row
in this table." in this table."
::= { capwapBaseMacAclEntry 3 } ::= { capwapBaseMacAclEntry 3 }
-- End of capwapBaseMacAclTable table -- End of capwapBaseMacAclTable table
skipping to change at page 23, line 50 skipping to change at page 28, line 14
capwapBaseMacTypeOptions CapwapBaseMacTypeTC, capwapBaseMacTypeOptions CapwapBaseMacTypeTC,
capwapBaseWtpDiscoveryType INTEGER, capwapBaseWtpDiscoveryType INTEGER,
capwapBaseWtpRadiosInUseNum Unsigned32, capwapBaseWtpRadiosInUseNum Unsigned32,
capwapBaseWtpRadioNumLimit Unsigned32, capwapBaseWtpRadioNumLimit Unsigned32,
capwapBaseWtpStaticIpEnable TruthValue, capwapBaseWtpStaticIpEnable TruthValue,
capwapBaseWtpStaticIpType InetAddressType, capwapBaseWtpStaticIpType InetAddressType,
capwapBaseWtpStaticIp InetAddress, capwapBaseWtpStaticIp InetAddress,
capwapBaseWtpNetmask InetAddress, capwapBaseWtpNetmask InetAddress,
capwapBaseWtpGateway InetAddress, capwapBaseWtpGateway InetAddress,
capwapBaseWtpFallbackEnable INTEGER, capwapBaseWtpFallbackEnable INTEGER,
capwapBaseWtpRetransmitCount Unsigned32 capwapBaseWtpRetransmitCount Unsigned32,
capwapBaseWtpMaxDiscoveries Unsigned32,
capwapBaseWtpMaxFailedDTLSSessionRetry Unsigned32,
capwapBaseWtpMaxRetransmitCnt Unsigned32,
capwapBaseWtpDataChannelKeepAliveTimer Unsigned32,
capwapBaseWtpDataChannelDeadInterval Unsigned32,
capwapBaseWtpDiscoveryInterval Unsigned32,
capwapBaseWtpDTLSSessionDeleteTimer Unsigned32,
capwapBaseWtpEchoInterval Unsigned32,
capwapBaseWtpIdleTimeout Unsigned32,
capwapBaseWtpImageDataStartTimer Unsigned32,
capwapBaseWtpMaxDiscoveryInterval Unsigned32,
capwapBaseWtpReportInterval Unsigned32,
capwapBaseWtpRetransmitInterval Unsigned32,
capwapBaseWtpSilentInterval Unsigned32,
capwapBaseWtpStatisticsTimer Unsigned32,
capwapBaseWtpWaitDTLSTimer Unsigned32
} }
capwapBaseWtpCurrId OBJECT-TYPE capwapBaseWtpCurrId OBJECT-TYPE
SYNTAX CapwapBaseWtpIdTC SYNTAX CapwapBaseWtpIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the unique identifier of a WTP Which is "Represents the unique identifier of a WTP Which is
in running state." in running state."
::= { capwapBaseWtpEntry 1 } ::= { capwapBaseWtpEntry 1 }
skipping to change at page 28, line 20 skipping to change at page 32, line 47
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the number of retransmissions for a given "Represents the number of retransmissions for a given
CAPWAP packet." CAPWAP packet."
REFERENCE REFERENCE
"Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.8. of CAPWAP Protocol Specification, RFC xxx."
::= { capwapBaseWtpEntry 17 } ::= { capwapBaseWtpEntry 17 }
capwapBaseWtpMaxDiscoveries OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represent the maximum number of Discovery Request messages
that will be sent after a WTP boots."
REFERENCE
"Section 4.8.5. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 10 }
::= { capwapBaseWtpEntry 18 }
capwapBaseWtpMaxFailedDTLSSessionRetry OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represent the maximum number of failed DTLS session
establishment attempts before the CAPWAP device enters a
silent period."
REFERENCE
"Section 4.8.6. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 3 }
::= { capwapBaseWtpEntry 19 }
capwapBaseWtpMaxRetransmitCnt OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represent the maximum number of retransmission for a given
CAPWAP packet before the link layer considers the peer dead."
REFERENCE
"Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 }
::= { capwapBaseWtpEntry 20 }
capwapBaseWtpDataChannelKeepAliveTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the the next opportunity, in seconds, the WTP must
transmit the Data Channel KeepAlive message."
REFERENCE
"Section 4.7.2. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseWtpEntry 21 }
capwapBaseWtpDataChannelDeadInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait
without having received a Data Channel Keep Alive packet
before the destination for the Data Channel Keep Alive
packets may be considered dead."
REFERENCE
"Section 4.7.3. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 }
::= { capwapBaseWtpEntry 22 }
capwapBaseWtpDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, that a WTP MUST
wait after receiving a Discovery Response message, before
initiating a DTLS handshake."
REFERENCE
"Section 4.7.5. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 }
::= { capwapBaseWtpEntry 23 }
capwapBaseWtpDTLSSessionDeleteTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait
for DTLS session deletion."
REFERENCE
"Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 }
::= { capwapBaseWtpEntry 24 }
capwapBaseWtpEchoInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo
Request messages to the AC with which the WTP has joined."
REFERENCE
"Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseWtpEntry 25 }
capwapBaseWtpIdleTimeout OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the idle timeout value that the WTP SHOULD enforce
for its active stations."
REFERENCE
"Section 4.7.8. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 300 }
::= { capwapBaseWtpEntry 26 }
capwapBaseWtpImageDataStartTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the number of seconds the WTP will wait for its peer
to transmit the Image Data Request."
REFERENCE
"Section 4.7.9. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseWtpEntry 27 }
capwapBaseWtpMaxDiscoveryInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time allowed between sending Discovery
Request messages, in seconds. This value MUST be no less than
2 seconds and no greater than 180 seconds."
REFERENCE
"Section 4.7.10. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 20 }
::= { capwapBaseWtpEntry 28 }
capwapBaseWtpReportInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the interval for WTP to send Decryption Error
report."
REFERENCE
"Section 4.7.11. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 120 }
::= { capwapBaseWtpEntry 29 }
capwapBaseWtpRetransmitInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, in which a
non-acknowledged CAPWAP packet will be retransmitted."
REFERENCE
"Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 3 }
::= { capwapBaseWtpEntry 30 }
capwapBaseWtpSilentInterval OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the minimum time, in seconds, a WTP MUST wait
before it MAY again send Discovery Request messages or attempt
to a establish DTLS session."
REFERENCE
"Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseWtpEntry 31 }
capwapBaseWtpStatisticsTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the interval the WTP uses between the WTP Events
Requests it transmits to the AC to communicate its statistics,
in seconds."
REFERENCE
"Section 4.7.14. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 120 }
::= { capwapBaseWtpEntry 32 }
capwapBaseWtpWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "second"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the maximum time, in seconds, an AC MUST wait
without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds."
REFERENCE
"Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 }
::= { capwapBaseWtpEntry 33 }
-- End of capwapBaseWtpTable table -- End of capwapBaseWtpTable table
-- capwapBaseRadioBindTable Table -- capwapBaseRadioBindTable Table
capwapBaseRadioBindTable OBJECT-TYPE capwapBaseRadioBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry SYNTAX SEQUENCE OF CapwapBaseRadioBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display the mapping relationship "A table of objects that display the mapping relationship
skipping to change at page 38, line 22 skipping to change at page 47, line 19
::= { capwapBaseRadioStatsEntry 11 } ::= { capwapBaseRadioStatsEntry 11 }
-- End of capwapBaseRadioStatsTable table -- End of capwapBaseRadioStatsTable table
-- End of WTP Objects Group -- End of WTP Objects Group
-- CAPWAP Base Parameters Group -- CAPWAP Base Parameters Group
capwapBaseParameters OBJECT IDENTIFIER capwapBaseParameters OBJECT IDENTIFIER
::= { capwapBaseObjects 3 } ::= { capwapBaseObjects 3 }
capwapBaseMaxRetransmitNum OBJECT-TYPE capwapBaseAcMaxRetransmitCnt OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represent the maximum number of retransmission for a given "Represent the maximum number of retransmission for a given
CAPWAP packet before the link layer considers the peer dead." CAPWAP packet before the link layer considers the peer dead."
REFERENCE REFERENCE
"Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.8.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 }
::= { capwapBaseParameters 1 } ::= { capwapBaseParameters 1 }
capwapBaseChangeStatePendingTimer OBJECT-TYPE capwapBaseAcChangeStatePendingTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, the AC will wait "Represents the maximum time, in seconds, the AC will wait
for the Change State Event Request from the WTP after having for the Change State Event Request from the WTP after having
transmitted a successful Configuration Status Response transmitted a successful Configuration Status Response
message." message."
REFERENCE REFERENCE
"Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.1. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 25 }
::= { capwapBaseParameters 2 } ::= { capwapBaseParameters 2 }
capwapBaseDataCheckTimer OBJECT-TYPE capwapBaseAcDataCheckTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents The number of seconds the AC will wait for "Represents The number of seconds the AC will wait for
the Data Channel Keep Alive, which is required by the the Data Channel Keep Alive, which is required by the
CAPWAP state machine's Data Check state. CAPWAP state machine's Data Check state.
The AC resets the state machine if this timer expires The AC resets the state machine if this timer expires
prior to transitioning to the next state." prior to transitioning to the next state."
REFERENCE REFERENCE
"Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.4. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseParameters 3 } ::= { capwapBaseParameters 3 }
capwapBaseMinDTLSSessionDeleteTimer OBJECT-TYPE capwapBaseAcDTLSSessionDeleteTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, an AC MUST wait "Represents the minimum time, in seconds, an AC MUST wait
for DTLS session deletion." for DTLS session deletion."
REFERENCE REFERENCE
"Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.6. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 5 }
::= { capwapBaseParameters 4 } ::= { capwapBaseParameters 4 }
capwapBaseEchoInterval OBJECT-TYPE capwapBaseAcEchoInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, between sending Echo "Represents the minimum time, in seconds, between sending Echo
Request messages to the AC with which the WTP has joined." Request messages to the AC with which the WTP has joined."
REFERENCE REFERENCE
"Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.7. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseParameters 5 } ::= { capwapBaseParameters 5 }
capwapBaseRetransmitInterval OBJECT-TYPE capwapBaseAcRetransmitInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, in which a "Represents the minimum time, in seconds, in which a
non-acknowledged CAPWAP packet will be retransmitted." non-acknowledged CAPWAP packet will be retransmitted."
REFERENCE REFERENCE
"Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.12. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 3 }
::= { capwapBaseParameters 6 } ::= { capwapBaseParameters 6 }
capwapBaseSilentInterval OBJECT-TYPE capwapBaseAcSilentInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the minimum time, in seconds, during which the AC "Represents the minimum time, in seconds, during which the AC
SHOULD ignore all CAPWAP and DTLS packets received from the SHOULD ignore all CAPWAP and DTLS packets received from the
WTP that is in the Sulking state." WTP that is in the Sulking state."
REFERENCE REFERENCE
"Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.13. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 30 }
::= { capwapBaseParameters 7 } ::= { capwapBaseParameters 7 }
capwapBaseWaitDTLSTimer OBJECT-TYPE capwapBaseAcWaitDTLSTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, an AC MUST wait "Represents the maximum time, in seconds, an AC MUST wait
without having received a DTLS Handshake message from an AC. without having received a DTLS Handshake message from an AC.
This timer MUST be greater than 30 seconds." This timer MUST be greater than 30 seconds."
REFERENCE REFERENCE
"Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.15. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 }
::= { capwapBaseParameters 8 } ::= { capwapBaseParameters 8 }
capwapBaseWaitJoinTimer OBJECT-TYPE capwapBaseAcWaitJoinTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "second" UNITS "second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the maximum time, in seconds, an AC will wait after "Represents the maximum time, in seconds, an AC will wait after
the DTLS session has been established until it receives the the DTLS session has been established until it receives the
Join Request from the WTP. This timer MUST be greater than 20 Join Request from the WTP. This timer MUST be greater than 20
seconds." seconds."
REFERENCE REFERENCE
"Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx." "Section 4.7.16. of CAPWAP Protocol Specification, RFC xxx."
DEFVAL { 60 }
::= { capwapBaseParameters 9 } ::= { capwapBaseParameters 9 }
-- End of CAPWAP Base Parameters Group -- End of CAPWAP Base Parameters Group
-- CAPWAP Statistics Group -- CAPWAP Statistics Group
capwapBaseStats OBJECT IDENTIFIER capwapBaseStats OBJECT IDENTIFIER
::= { capwapBaseObjects 4 } ::= { capwapBaseObjects 4 }
capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE capwapBaseFailedDTLSAuthFailCount OBJECT-TYPE
skipping to change at page 49, line 43 skipping to change at page 59, line 4
SYNTAX INTEGER { reserved0(0), reserved2(2) } SYNTAX INTEGER { reserved0(0), reserved2(2) }
DESCRIPTION DESCRIPTION
"A value other than reserved0(0), reserved2(2) need not be "A value other than reserved0(0), reserved2(2) need not be
supported if there is no wireless binding defined for supported if there is no wireless binding defined for
technologies used." technologies used."
::= { capwapBaseCompliances 1 } ::= { capwapBaseCompliances 1 }
capwapBaseAcNodeGroup OBJECT-GROUP capwapBaseAcNodeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpSessions, capwapBaseWtpSessions,
capwapBaseMaxWtpSessionsConfig, capwapBaseWtpSessionsLimit,
capwapBaseStationSessions, capwapBaseStationSessions,
capwapBaseMaxStationSessionsConfig capwapBaseStationSessionsLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
basic properties for AC from CAPWAP protocol perspective." basic properties for AC from CAPWAP protocol perspective."
::= { capwapBaseGroups 1 } ::= { capwapBaseGroups 1 }
capwapBaseAcNodeGroup2 OBJECT-GROUP capwapBaseAcNodeGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseDataChannelSecOptions, capwapBaseDataChannelSecOptions,
skipping to change at page 50, line 34 skipping to change at page 59, line 43
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "The collection of objects which are used to configure
AC name list." AC name list."
::= { capwapBaseGroups 3 } ::= { capwapBaseGroups 3 }
capwapBaseMacAclsGroup OBJECT-GROUP capwapBaseMacAclsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseMacAclStationId, capwapBaseMacAclStationId,
capwapBaseMacAclsRowStatus capwapBaseMacAclRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to configure "The collection of objects which are used to configure
stations ACL." stations ACL."
::= { capwapBaseGroups 4 } ::= { capwapBaseGroups 4 }
capwapBaseWtpStateGroup OBJECT-GROUP capwapBaseWtpStateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpIpAddressType, capwapBaseWtpIpAddressType,
skipping to change at page 51, line 33 skipping to change at page 60, line 43
capwapBaseWtpsGroup2 OBJECT-GROUP capwapBaseWtpsGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseWtpPhyIndex, capwapBaseWtpPhyIndex,
capwapBaseWtpDiscoveryType, capwapBaseWtpDiscoveryType,
capwapBaseWtpStaticIpEnable, capwapBaseWtpStaticIpEnable,
capwapBaseWtpStaticIpType, capwapBaseWtpStaticIpType,
capwapBaseWtpStaticIp, capwapBaseWtpStaticIp,
capwapBaseWtpNetmask, capwapBaseWtpNetmask,
capwapBaseWtpGateway, capwapBaseWtpGateway,
capwapBaseWtpFallbackEnable, capwapBaseWtpFallbackEnable,
capwapBaseWtpRetransmitCount capwapBaseWtpRetransmitCount,
capwapBaseWtpMaxDiscoveries,
capwapBaseWtpMaxFailedDTLSSessionRetry,
capwapBaseWtpMaxRetransmitCnt,
capwapBaseWtpDataChannelKeepAliveTimer,
capwapBaseWtpDataChannelDeadInterval,
capwapBaseWtpDiscoveryInterval,
capwapBaseWtpDTLSSessionDeleteTimer,
capwapBaseWtpEchoInterval,
capwapBaseWtpIdleTimeout,
capwapBaseWtpImageDataStartTimer,
capwapBaseWtpMaxDiscoveryInterval,
capwapBaseWtpReportInterval,
capwapBaseWtpRetransmitInterval,
capwapBaseWtpSilentInterval,
capwapBaseWtpStatisticsTimer,
capwapBaseWtpWaitDTLSTimer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects which are used to represent
configuration and properties information for WTP configuration and properties information for WTP
in running state." in running state."
::= { capwapBaseGroups 7 } ::= { capwapBaseGroups 7 }
capwapBaseRadiosGroup OBJECT-GROUP capwapBaseRadiosGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 53, line 10 skipping to change at page 62, line 36
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used for collecting "The collection of objects which are used for collecting
radio reset count, channel change count, hardware failure radio reset count, channel change count, hardware failure
count and so on" count and so on"
::= { capwapBaseGroups 11 } ::= { capwapBaseGroups 11 }
capwapBaseParametersGroup OBJECT-GROUP capwapBaseParametersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseMaxRetransmitNum, capwapBaseAcMaxRetransmitCnt,
capwapBaseChangeStatePendingTimer, capwapBaseAcChangeStatePendingTimer,
capwapBaseDataCheckTimer, capwapBaseAcDataCheckTimer,
capwapBaseMinDTLSSessionDeleteTimer, capwapBaseAcDTLSSessionDeleteTimer,
capwapBaseEchoInterval, capwapBaseAcEchoInterval,
capwapBaseRetransmitInterval, capwapBaseAcRetransmitInterval,
capwapBaseSilentInterval, capwapBaseAcSilentInterval,
capwapBaseWaitDTLSTimer, capwapBaseAcWaitDTLSTimer,
capwapBaseWaitJoinTimer capwapBaseAcWaitJoinTimer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for CAPWAP protocol." "Objects used for CAPWAP protocol."
::= { capwapBaseGroups 12 } ::= { capwapBaseGroups 12 }
capwapBaseStatsGroup OBJECT-GROUP capwapBaseStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
capwapBaseFailedDTLSAuthFailCount, capwapBaseFailedDTLSAuthFailCount,
capwapBaseFailedDTLSSessionCount capwapBaseFailedDTLSSessionCount
skipping to change at page 54, line 26 skipping to change at page 64, line 5
capwapBaseNtfConfigMsgErrorType, capwapBaseNtfConfigMsgErrorType,
capwapBaseNtfMsgErrorElements capwapBaseNtfMsgErrorElements
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used for notification." "Objects used for notification."
::= { capwapBaseGroups 15 } ::= { capwapBaseGroups 15 }
END END
10. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. The followings are the tables and objects and network operations. The followings are the tables and objects and
their sensitivity/vulnerability: their sensitivity/vulnerability:
o - Unauthorized changes to the capwapBaseWtpTable, writable objects - Unauthorized changes to the capwapBaseWtpTable, writable objects
under capwapBaseAcs group may disrupt allocation of resources in under capwapBaseAcs group may disrupt allocation of resources in the
the network. network. For example, a WTP's static Ip address could be changed by
set capwapBaseWtpStaticIp object.
- Unauthorized changes to writable objects under the capwapBaseAc
group, it may disrupt allocation of resources in the network. For
example, a invalid value for capwapBaseWtpSessionsLimit object will
increase AC's traffic burden. Also, some objects such as
capwapBaseDataChannelSecConfig may cause network unsafe.
- Unauthorized changes to the capwapBaseMacAclTable, it may cause
legal stations could not access network any more while illegal
stations have chance to access network.
- Unauthorized changes to writable objects under the
capwapBaseParameters group, it may influence CAPWAP protocol
behaviour and status. For example, the invalid value for
capwapBaseAcDataCheckTimer may influence CAPWAP state machine.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. The followings are the tables and objects and the network via SNMP. The followings are the tables and objects and
their sensitivity/vulnerability: their sensitivity/vulnerability:
o - The capwapBaseWtpTable exposes WTP's important information like - The capwapBaseDataChannelSecOptions and
IP address, MAC type and so on; capwapBaseControlChannelAuthenOptions under the capwapBaseAc group
o - The capwapBaseWtpRebootStatTable exposes WTP's failure exposes the current security option for CAPWAP data and control
information; channel.
o - The capwapBaseRadioStatsTable exposes radio's failure - The capwapBaseWtpTable exposes WTP's important information like IP
information; address, MAC type and so on.
- The capwapBaseWtpRebootStatTable exposes WTP's failure information.
- The capwapBaseRadioStatsTable exposes radio's failure information.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations 12. IANA Considerations
11.1. IANA Considerations for CAPWAP-BASE-MIB 12.1. IANA Considerations for CAPWAP-BASE-MIB
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
capwapBaseMIB { mib-2 XXX } capwapBaseMIB { mib-2 XXX }
11.2. IANA Considerations for ifType 12.2. IANA Considerations for ifType
Require IANA to assign a ifType for 'WTP Virtual Radio Interface' Require IANA to assign a ifType for 'WTP Virtual Radio Interface'
type. type.
12. Contributors 13. Contributors
This MIB is based on contributions from Long Gao. This MIB is based on contributions from Long Gao.
13. Acknowledgements 14. Acknowledgements
The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin The authors wish to thank David Harrington, Yu Liu, Xi Yao, Sachin
Dutta, Ju Wang, Yujin Zhao, Haitao Zhang. Dutta, Ju Wang, Yujin Zhao, Haitao Zhang.
14. References 15. References
14.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for [RFC2119] Bradner, S., "Key words for
use in RFCs to Indicate use in RFCs to Indicate
Requirement Levels", Requirement Levels",
BCP 14, RFC 2119, BCP 14, RFC 2119,
March 1997. March 1997.
[RFC2578] McCloghrie, K., Ed., [RFC2578] McCloghrie, K., Ed.,
Perkins, D., Ed., and J. Perkins, D., Ed., and J.
Schoenwaelder, Ed., Schoenwaelder, Ed.,
skipping to change at page 57, line 24 skipping to change at page 67, line 17
(Version 3)", RFC 4133, (Version 3)", RFC 4133,
August 2005. August 2005.
[I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley, [I-D.ietf-capwap-protocol-specification] Montemurro, M., Stanley,
D., and P. Calhoun, "CAPWAP D., and P. Calhoun, "CAPWAP
Protocol Specification", dr Protocol Specification", dr
aft-ietf-capwap-protocol- aft-ietf-capwap-protocol-
specification-14 (work in specification-14 (work in
progress), October 2008. progress), October 2008.
14.2. Informative References 15.2. Informative References
[RFC3410] Case, J., Mundy, R., [RFC3410] Case, J., Mundy, R.,
Partain, D., and B. Partain, D., and B.
Stewart, "Introduction and Stewart, "Introduction and
Applicability Statements Applicability Statements
for Internet-Standard for Internet-Standard
Management Framework", Management Framework",
RFC 3410, December 2002. RFC 3410, December 2002.
Appendix A. Appendix A. Changes from -02
1) Section 9 is added to describe CAPWAP Message Element Extension
2) In the Section 10, the MIB objects (such as
capwapBaseWtpSilentInterval) are added into capwapBaseWtpTable and
capwapBaseParameters to manage CAPWAP protocol timers and variables.
Rename object capwapBaseMaxStationSessionsConfig as
capwapBaseStationSessionsLimit and capwapBaseMaxWtpSessionsConfig as
capwapBaseWtpSessionsLimit.
3) Section 11 is updated for capwapBaseParameters group, capwapBaseAc
group and capwapBaseMacAclTable to describe the security
considerations for them.
4) Appendix is added to log the changes happened between versions.
Authors' Addresses Authors' Addresses
Yang Shi (editor) Yang Shi (editor)
H3C Tech. Co., Ltd H3C Tech. Co., Ltd
Digital Technology Plaza, NO.9 Shangdi 9th Street,Haidian District, 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
 End of changes. 52 change blocks. 
65 lines changed or deleted 535 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/