1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
|
<pre>Network Working Group G. Zorn
Request for Comments: 2621 B. Aboba
Category: Informational Microsoft
June 1999
<span class="h1">RADIUS Accounting Server MIB</span>
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.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMP Management Framework</span>
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in <a href="./rfc2571">RFC 2571</a> [<a href="#ref-1" title=""An Architecture for Describing SNMP Management Frameworks"">1</a>].
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
<span class="grey">Zorn & Aboba Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
STD 15, <a href="./rfc1155">RFC 1155</a> [<a href="#ref-2" title=""Structure and Identification of Management Information for TCP/IP-based Internets"">2</a>], STD 16, <a href="./rfc1212">RFC 1212</a> [<a href="#ref-3" title=""Concise MIB Definitions"">3</a>] and <a href="./rfc1215">RFC 1215</a> [<a href="#ref-4" title=""A Convention for Defining Traps for use with the SNMP"">4</a>].
The second version, called SMIv2, is described in STD 58, <a href="./rfc2578">RFC</a>
<a href="./rfc2578">2578</a> [<a href="#ref-5" title=""Structure of Management Information Version 2 (SMIv2)"">5</a>], <a href="./rfc2579">RFC 2579</a> [<a href="#ref-6" title=""Textual Conventions for SMIv2"">6</a>] and <a href="./rfc2580">RFC 2580</a> [<a href="#ref-7" title=""Conformance Statements for SMIv2"">7</a>].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title=""Simple Network Management Protocol"">8</a>]. A second version of the
SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in <a href="./rfc1901">RFC 1901</a>
[<a href="#ref-9" title=""Introduction to Community-based SNMPv2"">9</a>] and <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title=""Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)"">10</a>]. The third version of the message
protocol is called SNMPv3 and described in <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title=""Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)"">10</a>], <a href="./rfc2572">RFC</a>
<a href="./rfc2572">2572</a> [<a href="#ref-11" title=""Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)"">11</a>] and <a href="./rfc2574">RFC 2574</a> [<a href="#ref-12" title=""User-based Security Model for Version 3 of the Simple Network Management Protocol (SNMPv3)"">12</a>].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title=""Simple Network Management Protocol"">8</a>]. A second set of protocol
operations and associated PDU formats is described in <a href="./rfc1905">RFC 1905</a>
[<a href="#ref-13" title=""Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)"">13</a>].
o A set of fundamental applications described in <a href="./rfc2573">RFC 2573</a> [<a href="#ref-14" title=""SNMP Applications"">14</a>] and
the view-based access control mechanism described in <a href="./rfc2575">RFC 2575</a>
[<a href="#ref-15" title=""View-based Access Control Model for the Simple Network Management Protocol (SNMP)"">15</a>].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span>
The RADIUS accounting protocol, described in [<a href="#ref-16" title=""RADIUS Accounting"">16</a>], 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
function, and thus would be expected to implement the RADIUS
accounting client MIB, while RADIUS accounting servers implement the
server function, and thus would be expected to implement the RADIUS
accounting server MIB.
<span class="grey">Zorn & Aboba Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
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.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Selected objects</span>
This MIB module contains thirteen 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
columns presenting a view of the activity of the RADIUS accounting
server.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span>
RADIUS-ACC-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32,
IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusAccServMIB MODULE-IDENTITY
LAST-UPDATED "9906110000Z" -- 11 Jun 1999
ORGANIZATION "IETF RADIUS Working Group."
CONTACT-INFO
" Bernard Aboba
Microsoft
One Microsoft Way
Redmond, WA 98052
US
Phone: +1 425 936 6605
EMail: bernarda@microsoft.com"
DESCRIPTION
"The MIB module for entities implementing the server
side of the Remote Access Dialin User Service (RADIUS)
accounting protocol."
REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in <a href="./rfc2621">RFC 2621</a>"
<span class="grey">Zorn & Aboba Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
::= { radiusAccounting 1 }
radiusMIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 67 }
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
radiusAccServMIBObjects OBJECT IDENTIFIER ::=
{ radiusAccServMIB 1 }
radiusAccServ OBJECT IDENTIFIER ::= { radiusAccServMIBObjects 1 }
radiusAccServIdent OBJECT-TYPE
SYNTAX SnmpAdminString
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 TimeTicks
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 (in hundredths of a
second) since the server process was started.
For software without persistent state, this value will
be zero."
::= {radiusAccServ 2}
radiusAccServResetTime OBJECT-TYPE
SYNTAX TimeTicks
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 (in hundredths of a second) since the
server was `reset.' For software that does not
have persistence or does not support a `reset' operation,
<span class="grey">Zorn & Aboba Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
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
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}
-- New Stats proposed by Dale E. Reed Jr (daler@iea.com)
radiusAccServTotalRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received on the
accounting port."
::= { radiusAccServ 5 }
radiusAccServTotalInvalidRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
received from unknown addresses."
::= { radiusAccServ 6 }
radiusAccServTotalDupRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate RADIUS Accounting-Request
<span class="grey">Zorn & Aboba Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
packets received."
::= { radiusAccServ 7 }
radiusAccServTotalResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response packets sent."
::= { radiusAccServ 8 }
radiusAccServTotalMalformedRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of malformed RADIUS Accounting-Request
packets received. Bad authenticators or unknown
types are not included as malformed Access-Requests."
::= { radiusAccServ 9 }
radiusAccServTotalBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
which contained invalid Signature attributes."
::= { radiusAccServ 10 }
radiusAccServTotalPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming packets silently discarded
for a reason other than malformed, bad authenticators,
or unknown types."
::= { radiusAccServ 11 }
radiusAccServTotalNoRecords OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
which were received and responded to but not
recorded."
<span class="grey">Zorn & Aboba Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
::= { radiusAccServ 12 }
radiusAccServTotalUnknownTypes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknowntype which
were received."
::= { radiusAccServ 13 }
-- End of new
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 14 }
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 SnmpAdminString,
radiusAccServPacketsDropped Counter32,
radiusAccServRequests Counter32,
radiusAccServDupRequests Counter32,
radiusAccServResponses Counter32,
radiusAccServBadAuthenticators Counter32,
radiusAccServMalformedRequests Counter32,
radiusAccServNoRecords Counter32,
radiusAccServUnknownTypes Counter32
}
radiusAccClientIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
<span class="grey">Zorn & Aboba Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying each RADIUS accounting
client with which this server communicates."
::= { 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 SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client
referred to in this table entry. This is not necessarily
the same as sysName in MIB II."
::= { radiusAccClientEntry 3 }
-- Server Counters
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - Responses = Pending
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - NoRecords = entries logged
radiusAccServPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming packets received
from this client and silently discarded
for a reason other than malformed, bad
authenticators, or unknown types."
::= { radiusAccClientEntry 4 }
radiusAccServRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
<span class="grey">Zorn & Aboba Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
STATUS current
DESCRIPTION
"The number of packets received from this
client on the accounting port."
::= { radiusAccClientEntry 5 }
radiusAccServDupRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of duplicate RADIUS Accounting-Request
packets received from this client."
::= { radiusAccClientEntry 6 }
radiusAccServResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response packets
sent to this client."
::= { radiusAccClientEntry 7 }
radiusAccServBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
which contained invalid authenticators received
from this client."
::= { radiusAccClientEntry 8 }
radiusAccServMalformedRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of malformed RADIUS Accounting-Request
packets which were received from this client.
Bad authenticators and unknown types
are not included as malformed Accounting-Requests."
::= { radiusAccClientEntry 9 }
radiusAccServNoRecords OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
<span class="grey">Zorn & Aboba Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
which were received and responded to but not
recorded."
::= { radiusAccClientEntry 10 }
radiusAccServUnknownTypes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknown type which
were received from this client."
::= { radiusAccClientEntry 11 }
-- conformance information
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 }
OBJECT radiusAccServConfigReset
WRITE-SYNTAX INTEGER { reset(2) }
DESCRIPTION "The only SETable value is 'reset' (2)."
::= { radiusAccServMIBCompliances 1 }
-- units of conformance
radiusAccServMIBGroup OBJECT-GROUP
OBJECTS {radiusAccServIdent,
radiusAccServUpTime,
<span class="grey">Zorn & Aboba Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
radiusAccServResetTime,
radiusAccServConfigReset,
radiusAccServTotalRequests,
radiusAccServTotalInvalidRequests,
radiusAccServTotalDupRequests,
radiusAccServTotalResponses,
radiusAccServTotalMalformedRequests,
radiusAccServTotalBadAuthenticators,
radiusAccServTotalPacketsDropped,
radiusAccServTotalNoRecords,
radiusAccServTotalUnknownTypes,
radiusAccClientAddress,
radiusAccClientID,
radiusAccServPacketsDropped,
radiusAccServRequests,
radiusAccServDupRequests,
radiusAccServResponses,
radiusAccServBadAuthenticators,
radiusAccServMalformedRequests,
radiusAccServNoRecords,
radiusAccServUnknownTypes
}
STATUS current
DESCRIPTION
"The collection of objects providing management of
a RADIUS Accounting Server."
::= { radiusAccServMIBGroups 1 }
END
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
[<a id="ref-1">1</a>] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", <a href="./rfc2571">RFC 2571</a>, April
1999.
[<a id="ref-2">2</a>] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, <a href="./rfc1155">RFC</a>
<a href="./rfc1155">1155</a>, May 1990.
[<a id="ref-3">3</a>] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
<a href="./rfc1212">RFC 1212</a>, March 1991.
[<a id="ref-4">4</a>] Rose, M., "A Convention for Defining Traps for use with the
SNMP", <a href="./rfc1215">RFC 1215</a>, Performance Systems International, March 1991.
<span class="grey">Zorn & Aboba Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
[<a id="ref-5">5</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M. and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
[<a id="ref-6">6</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
<a href="./rfc2579">RFC 2579</a>, April 1999.
[<a id="ref-7">7</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
58, <a href="./rfc2580">RFC 2580</a>, April 1999.
[<a id="ref-8">8</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, May 1990.
[<a id="ref-9">9</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", <a href="./rfc1901">RFC 1901</a>, January
1996.
[<a id="ref-10">10</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
[<a id="ref-11">11</a>] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", <a href="./rfc2572">RFC 2572</a>, April 1999.
[<a id="ref-12">12</a>] Blumenthal, U., and B. Wijnen, "User-based Security Model for
Version 3 of the Simple Network Management Protocol (SNMPv3)",
<a href="./rfc2574">RFC 2574</a>, April 1999.
[<a id="ref-13">13</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
[<a id="ref-14">14</a>] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", <a href="./rfc2573">RFC</a>
<a href="./rfc2573">2573</a>, April 1999.
[<a id="ref-15">15</a>] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model for the Simple Network Management Protocol
(SNMP)", <a href="./rfc2575">RFC 2575</a>, April 1999.
[<a id="ref-16">16</a>] Rigney, C., "RADIUS Accounting", <a href="./rfc2139">RFC 2139</a>, April 1997.
<span class="grey">Zorn & Aboba Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
There are management objects (radiusAccServConfigReset) defined in
this MIB that have a MAX-ACCESS clause of read-write and/or read-
create. Such objects may be considered sensitive or vulnerable in
some network environments. The support for SET operations in a non-
secure environment without proper protection can have a negative
effect on network operations.
There are a number of managed objects in this MIB that may contain
sensitive information. These are:
radiusAccClientAddress
This can be used to determine the address of the RADIUS
accounting client with which the server is communicating.
This information could be useful in impersonating the
client.
radiusAccClientID This can be used to determine the client ID for the
accounting client with which the server is communicating.
This information could be useful in impersonating the
client.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), there is no control as
to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model <a href="./rfc2574">RFC 2574</a> [<a href="#ref-12" title=""User-based Security Model for Version 3 of the Simple Network Management Protocol (SNMPv3)"">12</a>] and the View-based
Access Control Model <a href="./rfc2575">RFC 2575</a> [<a href="#ref-15" title=""View-based Access Control Model for the Simple Network Management Protocol (SNMP)"">15</a>] is recommended. Using these
security features, customer/users can give access to the objects only
to those principals (users) that have legitimate rights to GET or SET
(change/create/delete) them.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
The authors acknowledge the contributions of the RADIUS Working Group
in the development of this MIB. Thanks to Narendra Gidwani of
Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston and
Peter Heitman of American Internet Corporation for useful discussions
of this problem space.
<span class="grey">Zorn & Aboba Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span>
Bernard Aboba
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 425-936-6605
EMail: bernarda@microsoft.com
Glen Zorn
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Phone: 425-703-1559
EMail: glennz@microsoft.com
<span class="grey">Zorn & Aboba Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc2621">RFC 2621</a> RADIUS Accounting Server MIB June 1999</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Zorn & Aboba Informational [Page 15]
</pre>
|
