7 Network Working Group G. Zorn
8 Request for Comments: 2621 B. Aboba
9 Category: Informational Microsoft
13 RADIUS Accounting Server MIB
17 This memo provides information for the Internet community. This memo
18 does not specify an Internet standard of any kind. Distribution of
19 this memo is unlimited.
23 Copyright (C) The Internet Society (1999). All Rights Reserved.
27 This memo defines a set of extensions which instrument RADIUS
28 accounting server functions. These extensions represent a portion of
29 the Management Information Base (MIB) for use with network management
30 protocols in the Internet community. Using these extensions IP-based
31 management stations can manage RADIUS accounting servers.
35 This memo defines a portion of the Management Information Base (MIB)
36 for use with network management protocols in the Internet community.
37 In particular, it describes managed objects used for managing RADIUS
40 RADIUS accounting servers are today widely deployed by dialup
41 Internet Service Providers, in order to provide accounting services.
42 As a result, the effective management of RADIUS accounting servers is
43 of considerable importance.
45 2. The SNMP Management Framework
47 The SNMP Management Framework presently consists of five major
50 o An overall architecture, described in RFC 2571 [1].
52 o Mechanisms for describing and naming objects and events for the
53 purpose of management. The first version of this Structure of
54 Management Information (SMI) is called SMIv1 and described in
58 Zorn & Aboba Informational [Page 1]
60 RFC 2621 RADIUS Accounting Server MIB June 1999
63 STD 15, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
64 The second version, called SMIv2, is described in STD 58, RFC
65 2578 [5], RFC 2579 [6] and RFC 2580 [7].
67 o Message protocols for transferring management information. The
68 first version of the SNMP message protocol is called SNMPv1 and
69 described in STD 15, RFC 1157 [8]. A second version of the
70 SNMP message protocol, which is not an Internet standards
71 track protocol, is called SNMPv2c and described in RFC 1901
72 [9] and RFC 1906 [10]. The third version of the message
73 protocol is called SNMPv3 and described in RFC 1906 [10], RFC
74 2572 [11] and RFC 2574 [12].
76 o Protocol operations for accessing management information. The
77 first set of protocol operations and associated PDU formats is
78 described in STD 15, RFC 1157 [8]. A second set of protocol
79 operations and associated PDU formats is described in RFC 1905
82 o A set of fundamental applications described in RFC 2573 [14] and
83 the view-based access control mechanism described in RFC 2575
86 Managed objects are accessed via a virtual information store, termed
87 the Management Information Base or MIB. Objects in the MIB are
88 defined using the mechanisms defined in the SMI.
90 This memo specifies a MIB module that is compliant to the SMIv2. A
91 MIB conforming to the SMIv1 can be produced through the appropriate
92 translations. The resulting translated MIB must be semantically
93 equivalent, except where objects or events are omitted because no
94 translation is possible (use of Counter64). Some machine readable
95 information in SMIv2 will be converted into textual descriptions in
96 SMIv1 during the translation process. However, this loss of machine
97 readable information is not considered to change the semantics of the
102 The RADIUS accounting protocol, described in [16], distinguishes
103 between the client function and the server function. In RADIUS
104 accounting, clients send Accounting-Requests, and servers reply with
105 Accounting-Responses. Typically NAS devices implement the client
106 function, and thus would be expected to implement the RADIUS
107 accounting client MIB, while RADIUS accounting servers implement the
108 server function, and thus would be expected to implement the RADIUS
109 accounting server MIB.
114 Zorn & Aboba Informational [Page 2]
116 RFC 2621 RADIUS Accounting Server MIB June 1999
119 However, it is possible for a RADIUS accounting entity to perform
120 both client and server functions. For example, a RADIUS proxy may act
121 as a server to one or more RADIUS accounting clients, while
122 simultaneously acting as an accounting client to one or more
123 accounting servers. In such situations, it is expected that RADIUS
124 entities combining client and server functionality will support both
125 the client and server MIBs.
127 3.1. Selected objects
129 This MIB module contains thirteen scalars as well as a single table:
131 (1) the RADIUS Accounting Client Table contains one row for each
132 RADIUS accounting client that the server shares a secret with.
134 Each entry in the RADIUS Accounting Client Table includes eleven
135 columns presenting a view of the activity of the RADIUS accounting
140 RADIUS-ACC-SERVER-MIB DEFINITIONS ::= BEGIN
143 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
144 Counter32, Integer32,
145 IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
146 SnmpAdminString FROM SNMP-FRAMEWORK-MIB
147 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
149 radiusAccServMIB MODULE-IDENTITY
150 LAST-UPDATED "9906110000Z" -- 11 Jun 1999
151 ORGANIZATION "IETF RADIUS Working Group."
159 Phone: +1 425 936 6605
160 EMail: bernarda@microsoft.com"
162 "The MIB module for entities implementing the server
163 side of the Remote Access Dialin User Service (RADIUS)
164 accounting protocol."
165 REVISION "9906110000Z" -- 11 Jun 1999
166 DESCRIPTION "Initial version as published in RFC 2621"
170 Zorn & Aboba Informational [Page 3]
172 RFC 2621 RADIUS Accounting Server MIB June 1999
175 ::= { radiusAccounting 1 }
177 radiusMIB OBJECT-IDENTITY
180 "The OID assigned to RADIUS MIB work by the IANA."
183 radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
185 radiusAccServMIBObjects OBJECT IDENTIFIER ::=
186 { radiusAccServMIB 1 }
188 radiusAccServ OBJECT IDENTIFIER ::= { radiusAccServMIBObjects 1 }
190 radiusAccServIdent OBJECT-TYPE
191 SYNTAX SnmpAdminString
195 "The implementation identification string for the
196 RADIUS accounting server software in use on the
197 system, for example; `FNS-2.1'"
198 ::= {radiusAccServ 1}
200 radiusAccServUpTime OBJECT-TYPE
205 "If the server has a persistent state (e.g., a process),
206 this value will be the time elapsed (in hundredths of a
207 second) since the server process was started.
208 For software without persistent state, this value will
210 ::= {radiusAccServ 2}
212 radiusAccServResetTime OBJECT-TYPE
217 "If the server has a persistent state (e.g., a process)
218 and supports a `reset' operation (e.g., can be told to
219 re-read configuration files), this value will be the
220 time elapsed (in hundredths of a second) since the
221 server was `reset.' For software that does not
222 have persistence or does not support a `reset' operation,
226 Zorn & Aboba Informational [Page 4]
228 RFC 2621 RADIUS Accounting Server MIB June 1999
231 this value will be zero."
232 ::= {radiusAccServ 3}
234 radiusAccServConfigReset OBJECT-TYPE
235 SYNTAX INTEGER { other(1),
239 MAX-ACCESS read-write
242 "Status/action object to reinitialize any persistent
243 server state. When set to reset(2), any persistent
244 server state (such as a process) is reinitialized as if
245 the server had just been started. This value will
246 never be returned by a read operation. When read, one
247 of the following values will be returned:
248 other(1) - server in some unknown state;
249 initializing(3) - server (re)initializing;
250 running(4) - server currently running."
251 ::= {radiusAccServ 4}
253 -- New Stats proposed by Dale E. Reed Jr (daler@iea.com)
255 radiusAccServTotalRequests OBJECT-TYPE
260 "The number of packets received on the
262 ::= { radiusAccServ 5 }
264 radiusAccServTotalInvalidRequests OBJECT-TYPE
269 "The number of RADIUS Accounting-Request packets
270 received from unknown addresses."
271 ::= { radiusAccServ 6 }
273 radiusAccServTotalDupRequests OBJECT-TYPE
278 "The number of duplicate RADIUS Accounting-Request
282 Zorn & Aboba Informational [Page 5]
284 RFC 2621 RADIUS Accounting Server MIB June 1999
288 ::= { radiusAccServ 7 }
290 radiusAccServTotalResponses OBJECT-TYPE
295 "The number of RADIUS Accounting-Response packets sent."
296 ::= { radiusAccServ 8 }
298 radiusAccServTotalMalformedRequests OBJECT-TYPE
303 "The number of malformed RADIUS Accounting-Request
304 packets received. Bad authenticators or unknown
305 types are not included as malformed Access-Requests."
306 ::= { radiusAccServ 9 }
308 radiusAccServTotalBadAuthenticators OBJECT-TYPE
313 "The number of RADIUS Accounting-Request packets
314 which contained invalid Signature attributes."
315 ::= { radiusAccServ 10 }
317 radiusAccServTotalPacketsDropped OBJECT-TYPE
322 "The number of incoming packets silently discarded
323 for a reason other than malformed, bad authenticators,
325 ::= { radiusAccServ 11 }
327 radiusAccServTotalNoRecords OBJECT-TYPE
332 "The number of RADIUS Accounting-Request packets
333 which were received and responded to but not
338 Zorn & Aboba Informational [Page 6]
340 RFC 2621 RADIUS Accounting Server MIB June 1999
343 ::= { radiusAccServ 12 }
345 radiusAccServTotalUnknownTypes OBJECT-TYPE
350 "The number of RADIUS packets of unknowntype which
352 ::= { radiusAccServ 13 }
356 radiusAccClientTable OBJECT-TYPE
357 SYNTAX SEQUENCE OF RadiusAccClientEntry
358 MAX-ACCESS not-accessible
361 "The (conceptual) table listing the RADIUS accounting
362 clients with which the server shares a secret."
363 ::= { radiusAccServ 14 }
365 radiusAccClientEntry OBJECT-TYPE
366 SYNTAX RadiusAccClientEntry
367 MAX-ACCESS not-accessible
370 "An entry (conceptual row) representing a RADIUS
371 accounting client with which the server shares a secret."
372 INDEX { radiusAccClientIndex }
373 ::= { radiusAccClientTable 1 }
375 RadiusAccClientEntry ::= SEQUENCE {
376 radiusAccClientIndex Integer32,
377 radiusAccClientAddress IpAddress,
378 radiusAccClientID SnmpAdminString,
379 radiusAccServPacketsDropped Counter32,
380 radiusAccServRequests Counter32,
381 radiusAccServDupRequests Counter32,
382 radiusAccServResponses Counter32,
383 radiusAccServBadAuthenticators Counter32,
384 radiusAccServMalformedRequests Counter32,
385 radiusAccServNoRecords Counter32,
386 radiusAccServUnknownTypes Counter32
389 radiusAccClientIndex OBJECT-TYPE
390 SYNTAX Integer32 (1..2147483647)
394 Zorn & Aboba Informational [Page 7]
396 RFC 2621 RADIUS Accounting Server MIB June 1999
399 MAX-ACCESS not-accessible
402 "A number uniquely identifying each RADIUS accounting
403 client with which this server communicates."
404 ::= { radiusAccClientEntry 1 }
406 radiusAccClientAddress OBJECT-TYPE
411 "The NAS-IP-Address of the RADIUS accounting client
412 referred to in this table entry."
413 ::= { radiusAccClientEntry 2 }
415 radiusAccClientID OBJECT-TYPE
416 SYNTAX SnmpAdminString
420 "The NAS-Identifier of the RADIUS accounting client
421 referred to in this table entry. This is not necessarily
422 the same as sysName in MIB II."
423 ::= { radiusAccClientEntry 3 }
427 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
428 -- UnknownTypes - PacketsDropped - Responses = Pending
430 -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
431 -- UnknownTypes - PacketsDropped - NoRecords = entries logged
433 radiusAccServPacketsDropped OBJECT-TYPE
438 "The number of incoming packets received
439 from this client and silently discarded
440 for a reason other than malformed, bad
441 authenticators, or unknown types."
442 ::= { radiusAccClientEntry 4 }
444 radiusAccServRequests OBJECT-TYPE
450 Zorn & Aboba Informational [Page 8]
452 RFC 2621 RADIUS Accounting Server MIB June 1999
457 "The number of packets received from this
458 client on the accounting port."
459 ::= { radiusAccClientEntry 5 }
461 radiusAccServDupRequests OBJECT-TYPE
466 "The number of duplicate RADIUS Accounting-Request
467 packets received from this client."
468 ::= { radiusAccClientEntry 6 }
470 radiusAccServResponses OBJECT-TYPE
475 "The number of RADIUS Accounting-Response packets
476 sent to this client."
477 ::= { radiusAccClientEntry 7 }
479 radiusAccServBadAuthenticators OBJECT-TYPE
484 "The number of RADIUS Accounting-Request packets
485 which contained invalid authenticators received
487 ::= { radiusAccClientEntry 8 }
489 radiusAccServMalformedRequests OBJECT-TYPE
494 "The number of malformed RADIUS Accounting-Request
495 packets which were received from this client.
496 Bad authenticators and unknown types
497 are not included as malformed Accounting-Requests."
498 ::= { radiusAccClientEntry 9 }
500 radiusAccServNoRecords OBJECT-TYPE
506 Zorn & Aboba Informational [Page 9]
508 RFC 2621 RADIUS Accounting Server MIB June 1999
513 "The number of RADIUS Accounting-Request packets
514 which were received and responded to but not
516 ::= { radiusAccClientEntry 10 }
518 radiusAccServUnknownTypes OBJECT-TYPE
523 "The number of RADIUS packets of unknown type which
524 were received from this client."
525 ::= { radiusAccClientEntry 11 }
528 -- conformance information
530 radiusAccServMIBConformance
531 OBJECT IDENTIFIER ::= { radiusAccServMIB 2 }
532 radiusAccServMIBCompliances
533 OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 1 }
534 radiusAccServMIBGroups
535 OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 2 }
537 -- compliance statements
539 radiusAccServMIBCompliance MODULE-COMPLIANCE
542 "The compliance statement for accounting servers
543 implementing the RADIUS Accounting Server MIB."
544 MODULE -- this module
545 MANDATORY-GROUPS { radiusAccServMIBGroup }
547 OBJECT radiusAccServConfigReset
548 WRITE-SYNTAX INTEGER { reset(2) }
549 DESCRIPTION "The only SETable value is 'reset' (2)."
551 ::= { radiusAccServMIBCompliances 1 }
554 -- units of conformance
556 radiusAccServMIBGroup OBJECT-GROUP
557 OBJECTS {radiusAccServIdent,
562 Zorn & Aboba Informational [Page 10]
564 RFC 2621 RADIUS Accounting Server MIB June 1999
567 radiusAccServResetTime,
568 radiusAccServConfigReset,
569 radiusAccServTotalRequests,
570 radiusAccServTotalInvalidRequests,
571 radiusAccServTotalDupRequests,
572 radiusAccServTotalResponses,
573 radiusAccServTotalMalformedRequests,
574 radiusAccServTotalBadAuthenticators,
575 radiusAccServTotalPacketsDropped,
576 radiusAccServTotalNoRecords,
577 radiusAccServTotalUnknownTypes,
578 radiusAccClientAddress,
580 radiusAccServPacketsDropped,
581 radiusAccServRequests,
582 radiusAccServDupRequests,
583 radiusAccServResponses,
584 radiusAccServBadAuthenticators,
585 radiusAccServMalformedRequests,
586 radiusAccServNoRecords,
587 radiusAccServUnknownTypes
591 "The collection of objects providing management of
592 a RADIUS Accounting Server."
593 ::= { radiusAccServMIBGroups 1 }
599 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
600 for Describing SNMP Management Frameworks", RFC 2571, April
603 [2] Rose, M., and K. McCloghrie, "Structure and Identification of
604 Management Information for TCP/IP-based Internets", STD 16, RFC
607 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
608 RFC 1212, March 1991.
610 [4] Rose, M., "A Convention for Defining Traps for use with the
611 SNMP", RFC 1215, Performance Systems International, March 1991.
618 Zorn & Aboba Informational [Page 11]
620 RFC 2621 RADIUS Accounting Server MIB June 1999
623 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
624 M. and S. Waldbusser, "Structure of Management Information
625 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
627 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
628 M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
629 RFC 2579, April 1999.
631 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
632 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
633 58, RFC 2580, April 1999.
635 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
636 Network Management Protocol", STD 15, RFC 1157, May 1990.
638 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
639 "Introduction to Community-based SNMPv2", RFC 1901, January
642 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
643 "Transport Mappings for Version 2 of the Simple Network
644 Management Protocol (SNMPv2)", RFC 1906, January 1996.
646 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
647 Processing and Dispatching for the Simple Network Management
648 Protocol (SNMP)", RFC 2572, April 1999.
650 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model for
651 Version 3 of the Simple Network Management Protocol (SNMPv3)",
652 RFC 2574, April 1999.
654 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
655 Operations for Version 2 of the Simple Network Management
656 Protocol (SNMPv2)", RFC 1905, January 1996.
658 [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC
661 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
662 Control Model for the Simple Network Management Protocol
663 (SNMP)", RFC 2575, April 1999.
665 [16] Rigney, C., "RADIUS Accounting", RFC 2139, April 1997.
674 Zorn & Aboba Informational [Page 12]
676 RFC 2621 RADIUS Accounting Server MIB June 1999
679 6. Security Considerations
681 There are management objects (radiusAccServConfigReset) defined in
682 this MIB that have a MAX-ACCESS clause of read-write and/or read-
683 create. Such objects may be considered sensitive or vulnerable in
684 some network environments. The support for SET operations in a non-
685 secure environment without proper protection can have a negative
686 effect on network operations.
688 There are a number of managed objects in this MIB that may contain
689 sensitive information. These are:
691 radiusAccClientAddress
692 This can be used to determine the address of the RADIUS
693 accounting client with which the server is communicating.
694 This information could be useful in impersonating the
697 radiusAccClientID This can be used to determine the client ID for the
698 accounting client with which the server is communicating.
699 This information could be useful in impersonating the
702 It is thus important to control even GET access to these objects and
703 possibly to even encrypt the values of these object when sending them
704 over the network via SNMP. Not all versions of SNMP provide features
705 for such a secure environment.
707 SNMPv1 by itself is not a secure environment. Even if the network
708 itself is secure (for example by using IPSec), there is no control as
709 to who on the secure network is allowed to access and GET/SET
710 (read/change/create/delete) the objects in this MIB.
712 It is recommended that the implementers consider the security
713 features as provided by the SNMPv3 framework. Specifically, the use
714 of the User-based Security Model RFC 2574 [12] and the View-based
715 Access Control Model RFC 2575 [15] is recommended. Using these
716 security features, customer/users can give access to the objects only
717 to those principals (users) that have legitimate rights to GET or SET
718 (change/create/delete) them.
722 The authors acknowledge the contributions of the RADIUS Working Group
723 in the development of this MIB. Thanks to Narendra Gidwani of
724 Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston and
725 Peter Heitman of American Internet Corporation for useful discussions
726 of this problem space.
730 Zorn & Aboba Informational [Page 13]
732 RFC 2621 RADIUS Accounting Server MIB June 1999
735 8. Authors' Addresses
738 Microsoft Corporation
743 EMail: bernarda@microsoft.com
747 Microsoft Corporation
752 EMail: glennz@microsoft.com
786 Zorn & Aboba Informational [Page 14]
788 RFC 2621 RADIUS Accounting Server MIB June 1999
791 9. Full Copyright Statement
793 Copyright (C) The Internet Society (1999). All Rights Reserved.
795 This document and translations of it may be copied and furnished to
796 others, and derivative works that comment on or otherwise explain it
797 or assist in its implmentation may be prepared, copied, published and
798 distributed, in whole or in part, without restriction of any kind,
799 provided that the above copyright notice and this paragraph are
800 included on all such copies and derivative works. However, this
801 document itself may not be modified in any way, such as by removing
802 the copyright notice or references to the Internet Society or other
803 Internet organizations, except as needed for the purpose of
804 developing Internet standards in which case the procedures for
805 copyrights defined in the Internet Standards process must be
806 followed, or as required to translate it into languages other than
809 The limited permissions granted above are perpetual and will not be
810 revoked by the Internet Society or its successors or assigns.
812 This document and the information contained herein is provided on an
813 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
814 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
815 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
816 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
817 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
821 Funding for the RFC Editor function is currently provided by the
842 Zorn & Aboba Informational [Page 15]