RADIUS Working Group Glen Zorn
INTERNET-DRAFT Microsoft
Category: Informational Bernard Aboba
<draft-ietf-radius-acc-servmib-00.txt> Microsoft
9 August 1997
RADIUS Accounting Server MIB
1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working docu-
ments of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute work-
ing documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference mate-
rial or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
The distribution of this memo is unlimited. It is filed as <draft-
ietf-radius-acc-servmib-00.txt>, and expires February 1, 1998. Please
send comments to the authors.
2. Abstract
This memo defines a set of extensions which instrument RADIUS account-
ing server functions. These extensions represent a portion of the Man-
agement Information Base (MIB) for use with network management proto-
cols in the Internet community. Using these extensions IP-based man-
agement stations can manage RADIUS accounting servers.
3. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing RADIUS
accounting servers.
RADIUS accounting servers are today widely deployed by dialup Internet
Service Providers, in order to provide accounting services. As a
result, the effective management of RADIUS accounting servers is of
considerable importance.
Zorn & Aboba [Page 1]
INTERNET-DRAFT 9 August 1997
4. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major compo-
nents. They are:
o RFC 1902 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
o RFC 1905 which defines the protocol used for network access to
managed objects.
o RFC 1907 defines the core set of managed objects for the
Internet suite of protocols.
o RFC 1909 which defines the administrative aspects of the
framework.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
4.1. Object Definitions
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in
the SMI. In particular, each object object type is named by an OBJECT
IDENTIFIER, an administratively assigned name. The object type
together with an object instance serves to uniquely identify a spe-
cific instantiation of the object. For human convenience, we often use
a textual string, termed the descriptor, to refer to the object type.
5. Overview
The RADIUS accounting protocol, described in [2], distinguishes
between the client function and the server function. In RADIUS
accounting, clients send Accounting-Requests, and servers reply with
Accounting-Responses. Typically NAS devices implement the client func-
tion, and thus would be expected to implement the RADIUS accounting
client MIB, while RADIUS accounting servers implement the server func-
tion, and thus would be expected to implement the RADIUS accounting
server MIB.
However, it is possible for a RADIUS accounting entity to perform both
client and server functions. For example, a RADIUS proxy may act as a
server to one or more RADIUS accounting clients, while simultaneously
acting as an accounting client to one or more accounting servers. In
such situations, it is expected that RADIUS entities combining client
and server functionality will support both the client and server MIBs.
Zorn & Aboba [Page 2]
INTERNET-DRAFT 9 August 1997
5.1. Selected objects
This MIB module contains five scalars as well as a single table:
(1) the RADIUS Accounting Client Table contains one row for each
RADIUS accounting client that the server shares a secret with.
Each entry in the RADIUS Accounting Client Table includes eleven
entries presenting a view of the activity of the RADIUS accounting
server.
6. Definitions
RADIUS-ACC-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
OBJECT-IDENTITY, experimental,
Counter32, Gauge32, Integer32,
IpAddress, TimeTicks FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus,
TruthValue, DisplayString FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radius OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { experimental 79 }
radiusAccounting OBJECT-IDENTIFIER ::= {radius 2}
radiusAccServMIB MODULE-IDENTITY
LAST-UPDATED "9708211659Z"
ORGANIZATION "IETF RADIUS Working Group."
CONTACT-INFO
" Glen Zorn
Microsoft
One Microsoft Way
Redmond, WA 98052
US
Phone: +1 425 703 1559
EMail: glennz@microsoft.com"
DESCRIPTION
"The MIB module for entities implementing the server
side of the Remote Access Dialin User Service (RADIUS)
accounting protocol."
::= { radiusAccounting 1 }
radiusAccServMIBObjects OBJECT IDENTIFIER ::= { radiusAccServMIB 1 }
Zorn & Aboba [Page 3]
INTERNET-DRAFT 9 August 1997
radiusAccServ OBJECT IDENTIFIER ::= { radiusAccServMIBObjects 1 }
-- Textual conventions
RadiusTime ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4d"
STATUS current
DESCRIPTION
"RadiusTime values are 32-bit unsigned integers which
measure time in seconds."
SYNTAX Gauge32
radiusAccServIdent OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The implementation identification string for the
RADIUS accounting server software in use on the
system, for example; `FNS-2.1'"
::= {radiusAccServ 1}
radiusAccServUpTime OBJECT-TYPE
SYNTAX RadiusTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the server has a persistent state (e.g., a process),
this value will be the time elapsed since it started.
For software without persistent state, this value will
be zero."
::= {radiusAccServ 2}
radiusAccServResetTime OBJECT-TYPE
SYNTAX RadiusTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the server has a persistent state (e.g., a process)
and supports a `reset' operation (e.g., can be told to
re-read configuration files), this value will be the
time elapsed since the last time the name server was
`reset.' For software that does not have persistence or
does not support a `reset' operation, this value will be
zero."
::= {radiusAccServ 3}
radiusAccServConfigReset OBJECT-TYPE
SYNTAX INTEGER { other(1),
reset(2),
initializing(3),
running(4)}
MAX-ACCESS read-write
STATUS current
Zorn & Aboba [Page 4]
INTERNET-DRAFT 9 August 1997
DESCRIPTION
"Status/action object to reinitialize any persistent
server state. When set to reset(2), any persistent
server state (such as a process) is reinitialized as if
the server had just been started. This value will
never be returned by a read operation. When read, one of
the following values will be returned:
other(1) - server in some unknown state;
initializing(3) - server (re)initializing;
running(4) - server currently running."
::= {radiusAccServ 4}
radiusAccServInvalidClientAddresses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request packets
received from unknown addresses since server start-up."
::= {radiusAccServ 5}
radiusAccClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS accounting
clients with which the server shares a secret."
::= { radiusAccServ 6 }
radiusAccClientEntry OBJECT-TYPE
SYNTAX RadiusAccClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) representing a RADIUS
accounting client with which the server shares a secret."
INDEX { radiusAccClientIndex }
::= { radiusAccClientTable 1 }
RadiusAccClientEntry ::= SEQUENCE {
radiusAccClientIndex Integer32,
radiusAccClientAddress IpAddress,
radiusAccClientID DisplayString,
radiusAccServPacketsDropped Counter32,
radiusAccServAccountingRequests Counter32,
radiusAccServDupAccountingRequests Counter32,
radiusAccServAccountingResponses Counter32,
radiusAccServAccountingBadAuthenticators Counter32,
radiusAccServMalformedAccountingRequests Counter32,
radiusAccServAccountingNoRecord Counter32,
radiusAccServUnknownType Counter32
}
Zorn & Aboba [Page 5]
INTERNET-DRAFT 9 August 1997
radiusAccClientIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The RADIUS accounting client referred to in this
table entry."
::= { radiusAccClientEntry 1 }
radiusAccClientAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-IP-Address of the RADIUS accounting client
referred to in this table entry."
::= { radiusAccClientEntry 2 }
radiusAccClientID OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client
referred to in this table entry."
::= { radiusAccClientEntry 3 }
-- Server Counters
radiusAccServPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets dropped from this client,
with no reply sent."
::= { radiusAccClientEntry 4 }
radiusAccServAccountingRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request packets
received from this client since server start-up."
::= { radiusAccClientEntry 5 }
radiusAccServDupAccountingRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of duplicate RADIUS Accounting-Request
packets received from this client since server start-up."
Zorn & Aboba [Page 6]
INTERNET-DRAFT 9 August 1997
::= { radiusAccClientEntry 6 }
radiusAccServAccountingResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Response packets
sent to this client since server start-up."
::= { radiusAccClientEntry 7 }
radiusAccServAccountingBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request packets
which contained invalid authenticators received
from this client since server start-up."
::= { radiusAccClientEntry 8 }
radiusAccServMalformedAccountingRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of malformed RADIUS Accounting-Request
packets which were received from this client since
server start-up. Bad authenticators are not included as
malformed Accounting-Requests."
::= { radiusAccClientEntry 9 }
radiusAccServAccountingNoRecord OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request packets
which were received from this client but not recorded
since server start-up."
::= { radiusAccClientEntry 10 }
radiusAccServUnknownType OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS packets of unknown type which
were received from this client since accounting server
start-up."
::= { radiusAccClientEntry 11 }
-- conformance information
Zorn & Aboba [Page 7]
INTERNET-DRAFT 9 August 1997
radiusAccServMIBConformance
OBJECT IDENTIFIER ::= { radiusAccServMIB 2 }
radiusAccServMIBCompliances
OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 1 }
radiusAccServMIBGroups
OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 2 }
-- compliance statements
radiusAccServMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for accounting servers
implementing the RADIUS Accounting Server MIB."
MODULE -- this module
MANDATORY-GROUPS { radiusAccServMIBGroup }
::= { radiusAccServMIBCompliances 1 }
-- units of conformance
radiusAccServMIBGroup OBJECT-GROUP
OBJECTS {radiusAccServIdent,
radiusAccServUpTime,
radiusAccServResetTime,
radiusAccServConfigReset,
radiusAccServInvalidClientAddresses,
radiusAccClientAddress,
radiusAccClientID,
radiusAccServPacketsDropped,
radiusAccServAccountingRequests,
radiusAccServDupAccountingRequests,
radiusAccServAccountingResponses,
radiusAccServAccountingBadAuthenticators,
radiusAccServMalformedAccountingRequests,
radiusAccServAccountingNoRecord,
radiusAccServUnknownType
}
STATUS current
DESCRIPTION
"The collection of objects providing management of
a RADIUS Accounting Server."
::= { radiusAccServMIBGroups 1 }
END
7. Security considerations
All MIB variables described in this document are read-only, with the
exception of radiusAccServConfigReset.
Zorn & Aboba [Page 8]
INTERNET-DRAFT 9 August 1997
8. Acknowledgments
Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT,
Carl Rigney of Livingston, and Peter Heitman of American Internet Cor-
poration for useful discussions of this problem space.
9. References
[1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti-
cation Dial In User Service (RADIUS)." RFC 2138, Livingston, Merit,
Daydreamer, April, 1997.
[2] C. Rigney. "RADIUS Accounting." RFC 2139, Livingston, April,
1997.
[3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius-
ext-00.txt, Livingston, January, 1997.
[4] "Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1)", International
Organization for Standardization, International Standard 8824, Decem-
ber 1987.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc-
tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco
Systems, Dover Beach Consulting, Inc., International Network Services,
January, 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network Manage-
ment Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco Systems,
Dover Beach Consulting, Inc., International Network Services, January,
1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for version 2 of the the Simple Network Management Proto-
col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover
Beach Consulting, Inc., International Network Services, January, 1996.
[8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor-
mance Statements for version 2 of the the Simple Network Management
Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems,
Dover Beach Consulting, Inc., International Network Services, January,
1996.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach
Consulting, Inc., International Network Services, January, 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach
Zorn & Aboba [Page 9]
INTERNET-DRAFT 9 August 1997
Consulting, Inc., International Network Services, January, 1996.
[11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage-
ment Information Base for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1907, SNMP Research, nc., Cisco Systems, Dover
Beach Consulting, Inc., International Network Services, January, 1996.
[12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis-
tence between Version 1 and Version 2 of the Internet-standard Network
Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems,
Dover Beach Consulting, Inc., International Network Services, January,
1996.
[13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2",
RFC 1909, Cisco Systems, February, 1996.
10. Authors' Addresses
Glen Zorn
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 425-703-1559
EMail: glennz@microsoft.com
Bernard Aboba
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 425-936-6605
EMail: bernarda@microsoft.com
Zorn & Aboba [Page 10]
