LBHUB-FMS-MIB: View SNMP OID List / Download MIB

A list of alarm entries.

A list of parameters that set up a periodic checking for alarm conditions.

An index that uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device.

The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this variable, care should be given to ensure that the variable being monitored will not exceed 2^31 - 1 and roll over the alarmValue object during the interval. This object may not be modified if the associated alarmStatus object is equal to valid(1).

The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Counter, Gauge, or TimeTicks) may be sampled. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. During a set operation, if the supplied variable name is not available in the selected MIB view, a badValue error must be returned. If at any time the variable name of an established alarmEntry is no longer available in the selected MIB view, the probe must change the status of this alarmEntry to invalid(4). This object may not be modified if the associated alarmStatus object is equal to valid(1).

The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is absoluteValue(1), the value of the selected variable will be compared directly with the thresholds at the end of the sampling interval. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds. This object may not be modified if the associated alarmStatus object is equal to valid(1). Enumeration: 'absoluteValue': 1, 'deltaValue': 2.

The value of the statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed.

The alarm that may be sent when this entry is first set to valid. If the first sample after this entry becomes valid is greater than or equal to the risingThreshold and alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the fallingThreshold and alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3), then a single falling alarm will be generated. This object may not be modified if the associated alarmStatus object is equal to valid(1). Enumeration: 'fallingAlarm': 2, 'risingAlarm': 1, 'risingOrFallingAlarm': 3.

A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the alarmFallingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).

A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the alarmRisingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).

The index of the eventEntry that is used when a rising threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated alarmStatus object is equal to valid(1).

The index of the eventEntry that is used when a falling threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated alarmStatus object is equal to valid(1).

The entity that configured this entry and is therefore using the resources assigned to it.

The status of this alarm entry. Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.

A list of events to be generated.

A set of parameters that describe an event to be generated when certain conditions are met.

An index that uniquely identifies an entry in the event table. Each such entry defines one event that is to be generated when the appropriate conditions occur.

A comment describing this event entry.

The type of notification that the probe will make about this event. In the case of log, an entry is made in the log table for each event. In the case of snmp-trap, an SNMP trap is sent to one or more management stations. Enumeration: 'snmp-trap': 3, 'none': 1, 'log': 2, 'log-and-trap': 4.

If an SNMP trap is to be sent, it will be sent to the SNMP community specified by this octet string. In the future this table will be extended to include the party security mechanism. This object shall be set to a string of length zero if it is intended that that mechanism be used to specify the destination of the trap.

The value of sysUpTime at the time this event entry last generated an event. If this entry has not generated any events, this value will be zero.

The entity that configured this entry and is therefore using the resources assigned to it. If this object contains a string starting with 'monitor' and has associated entries in the log table, all connected management stations should retrieve those log entries, as they may have significance to all management stations connected to this device

The status of this event entry. If this object is not equal to valid(1), all associated log entries shall be deleted by the agent. Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.

A list of events that have been logged.

A set of data describing an event that has been logged.

The event entry that generated this log entry. The log identified by a particular value of this index is associated with the same eventEntry as identified by the same value of eventIndex.

An index that uniquely identifies an entry in the log table amongst those generated by the same eventEntries. These indexes are assigned beginning with 1 and increase by one with each new log entry. The association between values of logIndex and logEntries is fixed for the lifetime of each logEntry. The agent may choose to delete the oldest instances of logEntry as required because of lack of memory. It is an implementation-specific matter as to when this deletion may occur.

The value of sysUpTime when this log entry was created.

An implementation dependent description of the event that activated this log entry.

The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.

The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.

The IPX System Table - basic information.

Each entry corresponds to one instance of IPX running on the system.

The unique identifier of the instance of IPX to which this row corresponds. This value may be written only when creating a new entry in the table.

The validity of this entry in the IPX system table. Setting this field to off indicates that this entry may be deleted from the system table at the IPX implementation's discretion. Enumeration: 'on': 2, 'off': 1.

The network number portion of the IPX address of this system.

The node number portion of the IPX address of this system.

The readable name for this system.

The total number of IPX packets received, including those received in error.

The number of IPX packets discarded due to errors in their headers, including any IPX packets with a size less than the minimum of 30 bytes.

The number of IPX packets discarded because the destination socket was not open.

The number of IPX packets received but discarded due to reasons other than those accounted for by ipxBasicSysInHdrErrors, ipxBasicSysInUnknownSockets, ipxAdvSysInDiscards, and ipxAdvSysInCompressDiscards.

The number of IPX packets received with incorrect checksums.

The total number of IPX packets delivered locally, including packets from local applications.

The number of times no route to a destination was found.

The number of IPX packets supplied locally for transmission, not including any packets counted in ipxAdvForwPackets.

The number of IPX packets supplied locally that contained errors in their structure.

The number of outgoing IPX packets discarded due to reasons other than those accounted for in ipxBasicSysOutMalformedDiscards, ipxAdvSysOutFiltered, and ipxAdvSysOutCompressDiscards.

The total number of IPX packets transmitted.

The configured maximum number of IPX sockets that may be open at one time.

The number of IPX socket open calls which failed.

The IPX System Table - advanced information.

Each entry corresponds to one instance of IPX running on the system.

The unique identifer of the instance of IPX to which this row corresponds. This value may be written only when creating a new entry in the table.

The maximum number of paths with equal routing metric value which this instance of the IPX my split between when forwarding packets.

The maximum number of hops a packet may take.

The number of IPX packets discarded due to exceeding the maximum hop count.

The number of incoming IPX packets discarded due to filtering.

The number of incoming IPX packets discarded due to decompression errors.

The number of NETBIOS packets received.

The number of IPX packets forwarded.

The number of outgoing IPX packets discarded due to filtering.

The number of outgoing IPX packets discarded due to compression errors.

The number of circuits known to this instance of IPX.

The number of currently reachable destinations known to this instance of IPX.

The number of services known to this instance of IPX.

The results of the start up check on NVRAM Battery condition. Enumeration: 'low': 2, 'normal': 1.

The results of the Power On Self Test are recorded here. The value read is a bit mask of possible errors, these are as follows:- bit 3 set - error accessing the Ethernet Address PROM bit 5 set - error accessing System RAM bit 6 set - error accessing NVRAM bit 7 set - battery level low bit 8 set - MFP errors bit 9 set - LANCE errors bit 11 set - error allocating unit ids to units bit 12 set - error on acessing repeater bit 13 set - as above bit 14 set - as above bit 15 set - as above bit 16 set - as above bit 17 set - error accessing processor bus bit 2 set - error accessing the Ethernet Address PROM bit 3 set - error accessing System RAM bit 4 set - as above bit 5 set - error accessing NVRAM bit 6 set - battery level low bit 7 set - MFP errors bit 8 set - LANCE errors bit 9 set - MBGA errors bit 10 set - watchdog bit 11 set - error allocating unit ids bit 12 set - error on acessing repeater bit 13 set - as above bit 14 set - as above bit 15 set - as above bit 16 set - as above bit 17 set - as above bit 18 set - hardware bus error bit 19 set - as above bit 20 set - as above bit 21 set - as above bit 22 set - interrupt error bit 23 set - as above bit 24 set - unknown

In order to ensure a clean read of the Fault table this flag should be set to clean_read when commencing to read the table and should be examined after reading the entire table. If still set to clean_read then the table read is okay, if not the table should be re-read as it has been modified during the read process. Enumeration: 'clean-read': 1, 'modified': 2.

The Fault Table.

Information relating to a single fault.

The index into the Fault table. The initial read from the table should be read as the next, from an index of 0; subsequent reads should read the next from the index returned by the previous read.

This error number for this fault log entry.

The time since startup, in milliseconds, when the fault occurred.

The number of restarts at time of fault.

This enables/disables the Echo service for test purposes only. Enumeration: 'disabled': 1, 'enabled': 2.

Hardware error counter.

Hardware error counter.

Hardware error counter.

Hardware error counter.

Table configuration options for all of the groups.

Configuration options for a single group.

This attribute uniquely identifies this group within the repeater, it is part of the index for the group table.

This attribute identifies which ports are present on this group. It is formatted as a bit mask. Bit 0, the least significant bit, represents port number one, bit 1 represents port number two and so on. Port number one is the port that has a xxxxPortIndex of 1 where xxxx depends upon which MIB table is being examined. The bits in the bit mask are set to a 1 if the port is present in this group and set to a zero if the port is not present.

Table configuration options for all of the ports.

Configuration options for a single port.

This attribute uniquely identifies this group within the repeater, it is part of the index for the port table.

This attribute uniquely identifies this port within the group, it is part of the index for the port table.

This attribute controls the 10BaseT squelch level for a 10BaseT port. It enables it to be set to the IEEE standard level = normal, or to be set more sensative = low. Enumeration: 'notApplicable': 3, 'low': 2, 'normal': 1.

This attribute determines if link pulse generating and monitoring is enabled or disabled for a 10BaseT port. The attribute may take the values of enabled (standard) or disabled (non standard). Enumeration: 'disabled': 2, 'notApplicable': 3, 'enabled': 1.

This attribute determines the state of the cross over switch, this is only applicable to fixed UTP ports. Enumeration: 'notApplicable': 1, 'crossed': 3, 'normal': 2.

This attribute describes the port type in terms of media supported, modular or fixed and manufacturer. Enumeration: 'fms-ModularFMaleAUI': 9, 'fms-ModularCoax': 10, 'fms-ModularBridge': 4, 'bti-FixedUTP': 32, 'bti-ModularCoax': 41, 'fms-ModularFibreFB': 14, 'bti-AUI': 50, 'fms-ModularMaleAUI': 8, 'fms-FixedFibreFL': 3, 'fms-ModularSTP': 13, 'fms-FixedCoax': 2, 'fms-AUI': 15, 'bti-ModularFibreFL': 40, 'unknown': 60, 'fms-FixedTP': 1, 'fms-ModularFibreFL': 11, 'fms-ModularUTP': 12.

Configuration information and control variables for a collection of media cards this repeater.

Configuration information and control variables for a single media card.

This attribute uniquely identifies this media card, it is part of the index for the Media Table.

The Media Module Hardware revision number.

The Media Module Card Type. Enumeration: 'fms-24PortUTP': 5, 'fmsII-6Port-Fibre': 68, 'bt-12Port-UTP-Rev1': 15, 'fmsII-24Port-TP-RJ45': 69, 'fms-6Port-Fibre': 4, 'bt-12Port-UTP-Rev2': 14, 'fmsII-10Port-Coax': 66, 'bti-12Port-UTP-Rev2': 30, 'fms-12Port-UTP': 1, 'fmsII-24Port-TP-Telco': 70, 'fmsII-12Port-Fibre': 67, 'fms-10Port-Coax': 2, 'fmsII-12Port-TP-RJ45': 65, 'bti-12Port-UTP-Rev1': 31, 'fms-12Port-Fibre': 3, 'fmsII-RMON-Box': 71.

The deprRptrGroupCapacity is the number of groups that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range from 1 to deprRptrGroupCapacity. Some groups may not be present in a given repeater instance, in which case the actual number of groups present will be less than deprRptrGroupCapacity. The number of groups present will never be greater than deprRptrGroupCapacity. Note: In practice, this will generally be the number of field-replaceable units (i.e., modules, cards, or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to numbers marked on the physical enclosure.

The deprRptrOperStatus object indicates the operational state of the repeater. The deprRptrHealthText object may be consulted for more specific information about the state of the repeater's health. In the case of multiple kinds of failures (e.g., repeater failure and port failure), the value of this attribute shall reflect the highest priority failure in the following order: rptrFailure(3) groupFailure(4) portFailure(5) generalFailure(6) Enumeration: 'generalFailure': 6, 'ok': 2, 'groupFailure': 4, 'portFailure': 5, 'other': 1, 'rptrFailure': 3.

The health text object is a text string that provides information relevant to the operational state of the repeater. Agents may use this mechanism to provide detailed failure information or instructions for problem resolution. The contents are agent-specific.

Setting this variable to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [11]. Setting this variable to noReset(1) has no effect. The agent will always return the value noReset(1) when this variable is read. This action does not reset the management counters defined in this document nor does it affect the portAdminState parameters. Included in this action is the execution of a disruptive Self-Test. As a result of this action a deprRptrReset trap may be sent. Note: This action may result in the loss of packets. Enumeration: 'reset': 2, 'noReset': 1.

Setting this variable to selfTest(2) causes the repeater to perform a agent-specific, non- disruptive self-test that has the following characteristics: (1) The nature of the tests is not specified. (2) The test does not change the state of the repeater or management information about the repeater. (3) The test does not inject packets onto any segment. (4) The test does not prevent the relay of any packets. (5) The test does not interfere with management functions. After performing this test the agent will update the repeater health information. If a change in the repeater health has occurred, the agent will send a deprRptrHealth trap. Setting this variable to noSelfTest(1) has no effect. The agent will always return the value noSelfTest(1) when this variable is read. Enumeration: 'noSelfTest': 1, 'selfTest': 2.

This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: deprRptrPortOperStatus does not have the value notPresent(3), deprRptrPortAdminStatus is enabled(1), and deprRptrPortAutoPartitionState is autoPartitioned(1).

Table of descriptive and status information about the groups of ports.

An entry in the table, containing information about a single group of ports.

This variable identifies the group within the repeater for which this entry contains information. This value is never greater than deprRptrGroupCapacity.

A textual description of the group. This value should include the full name and version identification of the group's hardware type and indicate how the group is differentiated from other groups in the repeater. 'Wilma Flintstone 6-Port FOIRL Plug-in Module, Rev A' or 'Barney Rubble 10BASE-T 4-port SIMM socket V. 2.1' are examples of valid group descriptions. It is mandatory that this only contain printable ASCII characters.

The vendor's authoritative identification of the group. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of group is being managed. For example, this variable could take the value 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, and had assigned the identifier 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 6-Port FOIRL Plug-in Module.'

An object that indicates the operational status of the group. A status of notPresent(4) indicates that the group has been physically removed from the repeater. A status of operational(2) indicates that the group is functioning, and a status of malFunctioning(3) indicates that the group is malfunctioning in some way. Enumeration: 'malFunctioning': 3, 'resetInProgress': 6, 'operational': 2, 'other': 1, 'undertest': 5, 'notPresent': 4.

An object that contains the value of sysUpTime at the time that the value of the deprRptrGroupOperStatus object for this group last changed. A value of zero indicates that the group's oper status has not changed since the agent last restarted.

The deprRptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-1024. Within each group, the ports are uniquely numbered in the range from 1 to deprRptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.

Table of descriptive and status information about the ports.

An entry in the table, containing information about a single port.

This variable identifies the group containing the port for which this entry contains information.

This variable identifies the port within the group within the repeater for which this entry contains management information. This value can never be greater than deprRptrGroupPortCapacity for the associated group.

Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. (In effect, when a port is disabled, the value of deprRptrPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the deprRptrPortAutoPartitionState becomes notAutoPartitioned(2), regardless of its pre-disabling state.) Enumeration: 'disabled': 2, 'enabled': 1.

The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Sect. 9 [11]. They are not differentiated here. Enumeration: 'autoPartitioned': 1, 'notAutoPartitioned': 2.

This object indicates the port's operational state. The notPresent(3) state indicates the port is physically removed (note this may or may not be possible depending on the type of port.) The operational(1) state indicates that the port is enabled (see deprRptrPortAdminStatus) and working, even though it might be auto-partitioned (see deprRptrPortAutoPartitionState). Enumeration: 'notPresent': 3, 'notOperational': 2, 'operational': 1.

This counter is incremented every time the repeater state machine enters the TRANSMIT COLLISION state from any state other than ONE PORT LEFT (Ref: Fig 9-2) [11]. Note: The approximate minimum time for counter rollover is 16 hours.

Table of performance and error statistics for the groups.

An entry in the table, containing total performance and error statistics for a single group. Regular retrieval of the information in this table provides a means of tracking the performance and health of the networked devices attached to this group's ports. The counters in this table are redundant in the sense that they are the summations of information already available through other objects. However, these sums provide a considerable optimization of network management traffic over the otherwise necessary retrieval of the individual counters included in each sum.

This object identifies the group within the repeater for which this entry contains information.

The total number of frames of valid frame length that have been received on the ports in this group. This counter is the summation of the values of the deprRptrMonitorPortReadableFrames counters for all of the ports in the group. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.

The total number of octets contained in the valid frames that have been received on the ports in this group. This counter is the summation of the values of the deprRptrMonitorPortReadableOctets counters for all of the ports in the group. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.

The total number of errors which have occurred on all of the ports in this group. This counter is the summation of the values of the deprRptrMonitorPortTotalErrors counters for all of the ports in the group.

Table of performance and error statistics for the ports.

An entry in the table, containing performance and error statistics for a single port.

This object identifies the group containing the port for which this entry contains information.

This object identifies the port within the group for which this entry contains information.

This object is the number of frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1) and for which the FCSError and CollisionEvent signals are not asserted. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.

This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.

This counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError and CollisionEvent signals deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). The approximate minimum time for rollover of this counter is 80 hours.

This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If deprRptrMonitorPortAlignmentErrors is incremented then the deprRptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. The approximate minimum time for rollover of this counter is 80 hours.

This counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). If deprRptrMonitorPortFrameTooLongs is incremented then neither the deprRptrMonitorPortAlignmentErrors nor the deprRptrMonitorPortFCSErrors counter shall be incremented for the frame. The approximate minimum time for rollover of this counter is 61 days.

This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Note: shortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network. Implementors may wish to consider selecting the ShortEventMaxTime towards the lower end of the allowed tolerance range to accommodate bit losses suffered through physical channel devices not budgeted for within this standard. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than ValidPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times. An event whose length is greater than 74 bit times but less than 82 bit times shall increment either the shortEvents counter or the runts counter but not both. A CarrierEvent greater than or equal to 552 bit times but less than 565 bit times may or may not be counted as a runt. ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of runts may exceed ValidPacketMinTime. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one for any CarrierEvent signal on any port for which the CollisionEvent signal on this port is asserted. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variable transitions to the value SQE (Ref: 9.6.6.2, IEEE 802.3 Std) while the ActivityDuration is greater than the LateEventThreshold. Such a CarrierEvent is counted twice, as both a collision and as a lateEvent. The LateEventThreshold is greater than 480 bit times and less than 565 bit times. LateEventThreshold has tolerances included to permit an implementation to build a single threshold to serve as both the LateEventThreshold and ValidPacketMinTime threshold. The approximate minimum time for rollover of this counter is 81 hours.

This counter is incremented by one for each CarrierEvent on this port whose ActivityDuration is greater than the MAU Jabber Lockup Protection timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). Other counters may be incremented as appropriate.

This counter is incremented by one for each frame received on this port that meets all of the following conditions: a) The CollisionEvent signal is not asserted. b) The ActivityDuration is greater than ValidPacketMinTime. c) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing. When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.

This counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause port partitioning are specified in the partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here.

The total number of errors which have occurred on this port. This counter is the summation of the values of other error counters (for the same port), namely: deprRptrMonitorPortFCSErrors, deprRptrMonitorPortAlignmentErrors, deprRptrMonitorPortFrameTooLongs, deprRptrMonitorPortShortEvents, deprRptrMonitorPortLateEvents, deprRptrMonitorPortVeryLongEvents, and deprRptrMonitorPortDataRateMismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.

Table of address mapping information about the ports.

An entry in the table, containing address mapping information about a single port.

This object identifies the group containing the port for which this entry contains information.

This object identifies the port within the group for which this entry contains information.

This object is the SourceAddress of the last readable frame (i.e., counted by deprRptrMonitorPortReadableFrames) received by this port.

This counter is incremented by one for each time that the deprRptrAddrTrackLastSourceAddress attribute for this port has changed. This may indicate whether a link is connected to a single DTE or another multi-user segment. The approximate minimum time for rollover of this counter is 81 hours.

Table of descriptive and status information about the groups of ports.

An entry in the table, containing information about a single group of ports.

This variable uniquely identifies the repeater group that contains the port to which is connected the MAU for which this entry contains information.

This variable uniquely identifies the repeater port to which is connected the MAU for which this entry contains information.

This variable uniquely identifies the MAU for which this entry contains information.

A value that identifies the 10 Mb/s baseband MAU type. The enumeration of the type is such that the value matches the section number of the IEEE 802.3 standard that specifies the particular MAU. Enumeration: 'tenbaseFP': 16, 'aui': 7, 'unknown': 2, 'tenbase2': 10, 'tenbase5': 8, 'foirl': 9, 'other': 1, 'tenbaseT': 14, 'tenbaseFB': 17, 'tenbaseFL': 18.

The administrative state of the MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the administrative state. A MAU in the operational(3) state is fully functional, operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI and the media transmitter to idle. Standby(4) mode only applies to link type MAUs. The state of mauMediaAvailable is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter as if it were powered down. The MAU may return other(1) state for the mauJabber and mauMediaAvailable objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power- on cycle would. Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state. Enumeration: 'reset': 6, 'standby': 4, 'unknown': 2, 'operational': 3, 'other': 1, 'shutdown': 5.

If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link integrity/low light state. For an AUI or coax MAU this indicates whether or not loopback is detected on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2, and 10BASE-FP. NOTE: IEEE 802.3 modified the following descriptive text at their meeting the week of 3/9/92. New text will be provided at the San Diego IETF plenary. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback will be tested on each transmission during which no collision is detected. If DI receives input within startUpDelay of the start of output on DO, loopback will be detected. The value of startUpDelay shall be between 15 and 25 BT (bit times). Transition form input to output_idle on DI while output is present on DO may also be detected on loopback. The value of this attribute will only change during non-collided transmissions for AUI, coax, and 10BASE-FP MAUs. Enumeration: 'invalidSignal': 6, 'unknown': 2, 'other': 1, 'remoteFault': 5, 'notPresent': 4, 'present': 3.

A count of the number of times that deprRpMauMediaAvailable for this MAU instance leaves the state available(3). Implementation of this object is mandatory for MAU instances with deprRpMauType of AUI(7). It is recommended for all MAU types.

If the MAU is in jabber state the attribute is set to the jabbering(4) value. This object returns the value other(1) for MAU type AUI. Enumeration: 'unknown': 2, 'other': 1, 'noJabber': 3, 'jabbering': 4.

A count of the number of times that deprRpMauJabberState for this MAU instance enters the state jabbering(4).

Table of performance and error statistics for the MACs.

This object identifies the MAC for which this entry contains information.

The number of packets the MAC has failed to receive. This may be due to no receive buffer being available or a SILO overflow.

The number of packets, whose length has exceeded 1519 bytes, transmitted by the MAC.

The number of times the MAC has been unable to obtain bus mastership with the specified period.

The number packets received by the MAC containing an FCS error.

The number of packets received by the MAC which caused a SILO overflow error.

The number of packets received by the MAC containing a non-integer multiple of 8 bits and a FCS error.

The number of times the MAC has failed, in 16 attempts, to transmit a packet due to collisions on the network.

The number of times the MAC detected an out of window collision during transmission of a packet.

The number of times the MAC has detected a loss of carrier during transmission of a packet.

The number of times the MAC has truncated an outgoing packet due to the SILO emptying before the end of packet has been reached.

The time, in seconds, between successive heartbeat events sent to the management station. An interval of 0 indicates that no heartbeat events are to be generated.

This table shows the IP address and network mask to be used to initialise ipAddrTable on each network interface after the next system restart. There is one entry per network interface and the index is equivalent to the index for the ifTable in the MIB-II interfaces group.

The default information relating to a single IP interface.

The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex (for ifTable).

The IP address to be used for this interface.

The IP network mask to be used for this interface.

This is the IP address of the default router to be used for sending IP datagrams to remote destinations which have no suitable entry in the routing table. This corresponds to an entry in the MIB-II ipRouteTable with an ipRouteDest field of '0.0.0.0' (the default router) which is set up from this value after a system restart. Changes to this value do not affect the IP routing table until after the next system restart. (To change the default router without a restart, the IP routing table should be changed directly, with an equivalent change to setIpIfRouter only if the change is required to be made permanently.)

The PROM software version number.

The number of restarts the box has undergone, either power on or reset switch or watchdog expiries.

The reason for the last system restart. This may be due to management command; watchdog timeout expiry; power interruption; the reset switch was pressed or system error. It is not possible to differentiate between the latter two causes. Enumeration: 'watchdog': 3, 'power-reset': 4, 'other': 1, 'command': 2, 'system-error': 5.

Reset the device with manufacturers default configuration if the manDefaultReset value is written to this item. Enumeration: 'nochange': 1, 'manDefaultReset': 2.

The last System Error experienced by the system. This is set to the NVRAM last system error code on startup. When the system issues a TRAP indicating the last system error number the NVRAM version is set to zero. Hence after the next restart this attribute will have the value zero also.

Restart the device with it's current configuration if the restart value is written to this item. Enumeration: 'nochange': 1, 'restart': 2.

A table which is used to control the loading of new software images to the devices controlled by the management agent. By convention the first entry in the table (device type = system(1), instance = 1) controls the loading of the device containing the management agent itself. Agents which have no subsidiary devices will have only this one entry in the table. If the Agent does control subsidiary devices, the other entries control the loading of software into subsidiary devices.

An entry containing the objects for controlling the loading of a software image to a device controlled by the agent.

The type of the device to load. Simple agents only contain one device type, which is always `system'. More complex agents, probably containing multiple processors, may contain subsidiary devices denoted (for the purposes of the system loader) as `component'. In general, a `system' device is one which monitors and/or manages the operation of `component' devices. Enumeration: 'component': 2, 'system': 1.

The instance of the device type specified by slDeviceType. By convention instance 1 of the system devices is the one containing the management agent, and always exists. Many systems will contain only the one instance of the system device type.

The status of the last system load operation requested for this device. If the value of this object is in the range 1 to 19 inclusive, or 200 or more, the download failed, and the value is an error code indicating the reason why. Codes 1 to 7 are a direct mapping from the TFTP error codes defined in RFC-783. The possible status values and their meanings are as follows:- fileNotFound(1) the server cannot find the requested file; accessViolation(2) the file system security mechanism does not permit TFTP to access the requested file; illegalOperation(4) TFTP protocol error; unknownTransferID(5) TFTP protocol error; noSuchUser(7) user number not recognised; noResponse(8) load server failed to respond; noResource(9) the download could not be started because of a lack of resources; recLenMismatch(10) the record length differs from that implied by the value of the record length field; invalidRecType(11) the record type is not recognised; checksumError(12) record checksum error; wrongDevice(13) the device type in the file is incorrect; wrongHardwareVersion(14) the software image is not suitable for this version of the hardware; noFileHeader(15) the first record in the file was not a file header; byteCountError(16) the byte count reported in the file trailer record differed from the number of bytes actually received; invalidProgAddress(17) the load file contained a load address which was outside the valid range of memory; eraseFailed(18) unable to erase the program memory; progFailed(19) hardware error programming the memory. The meanings of the remaining values are as follows:- loadPending(20) a load has been requested but has not yet begun; loadActive(21) the device is currently being downloaded; success(22) the device has been downloaded successfully; paused(23) the device could not complete the download at this time, it will request that the load be restarted when it is ready. The following status values may result from downloading a subsidiary module:- modInvalidAdress(200) the load file contained a load address which was outside the valid range of memory; modChecksumError(201) the load data was corrupted as it was transferred from the management agent to the subsidiary module; modTimeout(202) the management agent timed out while waiting for a response from the subsidiary module; modBusy(203) the subsidiary module was unable to accept a command from the management agent; modRemoved(204) the subsidiary module was removed during the download; modNoResource(205) the download could not continue because of a lack of resources; modFailure(255) the subsidiary module failed during the download. Enumeration: 'wrongHardwareVersion': 14, 'byteCountError': 16, 'modFailure': 255, 'modTimeout': 202, 'noFileHeader': 15, 'checksumError': 12, 'progFailed': 19, 'invalidRecType': 11, 'loadPending': 20, 'invalidProgAddress': 17, 'accessViolation': 2, 'modInvalidAdress': 200, 'wrongDevice': 13, 'unknownTransferID': 5, 'modNoResource': 205, 'noResponse': 8, 'recLenMismatch': 10, 'paused': 23, 'noResource': 9, 'illegalOperation': 4, 'success': 22, 'eraseFailed': 18, 'loadActive': 21, 'noSuchUser': 7, 'modChecksumError': 201, 'modRemoved': 204, 'fileNotFound': 1, 'modBusy': 203.

The version identifier of the software running in the device.

The version number identifying the revision level of the hardware of the device

The name of the file which contains the software image to load, or which was the last loaded to the device.

The IP address of the host containing the software image to load, or from which the last image loaded was read. This object has been deprecated in favour of writing the IP address into slServerAddress.

Writing 2 to this object causes the agent to attempt to load a new software image to the corresponding device. The file to load and the address of the server to load it from are specified in the other objects in the same row of the table. Enumeration: 'startDownload': 2, 'noAction': 1.

The address of the server containing the software image to load, or from which the last image was loaded. This is either an IP address in standard dotted notation, or an IPX address in the format aabbccdd:112233445566. An error is returned if the agent does not support the download protocol implied by the address format.

This is the protocol to use when downloading the software from the server specified in slServerAddress. At present, this value is determined by the value of slServerAddress which is currently un-ambiguous and so this object is read-only. Enumeration: 'unknown': 1, 'tftp-ip': 2, 'tftp-ipx': 3.

A table of permissions for access to the managed device from each of its interfaces, at each security access level. The table is fixed at 5 rows, indexed by the access level.

This table allows individual interfaces to be enabled or disabled separately for each security level.

Index to the security enable table. Enumeration: 'manager': 3, 'specialist': 4, 'secureMonitor': 2, 'security': 5, 'monitor': 1.

Community SNMP access permission Enumeration: 'permanentlyEnabled': 3, 'enable': 1, 'permanentlyDisabled': 4, 'disable': 2.

Secure SNMP access permission Enumeration: 'permanentlyEnabled': 3, 'enable': 1, 'permanentlyDisabled': 4, 'disable': 2.

Local Terminal access permission Enumeration: 'permanentlyEnabled': 3, 'enable': 1, 'permanentlyDisabled': 4, 'disable': 2.

Telnet access permission Enumeration: 'permanentlyEnabled': 3, 'enable': 1, 'permanentlyDisabled': 4, 'disable': 2.

Front Panel access permission Enumeration: 'permanentlyEnabled': 3, 'enable': 1, 'permanentlyDisabled': 4, 'disable': 2.

A table used to define Users. Users can be created/modified or deleted, with the exception of the default Users which cannot be deleted.

1. Creating a new user is done by using the username as a qualifier and SETting any of the items in the row - defaults will be used for the remaining values. 2. Deleting a user is by writing 'invalid' to the status column. 3. There must always be users called 'monitor', 'manager' and 'security' - these cannot be deleted.

User Status. `invalid' is used to indicate this user is no longer allowed to access this device, and the table entry may subsequently be re-used. Note that the Status of default Users cannot be set to invalid. Enumeration: 'valid': 1, 'invalid': 2.

An ASCII string for the User Name. Empty strings are not allowed. The index column for the User Table.

User Access Level defining the scope of management allowed for this user. Note that the access level of default Users cannot be changed. Enumeration: 'manager': 3, 'specialist': 4, 'secureMonitor': 2, 'security': 5, 'monitor': 1.

The password required for user confirmation, when access is made via the local serial port, the front panel, or via Telnet.

The community string identifying this user, when access is made via the original community-based SNMP (RFC1157).

The local party identity of this user, when access is made via secure SNMP.

The manager party identity for this user, when access is made via secure SNMP.

The audit log is a circular table recording all updates to the managed database on the device. The log must be read regularly by a management device, to maintain a more permanent record of the management history.

Each entry contains the time an update was made, by whom, the item referenced, the new value and the result of this request.

Audit Log Index. A monotonically increasing value to uniquely identify an entry in the audit log. This value wraps around (to 1) after reaching the maximum value (65535).

The time, in hundredths of a second since the last system restart, of the update request.

The name of the user making the request.

The object identifier of the item being updated. This includes any qualifier for the item.

The new value for the item.

The result of the update request may indicate that it was applied successfully, that it failed (for one of a number of reasons) or that it is still in progress. Enumeration: 'locked': 4, 'success': 255, 'no-such-function': 6, 'no-such-item': 7, 'too-big': 2, 'failed': 3, 'security-violation': 5, 'pending': 1.

A table used to define Alarms.

This table allows Alarms to be set-up on items in the MIB.

Unique identifier for a row in the Alarm Table. Allocated by the Alarms Subsystem. An integer in the range 1..gaugeTableSize.

The object Id and qualifier of the item to be monitored by this alarm.

A 'counter', by definition will always be a positive number. 'Meters' can be signed or unsigned. Enumeration: 'signedMeter': 2, 'unsignedMeter': 3, 'counter': 1.

The number of samples used to calculate the Alarm Value. The default number of samples is four. If a SamplesPerAverage value of one is used, no average is calculated and the GaugeValue will be the most recent sample. Enumeration: 'maxSamples': 4, 'twoSamples': 2, 'threeSamples': 3, 'nonAveraging': 1.

Number of seconds between samples. The total averaging period is given by (gaugeSamplesPerAverage * gaugeSamplePeiod) secs.

The most recently computed average of the item being monitored. For a `meter' alarm, this is the simple average of the samples. For a 'counter' alarm, this is the average of the differences between successive samples. Counters and unsignedMeters are unsigned 32-bit values and have a maximum value of 4294967295. signedMeters are signed 32-bit values and have a maximum value of +-2147483647 divided by the value of gaugeSamplesPerAverage .

The highest recorded Alarm Value. This will be either a signed or unsigned 32 bit value depending on the gaugeItemType

The threshold value of the the Alarm which causes the ThresholdState to move from the 'ready' state to the 'fired' state and also causes the the ThresholdAction to be taken. It will be either a signed or unsigned 32-bit integer depending on the gaugeItemType.

The threshold value of the the Alarm which causes the ThresholdState to move from the `fired' state to the `ready' state and also causes the the RecoveryAction to be taken. This value will be either a signed or unsigned 32-bit integer depending on the gaugeItemType.

This object identifies the action to be taken when an Alarm crosses the Threshold Level. The default action will be to send a trigger event (sendTrap). The other actions are device specific and may not be available on all devices. See the RMON Event Table for the actions supported by this device. Enumeration: 'notifyAndBlipCardOff': 6, 'notifyPollFailed': 22, 'enable': 4, 'blipPortOff': 12, 'disablePort': 14, 'notifyAndDisablePort': 8, 'notifyAndResilientSwitch': 18, 'noAction': 1, 'blipCardOff': 13, 'notifyBandwidthExceeded': 19, 'disable': 3, 'notifyAndDisableCard': 9, 'notifyAndBlipPortOff': 5, 'sendTrap': 2, 'notifyFilterBridgePort': 23, 'disableCard': 15, 'notifyErrorsExceeded': 20.

This object identifies the action to be taken when a 'fired' Alarm crosses the Recovery Level. The default action will be to send a recovery event (sendTrap). The actions for 'disable' and 'enable' are device specific. Enumeration: 'notifyAndEnableCard': 11, 'enable': 4, 'notifyPollSuccess': 21, 'notifyUnfilterBridgePort': 24, 'noAction': 1, 'enablePort': 16, 'disable': 3, 'notifyAndEnablePort': 10, 'sendTrap': 2, 'enableCard': 17.

onTriggersEnabled - This is the normal active state of a alarm. The gaugeValue is updated on every sample and if it crosses the Threshold or Recovery Levels, the corresponding Action will be taken. onTriggersDisabled - This is used when a new device, or alarm is set up and the Threshold and Recovery Levels have not been calibrated. The Alarm runs as normal and the gaugeValue and peakValue are updated. However, if the gaugeValue crosses the Threshold or Recovery Levels, no action is taken. off - This de-activates the alarm, allowing it to be configured safely . Before updating any of the Alarm fields the alarm SHOULD be turned off. Turning the alarm 'off' and then 'on' will not lose any of the sampling data, gaugeValue, peakValue, or thresholdStatus. Updates to the index fields will fail since they are read-only. deleted - An alarm is invalidated by setting it to 'deleted'. A 'deleted' alarm will not be returned by a 'GetNext' request. autoCalibrate - Updates the Threshold and Recovery values according to the current peak value. The gaugeState will then be set to 'onTriggersEnabled'. This can be done when the gaugeState is in states (1), (2), or (3). After this operation: thresholdLevel = peakValue * %gaugeThresholdLevelScaler recoveryLevel = peakValue * %gaugeRecoveryLevelScaler gaugeState = onTriggersEnabled When the gaugeState is set to either of the 'on' states, all the fields for the Alarm are validated. If any of the fields are invalid, the operation will fail. The sampling data, gaugeValue, peakValue and thresholdState can be reset by writing 'onTriggersEnabled', 'onTriggers- Disabled' , or 'autoCalibrate' to the gaugeState when it is already in either of the 'on' states. Enumeration: 'deleted': 4, 'autoCalibrate': 5, 'off': 3, 'onTriggersDisabled': 2, 'onTriggersEnabled': 1.

The entity that configured this entry and is therefore using the resources assigned to it.

Number of entries in Alarm Table. The size of the Alarm Table depends on the requirements and available resources of the device. The actual maximum will probably be around 1000.

The ThresholdLevel is set to this percentage of the peakValue when the Alarm is auto-calibrated. e.g gaugeThresholdLevelScaler = 120 gaugePeakValue = 360 After writing 'calibrateTriggers' to the gaugeState: ThresholdLevel = 120/100 * 360 = 432

The RecoveryLevel is set to this percentage of the peakValue when the Alarm is auto-calibrated. e.g gaugeRecoveryLevelScaler = 90 gaugePeakValue = 360 After writing 'calibrateTriggers' to the gaugeState: RecoveryLevel = 90/100 * 360 = 324

Performs the specified operation on every Alarm in the table. Enumeration: 'deleteAll': 1.

Object Id and qualifier of alarm(s) to be updated.

Alarm Table Column to be updated. Enumeration: 'recoveryLevel': 5, 'thresholdAction': 6, 'itemType': 1, 'gaugeState': 8, 'samplesPerAverage': 2, 'samplePeriod': 3, 'recoveryAction': 7, 'thresholdLevel': 4.

Value to be written to the 'gaugeConfigureColumn' of the Alarms which match the 'gaugeConfigureObjId'. Writing to this value initiates the operation.

Indicates the gaugeIndex which must be used to create the next alarm. Index is set to GAUGE_TABLE_FULL (zero) if there are no free rows in the table.

Time in hundredths of a second when the last Login was attempted. Note, that only the ASCII Agent can write to this parameter. A write operation from any other agent will result in an ERROR

An ASCII string used when attempted login. Empty string is NOT valid. Note, that only the ASCII Agent can write to this parameter. A write operation from any other agent will result in an ERROR

Status of last attempted login. The value 'loginOKFromTelnet' or 'loginOKFromSerialPort' is used to show that the user was allowed access via Telnet or Serial Port. 'DeniedAccessFromTelnet' indicates that a user was denied access via Telnet. The value 'unknownUserFromTelnet' is used to show that a user attempted to login with an invalid user name from a Telnet session and 'incorrectPasswordFromTelnet' is used to show that an invalid password was entered having supplied a valid user name. The value 'securityViolationFromTelnet' is used to indicate that a user has entered the password incorrectly three time consecutively from a Telnet session. Note that only the ASCII Agent can write to this parameter. A write operation from any other agent will result in an ERROR Enumeration: 'incorrectPasswordFromSerialPort': 8, 'unknownUserFromTelnet': 5, 'incorrectPasswordFromTelnet': 7, 'securityViolationFromSerialPort': 10, 'nologin': 11, 'securityViolationFromTelnet': 9, 'unknownUserFromSerialPort': 6, 'deniedAccessFromTelnet': 3, 'deniedAccessFromSerialPort': 4, 'loginOKFromTelnet': 1, 'loginOKFromSerialPort': 2.

An ASCII string describing the Banner to appear on the FIRST screen of the Local Management Terminal. The string of 490 characters defines a region in the centre of the screen which is 7 Rows by 70 Columns

This object identifies the serial port which SLIP can use to send/receive packets. If this object is set to 0xFFFF, then SLIP cannot send/receive packets.

Configuration parameters for all the V.24 ports in a system.

Configuration parameters for a V.24 port in the system.

This attribute uniquely identifies this V.24 port, it is the index for the V.24 table.

This determines if the V.24 port is to be connected locally to a terminal or terminal emulator in which case no interface signals need to be asserted unless requested by other management options below or if the V.24 port is to be connected to a modem when at least DSR is required to be asserted. Enumeration: 'remote': 2, 'local': 1.

This determines if the configuration parameters for the V.24 port, speed, parity, stop bits, character size, are to be determined automatically from an initial character sequence entered by the user or they will be defined by the management options below. Enumeration: 'disabled': 1, 'enabled': 2.

This determines the receive and transmit speed of the V.24 port unless the autoconfigure attribute is enabled when the data rates are determined from the line. Split rx and tx speeds are not possible. Enumeration: 'speed4800': 6, 'speed19200': 8, 'speed9600': 7, 'speed38400': 9, 'speed1200': 4, 'speed2400': 5.

This determines the character size, unless the autoconfigure attribute is enabled when character size is determined automatically from the line, it may be set to either 7 or 8 bits. Enumeration: 'size7': 3, 'size8': 4.

This determines the number of stop bits. Enumeration: 'stopTwo': 3, 'stopOne': 1, 'stopOneDotFive': 2.

This determines the parity option to be used, unless the autoconfigure attribute is enabled when parity is determined automatically from the line, it may be set to either no parity, space (parity bit always 0), mark (parity bit always 1), odd or even. Enumeration: 'evenParity': 5, 'markParity': 3, 'spaceParity': 2, 'noParity': 1, 'oddParity': 4.

This attribute is only applicable to local connection types. It determines if DSR need be asserted for a local connection to be made and if the connection need be released if DSR is seen deasserted. Enumeration: 'disabled': 1, 'enabled': 2.

This attribute is only applicable to local connection types. It determines if DCD need be asserted for a local connection to be made and if the connection should be release if DCD is seen deasserted. Enumeration: 'disabled': 1, 'enabled': 2.

This determines the flow control protocol to be used, either no flow control, xon-xoff, rts-cts full duplex or rts-cts. Full duplex rts/cts uses the rts and cts lines as two independent signals. The DTE signals to the DCE that it is prepared to accept more data by asserting RTS, the DCE signals to the DTE that is is prepared to accept more data by asserting CTS. Half duplex rts/cts (the conventional way) uses CTS as a response to RTS, the DCE flow controls the DTE by only returning CTS is response to a RTS from the DTE when the DCE can accept more data. The DTE can flow control the DCE by raising RTS when it does not want to receive any more input and dropping it when it is ready to receive more. Enumeration: 'noFlowControl': 1, 'rtsCtsHalfDplx': 4, 'rtsCtsFullDplx': 3, 'xonXoff': 2.

This attribute may be written to to force the operational V.24 port parameters to be updated. Enumeration: 'nochange': 1, 'update': 2.

This counter is incremented by one for each frame whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFraneSize and for which FCSError is not asserted that is received by the repeater.

This counter is incremented by the octet count for each readable frame received by the repeater.

This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size received by the repeater.

This counter is incremented by one for each frame with an FCS error that does have a framing error and which is of legal frame size received by the repeater.

This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater.

This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected by the repeater.

This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision detected by the repeater.

This counter is incremented by one each time the repeater state machine enters the COLLISION COUNT INCREMENT state.

This counter is incremented by one each time a collisions occurs after valid packet min time, a late event is counted as both a collision and as a late event.

This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time.

This counter is incremented by one each time a packet has been received by this repeater with the data rate detectably mismatched from the local frequency.

This counter is incremented by one each time the repeater has automatically partitioned any port.

This counter is incremented by one for each readable frame seen by the repeater that is addressed to a unicast (non group) address.

This counter is incremented by one for each readable frame seen by the repeater that is addressed to a multicast (non broadcast) address.

This counter is incremented by one for each readable frame seen by the repeater that is addressed to the broadcast address.

This attribute allows all counters on this repeater to be cleared. Enumeration: 'clearCounters': 2, 'noChangeCounters': 1.

This attribute enable/disables traps to be issued when a ports media is lost/regained. Enumeration: 'disableMediaTraps': 2, 'enableMediaTraps': 1.

This attribute enables/disables traps to be issued when ports autopartition or reconnect. Enumeration: 'enablePartitionTraps': 1, 'disablePartitionTraps': 2.

This counter is incremented by one for each erroneous frame seen by the repeater.

Status information and control variables for a collection of groups in this repeater.

Status information and control variables for a single group of ports.

This attribute uniquely identifies this group, it is part of the index for the Group Table.

This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size.

This counter is incremented by one for each frame with an FCS error that does have a framing error and which is of legal frame size .

This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater.

This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected.

This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision.

This counter is incremented by one each time the repeater state machine enters the COLLISION COUNT INCREMENT state.

This counter is incremented by one each time a collisions occurs after valid packet min time, a late event is counted as both a collision and as a late event.

This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time.

This counter is incremented by one each time a packet has been received with the data rate detectably mismatched from the local frequency.

This counter is incremented by one each time the repeater has automatically partitioned any port.

This counter is incremented by one for each readable frame seen by the group that is addressed to a unicast (non group) address.

This counter is incremented by one for each readable frame seen by the group that is addressed to a multicast (non broadcast) address.

This counter is incremented by one for each readable frame seen by the group that is addressed to the broadcast address.

This attribute allows all counters on this Group to be cleared. Enumeration: 'clearCounters': 2, 'noChangeCounters': 1.

Table of performance and error statistics for the ports.

Performance and error statistics for a single port.

This attribute uniquely identifies this group within the repeater, it is part of the index for the port table.

This attribute uniquely identifies this port within the group, it is part of the index for the port table.

This counter is incremented by one for each readable frame seen by the group that is addressed to a unicast (non group) address.

This counter is incremented by one for each readable frame seen by the group that is addressed to a multicast (non broadcast) address.

This counter is incremented by one for each readable frame seen by the group that is addressed to the broadcast address.

This attribute allows all counters on this Port to be cleared. Enumeration: 'clearCounters': 2, 'noChangeCounters': 1.

This attribute passes or filters out entries from this port from going to the End Station Table processing. For instance the backbone port on a repeater would normally have this atribute set to filter, while the UTP ports would normally have this set to pass. Enumeration: 'filter': 1, 'pass': 2.

This attribute enable/disables traps to be issued when a ports media is lost/regained. Enumeration: 'disableMediaTraps': 2, 'enableMediaTraps': 1.

This attribute enables/disables traps to be issued when ports autopartition or reconnect. Enumeration: 'enablePartitionTraps': 1, 'disablePartitionTraps': 2.

This parameter is normally set to 'NO-CHANGE'. When any change is made to the database the value of this parameter becomes 'MODIFIED'. It will remain in this state until a manager sets it back to NO-CHANGE. Enumeration: 'noChange': 1, 'modified': 2.

This parameter clears the End Station Database Enumeration: 'flush': 1.

End Station Table

The end station database maintains information concerning end-station address information against device port for 802.3 repeater type devices. This table provides one of three views on that database. The view provided by this particular table is indexed firstly on address type and then on address and so can be used to read the entire contents of the database in end-station address order. Additionally one can read all addresses of a certain type from the database, e.g. all IP addresses known. There are some points to note when reading the contents of the end station table. Firstly the repeater number reported will change if a unit is moved from one repeater within a device to another or if a unit is isolated. Secondly an address will only appear in the table once. If an address which is already present in the database is found on another port then the original record is changed and the 'modified' flag set for that entry.

The end station database is capable of storing information for a number of different protocols. Each protocol has it's own addressing format. This parameter allows access to the end station database indexed on address type. For example to read all IEE8021 addresses simply start with a get-next operation on IEEE8021.0 and read until the type changes. Enumeration: 'ipx': 3, 'internet': 2, 'ieee8021': 1.

The address information held in this entry of the database. The length and format of the string depends on the address type. For example a MAC address will be a 6 byte OCTET STRING, an IP address a 4 byte OCTET STRING.

Number of unit on which this address was learnt.

Port number of unit on which this address was learnt.

End Station Table ( Modified )

The end station database maintains information concerning end-station address information against device port for 802.3 repeater type devices. This table provides one of three views on that database. The view provided by this particular table is indexed firstly on address type and then on address. The view is restricted to include only those entries in the database which have the MODIFIED flag set, i.e. that have been changed since the database was last viewed by the manager. This table can be used to read all the modified entries in the table. This is the table generally used to update the contents of a station map in a management station. Note that it can take a reasonable time to read the contents of the table and in that time other changes may occur. To detect this an additional MIB parameter is specified 'esDatabaseState'. This parameter is normally set to 'NO-CHANGE'. When any change is made to the database the value of this parameter becomes 'MODIFIED'. It will remain in this state until a manager sets it back to NO-CHANGE. The recommended access for this table is as follows: do { write 'NO-CHANGE' to esDatabaseState read modified table read esDatabaseState } while esDatabaseState is MODIFIED There are some points to note when reading the contents of the end station table. Firstly the repeater number reported will change if a unit is moved from one repeater within a device to another or if a unit is isolated. Secondly an address will only appear in the table once. If an address which is already present in the database is found on another port then the original record is changed and the 'modified' flag set for that entry.

The end station database is capable of storing information for a number of different protocols. Each protocol has it's own addressing format. This parameter allows access to the end station database indexed on address type. For example to read all IEE8021 addresses simply start with a get-next operation on IEEE8021.0 and read until the type changes. Enumeration: 'ipx': 3, 'internet': 2, 'ieee8021': 1.

The address information held in this entry of the database. The length and format of the string depends on the address type. For example a MAC address will be a 6 byte OCTET STRING, an IP address a 4 byte OCTET STRING.

Unit number on which this address was learnt.

Port number of unit on which this address was learnt.

End Station Table ( Port Access )

The end station database maintains information concerning end-station address information against device port for 802.3 repeater type devices. This table provides one of three views on that database. The view provided by this particular table allows one to determine the addresses learnt against a particular port.

Unit part of the identifier for this port.

Port number on unit of port for which end station information is required.

Each port may have a number of addresses against it. This index allows these various addresses to be distinguished. The only stipulation on this number is that it will be unique for the any combination of unit and port. The numbers will be returned in numerically ascending order for a particular unit.port combination but will not be contiguous. For example the following sequence could be seen: Unit Port Index 1 1 211 1 1 231 1 1 438 1 1 672 1 2 120 etc

The end station database is capable of storing information for a number of different protocols. Each protocol has it's own addressing format. This parameter identifies the type of address in this entry of the table. Enumeration: 'ipx': 3, 'internet': 2, 'ieee8021': 1.

The address information held in this entry of the database. The length and format of the string depends on the address type. For example a MAC address will be a 6 byte OCTET STRING, an IP address a 4 byte OCTET STRING.

The snmp Trap database

A single snmp Trap entry

The Status of the Entry valid(1) or invalid(2), writing invalid(2) will delete the entry from the table Enumeration: 'valid': 1, 'invalid': 2.

The Destination IP Address

SNMP Community to be used to send traps to destination trapDestination

SNMP Subject Party used to generate traps to destination trapDestination

32 Bit Mask indicating which Trap categories that the snmpTrapDestination is interested in. '00000001'h - High Priority Configuration Traps '00000002'h - Low Priority Configuration Traps '00000004'h - High Priority Security Traps '00000008'h - Low Priority Security Traps '00000010'h - Alarms & Polling Traps '00000020'h - Regular Heartbeat Traps '00000040'h - End Station Table Traps '00000080'h - reserved '00000100'h - Physical Entity Traps '00000200'h - Facility Traps '00000400'h - Service Related Traps A value of 0xFFFFFFFF enables all traps.

The Maximum rate at which that trapDestination is willing to receive traps, specified as the minimum interval in milliseconds between traps. A value of zero indicates that no trap throttling is required.

This table can store the destination addresses of SNMP managers that wish to receive traps from this device.

This table can store the destination addresses of SNMP managers that wish to receive traps from this device.

This is the unique identifier for this row in the snmpTrapTable. When creating a new row, a manager can read the value of the snmpTrapNextFreeIndex object and (if non-zero) can use this value as the index of the new row to be created. The actual number of rows that can be created on any particular device depends on the memory and processing resources available at the time.

This DisplayString is the network address of the device to which SNMP traps will be sent. This is an IP or IPX address. The following formats can be used. IP nnn.nnn.nnn.nnn - dotted format IPX AABBCCDD:AABBCCDDEEFF - network : node Destination addresses must be unique within this table. An error is returned if an attempt is made to add a duplicate address.

This defines the transport protocol to use when sending an SNMP trap. At present, this value is determined by the format/value of snmpTrapDestionation which is currently un-ambiguous and so this object is read-only. Enumeration: 'unknown': 1, 'ipx': 3, 'ip': 2.

SNMP Community String to be used when sending Traps to this destination.

32 Bit Mask indicating which Trap categories that the snmpTrapDestination is interested in. '00000001'h - High Priority Configuration Traps '00000002'h - Low Priority Configuration Traps '00000004'h - High Priority Security Traps '00000008'h - Low Priority Security Traps '00000010'h - Alarms & Polling Traps '00000020'h - Regular Heartbeat Traps '00000040'h - End Station Table Traps '00000080'h - reserved '00000100'h - Physical Entity Traps '00000200'h - Facility Traps '00000400'h - Service Related Traps A value of 0xFFFFFFFF enables all traps.

The maximum rate at which that snmpTrapDestination is willing to receive traps, specified as the minimum interval in milliseconds between traps. For example, a value of 2000 will limit traps sent to this destination to one trap every 2 seconds. A value of zero indicates that no trap throttling is required.

The SNMPv2 RowStatus convention. Notes: Because this is such a simple table:- 1) Writing any data to a destroyed row, changes its state to active. 2) There is no notReady or notInService state. Each row is either active or destroyed. Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

Indicates the the next value of snmpTrapIndex which can be used to create a new trap destination entry. This value is zero if there are no free rows in the table.

An MSH may be configured to contain a number of 'resilient pairs'. These are 802.3 point to point connections, e.g. UTP, that allow two repeaters to be connected together in a resilient configuration. In such a configuration one of the two ports is nominated the 'main' port while the other is the 'standby' port. One of these two ports is enabled and is the current active port. The other is present in case of failure of the active port. Such a failure is detected by the MSH and a switch performed. There are a couple of rules that must apply to a resilient pair definition before that definition becomes a valid resilient pair. Firstly both ports must be on the same repeater. Secondly the standby port must be configured to be 'disabled on boot'. That is it must recover from a power failure in a disabled state. This prevents loops in the network. Several tables control the resilient repeater configuration for the MSH. This is the first. This is the main table and allows the creation and deletion of pairs and provides status control and information. The information in this table is indexed on the repeater number and the slot/port location of the main port. To create a new resilient pair simply write any writeable object indexed on the main port. This will create a new entry in the table which has the state 'invalid' (read resPairState). Having created the row, write to the other parameters specifying valid information. When all the parameters are valid the resPairState will become 'operational'. In this state the pair will correctly operate as a resilient pair. If any of the attributes in the table change so that the pair in no linger valid this will be reflected in the resPortState parameter. To delete a resilient pair, write 'delete' to resPairAction.

A resilient pair must be attached to one of the repeaters in the chassis. This is part of the index value required to access this table.

This is the second key in the index to this table. This is the slot number of the main port in this pair.

This is the final, key used to index entries in this table. It is the port number of the main port in the pair.

Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly OK. This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the OK and Active state. OK and Active means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read. Enumeration: 'failed': 1, 'ok-and-active': 3, 'ok': 2.

This is the slot number of the standby port for this pair. The port must be present on the same repeater as the main port and so this information is not duplicated.

This is the port number of the standby port.

Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly OK. This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the OK and Active state. OK and Active means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read. Enumeration: 'failed': 1, 'ok-and-active': 3, 'ok': 2.

Each row in the table is in one of two states, 'invalid' or 'operational'. If the state is 'invalid', the resilient pair represented by this row is not active. There are several reasons why this may be the case. Firstly during the row creation process, not all information necessary may have been provided. Secondly an operational pair may become invalid because the resilient pair rules are no longer met because of a change in the MSH configuration. The rules are that both main and standby ports be on the same repeater and that the standby port be 'disable on boot'. Changing the standby card, moving one of the cards to a different repeater are two possible changes that can invalidate a pair configration. If the parameters in the row are all valid then the pair becomes 'operational'. Enumeration: 'invalid': 1, 'operational': 2.

This parameter must be set to under-modification before any changes are made to an existing configuration. Changes are not applied until this parameter is set to stable. Enumeration: 'under-modification': 1, 'stable': 2.

This is object allows the state of a resilient pair to be modified. The create operation configures the resilient port from this table entry. The delete operation removes the resilient definitions from this table and terminates operation of resilience on this pair of ports. The togglePort operation allows the current active port to be changed to the other port. This second operation will only take affect if the state of the currently non-active port is 'OK'. Enumeration: 'create': 1, 'togglePort': 3, 'delete': 2.

This parameter controls whether the resilient pair is enabled or not. In the disabled state , both ports of the resilient pair are disabled. The default value of this parameter is enable Enumeration: 'enable': 1, 'disable': 2.

This table is read-only. If provides shortcut information to allow for the translation of a port number to a corresponding main port number. This value can then be used to access the main resilience table. Each resilient pair has two entries in this table, one for the main port and one for the standby port. The entry for the main port returns the same port, the entry for the standby port returns the corresponding main port.

The repeater index of the port being accessed. This is the first of three indices on this table.

Second index on this table.

Third index on this table.

This attribute specifies whether the port indexed is a main or standby port in the resilient pair table. If the port is neither then there will not be a row in this table indexed for that port. Enumeration: 'standby': 2, 'main': 1.

This is the slot number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.

This is the port number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.

This parameter causes all entries in the resilience table to be flushed. Flushing the resilience table does not affect the state of any of the resilient links or ports. Once the table has been flushed , NO resilient links are configured. This parameter is used to ensure that the resilient link table is empty , before new resilient links are configured.

Table of descriptive and status information about the groups of ports.

An entry in the table, containing information about a single group of ports.

This identifies one of the repeaters within the chassis as the target of a request.

This object identifies the card within the repeater for which this entry contains information.

The mrmCardPortCapacity is the number of ports that can be contained within the group. Valid range is 1-1024. Within each group, the ports are uniquely numbered in the range from 1 to mrmCardPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.

An object that allows the user to test the operation of a card. Writing test(2) to this object forces the card to perform a disruptive test to determine if the card is functioning properly. Reading this object while the card is under test return the value testing(3). When the test is completed, reading this value will return either passed(4) or failed(5). Enumeration: 'test': 2, 'failed': 5, 'testing': 3, 'passed': 4, 'noTest': 1.

MSH Repeater Cards have the ability to disable ports at power up or reset. Ports configured in this way are useful for configuring resilient links because they prevent loops in the network from occurring at startup. The disable on boot feature is determined according to a hardware strap which cannot be changed via software. This parameter is a mask containing a single bit for each port on the card. Port 1 is represented by bit 0 and so-on. If a bit representing a particular port is 0 this port boots up disabled. If the bit is a 1 the port boots up enabled. This parameter allows the state of these parameters to be rapidly determined by a network management application.

10Base-T line cards are normally configured (mdi_disabled(2)) to link to an external network device ( internal crossover ). Port 1 may be configured ( mdi_enabled(3) ) to link to another 10Base-T line card ( with no internal crossover ). This parameter allows the configuration to be determined. Note ECS line cards show unknown(1) since the configuration cannot be accessed via the management interface. Enumeration: 'unknown': 1, 'mdiDisabled': 2, 'notApplicable': 4, 'mdiEnabled': 3.

Table of descriptive and status information about the ports.

An entry in the table, containing information about a single port.

This object identifies the repeater which this entry contains information.

This object identifies the group containing the port for which this entry contains information.

This object identifies the port within the group for which this entry contains information. This value can never be greater than mrmCardPortCapacity for the associated group.

This object specifies the type of electrical interface made available at the interface to the card for this port. The interface does not necessarily specify what the actual media to end station is. Enumeration: 'twistedPair': 5, 'fiber': 7, 'thinCoax': 4, 'unknown': 1, 'maleAUI': 2, 'unshieldedTP': 6, 'femaleAUI': 3.

This specifies the type of the physical connector through which one would attach to this card. This is distinct from the media type. For example UTP may be connected to the port via either an RJ45 or a Telco connector. Enumeration: 'dtype-15': 6, 'telco': 3, 'unknown': 1, 'st': 4, 'rj45': 2, 'bnc': 7, 'sma': 5.

Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. In effect, when a port is disabled, the value of mrmPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the mrmPortAutoPartitionState becomes notAutoPartitioned(2), regardless of its pre-disabling state.) Enumeration: 'disabled': 2, 'enabled': 1.

The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Section 9 IEEE 802.3 Std]. They are not differentiated here. Enumeration: 'partitioned': 1, 'unpartitioned': 2.

This object reflects the presence or absence of signal on this port. The signal may be either light in the case of fiber, or general link present in the case of copper. The value of this parameter is correct regardless of the state the admin state or the partition state. Enumeration: 'absent': 2, 'present': 1.

A repeater port may be enabled or disabled after a reset. This parameter indicates the default for this port. Enumeration: 'enable': 2, 'disable': 1.

This attribute determines whether and which address information is extracted from packets received on a port and forwarded to the end station database. It is recommended that this attribute be disabled for inter-repeater links to prevent the database being filled with remote information. To disable this feature for all address types write the value forwardNone (128) to this variable. Enumeration: 'forwardNone': 128, 'forwardMAC': 1, 'forwardIP': 2, 'forwardAll': 127.

Specifies whether a trap should be sent if the port partition state changes. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether a trap should be sent if the link state changes. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether security is an available feature on this port. Only ports that have this feature available can have an entry in the repeater security table. Enumeration: 'available': 1, 'notAvailable': 2.

This attribute determines if link pulse generating and monitoring is enabled or disabled for a 10BaseT port. The attribute may take the values of enabled (standard) or disabled (non standard). Enumeration: 'disabled': 2, 'notApplicable': 3, 'enabled': 1.

This attribute indicates whether the port is a modular port or not. Enumeration: 'unknown': 1, 'modularPort': 2, 'notModularPort': 3.

DUD Action for this port. Enumeration: 'disconnect': 3, 'notify': 2, 'noAction': 1.

This atribute indicates the function of the port. Enumeration: 'unknown': 1, 'repeater': 2, 'bridge': 3.

Table of performance and error statistics for the ports.

This table provides statistical and control information concerning the entire repeater.

This parameter is used as the index in this table. A modular chassis contains potentially many repeater services. Each repeater service contains a number of cards (or groups). This parameter allows one of those repeaters to be selected.

This counter is incremented by one for each frame whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize and for which FCSError is not asserted that is received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one for each readable frame seen by the Repeater that is addressed to a unicast (non Card) address.

This counter is incremented by one for each readable frame seen by the Repeater that is addressed to a multicast (non broadcast) address.

This counter is incremented by one for each readable frame seen by the Repeater that is addressed to the broadcast address ffffffffffff.

This counter is incremented by the octet count for each readable frame received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This object is the number of octets contained in valid frames that have been received on this port in which the destination field was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination was the broadcast address ffffffffffff. By attaching a gauge to this counter one can monitor the port for broadcast storms. Action can then be taken to automatically recover network normal operation. The approximate minimum time for rollover of this counter is 58 minutes.

This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one for each frame with an FCS error that does have a framing error and which is of legal frame size received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision detected by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one for any CarrierEvent signal on any port of this repeater for which the CollisionEvent signal on this port is asserted. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one each time a collisions occurs after valid packet min time, a late event is counted as both a collision and as a late event. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one each time a packet has been received by this repeater with the data rate detectably mismatched from the local frequency. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

This counter is incremented by one each time the repeater has automatically partitioned any port. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.

The total number of errors which have occurred on all ports on all groups of this repeater. This counter is the summation of the values of the mrmMonCardTotalErrors counters for all of the cards in the repeater. It is the sum of the following: FCS, Alignment, Frames Too Long, Short Events, Late Events, Very Long Events and Data Rate Mismatches. As a general indicator the individual error counters are too detailed. This parameter gives a very good monitor type parameter.

This object is a summation of the number of frames (including error frames) with a length of 64 octets which were received by each port on every card of this repeater.

This object is a summation of the number of frames (including error frames) with a length of between 65 and 127 octets inclusive which were received by each port on every card of this repeater.

This object is a summation of the number of frames (including error frames) with a length of between 128 and 255 octets inclusive which were received by each port on every card of this repeater.

This object is a summation of the number of frames (including error frames) with a length of between 256 and 511 octets inclusive which were received by each port on every card of this repeater.

This object is a summation of the number of frames (including error frames) with a length of between 512 and 1023 octets inclusive which were received by each port on every card of this repeater.

This object is a summation of the number of frames (including error frames) with a length of between 1024 and 1518 octets inclusive which were received by each port on every card of this repeater.

This object allows repeater stats specific actions to be implemented. There is only one action currently defined, 'clearCounters'. Writing this value to a repeater entry will clear ALL counters in this repeater. That include port stats, card and repeater totals. If this object is read then noAction will be returned. Enumeration: 'clearCounters': 1, 'noAction': 128.

This is a high level 'smart MIB' object. This object provides a running average of the bandwidth in use. This value is calculated locally on the agent and so does not require processor bandwidth from the management station or occupy valuable network bandwidth communicating with that station. By default an agent supporting this parameter will exhibit the following characteristics: 1) The parameter will be recalculated at approx 15 second intervals 2) Every calculation period the device will read the value of rptrMonitorPortReadableOctets. 3) The calculation will be performed on the most recent 4 samples as follows: 4 Sum(sample(i)/(time(i) * K)) * 100/4 i=1 Sample(i) is rptrMonitorPortReadableOctets(i)-rptrMonitorPortReadableOctets(i-1) time(i) is the time between sample(i-1) and sample(i) K is the max bytes per unit time (i.e. the available bandwidth K depends on the ring speed. The value is expressed as a percentage. A default threshold exists on this average so that if a calculated average exceeds 15% a trap will be sent to the management station. Further traps will not be sent until the average drops to below 10%. A particular device may provide a means of changing the number of samples, the averaging period, threshold and threshold action if it so wishes.

This is a high level 'smart MIB' object. This object provides a running average of the number of errors per 10000 packets. This is an error rate, and is calculated over the number of packets received in the sample periods, and not on every 10000 packets. This value is calculated locally on the agent and so does not require processor bandwidth from a management station or occupy valuable network bandwidth communicating with that station. By default an agent supporting this parameter will exhibit the following behaviour: 1) The parameter will be recalculated at approx 15 second intervals. 2) Every calculation period the device will read the value of rptrMonitorPortTotalErrors and rptrMonitorPortReadableFrames. 3) The calculation will be performed on the most recent 4 samples as follows: 4 10000 * Sum(Errors(i)/Frames(i)) i=1 Errors(i) = rptrMonitorPortTotalErrors(i)-rptrMonitorPortTotalErrors(i-1) Frames(i) = rptrMonitorPortReadableFrames(i)-rptrMonitorPortReadableFrames(i-1) The value is an integer number of errors per 10,000 packets received by this repeater. A default threshold exists on this average so that if a calculated average exceeds 200 (i.e. 2% of frames are in error) a trap will be sent to the management station. Further traps will not be sent until the average drops to below 100 (i.e. 1% of frames are in error). A particular device may provide a means of changing the number of samples, the averaging period and threshold if it so wishes.

This table contains parameters about the various repeater cards within the chassis. The table is indexed using the 'serviceIndex' for the repeater and the slot number within that repeater.

Status information and control variables for the ports on a single card.

This parameter is used as the first of two indices in this table. A modular chassis contains potentially many repeater services. Each repeater service contains a number of cards (or groups). In order to uniquely identify a port it is necessary to specify both the repeater service and the card within that repeater.

This is the second part of the key on this table. Having selected one of the repeaters within the chassis it is necessary to identify the card within that repeater.

This counter is incremented by one for each frame whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize and for which FCSError is not asserted that is received for any port on this card.

This counter is incremented by one for each readable frame seen by the Card that is addressed to a unicast (non Card) address.

This counter is incremented by one for each readable frame seen by the Card that is addressed to a multicast (non broadcast) address.

This counter is incremented by one for each readable frame seen by the Card that is addressed to the broadcast address ffffffffffff.

This counter is incremented by the octet count for each readable frame received by any port on this card.

This object is the number of octets contained in valid frames that have been received on this port in which the destination field was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination was the broadcast address ffffffffffff. By attaching a gauge to this counter one can monitor the port for broadcast storms. Action can then be taken to automatically recover network normal operation. The approximate minimum time for rollover of this counter is 58 minutes.

This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size.

This counter is incremented by one for each frame with an FCS error that does have a framing error and which is of legal frame size .

This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater.

This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected.

This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision.

This counter is incremented by one each time a collisions occurs after valid packet min time, a late event is counted as both a collision and as a late event.

This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time.

This counter is incremented by one each time a packet has been received with the data rate detectably mismatched from the local frequency.

This counter is incremented by one each time the repeater has automatically partitioned any port.

The total number of errors which have occurred on all ports of this card. This counter is the summation of the values of other error counters (for each port), namely: FCS Errors, Alignment Errors, Frames Too Long, Short Events, Late Events, Very Long Events, Data Rate Mismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.

This object is a summation of the number of frames (including error frames) with a length of 64 octets which were received by each port on this card.

This object is a summation of the number of frames (including error frames) with a length of between 65 and 127 octets inclusive which were received by each port on this card.

This object is a summation of the number of frames (including error frames) with a length of between 128 and 255 octets inclusive which were received by each port on this card.

This object is a summation of the number of frames (including error frames) with a length of between 256 and 511 octets inclusive which were received by each port on this card.

This object is a summation of the number of frames (including error frames) with a length of between 512 and 1023 octets inclusive which were received by each port on this card.

This object is a summation of the number of frames (including error frames) with a length of between 1024 and 1518 octets inclusive which were received by each port on this card.

This attribute allows all counters on this Card to be cleared. If this object is read then it will return noChangeCounters(1). Enumeration: 'clearCounters': 2, 'noChangeCounters': 1.

This is a high level 'smart MIB' object. This object provides a running average of the bandwidth in use. This value is calculated locally on the agent and so does not require processor bandwidth from the management station or occupy valuable network bandwidth communicating with that station. By default an agent supporting this parameter will exhibit the following characteristics: 1) The parameter will be recalculated at approx 15 second intervals 2) Every calculation period the device will read the value of rptrMonitorGroupTotalOctets. 3) The calculation will be performed on the most recent 4 samples as follows: 4 Sum(sample(i)/(time(i) * K)) * 100/4 i=1 Sample(i) is rptrMonitorGroupTotalOctets(i)-rptrMonitorGroupTotalOctets(i-1) time(i) is the time between sample(i-1) and sample(i) K is the max bytes per unit time (i.e. the available bandwidth K depends on the ring speed. The value is expressed as a percentage. A default threshold exists on this average so that if a calculated average exceeds 15% a trap will be sent to the management station. Further traps will not be sent until the average drops to below 10%. A particular device may provide a means of changing the number of samples, the averaging period, threshold and threshold action if it so wishes.

This is a high level 'smart MIB' object. This object provides a running average of the number of errors per 10000 packets. This is an error rate, and is calculated over the number of packets received in the sample periods, and not on every 10000 packets. This value is calculated locally on the agent and so does not require processor bandwidth from a management station or occupy valuable network bandwidth communicating with that station. By default an agent supporting this parameter will exhibit the following behaviour: 1) The parameter will be recalculated at approx 15 second intervals. 2) Every calculation period the device will read the value of rptrMonitorGroupTotalErrors and rptrMonitorGroupTotalFrames. 3) The calculation will be performed on the most recent 4 samples as follows: 4 10000 * Sum(Errors(i)/Frames(i)) i=1 Errors(i) = rptrMonitorGroupTotalErrors(i)-rptrMonitorGroupTotalErrors(i-1) Frames(i) = rptrMonitorGroupTotalFrames(i)-rptrMonitorGroupTotalFrames(i-1) The value is an integer number of errors per 10,000 packets received by this repeater. A default threshold exists on this average so that if a calculated average exceeds 200 (i.e. 2% of frames are in error) a trap will be sent to the management station. Further traps will not be sent until the average drops to below 100 (i.e. 1% of frames are in error). A particular device may provide a means of changing the number of samples, the averaging period and threshold if it so wishes.

Table of performance and error statistics for the ports.

Performance and error statistics for a single port.

This parameter selects one of the repeaters within the chassis. This forms the first, most significant index column. Having selected a repeater one must select a card then port within that repeater.

This attribute uniquely identifies this Card within the repeater, it is part of the index for the port table.

This attribute uniquely identifies this port within the Card, it is part of the index for the port table.

This object is the number of frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1) and for which the FCSError and CollisionEvent signals are not asserted. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.

This counter is incremented by one for each readable frame seen by the Card that is addressed to a unicast (non Card) address.

This counter is incremented by one for each readable frame seen by the Card that is addressed to a multicast (non broadcast) address.

This counter is incremented by one for each readable frame seen by the Card that is addressed to the broadcast address.

This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination field was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.

This object is the number of octets contained in valid frames that have been received on this port in which the destination was the broadcast address ffffffffffff. By attaching a gauge to this counter one can monitor the port for broadcast storms. Action can then be taken to automatically recover network normal operation. The approximate minimum time for rollover of this counter is 58 minutes.

This counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError and CollisionEvent signals deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). The approximate minimum time for rollover of this counter is 80 hours.

This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If rptrMonitorPortAlignmentErrors is incremented then the rptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. The approximate minimum time for rollover of this counter is 80 hours.

This counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). If this parameter is incremented then neither the alignment error nor the FCS error counters shall be incremented for the frame. The approximate minimum time for rollover of this counter is 61 days.

This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Note: shortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than ValidPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times. An event whose length is greater than 74 bit times but less than 82 bit times shall increment either the shortEvents counter or the runts counter but not both. A CarrierEvent greater than or equal to 552 bit times but less than 565 bit times may or may not be counted as a runt. ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of runts may exceed ValidPacketMinTime. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one each time a collision is detected on this port or when the CollisionEvent signal is asserted on this port. The approximate minimum time for rollover of this counter is 16 hours.

This counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variable transitions to the value SQE (Ref: 9.6.6.2, IEEE 802.3 Std) while the ActivityDuration is greater than the LateEventThreshold. Such a CarrierEvent is counted twice, as both a collision and as a lateEvent. The LateEventThreshold is greater than 480 bit times and less than 565 bit times. LateEventThreshold has tolerances included to permit an implementation to build a single threshold to serve as both the LateEventThreshold and ValidPacketMinTime threshold. The approximate minimum time for rollover of this counter is 81 hours.

This counter is incremented by one for each CarrierEvent on this port whose ActivityDuration is greater than the MAU Jabber Lockup Protection timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). Other counters may be incremented as appropriate.

This counter is incremented by one for each frame received on this port that meets all of the following conditions: a) The CollisionEvent signal is not asserted. b) The ActivityDuration is greater than ValidPacketMinTime. c) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing. When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.

This counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause port partitioning are specified in the partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here.

The total number of errors which have occurred on this port. This counter is the summation of the values of other error counters (for the same port), namely: FCS Errors, Alignment Errors, Frames Too Long, Short Events, Late Events, Very Long Events, Data Rate Mismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.

This object is the number of frames (including error frames) with a length of 64 octets which were received on this port.

This object is the number of frames (including error frames) with a length of between 65 and 127 octets inclusive which were received on this port.

This object is the number of frames (including error frames) with a length of between 128 and 255 octets inclusive which were received on this port.

This object is the number of frames (including error frames) with a length of between 256 and 511 octets inclusive which were received on this port.

This object is the number of frames (including error frames) with a length of between 512 and 1023 octets inclusive which were received on this port.

This object is the number of frames (including error frames) with a length of between 1024 and 1518 octets inclusive which were received on this port.

This is a high level 'smart MIB' object. This object provides a running average of the bandwidth in use. This value is calculated locally on the agent and so does not require processor bandwidth from the management station or occupy valuable network bandwidth communicating with that station. By default an agent supporting this parameter will exhibit the following characteristics: 1) The parameter will be recalculated at approx 15 second intervals 2) Every calculation period the device will read the value of mrmMonPortReadableOctets. 3) The calculation will be performed on the most recent 4 samples as follows: 4 Sum(sample(i)/(time(i) * K)) * 100/4 i=1 Sample(i) is mrmMonPortReadableOctets(i)-mrmMonPortReadableOctets(i-1) time(i) is the time between sample(i-1) and sample(i) K is the max bytes per unit time (i.e. the available bandwidth K depends on the ring speed. The value is expressed as a percentage. A default threshold exists on this average so that if a calculated average exceeds 15% a trap will be sent to the management station. Further traps will not be sent until the average drops to below 10%. A particular device may provide a means of changing the number of samples, the averaging period, threshold and threshold action if it so wishes.

This is a high level 'smart MIB' object. This object provides a running average of the number of errors per 10000 packets. This is an error rate, and is calculated over the number of packets received in the sample periods, and not on every 10000 packets. This value is calculated locally on the agent and so does not require processor bandwidth from a management station or occupy valuable network bandwidth communicating with that station. By default an agent supporting this parameter will exhibit the following behaviour: 1) The parameter will be recalculated at approx 15 second intervals. 2) Every calculation period the device will read the value of mrmMonPortTotalErrors and mrmMonPortReadableFrames. 3) The calculation will be performed on the most recent 4 samples as follows: 4 Sum(Errors(i)/Frames(i)) * 10000/4 i=1 Errors(i) = mrmMonPortTotalErrors(i)-mrmMonPortTotalErrors(i-1) Frames(i) = mrmMonPortReadableFrames(i)-mrmMonPortReadableFrames(i-1) The value is an integer number of errors per 10,000 packets received by this repeater. A default threshold exists on this average so that if a calculated average exceeds 200 (i.e. 2% of frames are in error) a trap will be sent to the management station. Further traps will not be sent until the average drops to below 100 (i.e. 1% of frames are in error). A particular device may provide a means of changing the number of samples, the averaging period and threshold if it so wishes.

This attribute allows all counters on this Port to be cleared. If read this object will return noChangeCounters(1). Enumeration: 'clearCounters': 2, 'noChangeCounters': 1.

This is the last MAC address seen on this port.

This is a count of the number of times the MAC address on this port has changed. A high number of changes indicates this is either an inter-repeater link or a multi-drop segment.

This is a dummy 'smart MIB' object which is used internally by the agent to provide a running average of the bandwidth in use. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonPortBandwidthUsed'. See 'mrmMonPortBandwidthUsed' for a description of how the bandwidth used is calculated.

This is a dummy 'smart MIB' object which is used internally by the agent to provide a running average of the error rate. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonPortErrorsPer10000Packets'. See 'mrmMonPortErrorsPer10000Packets' for a description of how the error rate is calculated.

This is a smart MIB object which is used internally by the agent to provide a running average of the bandwidth in use. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonRepeaterBandwidthUsed'. See 'mrmMonRepeaterBandwidthUsed' for a description of how the bandwidth used is calculated.

This is a smart MIB object which is used internally by the agent to provide a running average of the error rate. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonRepeaterErrorsPer10000Packets'. See 'mrmMonRepeaterErrorsPer10000Packets' for a description of how the error rate is calculated.

This is a smart MIB object which is used internally by the agent to provide a running average of the bandwidth in use. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonCardBandwidthUsed'. See 'mrmMonCardBandwidthUsed' for a description of how the bandwidth used is calculated.

This is a smart MIB object which is used internally by the agent to provide a running average of the error rate. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonCardErrorsPer10000Packets'. See 'mrmMonCardErrorsPer10000Packets' for a description of how the error rate is calculated.

This is a smart MIB object which is used internally by the agent to provide a running average of the bandwidth in use. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonPortBandwidthUsed'. See 'mrmMonPortBandwidthUsed' for a description of how the bandwidth used is calculated.

This is a smart MIB object which is used internally by the agent to provide a running average of the error rate. It should not be accessed by a management station and is used by the logic which calculates the value of its associated object 'mrmMonPortErrorsPer10000Packets'. See 'mrmMonPortErrorsPer10000Packets' for a description of how the error rate is calculated.

In order to ensure a clean read of the Fault table this flag should be set to clean_read when commencing to read the table and should be examined after reading the entire table. If still set to clean_read then the table read is okay, if not the table should be re-read as it has been modified during the read process. Enumeration: 'clean-read': 1, 'modified': 2.

The Fault Table.

Information relating to a single fault.

The index into the Fault table. The initial read from the table should be read as the next, from an index of 0; subsequent reads should read the next from the index returned by the previous read.

This error number for this fault log entry.

The time since startup, in milliseconds, when the fault occurred.

The number of restarts at time of fault.

This table is used to provide remote device monitoring facilities. This table allows a list of network devices to be set up and polled regularly (or only once) by a variety of protocols. The table can be configured to inform the management station(s) of devices that are not responding to polls or that have started to respond after a period of silence. The minimum effort required to do a single poll is 1. In one packet, Write the address, rate=once-only(1) and RowStatus=CreateAndGo. 2. In the next packet, read the roundTripTime. The minimum effort required to monitor a device is 1. In one packet, Write the address, rate=every-30-seconds(1) and RowStatus=CreateAndGo. 2. Wait for traps to come in.

A table used to define device monitoring.

Unique identifier of a row in the Poll Table. The actual number of rows that can be created on any particular device depends on the memory and processing resources available at the time.

This DisplayString is the network address of the device to monitor. Typically this is an IP, MAC or IPX address. The following formats can be used. IP nnn.nnn.nnn.nnn - dotted format IPX AABBCCDD:AABBCCDDEEFF - network : node

This defines the protocol to use with which to monitor the device. Writing an address to the pollAddress field causes a default pollProtocol value to be setup. The default value is derived from the format of the address - four bytes means ip(2), and 10 bytes means ipx(3) addresses. If the requested protocol is not supported or is not compatible with the pollAddress, then an error is returned when an attempt is made to set the RowStatus to active or notInService. Enumeration: 'llc': 5, 'unknown': 1, 'ipx': 3, 'learn': 4, 'ip': 2.

This defines how often a poll packet is sent to the device. If once-only(1) is chosen, then when the RowStatus is set to active, a single poll packet is to be sent. There are no re-transmissions and no traps are generated. The results of the operation can be read in the pollLastPollSent and pollRoundTripTime fields. When a reply to the poll is received, then the RowStatus is changed to notInService. For the other values, setting the RowStatus to active causes the device to be regularly polled. The operation of the poll can be monitored by reading the pollLastPollSent and pollRoundTripTime fields. After four un-successful polls a pollLostContact trap is generated. The next successful poll to the device causes a pollEstablishedContact trap to be generated. Changing RowStatus from the active state causes polling to stop - in particular changing RowStatus from active to notInService (and vice-versa) is a convenient way of stopping and starting the polls. A poll is said to have been un-successful, if no reply has been received by the time the device is due to be polled again - i.e. if the pollRoundTripTime is still zero. By convention, row 1 of the PollTable is only ever used for once-only(1) polls. The facilities of the RMON Alarm and RMON Event groups are used when regular polling is taking place. These groups perform the timing, threshold checking and trap generation. Enumeration: 'every-hour': 6, 'once-only': 1, 'every-30-minutes': 5, 'every-30-seconds': 2, 'every-5-minutes': 4, 'every-minute': 3.

This field is provided solely for the purpose of the Network Management station to allow extra information to be stored about this poll table entry. This value is not used by the device. Enumeration: 'file-server': 2, 'other': 1.

Reading this variable returns the sysUpTime at which the last poll was sent to the device. A value of 0 means that no polls have been sent or that the poll could not be sent e.g. protocol error.

This is the round trip time in milli-seconds of the most recent poll to the pollAddress device. A value of 0 means that no reply has been received from the last poll. Round trip times of less than one hundred of a second are reported with the value of 10 milli-seconds.

After each successful poll, this field is updated with some protocol specific information that was gleaned from the packet exchange. For the IPX protocol, this string contains the number of router hops made by the poll response packet. For the IP protocol, this string contains the value of Time-To-Live from the IP packet header.

This is a value of alarmIndex from the RMON Alarm Table. The alarm indicated is being used by the PollTable to provide the timing and trap generation facilities. If this value is 0, then no alarm is associated with this PollTable entry.

The RMON OwnerString conventions are used here to help control the multi-manager situations. This data type is used to model an administratively assigned name of the owner of a resource. This information is taken from the NVT ASCII character set. It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'. SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties.

The SNMPv2 RowStatus convention. Notes: 1) Writing any data to a destroyed row, changes its state to notReady. 2) If the status is active or notInService and any of the configuration parameters are changed, then the polling stops and the status is set to notReady. Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

Indicates the the next value of pollIndex which can be used to create the next poll entry. This value is set to zero if there are no free rows in the table.

Indicates whether a Resilient Backup Power Supply is being used by this stack of units. Enumeration: 'notPresent': 1, 'present': 2.

Supplies all the information about the power supplies attached to each unit in a stack. This object is provided to speed up processing by Network Manager applications. There is one octet for each unit in the stack. Each octet contains the following information: Bit 1: RBS applicable ( 1 = Yes, 0 = No ) Bit 2: RBS present ( 1 = Yes, 0 = No ) Bit 3: RBS status ( 1 = fault, 0 = OK ) ( RBS = Resilient Backup Power Supply ) If Bit 1 is zero, this means that an RBS cannot be attached to this unit and all the other bits will be zero.

This table provides power supply status information for all units in an FMS stack.

Each Table entry provides information for a single unit in the stack.

Identifies which FMS unit (1-8) the table entry relates to.

This indicates whether a Resilient Power Supply is attached to this unit. A value of rbsNotApplicable indicates that this unit does not support Resilient Power Supplies, rbsPresent indicates that a RBS is attached and in use, rbsNotPresent indicates that this unit is using it's internal supply. Enumeration: 'rbsNotPresent': 3, 'rbsNotApplicable': 1, 'rbsPresent': 2.

This indicates the status of a Resilient Power Supply attached to this unit. A value of rbsNotApplicable indicates that this unit does not support Resilient Power Supplies, rbsok indicates that the attached RBS is functioning with no faults, rbsFault indicates that the RBS has a fault e.g. fan has failed or switched power supplies. Enumeration: 'rbsOK': 2, 'rbsNotApplicable': 1, 'rbsFault': 3.

The deprRptrHealth trap conveys information related to the operational state of the repeater. This trap is sent only when the oper status of the repeater changes. The deprRptrHealth trap must contain the deprRptrOperStatus variable. The agent may optionally include the deprRptrHealthText variable in the varBind list. See the deprRptrOperStatus and deprRptrHealthText objects for descriptions of the information that is sent. The agent must throttle the generation of consecutive deprRptrHealth traps so that there is at least a five-second gap between them.

This trap is sent when a change occurs in the group structure of a repeater. This occurs only when a group is logically removed from or added to a repeater. The varBind list contains the identifier of the group that was removed or added. The agent must throttle the generation of consecutive deprRptrGroupChange traps for the same group so that there is at least a five-second gap between them.

The deprRptrReset trap conveys information related to the operational state of the repeater. This trap is sent on completion of a repeater reset action. A repeater reset action is defined as an a transition to the START state of Fig 9-2 in section 9 [11], when triggered by a management command (e.g., an SNMP Set on the deprRptrReset object). The agent must throttle the generation of consecutive deprRptrReset traps so that there is at least a five-second gap between them. The deprRptrReset trap is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the deprRptrHealth variables as optional variables with its coldStart and warmStart trap PDUs. The deprRptrOperStatus variable must be included in the varbind list sent with this trap. The agent may optionally include the deprRptrHealthText variable as well.

Generated at a regular interval to inform the manager this device is still operating and can be reached on the network.

A local management update trap indicates that the configuration of the device has been modified via the ascii agent. This may be through Telnet or the V24 port.

A security violation trap indicates that a user has attempted to login and failed to enter the correct password Three times consecutively.

Generated when the Alarm value for this Alarm crosses the Threshold Level.

Generated when the Alarm value for this Alarm crosses the Recovery Level.

When a system load is requested, a response is returned immediately and the load proceeds in the background. If an error is detected this trap is generated indicating the reason why in the status, as follows:- (1) file not found; (2) access violation; (4) illegal TFTP operation; (5) unknown transfer ID; (7) no such user; (8) no response from the load server; (9) the download could not be started because of a lack of resources; (10) the length of a record differs from that implied by the value of the record length field; (11) the record type is not recognised; (12) record checksum error; (13) the device type in the file is incorrect; (14) the software image is not suitable for this version of the hardware; (15) the first record in the file was not a file header; (16) The byte count reported in the file trailer record differed from the number of bytes actually received; (200) the load file contained a load address which was outside the valid range of memory; (201) the load data was corrupted as it was transferred from the management agent to the subsidiary module; (202) the management agent timed out while waiting for a response from the subsidiary module; (203) the subsidiary module was unable to accept a command from the management agent; (204) the subsidiary module was removed during the download; (205) the download could not continue because of a lack of resources; (255) the subsidiary module failed during the download. When loading a new image into the device containing the agent itself, the agent first reads the beginning of the image file to test if it is accessible and contains a valid image. If there is anything wrong, this trap is generated, no download is performed and the device continues to run uninterrupted. If this check is successful the download proper is begun. Should that fail, it is simply retried continuously until either an attempt succeeds or the device is reset.

When the end-station table moves from the noChange to modified state this trap is generated. The trap is sent once on this transition and not subsequently until the 'Database State' is changed back to 'noChange' by a manager.

When the end-station table becomes full this trap is generated.

This trap is sent whenever a managed MAU enters the jabber state. The agent must throttle the generation of consecutive deprRpMauJabberTraps so that there is at least a five-second gap between them.

This trap indicates that the mau for this port has entered or left rpMauMediaAvailable = available(3) state.

This trap indicates that the repeater SM for this port has entered or left the partitioned state.

This trap is sent when the partition state of a port changes. The trap is accompanied by the new partition state of the port.

This trap is sent when the link state of a port changes. The var-bind identifies which port has changed state and what the new state of that port is.

This trap is only sent when the administration state of a port is changed by a gauge. It is not sent if a user initiates a state change via SNMP, Telnet or the V.24 terminal interface.

This trap is sent when the port bandwidth used exceeds the defined threshold. This threshold is by default 15%, although this may have been changed on a particular device.

This trap is sent when the errors per packet exceeds the the defined threshold.

This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated. Generation of this trap is summarised in the following table: ------------------------------------------------------------------------------ State | Event Main Backup |Main Fail |Main OK |StandBy Fail |Standby OK ------------------------------------------------------------------------------ Active OK | switch | ----- | state | ----- Active Fail | state | ----- | ----- | state OK Active | state | ----- | switch | ----- Fail Active | ----- | state | state | ----- Fail Fail | ----- | switch | ----- | state ----------------------------------------------------------------------------- In this table '-----' indicates no trap is sent. 'switch' indicates the resResilienceSwitch trap is sent and 'state' indicates resStateChange is sent. NOTE: The agent in the MSH does not suppress any traps that caused the state change. For example if the active link is lost then both a 'loss-of-link' trap AND a resilienceSwitch trap are generated.

This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated. Generation of this trap is summarised in the following table: ------------------------------------------------------------------------------ State | Event Main Backup |Main Fail |Main OK |StandBy Fail |Standby OK ------------------------------------------------------------------------------ Active OK | switch | ----- | state | ----- Active Fail | state | ----- | ----- | state OK Active | state | ----- | switch | ----- Fail Active | ----- | state | state | ----- Fail Fail | ----- | switch | ----- | state ----------------------------------------------------------------------------- In this table '-----' indicates no trap is sent. 'switch' indicates the resResilienceSwitch trap is sent and 'state' indicates resStateChange is sent. NOTE: The agent in the MSH does not suppress any traps that caused the state change. For example if the active link is lost then both a 'loss-of-link' trap AND a resilienceSwitch trap are generated.

This trap is generated when the PollTable in the managed agent receives a reply to a poll after a sequence of four or more un-successful polls.

This trap is generated when the PollTable in the managed agent fails to receive a reply to four successive polls.

This trap indicates that a Resilient Backup Power Supply connected to this repeater has developed a fault. This fault has not stopped the RBS from functioning e.g. fan failed, unit overheating, or unit has switched to resilient power supply.

This trap indicates that a Resilient Backup Power Supply connected to this repeater has recovered from and outstanding fault.

This trap is sent when an unrecognised MAC address appears on the port. It is only sent if DUD is set on the port.

This trap is sent when the repeater bandwidth used exceeds the defined threshold. This threshold is by default 15%, although this may have been changed on a particular device.

This trap is sent when the repeater errors per packet exceeds the the defined threshold.

This trap is sent when the card bandwidth used exceeds the defined threshold. This threshold is by default 15%, although this may have been changed on a particular device.

This trap is sent when the errors per packet exceeds the the defined threshold.