Difference between revisions of "RFC1285"
From RFC-Wiki
imported>Admin (Created page with " Network Working Group J. CaseRequest for Comments: 1285 SNMP Research, Incorporated ...") |
|||
| Line 4: | Line 4: | ||
| − | + | Network Working Group J. Case | |
| − | Network Working Group J. | + | Request for Comments: 1285 SNMP Research, Incorporated |
| + | January 1992 | ||
FDDI Management Information Base | FDDI Management Information Base | ||
Status of this Memo | Status of this Memo | ||
| − | This memo is an extension to the SNMP MIB. This RFC specifies an | + | This memo is an extension to the SNMP MIB. This RFC specifies an IAB |
| − | == Abstract == | + | standards track protocol for the Internet community, and requests |
| − | + | discussion and suggestions for improvements. Please refer to the | |
| + | current edition of the "IAB Official Protocol Standards" for the | ||
| + | standardization state and status of this protocol. Distribution of | ||
| + | this memo is unlimited. | ||
| + | Table of Contents | ||
| + | 1. Abstract .............................................. 1 | ||
| + | 2. The Network Management Framework....................... 1 | ||
| + | 3. Objects ............................................... 2 | ||
| + | 3.1 Format of Definitions ................................ 2 | ||
| + | 4. Overview .............................................. 3 | ||
| + | 4.1 Textual Conventions .................................. 3 | ||
| + | 5. Object Definitions .................................... 4 | ||
| + | 5.1 The SMT Group ........................................ 5 | ||
| + | 5.2 The MAC Group ........................................ 15 | ||
| + | 5.3 The PATH Group ....................................... 27 | ||
| + | 5.4 The PORT Group ....................................... 27 | ||
| + | 5.5 The ATTACHMENT Group ................................. 38 | ||
| + | 5.6 The Chip Set Group ................................... 42 | ||
| + | 6. Acknowledgements ...................................... 43 | ||
| + | 7. References ............................................ 45 | ||
| + | Security Considerations................................... 46 | ||
| + | Author's Address.......................................... 46 | ||
| + | == Abstract == | ||
This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | ||
for use with network management protocols in TCP/IP-based internets. | for use with network management protocols in TCP/IP-based internets. | ||
In particular, it defines objects for managing devices which | In particular, it defines objects for managing devices which | ||
implement the FDDI. | implement the FDDI. | ||
| + | == The Network Management Framework == | ||
| + | The Internet-standard Network Management Framework consists of three | ||
| + | components. They are: | ||
| − | |||
| − | |||
| − | |||
| Line 27: | Line 50: | ||
| − | + | RFC 1155 which defines the SMI, the mechanisms used for describing | |
| − | and naming objects for the purpose of management. | + | and naming objects for the purpose of management. RFC 1212 |
defines a more concise description mechanism, which is wholly | defines a more concise description mechanism, which is wholly | ||
consistent with the SMI. | consistent with the SMI. | ||
| − | + | RFC 1156 which defines MIB-I, the core set of managed objects for | |
| − | + | the Internet suite of protocols. RFC 1213, defines MIB-II, an | |
| − | the Internet suite of protocols. | ||
evolution of MIB-I based on implementation experience and new | evolution of MIB-I based on implementation experience and new | ||
operational requirements. | operational requirements. | ||
| − | + | RFC 1157 which defines the SNMP, the protocol used for network | |
| − | |||
access to managed objects. | access to managed objects. | ||
| − | |||
The Framework permits new objects to be defined for the purpose of | The Framework permits new objects to be defined for the purpose of | ||
experimentation and evaluation. | experimentation and evaluation. | ||
| − | + | == Objects == | |
| − | == Objects == | ||
| − | |||
Managed objects are accessed via a virtual information store, termed | Managed objects are accessed via a virtual information store, termed | ||
the Management Information Base or MIB. Objects in the MIB are | the Management Information Base or MIB. Objects in the MIB are | ||
| Line 55: | Line 73: | ||
convenience, we often use a textual string, termed the OBJECT | convenience, we often use a textual string, termed the OBJECT | ||
DESCRIPTOR, to also refer to the object type. | DESCRIPTOR, to also refer to the object type. | ||
| − | |||
The syntax of an object type defines the abstract data structure | The syntax of an object type defines the abstract data structure | ||
corresponding to that object type. The ASN.1 language is used for | corresponding to that object type. The ASN.1 language is used for | ||
| Line 61: | Line 78: | ||
constructs which may be used. These restrictions are explicitly made | constructs which may be used. These restrictions are explicitly made | ||
for simplicity. | for simplicity. | ||
| − | |||
The encoding of an object type is simply how that object type is | The encoding of an object type is simply how that object type is | ||
represented using the object type's syntax. Implicitly tied to the | represented using the object type's syntax. Implicitly tied to the | ||
notion of an object type's syntax and encoding is how the object type | notion of an object type's syntax and encoding is how the object type | ||
is represented when being transmitted on the network. | is represented when being transmitted on the network. | ||
| − | |||
The SMI specifies the use of the basic encoding rules of ASN.1 [6], | The SMI specifies the use of the basic encoding rules of ASN.1 [6], | ||
subject to the additional requirements imposed by the SNMP. | subject to the additional requirements imposed by the SNMP. | ||
| − | + | 3.1. Format of Definitions | |
| − | |||
| − | |||
Section 5 contains contains the specification of all object types | Section 5 contains contains the specification of all object types | ||
contained in this MIB module. The object types are defined using the | contained in this MIB module. The object types are defined using the | ||
| Line 80: | Line 93: | ||
| − | |||
| − | |||
| + | specified in [7]. | ||
| + | == Overview == | ||
This document defines the managed objects for FDDI devices which are | This document defines the managed objects for FDDI devices which are | ||
to be accessible via the Simple Network Management Protocol (SNMP). | to be accessible via the Simple Network Management Protocol (SNMP). | ||
At present, this applies to these values of the ifType variable in | At present, this applies to these values of the ifType variable in | ||
the Internet-standard MIB: | the Internet-standard MIB: | ||
| − | |||
fddi(15) | fddi(15) | ||
| − | |||
For these interfaces, the value of the ifSpecific variable in the | For these interfaces, the value of the ifSpecific variable in the | ||
MIB-II [4] has the OBJECT IDENTIFIER value: | MIB-II [4] has the OBJECT IDENTIFIER value: | ||
| − | |||
fddi OBJECT IDENTIFIER ::= { transmission 15 } | fddi OBJECT IDENTIFIER ::= { transmission 15 } | ||
| − | |||
The definitions of the objects presented here draws heavily from | The definitions of the objects presented here draws heavily from | ||
related work in the ANSI X3T9.5 committee and the SMT subcommittee of | related work in the ANSI X3T9.5 committee and the SMT subcommittee of | ||
| Line 107: | Line 116: | ||
remapping bit strings to octet strings, and the like. In addition, | remapping bit strings to octet strings, and the like. In addition, | ||
the naming of the objects was changed to achieve compatibility. | the naming of the objects was changed to achieve compatibility. | ||
| − | |||
These minimal syntactic changes with no semantic changes should allow | These minimal syntactic changes with no semantic changes should allow | ||
implementations of SNMP manageable FDDI systems to share | implementations of SNMP manageable FDDI systems to share | ||
| Line 114: | Line 122: | ||
information conveyed by managed objects from one network management | information conveyed by managed objects from one network management | ||
scheme to another is eased by these shared definitions. | scheme to another is eased by these shared definitions. | ||
| − | |||
Only the essential variables, as indicated by their mandatory status | Only the essential variables, as indicated by their mandatory status | ||
in the ANSI specification were retained in this document. The | in the ANSI specification were retained in this document. The | ||
importance of variables which have an optional status in the ANSI | importance of variables which have an optional status in the ANSI | ||
specification were perceived as being less widely accepted. | specification were perceived as being less widely accepted. | ||
| − | + | 4.1. Textual Conventions | |
| − | |||
| − | |||
Several new datatypes are introduced as a textual convention in this | Several new datatypes are introduced as a textual convention in this | ||
MIB document. These textual conventions enhance the readability of | MIB document. These textual conventions enhance the readability of | ||
| Line 128: | Line 133: | ||
conventions has no effect on either the syntax nor the semantics of | conventions has no effect on either the syntax nor the semantics of | ||
any managed objects. The use of these is merely an artifact of the | any managed objects. The use of these is merely an artifact of the | ||
| + | |||
| + | |||
| Line 139: | Line 146: | ||
merely for the convenience of readers and writers in pursuit of the | merely for the convenience of readers and writers in pursuit of the | ||
elusive goal of clear, concise, and unambiguous MIB documents. | elusive goal of clear, concise, and unambiguous MIB documents. | ||
| − | + | == Object Definitions == | |
| − | == Object Definitions == | ||
| − | |||
RFC1285-MIB DEFINITIONS ::= BEGIN | RFC1285-MIB DEFINITIONS ::= BEGIN | ||
| − | |||
IMPORTS | IMPORTS | ||
Counter | Counter | ||
| Line 151: | Line 155: | ||
OBJECT-TYPE | OBJECT-TYPE | ||
FROM RFC-1212; | FROM RFC-1212; | ||
| − | |||
-- This MIB module uses the extended OBJECT-TYPE macro as | -- This MIB module uses the extended OBJECT-TYPE macro as | ||
-- defined in [7]. | -- defined in [7]. | ||
| − | |||
-- this is the FDDI MIB module | -- this is the FDDI MIB module | ||
| − | |||
fddi OBJECT IDENTIFIER ::= { transmission 15 } | fddi OBJECT IDENTIFIER ::= { transmission 15 } | ||
| − | |||
-- textual conventions | -- textual conventions | ||
| − | |||
FddiTime ::= INTEGER (0..2147483647) | FddiTime ::= INTEGER (0..2147483647) | ||
-- This data type specifies octet units of 80 nanoseconds as | -- This data type specifies octet units of 80 nanoseconds as | ||
| Line 168: | Line 167: | ||
-- Synchronous Bandwidth values. The encoding is normal | -- Synchronous Bandwidth values. The encoding is normal | ||
-- integer representation (not twos complement). | -- integer representation (not twos complement). | ||
| − | |||
FddiResourceId ::= INTEGER (0..65535) | FddiResourceId ::= INTEGER (0..65535) | ||
-- This data type is used to refer to an instance of a MAC, | -- This data type is used to refer to an instance of a MAC, | ||
-- PORT, PATH, or ATTACHMENT Resource ID. Indexing begins | -- PORT, PATH, or ATTACHMENT Resource ID. Indexing begins | ||
-- at 1. Zero is used to indicate the absence of a resource. | -- at 1. Zero is used to indicate the absence of a resource. | ||
| − | |||
FddiSMTStationIdType ::= OCTET STRING (SIZE (8)) | FddiSMTStationIdType ::= OCTET STRING (SIZE (8)) | ||
-- The unique identifier for the FDDI station. This is a | -- The unique identifier for the FDDI station. This is a | ||
| Line 181: | Line 178: | ||
-- assigned address. The high order two bits of the IEEE | -- assigned address. The high order two bits of the IEEE | ||
-- address, the group address bit and the administration bit | -- address, the group address bit and the administration bit | ||
| + | |||
| + | |||
| Line 198: | Line 197: | ||
-- addresses in the ANSI FDDI standard SMT frames are | -- addresses in the ANSI FDDI standard SMT frames are | ||
-- represented in FDDI MAC order. | -- represented in FDDI MAC order. | ||
| − | |||
FddiMACLongAddressType ::= OCTET STRING (SIZE (6)) | FddiMACLongAddressType ::= OCTET STRING (SIZE (6)) | ||
-- The representation of long MAC addresses as management | -- The representation of long MAC addresses as management | ||
| Line 209: | Line 207: | ||
-- and so on. Note that the addresses in the SMT frames are | -- and so on. Note that the addresses in the SMT frames are | ||
-- represented in FDDI MAC order. | -- represented in FDDI MAC order. | ||
| − | |||
-- groups in the FDDI MIB module | -- groups in the FDDI MIB module | ||
| − | |||
snmpFddiSMT OBJECT IDENTIFIER ::= { fddi 1 } | snmpFddiSMT OBJECT IDENTIFIER ::= { fddi 1 } | ||
| − | |||
snmpFddiMAC OBJECT IDENTIFIER ::= { fddi 2 } | snmpFddiMAC OBJECT IDENTIFIER ::= { fddi 2 } | ||
| − | |||
snmpFddiPATH OBJECT IDENTIFIER ::= { fddi 3 } | snmpFddiPATH OBJECT IDENTIFIER ::= { fddi 3 } | ||
| − | |||
snmpFddiPORT OBJECT IDENTIFIER ::= { fddi 4 } | snmpFddiPORT OBJECT IDENTIFIER ::= { fddi 4 } | ||
| − | |||
snmpFddiATTACHMENT OBJECT IDENTIFIER ::= { fddi 5 } | snmpFddiATTACHMENT OBJECT IDENTIFIER ::= { fddi 5 } | ||
| − | |||
snmpFddiChipSets OBJECT IDENTIFIER ::= { fddi 6 } | snmpFddiChipSets OBJECT IDENTIFIER ::= { fddi 6 } | ||
| − | |||
-- the SMT group | -- the SMT group | ||
-- Implementation of the SMT group is mandatory for all | -- Implementation of the SMT group is mandatory for all | ||
-- systems which implement manageable FDDI subsystems. | -- systems which implement manageable FDDI subsystems. | ||
| − | |||
snmpFddiSMTNumber OBJECT-TYPE | snmpFddiSMTNumber OBJECT-TYPE | ||
SYNTAX INTEGER (0..65535) | SYNTAX INTEGER (0..65535) | ||
| Line 234: | Line 223: | ||
STATUS mandatory | STATUS mandatory | ||
DESCRIPTION | DESCRIPTION | ||
| + | |||
| + | |||
| Line 246: | Line 237: | ||
system to the next re-initialization." | system to the next re-initialization." | ||
::= { snmpFddiSMT 1 } | ::= { snmpFddiSMT 1 } | ||
| − | |||
-- the SMT table | -- the SMT table | ||
| − | |||
snmpFddiSMTTable OBJECT-TYPE | snmpFddiSMTTable OBJECT-TYPE | ||
SYNTAX SEQUENCE OF SnmpFddiSMTEntry | SYNTAX SEQUENCE OF SnmpFddiSMTEntry | ||
| Line 258: | Line 247: | ||
given by the value of snmpFddiSMTNumber." | given by the value of snmpFddiSMTNumber." | ||
::= { snmpFddiSMT 2 } | ::= { snmpFddiSMT 2 } | ||
| − | |||
snmpFddiSMTEntry OBJECT-TYPE | snmpFddiSMTEntry OBJECT-TYPE | ||
SYNTAX SnmpFddiSMTEntry | SYNTAX SnmpFddiSMTEntry | ||
| Line 268: | Line 256: | ||
INDEX { snmpFddiSMTIndex } | INDEX { snmpFddiSMTIndex } | ||
::= { snmpFddiSMTTable 1 } | ::= { snmpFddiSMTTable 1 } | ||
| − | |||
SnmpFddiSMTEntry ::= | SnmpFddiSMTEntry ::= | ||
SEQUENCE { | SEQUENCE { | ||
| Line 287: | Line 274: | ||
snmpFddiSMTMasterCt | snmpFddiSMTMasterCt | ||
INTEGER, | INTEGER, | ||
| + | |||
| + | |||
| Line 315: | Line 304: | ||
INTEGER | INTEGER | ||
} | } | ||
| − | |||
snmpFddiSMTIndex OBJECT-TYPE | snmpFddiSMTIndex OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 327: | Line 315: | ||
management system to the next re-initialization." | management system to the next re-initialization." | ||
::= { snmpFddiSMTEntry 1 } | ::= { snmpFddiSMTEntry 1 } | ||
| − | |||
snmpFddiSMTStationId OBJECT-TYPE | snmpFddiSMTStationId OBJECT-TYPE | ||
SYNTAX FddiSMTStationIdType -- OCTET STRING (SIZE (8)) | SYNTAX FddiSMTStationIdType -- OCTET STRING (SIZE (8)) | ||
| Line 337: | Line 324: | ||
"ANSI { fddiSMT 11 }" | "ANSI { fddiSMT 11 }" | ||
::= { snmpFddiSMTEntry 2 } | ::= { snmpFddiSMTEntry 2 } | ||
| + | |||
| + | |||
| Line 355: | Line 344: | ||
"ANSI { fddiSMT 13 }" | "ANSI { fddiSMT 13 }" | ||
::= { snmpFddiSMTEntry 3 } | ::= { snmpFddiSMTEntry 3 } | ||
| − | |||
snmpFddiSMTHiVersionId OBJECT-TYPE | snmpFddiSMTHiVersionId OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 366: | Line 354: | ||
"ANSI { fddiSMT 14 }" | "ANSI { fddiSMT 14 }" | ||
::= { snmpFddiSMTEntry 4 } | ::= { snmpFddiSMTEntry 4 } | ||
| − | |||
snmpFddiSMTLoVersionId OBJECT-TYPE | snmpFddiSMTLoVersionId OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 377: | Line 364: | ||
"ANSI { fddiSMT 15 }" | "ANSI { fddiSMT 15 }" | ||
::= { snmpFddiSMTEntry 5 } | ::= { snmpFddiSMTEntry 5 } | ||
| − | |||
snmpFddiSMTMACCt OBJECT-TYPE | snmpFddiSMTMACCt OBJECT-TYPE | ||
SYNTAX INTEGER (0..255) | SYNTAX INTEGER (0..255) | ||
| Line 388: | Line 374: | ||
"ANSI { fddiSMT 21 }" | "ANSI { fddiSMT 21 }" | ||
::= { snmpFddiSMTEntry 6 } | ::= { snmpFddiSMTEntry 6 } | ||
| − | |||
snmpFddiSMTNonMasterCt OBJECT-TYPE | snmpFddiSMTNonMasterCt OBJECT-TYPE | ||
SYNTAX INTEGER (0..2) | SYNTAX INTEGER (0..2) | ||
ACCESS read-only | ACCESS read-only | ||
STATUS mandatory | STATUS mandatory | ||
| + | |||
| + | |||
| Line 404: | Line 391: | ||
"ANSI { fddiSMT 22 }" | "ANSI { fddiSMT 22 }" | ||
::= { snmpFddiSMTEntry 7 } | ::= { snmpFddiSMTEntry 7 } | ||
| − | |||
snmpFddiSMTMasterCt OBJECT-TYPE | snmpFddiSMTMasterCt OBJECT-TYPE | ||
SYNTAX INTEGER (0..255) | SYNTAX INTEGER (0..255) | ||
| Line 415: | Line 401: | ||
"ANSI { fddiSMT 23 }" | "ANSI { fddiSMT 23 }" | ||
::= { snmpFddiSMTEntry 8 } | ::= { snmpFddiSMTEntry 8 } | ||
| − | |||
snmpFddiSMTPathsAvailable OBJECT-TYPE | snmpFddiSMTPathsAvailable OBJECT-TYPE | ||
SYNTAX INTEGER (0..7) | SYNTAX INTEGER (0..7) | ||
| Line 423: | Line 408: | ||
"A value that indicates the PATH types available | "A value that indicates the PATH types available | ||
in the station. | in the station. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each type of PATH that | the value zero, then for each type of PATH that | ||
| Line 429: | Line 413: | ||
added to the sum. The powers are according to the | added to the sum. The powers are according to the | ||
following table: | following table: | ||
| − | |||
Path Power | Path Power | ||
Primary 0 | Primary 0 | ||
Secondary 1 | Secondary 1 | ||
Local 2 | Local 2 | ||
| − | |||
For example, a station having Primary and Local | For example, a station having Primary and Local | ||
PATHs available would have a value of 5 (2**0 + | PATHs available would have a value of 5 (2**0 + | ||
| Line 441: | Line 423: | ||
"ANSI { fddiSMT 24 }" | "ANSI { fddiSMT 24 }" | ||
::= { snmpFddiSMTEntry 9 } | ::= { snmpFddiSMTEntry 9 } | ||
| − | |||
snmpFddiSMTConfigCapabilities OBJECT-TYPE | snmpFddiSMTConfigCapabilities OBJECT-TYPE | ||
SYNTAX INTEGER (0..3) | SYNTAX INTEGER (0..3) | ||
ACCESS read-only | ACCESS read-only | ||
STATUS mandatory | STATUS mandatory | ||
| + | |||
| + | |||
| Line 458: | Line 441: | ||
'CF-Wrap-AB' is present, this indicates that the | 'CF-Wrap-AB' is present, this indicates that the | ||
WRAP_AB state is forced. | WRAP_AB state is forced. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each of the configuration | the value zero, then for each of the configuration | ||
| Line 464: | Line 446: | ||
to a power is added to the sum. The powers are | to a power is added to the sum. The powers are | ||
according to the following table: | according to the following table: | ||
| − | |||
Policy Power | Policy Power | ||
holdAvailable 0 | holdAvailable 0 | ||
| Line 471: | Line 452: | ||
"ANSI { fddiSMT 25 }" | "ANSI { fddiSMT 25 }" | ||
::= { snmpFddiSMTEntry 10 } | ::= { snmpFddiSMTEntry 10 } | ||
| − | |||
snmpFddiSMTConfigPolicy OBJECT-TYPE | snmpFddiSMTConfigPolicy OBJECT-TYPE | ||
SYNTAX INTEGER (0..3) | SYNTAX INTEGER (0..3) | ||
| Line 483: | Line 463: | ||
if the Hold function is supported. The 'CF-Wrap- | if the Hold function is supported. The 'CF-Wrap- | ||
AB' policy refers to the CF_Wrap_AB flag. | AB' policy refers to the CF_Wrap_AB flag. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each of the configuration | the value zero, then for each of the configuration | ||
| Line 489: | Line 468: | ||
to a power is added to the sum. The powers are | to a power is added to the sum. The powers are | ||
according to the following table: | according to the following table: | ||
| − | |||
Policy Power | Policy Power | ||
configurationHold 0 | configurationHold 0 | ||
| Line 496: | Line 474: | ||
"ANSI { fddiSMT 26 }" | "ANSI { fddiSMT 26 }" | ||
::= { snmpFddiSMTEntry 11 } | ::= { snmpFddiSMTEntry 11 } | ||
| + | |||
| + | |||
| Line 520: | Line 500: | ||
T-Val(3) in the PC-Signaling sequence (refer to | T-Val(3) in the PC-Signaling sequence (refer to | ||
ANSI Section 9.6.3). | ANSI Section 9.6.3). | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each of the connection | the value zero, then for each of the connection | ||
| Line 526: | Line 505: | ||
to a power is added to the sum. The powers are | to a power is added to the sum. The powers are | ||
according to the following table: | according to the following table: | ||
| − | |||
Policy Power | Policy Power | ||
rejectA-A 0 | rejectA-A 0 | ||
| Line 544: | Line 522: | ||
rejectM-S 14 | rejectM-S 14 | ||
rejectM-M 15 | rejectM-M 15 | ||
| − | |||
Implementors should note that the polarity of | Implementors should note that the polarity of | ||
these bits is different in different places in an | these bits is different in different places in an | ||
| Line 552: | Line 529: | ||
"ANSI { fddiSMT 27 }" | "ANSI { fddiSMT 27 }" | ||
::= { snmpFddiSMTEntry 12 } | ::= { snmpFddiSMTEntry 12 } | ||
| + | |||
| + | |||
| Line 568: | Line 547: | ||
"ANSI { fddiSMT 29 }" | "ANSI { fddiSMT 29 }" | ||
::= { snmpFddiSMTEntry 13 } | ::= { snmpFddiSMTEntry 13 } | ||
| − | |||
snmpFddiSMTStatusReporting OBJECT-TYPE | snmpFddiSMTStatusReporting OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
| Line 581: | Line 559: | ||
"ANSI { fddiSMT 30 }" | "ANSI { fddiSMT 30 }" | ||
::= { snmpFddiSMTEntry 14 } | ::= { snmpFddiSMTEntry 14 } | ||
| − | |||
snmpFddiSMTECMState OBJECT-TYPE | snmpFddiSMTECMState OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 601: | Line 578: | ||
"ANSI { fddiSMT 41 }" | "ANSI { fddiSMT 41 }" | ||
::= { snmpFddiSMTEntry 15 } | ::= { snmpFddiSMTEntry 15 } | ||
| − | |||
snmpFddiSMTCFState OBJECT-TYPE | snmpFddiSMTCFState OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
cf0(1), -- Isolated | cf0(1), -- Isolated | ||
| + | |||
| + | |||
| Line 624: | Line 602: | ||
"ANSI { fddiSMT 42 }" | "ANSI { fddiSMT 42 }" | ||
::= { snmpFddiSMTEntry 16 } | ::= { snmpFddiSMTEntry 16 } | ||
| − | |||
snmpFddiSMTHoldState OBJECT-TYPE | snmpFddiSMTHoldState OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 648: | Line 625: | ||
"ANSI { fddiSMT 43 }" | "ANSI { fddiSMT 43 }" | ||
::= { snmpFddiSMTEntry 17 } | ::= { snmpFddiSMTEntry 17 } | ||
| − | |||
snmpFddiSMTRemoteDisconnectFlag OBJECT-TYPE | snmpFddiSMTRemoteDisconnectFlag OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
| Line 658: | Line 634: | ||
a Connect Action (SM_CM_CONNECT.request (Connect)) | a Connect Action (SM_CM_CONNECT.request (Connect)) | ||
to rejoin and clear the flag (refer to ANSI | to rejoin and clear the flag (refer to ANSI | ||
| + | |||
| + | |||
| Line 667: | Line 645: | ||
"ANSI { fddiSMT 44 }" | "ANSI { fddiSMT 44 }" | ||
::= { snmpFddiSMTEntry 18 } | ::= { snmpFddiSMTEntry 18 } | ||
| − | |||
snmpFddiSMTStationAction OBJECT-TYPE | snmpFddiSMTStationAction OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 682: | Line 659: | ||
other(1). The behavior of setting this variable | other(1). The behavior of setting this variable | ||
to each of the acceptable values is as follows: | to each of the acceptable values is as follows: | ||
| − | |||
Other: Results in a badValue error. | Other: Results in a badValue error. | ||
| − | |||
Connect: Generates an | Connect: Generates an | ||
SM_CM_Connect.request(connect) signal to CMT | SM_CM_Connect.request(connect) signal to CMT | ||
| Line 692: | Line 667: | ||
setting of this variable to 1. See ANSI Ref | setting of this variable to 1. See ANSI Ref | ||
9.3.1.1. | 9.3.1.1. | ||
| − | |||
Disconnect: Generates an | Disconnect: Generates an | ||
SM_CM_Connect.request(disconnect) signal to ECM | SM_CM_Connect.request(disconnect) signal to ECM | ||
and sets the fddiSMTRemoteDisconnectFlag. See | and sets the fddiSMTRemoteDisconnectFlag. See | ||
ANSI Ref 9.3.1.1. | ANSI Ref 9.3.1.1. | ||
| − | |||
Path-Test: Initiates a station path test. | Path-Test: Initiates a station path test. | ||
The Path_Test variable (See ANSI Ref. 9.4.1) is | The Path_Test variable (See ANSI Ref. 9.4.1) is | ||
set to Testing. The results of this action are | set to Testing. The results of this action are | ||
not specified in this standard. | not specified in this standard. | ||
| − | |||
Self-Test: Initiates a station self test. | Self-Test: Initiates a station self test. | ||
The results of this action are not specified in | The results of this action are not specified in | ||
this standard. | this standard. | ||
| − | |||
Attempts to set this object to all other values | Attempts to set this object to all other values | ||
results in a badValue error. Agents may elect to | results in a badValue error. Agents may elect to | ||
return a badValue error on attempts to set this | return a badValue error on attempts to set this | ||
variable to path-Test(4) or self-Test(5)." | variable to path-Test(4) or self-Test(5)." | ||
| + | |||
| + | |||
| Line 719: | Line 692: | ||
"ANSI { fddiSMT 60 }" | "ANSI { fddiSMT 60 }" | ||
::= { snmpFddiSMTEntry 19 } | ::= { snmpFddiSMTEntry 19 } | ||
| − | |||
-- the MAC group | -- the MAC group | ||
-- Implementation of the MAC Group is mandatory for all | -- Implementation of the MAC Group is mandatory for all | ||
-- systems which implement manageable FDDI subsystems. | -- systems which implement manageable FDDI subsystems. | ||
| − | |||
snmpFddiMACNumber OBJECT-TYPE | snmpFddiMACNumber OBJECT-TYPE | ||
SYNTAX INTEGER (0..65535) | SYNTAX INTEGER (0..65535) | ||
| Line 737: | Line 708: | ||
re-initialization." | re-initialization." | ||
::= { snmpFddiMAC 1 } | ::= { snmpFddiMAC 1 } | ||
| − | |||
-- the MAC table | -- the MAC table | ||
| − | |||
snmpFddiMACTable OBJECT-TYPE | snmpFddiMACTable OBJECT-TYPE | ||
SYNTAX SEQUENCE OF SnmpFddiMACEntry | SYNTAX SEQUENCE OF SnmpFddiMACEntry | ||
| Line 749: | Line 718: | ||
given by the value of snmpFddiMACNumber." | given by the value of snmpFddiMACNumber." | ||
::= { snmpFddiMAC 2 } | ::= { snmpFddiMAC 2 } | ||
| − | |||
snmpFddiMACEntry OBJECT-TYPE | snmpFddiMACEntry OBJECT-TYPE | ||
SYNTAX SnmpFddiMACEntry | SYNTAX SnmpFddiMACEntry | ||
| Line 759: | Line 727: | ||
INDEX { snmpFddiMACSMTIndex, snmpFddiMACIndex } | INDEX { snmpFddiMACSMTIndex, snmpFddiMACIndex } | ||
::= { snmpFddiMACTable 1 } | ::= { snmpFddiMACTable 1 } | ||
| − | |||
SnmpFddiMACEntry ::= | SnmpFddiMACEntry ::= | ||
SEQUENCE { | SEQUENCE { | ||
snmpFddiMACSMTIndex | snmpFddiMACSMTIndex | ||
INTEGER, | INTEGER, | ||
| + | |||
| + | |||
| Line 817: | Line 786: | ||
snmpFddiMACRMTState | snmpFddiMACRMTState | ||
INTEGER, | INTEGER, | ||
| + | |||
| + | |||
| Line 833: | Line 804: | ||
INTEGER | INTEGER | ||
} | } | ||
| − | |||
snmpFddiMACSMTIndex OBJECT-TYPE | snmpFddiMACSMTIndex OBJECT-TYPE | ||
| Line 843: | Line 813: | ||
MAC." | MAC." | ||
::= { snmpFddiMACEntry 1 } | ::= { snmpFddiMACEntry 1 } | ||
| − | |||
snmpFddiMACIndex OBJECT-TYPE | snmpFddiMACIndex OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 861: | Line 830: | ||
re-initialization." | re-initialization." | ||
::= { snmpFddiMACEntry 2 } | ::= { snmpFddiMACEntry 2 } | ||
| − | |||
snmpFddiMACFrameStatusCapabilities OBJECT-TYPE | snmpFddiMACFrameStatusCapabilities OBJECT-TYPE | ||
SYNTAX INTEGER (0..1799) | SYNTAX INTEGER (0..1799) | ||
| Line 870: | Line 838: | ||
station capabilities for operating in a bridged | station capabilities for operating in a bridged | ||
FDDI network. | FDDI network. | ||
| + | |||
| + | |||
| Line 879: | Line 849: | ||
2 raised to a power is added to the sum. The | 2 raised to a power is added to the sum. The | ||
powers are according to the following table: | powers are according to the following table: | ||
| − | |||
Capability Power | Capability Power | ||
| Line 885: | Line 854: | ||
-- MAC repeats A/C indicators as received on | -- MAC repeats A/C indicators as received on | ||
-- copying with the intent to forward. | -- copying with the intent to forward. | ||
| − | |||
FSC-Type1 1 | FSC-Type1 1 | ||
-- MAC sets C but not A on copying for | -- MAC sets C but not A on copying for | ||
-- forwarding. | -- forwarding. | ||
| − | |||
FSC-Type2 2 | FSC-Type2 2 | ||
-- MAC resets C and sets A on C set and | -- MAC resets C and sets A on C set and | ||
-- A reset if the frame is not copied and the | -- A reset if the frame is not copied and the | ||
-- frame was addressed to this MAC | -- frame was addressed to this MAC | ||
| − | |||
FSC-Type0-programmable 8 | FSC-Type0-programmable 8 | ||
-- Type0 capability is programmable | -- Type0 capability is programmable | ||
| − | |||
FSC-Type1-programmable 9 | FSC-Type1-programmable 9 | ||
-- Type1 capability is programmable | -- Type1 capability is programmable | ||
| − | |||
FSC-Type2-programmable 10 | FSC-Type2-programmable 10 | ||
-- Type2 capability is programmable | -- Type2 capability is programmable | ||
| Line 907: | Line 871: | ||
"ANSI { fddiMAC 11 }" | "ANSI { fddiMAC 11 }" | ||
::= { snmpFddiMACEntry 3 } | ::= { snmpFddiMACEntry 3 } | ||
| − | |||
snmpFddiMACTMaxGreatestLowerBound OBJECT-TYPE | snmpFddiMACTMaxGreatestLowerBound OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 918: | Line 881: | ||
"ANSI { fddiMAC 13 }" | "ANSI { fddiMAC 13 }" | ||
::= { snmpFddiMACEntry 4 } | ::= { snmpFddiMACEntry 4 } | ||
| − | |||
snmpFddiMACTVXGreatestLowerBound OBJECT-TYPE | snmpFddiMACTVXGreatestLowerBound OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
ACCESS read-only | ACCESS read-only | ||
STATUS mandatory | STATUS mandatory | ||
| + | |||
| + | |||
| Line 934: | Line 898: | ||
"ANSI { fddiMAC 14 }" | "ANSI { fddiMAC 14 }" | ||
::= { snmpFddiMACEntry 5 } | ::= { snmpFddiMACEntry 5 } | ||
| − | |||
snmpFddiMACPathsAvailable OBJECT-TYPE | snmpFddiMACPathsAvailable OBJECT-TYPE | ||
SYNTAX INTEGER (0..7) | SYNTAX INTEGER (0..7) | ||
| Line 942: | Line 905: | ||
"A value that indicates the PATH types available | "A value that indicates the PATH types available | ||
for this MAC. | for this MAC. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each type of PATH that | the value zero, then for each type of PATH that | ||
| Line 948: | Line 910: | ||
added to the sum. The powers are according to the | added to the sum. The powers are according to the | ||
following table: | following table: | ||
| − | |||
Path Power | Path Power | ||
Primary 0 | Primary 0 | ||
| Line 956: | Line 917: | ||
"ANSI { fddiMAC 22 }" | "ANSI { fddiMAC 22 }" | ||
::= { snmpFddiMACEntry 6 } | ::= { snmpFddiMACEntry 6 } | ||
| − | |||
snmpFddiMACCurrentPath OBJECT-TYPE | snmpFddiMACCurrentPath OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 973: | Line 933: | ||
"ANSI { fddiMAC 23 }" | "ANSI { fddiMAC 23 }" | ||
::= { snmpFddiMACEntry 7 } | ::= { snmpFddiMACEntry 7 } | ||
| − | |||
snmpFddiMACUpstreamNbr OBJECT-TYPE | snmpFddiMACUpstreamNbr OBJECT-TYPE | ||
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) | SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) | ||
| + | |||
| + | |||
| Line 992: | Line 953: | ||
"ANSI { fddiMAC 24 }" | "ANSI { fddiMAC 24 }" | ||
::= { snmpFddiMACEntry 8 } | ::= { snmpFddiMACEntry 8 } | ||
| − | |||
snmpFddiMACOldUpstreamNbr OBJECT-TYPE | snmpFddiMACOldUpstreamNbr OBJECT-TYPE | ||
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) | SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) | ||
| Line 1,007: | Line 967: | ||
"ANSI { fddiMAC 26 }" | "ANSI { fddiMAC 26 }" | ||
::= { snmpFddiMACEntry 9 } | ::= { snmpFddiMACEntry 9 } | ||
| − | |||
snmpFddiMACDupAddrTest OBJECT-TYPE | snmpFddiMACDupAddrTest OBJECT-TYPE | ||
SYNTAX INTEGER { none(1), pass(2), fail(3) } | SYNTAX INTEGER { none(1), pass(2), fail(3) } | ||
| Line 1,018: | Line 977: | ||
"ANSI { fddiMAC 29 }" | "ANSI { fddiMAC 29 }" | ||
::= { snmpFddiMACEntry 10 } | ::= { snmpFddiMACEntry 10 } | ||
| − | |||
snmpFddiMACPathsRequested OBJECT-TYPE | snmpFddiMACPathsRequested OBJECT-TYPE | ||
SYNTAX INTEGER | SYNTAX INTEGER | ||
| Line 1,026: | Line 984: | ||
"A value that indicates PATH(s) desired for this | "A value that indicates PATH(s) desired for this | ||
MAC. | MAC. | ||
| − | |||
The value is a sum which represents the individual | The value is a sum which represents the individual | ||
PATHs that are desired. This value initially | PATHs that are desired. This value initially | ||
| + | |||
| + | |||
| Line 1,038: | Line 997: | ||
the sum. The powers are according to the | the sum. The powers are according to the | ||
following table: | following table: | ||
| − | |||
Path Power | Path Power | ||
Primary 0 | Primary 0 | ||
| Line 1,044: | Line 1,002: | ||
Local 2 | Local 2 | ||
Isolated 3 | Isolated 3 | ||
| − | |||
The precedence order is primary, secondary, local, | The precedence order is primary, secondary, local, | ||
and then isolated if multiple PATHs are desired | and then isolated if multiple PATHs are desired | ||
| Line 1,051: | Line 1,008: | ||
"ANSI { fddiMAC 32 }" | "ANSI { fddiMAC 32 }" | ||
::= { snmpFddiMACEntry 11 } | ::= { snmpFddiMACEntry 11 } | ||
| − | |||
snmpFddiMACDownstreamPORTType OBJECT-TYPE | snmpFddiMACDownstreamPORTType OBJECT-TYPE | ||
SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) } | SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) } | ||
| Line 1,062: | Line 1,018: | ||
"ANSI { fddiMAC 33 }" | "ANSI { fddiMAC 33 }" | ||
::= { snmpFddiMACEntry 12 } | ::= { snmpFddiMACEntry 12 } | ||
| − | |||
snmpFddiMACSMTAddress OBJECT-TYPE | snmpFddiMACSMTAddress OBJECT-TYPE | ||
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) | SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6)) | ||
| Line 1,073: | Line 1,028: | ||
"ANSI { fddiMAC 41 }" | "ANSI { fddiMAC 41 }" | ||
::= { snmpFddiMACEntry 13 } | ::= { snmpFddiMACEntry 13 } | ||
| − | |||
snmpFddiMACTReq OBJECT-TYPE | snmpFddiMACTReq OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,082: | Line 1,036: | ||
ANSI MAC 7.3.5.2)." | ANSI MAC 7.3.5.2)." | ||
REFERENCE | REFERENCE | ||
| + | |||
| + | |||
| Line 1,089: | Line 1,045: | ||
"ANSI { fddiMAC 51 }" | "ANSI { fddiMAC 51 }" | ||
::= { snmpFddiMACEntry 14 } | ::= { snmpFddiMACEntry 14 } | ||
| − | |||
snmpFddiMACTNeg OBJECT-TYPE | snmpFddiMACTNeg OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,100: | Line 1,055: | ||
"ANSI { fddiMAC 52 }" | "ANSI { fddiMAC 52 }" | ||
::= { snmpFddiMACEntry 15 } | ::= { snmpFddiMACEntry 15 } | ||
| − | |||
snmpFddiMACTMax OBJECT-TYPE | snmpFddiMACTMax OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,111: | Line 1,065: | ||
"ANSI { fddiMAC 53 }" | "ANSI { fddiMAC 53 }" | ||
::= { snmpFddiMACEntry 16 } | ::= { snmpFddiMACEntry 16 } | ||
| − | |||
snmpFddiMACTvxValue OBJECT-TYPE | snmpFddiMACTvxValue OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,122: | Line 1,075: | ||
"ANSI { fddiMAC 54 }" | "ANSI { fddiMAC 54 }" | ||
::= { snmpFddiMACEntry 17 } | ::= { snmpFddiMACEntry 17 } | ||
| − | |||
snmpFddiMACTMin OBJECT-TYPE | snmpFddiMACTMin OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,133: | Line 1,085: | ||
"ANSI { fddiMAC 55 }" | "ANSI { fddiMAC 55 }" | ||
::= { snmpFddiMACEntry 18 } | ::= { snmpFddiMACEntry 18 } | ||
| + | |||
| + | |||
| Line 1,147: | Line 1,101: | ||
"A value that indicates the MAC's operational | "A value that indicates the MAC's operational | ||
frame status setting functionality. | frame status setting functionality. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each functionality | the value zero, then for each functionality | ||
present, 2 raised to a power is added to the sum. | present, 2 raised to a power is added to the sum. | ||
The powers are according to the following table: | The powers are according to the following table: | ||
| − | |||
Functionality Power | Functionality Power | ||
FSC-Type0 0 | FSC-Type0 0 | ||
-- MAC repeats A/C indicators as received | -- MAC repeats A/C indicators as received | ||
| − | |||
FSC-Type1 1 | FSC-Type1 1 | ||
-- MAC sets C but not A on copying for | -- MAC sets C but not A on copying for | ||
-- forwarding | -- forwarding | ||
| − | |||
FSC-Type2 2 | FSC-Type2 2 | ||
-- MAC resets C and sets A on C set and A | -- MAC resets C and sets A on C set and A | ||
| Line 1,168: | Line 1,118: | ||
"ANSI { fddiMAC 63 }" | "ANSI { fddiMAC 63 }" | ||
::= { snmpFddiMACEntry 19 } | ::= { snmpFddiMACEntry 19 } | ||
| − | |||
snmpFddiMACFrameCts OBJECT-TYPE | snmpFddiMACFrameCts OBJECT-TYPE | ||
SYNTAX Counter | SYNTAX Counter | ||
| Line 1,178: | Line 1,127: | ||
"ANSI { fddiMAC 71 }" | "ANSI { fddiMAC 71 }" | ||
::= { snmpFddiMACEntry 20 } | ::= { snmpFddiMACEntry 20 } | ||
| − | |||
snmpFddiMACErrorCts OBJECT-TYPE | snmpFddiMACErrorCts OBJECT-TYPE | ||
SYNTAX Counter | SYNTAX Counter | ||
| Line 1,188: | Line 1,136: | ||
"ANSI { fddiMAC 81 }" | "ANSI { fddiMAC 81 }" | ||
::= { snmpFddiMACEntry 21 } | ::= { snmpFddiMACEntry 21 } | ||
| + | |||
| + | |||
| Line 1,202: | Line 1,152: | ||
"ANSI { fddiMAC 82 }" | "ANSI { fddiMAC 82 }" | ||
::= { snmpFddiMACEntry 22 } | ::= { snmpFddiMACEntry 22 } | ||
| − | |||
snmpFddiMACFrameErrorThreshold OBJECT-TYPE | snmpFddiMACFrameErrorThreshold OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 1,228: | Line 1,177: | ||
"ANSI { fddiMAC 95 }" | "ANSI { fddiMAC 95 }" | ||
::= { snmpFddiMACEntry 23 } | ::= { snmpFddiMACEntry 23 } | ||
| − | |||
snmpFddiMACFrameErrorRatio OBJECT-TYPE | snmpFddiMACFrameErrorRatio OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 1,241: | Line 1,189: | ||
"ANSI { fddiMAC 96 }" | "ANSI { fddiMAC 96 }" | ||
::= { snmpFddiMACEntry 24 } | ::= { snmpFddiMACEntry 24 } | ||
| + | |||
| + | |||
| Line 1,266: | Line 1,216: | ||
"ANSI { fddiMAC 111 }" | "ANSI { fddiMAC 111 }" | ||
::= { snmpFddiMACEntry 25 } | ::= { snmpFddiMACEntry 25 } | ||
| − | |||
snmpFddiMACDaFlag OBJECT-TYPE | snmpFddiMACDaFlag OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
| Line 1,277: | Line 1,226: | ||
"ANSI { fddiMAC 112 }" | "ANSI { fddiMAC 112 }" | ||
::= { snmpFddiMACEntry 26 } | ::= { snmpFddiMACEntry 26 } | ||
| − | |||
snmpFddiMACUnaDaFlag OBJECT-TYPE | snmpFddiMACUnaDaFlag OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
| Line 1,289: | Line 1,237: | ||
"ANSI { fddiMAC 113 }" | "ANSI { fddiMAC 113 }" | ||
::= { snmpFddiMACEntry 27 } | ::= { snmpFddiMACEntry 27 } | ||
| − | |||
snmpFddiMACFrameCondition OBJECT-TYPE | snmpFddiMACFrameCondition OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
ACCESS read-only | ACCESS read-only | ||
STATUS mandatory | STATUS mandatory | ||
| + | |||
| + | |||
| Line 1,306: | Line 1,255: | ||
"ANSI { fddiMAC 114 }" | "ANSI { fddiMAC 114 }" | ||
::= { snmpFddiMACEntry 28 } | ::= { snmpFddiMACEntry 28 } | ||
| − | |||
snmpFddiMACChipSet OBJECT-TYPE | snmpFddiMACChipSet OBJECT-TYPE | ||
SYNTAX OBJECT IDENTIFIER | SYNTAX OBJECT IDENTIFIER | ||
| Line 1,340: | Line 1,288: | ||
the hardware chip set is unknown, the object | the hardware chip set is unknown, the object | ||
identifier | identifier | ||
| − | |||
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } | unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } | ||
| − | |||
is returned. Note that unknownChipSet is a | is returned. Note that unknownChipSet is a | ||
syntactically valid object identifier, and any | syntactically valid object identifier, and any | ||
conformant implementation of ASN.1 and the BER | conformant implementation of ASN.1 and the BER | ||
must be able to generate and recognize this | must be able to generate and recognize this | ||
| + | |||
| + | |||
| Line 1,354: | Line 1,302: | ||
value." | value." | ||
::= { snmpFddiMACEntry 29 } | ::= { snmpFddiMACEntry 29 } | ||
| − | |||
snmpFddiMACAction OBJECT-TYPE | snmpFddiMACAction OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 1,369: | Line 1,316: | ||
other(1). The behavior of setting this variable | other(1). The behavior of setting this variable | ||
to each of the acceptable values is as follows: | to each of the acceptable values is as follows: | ||
| − | |||
Other: Results in a badValue | Other: Results in a badValue | ||
error. | error. | ||
| − | |||
enableLLCService: enables MAC service to | enableLLCService: enables MAC service to | ||
higher layers. | higher layers. | ||
| − | |||
disableLLCService: disables MAC service to | disableLLCService: disables MAC service to | ||
higher layers. | higher layers. | ||
| − | |||
connectMAC: connect this MAC in | connectMAC: connect this MAC in | ||
station. | station. | ||
| − | |||
disconnectMAC: disconnect this MAC in | disconnectMAC: disconnect this MAC in | ||
station. | station. | ||
| − | |||
Attempts to set this object to all other values | Attempts to set this object to all other values | ||
results in a badValue error." | results in a badValue error." | ||
| Line 1,390: | Line 1,331: | ||
"ANSI { fddiMAC 130 }" | "ANSI { fddiMAC 130 }" | ||
::= { snmpFddiMACEntry 30 } | ::= { snmpFddiMACEntry 30 } | ||
| − | |||
-- the PATH group | -- the PATH group | ||
| − | |||
-- the PATH group is empty for now and shall remain so until | -- the PATH group is empty for now and shall remain so until | ||
-- the ANSI community sorts out their PATH group | -- the ANSI community sorts out their PATH group | ||
| − | |||
-- the PORT group | -- the PORT group | ||
-- Implementation of the PORT group is mandatory for all | -- Implementation of the PORT group is mandatory for all | ||
| + | |||
| + | |||
| Line 1,406: | Line 1,346: | ||
-- systems which implement manageable FDDI subsystems. | -- systems which implement manageable FDDI subsystems. | ||
| − | |||
snmpFddiPORTNumber OBJECT-TYPE | snmpFddiPORTNumber OBJECT-TYPE | ||
SYNTAX INTEGER (0..65535) | SYNTAX INTEGER (0..65535) | ||
| Line 1,419: | Line 1,358: | ||
re-initialization." | re-initialization." | ||
::= { snmpFddiPORT 1 } | ::= { snmpFddiPORT 1 } | ||
| − | |||
-- the PORT table | -- the PORT table | ||
| − | |||
snmpFddiPORTTable OBJECT-TYPE | snmpFddiPORTTable OBJECT-TYPE | ||
SYNTAX SEQUENCE OF SnmpFddiPORTEntry | SYNTAX SEQUENCE OF SnmpFddiPORTEntry | ||
| Line 1,431: | Line 1,368: | ||
given by the value of snmpFddiPORTNumber." | given by the value of snmpFddiPORTNumber." | ||
::= { snmpFddiPORT 2 } | ::= { snmpFddiPORT 2 } | ||
| − | |||
snmpFddiPORTEntry OBJECT-TYPE | snmpFddiPORTEntry OBJECT-TYPE | ||
SYNTAX SnmpFddiPORTEntry | SYNTAX SnmpFddiPORTEntry | ||
| Line 1,441: | Line 1,377: | ||
INDEX { snmpFddiPORTSMTIndex, snmpFddiPORTIndex } | INDEX { snmpFddiPORTSMTIndex, snmpFddiPORTIndex } | ||
::= { snmpFddiPORTTable 1 } | ::= { snmpFddiPORTTable 1 } | ||
| − | |||
SnmpFddiPORTEntry ::= | SnmpFddiPORTEntry ::= | ||
SEQUENCE { | SEQUENCE { | ||
| Line 1,453: | Line 1,388: | ||
INTEGER, | INTEGER, | ||
snmpFddiPORTConnectionPolicies | snmpFddiPORTConnectionPolicies | ||
| + | |||
| + | |||
| Line 1,500: | Line 1,437: | ||
INTEGER | INTEGER | ||
} | } | ||
| − | |||
snmpFddiPORTSMTIndex OBJECT-TYPE | snmpFddiPORTSMTIndex OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 1,506: | Line 1,442: | ||
STATUS mandatory | STATUS mandatory | ||
DESCRIPTION | DESCRIPTION | ||
| + | |||
| + | |||
| Line 1,514: | Line 1,452: | ||
PORT." | PORT." | ||
::= { snmpFddiPORTEntry 1 } | ::= { snmpFddiPORTEntry 1 } | ||
| − | |||
snmpFddiPORTIndex OBJECT-TYPE | snmpFddiPORTIndex OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 1,529: | Line 1,466: | ||
management system to the next re-initialization." | management system to the next re-initialization." | ||
::= { snmpFddiPORTEntry 2 } | ::= { snmpFddiPORTEntry 2 } | ||
| − | |||
snmpFddiPORTPCType OBJECT-TYPE | snmpFddiPORTPCType OBJECT-TYPE | ||
SYNTAX INTEGER { a(1), b(2), s(3), m(4) } | SYNTAX INTEGER { a(1), b(2), s(3), m(4) } | ||
| Line 1,540: | Line 1,476: | ||
"ANSI { fddiPORT 12 }" | "ANSI { fddiPORT 12 }" | ||
::= { snmpFddiPORTEntry 3 } | ::= { snmpFddiPORTEntry 3 } | ||
| − | |||
snmpFddiPORTPCNeighbor OBJECT-TYPE | snmpFddiPORTPCNeighbor OBJECT-TYPE | ||
SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) } | SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) } | ||
| Line 1,552: | Line 1,487: | ||
"ANSI { fddiPORT 13 }" | "ANSI { fddiPORT 13 }" | ||
::= { snmpFddiPORTEntry 4 } | ::= { snmpFddiPORTEntry 4 } | ||
| − | |||
snmpFddiPORTConnectionPolicies OBJECT-TYPE | snmpFddiPORTConnectionPolicies OBJECT-TYPE | ||
SYNTAX INTEGER (0..7) | SYNTAX INTEGER (0..7) | ||
| Line 1,559: | Line 1,493: | ||
DESCRIPTION | DESCRIPTION | ||
"A value that indicates the node's PORT policies. | "A value that indicates the node's PORT policies. | ||
| + | |||
| + | |||
| Line 1,568: | Line 1,504: | ||
Capability flags should be set (refer to ANSI SMT | Capability flags should be set (refer to ANSI SMT | ||
9.4.3.2). | 9.4.3.2). | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each PORT policy, 2 | the value zero, then for each PORT policy, 2 | ||
raised to a power is added to the sum. The powers | raised to a power is added to the sum. The powers | ||
are according to the following table: | are according to the following table: | ||
| − | |||
Policy Power | Policy Power | ||
Pc-MAC-LCT 0 | Pc-MAC-LCT 0 | ||
| Line 1,581: | Line 1,515: | ||
"ANSI { fddiPORT 14 }" | "ANSI { fddiPORT 14 }" | ||
::= { snmpFddiPORTEntry 5 } | ::= { snmpFddiPORTEntry 5 } | ||
| − | |||
snmpFddiPORTRemoteMACIndicated OBJECT-TYPE | snmpFddiPORTRemoteMACIndicated OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
| Line 1,594: | Line 1,527: | ||
"ANSI { fddiPORT 15 }" | "ANSI { fddiPORT 15 }" | ||
::= { snmpFddiPORTEntry 6 } | ::= { snmpFddiPORTEntry 6 } | ||
| − | |||
snmpFddiPORTCEState OBJECT-TYPE | snmpFddiPORTCEState OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 1,612: | Line 1,544: | ||
REFERENCE | REFERENCE | ||
"ANSI { fddiPORT 16 }" | "ANSI { fddiPORT 16 }" | ||
| + | |||
| + | |||
| Line 1,618: | Line 1,552: | ||
::= { snmpFddiPORTEntry 7 } | ::= { snmpFddiPORTEntry 7 } | ||
| − | |||
snmpFddiPORTPathsRequested OBJECT-TYPE | snmpFddiPORTPathsRequested OBJECT-TYPE | ||
SYNTAX INTEGER (0..15) | SYNTAX INTEGER (0..15) | ||
| Line 1,637: | Line 1,570: | ||
sent and neither the 'Primary' or 'Secondary' | sent and neither the 'Primary' or 'Secondary' | ||
PATHs are sent, then the CF_Insert_L flag is set. | PATHs are sent, then the CF_Insert_L flag is set. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each type of PATH | the value zero, then for each type of PATH | ||
desired, 2 raised to a power is added to the sum. | desired, 2 raised to a power is added to the sum. | ||
The powers are according to the following table: | The powers are according to the following table: | ||
| − | |||
Path Power | Path Power | ||
Primary 0 | Primary 0 | ||
| Line 1,651: | Line 1,582: | ||
"ANSI { fddiPORT 17 }" | "ANSI { fddiPORT 17 }" | ||
::= { snmpFddiPORTEntry 8 } | ::= { snmpFddiPORTEntry 8 } | ||
| − | |||
snmpFddiPORTMACPlacement OBJECT-TYPE | snmpFddiPORTMACPlacement OBJECT-TYPE | ||
SYNTAX FddiResourceId -- INTEGER (0..65535) | SYNTAX FddiResourceId -- INTEGER (0..65535) | ||
| Line 1,665: | Line 1,595: | ||
"ANSI { fddiPORT 18 }" | "ANSI { fddiPORT 18 }" | ||
::= { snmpFddiPORTEntry 9 } | ::= { snmpFddiPORTEntry 9 } | ||
| + | |||
| + | |||
| Line 1,677: | Line 1,609: | ||
"A value that indicates the PATH types available | "A value that indicates the PATH types available | ||
for M and S PORTs. | for M and S PORTs. | ||
| − | |||
The value is a sum. This value initially takes | The value is a sum. This value initially takes | ||
the value zero, then for each type of PATH that | the value zero, then for each type of PATH that | ||
| Line 1,683: | Line 1,614: | ||
added to the sum. The powers are according to the | added to the sum. The powers are according to the | ||
following table: | following table: | ||
| − | |||
Path Power | Path Power | ||
Primary 0 | Primary 0 | ||
| Line 1,691: | Line 1,621: | ||
"ANSI { fddiPORT 19 }" | "ANSI { fddiPORT 19 }" | ||
::= { snmpFddiPORTEntry 10 } | ::= { snmpFddiPORTEntry 10 } | ||
| − | |||
snmpFddiPORTMACLoopTime OBJECT-TYPE | snmpFddiPORTMACLoopTime OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,703: | Line 1,632: | ||
"ANSI { fddiPORT 21 }" | "ANSI { fddiPORT 21 }" | ||
::= { snmpFddiPORTEntry 11 } | ::= { snmpFddiPORTEntry 11 } | ||
| − | |||
snmpFddiPORTTBMax OBJECT-TYPE | snmpFddiPORTTBMax OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 1,713: | Line 1,641: | ||
"ANSI { fddiPORT 32 }" | "ANSI { fddiPORT 32 }" | ||
::= { snmpFddiPORTEntry 12 } | ::= { snmpFddiPORTEntry 12 } | ||
| − | |||
snmpFddiPORTBSFlag OBJECT-TYPE | snmpFddiPORTBSFlag OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
ACCESS read-only | ACCESS read-only | ||
STATUS mandatory | STATUS mandatory | ||
| + | |||
| + | |||
| Line 1,729: | Line 1,658: | ||
"ANSI { fddiPORT 33 }" | "ANSI { fddiPORT 33 }" | ||
::= { snmpFddiPORTEntry 13 } | ::= { snmpFddiPORTEntry 13 } | ||
| − | |||
snmpFddiPORTLCTFailCts OBJECT-TYPE | snmpFddiPORTLCTFailCts OBJECT-TYPE | ||
SYNTAX Counter | SYNTAX Counter | ||
| Line 1,741: | Line 1,669: | ||
"ANSI { fddiPORT 42 }" | "ANSI { fddiPORT 42 }" | ||
::= { snmpFddiPORTEntry 14 } | ::= { snmpFddiPORTEntry 14 } | ||
| − | |||
snmpFddiPORTLerEstimate OBJECT-TYPE | snmpFddiPORTLerEstimate OBJECT-TYPE | ||
SYNTAX INTEGER (4..15) | SYNTAX INTEGER (4..15) | ||
| Line 1,753: | Line 1,680: | ||
"ANSI { fddiPORT 51 }" | "ANSI { fddiPORT 51 }" | ||
::= { snmpFddiPORTEntry 15 } | ::= { snmpFddiPORTEntry 15 } | ||
| − | |||
snmpFddiPORTLemRejectCts OBJECT-TYPE | snmpFddiPORTLemRejectCts OBJECT-TYPE | ||
SYNTAX Counter | SYNTAX Counter | ||
| Line 1,764: | Line 1,690: | ||
"ANSI { fddiPORT 52 }" | "ANSI { fddiPORT 52 }" | ||
::= { snmpFddiPORTEntry 16 } | ::= { snmpFddiPORTEntry 16 } | ||
| − | |||
snmpFddiPORTLemCts OBJECT-TYPE | snmpFddiPORTLemCts OBJECT-TYPE | ||
SYNTAX Counter | SYNTAX Counter | ||
| Line 1,771: | Line 1,696: | ||
DESCRIPTION | DESCRIPTION | ||
"The aggregate link error monitor error count, set | "The aggregate link error monitor error count, set | ||
| + | |||
| + | |||
| Line 1,780: | Line 1,707: | ||
"ANSI { fddiPORT 53 }" | "ANSI { fddiPORT 53 }" | ||
::= { snmpFddiPORTEntry 17 } | ::= { snmpFddiPORTEntry 17 } | ||
| − | |||
snmpFddiPORTLerCutoff OBJECT-TYPE | snmpFddiPORTLerCutoff OBJECT-TYPE | ||
SYNTAX INTEGER (4..15) | SYNTAX INTEGER (4..15) | ||
| Line 1,793: | Line 1,719: | ||
"ANSI { fddiPORT 58 }" | "ANSI { fddiPORT 58 }" | ||
::= { snmpFddiPORTEntry 18 } | ::= { snmpFddiPORTEntry 18 } | ||
| − | |||
snmpFddiPORTLerAlarm OBJECT-TYPE | snmpFddiPORTLerAlarm OBJECT-TYPE | ||
SYNTAX INTEGER (4..15) | SYNTAX INTEGER (4..15) | ||
| Line 1,806: | Line 1,731: | ||
"ANSI { fddiPORT 59 }" | "ANSI { fddiPORT 59 }" | ||
::= { snmpFddiPORTEntry 19 } | ::= { snmpFddiPORTEntry 19 } | ||
| − | |||
snmpFddiPORTConnectState OBJECT-TYPE | snmpFddiPORTConnectState OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 1,823: | Line 1,747: | ||
and their corresponding PCM states and PC-Withhold | and their corresponding PCM states and PC-Withhold | ||
condition, when relevant, are: | condition, when relevant, are: | ||
| + | |||
| + | |||
| Line 1,830: | Line 1,756: | ||
disabled: (PC0:Off, PC9:Maint) | disabled: (PC0:Off, PC9:Maint) | ||
| − | |||
connecting: (PC1(Break) || PC3 (Connect) || PC4 | connecting: (PC1(Break) || PC3 (Connect) || PC4 | ||
(Next) || PC5 (Signal) || PC6 | (Next) || PC5 (Signal) || PC6 | ||
(Join) || PC7 (Verify)) && | (Join) || PC7 (Verify)) && | ||
(PC_Withhold = None) | (PC_Withhold = None) | ||
| − | |||
standby: (NOT PC_Withhold == None) | standby: (NOT PC_Withhold == None) | ||
| − | |||
active: (PC2:Trace || PC8:Active) " | active: (PC2:Trace || PC8:Active) " | ||
REFERENCE | REFERENCE | ||
"ANSI { fddiPORT 61 }" | "ANSI { fddiPORT 61 }" | ||
::= { snmpFddiPORTEntry 20 } | ::= { snmpFddiPORTEntry 20 } | ||
| − | |||
snmpFddiPORTPCMState OBJECT-TYPE | snmpFddiPORTPCMState OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 1,863: | Line 1,785: | ||
"ANSI { fddiPORT 62 }" | "ANSI { fddiPORT 62 }" | ||
::= { snmpFddiPORTEntry 21 } | ::= { snmpFddiPORTEntry 21 } | ||
| − | |||
snmpFddiPORTPCWithhold OBJECT-TYPE | snmpFddiPORTPCWithhold OBJECT-TYPE | ||
SYNTAX INTEGER { none(1), m-m(2), other(3) } | SYNTAX INTEGER { none(1), m-m(2), other(3) } | ||
| Line 1,873: | Line 1,794: | ||
"ANSI { fddiPORT 63 }" | "ANSI { fddiPORT 63 }" | ||
::= { snmpFddiPORTEntry 22 } | ::= { snmpFddiPORTEntry 22 } | ||
| − | |||
snmpFddiPORTLerCondition OBJECT-TYPE | snmpFddiPORTLerCondition OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
ACCESS read-only | ACCESS read-only | ||
| + | |||
| + | |||
| Line 1,889: | Line 1,811: | ||
"ANSI { fddiPORT 64 }" | "ANSI { fddiPORT 64 }" | ||
::= { snmpFddiPORTEntry 23 } | ::= { snmpFddiPORTEntry 23 } | ||
| − | |||
snmpFddiPORTChipSet OBJECT-TYPE | snmpFddiPORTChipSet OBJECT-TYPE | ||
SYNTAX OBJECT IDENTIFIER | SYNTAX OBJECT IDENTIFIER | ||
| Line 1,923: | Line 1,844: | ||
chips. If the hardware chip set is unknown, the | chips. If the hardware chip set is unknown, the | ||
object identifier | object identifier | ||
| − | |||
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } | unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } | ||
| − | |||
is returned. Note that unknownChipSet is a | is returned. Note that unknownChipSet is a | ||
syntactically valid object identifier, and any | syntactically valid object identifier, and any | ||
conformant implementation of ASN.1 and the BER | conformant implementation of ASN.1 and the BER | ||
must be able to generate and recognize this | must be able to generate and recognize this | ||
| + | |||
| + | |||
| Line 1,937: | Line 1,858: | ||
value." | value." | ||
::= { snmpFddiPORTEntry 24 } | ::= { snmpFddiPORTEntry 24 } | ||
| − | |||
snmpFddiPORTAction OBJECT-TYPE | snmpFddiPORTAction OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
| Line 1,953: | Line 1,873: | ||
other(1). The behavior of setting this variable | other(1). The behavior of setting this variable | ||
to each of the acceptable values is as follows: | to each of the acceptable values is as follows: | ||
| − | |||
Other: Results in a badValue error. | Other: Results in a badValue error. | ||
| − | |||
maintPORT: Signal PC_Maint | maintPORT: Signal PC_Maint | ||
| − | |||
enablePORT: Signal PC_Enable | enablePORT: Signal PC_Enable | ||
| − | |||
disablePORT: Signal PC_Disable | disablePORT: Signal PC_Disable | ||
| − | |||
startPORT: Signal PC_Start | startPORT: Signal PC_Start | ||
| − | |||
stopPORT: Signal PC_Stop | stopPORT: Signal PC_Stop | ||
| − | |||
Signals cause an SM_CM_CONTROL.request service to | Signals cause an SM_CM_CONTROL.request service to | ||
be generated with a control_action of `Signal' and | be generated with a control_action of `Signal' and | ||
| Line 1,971: | Line 1,884: | ||
value (i.e., PC_Maint, PC_Enable, PC_Disable, | value (i.e., PC_Maint, PC_Enable, PC_Disable, | ||
PC_Start, PC_Stop). Ref. ANSI SMT Section 9.3.2. | PC_Start, PC_Stop). Ref. ANSI SMT Section 9.3.2. | ||
| − | |||
Attempts to set this object to all other values | Attempts to set this object to all other values | ||
results in a badValue error." | results in a badValue error." | ||
| Line 1,977: | Line 1,889: | ||
"ANSI { fddiPORT 70 }" | "ANSI { fddiPORT 70 }" | ||
::= { snmpFddiPORTEntry 25 } | ::= { snmpFddiPORTEntry 25 } | ||
| − | |||
-- the ATTACHMENT group | -- the ATTACHMENT group | ||
-- Implementation of the ATTACHMENT group is mandatory for | -- Implementation of the ATTACHMENT group is mandatory for | ||
-- all systems which implement manageable FDDI subsystems. | -- all systems which implement manageable FDDI subsystems. | ||
| + | |||
| + | |||
| Line 2,000: | Line 1,913: | ||
re-initialization." | re-initialization." | ||
::= { snmpFddiATTACHMENT 1 } | ::= { snmpFddiATTACHMENT 1 } | ||
| − | |||
-- the ATTACHMENT table | -- the ATTACHMENT table | ||
| − | |||
snmpFddiATTACHMENTTable OBJECT-TYPE | snmpFddiATTACHMENTTable OBJECT-TYPE | ||
SYNTAX SEQUENCE OF SnmpFddiATTACHMENTEntry | SYNTAX SEQUENCE OF SnmpFddiATTACHMENTEntry | ||
| Line 2,013: | Line 1,924: | ||
snmpFddiATTACHMENTNumber." | snmpFddiATTACHMENTNumber." | ||
::= { snmpFddiATTACHMENT 2 } | ::= { snmpFddiATTACHMENT 2 } | ||
| − | |||
snmpFddiATTACHMENTEntry OBJECT-TYPE | snmpFddiATTACHMENTEntry OBJECT-TYPE | ||
SYNTAX SnmpFddiATTACHMENTEntry | SYNTAX SnmpFddiATTACHMENTEntry | ||
| Line 2,021: | Line 1,931: | ||
"An ATTACHMENT entry containing information common | "An ATTACHMENT entry containing information common | ||
to a given set of ATTACHMENTs. | to a given set of ATTACHMENTs. | ||
| − | |||
The ATTACHMENT Resource represents a PORT or a | The ATTACHMENT Resource represents a PORT or a | ||
pair of PORTs plus the optional associated optical | pair of PORTs plus the optional associated optical | ||
| Line 2,036: | Line 1,945: | ||
INDEX { snmpFddiATTACHMENTSMTIndex, | INDEX { snmpFddiATTACHMENTSMTIndex, | ||
snmpFddiATTACHMENTIndex } | snmpFddiATTACHMENTIndex } | ||
| + | |||
| + | |||
| Line 2,042: | Line 1,953: | ||
::= { snmpFddiATTACHMENTTable 1 } | ::= { snmpFddiATTACHMENTTable 1 } | ||
| − | |||
SnmpFddiATTACHMENTEntry ::= | SnmpFddiATTACHMENTEntry ::= | ||
SEQUENCE { | SEQUENCE { | ||
| Line 2,060: | Line 1,970: | ||
INTEGER | INTEGER | ||
} | } | ||
| − | |||
snmpFddiATTACHMENTSMTIndex OBJECT-TYPE | snmpFddiATTACHMENTSMTIndex OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 2,069: | Line 1,978: | ||
ATTACHMENT." | ATTACHMENT." | ||
::= { snmpFddiATTACHMENTEntry 1 } | ::= { snmpFddiATTACHMENTEntry 1 } | ||
| − | |||
snmpFddiATTACHMENTIndex OBJECT-TYPE | snmpFddiATTACHMENTIndex OBJECT-TYPE | ||
SYNTAX INTEGER (1..65535) | SYNTAX INTEGER (1..65535) | ||
| Line 2,084: | Line 1,992: | ||
management system to the next re-initialization." | management system to the next re-initialization." | ||
::= { snmpFddiATTACHMENTEntry 2 } | ::= { snmpFddiATTACHMENTEntry 2 } | ||
| − | |||
snmpFddiATTACHMENTClass OBJECT-TYPE | snmpFddiATTACHMENTClass OBJECT-TYPE | ||
SYNTAX INTEGER { | SYNTAX INTEGER { | ||
single-attachment(1), | single-attachment(1), | ||
dual-attachment(2), | dual-attachment(2), | ||
| + | |||
| + | |||
| Line 2,103: | Line 2,012: | ||
optical bypass that are managed as a functional | optical bypass that are managed as a functional | ||
unit. The PORT associations are the following: | unit. The PORT associations are the following: | ||
| − | |||
single-attachment - S PORTs | single-attachment - S PORTs | ||
dual-attachment - A/B PORT Pairs | dual-attachment - A/B PORT Pairs | ||
| Line 2,110: | Line 2,018: | ||
"ANSI { fddiATTACHMENT 11 }" | "ANSI { fddiATTACHMENT 11 }" | ||
::= { snmpFddiATTACHMENTEntry 3 } | ::= { snmpFddiATTACHMENTEntry 3 } | ||
| − | |||
snmpFddiATTACHMENTOpticalBypassPresent OBJECT-TYPE | snmpFddiATTACHMENTOpticalBypassPresent OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2) } | SYNTAX INTEGER { true(1), false(2) } | ||
| Line 2,125: | Line 2,032: | ||
"ANSI { fddiATTACHMENT 12 }" | "ANSI { fddiATTACHMENT 12 }" | ||
::= { snmpFddiATTACHMENTEntry 4 } | ::= { snmpFddiATTACHMENTEntry 4 } | ||
| − | |||
snmpFddiATTACHMENTIMaxExpiration OBJECT-TYPE | snmpFddiATTACHMENTIMaxExpiration OBJECT-TYPE | ||
SYNTAX FddiTime | SYNTAX FddiTime | ||
| Line 2,139: | Line 2,045: | ||
"ANSI { fddiATTACHMENT 13 }" | "ANSI { fddiATTACHMENT 13 }" | ||
::= { snmpFddiATTACHMENTEntry 5 } | ::= { snmpFddiATTACHMENTEntry 5 } | ||
| − | |||
snmpFddiATTACHMENTInsertedStatus OBJECT-TYPE | snmpFddiATTACHMENTInsertedStatus OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2), unimplemented(3) } | SYNTAX INTEGER { true(1), false(2), unimplemented(3) } | ||
| + | |||
| + | |||
| Line 2,155: | Line 2,062: | ||
"ANSI { fddiATTACHMENT 14 }" | "ANSI { fddiATTACHMENT 14 }" | ||
::= { snmpFddiATTACHMENTEntry 6 } | ::= { snmpFddiATTACHMENTEntry 6 } | ||
| − | |||
snmpFddiATTACHMENTInsertPolicy OBJECT-TYPE | snmpFddiATTACHMENTInsertPolicy OBJECT-TYPE | ||
SYNTAX INTEGER { true(1), false(2), unimplemented(3) } | SYNTAX INTEGER { true(1), false(2), unimplemented(3) } | ||
| Line 2,167: | Line 2,073: | ||
"ANSI { fddiATTACHMENT 15 }" | "ANSI { fddiATTACHMENT 15 }" | ||
::= { snmpFddiATTACHMENTEntry 7 } | ::= { snmpFddiATTACHMENTEntry 7 } | ||
| − | |||
-- the Chip Set group | -- the Chip Set group | ||
| Line 2,173: | Line 2,078: | ||
-- with the snmpFddiMACChipSet and snmpFddiPORTChipSet | -- with the snmpFddiMACChipSet and snmpFddiPORTChipSet | ||
-- variables. | -- variables. | ||
| − | |||
snmpFddiPHYChipSets -- Chips primarily responsible | snmpFddiPHYChipSets -- Chips primarily responsible | ||
-- for implementing the PHY | -- for implementing the PHY | ||
-- function. | -- function. | ||
OBJECT IDENTIFIER ::= { snmpFddiChipSets 1 } | OBJECT IDENTIFIER ::= { snmpFddiChipSets 1 } | ||
| − | |||
-- None defined at present | -- None defined at present | ||
-- Chipsets may someday be | -- Chipsets may someday be | ||
-- defined here | -- defined here | ||
| − | |||
snmpFddiMACChipSets -- Chips primarily responsible | snmpFddiMACChipSets -- Chips primarily responsible | ||
| Line 2,188: | Line 2,090: | ||
-- MAC function. | -- MAC function. | ||
OBJECT IDENTIFIER ::= { snmpFddiChipSets 2 } | OBJECT IDENTIFIER ::= { snmpFddiChipSets 2 } | ||
| − | |||
-- None defined at present | -- None defined at present | ||
-- Chipsets may someday be | -- Chipsets may someday be | ||
-- defined here | -- defined here | ||
| − | |||
snmpFddiPHYMACChipSets -- Chips which implement both | snmpFddiPHYMACChipSets -- Chips which implement both | ||
-- the PHY and MAC functions | -- the PHY and MAC functions | ||
| + | |||
| + | |||
| Line 2,201: | Line 2,103: | ||
OBJECT IDENTIFIER ::= { snmpFddiChipSets 3 } | OBJECT IDENTIFIER ::= { snmpFddiChipSets 3 } | ||
| − | |||
-- None defined at present | -- None defined at present | ||
-- Chipsets may someday be | -- Chipsets may someday be | ||
-- defined here | -- defined here | ||
| − | |||
END | END | ||
| − | + | == Acknowledgements == | |
| − | == Acknowledgements == | ||
| − | |||
This document was produced by the IETF FDDI MIB working group: | This document was produced by the IETF FDDI MIB working group: | ||
| − | |||
Steve Adams, Digital Equipment Corporation | Steve Adams, Digital Equipment Corporation | ||
Hossein Alaee, 3Com Corporation | Hossein Alaee, 3Com Corporation | ||
| Line 2,248: | Line 2,145: | ||
Scott Hiles, U.S. Naval Surface Warfare Center | Scott Hiles, U.S. Naval Surface Warfare Center | ||
Greg Jones, Data General | Greg Jones, Data General | ||
| + | |||
| + | |||
| Line 2,301: | Line 2,200: | ||
Bert Williams, Synernetics | Bert Williams, Synernetics | ||
Mark Wood, AT&T Computer Systems | Mark Wood, AT&T Computer Systems | ||
| + | |||
| + | |||
| Line 2,309: | Line 2,210: | ||
Denis Yaro, Sun Microsystems | Denis Yaro, Sun Microsystems | ||
Jeff Young, Cray Research | Jeff Young, Cray Research | ||
| − | |||
The editor gratefully acknowledges the contributions of the editor of | The editor gratefully acknowledges the contributions of the editor of | ||
the ANSI X3T9.5 SMT document, Mary Jane Strohl of Hewlett | the ANSI X3T9.5 SMT document, Mary Jane Strohl of Hewlett | ||
Packard/Apollo, whose provision of that document in machine readable | Packard/Apollo, whose provision of that document in machine readable | ||
form saved much typing and avoided many data entry errors. | form saved much typing and avoided many data entry errors. | ||
| − | |||
The author gratefully acknowledges the labors of Dr. Marshall T. Rose | The author gratefully acknowledges the labors of Dr. Marshall T. Rose | ||
in assisting with converting this document to the new concise MIB | in assisting with converting this document to the new concise MIB | ||
format. | format. | ||
| + | == References == | ||
| + | [1] Rose M., and K. McCloghrie, "Structure and Identification of | ||
| + | Management Information for TCP/IP-based internets", RFC 1155, | ||
| + | Performance Systems International, Hughes LAN Systems, May 1990. | ||
| + | [2] McCloghrie K., and M. Rose, "Management Information Base for | ||
| + | Network Management of TCP/IP-based internets", RFC 1156, Hughes | ||
| + | LAN Systems, Performance Systems International, May 1990. | ||
| + | [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple | ||
| + | Network Management Protocol", RFC 1157, SNMP Research, | ||
| + | Performance Systems International, Performance Systems | ||
| + | International, MIT Laboratory for Computer Science, May 1990. | ||
| + | [4] McCloghrie K., and M. Rose, Editors, "Management Information Base | ||
| + | for Network Management of TCP/IP-based internets", RFC 1213, | ||
| + | Performance Systems International, March 1991. | ||
| + | [5] Information processing systems - Open Systems Interconnection - | ||
| + | Specification of Abstract Syntax Notation One (ASN.1), | ||
| + | International Organization for Standardization, International | ||
| + | Standard 8824, December 1987. | ||
| + | [6] Information processing systems - Open Systems Interconnection - | ||
| + | Specification of Basic Encoding Rules for Abstract Notation One | ||
| + | (ASN.1), International Organization for Standardization, | ||
| + | International Standard 8825, December 1987. | ||
| + | [7] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", | ||
| + | RFC 1212, Performance Systems International, Hughes LAN Systems, | ||
| + | March 1991. | ||
| + | [8] American National Standards Institute, "FDDI Station Management | ||
| + | (SMT)", Preliminary Draft Proposed American National Standard, | ||
| + | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | American National Standards Institute, X3T9/90-X3T9.5/84-49 REV | + | American National Standards Institute, X3T9/90-X3T9.5/84-49 REV |
| + | 6.2, May 18, 1990. | ||
Security Considerations | Security Considerations | ||
Security issues are not discussed in this memo. | Security issues are not discussed in this memo. | ||
Author's Address | Author's Address | ||
| − | Jeffrey D. | + | Jeffrey D. Case |
| + | SNMP Research, Incorporated | ||
| + | 3001 Kimberlin Heights Road | ||
| + | Knoxville, Tennessee 37920 | ||
Phone: (615) 573-1434 | Phone: (615) 573-1434 | ||
EMail: [email protected] | EMail: [email protected] | ||
Revision as of 00:53, 23 September 2020
Network Working Group J. Case Request for Comments: 1285 SNMP Research, Incorporated
January 1992
FDDI Management Information Base
Status of this Memo This memo is an extension to the SNMP MIB. This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Table of Contents 1. Abstract .............................................. 1 2. The Network Management Framework....................... 1 3. Objects ............................................... 2 3.1 Format of Definitions ................................ 2 4. Overview .............................................. 3 4.1 Textual Conventions .................................. 3 5. Object Definitions .................................... 4 5.1 The SMT Group ........................................ 5 5.2 The MAC Group ........................................ 15 5.3 The PATH Group ....................................... 27 5.4 The PORT Group ....................................... 27 5.5 The ATTACHMENT Group ................................. 38 5.6 The Chip Set Group ................................... 42 6. Acknowledgements ...................................... 43 7. References ............................................ 45 Security Considerations................................... 46 Author's Address.......................................... 46
Contents
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI.
The Network Management Framework
The Internet-standard Network Management Framework consists of three components. They are:
RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1156 which defines MIB-I, the core set of managed objects for the Internet suite of protocols. RFC 1213, defines MIB-II, an evolution of MIB-I based on implementation experience and new operational requirements. RFC 1157 which defines the SNMP, the protocol used for network access to managed objects.
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
Objects
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [5] defined in the SMI. In particular, each object has a name, a syntax, and an encoding. The name is an object identifier, an administratively assigned name, which specifies an object type. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the OBJECT DESCRIPTOR, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 language is used for this purpose. However, the SMI [1] purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The encoding of an object type is simply how that object type is represented using the object type's syntax. Implicitly tied to the notion of an object type's syntax and encoding is how the object type is represented when being transmitted on the network. The SMI specifies the use of the basic encoding rules of ASN.1 [6], subject to the additional requirements imposed by the SNMP. 3.1. Format of Definitions Section 5 contains contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions
specified in [7].
Overview
This document defines the managed objects for FDDI devices which are to be accessible via the Simple Network Management Protocol (SNMP). At present, this applies to these values of the ifType variable in the Internet-standard MIB:
fddi(15)
For these interfaces, the value of the ifSpecific variable in the MIB-II [4] has the OBJECT IDENTIFIER value:
fddi OBJECT IDENTIFIER ::= { transmission 15 }
The definitions of the objects presented here draws heavily from related work in the ANSI X3T9.5 committee and the SMT subcommittee of that committee [8]. In fact, the definitions of the managed objects in this document are, to the maximum extent possible, identical to those identified by the ANSI committee. The semantics of each managed object should be the same with syntactic changes made as necessary to recast the objects in terms of the Internet-standard SMI and MIB so as to be compatible with the SNMP. Examples of these syntactic changes include remapping booleans to enumerated integers, remapping bit strings to octet strings, and the like. In addition, the naming of the objects was changed to achieve compatibility. These minimal syntactic changes with no semantic changes should allow implementations of SNMP manageable FDDI systems to share instrumentation with other network management schemes and thereby minimize implementation cost. In addition, the translation of information conveyed by managed objects from one network management scheme to another is eased by these shared definitions. Only the essential variables, as indicated by their mandatory status in the ANSI specification were retained in this document. The importance of variables which have an optional status in the ANSI specification were perceived as being less widely accepted. 4.1. Textual Conventions Several new datatypes are introduced as a textual convention in this MIB document. These textual conventions enhance the readability of the document and ease comparisons with its ANSI counterpart. It should be noted that the introduction of the following textual conventions has no effect on either the syntax nor the semantics of any managed objects. The use of these is merely an artifact of the
explanatory method used. Objects defined in terms of one of these methods are always encoded by means of the rules that define the primitive type. Hence, no changes to the SMI or the SNMP are necessary to accommodate these textual conventions which are adopted merely for the convenience of readers and writers in pursuit of the elusive goal of clear, concise, and unambiguous MIB documents.
Object Definitions
RFC1285-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter
FROM RFC1155-SMI
transmission
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [7].
-- this is the FDDI MIB module
fddi OBJECT IDENTIFIER ::= { transmission 15 }
-- textual conventions
FddiTime ::= INTEGER (0..2147483647)
-- This data type specifies octet units of 80 nanoseconds as
-- an integer value. It is used for Path Latency and
-- Synchronous Bandwidth values. The encoding is normal
-- integer representation (not twos complement).
FddiResourceId ::= INTEGER (0..65535)
-- This data type is used to refer to an instance of a MAC,
-- PORT, PATH, or ATTACHMENT Resource ID. Indexing begins
-- at 1. Zero is used to indicate the absence of a resource.
FddiSMTStationIdType ::= OCTET STRING (SIZE (8))
-- The unique identifier for the FDDI station. This is a
-- string of 8 octets, represented as
-- X' yy yy xx xx xx xx xx xx'
-- with the low order 6 octet (xx) from a unique IEEE
-- assigned address. The high order two bits of the IEEE
-- address, the group address bit and the administration bit
-- (Universal/Local) bit should both be zero. The first two
-- octets, the yy octets, are implementor-defined.
--
-- The representation of the address portion of the station id
-- is in the IEEE (ANSI/IEEE P802.1A) canonical notation for
-- 48 bit addresses. The canonical form is a 6-octet string
-- where the first octet contains the first 8 bits of the
-- address, with the I/G(Individual/Group) address bit as the
-- least significant bit and the U/L (Universal/Local) bit
-- as the next more significant bit, and so on. Note that
-- addresses in the ANSI FDDI standard SMT frames are
-- represented in FDDI MAC order.
FddiMACLongAddressType ::= OCTET STRING (SIZE (6))
-- The representation of long MAC addresses as management
-- values is in the IEEE (ANSI/IEEE P802.1A) canonical
-- notation for 48 bit addresses. The canonical form is a
-- 6-octet string where the first octet contains the first 8
-- bits of the address, with the I/G (Individual/Group)
-- address bit as the least significant bit and the U/L
-- (Universal/Local) bit as the next more significant bit,
-- and so on. Note that the addresses in the SMT frames are
-- represented in FDDI MAC order.
-- groups in the FDDI MIB module
snmpFddiSMT OBJECT IDENTIFIER ::= { fddi 1 }
snmpFddiMAC OBJECT IDENTIFIER ::= { fddi 2 }
snmpFddiPATH OBJECT IDENTIFIER ::= { fddi 3 }
snmpFddiPORT OBJECT IDENTIFIER ::= { fddi 4 }
snmpFddiATTACHMENT OBJECT IDENTIFIER ::= { fddi 5 }
snmpFddiChipSets OBJECT IDENTIFIER ::= { fddi 6 }
-- the SMT group
-- Implementation of the SMT group is mandatory for all
-- systems which implement manageable FDDI subsystems.
snmpFddiSMTNumber OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of SMT implementations (regardless of
their current state) on this network management
application entity. The value for this variable
must remain constant at least from one re-
initialization of the entity's network management
system to the next re-initialization."
::= { snmpFddiSMT 1 }
-- the SMT table
snmpFddiSMTTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpFddiSMTEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of SMT entries. The number of entries is
given by the value of snmpFddiSMTNumber."
::= { snmpFddiSMT 2 }
snmpFddiSMTEntry OBJECT-TYPE
SYNTAX SnmpFddiSMTEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An SMT entry containing information common to a
given SMT."
INDEX { snmpFddiSMTIndex }
::= { snmpFddiSMTTable 1 }
SnmpFddiSMTEntry ::=
SEQUENCE {
snmpFddiSMTIndex
INTEGER,
snmpFddiSMTStationId
FddiSMTStationIdType,
snmpFddiSMTOpVersionId
INTEGER,
snmpFddiSMTHiVersionId
INTEGER,
snmpFddiSMTLoVersionId
INTEGER,
snmpFddiSMTMACCt
INTEGER,
snmpFddiSMTNonMasterCt
INTEGER,
snmpFddiSMTMasterCt
INTEGER,
snmpFddiSMTPathsAvailable
INTEGER,
snmpFddiSMTConfigCapabilities
INTEGER,
snmpFddiSMTConfigPolicy
INTEGER,
snmpFddiSMTConnectionPolicy
INTEGER,
snmpFddiSMTTNotify
INTEGER,
snmpFddiSMTStatusReporting
INTEGER,
snmpFddiSMTECMState
INTEGER,
snmpFddiSMTCFState
INTEGER,
snmpFddiSMTHoldState
INTEGER,
snmpFddiSMTRemoteDisconnectFlag
INTEGER,
snmpFddiSMTStationAction
INTEGER
}
snmpFddiSMTIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each SMT. Its value ranges
between 1 and the value of snmpFddiSMTNumber. The
value for each SMT must remain constant at least
from one re-initialization of the entity's network
management system to the next re-initialization."
::= { snmpFddiSMTEntry 1 }
snmpFddiSMTStationId OBJECT-TYPE
SYNTAX FddiSMTStationIdType -- OCTET STRING (SIZE (8))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Uniquely identifies an FDDI station."
REFERENCE
"ANSI { fddiSMT 11 }"
::= { snmpFddiSMTEntry 2 }
snmpFddiSMTOpVersionId OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The version that this station is using for its
operation (refer to ANSI 7.1.2.2)."
REFERENCE
"ANSI { fddiSMT 13 }"
::= { snmpFddiSMTEntry 3 }
snmpFddiSMTHiVersionId OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The highest version of SMT that this station
supports (refer to ANSI 7.1.2.2)."
REFERENCE
"ANSI { fddiSMT 14 }"
::= { snmpFddiSMTEntry 4 }
snmpFddiSMTLoVersionId OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The lowest version of SMT that this station
supports (refer to ANSI 7.1.2.2)."
REFERENCE
"ANSI { fddiSMT 15 }"
::= { snmpFddiSMTEntry 5 }
snmpFddiSMTMACCt OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of MACs in the station or
concentrator."
REFERENCE
"ANSI { fddiSMT 21 }"
::= { snmpFddiSMTEntry 6 }
snmpFddiSMTNonMasterCt OBJECT-TYPE
SYNTAX INTEGER (0..2)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Non Master PORTs (A, B, or S PORTs)
in the station or concentrator."
REFERENCE
"ANSI { fddiSMT 22 }"
::= { snmpFddiSMTEntry 7 }
snmpFddiSMTMasterCt OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Master PORTs in a node. If the
node is not a concentrator, the value is zero."
REFERENCE
"ANSI { fddiSMT 23 }"
::= { snmpFddiSMTEntry 8 }
snmpFddiSMTPathsAvailable OBJECT-TYPE
SYNTAX INTEGER (0..7)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that indicates the PATH types available
in the station.
The value is a sum. This value initially takes
the value zero, then for each type of PATH that
this node has available, 2 raised to a power is
added to the sum. The powers are according to the
following table:
Path Power
Primary 0
Secondary 1
Local 2
For example, a station having Primary and Local
PATHs available would have a value of 5 (2**0 +
2**2)."
REFERENCE
"ANSI { fddiSMT 24 }"
::= { snmpFddiSMTEntry 9 }
snmpFddiSMTConfigCapabilities OBJECT-TYPE
SYNTAX INTEGER (0..3)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that indicates capabilities that are
present in the node. If 'holdAvailable' is
present, this indicates support of the optional
Hold Function (refer to ANSI SMT 9.4.3.2). If
'CF-Wrap-AB' is present, this indicates that the
WRAP_AB state is forced.
The value is a sum. This value initially takes
the value zero, then for each of the configuration
policies currently enforced on the node, 2 raised
to a power is added to the sum. The powers are
according to the following table:
Policy Power
holdAvailable 0
CF-Wrap-AB 1 "
REFERENCE
"ANSI { fddiSMT 25 }"
::= { snmpFddiSMTEntry 10 }
snmpFddiSMTConfigPolicy OBJECT-TYPE
SYNTAX INTEGER (0..3)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that indicates the configuration policies
currently enforced in the node (refer to ANSI SMT
9.4.3.2). The 'configurationHold' policy refers
to the Hold flag, and should not be present only
if the Hold function is supported. The 'CF-Wrap-
AB' policy refers to the CF_Wrap_AB flag.
The value is a sum. This value initially takes
the value zero, then for each of the configuration
policies currently enforced on the node, 2 raised
to a power is added to the sum. The powers are
according to the following table:
Policy Power
configurationHold 0
CF-Wrap-AB 1 "
REFERENCE
"ANSI { fddiSMT 26 }"
::= { snmpFddiSMTEntry 11 }
snmpFddiSMTConnectionPolicy OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that indicates the connection policies
enforced at the station. A station sets the
corresponding policy for each of the connection
types that it rejects. The letter designations, X
and Y, in the 'rejectX-Y' names have the following
significance: X represents the PC-Type of the
local PORT and Y represents a PC-Neighbor in the
evaluation of Connection-Policy (PC-Type, PC-
Neighbor) that is done to determine the setting of
T-Val(3) in the PC-Signaling sequence (refer to
ANSI Section 9.6.3).
The value is a sum. This value initially takes
the value zero, then for each of the connection
policies currently enforced on the node, 2 raised
to a power is added to the sum. The powers are
according to the following table:
Policy Power
rejectA-A 0
rejectA-B 1
rejectA-S 2
rejectA-M 3
rejectB-A 4
rejectB-B 5
rejectB-S 6
rejectB-M 7
rejectS-A 8
rejectS-B 9
rejectS-S 10
rejectS-M 11
rejectM-A 12
rejectM-B 13
rejectM-S 14
rejectM-M 15
Implementors should note that the polarity of
these bits is different in different places in an
SMT system. Implementors should take appropriate
care."
REFERENCE
"ANSI { fddiSMT 27 }"
::= { snmpFddiSMTEntry 12 }
snmpFddiSMTTNotify OBJECT-TYPE
SYNTAX INTEGER (2..30)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The timer used in the Neighbor Notification
protocol, reported in seconds and ranging from 2
to 30 seconds (refer to ANSI SMT 8.3.1)."
REFERENCE
"ANSI { fddiSMT 29 }"
::= { snmpFddiSMTEntry 13 }
snmpFddiSMTStatusReporting OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the node implements the Status
Reporting Protocol. This object is included for
compatibility with products that were designed
prior to the adoption of this standard."
REFERENCE
"ANSI { fddiSMT 30 }"
::= { snmpFddiSMTEntry 14 }
snmpFddiSMTECMState OBJECT-TYPE
SYNTAX INTEGER {
ec0(1), -- Out
ec1(2), -- In
ec2(3), -- Trace
ec3(4), -- Leave
ec4(5), -- Path_Test
ec5(6), -- Insert
ec6(7), -- Check
ec7(8) -- Deinsert
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the current state of the ECM state
machine (refer to ANSI SMT 9.5.2)."
REFERENCE
"ANSI { fddiSMT 41 }"
::= { snmpFddiSMTEntry 15 }
snmpFddiSMTCFState OBJECT-TYPE
SYNTAX INTEGER {
cf0(1), -- Isolated
cf1(2), -- Wrap_S
cf2(3), -- Wrap_A
cf3(4), -- Wrap_B
cf4(5), -- Wrap_AB
cf5(6) -- Thru
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The attachment configuration for the station or
concentrator (refer to ANSI SMT 9.7.4.3)."
REFERENCE
"ANSI { fddiSMT 42 }"
::= { snmpFddiSMTEntry 16 }
snmpFddiSMTHoldState OBJECT-TYPE
SYNTAX INTEGER {
not-implemented(1), -- holding not implemented
not-holding(2),
holding-prm(3), -- holding on primary
holding-sec(4) -- holding on secondary
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This value indicates the current state of the
Hold function. The values are determined as
follows: 'holding-prm' is set if the primary ring
is operational and the Recovery Enable Flag is
clear (NOT NO_Flag(primary) AND NOT RE_Flag). is
set if the secondary ring is operational and the
Recovery Enable Flag is clear (NOT
NO_Flag(secondary) AND NOT RE_Flag). Ref 9.4.3.
and 10.3.1. the primary or secondary, i.e., the
Recovery Enable, RE_Flag, is set."
REFERENCE
"ANSI { fddiSMT 43 }"
::= { snmpFddiSMTEntry 17 }
snmpFddiSMTRemoteDisconnectFlag OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A flag indicating that the station was remotely
disconnected from the network. A station requires
a Connect Action (SM_CM_CONNECT.request (Connect))
to rejoin and clear the flag (refer to ANSI
6.4.5.2)."
REFERENCE
"ANSI { fddiSMT 44 }"
::= { snmpFddiSMTEntry 18 }
snmpFddiSMTStationAction OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- none of the following
connect(2),
disconnect(3),
path-Test(4),
self-Test(5)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object, when read, always returns a value of
other(1). The behavior of setting this variable
to each of the acceptable values is as follows:
Other: Results in a badValue error.
Connect: Generates an
SM_CM_Connect.request(connect) signal to CMT
indicating that the ECM State machine is to begin
a connection sequence. The
fddiSMTRemoteDisconnectFlag is cleared on the
setting of this variable to 1. See ANSI Ref
9.3.1.1.
Disconnect: Generates an
SM_CM_Connect.request(disconnect) signal to ECM
and sets the fddiSMTRemoteDisconnectFlag. See
ANSI Ref 9.3.1.1.
Path-Test: Initiates a station path test.
The Path_Test variable (See ANSI Ref. 9.4.1) is
set to Testing. The results of this action are
not specified in this standard.
Self-Test: Initiates a station self test.
The results of this action are not specified in
this standard.
Attempts to set this object to all other values
results in a badValue error. Agents may elect to
return a badValue error on attempts to set this
variable to path-Test(4) or self-Test(5)."
REFERENCE
"ANSI { fddiSMT 60 }"
::= { snmpFddiSMTEntry 19 }
-- the MAC group
-- Implementation of the MAC Group is mandatory for all
-- systems which implement manageable FDDI subsystems.
snmpFddiMACNumber OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of MAC implementations (across
all SMTs) on this network management application
entity. The value for this variable must remain
constant at least from one re-initialization of
the entity's network management system to the next
re-initialization."
::= { snmpFddiMAC 1 }
-- the MAC table
snmpFddiMACTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpFddiMACEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of MAC entries. The number of entries is
given by the value of snmpFddiMACNumber."
::= { snmpFddiMAC 2 }
snmpFddiMACEntry OBJECT-TYPE
SYNTAX SnmpFddiMACEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A MAC entry containing information common to a
given MAC."
INDEX { snmpFddiMACSMTIndex, snmpFddiMACIndex }
::= { snmpFddiMACTable 1 }
SnmpFddiMACEntry ::=
SEQUENCE {
snmpFddiMACSMTIndex
INTEGER,
snmpFddiMACIndex
INTEGER,
snmpFddiMACFrameStatusCapabilities
INTEGER,
snmpFddiMACTMaxGreatestLowerBound
FddiTime,
snmpFddiMACTVXGreatestLowerBound
FddiTime,
snmpFddiMACPathsAvailable
INTEGER,
snmpFddiMACCurrentPath
INTEGER,
snmpFddiMACUpstreamNbr
FddiMACLongAddressType,
snmpFddiMACOldUpstreamNbr
FddiMACLongAddressType,
snmpFddiMACDupAddrTest
INTEGER,
snmpFddiMACPathsRequested
INTEGER,
snmpFddiMACDownstreamPORTType
INTEGER,
snmpFddiMACSMTAddress
FddiMACLongAddressType,
snmpFddiMACTReq
FddiTime,
snmpFddiMACTNeg
FddiTime,
snmpFddiMACTMax
FddiTime,
snmpFddiMACTvxValue
FddiTime,
snmpFddiMACTMin
FddiTime,
snmpFddiMACCurrentFrameStatus
INTEGER,
snmpFddiMACFrameCts
Counter,
snmpFddiMACErrorCts
Counter,
snmpFddiMACLostCts
Counter,
snmpFddiMACFrameErrorThreshold
INTEGER,
snmpFddiMACFrameErrorRatio
INTEGER,
snmpFddiMACRMTState
INTEGER,
snmpFddiMACDaFlag
INTEGER,
snmpFddiMACUnaDaFlag
INTEGER,
snmpFddiMACFrameCondition
INTEGER,
snmpFddiMACChipSet
OBJECT IDENTIFIER,
snmpFddiMACAction
INTEGER
}
snmpFddiMACSMTIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the SMT index associated with this
MAC."
::= { snmpFddiMACEntry 1 }
snmpFddiMACIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each MAC on the managed
entity. The MAC identified by a particular value
of this index is that identified by the same value
of an ifIndex object instance. That is, if a MAC
is associated with the interface whose value of
ifIndex in the Internet-Standard MIB is equal to
5, then the value of snmpFddiMACIndex shall also
equal 5. The value for each MAC must remain
constant at least from one re-initialization of
the entity's network management system to the next
re-initialization."
::= { snmpFddiMACEntry 2 }
snmpFddiMACFrameStatusCapabilities OBJECT-TYPE
SYNTAX INTEGER (0..1799)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that indicates the MAC's bridge and end-
station capabilities for operating in a bridged
FDDI network.
The value is a sum. This value initially takes
the value zero, then for each capability present,
2 raised to a power is added to the sum. The
powers are according to the following table:
Capability Power
FSC-Type0 0
-- MAC repeats A/C indicators as received on
-- copying with the intent to forward.
FSC-Type1 1
-- MAC sets C but not A on copying for
-- forwarding.
FSC-Type2 2
-- MAC resets C and sets A on C set and
-- A reset if the frame is not copied and the
-- frame was addressed to this MAC
FSC-Type0-programmable 8
-- Type0 capability is programmable
FSC-Type1-programmable 9
-- Type1 capability is programmable
FSC-Type2-programmable 10
-- Type2 capability is programmable
"
REFERENCE
"ANSI { fddiMAC 11 }"
::= { snmpFddiMACEntry 3 }
snmpFddiMACTMaxGreatestLowerBound OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The greatest lower bound of T_Max supported for
this MAC."
REFERENCE
"ANSI { fddiMAC 13 }"
::= { snmpFddiMACEntry 4 }
snmpFddiMACTVXGreatestLowerBound OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The greatest lower bound of TVX supported for
this MAC."
REFERENCE
"ANSI { fddiMAC 14 }"
::= { snmpFddiMACEntry 5 }
snmpFddiMACPathsAvailable OBJECT-TYPE
SYNTAX INTEGER (0..7)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that indicates the PATH types available
for this MAC.
The value is a sum. This value initially takes
the value zero, then for each type of PATH that
this MAC has available, 2 raised to a power is
added to the sum. The powers are according to the
following table:
Path Power
Primary 0
Secondary 1
Local 2 "
REFERENCE
"ANSI { fddiMAC 22 }"
::= { snmpFddiMACEntry 6 }
snmpFddiMACCurrentPath OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
primary(2),
secondary(4),
local(8),
isolated(16)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the association of the MAC with a
station PATH."
REFERENCE
"ANSI { fddiMAC 23 }"
::= { snmpFddiMACEntry 7 }
snmpFddiMACUpstreamNbr OBJECT-TYPE
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The MAC's upstream neighbor's long individual MAC
address. It may be determined by the Neighbor
Information Frame protocol (refer to ANSI SMT
7.2.1). The value shall be reported as '00 00 00
00 00 00' if it is unknown."
REFERENCE
"ANSI { fddiMAC 24 }"
::= { snmpFddiMACEntry 8 }
snmpFddiMACOldUpstreamNbr OBJECT-TYPE
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The previous value of the MAC's upstream
neighbor's long individual MAC address. It may be
determined by the Neighbor Information Frame
protocol (refer to ANSI SMT 7.2.1). The value
shall be reported as '00 00 00 00 00 00' if it is
unknown."
REFERENCE
"ANSI { fddiMAC 26 }"
::= { snmpFddiMACEntry 9 }
snmpFddiMACDupAddrTest OBJECT-TYPE
SYNTAX INTEGER { none(1), pass(2), fail(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Duplicate Address Test flag, Dup_Addr_Test
(refer to ANSI 8.3.1)."
REFERENCE
"ANSI { fddiMAC 29 }"
::= { snmpFddiMACEntry 10 }
snmpFddiMACPathsRequested OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that indicates PATH(s) desired for this
MAC.
The value is a sum which represents the individual
PATHs that are desired. This value initially
takes the value zero, then for each type of PATH
that this node is, 2 raised to a power is added to
the sum. The powers are according to the
following table:
Path Power
Primary 0
Secondary 1
Local 2
Isolated 3
The precedence order is primary, secondary, local,
and then isolated if multiple PATHs are desired
are set."
REFERENCE
"ANSI { fddiMAC 32 }"
::= { snmpFddiMACEntry 11 }
snmpFddiMACDownstreamPORTType OBJECT-TYPE
SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the PC-Type of the first port that is
downstream of this MAC (the exit port)."
REFERENCE
"ANSI { fddiMAC 33 }"
::= { snmpFddiMACEntry 12 }
snmpFddiMACSMTAddress OBJECT-TYPE
SYNTAX FddiMACLongAddressType -- OCTET STRING (SIZE (6))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The 48 bit individual address of the MAC used for
SMT frames."
REFERENCE
"ANSI { fddiMAC 41 }"
::= { snmpFddiMACEntry 13 }
snmpFddiMACTReq OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The value of T-Req (refer to ANSI MAC 2.2.1 and
ANSI MAC 7.3.5.2)."
REFERENCE
"ANSI { fddiMAC 51 }"
::= { snmpFddiMACEntry 14 }
snmpFddiMACTNeg OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of T-Neg (refer to ANSI MAC 2.2.1 and
ANSI MAC 7.3.5.2)."
REFERENCE
"ANSI { fddiMAC 52 }"
::= { snmpFddiMACEntry 15 }
snmpFddiMACTMax OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of T-Max (refer to ANSI MAC 2.2.1 and
ANSI MAC 7.3.5.2)."
REFERENCE
"ANSI { fddiMAC 53 }"
::= { snmpFddiMACEntry 16 }
snmpFddiMACTvxValue OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of TvxValue (refer to ANSI MAC 2.2.1
and ANSI MAC 7.3.5.2)."
REFERENCE
"ANSI { fddiMAC 54 }"
::= { snmpFddiMACEntry 17 }
snmpFddiMACTMin OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of T-Min (refer to ANSI MAC 2.2.1 and
ANSI MAC 7.3.5.2)."
REFERENCE
"ANSI { fddiMAC 55 }"
::= { snmpFddiMACEntry 18 }
snmpFddiMACCurrentFrameStatus OBJECT-TYPE
SYNTAX INTEGER (0..7)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that indicates the MAC's operational
frame status setting functionality.
The value is a sum. This value initially takes
the value zero, then for each functionality
present, 2 raised to a power is added to the sum.
The powers are according to the following table:
Functionality Power
FSC-Type0 0
-- MAC repeats A/C indicators as received
FSC-Type1 1
-- MAC sets C but not A on copying for
-- forwarding
FSC-Type2 2
-- MAC resets C and sets A on C set and A
-- reset if frame is not copied
"
REFERENCE
"ANSI { fddiMAC 63 }"
::= { snmpFddiMACEntry 19 }
snmpFddiMACFrameCts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Frame_Ct (refer to ANSI MAC 2.2.1)."
REFERENCE
"ANSI { fddiMAC 71 }"
::= { snmpFddiMACEntry 20 }
snmpFddiMACErrorCts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Error_Ct (refer to ANSI MAC 2.2.1)."
REFERENCE
"ANSI { fddiMAC 81 }"
::= { snmpFddiMACEntry 21 }
snmpFddiMACLostCts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Lost_Ct (refer to ANSI MAC 2.2.1)."
REFERENCE
"ANSI { fddiMAC 82 }"
::= { snmpFddiMACEntry 22 }
snmpFddiMACFrameErrorThreshold OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A threshold for determining when a MAC Condition
report should be generated. The condition is true
when the ratio, ((delta snmpFddiMACLostCt + delta
snmpFddiMACErrorCt) / (delta snmpFddiMACFrameCt +
delta snmpFddiMACLostCt)) x 2**16. exceeds the
threshold. It is used to determine when a station
has an unacceptable frame error threshold. The
sampling algorithm is implementation dependent.
Any attempt to set this variable to a value of
less than one shall result in a badValue error.
Those who are familiar with the SNMP management
framework will recognize that thresholds are not
in keeping with the SNMP philosophy. However,
this variable is supported by underlying SMT
implementations already and maintaining this
threshold should not pose an undue additional
burden on SNMP agent implementors."
REFERENCE
"ANSI { fddiMAC 95 }"
::= { snmpFddiMACEntry 23 }
snmpFddiMACFrameErrorRatio OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This attribute is the actual ratio, ((delta
snmpFddiMACLostCt + delta snmpFddiMACErrorCt) /
(delta snmpFddiMACFrameCt + delta
snmpFddiMACLostCt)) x 2**16."
REFERENCE
"ANSI { fddiMAC 96 }"
::= { snmpFddiMACEntry 24 }
snmpFddiMACRMTState OBJECT-TYPE
SYNTAX INTEGER {
rm0(1), -- Isolated
rm1(2), -- Non_Op
rm2(3), -- Ring_Op
rm3(4), -- Detect
rm4(5), -- Non_Op_Dup
rm5(6), -- Ring_Op_Dup
rm6(7), -- Directed
rm7(8) -- Trace
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the current state of the Ring
Management state machine (refer to ANSI Section
10)."
REFERENCE
"ANSI { fddiMAC 111 }"
::= { snmpFddiMACEntry 25 }
snmpFddiMACDaFlag OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The RMT flag Duplicate Address Flag, DA_Flag
(refer to ANSI 10.3.1.2)."
REFERENCE
"ANSI { fddiMAC 112 }"
::= { snmpFddiMACEntry 26 }
snmpFddiMACUnaDaFlag OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A flag set when the upstream neighbor reports a
duplicate address condition. Reset when the
condition clears."
REFERENCE
"ANSI { fddiMAC 113 }"
::= { snmpFddiMACEntry 27 }
snmpFddiMACFrameCondition OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the MAC Condition is active when set.
Cleared when the condition clears and on power
up."
REFERENCE
"ANSI { fddiMAC 114 }"
::= { snmpFddiMACEntry 28 }
snmpFddiMACChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object identifies the hardware chip(s) which
is (are) principally responsible for the
implementation of the MAC function. A few OBJECT
IDENTIFIERS are identified elsewhere in this memo.
For those The assignment of additional OBJECT
IDENTIFIERs to various types of hardware chip sets
is managed by the IANA. For example, vendors
whose chip sets are not defined in this memo may
request a number from the Internet Assigned
Numbers Authority (IANA) which indicates the
assignment of a enterprise specific subtree which,
among other things, may be used to allocate OBJECT
IDENTIFIER assignments for that enterprise's chip
sets. Similarly, in the absence of an
appropriately assigned OBJECT IDENTIFIER in this
memo or in an enterprise specific subtree of a
chip vendor, a board or system vendor can request
a number for a subtree from the IANA and make an
appropriate assignment. It is desired that,
whenever possible, the same OBJECT IDENTIFIER be
used for all chips of a given type. Consequently,
the assignment made in this memo for a chip, if
any, should be used in preference to any other
assignment and the assignment made by the chip
manufacturer, if any, should be used in preference
to assignments made by users of those chips. If
the hardware chip set is unknown, the object
identifier
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownChipSet is a
syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER
must be able to generate and recognize this
value."
::= { snmpFddiMACEntry 29 }
snmpFddiMACAction OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- none of the following
enableLLCService(2),
disableLLCService(3),
connectMAC(4),
disconnectMAC(5)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object, when read, always returns a value of
other(1). The behavior of setting this variable
to each of the acceptable values is as follows:
Other: Results in a badValue
error.
enableLLCService: enables MAC service to
higher layers.
disableLLCService: disables MAC service to
higher layers.
connectMAC: connect this MAC in
station.
disconnectMAC: disconnect this MAC in
station.
Attempts to set this object to all other values
results in a badValue error."
REFERENCE
"ANSI { fddiMAC 130 }"
::= { snmpFddiMACEntry 30 }
-- the PATH group
-- the PATH group is empty for now and shall remain so until
-- the ANSI community sorts out their PATH group
-- the PORT group
-- Implementation of the PORT group is mandatory for all
-- systems which implement manageable FDDI subsystems.
snmpFddiPORTNumber OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of PORT implementations (across
all SMTs) on this network management application
entity. The value for this variable must remain
constant at least from one re-initialization of
the entity's network management system to the next
re-initialization."
::= { snmpFddiPORT 1 }
-- the PORT table
snmpFddiPORTTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpFddiPORTEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of PORT entries. The number of entries is
given by the value of snmpFddiPORTNumber."
::= { snmpFddiPORT 2 }
snmpFddiPORTEntry OBJECT-TYPE
SYNTAX SnmpFddiPORTEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A PORT entry containing information common to a
given PORT."
INDEX { snmpFddiPORTSMTIndex, snmpFddiPORTIndex }
::= { snmpFddiPORTTable 1 }
SnmpFddiPORTEntry ::=
SEQUENCE {
snmpFddiPORTSMTIndex
INTEGER,
snmpFddiPORTIndex
INTEGER,
snmpFddiPORTPCType
INTEGER,
snmpFddiPORTPCNeighbor
INTEGER,
snmpFddiPORTConnectionPolicies
INTEGER,
snmpFddiPORTRemoteMACIndicated
INTEGER,
snmpFddiPORTCEState
INTEGER,
snmpFddiPORTPathsRequested
INTEGER,
snmpFddiPORTMACPlacement
FddiResourceId,
snmpFddiPORTAvailablePaths
INTEGER,
snmpFddiPORTMACLoopTime
FddiTime,
snmpFddiPORTTBMax
FddiTime,
snmpFddiPORTBSFlag
INTEGER,
snmpFddiPORTLCTFailCts
Counter,
snmpFddiPORTLerEstimate
INTEGER,
snmpFddiPORTLemRejectCts
Counter,
snmpFddiPORTLemCts
Counter,
snmpFddiPORTLerCutoff
INTEGER,
snmpFddiPORTLerAlarm
INTEGER,
snmpFddiPORTConnectState
INTEGER,
snmpFddiPORTPCMState
INTEGER,
snmpFddiPORTPCWithhold
INTEGER,
snmpFddiPORTLerCondition
INTEGER,
snmpFddiPORTChipSet
OBJECT IDENTIFIER,
snmpFddiPORTAction
INTEGER
}
snmpFddiPORTSMTIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the SMT index associated with this
PORT."
::= { snmpFddiPORTEntry 1 }
snmpFddiPORTIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each PORT within a given SMT.
Its value ranges between 1 and the sum of the
values of snmpFddiSMTNonMasterCt
{ snmpFddiSMTEntry 6 } and snmpFddiSMTMasterCt
{ snmpFddiSMTEntry 7 } on the given SMT. The
value for each PORT must remain constant at least
from one re-initialization of the entity's network
management system to the next re-initialization."
::= { snmpFddiPORTEntry 2 }
snmpFddiPORTPCType OBJECT-TYPE
SYNTAX INTEGER { a(1), b(2), s(3), m(4) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"PC_Type (refer to ANSI SMT 9.2.2 and ANSI SMT
9.6.3.2)."
REFERENCE
"ANSI { fddiPORT 12 }"
::= { snmpFddiPORTEntry 3 }
snmpFddiPORTPCNeighbor OBJECT-TYPE
SYNTAX INTEGER { a(1), b(2), s(3), m(4), unknown(5) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type (PC_Neighbor) of the remote PORT that is
determined in PC_Signaling in R_Val (1,2) (refer
to ANSI SMT 9.6.3.2)."
REFERENCE
"ANSI { fddiPORT 13 }"
::= { snmpFddiPORTEntry 4 }
snmpFddiPORTConnectionPolicies OBJECT-TYPE
SYNTAX INTEGER (0..7)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that indicates the node's PORT policies.
Pc-MAC-LCT, Pc-MAC-Loop, and Pc-MAC-Placement
indicate how the respective PC Signaling
Capability flags should be set (refer to ANSI SMT
9.4.3.2).
The value is a sum. This value initially takes
the value zero, then for each PORT policy, 2
raised to a power is added to the sum. The powers
are according to the following table:
Policy Power
Pc-MAC-LCT 0
Pc-MAC-Loop 1
Pc-MAC-Placement 2 "
REFERENCE
"ANSI { fddiPORT 14 }"
::= { snmpFddiPORTEntry 5 }
snmpFddiPORTRemoteMACIndicated OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The indication, in PC-Signaling that the remote
partner intends to place a MAC in the output token
PATH of this PORT. Signaled as R_Val (9) (refer
to ANSI SMT 9.6.3.2)."
REFERENCE
"ANSI { fddiPORT 15 }"
::= { snmpFddiPORTEntry 6 }
snmpFddiPORTCEState OBJECT-TYPE
SYNTAX INTEGER {
ce0(1), -- Isolated
ce1(2), -- Insert_P
ce2(3), -- Insert_S
ce3(4), -- Insert_X
ce4(5) -- Local
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the current state of PORT's
Configuration Element (CE) (refer to ANSI 9.7.5).
Note that this value represents the Current Path
information for this PORT."
REFERENCE
"ANSI { fddiPORT 16 }"
::= { snmpFddiPORTEntry 7 }
snmpFddiPORTPathsRequested OBJECT-TYPE
SYNTAX INTEGER (0..15)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that indicates the desired association(s)
of the port with a station PATH. The 'Primary'
Path is the default. The value of 'Secondary' is
only meaningful for S (slave) or M (master) PORT
PC-Types. This value effects the setting of the
CF_Insert_S, and CF_Insert_L flags (refer to ANSI
Section 9.4.3). If the 'Primary' PATH is present,
then the Primary PATH (the default PATH) is
selected. If the 'Secondary' PATH is present and
the 'Primary' PATH is not present, then the
CF_Insert_S flag is set. If the 'Local' PATH is
sent and neither the 'Primary' or 'Secondary'
PATHs are sent, then the CF_Insert_L flag is set.
The value is a sum. This value initially takes
the value zero, then for each type of PATH
desired, 2 raised to a power is added to the sum.
The powers are according to the following table:
Path Power
Primary 0
Secondary 1
Local 2
Isolated 3 "
REFERENCE
"ANSI { fddiPORT 17 }"
::= { snmpFddiPORTEntry 8 }
snmpFddiPORTMACPlacement OBJECT-TYPE
SYNTAX FddiResourceId -- INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the upstream MAC, if any, that is
associated with the PORT. The value shall be zero
if there is no MAC associated with the PORT.
Otherwise, the value shall be equal to the value
of snmpFddiMACIndex associated with the MAC."
REFERENCE
"ANSI { fddiPORT 18 }"
::= { snmpFddiPORTEntry 9 }
snmpFddiPORTAvailablePaths OBJECT-TYPE
SYNTAX INTEGER (0..7)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that indicates the PATH types available
for M and S PORTs.
The value is a sum. This value initially takes
the value zero, then for each type of PATH that
this port has available, 2 raised to a power is
added to the sum. The powers are according to the
following table:
Path Power
Primary 0
Secondary 1
Local 2 "
REFERENCE
"ANSI { fddiPORT 19 }"
::= { snmpFddiPORTEntry 10 }
snmpFddiPORTMACLoopTime OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Time for the optional MAC Local Loop, T_Next(9),
which is greater-than or equal-to 200 milliseconds
(refer to ANSI SMT 9.4.4.2.3)."
REFERENCE
"ANSI { fddiPORT 21 }"
::= { snmpFddiPORTEntry 11 }
snmpFddiPORTTBMax OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-write
STATUS mandatory
DESCRIPTION
"TB_Max (refer to ANSI SMT 9.4.4.2.1)."
REFERENCE
"ANSI { fddiPORT 32 }"
::= { snmpFddiPORTEntry 12 }
snmpFddiPORTBSFlag OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Break State, BS_Flag (refer to ANSI SMT
9.4.3.4)."
REFERENCE
"ANSI { fddiPORT 33 }"
::= { snmpFddiPORTEntry 13 }
snmpFddiPORTLCTFailCts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The count of the consecutive times the link
confidence test (LCT) has failed during connection
management (refer to ANSI 9.4.1)."
REFERENCE
"ANSI { fddiPORT 42 }"
::= { snmpFddiPORTEntry 14 }
snmpFddiPORTLerEstimate OBJECT-TYPE
SYNTAX INTEGER (4..15)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A long term average link error rate. It ranges
from 10**-4 to 10**-15 and is reported as the
absolute value of the exponent of the estimate."
REFERENCE
"ANSI { fddiPORT 51 }"
::= { snmpFddiPORTEntry 15 }
snmpFddiPORTLemRejectCts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A link error monitoring count of the times that a
link has been rejected."
REFERENCE
"ANSI { fddiPORT 52 }"
::= { snmpFddiPORTEntry 16 }
snmpFddiPORTLemCts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The aggregate link error monitor error count, set
to zero only on station power_up."
REFERENCE
"ANSI { fddiPORT 53 }"
::= { snmpFddiPORTEntry 17 }
snmpFddiPORTLerCutoff OBJECT-TYPE
SYNTAX INTEGER (4..15)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The link error rate estimate at which a link
connection will be broken. It ranges from 10**-4
to 10**-15 and is reported as the absolute value
of the exponent."
REFERENCE
"ANSI { fddiPORT 58 }"
::= { snmpFddiPORTEntry 18 }
snmpFddiPORTLerAlarm OBJECT-TYPE
SYNTAX INTEGER (4..15)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The link error rate estimate at which a link
connection will generate an alarm. It ranges from
10**-4 to 10**-15 and is reported as the absolute
value of the exponent of the estimate."
REFERENCE
"ANSI { fddiPORT 59 }"
::= { snmpFddiPORTEntry 19 }
snmpFddiPORTConnectState OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
connecting(2),
standby(3),
active(4)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An indication of the connect state of this PORT.
Basically, this gives a higher level view of the
state of the connection by grouping PCM states and
the PC-Withhold flag state. The supported values
and their corresponding PCM states and PC-Withhold
condition, when relevant, are:
disabled: (PC0:Off, PC9:Maint)
connecting: (PC1(Break) || PC3 (Connect) || PC4
(Next) || PC5 (Signal) || PC6
(Join) || PC7 (Verify)) &&
(PC_Withhold = None)
standby: (NOT PC_Withhold == None)
active: (PC2:Trace || PC8:Active) "
REFERENCE
"ANSI { fddiPORT 61 }"
::= { snmpFddiPORTEntry 20 }
snmpFddiPORTPCMState OBJECT-TYPE
SYNTAX INTEGER {
pc0(1), -- Off
pc1(2), -- Break
pc2(3), -- Trace
pc3(4), -- Connect
pc4(5), -- Next
pc5(6), -- Signal
pc6(7), -- Join
pc7(8), -- Verify
pc8(9), -- Active
pc9(10) -- Maint
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"(refer to SMT 9.6.2)."
REFERENCE
"ANSI { fddiPORT 62 }"
::= { snmpFddiPORTEntry 21 }
snmpFddiPORTPCWithhold OBJECT-TYPE
SYNTAX INTEGER { none(1), m-m(2), other(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"PC_Withhold, (refer to ANSI SMT 9.4.1)."
REFERENCE
"ANSI { fddiPORT 63 }"
::= { snmpFddiPORTEntry 22 }
snmpFddiPORTLerCondition OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This variable is set to true whenever LerEstimate
is less than or equal to LerAlarm."
REFERENCE
"ANSI { fddiPORT 64 }"
::= { snmpFddiPORTEntry 23 }
snmpFddiPORTChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object identifies the hardware chip(s) which
is (are) principally responsible for the
implementation of the PORT (PHY) function. A few
OBJECT IDENTIFIERS are identified elsewhere in
this memo. For those The assignment of additional
OBJECT IDENTIFIERs to various types of hardware
chip sets is managed by the IANA. For example,
vendors whose chip sets are not defined in this
memo may request a number from the Internet
Assigned Numbers Authority (IANA) which indicates
the assignment of a enterprise specific subtree
which, among other things, may be used to allocate
OBJECT IDENTIFIER assignments for that
enterprise's chip sets. Similarly, in the absence
of an appropriately assigned OBJECT IDENTIFIER in
this memo or in an enterprise specific subtree of
a chip vendor, a board or system vendor can
request a number for a subtree from the IANA and
make an appropriate assignment. It is desired
that, whenever possible, the same OBJECT
IDENTIFIER be used for all chips of a given type.
Consequently, the assignment made in this memo for
a chip, if any, should be used in preference to
any other assignment and the assignment made by
the chip manufacturer, if any, should be used in
preference to assignments made by users of those
chips. If the hardware chip set is unknown, the
object identifier
unknownChipSet OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownChipSet is a
syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER
must be able to generate and recognize this
value."
::= { snmpFddiPORTEntry 24 }
snmpFddiPORTAction OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- none of the following
maintPORT(2),
enablePORT(3),
disablePORT(4),
startPORT(5),
stopPORT(6)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This object, when read, always returns a value of
other(1). The behavior of setting this variable
to each of the acceptable values is as follows:
Other: Results in a badValue error.
maintPORT: Signal PC_Maint
enablePORT: Signal PC_Enable
disablePORT: Signal PC_Disable
startPORT: Signal PC_Start
stopPORT: Signal PC_Stop
Signals cause an SM_CM_CONTROL.request service to
be generated with a control_action of `Signal' and
the `variable' parameter set with the appropriate
value (i.e., PC_Maint, PC_Enable, PC_Disable,
PC_Start, PC_Stop). Ref. ANSI SMT Section 9.3.2.
Attempts to set this object to all other values
results in a badValue error."
REFERENCE
"ANSI { fddiPORT 70 }"
::= { snmpFddiPORTEntry 25 }
-- the ATTACHMENT group
-- Implementation of the ATTACHMENT group is mandatory for
-- all systems which implement manageable FDDI subsystems.
snmpFddiATTACHMENTNumber OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of attachments (across all SMTs)
on this network management application entity.
The value for this variable must remain constant
at least from one re-initialization of the
entity's network management system to the next
re-initialization."
::= { snmpFddiATTACHMENT 1 }
-- the ATTACHMENT table
snmpFddiATTACHMENTTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpFddiATTACHMENTEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of ATTACHMENT entries. The number of
entries is given by the value of
snmpFddiATTACHMENTNumber."
::= { snmpFddiATTACHMENT 2 }
snmpFddiATTACHMENTEntry OBJECT-TYPE
SYNTAX SnmpFddiATTACHMENTEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An ATTACHMENT entry containing information common
to a given set of ATTACHMENTs.
The ATTACHMENT Resource represents a PORT or a
pair of PORTs plus the optional associated optical
bypass that are managed as a functional unit.
Because of its relationship to the PORT Objects,
there is a natural association of ATTACHMENT
Resource Indices to the PORT Indices. The
resource index for the ATTACHMENT is equal to the
associated PORT index for 'single-attachment' and
'concentrator' type snmpFddiATTACHMENTClasses.
For 'dual-attachment' Classes, the ATTACHMENT
Index is the PORT Index of the A PORT of the A/B
PORT Pair that represents the ATTACHMENT."
INDEX { snmpFddiATTACHMENTSMTIndex,
snmpFddiATTACHMENTIndex }
::= { snmpFddiATTACHMENTTable 1 }
SnmpFddiATTACHMENTEntry ::=
SEQUENCE {
snmpFddiATTACHMENTSMTIndex
INTEGER,
snmpFddiATTACHMENTIndex
INTEGER,
snmpFddiATTACHMENTClass
INTEGER,
snmpFddiATTACHMENTOpticalBypassPresent
INTEGER,
snmpFddiATTACHMENTIMaxExpiration
FddiTime,
snmpFddiATTACHMENTInsertedStatus
INTEGER,
snmpFddiATTACHMENTInsertPolicy
INTEGER
}
snmpFddiATTACHMENTSMTIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the SMT index associated with this
ATTACHMENT."
::= { snmpFddiATTACHMENTEntry 1 }
snmpFddiATTACHMENTIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each ATTACHMENT on a given
SMT. Its value ranges between 1 and the sum of
the values of snmpFddiSMTNonMasterCt {
snmpFddiSMTEntry 6 } and snmpFddiSMTMasterCt {
snmpFddiSMTEntry 7 } on the given SMT. The value
for each ATTACHMENT must remain constant at least
from one re-initialization of the entity's network
management system to the next re-initialization."
::= { snmpFddiATTACHMENTEntry 2 }
snmpFddiATTACHMENTClass OBJECT-TYPE
SYNTAX INTEGER {
single-attachment(1),
dual-attachment(2),
concentrator(3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Attachment class. This represents a PORT or
a pair of PORTs plus the associated optional
optical bypass that are managed as a functional
unit. The PORT associations are the following:
single-attachment - S PORTs
dual-attachment - A/B PORT Pairs
concentrator - M PORTs "
REFERENCE
"ANSI { fddiATTACHMENT 11 }"
::= { snmpFddiATTACHMENTEntry 3 }
snmpFddiATTACHMENTOpticalBypassPresent OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this value is false for 'single-
attachment' and { snmpFddiATTACHMENT 11 }.
Correct operation of CMT for single-attachment and
concentrator attachments requires that a bypass
function must not loopback the network side of the
MIC, but only the node side."
REFERENCE
"ANSI { fddiATTACHMENT 12 }"
::= { snmpFddiATTACHMENTEntry 4 }
snmpFddiATTACHMENTIMaxExpiration OBJECT-TYPE
SYNTAX FddiTime
ACCESS read-only
STATUS mandatory
DESCRIPTION
"I_Max (refer to ANSI SMT 9.4.4.2.1). It is
recognized that some currently deployed systems do
not implement an optical bypass. Systems which do
not implement optical bypass should return a value
of 0."
REFERENCE
"ANSI { fddiATTACHMENT 13 }"
::= { snmpFddiATTACHMENTEntry 5 }
snmpFddiATTACHMENTInsertedStatus OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2), unimplemented(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the attachment is currently
inserted in the node."
REFERENCE
"ANSI { fddiATTACHMENT 14 }"
::= { snmpFddiATTACHMENTEntry 6 }
snmpFddiATTACHMENTInsertPolicy OBJECT-TYPE
SYNTAX INTEGER { true(1), false(2), unimplemented(3) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates the Insert Policy for this Attachment.
Insert: True (1), Don't Insert: False (2),
Unimplemented (3)"
REFERENCE
"ANSI { fddiATTACHMENT 15 }"
::= { snmpFddiATTACHMENTEntry 7 }
-- the Chip Set group
-- The following object identifiers are allocated for use
-- with the snmpFddiMACChipSet and snmpFddiPORTChipSet
-- variables.
snmpFddiPHYChipSets -- Chips primarily responsible
-- for implementing the PHY
-- function.
OBJECT IDENTIFIER ::= { snmpFddiChipSets 1 }
-- None defined at present
-- Chipsets may someday be
-- defined here
snmpFddiMACChipSets -- Chips primarily responsible
-- for implementing the
-- MAC function.
OBJECT IDENTIFIER ::= { snmpFddiChipSets 2 }
-- None defined at present
-- Chipsets may someday be
-- defined here
snmpFddiPHYMACChipSets -- Chips which implement both
-- the PHY and MAC functions
OBJECT IDENTIFIER ::= { snmpFddiChipSets 3 }
-- None defined at present
-- Chipsets may someday be
-- defined here
END
Acknowledgements
This document was produced by the IETF FDDI MIB working group:
Steve Adams, Digital Equipment Corporation
Hossein Alaee, 3Com Corporation
Haggar Alsaleh, Bell Northern Research
William Anderson, Mitre Corporation
Alan Apt, Addison-Wesley
Mary Artibee, Silicon Graphics
Karen Auerbach, Epilogue Technologies
Doug Bagnall, Apollo/Hewlett Packard
Chet Birger, Coral Network Corporation
Pablo Brenner, Sparta
Howard Brown, Cabletron
Jack Brown, US Army Computer Engineering Center
Eric Brunner
Jeff Case, The University of Tennessee
Tammy Chan, Fibercom
Asheem Chandna, AT&T
Cho Y. Chang, Apollo/Hewlett Packard
Chris Chiotasso, Fibronics
Paul Ciarfella, Digital Equipment Corporation
John Cook, Chipcom
Don Coolidge, Silicon Graphics
Burt Cyr, Unisys
James R. Davin, Massachusetts Institute of Technology
Nabil Damouny
Nadya El-Afandi, Network Systems Corporation
Hunaid Engineer, Cray Research
Jeff Fitzgerald, Fibercom
Richard Fox, Synoptics
Stan Froyd, ACC
Debbie Futcher, U.S. Naval Surface Warfare Center
Joseph Golio, Cray Research
Jeremy Greene, Coral
Brian D. Handspicker, Digital Equipment Corporation
Peter Hayden, Digital Equipment Corporation
Scott Hiles, U.S. Naval Surface Warfare Center
Greg Jones, Data General
Satish Joshi, SynOptics Communications
Jayant Kadambi, AT&T Bell Labs
Joanna Karwowska, Data General
Frank Kastenholz, Interlan
Jim Kinder, Fibercom
Christopher Kolb, PSI
Cheryl Krupczak, NCR
Peter Lin, Vitalink
Then Liu
John R. LoVerso, Concurrent Computer Corporation
Ron Mackey
Gary Malkin, Proteon
Bruce McClure, Synernetics
Keith McCloghrie, Hughes Lan Systems
Donna McMaster, SynOptics
John O'Hara, Massachusetts Institute of Technology
Dave Perkins, SynOptics Communications
James E. Reeves, SynOptics Communications
Jim Reinstedler, Ungermann-Bass
Radhi Renous, Fibronics
Anil Rijsinghani, Digital Equipment Corporation
Bob Rolla, Synernetics
Nelson Ronkin, Synernetics
Marshall T. Rose, Performance Systems International, Inc.
Milt Roselinsky, CMC
Jon Saperia, Digital Equipment Corporation
Greg Satz, cisco Systems
Steven Senum, Network Systems Corporation
Jim Sheridan, IBM Corporation
Jeffrey Schiller, MIT
Dror Shindelman, Sparta
Mark Sleeper, Sparta
Craig Smelser, Digital Equipment Corporation
Lou Steinberg, IBM Corporation
Mary Jane Strohl, Apollo/Hewlett Packard
Sally Tarquinio, Mitre Corporation
Kaj Tesink, Bellcore
Ian Thomas, Chipcom
Dean Throop, Data General
Bill Townsend, Xylogics
Ahmet H. Tuncay, SynOptics Communications
Mike Turico, Motorola
Chris VandenBerg, ACC
Sudhanshu Verma, Hewlett Packard
Joe Vermeulen, UNISYS
David Waiteman, BBN
Bert Williams, Synernetics
Mark Wood, AT&T Computer Systems
Y. C. Yang
Denis Yaro, Sun Microsystems
Jeff Young, Cray Research
The editor gratefully acknowledges the contributions of the editor of the ANSI X3T9.5 SMT document, Mary Jane Strohl of Hewlett Packard/Apollo, whose provision of that document in machine readable form saved much typing and avoided many data entry errors. The author gratefully acknowledges the labors of Dr. Marshall T. Rose in assisting with converting this document to the new concise MIB format.
References
[1] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990.
[2] McCloghrie K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets", RFC 1156, Hughes LAN Systems, Performance Systems International, May 1990.
[3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990.
[4] McCloghrie K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets", RFC 1213, Performance Systems International, March 1991.
[5] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987.
[6] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987.
[7] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991.
[8] American National Standards Institute, "FDDI Station Management
(SMT)", Preliminary Draft Proposed American National Standard,
American National Standards Institute, X3T9/90-X3T9.5/84-49 REV 6.2, May 18, 1990.
Security Considerations Security issues are not discussed in this memo. Author's Address Jeffrey D. Case SNMP Research, Incorporated 3001 Kimberlin Heights Road Knoxville, Tennessee 37920 Phone: (615) 573-1434 EMail: [email protected]
