| 1 |
<pre>Network Working Group K. McCloghrie |
| 2 |
Request For Comments: 1303 Hughes LAN Systems |
| 3 |
M. Rose |
| 4 |
Dover Beach Consulting |
| 5 |
February 1992 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">A Convention for Describing SNMP-based Agents</span> |
| 9 |
|
| 10 |
Status of This Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. It does |
| 13 |
not specify an Internet standard. Distribution of this memo is |
| 14 |
unlimited. |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
This memo suggests a straight-forward approach towards describing |
| 19 |
SNMP-based agents. |
| 20 |
|
| 21 |
Table of Contents |
| 22 |
|
| 23 |
<a href="#section-1">1</a>. The Network Management Framework ............................ <a href="#page-2">2</a> |
| 24 |
<a href="#section-2">2</a>. Objects ..................................................... <a href="#page-2">2</a> |
| 25 |
<a href="#section-3">3</a>. Describing Agents ........................................... <a href="#page-3">3</a> |
| 26 |
<a href="#section-3.1">3.1</a> Definitions ................................................ <a href="#page-4">4</a> |
| 27 |
<a href="#section-3.2">3.2</a> Mapping of the MODULE-CONFORMANCE macro .................... <a href="#page-5">5</a> |
| 28 |
<a href="#section-3.2.1">3.2.1</a> Mapping of the LAST-UPDATED clause ....................... <a href="#page-6">6</a> |
| 29 |
<a href="#section-3.2.2">3.2.2</a> Mapping of the PRODUCT-RELEASE clause .................... <a href="#page-6">6</a> |
| 30 |
<a href="#section-3.2.3">3.2.3</a> Mapping of the DESCRIPTION clause ........................ <a href="#page-6">6</a> |
| 31 |
<a href="#section-3.2.4">3.2.4</a> Mapping of the SUPPORTS clause ........................... <a href="#page-6">6</a> |
| 32 |
<a href="#section-3.2.4.1">3.2.4.1</a> Mapping of the INCLUDES clause ......................... <a href="#page-6">6</a> |
| 33 |
<a href="#section-3.2.4.2">3.2.4.2</a> Mapping of the VARIATION clause ........................ <a href="#page-6">6</a> |
| 34 |
<a href="#section-3.2.4.2.1">3.2.4.2.1</a> Mapping of the SYNTAX clause ......................... <a href="#page-6">6</a> |
| 35 |
<a href="#section-3.2.4.2.2">3.2.4.2.2</a> Mapping of the WRITE-SYNTAX clause ................... <a href="#page-7">7</a> |
| 36 |
<a href="#section-3.2.4.2.3">3.2.4.2.3</a> Mapping of the ACCESS clause ......................... <a href="#page-7">7</a> |
| 37 |
<a href="#section-3.2.4.2.4">3.2.4.2.4</a> Mapping of the CREATION-REQUIRES clause .............. <a href="#page-7">7</a> |
| 38 |
<a href="#section-3.2.4.2.5">3.2.4.2.5</a> Mapping of the DEFVAL clause ......................... <a href="#page-7">7</a> |
| 39 |
<a href="#section-3.2.4.2.6">3.2.4.2.6</a> Mapping of the DESCRIPTION clause .................... <a href="#page-7">7</a> |
| 40 |
<a href="#section-3.3">3.3</a> Refined Syntax ............................................. <a href="#page-7">7</a> |
| 41 |
<a href="#section-3.4">3.4</a> Usage Example .............................................. <a href="#page-8">8</a> |
| 42 |
<a href="#section-4">4</a>. Acknowledgements ............................................ <a href="#page-11">11</a> |
| 43 |
<a href="#section-5">5</a>. References .................................................. <a href="#page-11">11</a> |
| 44 |
<a href="#section-6">6</a>. Security Considerations...................................... <a href="#page-12">12</a> |
| 45 |
<a href="#section-7">7</a>. Authors' Addresses........................................... <a href="#page-12">12</a> |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">McCloghrie & Rose [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Network Management Framework</span> |
| 58 |
|
| 59 |
The Internet-standard Network Management Framework consists of |
| 60 |
three components. They are: |
| 61 |
|
| 62 |
<a href="./rfc1155">RFC 1155</a> [<a href="#ref-1" title=""Structure and Identification of Management Information for TCP/IP-based internets"">1</a>] which defines the SMI, the mechanisms used for |
| 63 |
describing and naming objects for the purpose of management. |
| 64 |
<a href="./rfc1212">RFC 1212</a> [<a href="#ref-2" title=""Concise MIB Definitions"">2</a>] defines a more concise description mechanism, |
| 65 |
which is wholly consistent with the SMI. |
| 66 |
|
| 67 |
<a href="./rfc1213">RFC 1213</a> [<a href="#ref-3" title=""Management Information Base forNetwork Management of TCP/IP-based internets"">3</a>] which defines MIB-II, the core set of managed |
| 68 |
objects for the Internet suite of protocols. |
| 69 |
|
| 70 |
<a href="./rfc1157">RFC 1157</a> [<a href="#ref-4" title="and J. Davin">4</a>] which defines the SNMP, the protocol used for |
| 71 |
network access to managed objects. |
| 72 |
|
| 73 |
The Framework permits new objects to be defined for the |
| 74 |
purpose of experimentation and evaluation. |
| 75 |
|
| 76 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Objects</span> |
| 77 |
|
| 78 |
Managed objects are accessed via a virtual information store, |
| 79 |
termed the Management Information Base or MIB. Within a given |
| 80 |
MIB module, objects are defined using <a href="./rfc1212">RFC 1212</a>'s OBJECT-TYPE |
| 81 |
macro. At a minimum, each object has a name, a syntax, an |
| 82 |
access-level, and an implementation-status. |
| 83 |
|
| 84 |
The name is an object identifier, an administratively assigned |
| 85 |
name, which specifies an object type. The object type |
| 86 |
together with an object instance serves to uniquely identify a |
| 87 |
specific instantiation of the object. For human convenience, |
| 88 |
we often use a textual string, termed the OBJECT DESCRIPTOR, |
| 89 |
to also refer to the object type. |
| 90 |
|
| 91 |
The syntax of an object type defines the abstract data |
| 92 |
structure corresponding to that object type. The ASN.1[5] |
| 93 |
language is used for this purpose. However, <a href="./rfc1155">RFC 1155</a> |
| 94 |
purposely restricts the ASN.1 constructs which may be used. |
| 95 |
These restrictions are explicitly made for simplicity. |
| 96 |
|
| 97 |
The access-level of an object type defines whether it makes |
| 98 |
"protocol sense" to read and/or write the value of an instance |
| 99 |
of the object type. (This access-level is independent of any |
| 100 |
administrative authorization policy.) |
| 101 |
|
| 102 |
The implementation-status of an object type indicates whether |
| 103 |
the object is mandatory, optional, obsolete, or deprecated. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">McCloghrie & Rose [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Describing Agents</span> |
| 114 |
|
| 115 |
When a MIB module is written, it is divided into units of |
| 116 |
conformance termed groups. If an agent claims conformance to |
| 117 |
a group, then it must implement each and every object within |
| 118 |
that group. Of course, for whatever reason, an agent may |
| 119 |
implement only a subset of the groups within a MIB module. In |
| 120 |
addition, the definition of some MIB objects leave some |
| 121 |
aspects of the definition to the discretion of an implementor. |
| 122 |
|
| 123 |
Practical experience has demonstrated a need for concisely |
| 124 |
describing the capabilities of an agent with regards to the |
| 125 |
MIB groups that it implements. This memo defines a new macro, |
| 126 |
MODULE-CONFORMANCE, which allows an agent implementor to |
| 127 |
describe the precise level of support which an agent claims in |
| 128 |
regards to a MIB group, and to bind that description to the |
| 129 |
sysObjectID associated with the agent. In particular, some |
| 130 |
objects may have restricted or augmented syntax or access- |
| 131 |
levels. |
| 132 |
|
| 133 |
If the MODULE-CONFORMANCE invocation is given to a |
| 134 |
management-station implementor, then that implementor can |
| 135 |
build management applications which optimize themselves when |
| 136 |
communicating with a particular agent. For example, the |
| 137 |
management-station can maintain a database of these |
| 138 |
invocations. When a management-station interacts with an |
| 139 |
agent, it retrieves the agent's sysObjectID. Based on this, |
| 140 |
it consults the database. If an entry is found, then the |
| 141 |
management application can optimize its behavior accordingly. |
| 142 |
|
| 143 |
This binding to sysObjectId may not always suffice to define |
| 144 |
all MIB objects to which an agent can provide access. In |
| 145 |
particular, this situation occurs where the agent dynamically |
| 146 |
learns of the objects it supports, for example, an agent |
| 147 |
supporting SMUX peers via the SMUX protocol [<a href="#ref-6" title=""SNMP MUX Protocol and MIB"">6</a>]. In these |
| 148 |
situations, additional MIB objects beyond sysObjectID must be |
| 149 |
used to name other invocations of the MODULE-CONFORMANCE macro |
| 150 |
to augment the description of MIB support provided by the |
| 151 |
agent. For example, if an agent's sysObjectID indicates that |
| 152 |
it supports the SMUX MIB, then each instance of smuxPidentity |
| 153 |
will indicate another MODULE-CONFORMANCE invocation which is |
| 154 |
dynamically being supported by the agent. |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">McCloghrie & Rose [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Definitions</span> |
| 170 |
|
| 171 |
<a href="./rfc1303">RFC-1303</a> DEFINITIONS ::= BEGIN |
| 172 |
|
| 173 |
IMPORTS |
| 174 |
ObjectName, ObjectSyntax |
| 175 |
FROM <a href="./rfc1155">RFC1155</a>-SMI |
| 176 |
DisplayString |
| 177 |
FROM <a href="./rfc1213">RFC1213</a>-MIB; |
| 178 |
|
| 179 |
MODULE-CONFORMANCE MACRO ::= |
| 180 |
BEGIN |
| 181 |
TYPE NOTATION ::= |
| 182 |
"LAST-UPDATED" |
| 183 |
value(update UTCTime) |
| 184 |
"PRODUCT-RELEASE" |
| 185 |
value(release DisplayString) |
| 186 |
"DESCRIPTION" |
| 187 |
value(description DisplayString) |
| 188 |
ModulePart |
| 189 |
|
| 190 |
VALUE NOTATION ::= -- agent's sysObjectID -- |
| 191 |
value(VALUE ObjectName) |
| 192 |
|
| 193 |
ModulePart ::= Modules |
| 194 |
| empty |
| 195 |
|
| 196 |
Modules ::= Module |
| 197 |
| Modules Module |
| 198 |
|
| 199 |
Module ::= -- name of module -- |
| 200 |
"SUPPORTS" ModuleName |
| 201 |
"INCLUDES" "{" Groups "}" |
| 202 |
VariationPart |
| 203 |
|
| 204 |
ModuleName ::= identifier ModuleIdentifier |
| 205 |
|
| 206 |
ModuleIdentifier ::= |
| 207 |
value (moduleID OBJECT IDENTIFIER) |
| 208 |
| empty |
| 209 |
|
| 210 |
Groups ::= Group |
| 211 |
| Groups "," Group |
| 212 |
|
| 213 |
Group ::= value(group OBJECT IDENTIFIER) |
| 214 |
|
| 215 |
VariationPart ::= Variations |
| 216 |
| empty |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">McCloghrie & Rose [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 223 |
|
| 224 |
|
| 225 |
Variations ::= Variation |
| 226 |
| Variations Variation |
| 227 |
|
| 228 |
Variation ::= "VARIATION" value(object ObjectName) |
| 229 |
Syntax WriteSyntax Access |
| 230 |
Creation DefaultValue |
| 231 |
"DESCRIPTION" |
| 232 |
value(limitext DisplayString) |
| 233 |
|
| 234 |
-- must be a refinement for object's SYNTAX |
| 235 |
Syntax ::= "SYNTAX" type(SYNTAX) |
| 236 |
| empty |
| 237 |
|
| 238 |
-- must be a refinement for object's SYNTAX |
| 239 |
WriteSyntax ::= "WRITE-SYNTAX" type(WriteSYNTAX) |
| 240 |
| empty |
| 241 |
|
| 242 |
Access ::= "ACCESS" AccessValue |
| 243 |
| empty |
| 244 |
|
| 245 |
AccessValue ::= "read-only" |
| 246 |
| "read-write" |
| 247 |
| "write-only" |
| 248 |
| "not-accessible" |
| 249 |
|
| 250 |
Creation ::= "CREATION-REQUIRES" "{" Cells "}" |
| 251 |
|
| 252 |
Cells ::= Cell |
| 253 |
| Cells "," Cell |
| 254 |
|
| 255 |
Cell ::= value(cell ObjectName) |
| 256 |
|
| 257 |
DefaultValue ::= "DEFVAL" |
| 258 |
"{" value (defval ObjectSyntax) "}" |
| 259 |
| empty |
| 260 |
|
| 261 |
END |
| 262 |
|
| 263 |
END |
| 264 |
|
| 265 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Mapping of the MODULE-CONFORMANCE macro</span> |
| 266 |
|
| 267 |
It should be noted that the expansion of the MODULE-CONFORMANCE macro |
| 268 |
is something which conceptually happens during implementation and not |
| 269 |
during run-time. |
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">McCloghrie & Rose [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Mapping of the LAST-UPDATED clause</span> |
| 282 |
|
| 283 |
The LAST-UPDATED clause, which must be present, contains the date and |
| 284 |
time that this definition was last edited. |
| 285 |
|
| 286 |
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Mapping of the PRODUCT-RELEASE clause</span> |
| 287 |
|
| 288 |
The PRODUCT-RELEASE clause, which must be present, contains a textual |
| 289 |
description of the product release which includes this agent. |
| 290 |
|
| 291 |
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Mapping of the DESCRIPTION clause</span> |
| 292 |
|
| 293 |
The DESCRIPTION clause, which must be present, contains a textual |
| 294 |
description of this agent. |
| 295 |
|
| 296 |
<span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Mapping of the SUPPORTS clause</span> |
| 297 |
|
| 298 |
The SUPPORTS clause, which need not be present, is repeatedly used to |
| 299 |
name each MIB module for which the agent claims a complete or partial |
| 300 |
implementation. Each MIB module is named by its module name, and |
| 301 |
optionally, by its associated OBJECT IDENTIFIER as well. (Note that |
| 302 |
only a few MIB modules have had OBJECT IDENTIFIERs assigned to them.) |
| 303 |
|
| 304 |
<span class="h5"><a class="selflink" id="section-3.2.4.1" href="#section-3.2.4.1">3.2.4.1</a>. Mapping of the INCLUDES clause</span> |
| 305 |
|
| 306 |
The INCLUDES clause, which must be present for each use of the |
| 307 |
SUPPORTS clause, is used to name each MIB group associated with the |
| 308 |
SUPPORT clause, which the agent claims to implement. |
| 309 |
|
| 310 |
<span class="h5"><a class="selflink" id="section-3.2.4.2" href="#section-3.2.4.2">3.2.4.2</a>. Mapping of the VARIATION clause</span> |
| 311 |
|
| 312 |
The VARIATION clause, which need not be present, is repeatedly used |
| 313 |
to name each MIB object which the agent implements in some variant or |
| 314 |
refined fashion. |
| 315 |
|
| 316 |
<span class="h6"><a class="selflink" id="section-3.2.4.2.1" href="#section-3.2.4.2.1">3.2.4.2.1</a>. Mapping of the SYNTAX clause</span> |
| 317 |
|
| 318 |
The SYNTAX clause, which need not be present, is used to provide a |
| 319 |
refined SYNTAX for the object named in the correspondent VARIATION |
| 320 |
clause. Note that if this clause and a WRITE-SYNTAX clause are both |
| 321 |
present, then this clause only applies when instances of the object |
| 322 |
named in the correspondent VARIATION clause are read. |
| 323 |
|
| 324 |
Consult <a href="#section-3.3">Section 3.3</a> for more information on refined syntax. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">McCloghrie & Rose [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h6"><a class="selflink" id="section-3.2.4.2.2" href="#section-3.2.4.2.2">3.2.4.2.2</a>. Mapping of the WRITE-SYNTAX clause</span> |
| 338 |
|
| 339 |
The WRITE-SYNTAX clause, which need not be present, is used to |
| 340 |
provide a refined SYNTAX for the object named in the correspondent |
| 341 |
VARIATION clause when instances of that object are written. |
| 342 |
|
| 343 |
Consult <a href="#section-3.3">Section 3.3</a> for more information on refined syntax. |
| 344 |
|
| 345 |
<span class="h6"><a class="selflink" id="section-3.2.4.2.3" href="#section-3.2.4.2.3">3.2.4.2.3</a>. Mapping of the ACCESS clause</span> |
| 346 |
|
| 347 |
The ACCESS clause, which need not be present, is used to provide a |
| 348 |
refined ACCESS for the object named in the correspondent VARIATION |
| 349 |
clause. |
| 350 |
|
| 351 |
<span class="h6"><a class="selflink" id="section-3.2.4.2.4" href="#section-3.2.4.2.4">3.2.4.2.4</a>. Mapping of the CREATION-REQUIRES clause</span> |
| 352 |
|
| 353 |
The CREATION-REQUIRES clause, which need not be present, is used to |
| 354 |
name the columnar objects of a conceptual row to which values must be |
| 355 |
explicitly assigned, by a SNMP Set operation, before the agent will |
| 356 |
create new instances of objects in that row. This clause must not be |
| 357 |
present unless the object named in the correspondent VARIATION clause |
| 358 |
is a conceptual row, i.e., has a syntax which resolves to a SEQUENCE |
| 359 |
containing columnar objects. The objects named in the value of this |
| 360 |
clause usually will refer to columnar objects in that row. However, |
| 361 |
objects unrelated to the conceptual row may also be specified. |
| 362 |
|
| 363 |
The absence of this clause for a particular conceptual row indicates |
| 364 |
that the agent does not support the creation, via SNMP operations, of |
| 365 |
new object instances in that row. |
| 366 |
|
| 367 |
<span class="h6"><a class="selflink" id="section-3.2.4.2.5" href="#section-3.2.4.2.5">3.2.4.2.5</a>. Mapping of the DEFVAL clause</span> |
| 368 |
|
| 369 |
The DEFVAL clause, which need not be present, is used to provide a |
| 370 |
refined DEFVAL value for the object named in the correspondent |
| 371 |
VARIATION clause. The semantics of this value are identical to those |
| 372 |
of the OBJECT-TYPE macro's DEFVAL clause [<a href="#ref-2" title=""Concise MIB Definitions"">2</a>]. |
| 373 |
|
| 374 |
<span class="h6"><a class="selflink" id="section-3.2.4.2.6" href="#section-3.2.4.2.6">3.2.4.2.6</a>. Mapping of the DESCRIPTION clause</span> |
| 375 |
|
| 376 |
The DESCRIPTION clause, which must be present for each use of the |
| 377 |
VARIATION clause, contains a textual description of the variant or |
| 378 |
refined implementation. |
| 379 |
|
| 380 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Refined Syntax</span> |
| 381 |
|
| 382 |
The SYNTAX and WRITE-SYNTAX clauses allow an object's Syntax to be |
| 383 |
refined. However, not all refinements of syntax are appropriate. In |
| 384 |
particular, |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">McCloghrie & Rose [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 391 |
|
| 392 |
|
| 393 |
(1) the object's primitive or application type (as defined in |
| 394 |
the SMI [<a href="#ref-1" title=""Structure and Identification of Management Information for TCP/IP-based internets"">1</a>]) must not be changed; |
| 395 |
|
| 396 |
(2) an object defined with an SMI type of OBJECT IDENTIFIER, |
| 397 |
IpAddress, Counter, or TimeTicks cannot be refined; and, |
| 398 |
|
| 399 |
(3) an object defined to have a specific set of values (e.g., |
| 400 |
an INTEGER with named values) cannot have additional |
| 401 |
values defined for it. |
| 402 |
|
| 403 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Usage Example</span> |
| 404 |
|
| 405 |
Consider how one might document the 4BSD/ISODE "Secure" SNMP |
| 406 |
agent: |
| 407 |
|
| 408 |
FourBSD-ISODE DEFINITIONS ::= BEGIN |
| 409 |
|
| 410 |
IMPORTS |
| 411 |
MODULE-CONFORMANCE |
| 412 |
FROM <a href="./rfc1303">RFC-1303</a> |
| 413 |
-- everything -- |
| 414 |
FROM RFCxxxx-MIB |
| 415 |
-- everything -- |
| 416 |
FROM <a href="./rfc1213">RFC1213</a>-MIB |
| 417 |
-- everything -- |
| 418 |
FROM UNIX-MIB |
| 419 |
-- everything -- |
| 420 |
FROM EVAL-MIB; |
| 421 |
|
| 422 |
fourBSD-isode-support MODULE-CONFORMANCE |
| 423 |
LAST-UPDATED "9201252354Z" |
| 424 |
PRODUCT-RELEASE "ISODE 7.0 + 'Secure' SNMP |
| 425 |
upgrade for SunOS 4.1" |
| 426 |
DESCRIPTION "4BSD/ISODE 'Secure' SNMP" |
| 427 |
|
| 428 |
SUPPORTS RFCxxxx-MIB -- SNMP Party MIB -- |
| 429 |
INCLUDES { partyPublic, partyPrivate } |
| 430 |
|
| 431 |
SUPPORTS <a href="./rfc1213">RFC1213</a>-MIB |
| 432 |
INCLUDES { system, interfaces, at, ip, icmp, |
| 433 |
tcp, udp, snmp } |
| 434 |
|
| 435 |
VARIATION atEntry |
| 436 |
CREATION-REQUIRES { atPhysAddress } |
| 437 |
DESCRIPTION "Address mappings on 4BSD require |
| 438 |
both protocol and media addresses" |
| 439 |
|
| 440 |
VARIATION ifAdminStatus |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">McCloghrie & Rose [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 447 |
|
| 448 |
|
| 449 |
SYNTAX INTEGER { up(1), down(2) } |
| 450 |
DESCRIPTION "Unable to set test mode on 4BSD" |
| 451 |
|
| 452 |
VARIATION ifOperStatus |
| 453 |
SYNTAX INTEGER { up(1), down(2) } |
| 454 |
DESCRIPTION "Information limited on 4BSD" |
| 455 |
|
| 456 |
VARIATION ipDefaultTTL |
| 457 |
SYNTAX INTEGER { maxttl(255) } |
| 458 |
DESCRIPTION "Hard-wired on 4BSD" |
| 459 |
|
| 460 |
VARIATION ipInAddrErrors |
| 461 |
ACCESS not-accessible |
| 462 |
DESCRIPTION "Information not available on 4BSD" |
| 463 |
|
| 464 |
VARIATION ipInDiscards |
| 465 |
ACCESS not-accessible |
| 466 |
DESCRIPTION "Information not available on 4BSD" |
| 467 |
|
| 468 |
VARIATION ipRouteEntry |
| 469 |
CREATION-REQUIRES { ipRouteNextHop } |
| 470 |
DESCRIPTION "Routes on 4BSD require both |
| 471 |
destination and next-hop" |
| 472 |
|
| 473 |
VARIATION ipRouteType |
| 474 |
SYNTAX INTEGER { direct(3), indirect(4) } |
| 475 |
WRITE-SYNTAX INTEGER { invalid(2), direct(3), |
| 476 |
indirect(4) } |
| 477 |
DESCRIPTION "Information limited on 4BSD" |
| 478 |
|
| 479 |
VARIATION ipRouteProto |
| 480 |
SYNTAX INTEGER { other(1), icmp (4) } |
| 481 |
DESCRIPTION "Information limited on 4BSD" |
| 482 |
|
| 483 |
VARIATION ipRouteAge |
| 484 |
ACCESS not-accessible |
| 485 |
DESCRIPTION "Information not available on 4BSD" |
| 486 |
|
| 487 |
VARIATION ipNetToMediaEntry |
| 488 |
CREATION-REQUIRES { ipNetToMediaPhysAddress } |
| 489 |
DESCRIPTION "Address mappings on 4BSD require |
| 490 |
both protocol and media addresses" |
| 491 |
|
| 492 |
VARIATION ipNetToMediaType |
| 493 |
SYNTAX INTEGER { dynamic(3), static(4) } |
| 494 |
WRITE-SYNTAX INTEGER { invalid(2), dynamic(3), |
| 495 |
static(4) } |
| 496 |
DESCRIPTION "Information limited on 4BSD" |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">McCloghrie & Rose [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 503 |
|
| 504 |
|
| 505 |
VARIATION tcpConnState |
| 506 |
ACCESS read-only |
| 507 |
DESCRIPTION "Unable to set this on 4BSD" |
| 508 |
|
| 509 |
VARIATION tcpInErrs |
| 510 |
ACCESS not-accessible |
| 511 |
DESCRIPTION "Information not available on 4BSD" |
| 512 |
|
| 513 |
VARIATION tcpOutRsts |
| 514 |
ACCESS not-accessible |
| 515 |
DESCRIPTION "Information not available on 4BSD" |
| 516 |
|
| 517 |
SUPPORTS UNIX-MIB |
| 518 |
INCLUDES { agents, mbuf, netstat } |
| 519 |
|
| 520 |
SUPPORTS EVAL-MIB |
| 521 |
INCLUDES { functions, expressions } |
| 522 |
|
| 523 |
::= { fourBSD-isode 6 6 } |
| 524 |
|
| 525 |
END |
| 526 |
|
| 527 |
According to this invocation, an agent with a sysObjectID of |
| 528 |
|
| 529 |
{ fourBSD-isode 6 6 } |
| 530 |
|
| 531 |
supports four MIB modules. |
| 532 |
|
| 533 |
From the SNMP Party MIB, all the objects contained in the partyPublic |
| 534 |
and partyPrivate groups are supported, without variation. |
| 535 |
|
| 536 |
From MIB-II, all groups except the egp group are supported. However, |
| 537 |
the objects |
| 538 |
|
| 539 |
ipInAddrErrors |
| 540 |
ipInDiscards |
| 541 |
ipRouteAge |
| 542 |
tcpInErrs |
| 543 |
tcpOutRsts |
| 544 |
|
| 545 |
are not available, whilst the objects |
| 546 |
|
| 547 |
ifAdminStatus |
| 548 |
ifOperStatus |
| 549 |
ipDefaultTTL |
| 550 |
ipRouteType |
| 551 |
ipRouteProto |
| 552 |
ipNetToMediaType |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">McCloghrie & Rose [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 559 |
|
| 560 |
|
| 561 |
have a restricted syntax, and the object |
| 562 |
|
| 563 |
tcpConnState |
| 564 |
|
| 565 |
is available only for reading. Note that in the case of the objects |
| 566 |
|
| 567 |
ipRouteType |
| 568 |
ipNetToMediaType |
| 569 |
|
| 570 |
the set of values which may be read is different than the set of |
| 571 |
values which may be written. Finally, when creating a new row in the |
| 572 |
atTable, the set-request must create an instance of atPhysAddress. |
| 573 |
Similarly, when creating a new row in the ipRouteTable, the set- |
| 574 |
request must create an instance of ipRouteNextHop. Similarly, when |
| 575 |
creating a new row in the ipNetToMediaTable, the set-request must |
| 576 |
create an instance of ipNetToMediaPhysAddress. |
| 577 |
|
| 578 |
From the UNIX-MIB, all the objects contained in the agents, mbuf, and |
| 579 |
netstat groups are supported, without variation. |
| 580 |
|
| 581 |
From the EVAL-MIB, all the objects contained in the functions and |
| 582 |
expressions groups are supported, without variation. |
| 583 |
|
| 584 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span> |
| 585 |
|
| 586 |
The authors gratefully acknowledge the comments of Mark van der Pol |
| 587 |
of Hughes LAN Systems, and David T. Perkins of SynOptics |
| 588 |
Communications. |
| 589 |
|
| 590 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span> |
| 591 |
|
| 592 |
[<a id="ref-1">1</a>] Rose M., and K. McCloghrie, "Structure and Identification of |
| 593 |
Management Information for TCP/IP-based internets", <a href="./rfc1155">RFC 1155</a>, |
| 594 |
Performance Systems International, Hughes LAN Systems, May 1990. |
| 595 |
|
| 596 |
[<a id="ref-2">2</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", |
| 597 |
<a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN Systems, |
| 598 |
March 1991. |
| 599 |
|
| 600 |
[<a id="ref-3">3</a>] McCloghrie K., and M. Rose, Editors, "Management Information |
| 601 |
Base forNetwork Management of TCP/IP-based internets", <a href="./rfc1213">RFC 1213</a>, |
| 602 |
Performance Systems International, March 1991. |
| 603 |
|
| 604 |
[<a id="ref-4">4</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple |
| 605 |
Network Management Protocol (SNMP), <a href="./rfc1157">RFC 1157</a>, SNMP Research, |
| 606 |
Performance Systems International, Performance Systems |
| 607 |
International, MIT Laboratory for Computer Science, May 1990. |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">McCloghrie & Rose [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1303">RFC 1303</a> Convention for Describing SNMP Agents February 1992</span> |
| 615 |
|
| 616 |
|
| 617 |
[<a id="ref-5">5</a>] Information processing systems - Open Systems Interconnection - |
| 618 |
Specification of Abstract Syntax Notation One (ASN.1), |
| 619 |
International Organization for Standardization, International |
| 620 |
Standard 8824, December 1987. |
| 621 |
|
| 622 |
[<a id="ref-6">6</a>] Rose, M., "SNMP MUX Protocol and MIB", <a href="./rfc1227">RFC 1227</a>, Performance |
| 623 |
Systems International, May 1991. |
| 624 |
|
| 625 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 626 |
|
| 627 |
Security issues are not discussed in this memo. |
| 628 |
|
| 629 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authors' Addresses</span> |
| 630 |
|
| 631 |
Keith McCloghrie |
| 632 |
Hughes LAN Systems |
| 633 |
1225 Charleston Road |
| 634 |
Mountain View, CA 94043 |
| 635 |
|
| 636 |
Phone: (415) 966-7934 |
| 637 |
EMail: [email protected] |
| 638 |
|
| 639 |
|
| 640 |
Marshall T. Rose |
| 641 |
Dover Beach Consulting, Inc. |
| 642 |
420 Whisman Court |
| 643 |
Mountain View, CA 94043-2112 |
| 644 |
|
| 645 |
Phone: (415) 968-1052 |
| 646 |
EMail: [email protected] |
| 647 |
|
| 648 |
|
| 649 |
|
| 650 |
|
| 651 |
|
| 652 |
|
| 653 |
|
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
McCloghrie & Rose [Page 12] |
| 669 |
</pre> |