Novell-Hub-Ethernet-MIB: View SNMP OID List / Download MIB

Status information and control variables for a collection of repeaters in a particular system.

Status information and control variables for a particular repeater in the system.

The value of rptrID is assigned so as to uniquely identify a repeater in a system where a single agent manages multiple repeaters.

A 24-bit value that identifies the manufacturer.

Manufacturer-defined product identifier. Its format and size are unrestricted.

Manufacturer-defined product revision designation. Its format and size are unrestricted.

The rptrBasGroupCapacity 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 rptrBasGroupCapacity. Some groups may not be present in a given repeater instance, in which case the actual number of groups present will be less than rptrBasGroupCapacity. The number of groups present will never be greater than rptrBasGroupCapacity. 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.

This octet string represents the current configuration of groups, encoded as a bit string. Each group is represented by a single bit. When the value of a bit=1, it indicates that the group represented by that bit is present in the repeater; when zero, the group is not present. Note: The bitstring mapping text below does not match the IETF conventions, and will be modified appropriately. The number of octets in the string is rptrBasGroupCapacity divided by 8, rounded up to the next whole number of octets. For example, if rptrBasGroupCapacity is 12, the octet string returned by the agent will be of length two. The first octet will encode the configuration of groups 1-8, where group one is represented by the least significant bit of the octet. The second octet will likewise encode groups 9-16. In general, octet i encodes groups (8i-7) through (8i), where (8i-7) is represented by the least significant bit and (8i) by the most significant bit of the octet.

The health state object indicates the operational state of the repeater. The rptrBasHealthData and rptrBasHealthText objects 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, 'rptrFailure': 3, 'portFailure': 5, 'other': 1, 'groupFailure': 4.

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.

The health data object is a block of data octets that provides information relevant to the operational state of the repeater. The encoding of this data block is agent-dependent. Agents may use this mechanism to provide detailed failure information or instructions for problem resolution.

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 rptrBasSelfTest2. As a result of this action a rptrReset trap will 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 rptrHealth 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.

Setting this variable to selfTest(2) causes the repeater to perform a agent-specific, disrupt)ve self-test that has the following characteristics: (1) The nature of the tests is not specified. (2) The test resets the repeater but without affecting management information about the repeater. (3) The test does not inject packets onto any segment. (4) Packets received during the test may or may not be relayed. 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 rptrHealth 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.

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 repeater containing the group for which this entry contains information.

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

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 contains the value of sysUpTime at the time that the management information relating to this group was last reset. A value of zero would indicate that the group was present when the agent last restarted. A non-zero value would indicate that the group had been added to the repeater after the agent last restarted.

The rptrBasGroupNumOfPorts is the number of ports contained within the group. Valid range is 1- 1024. Within each group, the ports are uniquely numbered in the range from 1 to rptrBasGroupNumOfPorts. 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 repeater containing the port for which this entry contains information.

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 rptrBasGroupNumOfPorts for the associated group.

Setting this variable to disabled(1) 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 state takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this variable to enabled(2) enables the port and exerts a BEGIN on the port's auto- partition state machine. Note: What the above means is that when a port becomes disabled, its current auto-partition state is frozen until the port is next enabled. When the port becomes enabled, the auto-partition state becomes notAutoPartitioned, regardless of its pre-disabling state. This text will be clarified in the next draft. Enumeration: 'disabled': 1, 'enabled': 2.

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.

Statistics for a collection of repeaters in a particular system.

An entry in the table, containing statistics for a single repeater.

This variable identifies the repeater for which this entry contains monitor information.

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.

The repeater MJLPs object counts the number of times the repeater enters the DISABLE OUTPUT state in the MAU Jabber Lockup Protection state diagram (Fig. 9-5) [11]. Note: The approximate minimum time for counter rollover is 200 days.

Table of performance and error statistics for the ports.

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

Repeater ID for identifying the port.

Group ID for identifying the port.

Port ID for identifying the port.

A representation of the total frames of valid frame length. 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 (Ref: 4.4.2.1 [11]) and for which FCSError is not asserted. Note: The approximate minimum time between counter rollovers is 81 hours.

Increment counter by OctetCount for each frame which which has been determined to be a readable frame. Note: The approximate minimum time between counter rollovers is 58 minutes.

Increment counter by one for each frame with FCSError and without FramingError and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1 [11]). Note: The approximate minimum time between counter rollovers is 81 hours.

Increment counter by one for each frame with FCSError and FramingError and whose octetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1 [11]). Note: The approximate minimum time between counter rollovers is 81 hours.

Increment counter by one for each frame whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1 [11]). Note: The approximate minimum time between counter rollovers is 61 days.

Increment counter by one for each carrier event whose ActivityDuration is greater than ShortEventMinTime and less than ShortEventMaxTime. ShortEventMinTime represents any event of sufficient duration to initiate transmission by a repeater. ShortEventMaxTime is greater than 7.4uS and less than 8.2uS. 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 an externally generated noise hit which will cause the relay 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. Such shortEvents are not a feature of normal network activity. Also it should be noted that a MAU that is attached to a coax segment may have several carrier dropouts on the DI circuit before the CI circuit is active and stable. Such dropouts will increment the shortEvent counter but are considered normal for a coax segment.

Increment counter by one for each carrier event whose ActivityDuration is greater than ShortEventMaxTime and less than RuntMaxTime. RuntMaxTime is greater than 53.2uS and less than 56.0uS. An event whose length is greater than 7.4uS but less than 8.2uS shall increment either the ShortEvent object or the runts object but not both. A non-collision event greater than 53.2uS but less than 56.0uS may or may not be counted as a runt. A non-collision event greater than or equal to 56.0uS shall not be counted as a Runt. RuntMaxTime 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: Runts do not indicate a problem in the network. The approximate minimum time for counter rollover is 16 hours.

Increment counter by one for each carrier event in which the CIPresent(X) variable has the value SQE (see 9.6.6.2 [11]). Note: The approximate minimum time for counter rollover is 16 hours.

Increment counter by one for each carrier event in which the CIPresent(X) variable has the value SQE (see 9.6.6.2 [11]) at any time when the ActivityDuration is greater than the RuntMaxTime. A late collision is counted twice, as both a collision and as a late collision. LateCollisionThreshold 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: The approximate minimum time between counter rollovers is 81 hours.

The dataRateMismatches object counts the number of times that a packet has been received by this port with the transmission frequency (data rate) detectably mismatched from the local transmit frequency. The exact degree is implementation- specific and is to be defined by the implementor for conformance testing. Note: Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.

The autoPartitions object counts the number of times that the repeater has automatically partitioned this port. The conditions that cause port partitioning are specified in partition state machine in Sect. 9 [11]. They are not differentiated here. Note: The approximate minimum time between counter rollovers is 20 days.

The veryLongEvents object counts the number of times a packet has been received by this port that was so long that the repeater was forced to go into a jabber protection condition. Note: The approximate minimum time for counter rollover is 200 days.

Table of address mapping information about the ports.

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

Repeater ID for identifying the port.

Group ID for identifying the port.

Port index for identifying the port.

The lastSourceAddress object is the source address of the last readable frame (i.e., counted by rptrMonPortReadableFrames) received by this port.

The rptrAddrSourceAddressChanges object counts the number of the times that the rptrAddrLastSourceAddress for this port has changed. Note: This may indicate whether a link is connected to a single DTE or another multi-user segment. The approximate minimum time for counter rollover is 81 hours.

Extended statistics for a collection of repeaters in a particular system.

An entry in the table, containing extended statistics for a single repeater.

This variable identifies the repeater for which this entry contains monitor information.

This counter is incremented by one for each octet repeated, including the 8 octets of preamble and the FCS for any packet, whether the FCS was correct or not. Note: The approximate minimum time between counter rollovers is 58 minutes.

A textual name administratively assigned to this repeater.

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 repeater containing the group for which this entry contains information.

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

The number of the slot in which the group card resides. A negative value signifies that the slot number is not known.

The number of the chassis in which the group card resides. A zero value signifies that the chassis number is not known.

Table of descriptive and status information about the ports.

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

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

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 rptrBasGroupNumOfPorts for the associated group.

A value indicating the current state of the link attached to the port. The possible values are: linkDown(1) The link pulses are not being received by the port. linkUp(2) The link pulses are being received by the port. notApplicable(3) The port is an AUI or other non-10BaseT port. Enumeration: 'linkUp': 2, 'linkDown': 1, 'notApplicable': 3.

A textual name administratively assigned to this port.

The login name of the user currently logged in, via this port, to the server containing this repeater; otherwise, the null string

The segment to which the port belongs.

The rptrHealth trap conveys information related to the operational state of the repeater. This trap is sent only when the health state of the repeater changes.

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 updated value of the rptrBasGroupMap variable.

The rptrReset trap conveys information related to the operational state of the repeater. This trap is sent on completion of a repeater reset action.