RADIUS Working Group Glen Zorn
INTERNET-DRAFT Microsoft
<draft-ietf-radius-servmib-02.txt> Bernard Aboba
25 March 1997 Microsoft
RADIUS 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-servmib-02.txt>, and expires October 1, 1997. Please send
comments to the authors.
2. Abstract
This memo defines a set of extensions which instrument RADIUS server
functions. These extensions represent a portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet community. Using these extensions IP-based management
stations can manage RADIUS 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
servers.
RADIUS servers are today widely deployed by dialup Internet Service
Providers, in order to provide for authentication, authorization, and
accounting. As a result, the effective management of RADIUS servers is
of considerable importance.
Zorn & Aboba [Page 1]
INTERNET-DRAFT 25 March 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
specific instantiation of the object. For human convenience, we often
use a textual string, termed the descriptor, to refer to the object
type.
5. Overview
This MIB module contains a scalar as well as a single table:
(1) the RADIUS Client Table contains one row for each
RADIUS client that the server shares a secret with.
Each entry in the RADIUS Client Table includes twelve counts present-
ing a view of the activity of the RADIUS server.
6. Definitions
RADIUS-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
OBJECT-IDENTITY, experimental,
Counter32, Gauge32, Integer32,
Zorn & Aboba [Page 2]
INTERNET-DRAFT 25 March 1997
IpAddress, TimeTicks FROM SNMPv2-SMI
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."
::= { not-assigned-yet }
radiusServMIB MODULE-IDENTITY
LAST-UPDATED "9703021659Z"
ORGANIZATION "IETF RADIUS Working Group."
CONTACT-INFO
" Glen Zorn
Microsoft
One Microsoft Way
Redmond, WA 98052
US
Phone: +1 206 703 1559
EMail: glennz@microsoft.com"
DESCRIPTION
"The MIB module for RADIUS Server Management."
::= { radius 1 }
radiusServMIBObjects OBJECT IDENTIFIER ::= { radiusServMIB 1 }
radiusServ OBJECT IDENTIFIER ::= { radiusServMIBObjects 1 }
radiusServInvalidClientAddresses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Access-Request messages
received from unknown addresses since server start-up"
::= {radiusServ 1}
radiusClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS clients with
which the server shares a secret."
::= { radiusServ 2 }
radiusClientEntry OBJECT-TYPE
SYNTAX RadiusClientEntry
MAX-ACCESS not-accessible
STATUS current
Zorn & Aboba [Page 3]
INTERNET-DRAFT 25 March 1997
DESCRIPTION
"An entry (conceptual row) representing a RADIUS client
with which the server shares a secret."
INDEX { radiusClientIndex }
::= { radiusClientTable 1 }
RadiusClientEntry ::= SEQUENCE {
radiusClientIndex Integer32,
radiusClientAddress IpAddress,
radiusServAccessRequests Counter32,
radiusServDupAccessRequests Counter32,
radiusServAccessAccepts Counter32,
radiusServAccessChallenges Counter32,
radiusServMalformedAccessRequests Counter32,
radiusServAccessRejects Counter32,
radiusServPacketsDropped Counter32,
radiusServAccountingRequests Counter32,
radiusServDupAccountingRequests Counter32,
radiusServAccountingResponses Counter32,
radiusServAccountingBadAuthenticators Counter32,
radiusServAccountingNoRecord Counter32
}
radiusClientIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The RADIUS client with whom the server interacts."
::= { radiusClientEntry 1 }
radiusClientAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the RADIUS client
referred to in this table entry."
::= { radiusClientEntry 2 }
radiusServAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Access-Request messages
received since server start-up"
::= { radiusClientEntry 3 }
radiusServDupAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Zorn & Aboba [Page 4]
INTERNET-DRAFT 25 March 1997
"The total number of duplicate RADIUS Access-Request
messages received since server start-up"
::= { radiusClientEntry 4 }
radiusServAccessAccepts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Access-Accept messages
sent since server start-up"
::= { radiusClientEntry 5 }
radiusServAccessChallenges OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Access-Challenge messages
sent since server start-up"
::= { radiusClientEntry 6 }
radiusServMalformedAccessRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of malformed RADIUS Access-Request messages
received since server start-up"
::= { radiusClientEntry 7 }
radiusServAccessRejects OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Access-Reject messages sent since server start-up"
::= { radiusClientEntry 8 }
radiusServPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of packets dropped, with no reply sent"
::= { radiusClientEntry 9 }
radiusServAccountingRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request messages received
since server start-up"
Zorn & Aboba [Page 5]
INTERNET-DRAFT 25 March 1997
::= { radiusClientEntry 10 }
radiusServDupAccountingRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of duplicate RADIUS Accounting-Request messages received
since server start-up"
::= { radiusClientEntry 11 }
radiusServAccountingResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Response messages sent
since server start-up"
::= { radiusClientEntry 12 }
radiusServAccountingBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request messages which
contained invalid authenticators received since server start-up"
::= { radiusClientEntry 13 }
radiusServAccountingNoRecord OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS Accounting-Request messages which
were received but not recorded since server start-up"
::= { radiusClientEntry 14 }
-- conformance information
radiusServMIBConformance
OBJECT IDENTIFIER ::= { radiusServMIB 2 }
radiusServMIBCompliances
OBJECT IDENTIFIER ::= { radiusServMIBConformance 1 }
radiusServMIBGroups OBJECT IDENTIFIER ::= { radiusServMIBConformance 2 }
-- compliance statements
radiusServMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for servers implementing the RADIUS
MIB."
Zorn & Aboba [Page 6]
INTERNET-DRAFT 25 March 1997
MODULE -- this module
MANDATORY-GROUPS { radiusServMIBGroup }
::= { radiusServMIBCompliances 1 }
-- units of conformance
radiusServMIBGroup OBJECT-GROUP
OBJECTS {radiusServInvalidClientAddresses,
radiusClientAddress,
radiusServAccessRequests,
radiusServDupAccessRequests,
radiusServAccessAccepts,
radiusServAccessChallenges,
radiusServMalformedAccessRequests,
radiusServAccessRejects,
radiusServPacketsDropped,
radiusServAccountingRequests,
radiusServDupAccountingRequests,
radiusServAccountingResponses,
radiusServAccountingBadAuthenticators,
radiusServAccountingNoRecord
}
STATUS current
DESCRIPTION
"The collection of objects providing management of
a RADIUS Server."
::= { radiusServMIBGroups 1 }
END
7. Security considerations
All MIB variables described in this document are read-only.
8. Acknowledgments
Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, and
Peter Heitman of American Internet Corporation 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 2058, Livingston, Merit,
Daydreamer, January, 1997.
[2] C. Rigney. "RADIUS Accounting." RFC 2059, Livingston, January,
1997.
Zorn & Aboba [Page 7]
INTERNET-DRAFT 25 March 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
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, Inc., 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.
Zorn & Aboba [Page 8]
INTERNET-DRAFT 25 March 1997
10. Authors' Addresses
Glen Zorn
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 206-703-1559
EMail: glennz@microsoft.com
Bernard Aboba
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 206-936-6605
EMail: bernarda@microsoft.com
Zorn & Aboba [Page 9]
