RFCs in HTML Format


RFC 1512

                    FDDI Management Information Base

Status of this Memo

   This RFC specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" for the standardization state and status
   of this protocol.  Distribution of this memo is unlimited.

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 based on the ANSI FDDI SMT 7.3 draft standard [8],
   which has been forwarded for publication by the X3T9.5 committee.

Table of Contents

   1. The Network Management Framework ......................    2
   1.1 Object Definitions ...................................    2
   1.2 Format of Definitions ................................    2
   2. Overview ..............................................    2
   2.1 Textual Conventions ..................................    3
   3. Changes from RFC 1285 .................................    3
   4. Object Definitions ....................................    4
   4.1 The SMT Group ........................................    6
   4.2 The MAC Group ........................................   17
   4.3 The Enhanced MAC Counters Group ......................   29
   4.4 The PATH Group .......................................   32
   4.5 The PORT Group .......................................   38
   5. Acknowledgements ......................................   48
   6. References ............................................   50
   7. Security Considerations ...............................   51
   8. Authors' Addresses ....................................   51








Case & Rijsinghani                                              [Page 1]

RFC 1512 FDDI MIB September 1993 1. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: o STD 16, RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. STD 16, RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. o STD 17, RFC 1213 defines MIB-II, the core set of managed objects for the Internet suite of protocols. o STD 15, 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. 1.1. Object Definitions 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) defined in the SMI. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. 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 descriptor, to refer to the object type. 1.2. Format of Definitions Section 4 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]. 2. 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 Case & Rijsinghani [Page 2]
RFC 1512 FDDI MIB September 1993 MIB-II [4] has the OBJECT IDENTIFIER value: fddimib OBJECT IDENTIFIER ::= { fddi 73 } 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. 2.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 these textual conventions has no effect on either the syntax or 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. 3. Changes from RFC 1285 The changes from RFC 1285 [2] to this document, based on changes from ANSI SMT 6.2 to SMT 7.3, were so numerous that the objects in this MIB module are located on a different branch of the MIB tree. No Case & Rijsinghani [Page 3]
RFC 1512 FDDI MIB September 1993 assumptions should be made about compatibility with RFC 1285. 4. Object Definitions FDDI-SMT73-MIB DEFINITIONS ::= BEGIN IMPORTS Counter FROM RFC1155-SMI 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 } fddimib OBJECT IDENTIFIER ::= { fddi 73 } -- textual conventions FddiTimeNano ::= INTEGER (0..2147483647) -- This data type specifies 1 nanosecond units as -- an integer value. -- -- NOTE: The encoding is normal integer representation, not -- two's complement. Since this type is used for variables -- which are encoded as TimerTwosComplement in the ANSI -- specification, two operations need to be performed on such -- variables to convert from ANSI form to SNMP form: -- -- 1) Convert from two's complement to normal integer -- representation -- 2) Multiply by 80 to convert from 80 nsec to 1 nsec units -- -- No resolution is lost. Moreover, the objects for which -- this data type is used effectively do not lose any range -- due to the lower maximum value since they do not require -- the full range. -- -- Example: If fddimibMACTReq had a value of 8 ms, it would -- be stored in ANSI TimerTwosComplement format as 0xFFFE7960 -- [8 ms is 100000 in 80 nsec units, which is then converted -- to two's complement] but be reported as 8000000 in SNMP -- since it is encoded here as FddiTimeNano. Case & Rijsinghani [Page 4]
RFC 1512 FDDI MIB September 1993 FddiTimeMilli ::= INTEGER (0..2147483647) -- This data type is used for some FDDI timers. It specifies -- time in 1 millisecond units, in normal integer -- representation. FddiResourceId ::= INTEGER (0..65535) -- This data type is used to refer to an instance of a MAC, -- PORT, or PATH 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 fddimibSMT OBJECT IDENTIFIER ::= { fddimib 1 } fddimibMAC OBJECT IDENTIFIER ::= { fddimib 2 } fddimibMACCounters OBJECT IDENTIFIER ::= { fddimib 3 } Case & Rijsinghani [Page 5]
RFC 1512 FDDI MIB September 1993 fddimibPATH OBJECT IDENTIFIER ::= { fddimib 4 } fddimibPORT OBJECT IDENTIFIER ::= { fddimib 5 } -- the SMT group -- Implementation of the SMT group is mandatory for all -- systems which implement manageable FDDI subsystems. fddimibSMTNumber 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." ::= { fddimibSMT 1 } -- the SMT table fddimibSMTTable OBJECT-TYPE SYNTAX SEQUENCE OF FddimibSMTEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of SMT entries. The number of entries shall not exceed the value of fddimibSMTNumber." ::= { fddimibSMT 2 } fddimibSMTEntry OBJECT-TYPE SYNTAX FddimibSMTEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An SMT entry containing information common to a given SMT." INDEX { fddimibSMTIndex } ::= { fddimibSMTTable 1 } FddimibSMTEntry ::= SEQUENCE { fddimibSMTIndex INTEGER, Case & Rijsinghani [Page 6]
RFC 1512 FDDI MIB September 1993 fddimibSMTStationId FddiSMTStationIdType, fddimibSMTOpVersionId INTEGER, fddimibSMTHiVersionId INTEGER, fddimibSMTLoVersionId INTEGER, fddimibSMTUserData OCTET STRING, fddimibSMTMIBVersionId INTEGER, fddimibSMTMACCts INTEGER, fddimibSMTNonMasterCts INTEGER, fddimibSMTMasterCts INTEGER, fddimibSMTAvailablePaths INTEGER, fddimibSMTConfigCapabilities INTEGER, fddimibSMTConfigPolicy INTEGER, fddimibSMTConnectionPolicy INTEGER, fddimibSMTTNotify INTEGER, fddimibSMTStatRptPolicy INTEGER, fddimibSMTTraceMaxExpiration FddiTimeMilli, fddimibSMTBypassPresent INTEGER, fddimibSMTECMState INTEGER, fddimibSMTCFState INTEGER, fddimibSMTRemoteDisconnectFlag INTEGER, fddimibSMTStationStatus INTEGER, fddimibSMTPeerWrapFlag INTEGER, fddimibSMTTimeStamp FddiTimeMilli, fddimibSMTTransitionTimeStamp FddiTimeMilli, Case & Rijsinghani [Page 7]
RFC 1512 FDDI MIB September 1993 fddimibSMTStationAction INTEGER } fddimibSMTIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "A unique value for each SMT. 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." ::= { fddimibSMTEntry 1 } fddimibSMTStationId OBJECT-TYPE SYNTAX FddiSMTStationIdType -- OCTET STRING (SIZE (8)) ACCESS read-only STATUS mandatory DESCRIPTION "Used to uniquely identify an FDDI station." REFERENCE "ANSI { fddiSMT 11 }" ::= { fddimibSMTEntry 2 } fddimibSMTOpVersionId OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The version that this station is using for its operation (refer to ANSI 7.1.2.2). The value of this variable is 2 for this SMT revision." REFERENCE "ANSI { fddiSMT 13 }" ::= { fddimibSMTEntry 3 } fddimibSMTHiVersionId 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 }" ::= { fddimibSMTEntry 4 } Case & Rijsinghani [Page 8]
RFC 1512 FDDI MIB September 1993 fddimibSMTLoVersionId 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 }" ::= { fddimibSMTEntry 5 } fddimibSMTUserData OBJECT-TYPE SYNTAX OCTET STRING (SIZE (32)) ACCESS read-write STATUS mandatory DESCRIPTION "This variable contains 32 octets of user defined information. The information shall be an ASCII string." REFERENCE "ANSI { fddiSMT 17 }" ::= { fddimibSMTEntry 6 } fddimibSMTMIBVersionId OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The version of the FDDI MIB of this station. The value of this variable is 1 for this SMT revision." REFERENCE "ANSI { fddiSMT 18 }" ::= { fddimibSMTEntry 7 } fddimibSMTMACCts OBJECT-TYPE SYNTAX INTEGER (0..255) ACCESS read-only STATUS mandatory DESCRIPTION "The number of MACs in this station or concentrator." REFERENCE "ANSI { fddiSMT 21 }" ::= { fddimibSMTEntry 8 } fddimibSMTNonMasterCts OBJECT-TYPE SYNTAX INTEGER (0..2) Case & Rijsinghani [Page 9]
RFC 1512 FDDI MIB September 1993 ACCESS read-only STATUS mandatory DESCRIPTION "The value of this variable is the number of A, B, and S ports in this station or concentrator." REFERENCE "ANSI { fddiSMT 22 }" ::= { fddimibSMTEntry 9 } fddimibSMTMasterCts OBJECT-TYPE SYNTAX INTEGER (0..255) ACCESS read-only STATUS mandatory DESCRIPTION "The number of M Ports in a node. If the node is not a concentrator, the value of the variable is zero." REFERENCE "ANSI { fddiSMT 23 }" ::= { fddimibSMTEntry 10 } fddimibSMTAvailablePaths 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 }" ::= { fddimibSMTEntry 11 } fddimibSMTConfigCapabilities OBJECT-TYPE Case & Rijsinghani [Page 10]
RFC 1512 FDDI MIB September 1993 SYNTAX INTEGER (0..3) ACCESS read-only STATUS mandatory DESCRIPTION "A value that indicates the configuration capabilities of a node. The 'Hold Available' bit indicates the support of the optional Hold Function, which is controlled by fddiSMTConfigPolicy. The 'CF-Wrap-AB' bit indicates that the station has the capability of performing a wrap_ab (refer to ANSI SMT 9.7.2.2). 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 }" ::= { fddimibSMTEntry 12 } fddimibSMTConfigPolicy OBJECT-TYPE SYNTAX INTEGER (0..1) ACCESS read-write STATUS mandatory DESCRIPTION "A value that indicates the configuration policies currently desired in a node. 'Hold' is one of the terms used for the Hold Flag, an optional ECM flag used to enable the optional Hold policy. 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 " REFERENCE "ANSI { fddiSMT 26 }" ::= { fddimibSMTEntry 13 } fddimibSMTConnectionPolicy OBJECT-TYPE Case & Rijsinghani [Page 11]
RFC 1512 FDDI MIB September 1993 SYNTAX INTEGER (32768..65535) ACCESS read-write STATUS mandatory DESCRIPTION "A value representing the connection policies in effect in a node. A station sets the corresponding bit 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 the PC_Type of the adjacent PORT (PC_Neighbor). The evaluation of Connection- Policy (PC-Type, PC-Neighbor) is done to determine the setting of T- Val(3) in the PC-Signalling sequence (refer to ANSI 9.6.3). Note that Bit 15, (rejectM-M), is always set and cannot be cleared. 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 " REFERENCE "ANSI { fddiSMT 27 }" ::= { fddimibSMTEntry 14 } fddimibSMTTNotify OBJECT-TYPE SYNTAX INTEGER (2..30) ACCESS read-write STATUS mandatory Case & Rijsinghani [Page 12]
RFC 1512 FDDI MIB September 1993 DESCRIPTION "The timer, expressed in seconds, used in the Neighbor Notification protocol. It has a range of 2 seconds to 30 seconds, and its default value is 30 seconds (refer to ANSI SMT 8.2)." REFERENCE "ANSI { fddiSMT 29 }" ::= { fddimibSMTEntry 15 } fddimibSMTStatRptPolicy OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "If true, indicates that the node will generate Status Reporting Frames for its implemented events and conditions. It has an initial value of true. This variable determines the value of the SR_Enable Flag (refer to ANSI SMT 8.3.2.1)." REFERENCE "ANSI { fddiSMT 30 }" ::= { fddimibSMTEntry 16 } fddimibSMTTraceMaxExpiration OBJECT-TYPE SYNTAX FddiTimeMilli ACCESS read-write STATUS mandatory DESCRIPTION "Reference Trace_Max (refer to ANSI SMT 9.4.4.2.2)." REFERENCE "ANSI { fddiSMT 31 }" ::= { fddimibSMTEntry 17 } fddimibSMTBypassPresent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "A flag indicating if the station has a bypass on its AB port pair." REFERENCE "ANSI { fddiSMT 34 }" ::= { fddimibSMTEntry 18 } fddimibSMTECMState OBJECT-TYPE SYNTAX INTEGER { ec0(1), -- Out Case & Rijsinghani [Page 13]
RFC 1512 FDDI MIB September 1993 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 }" ::= { fddimibSMTEntry 19 } fddimibSMTCFState OBJECT-TYPE SYNTAX INTEGER { cf0(1), -- isolated cf1(2), -- local_a cf2(3), -- local_b cf3(4), -- local_ab cf4(5), -- local_s cf5(6), -- wrap_a cf6(7), -- wrap_b cf7(8), -- wrap_ab cf8(9), -- wrap_s cf9(10), -- c_wrap_a cf10(11), -- c_wrap_b cf11(12), -- c_wrap_s cf12(13) -- thru } ACCESS read-only STATUS mandatory DESCRIPTION "The attachment configuration for the station or concentrator (refer to ANSI SMT 9.7.2.2)." REFERENCE "ANSI { fddiSMT 42 }" ::= { fddimibSMTEntry 20 } fddimibSMTRemoteDisconnectFlag OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "A flag indicating that the station was remotely Case & Rijsinghani [Page 14]
RFC 1512 FDDI MIB September 1993 disconnected from the network as a result of receiving an fddiSMTAction, disconnect (refer to ANSI SMT 6.4.5.3) in a Parameter Management Frame. A station requires a Connect Action to rejoin and clear the flag (refer to ANSI SMT 6.4.5.2)." REFERENCE "ANSI { fddiSMT 44 }" ::= { fddimibSMTEntry 21 } fddimibSMTStationStatus OBJECT-TYPE SYNTAX INTEGER { concatenated(1), separated(2), thru(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The current status of the primary and secondary paths within this station." REFERENCE "ANSI { fddiSMT 45 }" ::= { fddimibSMTEntry 22 } fddimibSMTPeerWrapFlag OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable assumes the value of the PeerWrapFlag in CFM (refer to ANSI SMT 9.7.2.4.4)." REFERENCE "ANSI { fddiSMT 46 }" ::= { fddimibSMTEntry 23 } fddimibSMTTimeStamp OBJECT-TYPE SYNTAX FddiTimeMilli ACCESS read-only STATUS mandatory DESCRIPTION "This variable assumes the value of TimeStamp (refer to ANSI SMT 8.3.2.1)." REFERENCE "ANSI { fddiSMT 51 }" ::= { fddimibSMTEntry 24 } fddimibSMTTransitionTimeStamp OBJECT-TYPE SYNTAX FddiTimeMilli ACCESS read-only STATUS mandatory DESCRIPTION Case & Rijsinghani [Page 15]
RFC 1512 FDDI MIB September 1993 "This variable assumes the value of TransitionTimeStamp (refer to ANSI SMT 8.3.2.1)." REFERENCE "ANSI { fddiSMT 52 }" ::= { fddimibSMTEntry 25 } fddimibSMTStationAction OBJECT-TYPE SYNTAX INTEGER { other(1), -- none of the following connect(2), disconnect(3), path-Test(4), self-Test(5), disable-a(6), disable-b(7), disable-m(8) } 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(1): Results in an appropriate error. connect(2): Generates a Connect signal to ECM to begin a connection sequence. See ANSI Ref 9.4.2. disconnect(3): Generates a Disconnect signal to ECM. see ANSI Ref 9.4.2. path-Test(4): 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(5): Initiates a station Self_Test. The results of this action are not specified in this standard. disable-a(6): Causes a PC_Disable on the A port if the A port mode is peer. disable-b(7): Causes a PC_Disable on the B port if the B port mode is peer. disable-m(8): Causes a PC_Disable on all M ports. Attempts to set this object to all other values results in an appropriate error. The result of setting this variable to path-Test(4) or self- Case & Rijsinghani [Page 16]
RFC 1512 FDDI MIB September 1993 Test(5) is implementation-specific." REFERENCE "ANSI { fddiSMT 60 }" ::= { fddimibSMTEntry 26 } -- the MAC group -- Implementation of the MAC Group is mandatory for all -- systems which implement manageable FDDI subsystems. fddimibMACNumber 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." ::= { fddimibMAC 1 } -- the MAC table fddimibMACTable OBJECT-TYPE SYNTAX SEQUENCE OF FddimibMACEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of MAC entries. The number of entries shall not exceed the value of fddimibMACNumber." ::= { fddimibMAC 2 } fddimibMACEntry OBJECT-TYPE SYNTAX FddimibMACEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A MAC entry containing information common to a given MAC." INDEX { fddimibMACSMTIndex, fddimibMACIndex } ::= { fddimibMACTable 1 } FddimibMACEntry ::= SEQUENCE { fddimibMACSMTIndex Case & Rijsinghani [Page 17]
RFC 1512 FDDI MIB September 1993 INTEGER, fddimibMACIndex INTEGER, fddimibMACIfIndex INTEGER, fddimibMACFrameStatusFunctions INTEGER, fddimibMACTMaxCapability FddiTimeNano, fddimibMACTVXCapability FddiTimeNano, fddimibMACAvailablePaths INTEGER, fddimibMACCurrentPath INTEGER, fddimibMACUpstreamNbr FddiMACLongAddressType, fddimibMACDownstreamNbr FddiMACLongAddressType, fddimibMACOldUpstreamNbr FddiMACLongAddressType, fddimibMACOldDownstreamNbr FddiMACLongAddressType, fddimibMACDupAddressTest INTEGER, fddimibMACRequestedPaths INTEGER, fddimibMACDownstreamPORTType INTEGER, fddimibMACSMTAddress FddiMACLongAddressType, fddimibMACTReq FddiTimeNano, fddimibMACTNeg FddiTimeNano, fddimibMACTMax FddiTimeNano, fddimibMACTvxValue FddiTimeNano, fddimibMACFrameCts Counter, fddimibMACCopiedCts Counter, fddimibMACTransmitCts Counter, fddimibMACErrorCts Counter, fddimibMACLostCts Case & Rijsinghani [Page 18]
RFC 1512 FDDI MIB September 1993 Counter, fddimibMACFrameErrorThreshold INTEGER, fddimibMACFrameErrorRatio INTEGER, fddimibMACRMTState INTEGER, fddimibMACDaFlag INTEGER, fddimibMACUnaDaFlag INTEGER, fddimibMACFrameErrorFlag INTEGER, fddimibMACMAUnitdataAvailable INTEGER, fddimibMACHardwarePresent INTEGER, fddimibMACMAUnitdataEnable INTEGER } fddimibMACSMTIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "The value of the SMT index associated with this MAC." ::= { fddimibMACEntry 1 } fddimibMACIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "Index variable for uniquely identifying the MAC object instances, which is the same as the corresponding resource index in SMT." REFERENCE "ANSI { fddiMAC 34 }" ::= { fddimibMACEntry 2 } fddimibMACIfIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION Case & Rijsinghani [Page 19]
RFC 1512 FDDI MIB September 1993
RFC 1512 FDDI MIB September 1993 "Indicates the Paths which are available to this Port. In the absence of faults, the A and B Ports will always have both the Primary and Secondary Paths available. 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 }" ::= { fddimibPORTEntry 10 } fddimibPORTPMDClass OBJECT-TYPE SYNTAX INTEGER { multimode(1), single-mode1(2), single-mode2(3), sonet(4), low-cost-fiber(5), twisted-pair(6), unknown(7), unspecified(8) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the type of PMD entity associated with this port." REFERENCE "ANSI { fddiPORT 22 }" ::= { fddimibPORTEntry 11 } fddimibPORTConnectionCapabilities OBJECT-TYPE SYNTAX INTEGER (0..3) ACCESS read-only STATUS mandatory DESCRIPTION "A value that indicates the connection capabilities of the port. The pc-mac-lct bit indicates that the station has the capability of setting the PC_MAC_LCT Flag. The pc-mac-loop bit Case & Rijsinghani [Page 43]
RFC 1512 FDDI MIB September 1993 indicates that the station has the capability of setting the PC_MAC_Loop Flag (refer to ANSI 9.4.3.2). The value is a sum. This value initially takes the value zero, then for each capability that this port has, 2 raised to a power is added to the sum. The powers are according to the following table: capability Power pc-mac-lct 0 pc-mac-loop 1 " REFERENCE "ANSI { fddiPORT 23 }" ::= { fddimibPORTEntry 12 } fddimibPORTBSFlag OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable assumes the value of the BS_Flag (refer to ANSI SMT 9.4.3.3)." REFERENCE "ANSI { fddiPORT 33 }" ::= { fddimibPORTEntry 13 } fddimibPORTLCTFailCts 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 }" ::= { fddimibPORTEntry 14 } fddimibPORTLerEstimate 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 base 10 logarithm (refer to ANSI SMT 9.4.7.5.)." Case & Rijsinghani [Page 44]
RFC 1512 FDDI MIB September 1993 REFERENCE "ANSI { fddiPORT 51 }" ::= { fddimibPORTEntry 15 } fddimibPORTLemRejectCts 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 }" ::= { fddimibPORTEntry 16 } fddimibPORTLemCts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The aggregate link error monitor error count, set to zero only on station initialization." REFERENCE "ANSI { fddiPORT 53 }" ::= { fddimibPORTEntry 17 } fddimibPORTLerCutoff 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 base 10 logarithm (default of 7)." REFERENCE "ANSI { fddiPORT 58 }" ::= { fddimibPORTEntry 18 } fddimibPORTLerAlarm 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 base 10 logarithm of the estimate Case & Rijsinghani [Page 45]
RFC 1512 FDDI MIB September 1993 (default of 8)." REFERENCE "ANSI { fddiPORT 59 }" ::= { fddimibPORTEntry 19 } fddimibPORTConnectState 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 and is equal to the value of Connect_State (refer to ANSI 9.4.1)" REFERENCE "ANSI { fddiPORT 61 }" ::= { fddimibPORTEntry 20 } fddimibPORTPCMState 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 "The state of this Port's PCM state machine refer to ANSI SMT 9.6.2)." REFERENCE "ANSI { fddiPORT 62 }" ::= { fddimibPORTEntry 21 } fddimibPORTPCWithhold OBJECT-TYPE SYNTAX INTEGER { none(1), m-m(2), Case & Rijsinghani [Page 46]
RFC 1512 FDDI MIB September 1993 otherincompatible(3), pathnotavailable(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The value of PC_Withhold (refer to ANSI SMT 9.4.1)." REFERENCE "ANSI { fddiPORT 63 }" ::= { fddimibPORTEntry 22 } fddimibPORTLerFlag OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "The condition becomes active when the value of fddiPORTLerEstimate is less than or equal to fddiPORTLerAlarm. This will be reported with the Status Report Frames (SRF) (refer to ANSI SMT 7.2.7 and 8.3)." REFERENCE "ANSI { fddiPORT 64 }" ::= { fddimibPORTEntry 23 } fddimibPORTHardwarePresent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the presence of underlying hardware support for this Port object. If the value of this object is false(2), the reporting of the objects in this entry may be handled in an implementation-specific manner." REFERENCE "ANSI { fddiPORT 65 }" ::= { fddimibPORTEntry 24 } fddimibPORTAction OBJECT-TYPE SYNTAX INTEGER { other(1), -- none of the following maintPORT(2), enablePORT(3), disablePORT(4), startPORT(5), stopPORT(6) Case & Rijsinghani [Page 47]
RFC 1512 FDDI MIB September 1993 } ACCESS read-write STATUS mandatory DESCRIPTION "Causes a Control signal 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, or PC_Stop) (refer to ANSI 9.4.2)." REFERENCE "ANSI { fddiPORT 70 }" ::= { fddimibPORTEntry 25 } END 5. Acknowledgements This document was produced by the IETF FDDI MIB working group: 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, Fibronics 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 Case & Rijsinghani [Page 48]
RFC 1512 FDDI MIB September 1993 Debbie Futcher, U.S. Naval Surface Warfare Center Joseph Golio, Cray Research Jeremy Greene, Coral 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, Distributed Systems International, Inc. Gary Malkin, Proteon Bruce McClure, Synernetics Keith McCloghrie, Hughes Lan Systems Donna McMaster, SynOptics John O'Hara, Massachusetts Institute of Technology Luc Pariseau, Digital Equipment Corporation Dave Perkins, SynOptics Communications James E. Reeves, SynOptics Communications Jim Reinstedler, Ungermann-Bass Radhi Renous, Fibronics Sal Ricci, AT&T/NCR 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, Fibronics Mark Sleeper, Sparta Lou Steinberg, IBM Corporation Larry Stefani, Digital Equipment Corporation Mary Jane Strohl, Apollo/Hewlett Packard Sally Tarquinio, Mitre Corporation Kaj Tesink, Bellcore Ian Thomas, Chipcom Dean Throop, Data General Bill Townsend, Xylogics Case & Rijsinghani [Page 49]
RFC 1512 FDDI MIB September 1993 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, Distributed Systems International, Inc. Y. C. Yang Denis Yaro, Sun Microsystems Jeff Young, Cray Research The author gratefully acknowledges the labors of Judi Talley and David Reid of SNMP Research, Inc. for their editorial assistance in the preparation of this document. 6. References [1] Rose M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", STD 16, RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990 [2] Case, J., "FDDI Management Information Base", RFC 1285, SNMP Research, Incorporated, January 1992. [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, 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", STD 17, 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", STD 16, RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. Case & Rijsinghani [Page 50]
RFC 1512 FDDI MIB September 1993 [8] American National Standards Institute, FDDI Station Management (SMT), Draft Proposed American National Standard, American National Standards Institute, X3T9.5/84-49 REV 7.3.



Back to RFC index

 

Associates:

 



Sponsered-Sites:

Register domain name and transfer | Cheap webhosting service | Domain name registration

 

 

""