Browse Prior Art Database

RADIUS Accounting Server MIB (RFC2621)

IP.com Disclosure Number: IPCOM000003208D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 12 page(s) / 26K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Zorn: AUTHOR [+2]

Abstract

This memo defines a set of extensions which instrument RADIUS accounting 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 accounting servers.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group G. Zorn

Request for Comments: 2621 B. Aboba

Category: Informational Microsoft

June 1999

RADIUS Accounting Server MIB

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This memo defines a set of extensions which instrument RADIUS

accounting 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 accounting servers.

1. 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.

2. The SNMP Management Framework

The SNMP Management Framework presently consists of five major

components:

o An overall architecture, described in RFC 2571 [1].

o Mechanisms for describing and naming objects and events for the

purpose of management. The first version of this Structure of

Management Information (SMI) is called SMIv1 and described in

STD 15, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].

The second version, called SMIv2, is described in STD 58, RFC

2578 [5], RFC 2579 [6] and RFC 2580 [7].

o Message protocols for transferring management information. The

first version of the SNMP message protocol is called SNMPv1 and

described in STD 15, RFC 1157 [8]. A second version of the

SNMP message protocol, which is not an Internet standards

track protocol, is called SNMPv2c and described in RFC 1901

[9] and RFC 1906 [10]. The third version of the message

protocol is called SNMPv3 and described in RFC 1906 [10], RFC

2572 [11] and RFC 2574 [12].

o Protocol operations for accessing management information. The

first set of protocol operations and associated ...