1
SNMP-TARGET-MIB DEFINITIONS ::= BEGIN
21
SnmpMessageProcessingModel,
24
FROM SNMP-FRAMEWORK-MIB
30
snmpTargetMIB MODULE-IDENTITY
31
LAST-UPDATED "200210140000Z"
32
ORGANIZATION "IETF SNMPv3 Working Group"
34
"WG-email: snmpv3@lists.tislabs.com
35
Subscribe: majordomo@lists.tislabs.com
36
In message body: subscribe snmpv3
39
Network Associates Laboratories
40
Postal: 15204 Omega Drive, Suite 300
41
Rockville, MD 20850-4601
43
EMail: mundy@tislabs.com
44
Phone: +1 301-947-7107
46
Co-Chair: David Harrington
48
Postal: 35 Industrial Way
50
Rochester, New Hampshire 03866-5005
52
EMail: dbh@enterasys.com
53
Phone: +1 603-337-2614
55
Co-editor: David B. Levi
57
Postal: 3505 Kesterwood Drive
58
Knoxville, Tennessee 37918
59
EMail: dlevi@nortelnetworks.com
60
Phone: +1 865 686 0432
63
Secure Computing Corporation
64
Postal: 2675 Long Lake Road
66
Roseville, Minnesota 55113
67
EMail: paul_meyer@securecomputing.com
68
Phone: +1 651 628 1592
70
Co-editor: Bob Stewart
73
"This MIB module defines MIB objects which provide
74
mechanisms to remotely configure the parameters used
75
by an SNMP entity for the generation of SNMP messages.
77
Copyright (C) The Internet Society (2002). This
78
version of this MIB module is part of RFC 3413;
79
see the RFC itself for full legal notices.
81
REVISION "200210140000Z" -- 14 October 2002
82
DESCRIPTION "Fixed DISPLAY-HINTS for UTF-8 strings, fixed hex
83
value of LF characters, clarified meaning of zero
84
length tag values, improved tag list examples.
85
Published as RFC 3413."
86
REVISION "199808040000Z" -- 4 August 1998
87
DESCRIPTION "Clarifications, published as
89
REVISION "199707140000Z" -- 14 July 1997
90
DESCRIPTION "The initial revision, published as RFC2273."
91
::= { snmpModules 12 }
93
snmpTargetObjects OBJECT IDENTIFIER ::= { snmpTargetMIB 1 }
94
snmpTargetConformance OBJECT IDENTIFIER ::= { snmpTargetMIB 3 }
96
SnmpTagValue ::= TEXTUAL-CONVENTION
100
"An octet string containing a tag value.
101
Tag values are preferably in human-readable form.
103
To facilitate internationalization, this information
104
is represented using the ISO/IEC IS 10646-1 character
105
set, encoded as an octet string using the UTF-8
106
character encoding scheme described in RFC 2279.
108
Since additional code points are added by amendments
109
to the 10646 standard from time to time,
110
implementations must be prepared to encounter any code
111
point from 0x00000000 to 0x7fffffff.
113
The use of control codes should be avoided, and certain
115
control codes are not allowed as described below.
117
For code points not directly supported by user
118
interface hardware or software, an alternative means
119
of entry and display, such as hexadecimal, may be
122
For information encoded in 7-bit US-ASCII, the UTF-8
123
representation is identical to the US-ASCII encoding.
125
Note that when this TC is used for an object that
126
is used or envisioned to be used as an index, then a
127
SIZE restriction must be specified so that the number
128
of sub-identifiers for any object instance does not
129
exceed the limit of 128, as defined by [RFC1905].
131
An object of this type contains a single tag value
132
which is used to select a set of entries in a table.
134
A tag value is an arbitrary string of octets, but
135
may not contain a delimiter character. Delimiter
136
characters are defined to be one of the following:
138
- An ASCII space character (0x20).
140
- An ASCII TAB character (0x09).
142
- An ASCII carriage return (CR) character (0x0D).
144
- An ASCII line feed (LF) character (0x0A).
146
Delimiter characters are used to separate tag values
147
in a tag list. An object of this type may only
148
contain a single tag value, and so delimiter
149
characters are not allowed in a value of this type.
151
Note that a tag value of 0 length means that no tag is
152
defined. In other words, a tag value of 0 length would
153
never match anything in a tag list, and would never
154
select any table entries.
156
Some examples of valid tag values are:
164
The use of a tag value to select table entries is
165
application and MIB specific."
166
SYNTAX OCTET STRING (SIZE (0..255))
168
SnmpTagList ::= TEXTUAL-CONVENTION
172
"An octet string containing a list of tag values.
173
Tag values are preferably in human-readable form.
175
To facilitate internationalization, this information
176
is represented using the ISO/IEC IS 10646-1 character
177
set, encoded as an octet string using the UTF-8
178
character encoding scheme described in RFC 2279.
180
Since additional code points are added by amendments
181
to the 10646 standard from time to time,
182
implementations must be prepared to encounter any code
183
point from 0x00000000 to 0x7fffffff.
185
The use of control codes should be avoided, except as
188
For code points not directly supported by user
189
interface hardware or software, an alternative means
190
of entry and display, such as hexadecimal, may be
193
For information encoded in 7-bit US-ASCII, the UTF-8
194
representation is identical to the US-ASCII encoding.
196
An object of this type contains a list of tag values
197
which are used to select a set of entries in a table.
199
A tag value is an arbitrary string of octets, but
200
may not contain a delimiter character. Delimiter
201
characters are defined to be one of the following:
203
- An ASCII space character (0x20).
205
- An ASCII TAB character (0x09).
207
- An ASCII carriage return (CR) character (0x0D).
209
- An ASCII line feed (LF) character (0x0A).
211
Delimiter characters are used to separate tag values
213
in a tag list. Only a single delimiter character may
214
occur between two tag values. A tag value may not
215
have a zero length. These constraints imply certain
216
restrictions on the contents of this object:
218
- There cannot be a leading or trailing delimiter
221
- There cannot be multiple adjacent delimiter
224
Some examples of valid tag lists are:
226
- '' -- an empty list
228
- 'acme' -- list of one tag
230
- 'host router bridge' -- list of several tags
232
Note that although a tag value may not have a length of
233
zero, an empty string is still valid. This indicates
234
an empty list (i.e. there are no tag values in the list).
236
The use of the tag list to select table entries is
237
application and MIB specific. Typically, an application
238
will provide one or more tag values, and any entry
239
which contains some combination of these tag values
241
SYNTAX OCTET STRING (SIZE (0..255))
245
-- The snmpTargetObjects group
249
snmpTargetSpinLock OBJECT-TYPE
251
MAX-ACCESS read-write
254
"This object is used to facilitate modification of table
255
entries in the SNMP-TARGET-MIB module by multiple
256
managers. In particular, it is useful when modifying
257
the value of the snmpTargetAddrTagList object.
259
The procedure for modifying the snmpTargetAddrTagList
260
object is as follows:
262
1. Retrieve the value of snmpTargetSpinLock and
263
of snmpTargetAddrTagList.
265
2. Generate a new value for snmpTargetAddrTagList.
267
3. Set the value of snmpTargetSpinLock to the
268
retrieved value, and the value of
269
snmpTargetAddrTagList to the new value. If
270
the set fails for the snmpTargetSpinLock
271
object, go back to step 1."
272
::= { snmpTargetObjects 1 }
274
snmpTargetAddrTable OBJECT-TYPE
275
SYNTAX SEQUENCE OF SnmpTargetAddrEntry
276
MAX-ACCESS not-accessible
279
"A table of transport addresses to be used in the generation
281
::= { snmpTargetObjects 2 }
283
snmpTargetAddrEntry OBJECT-TYPE
284
SYNTAX SnmpTargetAddrEntry
285
MAX-ACCESS not-accessible
288
"A transport address to be used in the generation
291
Entries in the snmpTargetAddrTable are created and
292
deleted using the snmpTargetAddrRowStatus object."
293
INDEX { IMPLIED snmpTargetAddrName }
294
::= { snmpTargetAddrTable 1 }
296
SnmpTargetAddrEntry ::= SEQUENCE {
297
snmpTargetAddrName SnmpAdminString,
298
snmpTargetAddrTDomain TDomain,
299
snmpTargetAddrTAddress TAddress,
300
snmpTargetAddrTimeout TimeInterval,
301
snmpTargetAddrRetryCount Integer32,
302
snmpTargetAddrTagList SnmpTagList,
303
snmpTargetAddrParams SnmpAdminString,
304
snmpTargetAddrStorageType StorageType,
305
snmpTargetAddrRowStatus RowStatus
308
snmpTargetAddrName OBJECT-TYPE
309
SYNTAX SnmpAdminString (SIZE(1..32))
310
MAX-ACCESS not-accessible
313
"The locally arbitrary, but unique identifier associated
314
with this snmpTargetAddrEntry."
315
::= { snmpTargetAddrEntry 1 }
317
snmpTargetAddrTDomain OBJECT-TYPE
319
MAX-ACCESS read-create
322
"This object indicates the transport type of the address
323
contained in the snmpTargetAddrTAddress object."
324
::= { snmpTargetAddrEntry 2 }
326
snmpTargetAddrTAddress OBJECT-TYPE
328
MAX-ACCESS read-create
331
"This object contains a transport address. The format of
332
this address depends on the value of the
333
snmpTargetAddrTDomain object."
334
::= { snmpTargetAddrEntry 3 }
336
snmpTargetAddrTimeout OBJECT-TYPE
338
MAX-ACCESS read-create
341
"This object should reflect the expected maximum round
342
trip time for communicating with the transport address
343
defined by this row. When a message is sent to this
344
address, and a response (if one is expected) is not
345
received within this time period, an implementation
346
may assume that the response will not be delivered.
348
Note that the time interval that an application waits
349
for a response may actually be derived from the value
350
of this object. The method for deriving the actual time
351
interval is implementation dependent. One such method
352
is to derive the expected round trip time based on a
353
particular retransmission algorithm and on the number
354
of timeouts which have occurred. The type of message may
355
also be considered when deriving expected round trip
356
times for retransmissions. For example, if a message is
357
being sent with a securityLevel that indicates both
359
authentication and privacy, the derived value may be
360
increased to compensate for extra processing time spent
361
during authentication and encryption processing."
363
::= { snmpTargetAddrEntry 4 }
365
snmpTargetAddrRetryCount OBJECT-TYPE
366
SYNTAX Integer32 (0..255)
367
MAX-ACCESS read-create
370
"This object specifies a default number of retries to be
371
attempted when a response is not received for a generated
372
message. An application may provide its own retry count,
373
in which case the value of this object is ignored."
375
::= { snmpTargetAddrEntry 5 }
377
snmpTargetAddrTagList OBJECT-TYPE
379
MAX-ACCESS read-create
382
"This object contains a list of tag values which are
383
used to select target addresses for a particular
386
::= { snmpTargetAddrEntry 6 }
388
snmpTargetAddrParams OBJECT-TYPE
389
SYNTAX SnmpAdminString (SIZE(1..32))
390
MAX-ACCESS read-create
393
"The value of this object identifies an entry in the
394
snmpTargetParamsTable. The identified entry
395
contains SNMP parameters to be used when generating
396
messages to be sent to this transport address."
397
::= { snmpTargetAddrEntry 7 }
399
snmpTargetAddrStorageType OBJECT-TYPE
401
MAX-ACCESS read-create
404
"The storage type for this conceptual row.
405
Conceptual rows having the value 'permanent' need not
406
allow write-access to any columnar objects in the row."
407
DEFVAL { nonVolatile }
408
::= { snmpTargetAddrEntry 8 }
410
snmpTargetAddrRowStatus OBJECT-TYPE
412
MAX-ACCESS read-create
415
"The status of this conceptual row.
417
To create a row in this table, a manager must
418
set this object to either createAndGo(4) or
421
Until instances of all corresponding columns are
422
appropriately configured, the value of the
423
corresponding instance of the snmpTargetAddrRowStatus
424
column is 'notReady'.
426
In particular, a newly created row cannot be made
427
active until the corresponding instances of
428
snmpTargetAddrTDomain, snmpTargetAddrTAddress, and
429
snmpTargetAddrParams have all been set.
431
The following objects may not be modified while the
432
value of this object is active(1):
433
- snmpTargetAddrTDomain
434
- snmpTargetAddrTAddress
435
An attempt to set these objects while the value of
436
snmpTargetAddrRowStatus is active(1) will result in
437
an inconsistentValue error."
438
::= { snmpTargetAddrEntry 9 }
440
snmpTargetParamsTable OBJECT-TYPE
441
SYNTAX SEQUENCE OF SnmpTargetParamsEntry
442
MAX-ACCESS not-accessible
445
"A table of SNMP target information to be used
446
in the generation of SNMP messages."
447
::= { snmpTargetObjects 3 }
449
snmpTargetParamsEntry OBJECT-TYPE
450
SYNTAX SnmpTargetParamsEntry
451
MAX-ACCESS not-accessible
454
"A set of SNMP target information.
456
Entries in the snmpTargetParamsTable are created and
457
deleted using the snmpTargetParamsRowStatus object."
458
INDEX { IMPLIED snmpTargetParamsName }
459
::= { snmpTargetParamsTable 1 }
461
SnmpTargetParamsEntry ::= SEQUENCE {
462
snmpTargetParamsName SnmpAdminString,
463
snmpTargetParamsMPModel SnmpMessageProcessingModel,
464
snmpTargetParamsSecurityModel SnmpSecurityModel,
465
snmpTargetParamsSecurityName SnmpAdminString,
466
snmpTargetParamsSecurityLevel SnmpSecurityLevel,
467
snmpTargetParamsStorageType StorageType,
468
snmpTargetParamsRowStatus RowStatus
471
snmpTargetParamsName OBJECT-TYPE
472
SYNTAX SnmpAdminString (SIZE(1..32))
473
MAX-ACCESS not-accessible
476
"The locally arbitrary, but unique identifier associated
477
with this snmpTargetParamsEntry."
478
::= { snmpTargetParamsEntry 1 }
480
snmpTargetParamsMPModel OBJECT-TYPE
481
SYNTAX SnmpMessageProcessingModel
482
MAX-ACCESS read-create
485
"The Message Processing Model to be used when generating
486
SNMP messages using this entry."
487
::= { snmpTargetParamsEntry 2 }
489
snmpTargetParamsSecurityModel OBJECT-TYPE
490
SYNTAX SnmpSecurityModel (1..2147483647)
491
MAX-ACCESS read-create
494
"The Security Model to be used when generating SNMP
495
messages using this entry. An implementation may
496
choose to return an inconsistentValue error if an
497
attempt is made to set this variable to a value
498
for a security model which the implementation does
500
::= { snmpTargetParamsEntry 3 }
502
snmpTargetParamsSecurityName OBJECT-TYPE
503
SYNTAX SnmpAdminString
504
MAX-ACCESS read-create
507
"The securityName which identifies the Principal on
508
whose behalf SNMP messages will be generated using
510
::= { snmpTargetParamsEntry 4 }
512
snmpTargetParamsSecurityLevel OBJECT-TYPE
513
SYNTAX SnmpSecurityLevel
514
MAX-ACCESS read-create
517
"The Level of Security to be used when generating
518
SNMP messages using this entry."
519
::= { snmpTargetParamsEntry 5 }
521
snmpTargetParamsStorageType OBJECT-TYPE
523
MAX-ACCESS read-create
526
"The storage type for this conceptual row.
527
Conceptual rows having the value 'permanent' need not
528
allow write-access to any columnar objects in the row."
529
DEFVAL { nonVolatile }
530
::= { snmpTargetParamsEntry 6 }
532
snmpTargetParamsRowStatus OBJECT-TYPE
534
MAX-ACCESS read-create
537
"The status of this conceptual row.
539
To create a row in this table, a manager must
540
set this object to either createAndGo(4) or
543
Until instances of all corresponding columns are
544
appropriately configured, the value of the
545
corresponding instance of the snmpTargetParamsRowStatus
546
column is 'notReady'.
548
In particular, a newly created row cannot be made
549
active until the corresponding
550
snmpTargetParamsMPModel,
551
snmpTargetParamsSecurityModel,
552
snmpTargetParamsSecurityName,
553
and snmpTargetParamsSecurityLevel have all been set.
555
The following objects may not be modified while the
556
value of this object is active(1):
557
- snmpTargetParamsMPModel
558
- snmpTargetParamsSecurityModel
559
- snmpTargetParamsSecurityName
560
- snmpTargetParamsSecurityLevel
561
An attempt to set these objects while the value of
562
snmpTargetParamsRowStatus is active(1) will result in
563
an inconsistentValue error."
564
::= { snmpTargetParamsEntry 7 }
566
snmpUnavailableContexts OBJECT-TYPE
571
"The total number of packets received by the SNMP
572
engine which were dropped because the context
573
contained in the message was unavailable."
574
::= { snmpTargetObjects 4 }
576
snmpUnknownContexts OBJECT-TYPE
581
"The total number of packets received by the SNMP
582
engine which were dropped because the context
583
contained in the message was unknown."
584
::= { snmpTargetObjects 5 }
588
-- Conformance information
592
snmpTargetCompliances OBJECT IDENTIFIER ::=
593
{ snmpTargetConformance 1 }
594
snmpTargetGroups OBJECT IDENTIFIER ::=
595
{ snmpTargetConformance 2 }
599
-- Compliance statements
604
snmpTargetCommandResponderCompliance MODULE-COMPLIANCE
607
"The compliance statement for SNMP entities which include
608
a command responder application."
609
MODULE -- This Module
610
MANDATORY-GROUPS { snmpTargetCommandResponderGroup }
611
::= { snmpTargetCompliances 1 }
613
snmpTargetBasicGroup OBJECT-GROUP
616
snmpTargetAddrTDomain,
617
snmpTargetAddrTAddress,
618
snmpTargetAddrTagList,
619
snmpTargetAddrParams,
620
snmpTargetAddrStorageType,
621
snmpTargetAddrRowStatus,
622
snmpTargetParamsMPModel,
623
snmpTargetParamsSecurityModel,
624
snmpTargetParamsSecurityName,
625
snmpTargetParamsSecurityLevel,
626
snmpTargetParamsStorageType,
627
snmpTargetParamsRowStatus
631
"A collection of objects providing basic remote
632
configuration of management targets."
633
::= { snmpTargetGroups 1 }
635
snmpTargetResponseGroup OBJECT-GROUP
637
snmpTargetAddrTimeout,
638
snmpTargetAddrRetryCount
642
"A collection of objects providing remote configuration
643
of management targets for applications which generate
644
SNMP messages for which a response message would be
646
::= { snmpTargetGroups 2 }
648
snmpTargetCommandResponderGroup OBJECT-GROUP
651
snmpUnavailableContexts,
656
"A collection of objects required for command responder
657
applications, used for counting error conditions."
658
::= { snmpTargetGroups 3 }
added
removed
mibs/SNMP-TARGET-MIB.txt
