VERTICAL-SNMP-REPEATER-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for VERTICAL-SNMP-REPEATER-MIB.
79
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
79 total| Object Name |
|---|
vsnmpDot3RptrMgt OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4 |
RFC-1215 Unknown .1.3.6.1.4.1.2338.4 |
vrptrBasicPackage OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.1 |
vrptrGroupInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.1.2 |
vrptrGroupTableTable of descriptive and status information about
the groups of ports. SEQUENCE OF VRptrGroupEntry .1.3.6.1.4.1.2338.4.1.2.1 |
vrptrGroupEntryAn entry in the table, containing information
about a single group of ports. VRptrGroupEntry .1.3.6.1.4.1.2338.4.1.2.1.1 |
vrptrGroupIndexThis object identifies the group within the
system for which this entry contains
information.ro INTEGER .1.3.6.1.4.1.2338.4.1.2.1.1.1 |
vrptrGroupObjectIDThe vendor's authoritative identification of the
group. This value may be 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 object 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.'ro OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.1.2.1.1.3 |
vrptrGroupOperStatusAn object that indicates the operational status
of the group.
A status of notPresent(4) indicates that the group
is temporarily or permanently physically and/or
logically not a part of the repeater. It is an
implementation-specific matter as to whether the
agent effectively removes notPresent entries from
the table.
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.ro Enumeration .1.3.6.1.4.1.2338.4.1.2.1.1.4 |
vrptrGroupPortCapacityThe rptrGroupPortCapacity is the number of ports
that can be contained within the group. Valid
range is 1-2147483647. Within each group, the
ports are uniquely numbered in the range from 1 to
vrptrGroupPortCapacity.
Some ports may not be present in the system, in
which case the actual number of ports present
will be less than the value of rptrGroupPortCapacity.
The number of ports present in the group will never
be greater than the value of rptrGroupPortCapacity.
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.ro INTEGER .1.3.6.1.4.1.2338.4.1.2.1.1.6 |
vrptrGroupSlotNumberThe physical slot number in the Vertical's InstantOffice
box that this repeater group resides.ro INTEGER .1.3.6.1.4.1.2338.4.1.2.1.1.7 |
vrptrGroupBroadcastDomainNumberThis object indicates the repeater's
broadcast domain. A broadcast domain is
an Ethernet segment or set of segments
throughout which a broadcast frame will
be transmitted. The segments may be
separated by repeaters or switches, but
not routers. This value will be 0 if the
broadcast domain number is unknown.ro INTEGER .1.3.6.1.4.1.2338.4.1.2.1.1.8 |
vrptrGroupNetworkAdapterNumberThis object indicates the identification
number of the InstantOffice network adapter
associated with the repeater, if any. This
value will be 0 if the repeated domain
number is unassociated or unknown.ro INTEGER .1.3.6.1.4.1.2338.4.1.2.1.1.9 |
vrptrGroupLedStatusThis object indicates the status of the
card LEDs. The LED status is shown for
any card that has an Ethernet interface.
Valid values are unknown (1), none(2),
green(3), red(4) and greenRed(5). A status
of unknown(1) indicates that the LED status
is not available from the hardware and
could not be determined from the card's state.
A status of greenRed(5) indicates that both
the green and red LEDs are ON. A status
of none(2) indicates neither the green
nor the red LED is ON. However, note that
the green LED on the Resource Switch Card
blinks every second to indicate an active
Fault Monitor, and therefore, if this value
is requested during the short period when
the green LED is off, it will indicate that
it is off.ro Enumeration .1.3.6.1.4.1.2338.4.1.2.1.1.10 |
vrptrGroupExternalPortCapacityThe rptrGroupExternalPortCapacity is similar to,
and typical equal to, rptrGroupPortCapacity.
External ports are those which extrude from the
front faceplate. Non-external ports may be used
for internal subsystems or testing, but which
are useful for statistic purposes.
External ports will always be listed first in
the group, and thus non-external ports are listed
with higher port numbers.ro INTEGER .1.3.6.1.4.1.2338.4.1.2.1.1.11 |
vrptrPortInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.1.3 |
vrptrPortTableTable of descriptive and status information about
the repeater ports in the system. The number of
entries is independent of the number of repeaters
in the managed system. SEQUENCE OF VRptrPortEntry .1.3.6.1.4.1.2338.4.1.3.1 |
vrptrPortEntryAn entry in the table, containing information
about a single port. VRptrPortEntry .1.3.6.1.4.1.2338.4.1.3.1.1 |
vrptrPortGroupIndexThis object identifies the group containing the
port for which this entry contains information.ro INTEGER .1.3.6.1.4.1.2338.4.1.3.1.1.1 |
vrptrPortIndexThis object identifies the port within the group
for which this entry contains information. This
identifies the port independently from the repeater
it may be attached to. The numbering scheme for
ports is implementation specific; however, this
value can never be greater than
rptrGroupPortCapacity for the associated group.ro INTEGER .1.3.6.1.4.1.2338.4.1.3.1.1.2 |
vrptrPortAdminStatusSetting 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
rptrPortAutoPartitionState for that port is frozen
until the port is next enabled. When the port
becomes enabled, the rptrPortAutoPartitionState
becomes notAutoPartitioned(1), regardless of its
pre-disabling state.)rw Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.3 |
vrptrPortAutoPartitionStateThe 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 Sections
9 and 27 of [IEEE 802.3 Std]. They are not
differentiated here.ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.4 |
vrptrPortOperStatusThis object indicates the port's operational
status. The notPresent(3) status indicates the
port is physically removed (note this may or may
not be possible depending on the type of port.)
The operational(1) status indicates that the port
is enabled (see rptrPortAdminStatus) and working,
even though it might be auto-partitioned (see
rptrPortAutoPartitionState).
If this object has the value operational(1) and
rptrPortAdminStatus is set to disabled(2), it is
expected that this object's value will soon change
to notOperational(2).ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.5 |
vrptrPortRptrIdThis object identifies the repeater to
which this port belongs. The repeater
identified by a particular value of this object
is the same as that identified by the same
value of rptrInfoId. A value of zero
indicates that this port currently is not
a member of any repeater.ro INTEGER .1.3.6.1.4.1.2338.4.1.3.1.1.6 |
vrptrPortLinkStateDescribes whether there is link on
this port or not:
link = 1
noLink = 2ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.7 |
vrptrPortSpeedSpecifies the ethernet speed of this
particular port. Valid values are :
unknown = 1,
10-MBPS =2 (10MB per second),
100-MBPS = 3 (100 MB per second)ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.8 |
vrptrPortSpeedSelectThis object indicates the selection used
by the port for negotiating the Ethernet
speed. If automatic is selected, the
highest supported speed will be negotiated.
Currently, this variable is read-only.
Valid values are :
speed-select-auto = 1,
speed-select-10 = 2 (10MB per second),
speed-select-100 = 3 (100 MB per second)ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.9 |
vrptrPortDuplexThis object indicates the duplex of the
Ethernet port. Valid values are :
unknown = 1,
half = 2,
full = 3ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.10 |
vrptrPortDuplexSelectThis object indicates the selection used
by the port for negotiating the Ethernet
duplex. If automatic is selected, the
best supported duplex will be negotiated.
This is currently a read-only variable.
Valid values are :
duplex-select-auto = 1,
duplex-select-half = 2,
duplex-select-full = 3ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.11 |
vrptrPortPolarityThis object indicates the polarity of the
Ethernet cable. If the polarity is crossed,
the repeater may compensate for it, but it
indicates a wiring problem with the
attached Ethernet device. Valid values are :
unknown = 1,
straight = 2,
crossed = 3ro Enumeration .1.3.6.1.4.1.2338.4.1.3.1.1.12 |
vrptrAllRptrInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.1.4 |
vrptrInfoTableA table of information about each
non-trivial repeater. The number of entries
depends on the physical configuration of the
managed system. SEQUENCE OF VRptrInfoEntry .1.3.6.1.4.1.2338.4.1.4.1 |
vrptrInfoEntryAn entry in the table, containing information
about a single non-trivial repeater. VRptrInfoEntry .1.3.6.1.4.1.2338.4.1.4.1.1 |
vrptrInfoIdThis object identifies the repeater for which
this entry contains information.ro INTEGER .1.3.6.1.4.1.2338.4.1.4.1.1.1 |
vrptrInfoRptrTypeThe rptrInfoRptrType returns a value that
identifies the CSMA/CD repeater type. The
value 5 (tenMbOrOnehundredMb) is a Vertical
Network extension specifying 10/100 MB
repeater which contains mixed 10Mb and
100 Mb ports.ro Enumeration .1.3.6.1.4.1.2338.4.1.4.1.1.2 |
vrptrInfoOperStatusThe rptrInfoOperStatus object indicates the
operational state of the repeater.ro Enumeration .1.3.6.1.4.1.2338.4.1.4.1.1.3 |
vrptrInfoResetSetting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
Setting this object to noReset(1) has no effect.
The agent will always return the value noReset(1)
when this object is read.
After receiving a request to set this variable to
reset(2), the agent is allowed to delay the reset
for a short period. For example, the implementor
may choose to delay the reset long enough to allow
the SNMP response to be transmitted. In any
event, the SNMP response must be transmitted.
This action does not reset the management counters
defined in this document nor does it affect the
portAdminStatus parameters. Included in this
action is the execution of a disruptive Self-Test
with the following characteristics: a) The nature
of the tests is not specified. b) The test resets
the repeater but without affecting management
information about the repeater. c) The test does
not inject packets onto any segment. d) Packets
received during the test may or may not be
transferred. e) The test does not interfere with
management functions.
After performing this self-test, the agent will
update the repeater health information (including
rptrInfoOperStatus), and send a rptrInfoResetEvent
notification.rw Enumeration .1.3.6.1.4.1.2338.4.1.4.1.1.4 |
vrptrInfoPartitionedPortsThis object returns the total number of ports in
the repeater whose current state meets all three
of the following criteria: rptrPortOperStatus
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1), and
rptrPortAutoPartitionState is autoPartitioned(2).ro Gauge .1.3.6.1.4.1.2338.4.1.4.1.1.5 |
vrptrInfoLastChangeThe value of sysUpTime when any of the following
conditions occurred:
1) agent cold- or warm-started;
2) this instance of repeater was created
(such as when a device or module was
added to the system);
3) a change in the value of rptrInfoOperStatus;
4) ports were added or removed as members of
the repeater; or
5) any of the counters associated with this
repeater had a discontinuity.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.2338.4.1.4.1.1.6 |
vrptrMonitorPackage OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.2 |
vrptrMonitorPortInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.2.3 |
vrptrMonitorPortTableTable of performance and error statistics for the
ports. The number of entries is the same as that
in the rptrPortTable.
The columnar object rptrMonitorPortLastChange
is used to indicate possible discontinuities
of counter type columnar objects in the table. SEQUENCE OF VRptrMonitorPortEntry .1.3.6.1.4.1.2338.4.2.3.1 |
vrptrMonitorPortEntryAn entry in the table, containing performance and
error statistics for a single port. VRptrMonitorPortEntry .1.3.6.1.4.1.2338.4.2.3.1.1 |
vrptrMonitorPortGroupIndexThis object identifies the group containing the
port for which this entry contains information.ro INTEGER .1.3.6.1.4.1.2338.4.2.3.1.1.1 |
vrptrMonitorPortIndexThis object identifies the port within the group
for which this entry contains information.ro INTEGER .1.3.6.1.4.1.2338.4.2.3.1.1.2 |
vrptrMonitorPortReadableFramesThis 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.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
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 at 10Mb/s.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.3 |
vrptrMonitorPortReadableOctetsThis 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 (i.e., including
FCS octets but excluding framing bits and dribble
bits).
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
This statistic provides an indicator of the total
data transferred. The approximate minimum time
for rollover of this counter in a 10Mb/s repeater
is 58 minutes.
For ports receiving traffic at a maximum rate in
a 100Mb/s repeater, this counter can roll over
in less than 6 minutes. Since that amount of time
could be less than a management station's poll cycle
time, in order to avoid a loss of information a
management station is advised to also poll the
rptrMonitorPortUpper32Octets object, or to use the
64-bit counter defined by
rptrMonitorPortHCReadableOctets instead of the
two 32-bit counters.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.4 |
vrptrMonitorPortFCSErrorsThis 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).
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 80 hours at 10Mb/s.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.5 |
vrptrMonitorPortAlignmentErrorsThis 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.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 80 hours at 10Mb/s.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.6 |
vrptrMonitorPortFrameTooLongsThis 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 rptrMonitorPortFrameTooLongs is incremented
then neither the rptrMonitorPortAlignmentErrors
nor the rptrMonitorPortFCSErrors counter shall be
incremented for the frame.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 61 days in a 10Mb/s repeater.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.7 |
vrptrMonitorPortShortEventsThis 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.
Notes:
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 significance of this attribute is different
in 10 and 100 Mb/s collision domains. Clause 9
repeaters perform fragment extension of short
events which would be counted as runts on the
interconnect ports of other repeaters. Clause
27 repeaters do not perform fragment extension.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 16 hours in a 10Mb/s repeater.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.8 |
vrptrMonitorPortRuntsThis 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 collision fragments may exceed
ValidPacketMinTime.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 16 hours in a 10Mb/s repeater.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.9 |
vrptrMonitorPortCollisionsFor a clause 9 repeater, this counter is
incremented by one for any CarrierEvent signal
on any port for which the CollisionEvent signal
on this port is asserted. For a clause 27
repeater port the counter increments on entering
the Collision Count Increment state of the
partition state diagram (fig 27-8 of
[IEEE 802.3 Std]).
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 16 hours in a 10Mb/s repeater.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.10 |
vrptrMonitorPortLateEventsFor a clause 9 repeater port, 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. For a clause 27 repeater
port, this counter is incremented by one on
entering the Collision Count Increment state
of the partition state diagram (fig 27-8)
while the ActivityDuration is greater than
the LateEvent- Threshold. 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.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 81 hours in a 10Mb/s repeater.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.11 |
vrptrMonitorPortVeryLongEventsFor a clause 9 repeater port, this counter
is incremented by one for each CarrierEvent
whose ActivityDuration is greater than the
MAU Jabber Lockup Protection timer TW3
(Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).
For a clause 27 repeater port, this counter
is incremented by one on entry to the
Rx Jabber state of the receiver timer state
diagram (fig 27-7). Other counters may
be incremented as appropriate.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.12 |
vrptrMonitorPortDataRateMismatchesThis counter is incremented by one for each
frame received by this port that meets all
of the conditions required by only one of the
following two measurement methods:
Measurement method A: 1) The CollisionEvent
signal is not asserted (10Mb/s operation) or
the Collision Count Increment state of the
partition state diagram (fig 27-8 of
[IEEE 802.3 Std]) has not been entered
(100Mb/s operation). 2) The ActivityDuration
is greater than ValidPacketMinTime. 3) The
frequency (data rate) is detectably mismatched
from the local transmit frequency.
Measurement method B: 1) The CollisionEvent
signal is not asserted (10Mb/s operation)
or the Collision Count Increment state of the
partition state diagram (fig 27-8 of
[IEEE 802.3 Std]) has not been entered
(100Mb/s operation). 2) The OctetCount is
greater than 63. 3) 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.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.3.1.1.13 |
vrptrMonitorPortAutoPartitionsThis counter is incremented by one for
each time the repeater has automatically
partitioned this port.
The conditions that cause a clause 9
repeater port to partition are specified in
the partition state diagram in clause 9 of
[IEEE 802.3 Std]. They are not differentiated
here. A clause 27 repeater port partitions
on entry to the Partition Wait state of the
partition state diagram (fig 27-8 in
[IEEE 802.3 Std]).
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.14 |
vrptrMonitorPortTotalErrorsThe 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:
vrptrMonitorPortFCSErrors,
vrptrMonitorPortAlignmentErrors,
vrptrMonitorPortFrameTooLongs,
vrptrMonitorPortShortEvents,
vrptrMonitorPortLateEvents,
vrptrMonitorPortVeryLongEvents,
vrptrMonitorPortDataRateMismatches, and
vrptrMonitorPortSymbolErrors.
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.
Note that rptrMonitorPortRunts is not included
in this total; this is because runts usually
indicate collision fragments, a normal network
event.
A discontinuity may occur in the value
when the value of object
vrptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.15 |
vrptrMonitorPortLastChangeThe value of sysUpTime when the last of
the following occurred:
1) the agent cold- or warm-started;
2) the row for the port was created
(such as when a device or module was added
to the system); or
3) any condition that would cause one of
the counters for the row to experience
a discontinuity.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.2338.4.2.3.1.1.16 |
vrptrMonitorPortSentFramesThis object is the number of frames of valid
frame length that have been sent on this port.
This counter is incremented by one for each frame
sent 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.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
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 at 10Mb/s.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.17 |
vrptrMonitorPortSentOctetsThis object is the number of octets contained in
valid frames that have been sent on this port.
This counter is incremented by OctetCount for each
frame sent on this port which has been
determined to be a readable frame (i.e., including
FCS octets but excluding framing bits and dribble
bits).
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
This statistic provides an indicator of the total
data transferred. The approximate minimum time
for rollover of this counter in a 10Mb/s repeater
is 58 minutes.
For ports receiving traffic at a maximum rate in
a 100Mb/s repeater, this counter can roll over
in less than 6 minutes. Since that amount of time
could be less than a management station's poll cycle
time, in order to avoid a loss of information a
management station is advised to also poll the
rptrMonitorPortUpper32SentOctets object, or to use the
64-bit counter defined by
rptrMonitorPortHCReadableOctets instead of the
two 32-bit counters.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.18 |
vrptrMonitorPortDroppedFramesThis counter is incremented by one for
each time the switch had dropped a frame
due a buffer full event.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.19 |
vrptrMonitorPortOtherErrorsThis counter is incremented by one for
each time the repeater has detected an
error which is not reported in any other
error counter. The frame may or may not
be lost due to the error.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.1.1.20 |
vrptrMonitor100PortTableTable of additional performance and error
statistics for 100Mb/s ports, above and
beyond those parameters that apply to both
10 and 100Mbps ports. Entries exist only for
ports attached to 100Mbps repeaters.
The columnar object rptrMonitorPortLastChange
is used to indicate possible discontinuities
of counter type columnar objects in this table. SEQUENCE OF VRptrMonitor100PortEntry .1.3.6.1.4.1.2338.4.2.3.2 |
vrptrMonitor100PortEntryAn entry in the table, containing performance
and error statistics for a single 100Mb/s port. VRptrMonitor100PortEntry .1.3.6.1.4.1.2338.4.2.3.2.1 |
vrptrMonitorPortIsolatesThis counter is incremented by one each time that
the repeater port automatically isolates as a
consequence of false carrier events. The conditions
which cause a port to automatically isolate are
defined by the transition from the False Carrier
state to the Link Unstable state of the carrier
integrity state diagram (figure 27-9)
[IEEE 802.3 Standard].
Note: Isolates do not affect the value of
the PortOperStatus object.
A discontinuity may occur in the value
when the value of object
vrptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.2.1.1 |
vrptrMonitorPortSymbolErrorsThis counter is incremented by one each time when
valid length packet was received at the port and
there was at least one occurrence of an invalid
data symbol. This can increment only once per valid
carrier event. A collision presence at any port of
the repeater containing port N, will not cause this
attribute to increment.
A discontinuity may occur in the value
when the value of object
rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this
counter is 7.4 hours at 100Mb/s.ro Counter .1.3.6.1.4.1.2338.4.2.3.2.1.2 |
vrptrMonitorPortUpper32OctetsThis object is the number of octets contained in
valid frames that have been received on this port,
modulo 2**32. That is, it contains the upper 32
bits of a 64-bit octets counter, of which the
lower 32 bits are contained in the
rptrMonitorPortReadableOctets object.
This two-counter mechanism is provided for those
network management protocols that do not support
64-bit counters (e.g. SNMP V1) and are used to
manage a repeater type of 100Mb/s.
Conformance clauses for this MIB are defined such
that implementation of this object is not required
in a system which does not support 100Mb/s.
However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.
A discontinuity may occur in the value
when the value of object
vrptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.2.1.3 |
vrptrMonitorPortUpper32SentOctetsThis object is the number of octets contained in
valid frames that have been sent on this port,
modulo 2**32. That is, it contains the upper 32
bits of a 64-bit octets counter, of which the
lower 32 bits are contained in the
rptrMonitorPortSentOctets object.
This two-counter mechanism is provided for those
network management protocols that do not support
64-bit counters (e.g. SNMP V1) and are used to
manage a repeater type of 100Mb/s.
Conformance clauses for this MIB are defined such
that implementation of this object is not required
in a system which does not support 100Mb/s.
However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.
A discontinuity may occur in the value
when the value of object
vrptrMonitorPortLastChange changes.ro Counter .1.3.6.1.4.1.2338.4.2.3.2.1.4 |
vrptrMonitorAllRptrInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2338.4.2.4 |
vrptrMonTableA table of information about each
non-trivial repeater. The number of entries
in this table is the same as the number of
entries in the rptrInfoTable.
The columnar object rptrInfoLastChange is
used to indicate possible discontinuities of
counter type columnar objects in this table. SEQUENCE OF VRptrMonEntry .1.3.6.1.4.1.2338.4.2.4.1 |
vrptrMonEntryAn entry in the table, containing information
about a single non-trivial repeater. VRptrMonEntry .1.3.6.1.4.1.2338.4.2.4.1.1 |
vrptrMonTxCollisionsFor a clause 9 (10Mb/s) repeater, 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 [IEEE 802.3 Std]).
For a clause 27 repeater, this counter is
incremented every time the repeater core state
diagram enters the Jam state as a result of
Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
The approximate minimum time for rollover of this
counter is 16 hours in a 10Mb/s repeater and 1.6
hours in a 100Mb/s repeater.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.4.1.1.1 |
vrptrMonTotalFramesThe number of frames of valid frame length
that have been received on the ports in this repeater
and for which the FCSError and CollisionEvent
signals were not asserted. If an implementation
can not obtain a count of frames as seen by
the repeater itself, this counter may be
implemented as the summation of the values of the
rptrMonitorPortReadableFrames counters for all of
the ports in the repeater.
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 in a 10Mb/s repeater.ro Counter .1.3.6.1.4.1.2338.4.2.4.1.1.3 |
vrptrMonTotalErrorsThe total number of errors which have occurred on
all of the ports in this repeater. The errors
included in this count are the same as those listed
for the rptrMonitorPortTotalErrors counter. If an
implementation can not obtain a count of these
errors as seen by the repeater itself, this counter
may be implemented as the summation of the values of
the rptrMonitorPortTotalErrors counters for all of
the ports in the repeater.ro Counter .1.3.6.1.4.1.2338.4.2.4.1.1.4 |
vrptrMonTotalOctetsThe total number of octets contained in the valid
frames that have been received on the ports in
this group. If an implementation can not obtain
a count of octets as seen by the repeater itself,
this counter may be the summation of the
values of the rptrMonitorPortReadableOctets
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 in a 10Mb/s repeater
is 58 minutes divided by the number of ports in
the repeater.
For 100Mb/s repeaters processing traffic at a
maximum rate, this counter can roll over in less
than 6 minutes divided by the number of ports in
the repeater. Since that amount of time could
be less than a management station's poll cycle
time, in order to avoid a loss of information a
management station is advised to also poll the
rptrMonUpper32TotalOctets object, or to use the
64-bit counter defined by rptrMonHCTotalOctets
instead of the two 32-bit counters.ro Counter SYNTAX INTEGER { notSupported(-1), supported(0) } .1.3.6.1.4.1.2338.4.2.4.1.1.5 |
vrptrMon100TableA table of additional information about each
100Mb/s repeater, augmenting the entries in
the rptrMonTable. Entries exist in this table
only for 100Mb/s repeaters.
The columnar object rptrInfoLastChange is
used to indicate possible discontinuities of
counter type columnar objects in this table. SEQUENCE OF VRptrMon100Entry .1.3.6.1.4.1.2338.4.2.4.2 |
vrptrMon100EntryAn entry in the table, containing information
about a single 100Mbps repeater. VRptrMon100Entry .1.3.6.1.4.1.2338.4.2.4.2.1 |
vrptrMonUpper32TotalOctetsThe total number of octets contained in the valid
frames that have been received on the ports in
this repeater, modulo 2**32. That is, it contains
the upper 32 bits of a 64-bit counter, of which
the lower 32 bits are contained in the
rptrMonTotalOctets object. If an implementation
can not obtain a count of octets as seen
by the repeater itself, the 64-bit value
may be the summation of the values of the
rptrMonitorPortReadableOctets counters combined
with the corresponding rptrMonitorPortUpper32Octets
counters for all of the ports in the repeater.
This statistic provides an indicator of the total
data transferred within the repeater.
This two-counter mechanism is provided for those
network management protocols that do not support
64-bit counters (e.g. SNMP V1) and are used to
manage a repeater type of 100Mb/s.
Conformance clauses for this MIB are defined such
that implementation of this object is not required
in a system which does not support 100Mb/s.
However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.ro Counter .1.3.6.1.4.1.2338.4.2.4.2.1.1 |