| 1 |
<pre>Network Working Group J. Case |
| 2 |
Request for Comments: 1285 SNMP Research, Incorporated |
| 3 |
January 1992 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">FDDI Management Information Base</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo is an extension to the SNMP MIB. This RFC specifies an IAB |
| 11 |
standards track protocol for the Internet community, and requests |
| 12 |
discussion and suggestions for improvements. Please refer to the |
| 13 |
current edition of the "IAB Official Protocol Standards" for the |
| 14 |
standardization state and status of this protocol. Distribution of |
| 15 |
this memo is unlimited. |
| 16 |
|
| 17 |
Table of Contents |
| 18 |
|
| 19 |
<a href="#section-1">1</a>. Abstract .............................................. <a href="#page-1">1</a> |
| 20 |
<a href="#section-2">2</a>. The Network Management Framework....................... <a href="#page-1">1</a> |
| 21 |
<a href="#section-3">3</a>. Objects ............................................... <a href="#page-2">2</a> |
| 22 |
<a href="#section-3.1">3.1</a> Format of Definitions ................................ <a href="#page-2">2</a> |
| 23 |
<a href="#section-4">4</a>. Overview .............................................. <a href="#page-3">3</a> |
| 24 |
<a href="#section-4.1">4.1</a> Textual Conventions .................................. <a href="#page-3">3</a> |
| 25 |
<a href="#section-5">5</a>. Object Definitions .................................... <a href="#page-4">4</a> |
| 26 |
<a href="#section-5.1">5.1</a> The SMT Group ........................................ <a href="#page-5">5</a> |
| 27 |
<a href="#section-5.2">5.2</a> The MAC Group ........................................ <a href="#page-15">15</a> |
| 28 |
<a href="#section-5.3">5.3</a> The PATH Group ....................................... <a href="#page-27">27</a> |
| 29 |
<a href="#section-5.4">5.4</a> The PORT Group ....................................... <a href="#page-27">27</a> |
| 30 |
<a href="#section-5.5">5.5</a> The ATTACHMENT Group ................................. <a href="#page-38">38</a> |
| 31 |
<a href="#section-5.6">5.6</a> The Chip Set Group ................................... <a href="#page-42">42</a> |
| 32 |
<a href="#section-6">6</a>. Acknowledgements ...................................... <a href="#page-43">43</a> |
| 33 |
<a href="#section-7">7</a>. References ............................................ <a href="#page-45">45</a> |
| 34 |
Security Considerations................................... <a href="#page-46">46</a> |
| 35 |
Author's Address.......................................... <a href="#page-46">46</a> |
| 36 |
|
| 37 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span> |
| 38 |
|
| 39 |
This memo defines a portion of the Management Information Base (MIB) |
| 40 |
for use with network management protocols in TCP/IP-based internets. |
| 41 |
In particular, it defines objects for managing devices which |
| 42 |
implement the FDDI. |
| 43 |
|
| 44 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Network Management Framework</span> |
| 45 |
|
| 46 |
The Internet-standard Network Management Framework consists of three |
| 47 |
components. They are: |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Case [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="./rfc1155">RFC 1155</a> which defines the SMI, the mechanisms used for describing |
| 58 |
and naming objects for the purpose of management. <a href="./rfc1212">RFC 1212</a> |
| 59 |
defines a more concise description mechanism, which is wholly |
| 60 |
consistent with the SMI. |
| 61 |
|
| 62 |
<a href="./rfc1156">RFC 1156</a> which defines MIB-I, the core set of managed objects for |
| 63 |
the Internet suite of protocols. <a href="./rfc1213">RFC 1213</a>, defines MIB-II, an |
| 64 |
evolution of MIB-I based on implementation experience and new |
| 65 |
operational requirements. |
| 66 |
|
| 67 |
<a href="./rfc1157">RFC 1157</a> which defines the SNMP, the protocol used for network |
| 68 |
access to managed objects. |
| 69 |
|
| 70 |
The Framework permits new objects to be defined for the purpose of |
| 71 |
experimentation and evaluation. |
| 72 |
|
| 73 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Objects</span> |
| 74 |
|
| 75 |
Managed objects are accessed via a virtual information store, termed |
| 76 |
the Management Information Base or MIB. Objects in the MIB are |
| 77 |
defined using the subset of Abstract Syntax Notation One (ASN.1) [<a href="#ref-5" title=" International Organization for Standardization">5</a>] |
| 78 |
defined in the SMI. In particular, each object has a name, a syntax, |
| 79 |
and an encoding. The name is an object identifier, an |
| 80 |
administratively assigned name, which specifies an object type. The |
| 81 |
object type together with an object instance serves to uniquely |
| 82 |
identify a specific instantiation of the object. For human |
| 83 |
convenience, we often use a textual string, termed the OBJECT |
| 84 |
DESCRIPTOR, to also refer to the object type. |
| 85 |
|
| 86 |
The syntax of an object type defines the abstract data structure |
| 87 |
corresponding to that object type. The ASN.1 language is used for |
| 88 |
this purpose. However, the SMI [<a href="#ref-1" title=""Structure and Identification of Management Information for TCP/IP-based internets"">1</a>] purposely restricts the ASN.1 |
| 89 |
constructs which may be used. These restrictions are explicitly made |
| 90 |
for simplicity. |
| 91 |
|
| 92 |
The encoding of an object type is simply how that object type is |
| 93 |
represented using the object type's syntax. Implicitly tied to the |
| 94 |
notion of an object type's syntax and encoding is how the object type |
| 95 |
is represented when being transmitted on the network. |
| 96 |
|
| 97 |
The SMI specifies the use of the basic encoding rules of ASN.1 [<a href="#ref-6" title=" International Standard 8825">6</a>], |
| 98 |
subject to the additional requirements imposed by the SNMP. |
| 99 |
|
| 100 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Format of Definitions</span> |
| 101 |
|
| 102 |
<a href="#section-5">Section 5</a> contains contains the specification of all object types |
| 103 |
contained in this MIB module. The object types are defined using the |
| 104 |
conventions defined in the SMI, as amended by the extensions |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Case [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 111 |
|
| 112 |
|
| 113 |
specified in [<a href="#ref-7" title=""Concise MIB Definitions"">7</a>]. |
| 114 |
|
| 115 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span> |
| 116 |
|
| 117 |
This document defines the managed objects for FDDI devices which are |
| 118 |
to be accessible via the Simple Network Management Protocol (SNMP). |
| 119 |
At present, this applies to these values of the ifType variable in |
| 120 |
the Internet-standard MIB: |
| 121 |
|
| 122 |
fddi(15) |
| 123 |
|
| 124 |
For these interfaces, the value of the ifSpecific variable in the |
| 125 |
MIB-II [<a href="#ref-4" title=""Management Information Base for Network Management of TCP/IP-based internets"">4</a>] has the OBJECT IDENTIFIER value: |
| 126 |
|
| 127 |
fddi OBJECT IDENTIFIER ::= { transmission 15 } |
| 128 |
|
| 129 |
The definitions of the objects presented here draws heavily from |
| 130 |
related work in the ANSI X3T9.5 committee and the SMT subcommittee of |
| 131 |
that committee [<a href="#ref-8" title=""FDDI Station Management (SMT)"">8</a>]. In fact, the definitions of the managed objects |
| 132 |
in this document are, to the maximum extent possible, identical to |
| 133 |
those identified by the ANSI committee. The semantics of each |
| 134 |
managed object should be the same with syntactic changes made as |
| 135 |
necessary to recast the objects in terms of the Internet-standard SMI |
| 136 |
and MIB so as to be compatible with the SNMP. Examples of these |
| 137 |
syntactic changes include remapping booleans to enumerated integers, |
| 138 |
remapping bit strings to octet strings, and the like. In addition, |
| 139 |
the naming of the objects was changed to achieve compatibility. |
| 140 |
|
| 141 |
These minimal syntactic changes with no semantic changes should allow |
| 142 |
implementations of SNMP manageable FDDI systems to share |
| 143 |
instrumentation with other network management schemes and thereby |
| 144 |
minimize implementation cost. In addition, the translation of |
| 145 |
information conveyed by managed objects from one network management |
| 146 |
scheme to another is eased by these shared definitions. |
| 147 |
|
| 148 |
Only the essential variables, as indicated by their mandatory status |
| 149 |
in the ANSI specification were retained in this document. The |
| 150 |
importance of variables which have an optional status in the ANSI |
| 151 |
specification were perceived as being less widely accepted. |
| 152 |
|
| 153 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Textual Conventions</span> |
| 154 |
|
| 155 |
Several new datatypes are introduced as a textual convention in this |
| 156 |
MIB document. These textual conventions enhance the readability of |
| 157 |
the document and ease comparisons with its ANSI counterpart. It |
| 158 |
should be noted that the introduction of the following textual |
| 159 |
conventions has no effect on either the syntax nor the semantics of |
| 160 |
any managed objects. The use of these is merely an artifact of the |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Case [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 167 |
|
| 168 |
|
| 169 |
explanatory method used. Objects defined in terms of one of these |
| 170 |
methods are always encoded by means of the rules that define the |
| 171 |
primitive type. Hence, no changes to the SMI or the SNMP are |
| 172 |
necessary to accommodate these textual conventions which are adopted |
| 173 |
merely for the convenience of readers and writers in pursuit of the |
| 174 |
elusive goal of clear, concise, and unambiguous MIB documents. |
| 175 |
|
| 176 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Object Definitions</span> |
| 177 |
|
| 178 |
<a href="./rfc1285">RFC1285</a>-MIB DEFINITIONS ::= BEGIN |
| 179 |
|
| 180 |
IMPORTS |
| 181 |
Counter |
| 182 |
FROM <a href="./rfc1155">RFC1155</a>-SMI |
| 183 |
transmission |
| 184 |
FROM <a href="./rfc1213">RFC1213</a>-MIB |
| 185 |
OBJECT-TYPE |
| 186 |
FROM <a href="./rfc1212">RFC-1212</a>; |
| 187 |
|
| 188 |
-- This MIB module uses the extended OBJECT-TYPE macro as |
| 189 |
-- defined in [<a href="#ref-7" title=""Concise MIB Definitions"">7</a>]. |
| 190 |
|
| 191 |
|
| 192 |
-- this is the FDDI MIB module |
| 193 |
|
| 194 |
fddi OBJECT IDENTIFIER ::= { transmission 15 } |
| 195 |
|
| 196 |
|
| 197 |
-- textual conventions |
| 198 |
|
| 199 |
FddiTime ::= INTEGER (0..2147483647) |
| 200 |
-- This data type specifies octet units of 80 nanoseconds as |
| 201 |
-- an integer value. It is used for Path Latency and |
| 202 |
-- Synchronous Bandwidth values. The encoding is normal |
| 203 |
-- integer representation (not twos complement). |
| 204 |
|
| 205 |
FddiResourceId ::= INTEGER (0..65535) |
| 206 |
-- This data type is used to refer to an instance of a MAC, |
| 207 |
-- PORT, PATH, or ATTACHMENT Resource ID. Indexing begins |
| 208 |
-- at 1. Zero is used to indicate the absence of a resource. |
| 209 |
|
| 210 |
FddiSMTStationIdType ::= OCTET STRING (SIZE (8)) |
| 211 |
-- The unique identifier for the FDDI station. This is a |
| 212 |
-- string of 8 octets, represented as |
| 213 |
-- X' yy yy xx xx xx xx xx xx' |
| 214 |
-- with the low order 6 octet (xx) from a unique IEEE |
| 215 |
-- assigned address. The high order two bits of the IEEE |
| 216 |
-- address, the group address bit and the administration bit |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Case [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 223 |
|
| 224 |
|
| 225 |
-- (Universal/Local) bit should both be zero. The first two |
| 226 |
-- octets, the yy octets, are implementor-defined. |
| 227 |
-- |
| 228 |
-- The representation of the address portion of the station id |
| 229 |
-- is in the IEEE (ANSI/IEEE P802.1A) canonical notation for |
| 230 |
-- 48 bit addresses. The canonical form is a 6-octet string |
| 231 |
-- where the first octet contains the first 8 bits of the |
| 232 |
-- address, with the I/G(Individual/Group) address bit as the |
| 233 |
-- least significant bit and the U/L (Universal/Local) bit |
| 234 |
-- as the next more significant bit, and so on. Note that |
| 235 |
-- addresses in the ANSI FDDI standard SMT frames are |
| 236 |
-- represented in FDDI MAC order. |
| 237 |
|
| 238 |
FddiMACLongAddressType ::= OCTET STRING (SIZE (6)) |
| 239 |
-- The representation of long MAC addresses as management |
| 240 |
-- values is in the IEEE (ANSI/IEEE P802.1A) canonical |
| 241 |
-- notation for 48 bit addresses. The canonical form is a |
| 242 |
-- 6-octet string where the first octet contains the first 8 |
| 243 |
-- bits of the address, with the I/G (Individual/Group) |
| 244 |
-- address bit as the least significant bit and the U/L |
| 245 |
-- (Universal/Local) bit as the next more significant bit, |
| 246 |
-- and so on. Note that the addresses in the SMT frames are |
| 247 |
-- represented in FDDI MAC order. |
| 248 |
|
| 249 |
-- groups in the FDDI MIB module |
| 250 |
|
| 251 |
snmpFddiSMT OBJECT IDENTIFIER ::= { fddi 1 } |
| 252 |
|
| 253 |
snmpFddiMAC OBJECT IDENTIFIER ::= { fddi 2 } |
| 254 |
|
| 255 |
snmpFddiPATH OBJECT IDENTIFIER ::= { fddi 3 } |
| 256 |
|
| 257 |
snmpFddiPORT OBJECT IDENTIFIER ::= { fddi 4 } |
| 258 |
|
| 259 |
snmpFddiATTACHMENT OBJECT IDENTIFIER ::= { fddi 5 } |
| 260 |
|
| 261 |
snmpFddiChipSets OBJECT IDENTIFIER ::= { fddi 6 } |
| 262 |
|
| 263 |
|
| 264 |
-- the SMT group |
| 265 |
-- Implementation of the SMT group is mandatory for all |
| 266 |
-- systems which implement manageable FDDI subsystems. |
| 267 |
|
| 268 |
snmpFddiSMTNumber OBJECT-TYPE |
| 269 |
SYNTAX INTEGER (0..65535) |
| 270 |
ACCESS read-only |
| 271 |
STATUS mandatory |
| 272 |
DESCRIPTION |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Case [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 279 |
|
| 280 |
|
| 281 |
"The number of SMT implementations (regardless of |
| 282 |
their current state) on this network management |
| 283 |
application entity. The value for this variable |
| 284 |
must remain constant at least from one re- |
| 285 |
initialization of the entity's network management |
| 286 |
system to the next re-initialization." |
| 287 |
::= { snmpFddiSMT 1 } |
| 288 |
|
| 289 |
|
| 290 |
-- the SMT table |
| 291 |
|
| 292 |
snmpFddiSMTTable OBJECT-TYPE |
| 293 |
SYNTAX SEQUENCE OF SnmpFddiSMTEntry |
| 294 |
ACCESS not-accessible |
| 295 |
STATUS mandatory |
| 296 |
DESCRIPTION |
| 297 |
"A list of SMT entries. The number of entries is |
| 298 |
given by the value of snmpFddiSMTNumber." |
| 299 |
::= { snmpFddiSMT 2 } |
| 300 |
|
| 301 |
snmpFddiSMTEntry OBJECT-TYPE |
| 302 |
SYNTAX SnmpFddiSMTEntry |
| 303 |
ACCESS not-accessible |
| 304 |
STATUS mandatory |
| 305 |
DESCRIPTION |
| 306 |
"An SMT entry containing information common to a |
| 307 |
given SMT." |
| 308 |
INDEX { snmpFddiSMTIndex } |
| 309 |
::= { snmpFddiSMTTable 1 } |
| 310 |
|
| 311 |
SnmpFddiSMTEntry ::= |
| 312 |
SEQUENCE { |
| 313 |
snmpFddiSMTIndex |
| 314 |
INTEGER, |
| 315 |
snmpFddiSMTStationId |
| 316 |
FddiSMTStationIdType, |
| 317 |
snmpFddiSMTOpVersionId |
| 318 |
INTEGER, |
| 319 |
snmpFddiSMTHiVersionId |
| 320 |
INTEGER, |
| 321 |
snmpFddiSMTLoVersionId |
| 322 |
INTEGER, |
| 323 |
snmpFddiSMTMACCt |
| 324 |
INTEGER, |
| 325 |
snmpFddiSMTNonMasterCt |
| 326 |
INTEGER, |
| 327 |
snmpFddiSMTMasterCt |
| 328 |
INTEGER, |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Case [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 335 |
|
| 336 |
|
| 337 |
snmpFddiSMTPathsAvailable |
| 338 |
INTEGER, |
| 339 |
snmpFddiSMTConfigCapabilities |
| 340 |
INTEGER, |
| 341 |
snmpFddiSMTConfigPolicy |
| 342 |
INTEGER, |
| 343 |
snmpFddiSMTConnectionPolicy |
| 344 |
INTEGER, |
| 345 |
snmpFddiSMTTNotify |
| 346 |
INTEGER, |
| 347 |
snmpFddiSMTStatusReporting |
| 348 |
INTEGER, |
| 349 |
snmpFddiSMTECMState |
| 350 |
INTEGER, |
| 351 |
snmpFddiSMTCFState |
| 352 |
INTEGER, |
| 353 |
snmpFddiSMTHoldState |
| 354 |
INTEGER, |
| 355 |
snmpFddiSMTRemoteDisconnectFlag |
| 356 |
INTEGER, |
| 357 |
snmpFddiSMTStationAction |
| 358 |
INTEGER |
| 359 |
} |
| 360 |
|
| 361 |
snmpFddiSMTIndex OBJECT-TYPE |
| 362 |
SYNTAX INTEGER (1..65535) |
| 363 |
ACCESS read-only |
| 364 |
STATUS mandatory |
| 365 |
DESCRIPTION |
| 366 |
"A unique value for each SMT. Its value ranges |
| 367 |
between 1 and the value of snmpFddiSMTNumber. The |
| 368 |
value for each SMT must remain constant at least |
| 369 |
from one re-initialization of the entity's network |
| 370 |
management system to the next re-initialization." |
| 371 |
::= { snmpFddiSMTEntry 1 } |
| 372 |
|
| 373 |
snmpFddiSMTStationId OBJECT-TYPE |
| 374 |
SYNTAX FddiSMTStationIdType -- OCTET STRING (SIZE (8)) |
| 375 |
ACCESS read-only |
| 376 |
STATUS mandatory |
| 377 |
DESCRIPTION |
| 378 |
"Uniquely identifies an FDDI station." |
| 379 |
REFERENCE |
| 380 |
"ANSI { fddiSMT 11 }" |
| 381 |
::= { snmpFddiSMTEntry 2 } |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Case [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 391 |
|
| 392 |
|
| 393 |
snmpFddiSMTOpVersionId OBJECT-TYPE |
| 394 |
SYNTAX INTEGER (1..65535) |
| 395 |
ACCESS read-write |
| 396 |
STATUS mandatory |
| 397 |
DESCRIPTION |
| 398 |
"The version that this station is using for its |
| 399 |
operation (refer to ANSI 7.1.2.2)." |
| 400 |
REFERENCE |
| 401 |
"ANSI { fddiSMT 13 }" |
| 402 |
::= { snmpFddiSMTEntry 3 } |
| 403 |
|
| 404 |
snmpFddiSMTHiVersionId OBJECT-TYPE |
| 405 |
SYNTAX INTEGER (1..65535) |
| 406 |
ACCESS read-only |
| 407 |
STATUS mandatory |
| 408 |
DESCRIPTION |
| 409 |
"The highest version of SMT that this station |
| 410 |
supports (refer to ANSI 7.1.2.2)." |
| 411 |
REFERENCE |
| 412 |
"ANSI { fddiSMT 14 }" |
| 413 |
::= { snmpFddiSMTEntry 4 } |
| 414 |
|
| 415 |
snmpFddiSMTLoVersionId OBJECT-TYPE |
| 416 |
SYNTAX INTEGER (1..65535) |
| 417 |
ACCESS read-only |
| 418 |
STATUS mandatory |
| 419 |
DESCRIPTION |
| 420 |
"The lowest version of SMT that this station |
| 421 |
supports (refer to ANSI 7.1.2.2)." |
| 422 |
REFERENCE |
| 423 |
"ANSI { fddiSMT 15 }" |
| 424 |
::= { snmpFddiSMTEntry 5 } |
| 425 |
|
| 426 |
snmpFddiSMTMACCt OBJECT-TYPE |
| 427 |
SYNTAX INTEGER (0..255) |
| 428 |
ACCESS read-only |
| 429 |
STATUS mandatory |
| 430 |
DESCRIPTION |
| 431 |
"The number of MACs in the station or |
| 432 |
concentrator." |
| 433 |
REFERENCE |
| 434 |
"ANSI { fddiSMT 21 }" |
| 435 |
::= { snmpFddiSMTEntry 6 } |
| 436 |
|
| 437 |
snmpFddiSMTNonMasterCt OBJECT-TYPE |
| 438 |
SYNTAX INTEGER (0..2) |
| 439 |
ACCESS read-only |
| 440 |
STATUS mandatory |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Case [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 447 |
|
| 448 |
|
| 449 |
DESCRIPTION |
| 450 |
"The number of Non Master PORTs (A, B, or S PORTs) |
| 451 |
in the station or concentrator." |
| 452 |
REFERENCE |
| 453 |
"ANSI { fddiSMT 22 }" |
| 454 |
::= { snmpFddiSMTEntry 7 } |
| 455 |
|
| 456 |
snmpFddiSMTMasterCt OBJECT-TYPE |
| 457 |
SYNTAX INTEGER (0..255) |
| 458 |
ACCESS read-only |
| 459 |
STATUS mandatory |
| 460 |
DESCRIPTION |
| 461 |
"The number of Master PORTs in a node. If the |
| 462 |
node is not a concentrator, the value is zero." |
| 463 |
REFERENCE |
| 464 |
"ANSI { fddiSMT 23 }" |
| 465 |
::= { snmpFddiSMTEntry 8 } |
| 466 |
|
| 467 |
snmpFddiSMTPathsAvailable OBJECT-TYPE |
| 468 |
SYNTAX INTEGER (0..7) |
| 469 |
ACCESS read-only |
| 470 |
STATUS mandatory |
| 471 |
DESCRIPTION |
| 472 |
"A value that indicates the PATH types available |
| 473 |
in the station. |
| 474 |
|
| 475 |
The value is a sum. This value initially takes |
| 476 |
the value zero, then for each type of PATH that |
| 477 |
this node has available, 2 raised to a power is |
| 478 |
added to the sum. The powers are according to the |
| 479 |
following table: |
| 480 |
|
| 481 |
Path Power |
| 482 |
Primary 0 |
| 483 |
Secondary 1 |
| 484 |
Local 2 |
| 485 |
|
| 486 |
For example, a station having Primary and Local |
| 487 |
PATHs available would have a value of 5 (2**0 + |
| 488 |
2**2)." |
| 489 |
REFERENCE |
| 490 |
"ANSI { fddiSMT 24 }" |
| 491 |
::= { snmpFddiSMTEntry 9 } |
| 492 |
|
| 493 |
snmpFddiSMTConfigCapabilities OBJECT-TYPE |
| 494 |
SYNTAX INTEGER (0..3) |
| 495 |
ACCESS read-only |
| 496 |
STATUS mandatory |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Case [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 503 |
|
| 504 |
|
| 505 |
DESCRIPTION |
| 506 |
"A value that indicates capabilities that are |
| 507 |
present in the node. If 'holdAvailable' is |
| 508 |
present, this indicates support of the optional |
| 509 |
Hold Function (refer to ANSI SMT 9.4.3.2). If |
| 510 |
'CF-Wrap-AB' is present, this indicates that the |
| 511 |
WRAP_AB state is forced. |
| 512 |
|
| 513 |
The value is a sum. This value initially takes |
| 514 |
the value zero, then for each of the configuration |
| 515 |
policies currently enforced on the node, 2 raised |
| 516 |
to a power is added to the sum. The powers are |
| 517 |
according to the following table: |
| 518 |
|
| 519 |
Policy Power |
| 520 |
holdAvailable 0 |
| 521 |
CF-Wrap-AB 1 " |
| 522 |
REFERENCE |
| 523 |
"ANSI { fddiSMT 25 }" |
| 524 |
::= { snmpFddiSMTEntry 10 } |
| 525 |
|
| 526 |
snmpFddiSMTConfigPolicy OBJECT-TYPE |
| 527 |
SYNTAX INTEGER (0..3) |
| 528 |
ACCESS read-write |
| 529 |
STATUS mandatory |
| 530 |
DESCRIPTION |
| 531 |
"A value that indicates the configuration policies |
| 532 |
currently enforced in the node (refer to ANSI SMT |
| 533 |
9.4.3.2). The 'configurationHold' policy refers |
| 534 |
to the Hold flag, and should not be present only |
| 535 |
if the Hold function is supported. The 'CF-Wrap- |
| 536 |
AB' policy refers to the CF_Wrap_AB flag. |
| 537 |
|
| 538 |
The value is a sum. This value initially takes |
| 539 |
the value zero, then for each of the configuration |
| 540 |
policies currently enforced on the node, 2 raised |
| 541 |
to a power is added to the sum. The powers are |
| 542 |
according to the following table: |
| 543 |
|
| 544 |
Policy Power |
| 545 |
configurationHold 0 |
| 546 |
CF-Wrap-AB 1 " |
| 547 |
REFERENCE |
| 548 |
"ANSI { fddiSMT 26 }" |
| 549 |
::= { snmpFddiSMTEntry 11 } |
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Case [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 559 |
|
| 560 |
|
| 561 |
snmpFddiSMTConnectionPolicy OBJECT-TYPE |
| 562 |
SYNTAX INTEGER (0..65535) |
| 563 |
ACCESS read-write |
| 564 |
STATUS mandatory |
| 565 |
DESCRIPTION |
| 566 |
"A value that indicates the connection policies |
| 567 |
enforced at the station. A station sets the |
| 568 |
corresponding policy for each of the connection |
| 569 |
types that it rejects. The letter designations, X |
| 570 |
and Y, in the 'rejectX-Y' names have the following |
| 571 |
significance: X represents the PC-Type of the |
| 572 |
local PORT and Y represents a PC-Neighbor in the |
| 573 |
evaluation of Connection-Policy (PC-Type, PC- |
| 574 |
Neighbor) that is done to determine the setting of |
| 575 |
T-Val(3) in the PC-Signaling sequence (refer to |
| 576 |
ANSI <a href="#section-9.6.3">Section 9.6.3</a>). |
| 577 |
|
| 578 |
The value is a sum. This value initially takes |
| 579 |
the value zero, then for each of the connection |
| 580 |
policies currently enforced on the node, 2 raised |
| 581 |
to a power is added to the sum. The powers are |
| 582 |
according to the following table: |
| 583 |
|
| 584 |
Policy Power |
| 585 |
rejectA-A 0 |
| 586 |
rejectA-B 1 |
| 587 |
rejectA-S 2 |
| 588 |
rejectA-M 3 |
| 589 |
rejectB-A 4 |
| 590 |
rejectB-B 5 |
| 591 |
rejectB-S 6 |
| 592 |
rejectB-M 7 |
| 593 |
rejectS-A 8 |
| 594 |
rejectS-B 9 |
| 595 |
rejectS-S 10 |
| 596 |
rejectS-M 11 |
| 597 |
rejectM-A 12 |
| 598 |
rejectM-B 13 |
| 599 |
rejectM-S 14 |
| 600 |
rejectM-M 15 |
| 601 |
|
| 602 |
Implementors should note that the polarity of |
| 603 |
these bits is different in different places in an |
| 604 |
SMT system. Implementors should take appropriate |
| 605 |
care." |
| 606 |
REFERENCE |
| 607 |
"ANSI { fddiSMT 27 }" |
| 608 |
::= { snmpFddiSMTEntry 12 } |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Case [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 615 |
|
| 616 |
|
| 617 |
snmpFddiSMTTNotify OBJECT-TYPE |
| 618 |
SYNTAX INTEGER (2..30) |
| 619 |
ACCESS read-write |
| 620 |
STATUS mandatory |
| 621 |
DESCRIPTION |
| 622 |
"The timer used in the Neighbor Notification |
| 623 |
protocol, reported in seconds and ranging from 2 |
| 624 |
to 30 seconds (refer to ANSI SMT 8.3.1)." |
| 625 |
REFERENCE |
| 626 |
"ANSI { fddiSMT 29 }" |
| 627 |
::= { snmpFddiSMTEntry 13 } |
| 628 |
|
| 629 |
snmpFddiSMTStatusReporting OBJECT-TYPE |
| 630 |
SYNTAX INTEGER { true(1), false(2) } |
| 631 |
ACCESS read-only |
| 632 |
STATUS mandatory |
| 633 |
DESCRIPTION |
| 634 |
"Indicates whether the node implements the Status |
| 635 |
Reporting Protocol. This object is included for |
| 636 |
compatibility with products that were designed |
| 637 |
prior to the adoption of this standard." |
| 638 |
REFERENCE |
| 639 |
"ANSI { fddiSMT 30 }" |
| 640 |
::= { snmpFddiSMTEntry 14 } |
| 641 |
|
| 642 |
snmpFddiSMTECMState OBJECT-TYPE |
| 643 |
SYNTAX INTEGER { |
| 644 |
ec0(1), -- Out |
| 645 |
ec1(2), -- In |
| 646 |
ec2(3), -- Trace |
| 647 |
ec3(4), -- Leave |
| 648 |
ec4(5), -- Path_Test |
| 649 |
ec5(6), -- Insert |
| 650 |
ec6(7), -- Check |
| 651 |
ec7(8) -- Deinsert |
| 652 |
} |
| 653 |
ACCESS read-only |
| 654 |
STATUS mandatory |
| 655 |
DESCRIPTION |
| 656 |
"Indicates the current state of the ECM state |
| 657 |
machine (refer to ANSI SMT 9.5.2)." |
| 658 |
REFERENCE |
| 659 |
"ANSI { fddiSMT 41 }" |
| 660 |
::= { snmpFddiSMTEntry 15 } |
| 661 |
|
| 662 |
snmpFddiSMTCFState OBJECT-TYPE |
| 663 |
SYNTAX INTEGER { |
| 664 |
cf0(1), -- Isolated |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Case [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 671 |
|
| 672 |
|
| 673 |
cf1(2), -- Wrap_S |
| 674 |
cf2(3), -- Wrap_A |
| 675 |
cf3(4), -- Wrap_B |
| 676 |
cf4(5), -- Wrap_AB |
| 677 |
cf5(6) -- Thru |
| 678 |
} |
| 679 |
ACCESS read-only |
| 680 |
STATUS mandatory |
| 681 |
DESCRIPTION |
| 682 |
"The attachment configuration for the station or |
| 683 |
concentrator (refer to ANSI SMT 9.7.4.3)." |
| 684 |
REFERENCE |
| 685 |
"ANSI { fddiSMT 42 }" |
| 686 |
::= { snmpFddiSMTEntry 16 } |
| 687 |
|
| 688 |
snmpFddiSMTHoldState OBJECT-TYPE |
| 689 |
SYNTAX INTEGER { |
| 690 |
not-implemented(1), -- holding not implemented |
| 691 |
not-holding(2), |
| 692 |
holding-prm(3), -- holding on primary |
| 693 |
holding-sec(4) -- holding on secondary |
| 694 |
} |
| 695 |
ACCESS read-only |
| 696 |
STATUS mandatory |
| 697 |
DESCRIPTION |
| 698 |
"This value indicates the current state of the |
| 699 |
Hold function. The values are determined as |
| 700 |
follows: 'holding-prm' is set if the primary ring |
| 701 |
is operational and the Recovery Enable Flag is |
| 702 |
clear (NOT NO_Flag(primary) AND NOT RE_Flag). is |
| 703 |
set if the secondary ring is operational and the |
| 704 |
Recovery Enable Flag is clear (NOT |
| 705 |
NO_Flag(secondary) AND NOT RE_Flag). Ref 9.4.3. |
| 706 |
and 10.3.1. the primary or secondary, i.e., the |
| 707 |
Recovery Enable, RE_Flag, is set." |
| 708 |
REFERENCE |
| 709 |
"ANSI { fddiSMT 43 }" |
| 710 |
::= { snmpFddiSMTEntry 17 } |
| 711 |
|
| 712 |
snmpFddiSMTRemoteDisconnectFlag OBJECT-TYPE |
| 713 |
SYNTAX INTEGER { true(1), false(2) } |
| 714 |
ACCESS read-only |
| 715 |
STATUS mandatory |
| 716 |
DESCRIPTION |
| 717 |
"A flag indicating that the station was remotely |
| 718 |
disconnected from the network. A station requires |
| 719 |
a Connect Action (SM_CM_CONNECT.request (Connect)) |
| 720 |
to rejoin and clear the flag (refer to ANSI |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Case [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 727 |
|
| 728 |
|
| 729 |
6.4.5.2)." |
| 730 |
REFERENCE |
| 731 |
"ANSI { fddiSMT 44 }" |
| 732 |
::= { snmpFddiSMTEntry 18 } |
| 733 |
|
| 734 |
snmpFddiSMTStationAction OBJECT-TYPE |
| 735 |
SYNTAX INTEGER { |
| 736 |
other(1), -- none of the following |
| 737 |
connect(2), |
| 738 |
disconnect(3), |
| 739 |
path-Test(4), |
| 740 |
self-Test(5) |
| 741 |
} |
| 742 |
ACCESS read-write |
| 743 |
STATUS mandatory |
| 744 |
DESCRIPTION |
| 745 |
"This object, when read, always returns a value of |
| 746 |
other(1). The behavior of setting this variable |
| 747 |
to each of the acceptable values is as follows: |
| 748 |
|
| 749 |
Other: Results in a badValue error. |
| 750 |
|
| 751 |
Connect: Generates an |
| 752 |
SM_CM_Connect.request(connect) signal to CMT |
| 753 |
indicating that the ECM State machine is to begin |
| 754 |
a connection sequence. The |
| 755 |
fddiSMTRemoteDisconnectFlag is cleared on the |
| 756 |
setting of this variable to 1. See ANSI Ref |
| 757 |
9.3.1.1. |
| 758 |
|
| 759 |
Disconnect: Generates an |
| 760 |
SM_CM_Connect.request(disconnect) signal to ECM |
| 761 |
and sets the fddiSMTRemoteDisconnectFlag. See |
| 762 |
ANSI Ref 9.3.1.1. |
| 763 |
|
| 764 |
Path-Test: Initiates a station path test. |
| 765 |
The Path_Test variable (See ANSI Ref. 9.4.1) is |
| 766 |
set to Testing. The results of this action are |
| 767 |
not specified in this standard. |
| 768 |
|
| 769 |
Self-Test: Initiates a station self test. |
| 770 |
The results of this action are not specified in |
| 771 |
this standard. |
| 772 |
|
| 773 |
Attempts to set this object to all other values |
| 774 |
results in a badValue error. Agents may elect to |
| 775 |
return a badValue error on attempts to set this |
| 776 |
variable to path-Test(4) or self-Test(5)." |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Case [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 783 |
|
| 784 |
|
| 785 |
REFERENCE |
| 786 |
"ANSI { fddiSMT 60 }" |
| 787 |
::= { snmpFddiSMTEntry 19 } |
| 788 |
|
| 789 |
|
| 790 |
-- the MAC group |
| 791 |
-- Implementation of the MAC Group is mandatory for all |
| 792 |
-- systems which implement manageable FDDI subsystems. |
| 793 |
|
| 794 |
snmpFddiMACNumber OBJECT-TYPE |
| 795 |
SYNTAX INTEGER (0..65535) |
| 796 |
ACCESS read-only |
| 797 |
STATUS mandatory |
| 798 |
DESCRIPTION |
| 799 |
"The total number of MAC implementations (across |
| 800 |
all SMTs) on this network management application |
| 801 |
entity. The value for this variable must remain |
| 802 |
constant at least from one re-initialization of |
| 803 |
the entity's network management system to the next |
| 804 |
re-initialization." |
| 805 |
::= { snmpFddiMAC 1 } |
| 806 |
|
| 807 |
|
| 808 |
-- the MAC table |
| 809 |
|
| 810 |
snmpFddiMACTable OBJECT-TYPE |
| 811 |
SYNTAX SEQUENCE OF SnmpFddiMACEntry |
| 812 |
ACCESS not-accessible |
| 813 |
STATUS mandatory |
| 814 |
DESCRIPTION |
| 815 |
"A list of MAC entries. The number of entries is |
| 816 |
given by the value of snmpFddiMACNumber." |
| 817 |
::= { snmpFddiMAC 2 } |
| 818 |
|
| 819 |
snmpFddiMACEntry OBJECT-TYPE |
| 820 |
SYNTAX SnmpFddiMACEntry |
| 821 |
ACCESS not-accessible |
| 822 |
STATUS mandatory |
| 823 |
DESCRIPTION |
| 824 |
"A MAC entry containing information common to a |
| 825 |
given MAC." |
| 826 |
INDEX { snmpFddiMACSMTIndex, snmpFddiMACIndex } |
| 827 |
::= { snmpFddiMACTable 1 } |
| 828 |
|
| 829 |
SnmpFddiMACEntry ::= |
| 830 |
SEQUENCE { |
| 831 |
snmpFddiMACSMTIndex |
| 832 |
INTEGER, |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Case [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 839 |
|
| 840 |
|
| 841 |
snmpFddiMACIndex |
| 842 |
INTEGER, |
| 843 |
snmpFddiMACFrameStatusCapabilities |
| 844 |
INTEGER, |
| 845 |
snmpFddiMACTMaxGreatestLowerBound |
| 846 |
FddiTime, |
| 847 |
snmpFddiMACTVXGreatestLowerBound |
| 848 |
FddiTime, |
| 849 |
snmpFddiMACPathsAvailable |
| 850 |
INTEGER, |
| 851 |
snmpFddiMACCurrentPath |
| 852 |
INTEGER, |
| 853 |
snmpFddiMACUpstreamNbr |
| 854 |
FddiMACLongAddressType, |
| 855 |
snmpFddiMACOldUpstreamNbr |
| 856 |
FddiMACLongAddressType, |
| 857 |
snmpFddiMACDupAddrTest |
| 858 |
INTEGER, |
| 859 |
snmpFddiMACPathsRequested |
| 860 |
INTEGER, |
| 861 |
snmpFddiMACDownstreamPORTType |
| 862 |
INTEGER, |
| 863 |
snmpFddiMACSMTAddress |
| 864 |
FddiMACLongAddressType, |
| 865 |
snmpFddiMACTReq |
| 866 |
FddiTime, |
| 867 |
snmpFddiMACTNeg |
| 868 |
FddiTime, |
| 869 |
snmpFddiMACTMax |
| 870 |
FddiTime, |
| 871 |
snmpFddiMACTvxValue |
| 872 |
FddiTime, |
| 873 |
snmpFddiMACTMin |
| 874 |
FddiTime, |
| 875 |
snmpFddiMACCurrentFrameStatus |
| 876 |
INTEGER, |
| 877 |
snmpFddiMACFrameCts |
| 878 |
Counter, |
| 879 |
snmpFddiMACErrorCts |
| 880 |
Counter, |
| 881 |
snmpFddiMACLostCts |
| 882 |
Counter, |
| 883 |
snmpFddiMACFrameErrorThreshold |
| 884 |
INTEGER, |
| 885 |
snmpFddiMACFrameErrorRatio |
| 886 |
INTEGER, |
| 887 |
snmpFddiMACRMTState |
| 888 |
INTEGER, |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Case [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 895 |
|
| 896 |
|
| 897 |
snmpFddiMACDaFlag |
| 898 |
INTEGER, |
| 899 |
snmpFddiMACUnaDaFlag |
| 900 |
INTEGER, |
| 901 |
snmpFddiMACFrameCondition |
| 902 |
INTEGER, |
| 903 |
snmpFddiMACChipSet |
| 904 |
OBJECT IDENTIFIER, |
| 905 |
snmpFddiMACAction |
| 906 |
INTEGER |
| 907 |
} |
| 908 |
|
| 909 |
|
| 910 |
snmpFddiMACSMTIndex OBJECT-TYPE |
| 911 |
SYNTAX INTEGER (1..65535) |
| 912 |
ACCESS read-only |
| 913 |
STATUS mandatory |
| 914 |
DESCRIPTION |
| 915 |
"The value of the SMT index associated with this |
| 916 |
MAC." |
| 917 |
::= { snmpFddiMACEntry 1 } |
| 918 |
|
| 919 |
snmpFddiMACIndex OBJECT-TYPE |
| 920 |
SYNTAX INTEGER (1..65535) |
| 921 |
ACCESS read-only |
| 922 |
STATUS mandatory |
| 923 |
DESCRIPTION |
| 924 |
"A unique value for each MAC on the managed |
| 925 |
entity. The MAC identified by a particular value |
| 926 |
of this index is that identified by the same value |
| 927 |
of an ifIndex object instance. That is, if a MAC |
| 928 |
is associated with the interface whose value of |
| 929 |
ifIndex in the Internet-Standard MIB is equal to |
| 930 |
5, then the value of snmpFddiMACIndex shall also |
| 931 |
equal 5. The value for each MAC must remain |
| 932 |
constant at least from one re-initialization of |
| 933 |
the entity's network management system to the next |
| 934 |
re-initialization." |
| 935 |
::= { snmpFddiMACEntry 2 } |
| 936 |
|
| 937 |
snmpFddiMACFrameStatusCapabilities OBJECT-TYPE |
| 938 |
SYNTAX INTEGER (0..1799) |
| 939 |
ACCESS read-only |
| 940 |
STATUS mandatory |
| 941 |
DESCRIPTION |
| 942 |
"A value that indicates the MAC's bridge and end- |
| 943 |
station capabilities for operating in a bridged |
| 944 |
FDDI network. |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Case [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 951 |
|
| 952 |
|
| 953 |
The value is a sum. This value initially takes |
| 954 |
the value zero, then for each capability present, |
| 955 |
2 raised to a power is added to the sum. The |
| 956 |
powers are according to the following table: |
| 957 |
|
| 958 |
|
| 959 |
Capability Power |
| 960 |
FSC-Type0 0 |
| 961 |
-- MAC repeats A/C indicators as received on |
| 962 |
-- copying with the intent to forward. |
| 963 |
|
| 964 |
FSC-Type1 1 |
| 965 |
-- MAC sets C but not A on copying for |
| 966 |
-- forwarding. |
| 967 |
|
| 968 |
FSC-Type2 2 |
| 969 |
-- MAC resets C and sets A on C set and |
| 970 |
-- A reset if the frame is not copied and the |
| 971 |
-- frame was addressed to this MAC |
| 972 |
|
| 973 |
FSC-Type0-programmable 8 |
| 974 |
-- Type0 capability is programmable |
| 975 |
|
| 976 |
FSC-Type1-programmable 9 |
| 977 |
-- Type1 capability is programmable |
| 978 |
|
| 979 |
FSC-Type2-programmable 10 |
| 980 |
-- Type2 capability is programmable |
| 981 |
" |
| 982 |
REFERENCE |
| 983 |
"ANSI { fddiMAC 11 }" |
| 984 |
::= { snmpFddiMACEntry 3 } |
| 985 |
|
| 986 |
snmpFddiMACTMaxGreatestLowerBound OBJECT-TYPE |
| 987 |
SYNTAX FddiTime |
| 988 |
ACCESS read-write |
| 989 |
STATUS mandatory |
| 990 |
DESCRIPTION |
| 991 |
"The greatest lower bound of T_Max supported for |
| 992 |
this MAC." |
| 993 |
REFERENCE |
| 994 |
"ANSI { fddiMAC 13 }" |
| 995 |
::= { snmpFddiMACEntry 4 } |
| 996 |
|
| 997 |
snmpFddiMACTVXGreatestLowerBound OBJECT-TYPE |
| 998 |
SYNTAX FddiTime |
| 999 |
ACCESS read-only |
| 1000 |
STATUS mandatory |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Case [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
DESCRIPTION |
| 1010 |
"The greatest lower bound of TVX supported for |
| 1011 |
this MAC." |
| 1012 |
REFERENCE |
| 1013 |
"ANSI { fddiMAC 14 }" |
| 1014 |
::= { snmpFddiMACEntry 5 } |
| 1015 |
|
| 1016 |
snmpFddiMACPathsAvailable OBJECT-TYPE |
| 1017 |
SYNTAX INTEGER (0..7) |
| 1018 |
ACCESS read-only |
| 1019 |
STATUS mandatory |
| 1020 |
DESCRIPTION |
| 1021 |
"A value that indicates the PATH types available |
| 1022 |
for this MAC. |
| 1023 |
|
| 1024 |
The value is a sum. This value initially takes |
| 1025 |
the value zero, then for each type of PATH that |
| 1026 |
this MAC has available, 2 raised to a power is |
| 1027 |
added to the sum. The powers are according to the |
| 1028 |
following table: |
| 1029 |
|
| 1030 |
Path Power |
| 1031 |
Primary 0 |
| 1032 |
Secondary 1 |
| 1033 |
Local 2 " |
| 1034 |
REFERENCE |
| 1035 |
"ANSI { fddiMAC 22 }" |
| 1036 |
::= { snmpFddiMACEntry 6 } |
| 1037 |
|
| 1038 |
snmpFddiMACCurrentPath OBJECT-TYPE |
| 1039 |
SYNTAX INTEGER { |
| 1040 |
unknown(1), |
| 1041 |
primary(2), |
| 1042 |
secondary(4), |
| 1043 |
local(8), |
| 1044 |
isolated(16) |
| 1045 |
} |
| 1046 |
ACCESS read-only |
| 1047 |
STATUS mandatory |
| 1048 |
DESCRIPTION |
| 1049 |
"Indicates the association of the MAC with a |
| 1050 |
station PATH." |
| 1051 |
REFERENCE |
| 1052 |
"ANSI { fddiMAC 23 }" |
| 1053 |
::= { snmpFddiMACEntry 7 } |
| 1054 |
|
| 1055 |
snmpFddiMACUpstreamNbr OBJECT-TYPE |
| 1056 |
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Case [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
ACCESS read-only |
| 1066 |
STATUS mandatory |
| 1067 |
DESCRIPTION |
| 1068 |
"The MAC's upstream neighbor's long individual MAC |
| 1069 |
address. It may be determined by the Neighbor |
| 1070 |
Information Frame protocol (refer to ANSI SMT |
| 1071 |
7.2.1). The value shall be reported as '00 00 00 |
| 1072 |
00 00 00' if it is unknown." |
| 1073 |
REFERENCE |
| 1074 |
"ANSI { fddiMAC 24 }" |
| 1075 |
::= { snmpFddiMACEntry 8 } |
| 1076 |
|
| 1077 |
snmpFddiMACOldUpstreamNbr OBJECT-TYPE |
| 1078 |
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) |
| 1079 |
ACCESS read-only |
| 1080 |
STATUS mandatory |
| 1081 |
DESCRIPTION |
| 1082 |
"The previous value of the MAC's upstream |
| 1083 |
neighbor's long individual MAC address. It may be |
| 1084 |
determined by the Neighbor Information Frame |
| 1085 |
protocol (refer to ANSI SMT 7.2.1). The value |
| 1086 |
shall be reported as '00 00 00 00 00 00' if it is |
| 1087 |
unknown." |
| 1088 |
REFERENCE |
| 1089 |
"ANSI { fddiMAC 26 }" |
| 1090 |
::= { snmpFddiMACEntry 9 } |
| 1091 |
|
| 1092 |
snmpFddiMACDupAddrTest OBJECT-TYPE |
| 1093 |
SYNTAX INTEGER { none(1), pass(2), fail(3) } |
| 1094 |
ACCESS read-only |
| 1095 |
STATUS mandatory |
| 1096 |
DESCRIPTION |
| 1097 |
"The Duplicate Address Test flag, Dup_Addr_Test |
| 1098 |
(refer to ANSI 8.3.1)." |
| 1099 |
REFERENCE |
| 1100 |
"ANSI { fddiMAC 29 }" |
| 1101 |
::= { snmpFddiMACEntry 10 } |
| 1102 |
|
| 1103 |
snmpFddiMACPathsRequested OBJECT-TYPE |
| 1104 |
SYNTAX INTEGER |
| 1105 |
ACCESS read-write |
| 1106 |
STATUS mandatory |
| 1107 |
DESCRIPTION |
| 1108 |
"A value that indicates PATH(s) desired for this |
| 1109 |
MAC. |
| 1110 |
|
| 1111 |
The value is a sum which represents the individual |
| 1112 |
PATHs that are desired. This value initially |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Case [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
takes the value zero, then for each type of PATH |
| 1122 |
that this node is, 2 raised to a power is added to |
| 1123 |
the sum. The powers are according to the |
| 1124 |
following table: |
| 1125 |
|
| 1126 |
Path Power |
| 1127 |
Primary 0 |
| 1128 |
Secondary 1 |
| 1129 |
Local 2 |
| 1130 |
Isolated 3 |
| 1131 |
|
| 1132 |
The precedence order is primary, secondary, local, |
| 1133 |
and then isolated if multiple PATHs are desired |
| 1134 |
are set." |
| 1135 |
REFERENCE |
| 1136 |
"ANSI { fddiMAC 32 }" |
| 1137 |
::= { snmpFddiMACEntry 11 } |
| 1138 |
|
| 1139 |
snmpFddiMACDownstreamPORTType OBJECT-TYPE |
| 1140 |
SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) } |
| 1141 |
ACCESS read-only |
| 1142 |
STATUS mandatory |
| 1143 |
DESCRIPTION |
| 1144 |
"Indicates the PC-Type of the first port that is |
| 1145 |
downstream of this MAC (the exit port)." |
| 1146 |
REFERENCE |
| 1147 |
"ANSI { fddiMAC 33 }" |
| 1148 |
::= { snmpFddiMACEntry 12 } |
| 1149 |
|
| 1150 |
snmpFddiMACSMTAddress OBJECT-TYPE |
| 1151 |
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) |
| 1152 |
ACCESS read-only |
| 1153 |
STATUS mandatory |
| 1154 |
DESCRIPTION |
| 1155 |
"The 48 bit individual address of the MAC used for |
| 1156 |
SMT frames." |
| 1157 |
REFERENCE |
| 1158 |
"ANSI { fddiMAC 41 }" |
| 1159 |
::= { snmpFddiMACEntry 13 } |
| 1160 |
|
| 1161 |
snmpFddiMACTReq OBJECT-TYPE |
| 1162 |
SYNTAX FddiTime |
| 1163 |
ACCESS read-write |
| 1164 |
STATUS mandatory |
| 1165 |
DESCRIPTION |
| 1166 |
"The value of T-Req (refer to ANSI MAC 2.2.1 and |
| 1167 |
ANSI MAC 7.3.5.2)." |
| 1168 |
REFERENCE |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Case [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
"ANSI { fddiMAC 51 }" |
| 1178 |
::= { snmpFddiMACEntry 14 } |
| 1179 |
|
| 1180 |
snmpFddiMACTNeg OBJECT-TYPE |
| 1181 |
SYNTAX FddiTime |
| 1182 |
ACCESS read-only |
| 1183 |
STATUS mandatory |
| 1184 |
DESCRIPTION |
| 1185 |
"The value of T-Neg (refer to ANSI MAC 2.2.1 and |
| 1186 |
ANSI MAC 7.3.5.2)." |
| 1187 |
REFERENCE |
| 1188 |
"ANSI { fddiMAC 52 }" |
| 1189 |
::= { snmpFddiMACEntry 15 } |
| 1190 |
|
| 1191 |
snmpFddiMACTMax OBJECT-TYPE |
| 1192 |
SYNTAX FddiTime |
| 1193 |
ACCESS read-only |
| 1194 |
STATUS mandatory |
| 1195 |
DESCRIPTION |
| 1196 |
"The value of T-Max (refer to ANSI MAC 2.2.1 and |
| 1197 |
ANSI MAC 7.3.5.2)." |
| 1198 |
REFERENCE |
| 1199 |
"ANSI { fddiMAC 53 }" |
| 1200 |
::= { snmpFddiMACEntry 16 } |
| 1201 |
|
| 1202 |
snmpFddiMACTvxValue OBJECT-TYPE |
| 1203 |
SYNTAX FddiTime |
| 1204 |
ACCESS read-only |
| 1205 |
STATUS mandatory |
| 1206 |
DESCRIPTION |
| 1207 |
"The value of TvxValue (refer to ANSI MAC 2.2.1 |
| 1208 |
and ANSI MAC 7.3.5.2)." |
| 1209 |
REFERENCE |
| 1210 |
"ANSI { fddiMAC 54 }" |
| 1211 |
::= { snmpFddiMACEntry 17 } |
| 1212 |
|
| 1213 |
snmpFddiMACTMin OBJECT-TYPE |
| 1214 |
SYNTAX FddiTime |
| 1215 |
ACCESS read-only |
| 1216 |
STATUS mandatory |
| 1217 |
DESCRIPTION |
| 1218 |
"The value of T-Min (refer to ANSI MAC 2.2.1 and |
| 1219 |
ANSI MAC 7.3.5.2)." |
| 1220 |
REFERENCE |
| 1221 |
"ANSI { fddiMAC 55 }" |
| 1222 |
::= { snmpFddiMACEntry 18 } |
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Case [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
snmpFddiMACCurrentFrameStatus OBJECT-TYPE |
| 1234 |
SYNTAX INTEGER (0..7) |
| 1235 |
ACCESS read-write |
| 1236 |
STATUS mandatory |
| 1237 |
DESCRIPTION |
| 1238 |
"A value that indicates the MAC's operational |
| 1239 |
frame status setting functionality. |
| 1240 |
|
| 1241 |
The value is a sum. This value initially takes |
| 1242 |
the value zero, then for each functionality |
| 1243 |
present, 2 raised to a power is added to the sum. |
| 1244 |
The powers are according to the following table: |
| 1245 |
|
| 1246 |
Functionality Power |
| 1247 |
FSC-Type0 0 |
| 1248 |
-- MAC repeats A/C indicators as received |
| 1249 |
|
| 1250 |
FSC-Type1 1 |
| 1251 |
-- MAC sets C but not A on copying for |
| 1252 |
-- forwarding |
| 1253 |
|
| 1254 |
FSC-Type2 2 |
| 1255 |
-- MAC resets C and sets A on C set and A |
| 1256 |
-- reset if frame is not copied |
| 1257 |
" |
| 1258 |
REFERENCE |
| 1259 |
"ANSI { fddiMAC 63 }" |
| 1260 |
::= { snmpFddiMACEntry 19 } |
| 1261 |
|
| 1262 |
snmpFddiMACFrameCts OBJECT-TYPE |
| 1263 |
SYNTAX Counter |
| 1264 |
ACCESS read-only |
| 1265 |
STATUS mandatory |
| 1266 |
DESCRIPTION |
| 1267 |
"Frame_Ct (refer to ANSI MAC 2.2.1)." |
| 1268 |
REFERENCE |
| 1269 |
"ANSI { fddiMAC 71 }" |
| 1270 |
::= { snmpFddiMACEntry 20 } |
| 1271 |
|
| 1272 |
snmpFddiMACErrorCts OBJECT-TYPE |
| 1273 |
SYNTAX Counter |
| 1274 |
ACCESS read-only |
| 1275 |
STATUS mandatory |
| 1276 |
DESCRIPTION |
| 1277 |
"Error_Ct (refer to ANSI MAC 2.2.1)." |
| 1278 |
REFERENCE |
| 1279 |
"ANSI { fddiMAC 81 }" |
| 1280 |
::= { snmpFddiMACEntry 21 } |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Case [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
snmpFddiMACLostCts OBJECT-TYPE |
| 1290 |
SYNTAX Counter |
| 1291 |
ACCESS read-only |
| 1292 |
STATUS mandatory |
| 1293 |
DESCRIPTION |
| 1294 |
"Lost_Ct (refer to ANSI MAC 2.2.1)." |
| 1295 |
REFERENCE |
| 1296 |
"ANSI { fddiMAC 82 }" |
| 1297 |
::= { snmpFddiMACEntry 22 } |
| 1298 |
|
| 1299 |
snmpFddiMACFrameErrorThreshold OBJECT-TYPE |
| 1300 |
SYNTAX INTEGER (1..65535) |
| 1301 |
ACCESS read-only |
| 1302 |
STATUS mandatory |
| 1303 |
DESCRIPTION |
| 1304 |
"A threshold for determining when a MAC Condition |
| 1305 |
report should be generated. The condition is true |
| 1306 |
when the ratio, ((delta snmpFddiMACLostCt + delta |
| 1307 |
snmpFddiMACErrorCt) / (delta snmpFddiMACFrameCt + |
| 1308 |
delta snmpFddiMACLostCt)) x 2**16. exceeds the |
| 1309 |
threshold. It is used to determine when a station |
| 1310 |
has an unacceptable frame error threshold. The |
| 1311 |
sampling algorithm is implementation dependent. |
| 1312 |
Any attempt to set this variable to a value of |
| 1313 |
less than one shall result in a badValue error. |
| 1314 |
Those who are familiar with the SNMP management |
| 1315 |
framework will recognize that thresholds are not |
| 1316 |
in keeping with the SNMP philosophy. However, |
| 1317 |
this variable is supported by underlying SMT |
| 1318 |
implementations already and maintaining this |
| 1319 |
threshold should not pose an undue additional |
| 1320 |
burden on SNMP agent implementors." |
| 1321 |
REFERENCE |
| 1322 |
"ANSI { fddiMAC 95 }" |
| 1323 |
::= { snmpFddiMACEntry 23 } |
| 1324 |
|
| 1325 |
snmpFddiMACFrameErrorRatio OBJECT-TYPE |
| 1326 |
SYNTAX INTEGER (1..65535) |
| 1327 |
ACCESS read-only |
| 1328 |
STATUS mandatory |
| 1329 |
DESCRIPTION |
| 1330 |
"This attribute is the actual ratio, ((delta |
| 1331 |
snmpFddiMACLostCt + delta snmpFddiMACErrorCt) / |
| 1332 |
(delta snmpFddiMACFrameCt + delta |
| 1333 |
snmpFddiMACLostCt)) x 2**16." |
| 1334 |
REFERENCE |
| 1335 |
"ANSI { fddiMAC 96 }" |
| 1336 |
::= { snmpFddiMACEntry 24 } |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Case [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
snmpFddiMACRMTState OBJECT-TYPE |
| 1346 |
SYNTAX INTEGER { |
| 1347 |
rm0(1), -- Isolated |
| 1348 |
rm1(2), -- Non_Op |
| 1349 |
rm2(3), -- Ring_Op |
| 1350 |
rm3(4), -- Detect |
| 1351 |
rm4(5), -- Non_Op_Dup |
| 1352 |
rm5(6), -- Ring_Op_Dup |
| 1353 |
rm6(7), -- Directed |
| 1354 |
rm7(8) -- Trace |
| 1355 |
} |
| 1356 |
ACCESS read-only |
| 1357 |
STATUS mandatory |
| 1358 |
DESCRIPTION |
| 1359 |
"Indicates the current state of the Ring |
| 1360 |
Management state machine (refer to ANSI <a href="#section-10">Section</a> |
| 1361 |
<a href="#section-10">10</a>)." |
| 1362 |
REFERENCE |
| 1363 |
"ANSI { fddiMAC 111 }" |
| 1364 |
::= { snmpFddiMACEntry 25 } |
| 1365 |
|
| 1366 |
snmpFddiMACDaFlag OBJECT-TYPE |
| 1367 |
SYNTAX INTEGER { true(1), false(2) } |
| 1368 |
ACCESS read-only |
| 1369 |
STATUS mandatory |
| 1370 |
DESCRIPTION |
| 1371 |
"The RMT flag Duplicate Address Flag, DA_Flag |
| 1372 |
(refer to ANSI 10.3.1.2)." |
| 1373 |
REFERENCE |
| 1374 |
"ANSI { fddiMAC 112 }" |
| 1375 |
::= { snmpFddiMACEntry 26 } |
| 1376 |
|
| 1377 |
snmpFddiMACUnaDaFlag OBJECT-TYPE |
| 1378 |
SYNTAX INTEGER { true(1), false(2) } |
| 1379 |
ACCESS read-only |
| 1380 |
STATUS mandatory |
| 1381 |
DESCRIPTION |
| 1382 |
"A flag set when the upstream neighbor reports a |
| 1383 |
duplicate address condition. Reset when the |
| 1384 |
condition clears." |
| 1385 |
REFERENCE |
| 1386 |
"ANSI { fddiMAC 113 }" |
| 1387 |
::= { snmpFddiMACEntry 27 } |
| 1388 |
|
| 1389 |
snmpFddiMACFrameCondition OBJECT-TYPE |
| 1390 |
SYNTAX INTEGER { true(1), false(2) } |
| 1391 |
ACCESS read-only |
| 1392 |
STATUS mandatory |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Case [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
DESCRIPTION |
| 1402 |
"Indicates the MAC Condition is active when set. |
| 1403 |
Cleared when the condition clears and on power |
| 1404 |
up." |
| 1405 |
REFERENCE |
| 1406 |
"ANSI { fddiMAC 114 }" |
| 1407 |
::= { snmpFddiMACEntry 28 } |
| 1408 |
|
| 1409 |
snmpFddiMACChipSet OBJECT-TYPE |
| 1410 |
SYNTAX OBJECT IDENTIFIER |
| 1411 |
ACCESS read-only |
| 1412 |
STATUS mandatory |
| 1413 |
DESCRIPTION |
| 1414 |
"This object identifies the hardware chip(s) which |
| 1415 |
is (are) principally responsible for the |
| 1416 |
implementation of the MAC function. A few OBJECT |
| 1417 |
IDENTIFIERS are identified elsewhere in this memo. |
| 1418 |
For those The assignment of additional OBJECT |
| 1419 |
IDENTIFIERs to various types of hardware chip sets |
| 1420 |
is managed by the IANA. For example, vendors |
| 1421 |
whose chip sets are not defined in this memo may |
| 1422 |
request a number from the Internet Assigned |
| 1423 |
Numbers Authority (IANA) which indicates the |
| 1424 |
assignment of a enterprise specific subtree which, |
| 1425 |
among other things, may be used to allocate OBJECT |
| 1426 |
IDENTIFIER assignments for that enterprise's chip |
| 1427 |
sets. Similarly, in the absence of an |
| 1428 |
appropriately assigned OBJECT IDENTIFIER in this |
| 1429 |
memo or in an enterprise specific subtree of a |
| 1430 |
chip vendor, a board or system vendor can request |
| 1431 |
a number for a subtree from the IANA and make an |
| 1432 |
appropriate assignment. It is desired that, |
| 1433 |
whenever possible, the same OBJECT IDENTIFIER be |
| 1434 |
used for all chips of a given type. Consequently, |
| 1435 |
the assignment made in this memo for a chip, if |
| 1436 |
any, should be used in preference to any other |
| 1437 |
assignment and the assignment made by the chip |
| 1438 |
manufacturer, if any, should be used in preference |
| 1439 |
to assignments made by users of those chips. If |
| 1440 |
the hardware chip set is unknown, the object |
| 1441 |
identifier |
| 1442 |
|
| 1443 |
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } |
| 1444 |
|
| 1445 |
is returned. Note that unknownChipSet is a |
| 1446 |
syntactically valid object identifier, and any |
| 1447 |
conformant implementation of ASN.1 and the BER |
| 1448 |
must be able to generate and recognize this |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Case [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
value." |
| 1458 |
::= { snmpFddiMACEntry 29 } |
| 1459 |
|
| 1460 |
snmpFddiMACAction OBJECT-TYPE |
| 1461 |
SYNTAX INTEGER { |
| 1462 |
other(1), -- none of the following |
| 1463 |
enableLLCService(2), |
| 1464 |
disableLLCService(3), |
| 1465 |
connectMAC(4), |
| 1466 |
disconnectMAC(5) |
| 1467 |
} |
| 1468 |
ACCESS read-write |
| 1469 |
STATUS mandatory |
| 1470 |
DESCRIPTION |
| 1471 |
"This object, when read, always returns a value of |
| 1472 |
other(1). The behavior of setting this variable |
| 1473 |
to each of the acceptable values is as follows: |
| 1474 |
|
| 1475 |
Other: Results in a badValue |
| 1476 |
error. |
| 1477 |
|
| 1478 |
enableLLCService: enables MAC service to |
| 1479 |
higher layers. |
| 1480 |
|
| 1481 |
disableLLCService: disables MAC service to |
| 1482 |
higher layers. |
| 1483 |
|
| 1484 |
connectMAC: connect this MAC in |
| 1485 |
station. |
| 1486 |
|
| 1487 |
disconnectMAC: disconnect this MAC in |
| 1488 |
station. |
| 1489 |
|
| 1490 |
Attempts to set this object to all other values |
| 1491 |
results in a badValue error." |
| 1492 |
REFERENCE |
| 1493 |
"ANSI { fddiMAC 130 }" |
| 1494 |
::= { snmpFddiMACEntry 30 } |
| 1495 |
|
| 1496 |
|
| 1497 |
-- the PATH group |
| 1498 |
|
| 1499 |
-- the PATH group is empty for now and shall remain so until |
| 1500 |
-- the ANSI community sorts out their PATH group |
| 1501 |
|
| 1502 |
|
| 1503 |
-- the PORT group |
| 1504 |
-- Implementation of the PORT group is mandatory for all |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Case [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
-- systems which implement manageable FDDI subsystems. |
| 1514 |
|
| 1515 |
snmpFddiPORTNumber OBJECT-TYPE |
| 1516 |
SYNTAX INTEGER (0..65535) |
| 1517 |
ACCESS read-only |
| 1518 |
STATUS mandatory |
| 1519 |
DESCRIPTION |
| 1520 |
"The total number of PORT implementations (across |
| 1521 |
all SMTs) on this network management application |
| 1522 |
entity. The value for this variable must remain |
| 1523 |
constant at least from one re-initialization of |
| 1524 |
the entity's network management system to the next |
| 1525 |
re-initialization." |
| 1526 |
::= { snmpFddiPORT 1 } |
| 1527 |
|
| 1528 |
|
| 1529 |
-- the PORT table |
| 1530 |
|
| 1531 |
snmpFddiPORTTable OBJECT-TYPE |
| 1532 |
SYNTAX SEQUENCE OF SnmpFddiPORTEntry |
| 1533 |
ACCESS not-accessible |
| 1534 |
STATUS mandatory |
| 1535 |
DESCRIPTION |
| 1536 |
"A list of PORT entries. The number of entries is |
| 1537 |
given by the value of snmpFddiPORTNumber." |
| 1538 |
::= { snmpFddiPORT 2 } |
| 1539 |
|
| 1540 |
snmpFddiPORTEntry OBJECT-TYPE |
| 1541 |
SYNTAX SnmpFddiPORTEntry |
| 1542 |
ACCESS not-accessible |
| 1543 |
STATUS mandatory |
| 1544 |
DESCRIPTION |
| 1545 |
"A PORT entry containing information common to a |
| 1546 |
given PORT." |
| 1547 |
INDEX { snmpFddiPORTSMTIndex, snmpFddiPORTIndex } |
| 1548 |
::= { snmpFddiPORTTable 1 } |
| 1549 |
|
| 1550 |
SnmpFddiPORTEntry ::= |
| 1551 |
SEQUENCE { |
| 1552 |
snmpFddiPORTSMTIndex |
| 1553 |
INTEGER, |
| 1554 |
snmpFddiPORTIndex |
| 1555 |
INTEGER, |
| 1556 |
snmpFddiPORTPCType |
| 1557 |
INTEGER, |
| 1558 |
snmpFddiPORTPCNeighbor |
| 1559 |
INTEGER, |
| 1560 |
snmpFddiPORTConnectionPolicies |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Case [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
INTEGER, |
| 1570 |
snmpFddiPORTRemoteMACIndicated |
| 1571 |
INTEGER, |
| 1572 |
snmpFddiPORTCEState |
| 1573 |
INTEGER, |
| 1574 |
snmpFddiPORTPathsRequested |
| 1575 |
INTEGER, |
| 1576 |
snmpFddiPORTMACPlacement |
| 1577 |
FddiResourceId, |
| 1578 |
snmpFddiPORTAvailablePaths |
| 1579 |
INTEGER, |
| 1580 |
snmpFddiPORTMACLoopTime |
| 1581 |
FddiTime, |
| 1582 |
snmpFddiPORTTBMax |
| 1583 |
FddiTime, |
| 1584 |
snmpFddiPORTBSFlag |
| 1585 |
INTEGER, |
| 1586 |
snmpFddiPORTLCTFailCts |
| 1587 |
Counter, |
| 1588 |
snmpFddiPORTLerEstimate |
| 1589 |
INTEGER, |
| 1590 |
snmpFddiPORTLemRejectCts |
| 1591 |
Counter, |
| 1592 |
snmpFddiPORTLemCts |
| 1593 |
Counter, |
| 1594 |
snmpFddiPORTLerCutoff |
| 1595 |
INTEGER, |
| 1596 |
snmpFddiPORTLerAlarm |
| 1597 |
INTEGER, |
| 1598 |
snmpFddiPORTConnectState |
| 1599 |
INTEGER, |
| 1600 |
snmpFddiPORTPCMState |
| 1601 |
INTEGER, |
| 1602 |
snmpFddiPORTPCWithhold |
| 1603 |
INTEGER, |
| 1604 |
snmpFddiPORTLerCondition |
| 1605 |
INTEGER, |
| 1606 |
snmpFddiPORTChipSet |
| 1607 |
OBJECT IDENTIFIER, |
| 1608 |
snmpFddiPORTAction |
| 1609 |
INTEGER |
| 1610 |
} |
| 1611 |
|
| 1612 |
snmpFddiPORTSMTIndex OBJECT-TYPE |
| 1613 |
SYNTAX INTEGER (1..65535) |
| 1614 |
ACCESS read-only |
| 1615 |
STATUS mandatory |
| 1616 |
DESCRIPTION |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Case [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
"The value of the SMT index associated with this |
| 1626 |
PORT." |
| 1627 |
::= { snmpFddiPORTEntry 1 } |
| 1628 |
|
| 1629 |
snmpFddiPORTIndex OBJECT-TYPE |
| 1630 |
SYNTAX INTEGER (1..65535) |
| 1631 |
ACCESS read-only |
| 1632 |
STATUS mandatory |
| 1633 |
DESCRIPTION |
| 1634 |
"A unique value for each PORT within a given SMT. |
| 1635 |
Its value ranges between 1 and the sum of the |
| 1636 |
values of snmpFddiSMTNonMasterCt |
| 1637 |
{ snmpFddiSMTEntry 6 } and snmpFddiSMTMasterCt |
| 1638 |
{ snmpFddiSMTEntry 7 } on the given SMT. The |
| 1639 |
value for each PORT must remain constant at least |
| 1640 |
from one re-initialization of the entity's network |
| 1641 |
management system to the next re-initialization." |
| 1642 |
::= { snmpFddiPORTEntry 2 } |
| 1643 |
|
| 1644 |
snmpFddiPORTPCType OBJECT-TYPE |
| 1645 |
SYNTAX INTEGER { a(1), b(2), s(3), m(4) } |
| 1646 |
ACCESS read-only |
| 1647 |
STATUS mandatory |
| 1648 |
DESCRIPTION |
| 1649 |
"PC_Type (refer to ANSI SMT 9.2.2 and ANSI SMT |
| 1650 |
9.6.3.2)." |
| 1651 |
REFERENCE |
| 1652 |
"ANSI { fddiPORT 12 }" |
| 1653 |
::= { snmpFddiPORTEntry 3 } |
| 1654 |
|
| 1655 |
snmpFddiPORTPCNeighbor OBJECT-TYPE |
| 1656 |
SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) } |
| 1657 |
ACCESS read-only |
| 1658 |
STATUS mandatory |
| 1659 |
DESCRIPTION |
| 1660 |
"The type (PC_Neighbor) of the remote PORT that is |
| 1661 |
determined in PC_Signaling in R_Val (1,2) (refer |
| 1662 |
to ANSI SMT 9.6.3.2)." |
| 1663 |
REFERENCE |
| 1664 |
"ANSI { fddiPORT 13 }" |
| 1665 |
::= { snmpFddiPORTEntry 4 } |
| 1666 |
|
| 1667 |
snmpFddiPORTConnectionPolicies OBJECT-TYPE |
| 1668 |
SYNTAX INTEGER (0..7) |
| 1669 |
ACCESS read-write |
| 1670 |
STATUS mandatory |
| 1671 |
DESCRIPTION |
| 1672 |
"A value that indicates the node's PORT policies. |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Case [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Pc-MAC-LCT, Pc-MAC-Loop, and Pc-MAC-Placement |
| 1682 |
indicate how the respective PC Signaling |
| 1683 |
Capability flags should be set (refer to ANSI SMT |
| 1684 |
9.4.3.2). |
| 1685 |
|
| 1686 |
The value is a sum. This value initially takes |
| 1687 |
the value zero, then for each PORT policy, 2 |
| 1688 |
raised to a power is added to the sum. The powers |
| 1689 |
are according to the following table: |
| 1690 |
|
| 1691 |
Policy Power |
| 1692 |
Pc-MAC-LCT 0 |
| 1693 |
Pc-MAC-Loop 1 |
| 1694 |
Pc-MAC-Placement 2 " |
| 1695 |
REFERENCE |
| 1696 |
"ANSI { fddiPORT 14 }" |
| 1697 |
::= { snmpFddiPORTEntry 5 } |
| 1698 |
|
| 1699 |
snmpFddiPORTRemoteMACIndicated OBJECT-TYPE |
| 1700 |
SYNTAX INTEGER { true(1), false(2) } |
| 1701 |
ACCESS read-only |
| 1702 |
STATUS mandatory |
| 1703 |
DESCRIPTION |
| 1704 |
"The indication, in PC-Signaling that the remote |
| 1705 |
partner intends to place a MAC in the output token |
| 1706 |
PATH of this PORT. Signaled as R_Val (9) (refer |
| 1707 |
to ANSI SMT 9.6.3.2)." |
| 1708 |
REFERENCE |
| 1709 |
"ANSI { fddiPORT 15 }" |
| 1710 |
::= { snmpFddiPORTEntry 6 } |
| 1711 |
|
| 1712 |
snmpFddiPORTCEState OBJECT-TYPE |
| 1713 |
SYNTAX INTEGER { |
| 1714 |
ce0(1), -- Isolated |
| 1715 |
ce1(2), -- Insert_P |
| 1716 |
ce2(3), -- Insert_S |
| 1717 |
ce3(4), -- Insert_X |
| 1718 |
ce4(5) -- Local |
| 1719 |
} |
| 1720 |
ACCESS read-only |
| 1721 |
STATUS mandatory |
| 1722 |
DESCRIPTION |
| 1723 |
"Indicates the current state of PORT's |
| 1724 |
Configuration Element (CE) (refer to ANSI 9.7.5). |
| 1725 |
Note that this value represents the Current Path |
| 1726 |
information for this PORT." |
| 1727 |
REFERENCE |
| 1728 |
"ANSI { fddiPORT 16 }" |
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Case [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
::= { snmpFddiPORTEntry 7 } |
| 1738 |
|
| 1739 |
snmpFddiPORTPathsRequested OBJECT-TYPE |
| 1740 |
SYNTAX INTEGER (0..15) |
| 1741 |
ACCESS read-write |
| 1742 |
STATUS mandatory |
| 1743 |
DESCRIPTION |
| 1744 |
"A value that indicates the desired association(s) |
| 1745 |
of the port with a station PATH. The 'Primary' |
| 1746 |
Path is the default. The value of 'Secondary' is |
| 1747 |
only meaningful for S (slave) or M (master) PORT |
| 1748 |
PC-Types. This value effects the setting of the |
| 1749 |
CF_Insert_S, and CF_Insert_L flags (refer to ANSI |
| 1750 |
<a href="#section-9.4.3">Section 9.4.3</a>). If the 'Primary' PATH is present, |
| 1751 |
then the Primary PATH (the default PATH) is |
| 1752 |
selected. If the 'Secondary' PATH is present and |
| 1753 |
the 'Primary' PATH is not present, then the |
| 1754 |
CF_Insert_S flag is set. If the 'Local' PATH is |
| 1755 |
sent and neither the 'Primary' or 'Secondary' |
| 1756 |
PATHs are sent, then the CF_Insert_L flag is set. |
| 1757 |
|
| 1758 |
The value is a sum. This value initially takes |
| 1759 |
the value zero, then for each type of PATH |
| 1760 |
desired, 2 raised to a power is added to the sum. |
| 1761 |
The powers are according to the following table: |
| 1762 |
|
| 1763 |
Path Power |
| 1764 |
Primary 0 |
| 1765 |
Secondary 1 |
| 1766 |
Local 2 |
| 1767 |
Isolated 3 " |
| 1768 |
REFERENCE |
| 1769 |
"ANSI { fddiPORT 17 }" |
| 1770 |
::= { snmpFddiPORTEntry 8 } |
| 1771 |
|
| 1772 |
snmpFddiPORTMACPlacement OBJECT-TYPE |
| 1773 |
SYNTAX FddiResourceId -- INTEGER (0..65535) |
| 1774 |
ACCESS read-only |
| 1775 |
STATUS mandatory |
| 1776 |
DESCRIPTION |
| 1777 |
"Indicates the upstream MAC, if any, that is |
| 1778 |
associated with the PORT. The value shall be zero |
| 1779 |
if there is no MAC associated with the PORT. |
| 1780 |
Otherwise, the value shall be equal to the value |
| 1781 |
of snmpFddiMACIndex associated with the MAC." |
| 1782 |
REFERENCE |
| 1783 |
"ANSI { fddiPORT 18 }" |
| 1784 |
::= { snmpFddiPORTEntry 9 } |
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Case [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
snmpFddiPORTAvailablePaths OBJECT-TYPE |
| 1794 |
SYNTAX INTEGER (0..7) |
| 1795 |
ACCESS read-only |
| 1796 |
STATUS mandatory |
| 1797 |
DESCRIPTION |
| 1798 |
"A value that indicates the PATH types available |
| 1799 |
for M and S PORTs. |
| 1800 |
|
| 1801 |
The value is a sum. This value initially takes |
| 1802 |
the value zero, then for each type of PATH that |
| 1803 |
this port has available, 2 raised to a power is |
| 1804 |
added to the sum. The powers are according to the |
| 1805 |
following table: |
| 1806 |
|
| 1807 |
Path Power |
| 1808 |
Primary 0 |
| 1809 |
Secondary 1 |
| 1810 |
Local 2 " |
| 1811 |
REFERENCE |
| 1812 |
"ANSI { fddiPORT 19 }" |
| 1813 |
::= { snmpFddiPORTEntry 10 } |
| 1814 |
|
| 1815 |
snmpFddiPORTMACLoopTime OBJECT-TYPE |
| 1816 |
SYNTAX FddiTime |
| 1817 |
ACCESS read-write |
| 1818 |
STATUS mandatory |
| 1819 |
DESCRIPTION |
| 1820 |
"Time for the optional MAC Local Loop, T_Next(9), |
| 1821 |
which is greater-than or equal-to 200 milliseconds |
| 1822 |
(refer to ANSI SMT 9.4.4.2.3)." |
| 1823 |
REFERENCE |
| 1824 |
"ANSI { fddiPORT 21 }" |
| 1825 |
::= { snmpFddiPORTEntry 11 } |
| 1826 |
|
| 1827 |
snmpFddiPORTTBMax OBJECT-TYPE |
| 1828 |
SYNTAX FddiTime |
| 1829 |
ACCESS read-write |
| 1830 |
STATUS mandatory |
| 1831 |
DESCRIPTION |
| 1832 |
"TB_Max (refer to ANSI SMT 9.4.4.2.1)." |
| 1833 |
REFERENCE |
| 1834 |
"ANSI { fddiPORT 32 }" |
| 1835 |
::= { snmpFddiPORTEntry 12 } |
| 1836 |
|
| 1837 |
snmpFddiPORTBSFlag OBJECT-TYPE |
| 1838 |
SYNTAX INTEGER { true(1), false(2) } |
| 1839 |
ACCESS read-only |
| 1840 |
STATUS mandatory |
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Case [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
DESCRIPTION |
| 1850 |
"The Break State, BS_Flag (refer to ANSI SMT |
| 1851 |
9.4.3.4)." |
| 1852 |
REFERENCE |
| 1853 |
"ANSI { fddiPORT 33 }" |
| 1854 |
::= { snmpFddiPORTEntry 13 } |
| 1855 |
|
| 1856 |
snmpFddiPORTLCTFailCts OBJECT-TYPE |
| 1857 |
SYNTAX Counter |
| 1858 |
ACCESS read-only |
| 1859 |
STATUS mandatory |
| 1860 |
DESCRIPTION |
| 1861 |
"The count of the consecutive times the link |
| 1862 |
confidence test (LCT) has failed during connection |
| 1863 |
management (refer to ANSI 9.4.1)." |
| 1864 |
REFERENCE |
| 1865 |
"ANSI { fddiPORT 42 }" |
| 1866 |
::= { snmpFddiPORTEntry 14 } |
| 1867 |
|
| 1868 |
snmpFddiPORTLerEstimate OBJECT-TYPE |
| 1869 |
SYNTAX INTEGER (4..15) |
| 1870 |
ACCESS read-only |
| 1871 |
STATUS mandatory |
| 1872 |
DESCRIPTION |
| 1873 |
"A long term average link error rate. It ranges |
| 1874 |
from 10**-4 to 10**-15 and is reported as the |
| 1875 |
absolute value of the exponent of the estimate." |
| 1876 |
REFERENCE |
| 1877 |
"ANSI { fddiPORT 51 }" |
| 1878 |
::= { snmpFddiPORTEntry 15 } |
| 1879 |
|
| 1880 |
snmpFddiPORTLemRejectCts OBJECT-TYPE |
| 1881 |
SYNTAX Counter |
| 1882 |
ACCESS read-only |
| 1883 |
STATUS mandatory |
| 1884 |
DESCRIPTION |
| 1885 |
"A link error monitoring count of the times that a |
| 1886 |
link has been rejected." |
| 1887 |
REFERENCE |
| 1888 |
"ANSI { fddiPORT 52 }" |
| 1889 |
::= { snmpFddiPORTEntry 16 } |
| 1890 |
|
| 1891 |
snmpFddiPORTLemCts OBJECT-TYPE |
| 1892 |
SYNTAX Counter |
| 1893 |
ACCESS read-only |
| 1894 |
STATUS mandatory |
| 1895 |
DESCRIPTION |
| 1896 |
"The aggregate link error monitor error count, set |
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Case [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
to zero only on station power_up." |
| 1906 |
REFERENCE |
| 1907 |
"ANSI { fddiPORT 53 }" |
| 1908 |
::= { snmpFddiPORTEntry 17 } |
| 1909 |
|
| 1910 |
snmpFddiPORTLerCutoff OBJECT-TYPE |
| 1911 |
SYNTAX INTEGER (4..15) |
| 1912 |
ACCESS read-write |
| 1913 |
STATUS mandatory |
| 1914 |
DESCRIPTION |
| 1915 |
"The link error rate estimate at which a link |
| 1916 |
connection will be broken. It ranges from 10**-4 |
| 1917 |
to 10**-15 and is reported as the absolute value |
| 1918 |
of the exponent." |
| 1919 |
REFERENCE |
| 1920 |
"ANSI { fddiPORT 58 }" |
| 1921 |
::= { snmpFddiPORTEntry 18 } |
| 1922 |
|
| 1923 |
snmpFddiPORTLerAlarm OBJECT-TYPE |
| 1924 |
SYNTAX INTEGER (4..15) |
| 1925 |
ACCESS read-write |
| 1926 |
STATUS mandatory |
| 1927 |
DESCRIPTION |
| 1928 |
"The link error rate estimate at which a link |
| 1929 |
connection will generate an alarm. It ranges from |
| 1930 |
10**-4 to 10**-15 and is reported as the absolute |
| 1931 |
value of the exponent of the estimate." |
| 1932 |
REFERENCE |
| 1933 |
"ANSI { fddiPORT 59 }" |
| 1934 |
::= { snmpFddiPORTEntry 19 } |
| 1935 |
|
| 1936 |
snmpFddiPORTConnectState OBJECT-TYPE |
| 1937 |
SYNTAX INTEGER { |
| 1938 |
disabled(1), |
| 1939 |
connecting(2), |
| 1940 |
standby(3), |
| 1941 |
active(4) |
| 1942 |
} |
| 1943 |
ACCESS read-only |
| 1944 |
STATUS mandatory |
| 1945 |
DESCRIPTION |
| 1946 |
"An indication of the connect state of this PORT. |
| 1947 |
Basically, this gives a higher level view of the |
| 1948 |
state of the connection by grouping PCM states and |
| 1949 |
the PC-Withhold flag state. The supported values |
| 1950 |
and their corresponding PCM states and PC-Withhold |
| 1951 |
condition, when relevant, are: |
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Case [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
disabled: (PC0:Off, PC9:Maint) |
| 1962 |
|
| 1963 |
connecting: (PC1(Break) || PC3 (Connect) || PC4 |
| 1964 |
(Next) || PC5 (Signal) || PC6 |
| 1965 |
(Join) || PC7 (Verify)) && |
| 1966 |
(PC_Withhold = None) |
| 1967 |
|
| 1968 |
standby: (NOT PC_Withhold == None) |
| 1969 |
|
| 1970 |
active: (PC2:Trace || PC8:Active) " |
| 1971 |
REFERENCE |
| 1972 |
"ANSI { fddiPORT 61 }" |
| 1973 |
::= { snmpFddiPORTEntry 20 } |
| 1974 |
|
| 1975 |
snmpFddiPORTPCMState OBJECT-TYPE |
| 1976 |
SYNTAX INTEGER { |
| 1977 |
pc0(1), -- Off |
| 1978 |
pc1(2), -- Break |
| 1979 |
pc2(3), -- Trace |
| 1980 |
pc3(4), -- Connect |
| 1981 |
pc4(5), -- Next |
| 1982 |
pc5(6), -- Signal |
| 1983 |
pc6(7), -- Join |
| 1984 |
pc7(8), -- Verify |
| 1985 |
pc8(9), -- Active |
| 1986 |
pc9(10) -- Maint |
| 1987 |
} |
| 1988 |
ACCESS read-only |
| 1989 |
STATUS mandatory |
| 1990 |
DESCRIPTION |
| 1991 |
"(refer to SMT 9.6.2)." |
| 1992 |
REFERENCE |
| 1993 |
"ANSI { fddiPORT 62 }" |
| 1994 |
::= { snmpFddiPORTEntry 21 } |
| 1995 |
|
| 1996 |
snmpFddiPORTPCWithhold OBJECT-TYPE |
| 1997 |
SYNTAX INTEGER { none(1), m-m(2), other(3) } |
| 1998 |
ACCESS read-only |
| 1999 |
STATUS mandatory |
| 2000 |
DESCRIPTION |
| 2001 |
"PC_Withhold, (refer to ANSI SMT 9.4.1)." |
| 2002 |
REFERENCE |
| 2003 |
"ANSI { fddiPORT 63 }" |
| 2004 |
::= { snmpFddiPORTEntry 22 } |
| 2005 |
|
| 2006 |
snmpFddiPORTLerCondition OBJECT-TYPE |
| 2007 |
SYNTAX INTEGER { true(1), false(2) } |
| 2008 |
ACCESS read-only |
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Case [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
STATUS mandatory |
| 2018 |
DESCRIPTION |
| 2019 |
"This variable is set to true whenever LerEstimate |
| 2020 |
is less than or equal to LerAlarm." |
| 2021 |
REFERENCE |
| 2022 |
"ANSI { fddiPORT 64 }" |
| 2023 |
::= { snmpFddiPORTEntry 23 } |
| 2024 |
|
| 2025 |
snmpFddiPORTChipSet OBJECT-TYPE |
| 2026 |
SYNTAX OBJECT IDENTIFIER |
| 2027 |
ACCESS read-only |
| 2028 |
STATUS mandatory |
| 2029 |
DESCRIPTION |
| 2030 |
"This object identifies the hardware chip(s) which |
| 2031 |
is (are) principally responsible for the |
| 2032 |
implementation of the PORT (PHY) function. A few |
| 2033 |
OBJECT IDENTIFIERS are identified elsewhere in |
| 2034 |
this memo. For those The assignment of additional |
| 2035 |
OBJECT IDENTIFIERs to various types of hardware |
| 2036 |
chip sets is managed by the IANA. For example, |
| 2037 |
vendors whose chip sets are not defined in this |
| 2038 |
memo may request a number from the Internet |
| 2039 |
Assigned Numbers Authority (IANA) which indicates |
| 2040 |
the assignment of a enterprise specific subtree |
| 2041 |
which, among other things, may be used to allocate |
| 2042 |
OBJECT IDENTIFIER assignments for that |
| 2043 |
enterprise's chip sets. Similarly, in the absence |
| 2044 |
of an appropriately assigned OBJECT IDENTIFIER in |
| 2045 |
this memo or in an enterprise specific subtree of |
| 2046 |
a chip vendor, a board or system vendor can |
| 2047 |
request a number for a subtree from the IANA and |
| 2048 |
make an appropriate assignment. It is desired |
| 2049 |
that, whenever possible, the same OBJECT |
| 2050 |
IDENTIFIER be used for all chips of a given type. |
| 2051 |
Consequently, the assignment made in this memo for |
| 2052 |
a chip, if any, should be used in preference to |
| 2053 |
any other assignment and the assignment made by |
| 2054 |
the chip manufacturer, if any, should be used in |
| 2055 |
preference to assignments made by users of those |
| 2056 |
chips. If the hardware chip set is unknown, the |
| 2057 |
object identifier |
| 2058 |
|
| 2059 |
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } |
| 2060 |
|
| 2061 |
is returned. Note that unknownChipSet is a |
| 2062 |
syntactically valid object identifier, and any |
| 2063 |
conformant implementation of ASN.1 and the BER |
| 2064 |
must be able to generate and recognize this |
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Case [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
value." |
| 2074 |
::= { snmpFddiPORTEntry 24 } |
| 2075 |
|
| 2076 |
snmpFddiPORTAction OBJECT-TYPE |
| 2077 |
SYNTAX INTEGER { |
| 2078 |
other(1), -- none of the following |
| 2079 |
maintPORT(2), |
| 2080 |
enablePORT(3), |
| 2081 |
disablePORT(4), |
| 2082 |
startPORT(5), |
| 2083 |
stopPORT(6) |
| 2084 |
} |
| 2085 |
ACCESS read-write |
| 2086 |
STATUS mandatory |
| 2087 |
DESCRIPTION |
| 2088 |
"This object, when read, always returns a value of |
| 2089 |
other(1). The behavior of setting this variable |
| 2090 |
to each of the acceptable values is as follows: |
| 2091 |
|
| 2092 |
Other: Results in a badValue error. |
| 2093 |
|
| 2094 |
maintPORT: Signal PC_Maint |
| 2095 |
|
| 2096 |
enablePORT: Signal PC_Enable |
| 2097 |
|
| 2098 |
disablePORT: Signal PC_Disable |
| 2099 |
|
| 2100 |
startPORT: Signal PC_Start |
| 2101 |
|
| 2102 |
stopPORT: Signal PC_Stop |
| 2103 |
|
| 2104 |
Signals cause an SM_CM_CONTROL.request service to |
| 2105 |
be generated with a control_action of `Signal' and |
| 2106 |
the `variable' parameter set with the appropriate |
| 2107 |
value (i.e., PC_Maint, PC_Enable, PC_Disable, |
| 2108 |
PC_Start, PC_Stop). Ref. ANSI SMT <a href="#section-9.3.2">Section 9.3.2</a>. |
| 2109 |
|
| 2110 |
Attempts to set this object to all other values |
| 2111 |
results in a badValue error." |
| 2112 |
REFERENCE |
| 2113 |
"ANSI { fddiPORT 70 }" |
| 2114 |
::= { snmpFddiPORTEntry 25 } |
| 2115 |
|
| 2116 |
|
| 2117 |
-- the ATTACHMENT group |
| 2118 |
-- Implementation of the ATTACHMENT group is mandatory for |
| 2119 |
-- all systems which implement manageable FDDI subsystems. |
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Case [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
snmpFddiATTACHMENTNumber OBJECT-TYPE |
| 2130 |
SYNTAX INTEGER (0..65535) |
| 2131 |
ACCESS read-only |
| 2132 |
STATUS mandatory |
| 2133 |
DESCRIPTION |
| 2134 |
"The total number of attachments (across all SMTs) |
| 2135 |
on this network management application entity. |
| 2136 |
The value for this variable must remain constant |
| 2137 |
at least from one re-initialization of the |
| 2138 |
entity's network management system to the next |
| 2139 |
re-initialization." |
| 2140 |
::= { snmpFddiATTACHMENT 1 } |
| 2141 |
|
| 2142 |
|
| 2143 |
-- the ATTACHMENT table |
| 2144 |
|
| 2145 |
snmpFddiATTACHMENTTable OBJECT-TYPE |
| 2146 |
SYNTAX SEQUENCE OF SnmpFddiATTACHMENTEntry |
| 2147 |
ACCESS not-accessible |
| 2148 |
STATUS mandatory |
| 2149 |
DESCRIPTION |
| 2150 |
"A list of ATTACHMENT entries. The number of |
| 2151 |
entries is given by the value of |
| 2152 |
snmpFddiATTACHMENTNumber." |
| 2153 |
::= { snmpFddiATTACHMENT 2 } |
| 2154 |
|
| 2155 |
snmpFddiATTACHMENTEntry OBJECT-TYPE |
| 2156 |
SYNTAX SnmpFddiATTACHMENTEntry |
| 2157 |
ACCESS not-accessible |
| 2158 |
STATUS mandatory |
| 2159 |
DESCRIPTION |
| 2160 |
"An ATTACHMENT entry containing information common |
| 2161 |
to a given set of ATTACHMENTs. |
| 2162 |
|
| 2163 |
The ATTACHMENT Resource represents a PORT or a |
| 2164 |
pair of PORTs plus the optional associated optical |
| 2165 |
bypass that are managed as a functional unit. |
| 2166 |
Because of its relationship to the PORT Objects, |
| 2167 |
there is a natural association of ATTACHMENT |
| 2168 |
Resource Indices to the PORT Indices. The |
| 2169 |
resource index for the ATTACHMENT is equal to the |
| 2170 |
associated PORT index for 'single-attachment' and |
| 2171 |
'concentrator' type snmpFddiATTACHMENTClasses. |
| 2172 |
For 'dual-attachment' Classes, the ATTACHMENT |
| 2173 |
Index is the PORT Index of the A PORT of the A/B |
| 2174 |
PORT Pair that represents the ATTACHMENT." |
| 2175 |
INDEX { snmpFddiATTACHMENTSMTIndex, |
| 2176 |
snmpFddiATTACHMENTIndex } |
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Case [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
::= { snmpFddiATTACHMENTTable 1 } |
| 2186 |
|
| 2187 |
SnmpFddiATTACHMENTEntry ::= |
| 2188 |
SEQUENCE { |
| 2189 |
snmpFddiATTACHMENTSMTIndex |
| 2190 |
INTEGER, |
| 2191 |
snmpFddiATTACHMENTIndex |
| 2192 |
INTEGER, |
| 2193 |
snmpFddiATTACHMENTClass |
| 2194 |
INTEGER, |
| 2195 |
snmpFddiATTACHMENTOpticalBypassPresent |
| 2196 |
INTEGER, |
| 2197 |
snmpFddiATTACHMENTIMaxExpiration |
| 2198 |
FddiTime, |
| 2199 |
snmpFddiATTACHMENTInsertedStatus |
| 2200 |
INTEGER, |
| 2201 |
snmpFddiATTACHMENTInsertPolicy |
| 2202 |
INTEGER |
| 2203 |
} |
| 2204 |
|
| 2205 |
snmpFddiATTACHMENTSMTIndex OBJECT-TYPE |
| 2206 |
SYNTAX INTEGER (1..65535) |
| 2207 |
ACCESS read-only |
| 2208 |
STATUS mandatory |
| 2209 |
DESCRIPTION |
| 2210 |
"The value of the SMT index associated with this |
| 2211 |
ATTACHMENT." |
| 2212 |
::= { snmpFddiATTACHMENTEntry 1 } |
| 2213 |
|
| 2214 |
snmpFddiATTACHMENTIndex OBJECT-TYPE |
| 2215 |
SYNTAX INTEGER (1..65535) |
| 2216 |
ACCESS read-only |
| 2217 |
STATUS mandatory |
| 2218 |
DESCRIPTION |
| 2219 |
"A unique value for each ATTACHMENT on a given |
| 2220 |
SMT. Its value ranges between 1 and the sum of |
| 2221 |
the values of snmpFddiSMTNonMasterCt { |
| 2222 |
snmpFddiSMTEntry 6 } and snmpFddiSMTMasterCt { |
| 2223 |
snmpFddiSMTEntry 7 } on the given SMT. The value |
| 2224 |
for each ATTACHMENT must remain constant at least |
| 2225 |
from one re-initialization of the entity's network |
| 2226 |
management system to the next re-initialization." |
| 2227 |
::= { snmpFddiATTACHMENTEntry 2 } |
| 2228 |
|
| 2229 |
snmpFddiATTACHMENTClass OBJECT-TYPE |
| 2230 |
SYNTAX INTEGER { |
| 2231 |
single-attachment(1), |
| 2232 |
dual-attachment(2), |
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Case [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
concentrator(3) |
| 2242 |
} |
| 2243 |
ACCESS read-only |
| 2244 |
STATUS mandatory |
| 2245 |
DESCRIPTION |
| 2246 |
"The Attachment class. This represents a PORT or |
| 2247 |
a pair of PORTs plus the associated optional |
| 2248 |
optical bypass that are managed as a functional |
| 2249 |
unit. The PORT associations are the following: |
| 2250 |
|
| 2251 |
single-attachment - S PORTs |
| 2252 |
dual-attachment - A/B PORT Pairs |
| 2253 |
concentrator - M PORTs " |
| 2254 |
REFERENCE |
| 2255 |
"ANSI { fddiATTACHMENT 11 }" |
| 2256 |
::= { snmpFddiATTACHMENTEntry 3 } |
| 2257 |
|
| 2258 |
snmpFddiATTACHMENTOpticalBypassPresent OBJECT-TYPE |
| 2259 |
SYNTAX INTEGER { true(1), false(2) } |
| 2260 |
ACCESS read-only |
| 2261 |
STATUS mandatory |
| 2262 |
DESCRIPTION |
| 2263 |
"The value of this value is false for 'single- |
| 2264 |
attachment' and { snmpFddiATTACHMENT 11 }. |
| 2265 |
Correct operation of CMT for single-attachment and |
| 2266 |
concentrator attachments requires that a bypass |
| 2267 |
function must not loopback the network side of the |
| 2268 |
MIC, but only the node side." |
| 2269 |
REFERENCE |
| 2270 |
"ANSI { fddiATTACHMENT 12 }" |
| 2271 |
::= { snmpFddiATTACHMENTEntry 4 } |
| 2272 |
|
| 2273 |
snmpFddiATTACHMENTIMaxExpiration OBJECT-TYPE |
| 2274 |
SYNTAX FddiTime |
| 2275 |
ACCESS read-only |
| 2276 |
STATUS mandatory |
| 2277 |
DESCRIPTION |
| 2278 |
"I_Max (refer to ANSI SMT 9.4.4.2.1). It is |
| 2279 |
recognized that some currently deployed systems do |
| 2280 |
not implement an optical bypass. Systems which do |
| 2281 |
not implement optical bypass should return a value |
| 2282 |
of 0." |
| 2283 |
REFERENCE |
| 2284 |
"ANSI { fddiATTACHMENT 13 }" |
| 2285 |
::= { snmpFddiATTACHMENTEntry 5 } |
| 2286 |
|
| 2287 |
snmpFddiATTACHMENTInsertedStatus OBJECT-TYPE |
| 2288 |
SYNTAX INTEGER { true(1), false(2), unimplemented(3) } |
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Case [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
ACCESS read-only |
| 2298 |
STATUS mandatory |
| 2299 |
DESCRIPTION |
| 2300 |
"Indicates whether the attachment is currently |
| 2301 |
inserted in the node." |
| 2302 |
REFERENCE |
| 2303 |
"ANSI { fddiATTACHMENT 14 }" |
| 2304 |
::= { snmpFddiATTACHMENTEntry 6 } |
| 2305 |
|
| 2306 |
snmpFddiATTACHMENTInsertPolicy OBJECT-TYPE |
| 2307 |
SYNTAX INTEGER { true(1), false(2), unimplemented(3) } |
| 2308 |
ACCESS read-write |
| 2309 |
STATUS mandatory |
| 2310 |
DESCRIPTION |
| 2311 |
"Indicates the Insert Policy for this Attachment. |
| 2312 |
Insert: True (1), Don't Insert: False (2), |
| 2313 |
Unimplemented (3)" |
| 2314 |
REFERENCE |
| 2315 |
"ANSI { fddiATTACHMENT 15 }" |
| 2316 |
::= { snmpFddiATTACHMENTEntry 7 } |
| 2317 |
|
| 2318 |
|
| 2319 |
-- the Chip Set group |
| 2320 |
-- The following object identifiers are allocated for use |
| 2321 |
-- with the snmpFddiMACChipSet and snmpFddiPORTChipSet |
| 2322 |
-- variables. |
| 2323 |
|
| 2324 |
snmpFddiPHYChipSets -- Chips primarily responsible |
| 2325 |
-- for implementing the PHY |
| 2326 |
-- function. |
| 2327 |
OBJECT IDENTIFIER ::= { snmpFddiChipSets 1 } |
| 2328 |
|
| 2329 |
-- None defined at present |
| 2330 |
-- Chipsets may someday be |
| 2331 |
-- defined here |
| 2332 |
|
| 2333 |
|
| 2334 |
snmpFddiMACChipSets -- Chips primarily responsible |
| 2335 |
-- for implementing the |
| 2336 |
-- MAC function. |
| 2337 |
OBJECT IDENTIFIER ::= { snmpFddiChipSets 2 } |
| 2338 |
|
| 2339 |
-- None defined at present |
| 2340 |
-- Chipsets may someday be |
| 2341 |
-- defined here |
| 2342 |
|
| 2343 |
snmpFddiPHYMACChipSets -- Chips which implement both |
| 2344 |
-- the PHY and MAC functions |
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Case [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
OBJECT IDENTIFIER ::= { snmpFddiChipSets 3 } |
| 2354 |
|
| 2355 |
-- None defined at present |
| 2356 |
-- Chipsets may someday be |
| 2357 |
-- defined here |
| 2358 |
|
| 2359 |
END |
| 2360 |
|
| 2361 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span> |
| 2362 |
|
| 2363 |
This document was produced by the IETF FDDI MIB working group: |
| 2364 |
|
| 2365 |
Steve Adams, Digital Equipment Corporation |
| 2366 |
Hossein Alaee, 3Com Corporation |
| 2367 |
Haggar Alsaleh, Bell Northern Research |
| 2368 |
William Anderson, Mitre Corporation |
| 2369 |
Alan Apt, Addison-Wesley |
| 2370 |
Mary Artibee, Silicon Graphics |
| 2371 |
Karen Auerbach, Epilogue Technologies |
| 2372 |
Doug Bagnall, Apollo/Hewlett Packard |
| 2373 |
Chet Birger, Coral Network Corporation |
| 2374 |
Pablo Brenner, Sparta |
| 2375 |
Howard Brown, Cabletron |
| 2376 |
Jack Brown, US Army Computer Engineering Center |
| 2377 |
Eric Brunner |
| 2378 |
Jeff Case, The University of Tennessee |
| 2379 |
Tammy Chan, Fibercom |
| 2380 |
Asheem Chandna, AT&T |
| 2381 |
Cho Y. Chang, Apollo/Hewlett Packard |
| 2382 |
Chris Chiotasso, Fibronics |
| 2383 |
Paul Ciarfella, Digital Equipment Corporation |
| 2384 |
John Cook, Chipcom |
| 2385 |
Don Coolidge, Silicon Graphics |
| 2386 |
Burt Cyr, Unisys |
| 2387 |
James R. Davin, Massachusetts Institute of Technology |
| 2388 |
Nabil Damouny |
| 2389 |
Nadya El-Afandi, Network Systems Corporation |
| 2390 |
Hunaid Engineer, Cray Research |
| 2391 |
Jeff Fitzgerald, Fibercom |
| 2392 |
Richard Fox, Synoptics |
| 2393 |
Stan Froyd, ACC |
| 2394 |
Debbie Futcher, U.S. Naval Surface Warfare Center |
| 2395 |
Joseph Golio, Cray Research |
| 2396 |
Jeremy Greene, Coral |
| 2397 |
Brian D. Handspicker, Digital Equipment Corporation |
| 2398 |
Peter Hayden, Digital Equipment Corporation |
| 2399 |
Scott Hiles, U.S. Naval Surface Warfare Center |
| 2400 |
Greg Jones, Data General |
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Case [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
Satish Joshi, SynOptics Communications |
| 2410 |
Jayant Kadambi, AT&T Bell Labs |
| 2411 |
Joanna Karwowska, Data General |
| 2412 |
Frank Kastenholz, Interlan |
| 2413 |
Jim Kinder, Fibercom |
| 2414 |
Christopher Kolb, PSI |
| 2415 |
Cheryl Krupczak, NCR |
| 2416 |
Peter Lin, Vitalink |
| 2417 |
Then Liu |
| 2418 |
John R. LoVerso, Concurrent Computer Corporation |
| 2419 |
Ron Mackey |
| 2420 |
Gary Malkin, Proteon |
| 2421 |
Bruce McClure, Synernetics |
| 2422 |
Keith McCloghrie, Hughes Lan Systems |
| 2423 |
Donna McMaster, SynOptics |
| 2424 |
John O'Hara, Massachusetts Institute of Technology |
| 2425 |
Dave Perkins, SynOptics Communications |
| 2426 |
James E. Reeves, SynOptics Communications |
| 2427 |
Jim Reinstedler, Ungermann-Bass |
| 2428 |
Radhi Renous, Fibronics |
| 2429 |
Anil Rijsinghani, Digital Equipment Corporation |
| 2430 |
Bob Rolla, Synernetics |
| 2431 |
Nelson Ronkin, Synernetics |
| 2432 |
Marshall T. Rose, Performance Systems International, Inc. |
| 2433 |
Milt Roselinsky, CMC |
| 2434 |
Jon Saperia, Digital Equipment Corporation |
| 2435 |
Greg Satz, cisco Systems |
| 2436 |
Steven Senum, Network Systems Corporation |
| 2437 |
Jim Sheridan, IBM Corporation |
| 2438 |
Jeffrey Schiller, MIT |
| 2439 |
Dror Shindelman, Sparta |
| 2440 |
Mark Sleeper, Sparta |
| 2441 |
Craig Smelser, Digital Equipment Corporation |
| 2442 |
Lou Steinberg, IBM Corporation |
| 2443 |
Mary Jane Strohl, Apollo/Hewlett Packard |
| 2444 |
Sally Tarquinio, Mitre Corporation |
| 2445 |
Kaj Tesink, Bellcore |
| 2446 |
Ian Thomas, Chipcom |
| 2447 |
Dean Throop, Data General |
| 2448 |
Bill Townsend, Xylogics |
| 2449 |
Ahmet H. Tuncay, SynOptics Communications |
| 2450 |
Mike Turico, Motorola |
| 2451 |
Chris VandenBerg, ACC |
| 2452 |
Sudhanshu Verma, Hewlett Packard |
| 2453 |
Joe Vermeulen, UNISYS |
| 2454 |
David Waiteman, BBN |
| 2455 |
Bert Williams, Synernetics |
| 2456 |
Mark Wood, AT&T Computer Systems |
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Case [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
Y. C. Yang |
| 2466 |
Denis Yaro, Sun Microsystems |
| 2467 |
Jeff Young, Cray Research |
| 2468 |
|
| 2469 |
The editor gratefully acknowledges the contributions of the editor of |
| 2470 |
the ANSI X3T9.5 SMT document, Mary Jane Strohl of Hewlett |
| 2471 |
Packard/Apollo, whose provision of that document in machine readable |
| 2472 |
form saved much typing and avoided many data entry errors. |
| 2473 |
|
| 2474 |
The author gratefully acknowledges the labors of Dr. Marshall T. Rose |
| 2475 |
in assisting with converting this document to the new concise MIB |
| 2476 |
format. |
| 2477 |
|
| 2478 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 2479 |
|
| 2480 |
[<a id="ref-1">1</a>] Rose M., and K. McCloghrie, "Structure and Identification of |
| 2481 |
Management Information for TCP/IP-based internets", <a href="./rfc1155">RFC 1155</a>, |
| 2482 |
Performance Systems International, Hughes LAN Systems, May 1990. |
| 2483 |
|
| 2484 |
[<a id="ref-2">2</a>] McCloghrie K., and M. Rose, "Management Information Base for |
| 2485 |
Network Management of TCP/IP-based internets", <a href="./rfc1156">RFC 1156</a>, Hughes |
| 2486 |
LAN Systems, Performance Systems International, May 1990. |
| 2487 |
|
| 2488 |
[<a id="ref-3">3</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple |
| 2489 |
Network Management Protocol", <a href="./rfc1157">RFC 1157</a>, SNMP Research, |
| 2490 |
Performance Systems International, Performance Systems |
| 2491 |
International, MIT Laboratory for Computer Science, May 1990. |
| 2492 |
|
| 2493 |
[<a id="ref-4">4</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base |
| 2494 |
for Network Management of TCP/IP-based internets", <a href="./rfc1213">RFC 1213</a>, |
| 2495 |
Performance Systems International, March 1991. |
| 2496 |
|
| 2497 |
[<a id="ref-5">5</a>] Information processing systems - Open Systems Interconnection - |
| 2498 |
Specification of Abstract Syntax Notation One (ASN.1), |
| 2499 |
International Organization for Standardization, International |
| 2500 |
Standard 8824, December 1987. |
| 2501 |
|
| 2502 |
[<a id="ref-6">6</a>] Information processing systems - Open Systems Interconnection - |
| 2503 |
Specification of Basic Encoding Rules for Abstract Notation One |
| 2504 |
(ASN.1), International Organization for Standardization, |
| 2505 |
International Standard 8825, December 1987. |
| 2506 |
|
| 2507 |
[<a id="ref-7">7</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", |
| 2508 |
<a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN Systems, |
| 2509 |
March 1991. |
| 2510 |
|
| 2511 |
[<a id="ref-8">8</a>] American National Standards Institute, "FDDI Station Management |
| 2512 |
(SMT)", Preliminary Draft Proposed American National Standard, |
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
<span class="grey">Case [Page 45]</span></pre> |
| 2517 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2518 |
<span class="grey"><a href="./rfc1285">RFC 1285</a> FDDI MIB January 1992</span> |
| 2519 |
|
| 2520 |
|
| 2521 |
American National Standards Institute, X3T9/90-X3T9.5/84-49 REV |
| 2522 |
6.2, May 18, 1990. |
| 2523 |
|
| 2524 |
Security Considerations |
| 2525 |
|
| 2526 |
Security issues are not discussed in this memo. |
| 2527 |
|
| 2528 |
Author's Address |
| 2529 |
|
| 2530 |
Jeffrey D. Case |
| 2531 |
SNMP Research, Incorporated |
| 2532 |
3001 Kimberlin Heights Road |
| 2533 |
Knoxville, Tennessee 37920 |
| 2534 |
|
| 2535 |
Phone: (615) 573-1434 |
| 2536 |
|
| 2537 |
EMail: [email protected] |
| 2538 |
|
| 2539 |
|
| 2540 |
|
| 2541 |
|
| 2542 |
|
| 2543 |
|
| 2544 |
|
| 2545 |
|
| 2546 |
|
| 2547 |
|
| 2548 |
|
| 2549 |
|
| 2550 |
|
| 2551 |
|
| 2552 |
|
| 2553 |
|
| 2554 |
|
| 2555 |
|
| 2556 |
|
| 2557 |
|
| 2558 |
|
| 2559 |
|
| 2560 |
|
| 2561 |
|
| 2562 |
|
| 2563 |
|
| 2564 |
|
| 2565 |
|
| 2566 |
|
| 2567 |
|
| 2568 |
|
| 2569 |
|
| 2570 |
|
| 2571 |
|
| 2572 |
Case [Page 46] |
| 2573 |
</pre> |