smilint output for ./CAPWAP-DOT11-MIB
Message Severities |
Severity | Count |
warning | 8 |
fyi | 5 |
Message Types |
Type | Count |
identifier-case-match (warning) | 3 |
identifier-external-case-match (warning) | 2 |
previous-definition (fyi) | 5 |
type-without-format (warning) | 3 |
Messages:
/home/fenner/mibindex/latest2/CAPWAP-MIB
1: -- extracted from draft-yangshi-capwap-base-mib-00.txt
2: -- at Tue Aug 7 06:08:54 2007
67: CapwapRadioId ::= TEXTUAL-CONVENTION
68: STATUS current
69: DESCRIPTION
70: "Represents a unique identifier of a radio on a WTP."
71: SYNTAX Unsigned32 (1..4294967295)
72:
73: CapwapWTPTunnelMode ::= TEXTUAL-CONVENTION
73: fyi -
info: previous definition of `CapwapWTPTunnelMode'
74: STATUS current
75: DESCRIPTION
...
86:
87: CapwapWTPMACType ::= TEXTUAL-CONVENTION
87: fyi -
info: previous definition of `CapwapWTPMACType'
88: STATUS current
89: DESCRIPTION
90: "Represents the MAC mode of operation supported by the WTP.
91: The possible value could be:
92: localMAC(1) - Local-MAC Mode,
93: splitMAC(2) - Split-MAC Mode."
CAPWAP-DOT11-MIB
1: -- extracted from draft-yangshi-capwap-802dot11-mib-00.txt
2: -- at Tue Aug 7 06:08:54 2007
53:
54: CapwapDot11WLANTemplateIfIndex ::= TEXTUAL-CONVENTION
54: fyi -
info: previous definition of `CapwapDot11WLANTemplateIfIndex'
54: warning -
warning: type `CapwapDot11WLANTemplateIfIndex' has no format specification
55: STATUS current
56: DESCRIPTION
57: "Represents the TC for a ifindex of 'WLAN Tempalte Interface'
58: logical interface type."
59: SYNTAX Integer32 (1..2147483647)
60:
61: CapwapDot11WLANBSSIfIndex ::= TEXTUAL-CONVENTION
61: fyi -
info: previous definition of `CapwapDot11WLANBSSIfIndex'
61: warning -
warning: type `CapwapDot11WLANBSSIfIndex' has no format specification
62: STATUS current
63: DESCRIPTION
64: "Represents the TC for a ifindex of 'WLAN BSS Interface'
65: logical interface type."
66: SYNTAX Unsigned32
67:
68: CapwapDot11WLANId ::= TEXTUAL-CONVENTION
68: fyi -
info: previous definition of `CapwapDot11WLANId'
68: warning -
warning: type `CapwapDot11WLANId' has no format specification
69: STATUS current
70: DESCRIPTION
71: "Represents the TC for WLAN Id."
72: SYNTAX Unsigned32
73:
74:
75: -- Top level components of this MIB
...
112:
113: capwapDot11WLANTemplateIfIndex OBJECT-TYPE
113: warning -
warning: identifier `capwapDot11WLANTemplateIfIndex' differs from `CapwapDot11WLANTemplateIfIndex' only in case
114: SYNTAX CapwapDot11WLANTemplateIfIndex
115: MAX-ACCESS not-accessible
116: STATUS current
117: DESCRIPTION
118: "Represents the ifindex for a interface of 'WLAN Template
119: interface' interface type.
120: Before WTPs connect to AC and get configuration, administrator
121: will prepare configuration for them. For WLAN related
122: configuration, administrator could create a logical interface
123: of 'WLAN Template interface' interface type, and
124: configure WLAN parameter under it.
125: For example, according to CAPWAP Binding for IEEE 802.11
126: '6.1. IEEE 802.11 Add WLAN', administrator could configure
127: specify Auth Type for a WLAN.
128: The 'WLAN Template interface' provides a way to
129: uniquely identify each WLAN by logical at AC side.
130: As most MIBs use ifindex to identify a interface for
131: configuration and statistic data, for example,
132: dot11AuthenticationAlgorithmsTable in 802.11 MIB use ifindex
133: as index, and dot11AuthenticationAlgorithm object is for
134: Auth Type mentioned in the CAPWAP '6.1. IEEE 802.11 Add WLAN',
135: With the way of 'WLAN Template interface', it will easily
136: reuse MIB table like dot11AuthenticationAlgorithmsTable, while
137: only care for other configurations like capwapWTPTunnelMode."
138: ::= { capwapDot11WLANConfigEntry 1 }
139:
140: capwapDot11WLANId OBJECT-TYPE
140: warning -
warning: identifier `capwapDot11WLANId' differs from `CapwapDot11WLANId' only in case
141: SYNTAX CapwapDot11WLANId
142: MAX-ACCESS read-create
143: STATUS current
144: DESCRIPTION
145: "Represents the WLAN id for a WLAN which has a
146: capwapDot11WLANTemplateIfIndex interface corresponding to it."
147: REFERENCE
148: "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
149: RFC xxx."
150: ::= { capwapDot11WLANConfigEntry 2 }
151:
152: capwapWTPMACType OBJECT-TYPE
152: warning -
warning: identifier `capwapWTPMACType' differs from `CAPWAP-MIB::CapwapWTPMACType' only in case
153: SYNTAX CapwapWTPMACType
154: MAX-ACCESS read-create
155: STATUS current
156: DESCRIPTION
157: "Represents specifies whether the WTP should run the WLAN in
158: Local or Split MAC modes."
159: REFERENCE
160: "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
161: RFC xxx."
162: ::= { capwapDot11WLANConfigEntry 3 }
163:
164: capwapWTPTunnelMode OBJECT-TYPE
164: warning -
warning: identifier `capwapWTPTunnelMode' differs from `CAPWAP-MIB::CapwapWTPTunnelMode' only in case
165: SYNTAX CapwapWTPTunnelMode
166: MAX-ACCESS read-create
167: STATUS current
168: DESCRIPTION
169: "Represents the frame tunneling type to be used for 802.11 data
170: frames from all stations associated with the WLAN."
171: REFERENCE
172: "Section 6.1. of CAPWAP Protocol Binding for IEEE 802.11,
173: RFC xxx."
174: ::= { capwapDot11WLANConfigEntry 4 }
...
225:
226: capwapDot11WLANBSSIfIndex OBJECT-TYPE
226: warning -
warning: identifier `capwapDot11WLANBSSIfIndex' differs from `CapwapDot11WLANBSSIfIndex' only in case
227: SYNTAX CapwapDot11WLANBSSIfIndex
228: MAX-ACCESS read-create
229: STATUS current
230: DESCRIPTION
231: "Represents a ifIndex for a interface of
232: 'WLAN BSS interface' iftype. Each capwapDot11WLANBSSIfIndex will
233: corresponding to a WLAN service on the PHY radio which is
234: identified by ifIndex.
235:
236: When CapwapWTPMACType is localMAC(1), the interface of
237: 'WLAN BSS interface' will be created at AP side.
238: The AP will use interface for local data forwarding.
239: When CapwapWTPMACType is splitMAC(2), the interface of
240: 'WLAN BSS interface' will be created at AC side.
241: The AC will use it for split data forwarding.
242:
243: The PHY address for capwapDot11WLANBSSIfIndex is BSSID.
244: While manufacturers are free to assign BSSIDs using any
245: arbitrary mechanism, it is advised that where possible the
246: BSSIDs are assigned as a contiguous block.
247: When assigned as a block, implementations can still assign
248: any of the available BSSIDs to any WLAN. One possible method
249: is for the WTP to assign the address using the following
250: algorithm: base BSSID address + WLAN ID."
251: REFERENCE
252: "Section 2.4. of CAPWAP Protocol Binding for IEEE 802.11,
253: RFC xxx."
254: ::= { capwapDot11WLANBSSEntry 1 }