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))
248
snmpTargetSpinLock OBJECT-TYPE
250
MAX-ACCESS read-write
253
"This object is used to facilitate modification of table
254
entries in the SNMP-TARGET-MIB module by multiple
255
managers. In particular, it is useful when modifying
256
the value of the snmpTargetAddrTagList object.
258
The procedure for modifying the snmpTargetAddrTagList
259
object is as follows:
261
1. Retrieve the value of snmpTargetSpinLock and
262
of snmpTargetAddrTagList.
264
2. Generate a new value for snmpTargetAddrTagList.
266
3. Set the value of snmpTargetSpinLock to the
267
retrieved value, and the value of
268
snmpTargetAddrTagList to the new value. If
269
the set fails for the snmpTargetSpinLock
270
object, go back to step 1."
271
::= { snmpTargetObjects 1 }
273
snmpTargetAddrTable OBJECT-TYPE
274
SYNTAX SEQUENCE OF SnmpTargetAddrEntry
275
MAX-ACCESS not-accessible
278
"A table of transport addresses to be used in the generation
280
::= { snmpTargetObjects 2 }
282
snmpTargetAddrEntry OBJECT-TYPE
283
SYNTAX SnmpTargetAddrEntry
284
MAX-ACCESS not-accessible
287
"A transport address to be used in the generation
290
Entries in the snmpTargetAddrTable are created and
291
deleted using the snmpTargetAddrRowStatus object."
292
INDEX { IMPLIED snmpTargetAddrName }
293
::= { snmpTargetAddrTable 1 }
295
SnmpTargetAddrEntry ::= SEQUENCE {
296
snmpTargetAddrName SnmpAdminString,
297
snmpTargetAddrTDomain TDomain,
298
snmpTargetAddrTAddress TAddress,
299
snmpTargetAddrTimeout TimeInterval,
300
snmpTargetAddrRetryCount Integer32,
301
snmpTargetAddrTagList SnmpTagList,
302
snmpTargetAddrParams SnmpAdminString,
303
snmpTargetAddrStorageType StorageType,
304
snmpTargetAddrRowStatus RowStatus
307
snmpTargetAddrName OBJECT-TYPE
308
SYNTAX SnmpAdminString (SIZE(1..32))
309
MAX-ACCESS not-accessible
312
"The locally arbitrary, but unique identifier associated
313
with this snmpTargetAddrEntry."
314
::= { snmpTargetAddrEntry 1 }
316
snmpTargetAddrTDomain OBJECT-TYPE
318
MAX-ACCESS read-create
321
"This object indicates the transport type of the address
322
contained in the snmpTargetAddrTAddress object."
323
::= { snmpTargetAddrEntry 2 }
325
snmpTargetAddrTAddress OBJECT-TYPE
327
MAX-ACCESS read-create
330
"This object contains a transport address. The format of
331
this address depends on the value of the
332
snmpTargetAddrTDomain object."
333
::= { snmpTargetAddrEntry 3 }
335
snmpTargetAddrTimeout OBJECT-TYPE
337
MAX-ACCESS read-create
340
"This object should reflect the expected maximum round
341
trip time for communicating with the transport address
342
defined by this row. When a message is sent to this
343
address, and a response (if one is expected) is not
344
received within this time period, an implementation
345
may assume that the response will not be delivered.
347
Note that the time interval that an application waits
348
for a response may actually be derived from the value
349
of this object. The method for deriving the actual time
350
interval is implementation dependent. One such method
351
is to derive the expected round trip time based on a
352
particular retransmission algorithm and on the number
353
of timeouts which have occurred. The type of message may
354
also be considered when deriving expected round trip
355
times for retransmissions. For example, if a message is
356
being sent with a securityLevel that indicates both
358
authentication and privacy, the derived value may be
359
increased to compensate for extra processing time spent
360
during authentication and encryption processing."
362
::= { snmpTargetAddrEntry 4 }
364
snmpTargetAddrRetryCount OBJECT-TYPE
365
SYNTAX Integer32 (0..255)
366
MAX-ACCESS read-create
369
"This object specifies a default number of retries to be
370
attempted when a response is not received for a generated
371
message. An application may provide its own retry count,
372
in which case the value of this object is ignored."
374
::= { snmpTargetAddrEntry 5 }
376
snmpTargetAddrTagList OBJECT-TYPE
378
MAX-ACCESS read-create
381
"This object contains a list of tag values which are
382
used to select target addresses for a particular
385
::= { snmpTargetAddrEntry 6 }
387
snmpTargetAddrParams OBJECT-TYPE
388
SYNTAX SnmpAdminString (SIZE(1..32))
389
MAX-ACCESS read-create
392
"The value of this object identifies an entry in the
393
snmpTargetParamsTable. The identified entry
394
contains SNMP parameters to be used when generating
395
messages to be sent to this transport address."
396
::= { snmpTargetAddrEntry 7 }
398
snmpTargetAddrStorageType OBJECT-TYPE
400
MAX-ACCESS read-create
403
"The storage type for this conceptual row.
404
Conceptual rows having the value 'permanent' need not
405
allow write-access to any columnar objects in the row."
406
DEFVAL { nonVolatile }
407
::= { snmpTargetAddrEntry 8 }
409
snmpTargetAddrRowStatus OBJECT-TYPE
411
MAX-ACCESS read-create
414
"The status of this conceptual row.
416
To create a row in this table, a manager must
417
set this object to either createAndGo(4) or
420
Until instances of all corresponding columns are
421
appropriately configured, the value of the
422
corresponding instance of the snmpTargetAddrRowStatus
423
column is 'notReady'.
425
In particular, a newly created row cannot be made
426
active until the corresponding instances of
427
snmpTargetAddrTDomain, snmpTargetAddrTAddress, and
428
snmpTargetAddrParams have all been set.
430
The following objects may not be modified while the
431
value of this object is active(1):
432
- snmpTargetAddrTDomain
433
- snmpTargetAddrTAddress
434
An attempt to set these objects while the value of
435
snmpTargetAddrRowStatus is active(1) will result in
436
an inconsistentValue error."
437
::= { snmpTargetAddrEntry 9 }
439
snmpTargetParamsTable OBJECT-TYPE
440
SYNTAX SEQUENCE OF SnmpTargetParamsEntry
441
MAX-ACCESS not-accessible
444
"A table of SNMP target information to be used
445
in the generation of SNMP messages."
446
::= { snmpTargetObjects 3 }
448
snmpTargetParamsEntry OBJECT-TYPE
449
SYNTAX SnmpTargetParamsEntry
450
MAX-ACCESS not-accessible
453
"A set of SNMP target information.
455
Entries in the snmpTargetParamsTable are created and
456
deleted using the snmpTargetParamsRowStatus object."
457
INDEX { IMPLIED snmpTargetParamsName }
458
::= { snmpTargetParamsTable 1 }
460
SnmpTargetParamsEntry ::= SEQUENCE {
461
snmpTargetParamsName SnmpAdminString,
462
snmpTargetParamsMPModel SnmpMessageProcessingModel,
463
snmpTargetParamsSecurityModel SnmpSecurityModel,
464
snmpTargetParamsSecurityName SnmpAdminString,
465
snmpTargetParamsSecurityLevel SnmpSecurityLevel,
466
snmpTargetParamsStorageType StorageType,
467
snmpTargetParamsRowStatus RowStatus
470
snmpTargetParamsName OBJECT-TYPE
471
SYNTAX SnmpAdminString (SIZE(1..32))
472
MAX-ACCESS not-accessible
475
"The locally arbitrary, but unique identifier associated
476
with this snmpTargetParamsEntry."
477
::= { snmpTargetParamsEntry 1 }
479
snmpTargetParamsMPModel OBJECT-TYPE
480
SYNTAX SnmpMessageProcessingModel
481
MAX-ACCESS read-create
484
"The Message Processing Model to be used when generating
485
SNMP messages using this entry."
486
::= { snmpTargetParamsEntry 2 }
488
snmpTargetParamsSecurityModel OBJECT-TYPE
489
SYNTAX SnmpSecurityModel (1..2147483647)
490
MAX-ACCESS read-create
493
"The Security Model to be used when generating SNMP
494
messages using this entry. An implementation may
495
choose to return an inconsistentValue error if an
496
attempt is made to set this variable to a value
497
for a security model which the implementation does
499
::= { snmpTargetParamsEntry 3 }
501
snmpTargetParamsSecurityName OBJECT-TYPE
502
SYNTAX SnmpAdminString
503
MAX-ACCESS read-create
506
"The securityName which identifies the Principal on
507
whose behalf SNMP messages will be generated using
509
::= { snmpTargetParamsEntry 4 }
511
snmpTargetParamsSecurityLevel OBJECT-TYPE
512
SYNTAX SnmpSecurityLevel
513
MAX-ACCESS read-create
516
"The Level of Security to be used when generating
517
SNMP messages using this entry."
518
::= { snmpTargetParamsEntry 5 }
520
snmpTargetParamsStorageType OBJECT-TYPE
522
MAX-ACCESS read-create
525
"The storage type for this conceptual row.
526
Conceptual rows having the value 'permanent' need not
527
allow write-access to any columnar objects in the row."
528
DEFVAL { nonVolatile }
529
::= { snmpTargetParamsEntry 6 }
531
snmpTargetParamsRowStatus OBJECT-TYPE
533
MAX-ACCESS read-create
536
"The status of this conceptual row.
538
To create a row in this table, a manager must
539
set this object to either createAndGo(4) or
542
Until instances of all corresponding columns are
543
appropriately configured, the value of the
544
corresponding instance of the snmpTargetParamsRowStatus
545
column is 'notReady'.
547
In particular, a newly created row cannot be made
548
active until the corresponding
549
snmpTargetParamsMPModel,
550
snmpTargetParamsSecurityModel,
551
snmpTargetParamsSecurityName,
552
and snmpTargetParamsSecurityLevel have all been set.
554
The following objects may not be modified while the
555
value of this object is active(1):
556
- snmpTargetParamsMPModel
557
- snmpTargetParamsSecurityModel
558
- snmpTargetParamsSecurityName
559
- snmpTargetParamsSecurityLevel
560
An attempt to set these objects while the value of
561
snmpTargetParamsRowStatus is active(1) will result in
562
an inconsistentValue error."
563
::= { snmpTargetParamsEntry 7 }
565
snmpUnavailableContexts OBJECT-TYPE
570
"The total number of packets received by the SNMP
571
engine which were dropped because the context
572
contained in the message was unavailable."
573
::= { snmpTargetObjects 4 }
575
snmpUnknownContexts OBJECT-TYPE
580
"The total number of packets received by the SNMP
581
engine which were dropped because the context
582
contained in the message was unknown."
583
::= { snmpTargetObjects 5 }
590
snmpTargetCompliances OBJECT IDENTIFIER ::=
591
{ snmpTargetConformance 1 }
592
snmpTargetGroups OBJECT IDENTIFIER ::=
593
{ snmpTargetConformance 2 }
601
snmpTargetCommandResponderCompliance MODULE-COMPLIANCE
604
"The compliance statement for SNMP entities which include
605
a command responder application."
606
MODULE -- This Module
607
MANDATORY-GROUPS { snmpTargetCommandResponderGroup }
608
::= { snmpTargetCompliances 1 }
610
snmpTargetBasicGroup OBJECT-GROUP
613
snmpTargetAddrTDomain,
614
snmpTargetAddrTAddress,
615
snmpTargetAddrTagList,
616
snmpTargetAddrParams,
617
snmpTargetAddrStorageType,
618
snmpTargetAddrRowStatus,
619
snmpTargetParamsMPModel,
620
snmpTargetParamsSecurityModel,
621
snmpTargetParamsSecurityName,
622
snmpTargetParamsSecurityLevel,
623
snmpTargetParamsStorageType,
624
snmpTargetParamsRowStatus
628
"A collection of objects providing basic remote
629
configuration of management targets."
630
::= { snmpTargetGroups 1 }
632
snmpTargetResponseGroup OBJECT-GROUP
634
snmpTargetAddrTimeout,
635
snmpTargetAddrRetryCount
639
"A collection of objects providing remote configuration
640
of management targets for applications which generate
641
SNMP messages for which a response message would be
643
::= { snmpTargetGroups 2 }
645
snmpTargetCommandResponderGroup OBJECT-GROUP
648
snmpUnavailableContexts,
653
"A collection of objects required for command responder
654
applications, used for counting error conditions."
655
::= { snmpTargetGroups 3 }
added
removed
mibs/SNMP-TARGET-MIB.txt
