7 Network Working Group G. Zorn
8 Request for Comments: 2619 B. Aboba
9 Category: Standards Track Microsoft
13 RADIUS Authentication Server MIB
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 (1999). All Rights Reserved.
29 This memo defines a set of extensions which instrument RADIUS
30 authentication server functions. These extensions represent a portion
31 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.
38 This memo defines a portion of the Management Information Base (MIB)
39 for use with network management protocols in the Internet community.
40 In particular, it describes managed objects used for managing RADIUS
41 authentication servers.
43 RADIUS authentication servers are today widely deployed by dialup
44 Internet Service Providers, in order to provide authentication
45 services. As a result, the effective management of RADIUS
46 authentication servers is of considerable importance.
58 Zorn & Aboba Standards Track [Page 1]
60 RFC 2619 RADIUS Authentication Server MIB June 1999
63 2. The SNMP Management Framework
65 The SNMP Management Framework presently consists of five major
68 o An overall architecture, described in RFC 2571 [1].
70 o Mechanisms for describing and naming objects and events for the
71 purpose of management. The first version of this Structure of
72 Management Information (SMI) is called SMIv1 and described in
73 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
74 The second version, called SMIv2, is described in STD 58, RFC
75 2578 [5], RFC 2579 [6] and RFC 2580 [7].
77 o Message protocols for transferring management information. The
78 first version of the SNMP message protocol is called SNMPv1 and
79 described in STD 15, RFC 1157 [8]. A second version of the
80 SNMP message protocol, which is not an Internet standards
81 track protocol, is called SNMPv2c and described in RFC 1901
82 [9] and RFC 1906 [10]. The third version of the message
83 protocol is called SNMPv3 and described in RFC 1906 [10], RFC
84 2572 [11] and RFC 2574 [12].
86 o Protocol operations for accessing management information. The
87 first set of protocol operations and associated PDU formats is
88 described in STD 15, RFC 1157 [8]. A second set of protocol
89 operations and associated PDU formats is described in RFC 1905
92 o A set of fundamental applications described in RFC 2573 [14] and
93 the view-based access control mechanism described in RFC 2575
96 Managed objects are accessed via a virtual information store, termed
97 the Management Information Base or MIB. Objects in the MIB are
98 defined using the mechanisms defined in the SMI.
100 This memo specifies a MIB module that is compliant to the SMIv2. A
101 MIB conforming to the SMIv1 can be produced through the appropriate
102 translations. The resulting translated MIB must be semantically
103 equivalent, except where objects or events are omitted because no
104 translation is possible (use of Counter64). Some machine readable
105 information in SMIv2 will be converted into textual descriptions in
106 SMIv1 during the translation process. However, this loss of machine
107 readable information is not considered to change the semantics of the
114 Zorn & Aboba Standards Track [Page 2]
116 RFC 2619 RADIUS Authentication Server MIB June 1999
121 The RADIUS authentication protocol, described in [16], distinguishes
122 between the client function and the server function. In RADIUS
123 authentication, clients send Access-Requests, and servers reply with
124 Access-Accepts, Access-Rejects, and Access-Challenges. Typically NAS
125 devices implement the client function, and thus would be expected to
126 implement the RADIUS authentication client MIB, while RADIUS
127 authentication servers implement the server function, and thus would
128 be expected to implement the RADIUS authentication server MIB.
130 However, it is possible for a RADIUS authentication entity to perform
131 both client and server functions. For example, a RADIUS proxy may act
132 as a server to one or more RADIUS authentication clients, while
133 simultaneously acting as an authentication client to one or more
134 authentication servers. In such situations, it is expected that
135 RADIUS entities combining client and server functionality will
136 support both the client and server MIBs.
138 3.1. Selected objects
140 This MIB module contains fourteen scalars as well as a single table:
142 (1) the RADIUS Authentication Client Table contains one row for
143 each RADIUS authentication client that the server shares a
146 Each entry in the RADIUS Authentication Client Table includes twelve
147 columns presenting a view of the activity of the RADIUS
148 authentication server.
152 RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN
155 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
156 Counter32, Integer32,
157 IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
158 SnmpAdminString FROM SNMP-FRAMEWORK-MIB
159 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
161 radiusAuthServMIB MODULE-IDENTITY
162 LAST-UPDATED "9906110000Z"
163 ORGANIZATION "IETF RADIUS Working Group."
170 Zorn & Aboba Standards Track [Page 3]
172 RFC 2619 RADIUS Authentication Server MIB June 1999
179 Phone: +1 425 936 6605
180 EMail: bernarda@microsoft.com"
182 "The MIB module for entities implementing the server
183 side of the Remote Access Dialin User Service (RADIUS)
184 authentication protocol."
185 REVISION "9906110000Z" -- 11 Jun 1999
186 DESCRIPTION "Initial version as published in RFC 2619"
187 ::= { radiusAuthentication 1 }
189 radiusMIB OBJECT-IDENTITY
192 "The OID assigned to RADIUS MIB work by the IANA."
195 radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1}
197 radiusAuthServMIBObjects OBJECT IDENTIFIER ::=
198 { radiusAuthServMIB 1 }
200 radiusAuthServ OBJECT IDENTIFIER ::= { radiusAuthServMIBObjects 1 }
202 radiusAuthServIdent OBJECT-TYPE
203 SYNTAX SnmpAdminString
207 "The implementation identification string for the
208 RADIUS authentication server software in use on the
209 system, for example; `FNS-2.1'"
210 ::= {radiusAuthServ 1}
212 radiusAuthServUpTime OBJECT-TYPE
217 "If the server has a persistent state (e.g., a process),
218 this value will be the time elapsed (in hundredths of a
219 seco) since the server process was started.
220 For software without persistent state, this value will
222 ::= {radiusAuthServ 2}
226 Zorn & Aboba Standards Track [Page 4]
228 RFC 2619 RADIUS Authentication Server MIB June 1999
231 radiusAuthServResetTime OBJECT-TYPE
236 "If the server has a persistent state (e.g., a process)
237 and supports a `reset' operation (e.g., can be told to
238 re-read configuration files), this value will be the
239 time elapsed (in hundredths of a second) since the
240 server was `reset.' For software that does not
241 have persistence or does not support a `reset' operation,
242 this value will be zero."
243 ::= {radiusAuthServ 3}
245 radiusAuthServConfigReset OBJECT-TYPE
246 SYNTAX INTEGER { other(1),
250 MAX-ACCESS read-write
253 "Status/action object to reinitialize any persistent
254 server state. When set to reset(2), any persistent
255 server state (such as a process) is reinitialized as if
256 the server had just been started. This value will
257 never be returned by a read operation. When read, one of
258 the following values will be returned:
259 other(1) - server in some unknown state;
260 initializing(3) - server (re)initializing;
261 running(4) - server currently running."
262 ::= {radiusAuthServ 4}
264 -- New Stats proposed by Dale E. Reed Jr (daler@iea-software.com)
266 radiusAuthServTotalAccessRequests OBJECT-TYPE
271 "The number of packets received on the
272 authentication port."
273 ::= { radiusAuthServ 5}
275 radiusAuthServTotalInvalidRequests OBJECT-TYPE
282 Zorn & Aboba Standards Track [Page 5]
284 RFC 2619 RADIUS Authentication Server MIB June 1999
288 "The number of RADIUS Access-Request packets
289 received from unknown addresses."
290 ::= { radiusAuthServ 6 }
292 radiusAuthServTotalDupAccessRequests OBJECT-TYPE
297 "The number of duplicate RADIUS Access-Request
299 ::= { radiusAuthServ 7 }
301 radiusAuthServTotalAccessAccepts OBJECT-TYPE
306 "The number of RADIUS Access-Accept packets sent."
307 ::= { radiusAuthServ 8 }
309 radiusAuthServTotalAccessRejects OBJECT-TYPE
314 "The number of RADIUS Access-Reject packets sent."
315 ::= { radiusAuthServ 9 }
317 radiusAuthServTotalAccessChallenges OBJECT-TYPE
322 "The number of RADIUS Access-Challenge packets sent."
323 ::= { radiusAuthServ 10 }
325 radiusAuthServTotalMalformedAccessRequests OBJECT-TYPE
330 "The number of malformed RADIUS Access-Request
331 packets received. Bad authenticators
332 and unknown types are not included as
333 malformed Access-Requests."
334 ::= { radiusAuthServ 11 }
338 Zorn & Aboba Standards Track [Page 6]
340 RFC 2619 RADIUS Authentication Server MIB June 1999
343 radiusAuthServTotalBadAuthenticators OBJECT-TYPE
348 "The number of RADIUS Authentication-Request packets
349 which contained invalid Signature attributes received."
350 ::= { radiusAuthServ 12 }
352 radiusAuthServTotalPacketsDropped OBJECT-TYPE
357 "The number of incoming packets
358 silently discarded for some reason other
359 than malformed, bad authenticators or
361 ::= { radiusAuthServ 13 }
363 radiusAuthServTotalUnknownTypes OBJECT-TYPE
368 "The number of RADIUS packets of unknown type which
370 ::= { radiusAuthServ 14 }
374 radiusAuthClientTable OBJECT-TYPE
375 SYNTAX SEQUENCE OF RadiusAuthClientEntry
376 MAX-ACCESS not-accessible
379 "The (conceptual) table listing the RADIUS authentication
380 clients with which the server shares a secret."
381 ::= { radiusAuthServ 15 }
383 radiusAuthClientEntry OBJECT-TYPE
384 SYNTAX RadiusAuthClientEntry
385 MAX-ACCESS not-accessible
388 "An entry (conceptual row) representing a RADIUS
389 authentication client with which the server shares a
394 Zorn & Aboba Standards Track [Page 7]
396 RFC 2619 RADIUS Authentication Server MIB June 1999
399 INDEX { radiusAuthClientIndex }
400 ::= { radiusAuthClientTable 1 }
402 RadiusAuthClientEntry ::= SEQUENCE {
403 radiusAuthClientIndex Integer32,
404 radiusAuthClientAddress IpAddress,
405 radiusAuthClientID SnmpAdminString,
406 radiusAuthServAccessRequests Counter32,
407 radiusAuthServDupAccessRequests Counter32,
408 radiusAuthServAccessAccepts Counter32,
409 radiusAuthServAccessRejects Counter32,
410 radiusAuthServAccessChallenges Counter32,
411 radiusAuthServMalformedAccessRequests Counter32,
412 radiusAuthServBadAuthenticators Counter32,
413 radiusAuthServPacketsDropped Counter32,
414 radiusAuthServUnknownTypes Counter32
417 radiusAuthClientIndex OBJECT-TYPE
418 SYNTAX Integer32 (1..2147483647)
419 MAX-ACCESS not-accessible
422 "A number uniquely identifying each RADIUS
423 authentication client with which this server
425 ::= { radiusAuthClientEntry 1 }
427 radiusAuthClientAddress OBJECT-TYPE
432 "The NAS-IP-Address of the RADIUS authentication client
433 referred to in this table entry."
434 ::= { radiusAuthClientEntry 2 }
436 radiusAuthClientID OBJECT-TYPE
437 SYNTAX SnmpAdminString
441 "The NAS-Identifier of the RADIUS authentication client
442 referred to in this table entry. This is not necessarily
443 the same as sysName in MIB II."
444 ::= { radiusAuthClientEntry 3 }
450 Zorn & Aboba Standards Track [Page 8]
452 RFC 2619 RADIUS Authentication Server MIB June 1999
456 -- Responses = AccessAccepts + AccessRejects + AccessChallenges
458 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
459 -- UnknownTypes - PacketsDropped - Responses = Pending
461 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
462 -- UnknownTypes - PacketsDropped = entries logged
464 radiusAuthServAccessRequests OBJECT-TYPE
469 "The number of packets received on the authentication
470 port from this client."
471 ::= { radiusAuthClientEntry 4 }
473 radiusAuthServDupAccessRequests OBJECT-TYPE
478 "The number of duplicate RADIUS Access-Request
479 packets received from this client."
480 ::= { radiusAuthClientEntry 5 }
482 radiusAuthServAccessAccepts OBJECT-TYPE
487 "The number of RADIUS Access-Accept packets
488 sent to this client."
489 ::= { radiusAuthClientEntry 6 }
491 radiusAuthServAccessRejects OBJECT-TYPE
496 "The number of RADIUS Access-Reject packets
497 sent to this client."
498 ::= { radiusAuthClientEntry 7 }
500 radiusAuthServAccessChallenges OBJECT-TYPE
506 Zorn & Aboba Standards Track [Page 9]
508 RFC 2619 RADIUS Authentication Server MIB June 1999
513 "The number of RADIUS Access-Challenge packets
514 sent to this client."
515 ::= { radiusAuthClientEntry 8 }
517 radiusAuthServMalformedAccessRequests OBJECT-TYPE
522 "The number of malformed RADIUS Access-Request
523 packets received from this client.
524 Bad authenticators and unknown types are not included as
525 malformed Access-Requests."
526 ::= { radiusAuthClientEntry 9 }
528 radiusAuthServBadAuthenticators OBJECT-TYPE
533 "The number of RADIUS Authentication-Request packets
534 which contained invalid Signature attributes received
536 ::= { radiusAuthClientEntry 10 }
538 radiusAuthServPacketsDropped OBJECT-TYPE
543 "The number of incoming packets from this
544 client silently discarded for some reason other
545 than malformed, bad authenticators or
547 ::= { radiusAuthClientEntry 11 }
549 radiusAuthServUnknownTypes OBJECT-TYPE
554 "The number of RADIUS packets of unknown type which
555 were received from this client."
556 ::= { radiusAuthClientEntry 12 }
562 Zorn & Aboba Standards Track [Page 10]
564 RFC 2619 RADIUS Authentication Server MIB June 1999
567 -- conformance information
569 radiusAuthServMIBConformance
570 OBJECT IDENTIFIER ::= { radiusAuthServMIB 2 }
571 radiusAuthServMIBCompliances
572 OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 1 }
573 radiusAuthServMIBGroups
574 OBJECT IDENTIFIER ::= { radiusAuthServMIBConformance 2 }
577 -- compliance statements
579 radiusAuthServMIBCompliance MODULE-COMPLIANCE
582 "The compliance statement for authentication servers
583 implementing the RADIUS Authentication Server MIB."
584 MODULE -- this module
585 MANDATORY-GROUPS { radiusAuthServMIBGroup }
587 OBJECT radiusAuthServConfigReset
588 WRITE-SYNTAX INTEGER { reset(2) }
589 DESCRIPTION "The only SETable value is 'reset' (2)."
591 ::= { radiusAuthServMIBCompliances 1 }
593 -- units of conformance
595 radiusAuthServMIBGroup OBJECT-GROUP
596 OBJECTS {radiusAuthServIdent,
597 radiusAuthServUpTime,
598 radiusAuthServResetTime,
599 radiusAuthServConfigReset,
600 radiusAuthServTotalAccessRequests,
601 radiusAuthServTotalInvalidRequests,
602 radiusAuthServTotalDupAccessRequests,
603 radiusAuthServTotalAccessAccepts,
604 radiusAuthServTotalAccessRejects,
605 radiusAuthServTotalAccessChallenges,
606 radiusAuthServTotalMalformedAccessRequests,
607 radiusAuthServTotalBadAuthenticators,
608 radiusAuthServTotalPacketsDropped,
609 radiusAuthServTotalUnknownTypes,
610 radiusAuthClientAddress,
612 radiusAuthServAccessRequests,
613 radiusAuthServDupAccessRequests,
614 radiusAuthServAccessAccepts,
618 Zorn & Aboba Standards Track [Page 11]
620 RFC 2619 RADIUS Authentication Server MIB June 1999
623 radiusAuthServAccessRejects,
624 radiusAuthServAccessChallenges,
625 radiusAuthServMalformedAccessRequests,
626 radiusAuthServBadAuthenticators,
627 radiusAuthServPacketsDropped,
628 radiusAuthServUnknownTypes
632 "The collection of objects providing management of
633 a RADIUS Authentication Server."
634 ::= { radiusAuthServMIBGroups 1 }
640 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
641 Describing SNMP Management Frameworks", RFC 2571, April 1999.
643 [2] Rose, M., and K. McCloghrie, "Structure and Identification of
644 Management Information for TCP/IP-based Internets", STD 16, RFC
647 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
648 RFC 1212, March 1991.
650 [4] Rose, M., "A Convention for Defining Traps for use with the
651 SNMP", RFC 1215, March 1991.
653 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
654 M. and S. Waldbusser, "Structure of Management Information
655 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
657 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
658 M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
659 RFC 2579, April 1999.
661 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
662 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
663 58, RFC 2580, April 1999.
665 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
666 Network Management Protocol", STD 15, RFC 1157, May 1990.
668 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
669 "Introduction to Community-based SNMPv2", RFC 1901, January
674 Zorn & Aboba Standards Track [Page 12]
676 RFC 2619 RADIUS Authentication Server MIB June 1999
679 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
680 "Transport Mappings for Version 2 of the Simple Network
681 Management Protocol (SNMPv2)", RFC 1906, January 1996.
683 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
684 Processing and Dispatching for the Simple Network
685 Management Protocol (SNMP)", RFC 2572, April 1999.
687 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model for
688 Version 3 of the Simple Network Management Protocol (SNMPv3)",
689 RFC 2574, April 1999.
691 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
692 Operations for Version 2 of the Simple Network Management
693 Protocol (SNMPv2)", RFC 1905, January 1996.
695 [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC
698 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
699 Control Model for the Simple Network Management Protocol
700 (SNMP)", RFC 2575, April 1999.
702 [16] Rigney, C., Rubens, A., Simpson W. and S. Willens, "Remote
703 Authentication Dial In User Service (RADIUS)", RFC 2138, April
706 6. Security Considerations
708 There are a number of management objects defined in this MIB that
709 have a MAX-ACCESS clause of read-write and/or read-create. Such
710 objects may be considered sensitive or vulnerable in some network
711 environments. The support for SET operations in a non-secure
712 environment without proper protection can have a negative effect on
715 There are a number of managed objects in this MIB that may contain
716 sensitive information. These are:
718 radiusAuthClientAddress
719 This can be used to determine the address of the RADIUS
720 authentication client with which the server is
721 communicating. This information could be useful in
722 impersonating the client.
724 radiusAuthClientID This can be used to determine the client ID of the
725 authentication client with which the server is
726 communicating. This information could be useful in
730 Zorn & Aboba Standards Track [Page 13]
732 RFC 2619 RADIUS Authentication Server MIB June 1999
735 impersonating the client.
737 It is thus important to control even GET access to these objects and
738 possibly to even encrypt the values of these object when sending them
739 over the network via SNMP. Not all versions of SNMP provide features
740 for such a secure environment.
742 SNMPv1 by itself is not a secure environment. Even if the network
743 itself is secure (for example by using IPSec), there is no control as
744 to who on the secure network is allowed to access and GET/SET
745 (read/change/create/delete) the objects in this MIB.
747 It is recommended that the implementers consider the security
748 features as provided by the SNMPv3 framework. Specifically, the use
749 of the User-based Security Model RFC 2574 [12] and the View-based
750 Access Control Model RFC 2575 [15] is recommended. Using these
751 security features, customer/users can give access to the objects only
752 to those principals (users) that have legitimate rights to GET or SET
753 (change/create/delete) them.
757 The authors acknowledge the contributions of the RADIUS Working Group
758 in the development of this MIB. Thanks to Narendra Gidwani of
759 Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston and
760 Peter Heitman of American Internet Corporation for useful discussions
761 of this problem space.
763 8. Authors' Addresses
766 Microsoft Corporation
771 EMail: bernarda@microsoft.com
774 Microsoft Corporation
779 EMail: glennz@microsoft.com
781 9. Intellectural Property Statement
786 Zorn & Aboba Standards Track [Page 14]
788 RFC 2619 RADIUS Authentication Server MIB June 1999
791 The IETF takes no position regarding the validity or scope of any
792 intellectual property or other rights that might be claimed to
793 pertain to the implementation or use of the technology described in
794 this document or the extent to which any license under such rights
795 might or might not be available; neither does it represent that it
796 has made any effort to identify any such rights. Information on the
797 IETF's procedures with respect to rights in standards-track and
798 standards- related documentation can be found in BCP-11. Copies of
799 claims of rights made available for publication and any assurances of
800 licenses to be made available, or the result of an attempt made to
801 obtain a general license or permission for the use of such
802 proprietary rights by implementors or users of this specification can
803 be obtained from the IETF Secretariat.
805 The IETF invites any interested party to bring to its attention any
806 copyrights, patents or patent applications, or other proprietary
807 rights which may cover technology that may be required to practice
808 this standard. Please address the information to the IETF Executive
842 Zorn & Aboba Standards Track [Page 15]
844 RFC 2619 RADIUS Authentication Server MIB June 1999
847 10. Full Copyright Statement
849 Copyright (C) The Internet Society (1999). All Rights Reserved.
851 This document and translations of it may be copied and furnished to
852 others, and derivative works that comment on or otherwise explain it
853 or assist in its implmentation may be prepared, copied, published and
854 distributed, in whole or in part, without restriction of any kind,
855 provided that the above copyright notice and this paragraph are
856 included on all such copies and derivative works. However, this
857 document itself may not be modified in any way, such as by removing
858 the copyright notice or references to the Internet Society or other
859 Internet organizations, except as needed for the purpose of
860 developing Internet standards in which case the procedures for
861 copyrights defined in the Internet Standards process must be
862 followed, or as required to translate it into languages other than
865 The limited permissions granted above are perpetual and will not be
866 revoked by the Internet Society or its successors or assigns.
868 This document and the information contained herein is provided on an
869 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
870 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
871 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
872 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
873 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
877 Funding for the RFC Editor function is currently provided by the
898 Zorn & Aboba Standards Track [Page 16]