7 Network Working Group D. Nelson
8 Request for Comments: 4669 Enterasys Networks
9 Obsoletes: 2619 August 2006
10 Category: Standards Track
13 RADIUS Authentication Server MIB for IPv6
17 This document specifies an Internet standards track protocol for the
18 Internet community, and requests discussion and suggestions for
19 improvements. Please refer to the current edition of the "Internet
20 Official Protocol Standards" (STD 1) for the standardization state
21 and status of this protocol. Distribution of this memo is unlimited.
25 Copyright (C) The Internet Society (2006).
29 This memo defines a set of extensions that instrument RADIUS
30 authentication server functions. These extensions represent a
31 portion of the Management Information Base (MIB) for use with network
32 management protocols in the Internet community. Using these
33 extensions, IP-based management stations can manage RADIUS
34 authentication servers.
36 This memo obsoletes RFC 2619 by deprecating the MIB table containing
37 IPv4-only address formats and defining a new table to add support for
38 version-neutral IP address formats. The remaining MIB objects from
39 RFC 2619 are carried forward into this document. This memo also adds
40 UNITS and REFERENCE clauses to selected objects.
58 Nelson Standards Track [Page 1]
60 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
65 1. Introduction ....................................................3
66 2. Terminology .....................................................3
67 3. The Internet-Standard Management Framework ......................3
68 4. Scope of Changes ................................................3
69 5. Structure of the MIB Module .....................................4
70 6. Deprecated Objects ..............................................5
71 7. Definitions .....................................................5
72 8. Security Considerations ........................................21
73 9. References .....................................................23
74 9.1. Normative References ......................................23
75 9.2. Informative References ....................................23
76 Appendix A. Acknowledgements ......................................24
114 Nelson Standards Track [Page 2]
116 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
121 This memo defines a portion of the Management Information Base (MIB)
122 for use with network management protocols in the Internet community.
123 The objects defined within this memo relate to the Remote
124 Authentication Dial-In User Service (RADIUS) Authentication Server as
125 defined in RFC 2865 [RFC2865].
129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
131 document are to be interpreted as described in RFC 2119 [RFC2119].
133 This document uses terminology from RFC 2865 [RFC2865].
135 This document uses the word "malformed" with respect to RADIUS
136 packets, particularly in the context of counters of "malformed
137 packets". While RFC 2865 does not provide an explicit definition of
138 "malformed", malformed generally means that the implementation has
139 determined the packet does not match the format defined in RFC 2865.
140 Some implementations may determine that packets are malformed when
141 the Vendor Specific Attribute (VSA) format does not follow the RFC
142 2865 recommendations for VSAs. Those implementations are used in
143 deployments today, and thus set the de facto definition of
146 3. The Internet-Standard Management Framework
148 For a detailed overview of the documents that describe the current
149 Internet-Standard Management Framework, please refer to section 7 of
152 Managed objects are accessed via a virtual information store, termed
153 the Management Information Base or MIB. MIB objects are generally
154 accessed through the Simple Network Management Protocol (SNMP).
155 Objects in the MIB are defined using the mechanisms defined in the
156 Structure of Management Information (SMI). This memo specifies a MIB
157 module that is compliant to the SMIv2, which is described in STD 58,
158 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
163 This document obsoletes RFC 2619 [RFC2619], RADIUS Authentication
164 Server MIB, by deprecating the radiusAuthClientTable table and adding
165 a new table, radiusAuthClientExtTable, containing
166 radiusAuthClientInetAddressType and radiusAuthClientInetAddress. The
170 Nelson Standards Track [Page 3]
172 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
175 purpose of these added MIB objects is to support version-neutral IP
176 addressing formats. The existing table containing
177 radiusAuthClientAddress is deprecated. The remaining MIB objects
178 from RFC 2619 are carried forward into this document. This memo also
179 adds UNITS and REFERENCE clauses to selected objects.
181 RFC 4001 [RFC4001], which defines the SMI Textual Conventions for
182 version-neutral IP addresses, contains the following recommendation.
184 'In particular, when revising a MIB module that contains IPv4
185 specific tables, it is suggested to define new tables using the
186 textual conventions defined in this memo [RFC4001] that support all
187 versions of IP. The status of the new tables SHOULD be "current",
188 whereas the status of the old IP version specific tables SHOULD be
189 changed to "deprecated". The other approach, of having multiple
190 similar tables for different IP versions, is strongly discouraged.'
192 5. Structure of the MIB Module
194 The RADIUS authentication protocol, described in RFC 2865 [RFC2865],
195 distinguishes between the client function and the server function.
196 In RADIUS authentication, clients send Access-Requests, and servers
197 reply with Access-Accepts, Access-Rejects, and Access-Challenges.
198 Typically, NAS devices implement the client function, and thus would
199 be expected to implement the RADIUS authentication client MIB, while
200 RADIUS authentication servers implement the server function, and thus
201 would be expected to implement the RADIUS authentication server MIB.
203 However, it is possible for a RADIUS authentication entity to perform
204 both client and server functions. For example, a RADIUS proxy may
205 act as a server to one or more RADIUS authentication clients, while
206 simultaneously acting as an authentication client to one or more
207 authentication servers. In such situations, it is expected that
208 RADIUS entities combining client and server functionality will
209 support both the client and server MIBs. The server MIB is defined
210 in this document, and the client MIB is defined in [RFC4668].
212 This MIB module contains fourteen scalars as well as a single table,
213 the RADIUS Authentication Client Table, which contains one row for
214 each RADIUS authentication client with which the server shares a
215 secret. Each entry in the RADIUS Authentication Client Table
216 includes thirteen columns presenting a view of the activity of the
217 RADIUS authentication server.
219 This MIB imports from [RFC2578], [RFC2580], [RFC3411], and [RFC4001].
226 Nelson Standards Track [Page 4]
228 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
231 6. Deprecated Objects
233 The deprecated table in this MIB is carried forward from RFC 2619
234 [RFC2619]. There are two conditions under which it MAY be desirable
235 for managed entities to continue to support the deprecated table:
237 1. The managed entity only supports IPv4 address formats.
239 2. The managed entity supports both IPv4 and IPv6 address formats,
240 and the deprecated table is supported for backwards compatibility
241 with older management stations. This option SHOULD only be used
242 when the IP addresses in the new table are in IPv4 format and can
243 accurately be represented in both the new table and the
246 Managed entities SHOULD NOT instantiate row entries in the deprecated
247 table, containing IPv4-only address objects, when the RADIUS client
248 address represented in such a table row is not an IPv4 address.
249 Managed entities SHOULD NOT return inaccurate values of IP address or
250 SNMP object access errors for IPv4-only address objects in otherwise
251 populated tables. When row entries exist in both the deprecated
252 IPv4-only table and the new IP-version-neutral table that describe
253 the same RADIUS client, the row indexes SHOULD be the same for the
254 corresponding rows in each table, to facilitate correlation of these
255 related rows by management applications.
259 RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN
262 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
263 Counter32, Integer32,
264 IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
265 SnmpAdminString FROM SNMP-FRAMEWORK-MIB
266 InetAddressType, InetAddress FROM INET-ADDRESS-MIB
267 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
269 radiusAuthServMIB MODULE-IDENTITY
270 LAST-UPDATED "200608210000Z" -- 21 August 2006
271 ORGANIZATION "IETF RADIUS Extensions Working Group."
278 Phone: +1 425 936 6605
282 Nelson Standards Track [Page 5]
284 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
287 EMail: bernarda@microsoft.com"
289 "The MIB module for entities implementing the server
290 side of the Remote Authentication Dial-In User
291 Service (RADIUS) authentication protocol. Copyright
292 (C) The Internet Society (2006). This version of this
293 MIB module is part of RFC 4669; see the RFC itself for
295 REVISION "200608210000Z" -- 21 August 2006
297 "Revised version as published in RFC 4669. This
298 version obsoletes that of RFC 2619 by deprecating the
299 MIB table containing IPv4-only address formats and
300 defining a new table to add support for version-neutral
301 IP address formats. The remaining MIB objects from RFC
302 2619 are carried forward into this version."
303 REVISION "199906110000Z" -- 11 Jun 1999
304 DESCRIPTION "Initial version as published in RFC 2619."
305 ::= { radiusAuthentication 1 }
307 radiusMIB OBJECT-IDENTITY
310 "The OID assigned to RADIUS MIB work by the IANA."
313 radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1}
315 radiusAuthServMIBObjects OBJECT IDENTIFIER
316 ::= { radiusAuthServMIB 1 }
318 radiusAuthServ OBJECT IDENTIFIER
319 ::= { radiusAuthServMIBObjects 1 }
321 radiusAuthServIdent OBJECT-TYPE
322 SYNTAX SnmpAdminString
326 "The implementation identification string for the
327 RADIUS authentication server software in use on the
328 system, for example, 'FNS-2.1'."
329 ::= {radiusAuthServ 1}
331 radiusAuthServUpTime OBJECT-TYPE
338 Nelson Standards Track [Page 6]
340 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
344 "If the server has a persistent state (e.g., a
345 process), this value will be the time elapsed (in
346 hundredths of a second) since the server process
347 was started. For software without persistent state,
348 this value will be zero."
349 ::= {radiusAuthServ 2}
351 radiusAuthServResetTime OBJECT-TYPE
356 "If the server has a persistent state (e.g., a process)
357 and supports a 'reset' operation (e.g., can be told to
358 re-read configuration files), this value will be the
359 time elapsed (in hundredths of a second) since the
360 server was 'reset.' For software that does not
361 have persistence or does not support a 'reset'
362 operation, this value will be zero."
363 ::= {radiusAuthServ 3}
365 radiusAuthServConfigReset OBJECT-TYPE
366 SYNTAX INTEGER { other(1),
370 MAX-ACCESS read-write
373 "Status/action object to reinitialize any persistent
374 server state. When set to reset(2), any persistent
375 server state (such as a process) is reinitialized as
376 if the server had just been started. This value will
377 never be returned by a read operation. When read,
378 one of the following values will be returned:
379 other(1) - server in some unknown state;
380 initializing(3) - server (re)initializing;
381 running(4) - server currently running."
382 ::= {radiusAuthServ 4}
384 radiusAuthServTotalAccessRequests OBJECT-TYPE
390 "The number of packets received on the
394 Nelson Standards Track [Page 7]
396 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
399 authentication port."
400 REFERENCE "RFC 2865 section 4.1"
401 ::= { radiusAuthServ 5}
403 radiusAuthServTotalInvalidRequests OBJECT-TYPE
409 "The number of RADIUS Access-Request packets
410 received from unknown addresses."
411 REFERENCE "RFC 2865 section 4.1"
412 ::= { radiusAuthServ 6 }
414 radiusAuthServTotalDupAccessRequests OBJECT-TYPE
420 "The number of duplicate RADIUS Access-Request
422 REFERENCE "RFC 2865 section 4.1"
423 ::= { radiusAuthServ 7 }
425 radiusAuthServTotalAccessAccepts OBJECT-TYPE
431 "The number of RADIUS Access-Accept packets sent."
432 REFERENCE "RFC 2865 section 4.2"
433 ::= { radiusAuthServ 8 }
435 radiusAuthServTotalAccessRejects OBJECT-TYPE
441 "The number of RADIUS Access-Reject packets sent."
442 REFERENCE "RFC 2865 section 4.3"
443 ::= { radiusAuthServ 9 }
445 radiusAuthServTotalAccessChallenges OBJECT-TYPE
450 Nelson Standards Track [Page 8]
452 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
459 "The number of RADIUS Access-Challenge packets sent."
460 REFERENCE "RFC 2865 section 4.4"
461 ::= { radiusAuthServ 10 }
463 radiusAuthServTotalMalformedAccessRequests OBJECT-TYPE
469 "The number of malformed RADIUS Access-Request
470 packets received. Bad authenticators
471 and unknown types are not included as
472 malformed Access-Requests."
473 REFERENCE "RFC 2865 section 4.1"
474 ::= { radiusAuthServ 11 }
476 radiusAuthServTotalBadAuthenticators OBJECT-TYPE
482 "The number of RADIUS Authentication-Request packets
483 that contained invalid Message Authenticator
484 attributes received."
485 REFERENCE "RFC 2865 section 3"
486 ::= { radiusAuthServ 12 }
488 radiusAuthServTotalPacketsDropped OBJECT-TYPE
494 "The number of incoming packets
495 silently discarded for some reason other
496 than malformed, bad authenticators or
498 REFERENCE "RFC 2865 section 3"
499 ::= { radiusAuthServ 13 }
501 radiusAuthServTotalUnknownTypes OBJECT-TYPE
506 Nelson Standards Track [Page 9]
508 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
515 "The number of RADIUS packets of unknown type that
517 REFERENCE "RFC 2865 section 4"
518 ::= { radiusAuthServ 14 }
521 radiusAuthClientTable OBJECT-TYPE
522 SYNTAX SEQUENCE OF RadiusAuthClientEntry
523 MAX-ACCESS not-accessible
526 "The (conceptual) table listing the RADIUS
527 authentication clients with which the server shares
529 ::= { radiusAuthServ 15 }
532 radiusAuthClientEntry OBJECT-TYPE
533 SYNTAX RadiusAuthClientEntry
534 MAX-ACCESS not-accessible
537 "An entry (conceptual row) representing a RADIUS
538 authentication client with which the server shares a
540 INDEX { radiusAuthClientIndex }
541 ::= { radiusAuthClientTable 1 }
543 RadiusAuthClientEntry ::= SEQUENCE {
544 radiusAuthClientIndex Integer32,
545 radiusAuthClientAddress IpAddress,
546 radiusAuthClientID SnmpAdminString,
547 radiusAuthServAccessRequests Counter32,
548 radiusAuthServDupAccessRequests Counter32,
549 radiusAuthServAccessAccepts Counter32,
550 radiusAuthServAccessRejects Counter32,
551 radiusAuthServAccessChallenges Counter32,
552 radiusAuthServMalformedAccessRequests Counter32,
553 radiusAuthServBadAuthenticators Counter32,
554 radiusAuthServPacketsDropped Counter32,
555 radiusAuthServUnknownTypes Counter32
558 radiusAuthClientIndex OBJECT-TYPE
562 Nelson Standards Track [Page 10]
564 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
567 SYNTAX Integer32 (1..2147483647)
568 MAX-ACCESS not-accessible
571 "A number uniquely identifying each RADIUS
572 authentication client with which this server
574 ::= { radiusAuthClientEntry 1 }
576 radiusAuthClientAddress OBJECT-TYPE
581 "The NAS-IP-Address of the RADIUS authentication client
582 referred to in this table entry."
583 REFERENCE "RFC 2865 section 2"
584 ::= { radiusAuthClientEntry 2 }
586 radiusAuthClientID OBJECT-TYPE
587 SYNTAX SnmpAdminString
591 "The NAS-Identifier of the RADIUS authentication client
592 referred to in this table entry. This is not
593 necessarily the same as sysName in MIB II."
594 REFERENCE "RFC 2865 section 5.32"
595 ::= { radiusAuthClientEntry 3 }
600 -- Responses = AccessAccepts + AccessRejects + AccessChallenges
602 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
603 -- UnknownTypes - PacketsDropped - Responses = Pending
605 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
606 -- UnknownTypes - PacketsDropped = entries logged
608 radiusAuthServAccessRequests OBJECT-TYPE
614 "The number of packets received on the authentication
618 Nelson Standards Track [Page 11]
620 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
623 port from this client."
624 REFERENCE "RFC 2865 section 4.1"
625 ::= { radiusAuthClientEntry 4 }
627 radiusAuthServDupAccessRequests OBJECT-TYPE
633 "The number of duplicate RADIUS Access-Request
634 packets received from this client."
635 REFERENCE "RFC 2865 section 4.1"
636 ::= { radiusAuthClientEntry 5 }
638 radiusAuthServAccessAccepts OBJECT-TYPE
644 "The number of RADIUS Access-Accept packets
645 sent to this client."
646 REFERENCE "RFC 2865 section 4.2"
647 ::= { radiusAuthClientEntry 6 }
649 radiusAuthServAccessRejects OBJECT-TYPE
655 "The number of RADIUS Access-Reject packets
656 sent to this client."
657 REFERENCE "RFC 2865 section 4.3"
658 ::= { radiusAuthClientEntry 7 }
660 radiusAuthServAccessChallenges OBJECT-TYPE
666 "The number of RADIUS Access-Challenge packets
667 sent to this client."
668 REFERENCE "RFC 2865 section 4.4"
669 ::= { radiusAuthClientEntry 8 }
674 Nelson Standards Track [Page 12]
676 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
679 radiusAuthServMalformedAccessRequests OBJECT-TYPE
685 "The number of malformed RADIUS Access-Request
686 packets received from this client.
687 Bad authenticators and unknown types are not included
688 as malformed Access-Requests."
689 REFERENCE "RFC 2865 section 3"
690 ::= { radiusAuthClientEntry 9 }
692 radiusAuthServBadAuthenticators OBJECT-TYPE
698 "The number of RADIUS Authentication-Request packets
699 that contained invalid Message Authenticator
700 attributes received from this client."
701 REFERENCE "RFC 2865 section 3"
702 ::= { radiusAuthClientEntry 10 }
704 radiusAuthServPacketsDropped OBJECT-TYPE
710 "The number of incoming packets from this
711 client silently discarded for some reason other
712 than malformed, bad authenticators or
714 REFERENCE "RFC 2865 section 3"
715 ::= { radiusAuthClientEntry 11 }
717 radiusAuthServUnknownTypes OBJECT-TYPE
723 "The number of RADIUS packets of unknown type that
724 were received from this client."
725 REFERENCE "RFC 2865 section 4"
726 ::= { radiusAuthClientEntry 12 }
730 Nelson Standards Track [Page 13]
732 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
735 -- New MIB objects added in this revision
737 radiusAuthClientExtTable OBJECT-TYPE
738 SYNTAX SEQUENCE OF RadiusAuthClientExtEntry
739 MAX-ACCESS not-accessible
742 "The (conceptual) table listing the RADIUS
743 authentication clients with which the server shares
745 ::= { radiusAuthServ 16 }
747 radiusAuthClientExtEntry OBJECT-TYPE
748 SYNTAX RadiusAuthClientExtEntry
749 MAX-ACCESS not-accessible
752 "An entry (conceptual row) representing a RADIUS
753 authentication client with which the server shares a
755 INDEX { radiusAuthClientExtIndex }
756 ::= { radiusAuthClientExtTable 1 }
758 RadiusAuthClientExtEntry ::= SEQUENCE {
759 radiusAuthClientExtIndex Integer32,
760 radiusAuthClientInetAddressType InetAddressType,
761 radiusAuthClientInetAddress InetAddress,
762 radiusAuthClientExtID SnmpAdminString,
763 radiusAuthServExtAccessRequests Counter32,
764 radiusAuthServExtDupAccessRequests Counter32,
765 radiusAuthServExtAccessAccepts Counter32,
766 radiusAuthServExtAccessRejects Counter32,
767 radiusAuthServExtAccessChallenges Counter32,
768 radiusAuthServExtMalformedAccessRequests Counter32,
769 radiusAuthServExtBadAuthenticators Counter32,
770 radiusAuthServExtPacketsDropped Counter32,
771 radiusAuthServExtUnknownTypes Counter32,
772 radiusAuthServCounterDiscontinuity TimeTicks
775 radiusAuthClientExtIndex OBJECT-TYPE
776 SYNTAX Integer32 (1..2147483647)
777 MAX-ACCESS not-accessible
780 "A number uniquely identifying each RADIUS
781 authentication client with which this server
786 Nelson Standards Track [Page 14]
788 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
791 ::= { radiusAuthClientExtEntry 1 }
793 radiusAuthClientInetAddressType OBJECT-TYPE
794 SYNTAX InetAddressType
798 "The type of address format used for the
799 radiusAuthClientInetAddress object."
800 ::= { radiusAuthClientExtEntry 2 }
802 radiusAuthClientInetAddress OBJECT-TYPE
807 "The IP address of the RADIUS authentication
808 client referred to in this table entry, using
809 the version-neutral IP address format."
810 ::= { radiusAuthClientExtEntry 3 }
813 radiusAuthClientExtID OBJECT-TYPE
814 SYNTAX SnmpAdminString
818 "The NAS-Identifier of the RADIUS authentication client
819 referred to in this table entry. This is not
820 necessarily the same as sysName in MIB II."
821 REFERENCE "RFC 2865 section 5.32"
822 ::= { radiusAuthClientExtEntry 4 }
827 -- Responses = AccessAccepts + AccessRejects + AccessChallenges
829 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
830 -- UnknownTypes - PacketsDropped - Responses = Pending
832 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
833 -- UnknownTypes - PacketsDropped = entries logged
835 radiusAuthServExtAccessRequests OBJECT-TYPE
842 Nelson Standards Track [Page 15]
844 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
849 "The number of packets received on the authentication
850 port from this client. This counter may experience a
851 discontinuity when the RADIUS Server module within the
852 managed entity is reinitialized, as indicated by the
853 current value of radiusAuthServCounterDiscontinuity."
854 REFERENCE "RFC 2865 section 4.1"
855 ::= { radiusAuthClientExtEntry 5 }
857 radiusAuthServExtDupAccessRequests OBJECT-TYPE
863 "The number of duplicate RADIUS Access-Request
864 packets received from this client. This counter may
865 experience a discontinuity when the RADIUS Server
866 module within the managed entity is reinitialized, as
867 indicated by the current value of
868 radiusAuthServCounterDiscontinuity."
869 REFERENCE "RFC 2865 section 4.1"
870 ::= { radiusAuthClientExtEntry 6 }
872 radiusAuthServExtAccessAccepts OBJECT-TYPE
878 "The number of RADIUS Access-Accept packets
879 sent to this client. This counter may experience a
880 discontinuity when the RADIUS Server module within the
881 managed entity is reinitialized, as indicated by the
882 current value of radiusAuthServCounterDiscontinuity."
883 REFERENCE "RFC 2865 section 4.2"
884 ::= { radiusAuthClientExtEntry 7 }
886 radiusAuthServExtAccessRejects OBJECT-TYPE
892 "The number of RADIUS Access-Reject packets
893 sent to this client. This counter may experience a
894 discontinuity when the RADIUS Server module within the
898 Nelson Standards Track [Page 16]
900 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
903 managed entity is reinitialized, as indicated by the
904 current value of radiusAuthServCounterDiscontinuity."
905 REFERENCE "RFC 2865 section 4.3"
906 ::= { radiusAuthClientExtEntry 8 }
908 radiusAuthServExtAccessChallenges OBJECT-TYPE
914 "The number of RADIUS Access-Challenge packets
915 sent to this client. This counter may experience a
916 discontinuity when the RADIUS Server module within the
917 managed entity is reinitialized, as indicated by the
918 current value of radiusAuthServCounterDiscontinuity."
919 REFERENCE "RFC 2865 section 4.4"
920 ::= { radiusAuthClientExtEntry 9 }
922 radiusAuthServExtMalformedAccessRequests OBJECT-TYPE
928 "The number of malformed RADIUS Access-Request
929 packets received from this client. Bad authenticators
930 and unknown types are not included as malformed
931 Access-Requests. This counter may experience a
932 discontinuity when the RADIUS Server module within the
933 managed entity is reinitialized, as indicated by the
934 current value of radiusAuthServCounterDiscontinuity."
935 REFERENCE "RFC 2865 sections 3, 4.1"
936 ::= { radiusAuthClientExtEntry 10 }
938 radiusAuthServExtBadAuthenticators OBJECT-TYPE
944 "The number of RADIUS Authentication-Request packets
945 that contained invalid Message Authenticator
946 attributes received from this client. This counter
947 may experience a discontinuity when the RADIUS Server
948 module within the managed entity is reinitialized, as
949 indicated by the current value of
950 radiusAuthServCounterDiscontinuity."
954 Nelson Standards Track [Page 17]
956 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
959 REFERENCE "RFC 2865 section 3"
960 ::= { radiusAuthClientExtEntry 11 }
962 radiusAuthServExtPacketsDropped OBJECT-TYPE
968 "The number of incoming packets from this client
969 silently discarded for some reason other than
970 malformed, bad authenticators or unknown types.
971 This counter may experience a discontinuity when the
972 RADIUS Server module within the managed entity is
973 reinitialized, as indicated by the current value of
974 radiusAuthServCounterDiscontinuity."
975 REFERENCE "RFC 2865 section 3"
976 ::= { radiusAuthClientExtEntry 12 }
978 radiusAuthServExtUnknownTypes OBJECT-TYPE
984 "The number of RADIUS packets of unknown type that
985 were received from this client. This counter may
986 experience a discontinuity when the RADIUS Server
987 module within the managed entity is reinitialized, as
988 indicated by the current value of
989 radiusAuthServCounterDiscontinuity."
990 REFERENCE "RFC 2865 section 4"
991 ::= { radiusAuthClientExtEntry 13 }
993 radiusAuthServCounterDiscontinuity OBJECT-TYPE
999 "The number of centiseconds since the last
1000 discontinuity in the RADIUS Server counters.
1001 A discontinuity may be the result of a
1002 reinitialization of the RADIUS Server module
1003 within the managed entity."
1004 ::= { radiusAuthClientExtEntry 14 }
1010 Nelson Standards Track [Page 18]
1012 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1015 -- conformance information
1017 radiusAuthServMIBConformance OBJECT IDENTIFIER
1018 ::= { radiusAuthServMIB 2 }
1020 radiusAuthServMIBCompliances OBJECT IDENTIFIER
1021 ::= { radiusAuthServMIBConformance 1 }
1023 radiusAuthServMIBGroups OBJECT IDENTIFIER
1024 ::= { radiusAuthServMIBConformance 2 }
1026 -- compliance statements
1028 radiusAuthServMIBCompliance MODULE-COMPLIANCE
1031 "The compliance statement for authentication
1032 servers implementing the RADIUS Authentication
1033 Server MIB. Implementation of this module is for
1034 IPv4-only entities, or for backwards compatibility
1035 use with entities that support both IPv4 and
1037 MODULE -- this module
1038 MANDATORY-GROUPS { radiusAuthServMIBGroup }
1040 OBJECT radiusAuthServConfigReset
1041 WRITE-SYNTAX INTEGER { reset(2) }
1042 DESCRIPTION "The only SETable value is 'reset' (2)."
1044 ::= { radiusAuthServMIBCompliances 1 }
1047 radiusAuthServMIBExtCompliance MODULE-COMPLIANCE
1050 "The compliance statement for authentication
1051 servers implementing the RADIUS Authentication
1052 Server IPv6 Extensions MIB. Implementation of
1053 this module is for entities that support IPv6,
1054 or support IPv4 and IPv6."
1055 MODULE -- this module
1056 MANDATORY-GROUPS { radiusAuthServExtMIBGroup }
1058 OBJECT radiusAuthServConfigReset
1059 WRITE-SYNTAX INTEGER { reset(2) }
1060 DESCRIPTION "The only SETable value is 'reset' (2)."
1062 OBJECT radiusAuthClientInetAddressType
1066 Nelson Standards Track [Page 19]
1068 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1071 SYNTAX InetAddressType { ipv4(1), ipv6(2) }
1073 "An implementation is only required to support
1074 IPv4 and globally unique IPv6 addresses."
1076 OBJECT radiusAuthClientInetAddress
1077 SYNTAX InetAddress ( SIZE (4|16) )
1079 "An implementation is only required to support
1080 IPv4 and globally unique IPv6 addresses."
1082 ::= { radiusAuthServMIBCompliances 2 }
1085 -- units of conformance
1087 radiusAuthServMIBGroup OBJECT-GROUP
1088 OBJECTS {radiusAuthServIdent,
1089 radiusAuthServUpTime,
1090 radiusAuthServResetTime,
1091 radiusAuthServConfigReset,
1092 radiusAuthServTotalAccessRequests,
1093 radiusAuthServTotalInvalidRequests,
1094 radiusAuthServTotalDupAccessRequests,
1095 radiusAuthServTotalAccessAccepts,
1096 radiusAuthServTotalAccessRejects,
1097 radiusAuthServTotalAccessChallenges,
1098 radiusAuthServTotalMalformedAccessRequests,
1099 radiusAuthServTotalBadAuthenticators,
1100 radiusAuthServTotalPacketsDropped,
1101 radiusAuthServTotalUnknownTypes,
1102 radiusAuthClientAddress,
1104 radiusAuthServAccessRequests,
1105 radiusAuthServDupAccessRequests,
1106 radiusAuthServAccessAccepts,
1107 radiusAuthServAccessRejects,
1108 radiusAuthServAccessChallenges,
1109 radiusAuthServMalformedAccessRequests,
1110 radiusAuthServBadAuthenticators,
1111 radiusAuthServPacketsDropped,
1112 radiusAuthServUnknownTypes
1116 "The collection of objects providing management of
1117 a RADIUS Authentication Server."
1118 ::= { radiusAuthServMIBGroups 1 }
1122 Nelson Standards Track [Page 20]
1124 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1127 radiusAuthServExtMIBGroup OBJECT-GROUP
1128 OBJECTS {radiusAuthServIdent,
1129 radiusAuthServUpTime,
1130 radiusAuthServResetTime,
1131 radiusAuthServConfigReset,
1132 radiusAuthServTotalAccessRequests,
1133 radiusAuthServTotalInvalidRequests,
1134 radiusAuthServTotalDupAccessRequests,
1135 radiusAuthServTotalAccessAccepts,
1136 radiusAuthServTotalAccessRejects,
1137 radiusAuthServTotalAccessChallenges,
1138 radiusAuthServTotalMalformedAccessRequests,
1139 radiusAuthServTotalBadAuthenticators,
1140 radiusAuthServTotalPacketsDropped,
1141 radiusAuthServTotalUnknownTypes,
1142 radiusAuthClientInetAddressType,
1143 radiusAuthClientInetAddress,
1144 radiusAuthClientExtID,
1145 radiusAuthServExtAccessRequests,
1146 radiusAuthServExtDupAccessRequests,
1147 radiusAuthServExtAccessAccepts,
1148 radiusAuthServExtAccessRejects,
1149 radiusAuthServExtAccessChallenges,
1150 radiusAuthServExtMalformedAccessRequests,
1151 radiusAuthServExtBadAuthenticators,
1152 radiusAuthServExtPacketsDropped,
1153 radiusAuthServExtUnknownTypes,
1154 radiusAuthServCounterDiscontinuity
1158 "The collection of objects providing management of
1159 a RADIUS Authentication Server."
1160 ::= { radiusAuthServMIBGroups 2 }
1164 8. Security Considerations
1166 There are a number of management objects defined in this MIB that
1167 have a MAX-ACCESS clause of read-write and/or read-create. Such
1168 objects may be considered sensitive or vulnerable in some network
1169 environments. The support for SET operations in a non-secure
1170 environment without proper protection can have a negative effect on
1171 network operations. These are:
1178 Nelson Standards Track [Page 21]
1180 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1183 radiusAuthServConfigReset
1184 This object can be used to reinitialize the persistent state of
1185 any server. When set to reset(2), any persistent server state
1186 (such as a process) is reinitialized as if the server had just
1187 been started. Depending on the server implementation details,
1188 this action may or may not interrupt the processing of pending
1189 request in the server. Abuse of this object may lead to a Denial
1190 of Service attack on the server.
1192 There are a number of managed objects in this MIB that may contain
1193 sensitive information. These are:
1195 radiusAuthClientIPAddress
1196 This can be used to determine the address of the RADIUS
1197 authentication client with which the server is communicating.
1198 This information could be useful in mounting an attack on the
1199 authentication client.
1201 radiusAuthClientInetAddress
1202 This can be used to determine the address of the RADIUS
1203 authentication client with which the server is communicating.
1204 This information could be useful in mounting an attack on the
1205 authentication client.
1207 It is thus important to control even GET access to these objects and
1208 possibly to even encrypt the values of these object when sending them
1209 over the network via SNMP. Not all versions of SNMP provide features
1210 for such a secure environment.
1212 SNMP versions prior to SNMPv3 do not provide a secure environment.
1213 Even if the network itself is secure (for example by using IPsec),
1214 there is no control as to who on the secure network is allowed to
1215 access and GET/SET (read/change/create/delete) the objects in this
1218 It is RECOMMENDED that implementers consider the security features as
1219 provided by the SNMPv3 framework (see [RFC3410], section 8),
1220 including full support for the SNMPv3 cryptographic mechanisms (for
1221 authentication and privacy).
1223 Further, deployment of SNMP versions prior to SNMPv3 is NOT
1224 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
1225 enable cryptographic security. It is then a customer/operator
1226 responsibility to ensure that the SNMP entity giving access to an
1227 instance of this MIB module is properly configured to give access to
1228 the objects only to those principals (users) that have legitimate
1229 rights to indeed GET or SET (change/create/delete) them.
1234 Nelson Standards Track [Page 22]
1236 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1241 9.1. Normative References
1243 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
1244 Requirement Levels", BCP 14, RFC 2119, March 1997.
1246 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
1247 Schoenwaelder, Ed., "Structure of Management Information
1248 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
1250 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
1251 Schoenwaelder, Ed., "Textual Conventions for SMIv2",
1252 STD 58, RFC 2579, April 1999.
1254 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
1255 "Conformance Statements for SMIv2", STD 58, RFC 2580,
1258 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
1259 "Remote Authentication Dial In User Service (RADIUS)",
1260 RFC 2865, June 2000.
1262 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
1263 Architecture for Describing Simple Network Management
1264 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
1267 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
1268 Schoenwaelder, "Textual Conventions for Internet Network
1269 Addresses", RFC 4001, February 2005.
1271 9.2. Informative References
1273 [RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB",
1274 RFC 2619, June 1999.
1276 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
1277 "Introduction and Applicability Statements for Internet-
1278 Standard Management Framework", RFC 3410, December 2002.
1280 [RFC4668] Nelson, D., "RADIUS Authentication Client MIB for IPv6",
1281 RFC 4668, August 2006.
1290 Nelson Standards Track [Page 23]
1292 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1295 Appendix A. Acknowledgements
1297 The authors of the original MIB are Bernard Aboba and Glen Zorn.
1299 Many thanks to all reviewers, especially to David Harrington, Dan
1300 Romascanu, C.M. Heard, Bruno Pape, Greg Weber, and Bert Wijnen.
1310 EMail: dnelson@enterasys.com
1346 Nelson Standards Track [Page 24]
1348 RFC 4669 RADIUS Auth Server MIB (IPv6) August 2006
1351 Full Copyright Statement
1353 Copyright (C) The Internet Society (2006).
1355 This document is subject to the rights, licenses and restrictions
1356 contained in BCP 78, and except as set forth therein, the authors
1357 retain all their rights.
1359 This document and the information contained herein are provided on an
1360 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1361 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1362 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1363 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1364 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1365 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1367 Intellectual Property
1369 The IETF takes no position regarding the validity or scope of any
1370 Intellectual Property Rights or other rights that might be claimed to
1371 pertain to the implementation or use of the technology described in
1372 this document or the extent to which any license under such rights
1373 might or might not be available; nor does it represent that it has
1374 made any independent effort to identify any such rights. Information
1375 on the procedures with respect to rights in RFC documents can be
1376 found in BCP 78 and BCP 79.
1378 Copies of IPR disclosures made to the IETF Secretariat and any
1379 assurances of licenses to be made available, or the result of an
1380 attempt made to obtain a general license or permission for the use of
1381 such proprietary rights by implementers or users of this
1382 specification can be obtained from the IETF on-line IPR repository at
1383 http://www.ietf.org/ipr.
1385 The IETF invites any interested party to bring to its attention any
1386 copyrights, patents or patent applications, or other proprietary
1387 rights that may cover technology that may be required to implement
1388 this standard. Please address the information to the IETF at
1393 Funding for the RFC Editor function is provided by the IETF
1394 Administrative Support Activity (IASA).
1402 Nelson Standards Track [Page 25]