LANART-AGENT
AI MIB Summary
Standard SNMP MIB module defining data structures for LANART-AGENT.
295
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
295 total| Object Name |
|---|
ccitt OBJECT IDENTIFIER .0 |
null OBJECT IDENTIFIER .0.0 |
iso OBJECT IDENTIFIER .1 |
org OBJECT IDENTIFIER .1.3 |
dod OBJECT IDENTIFIER .1.3.6 |
internet OBJECT IDENTIFIER .1.3.6.1 |
directory OBJECT IDENTIFIER .1.3.6.1.1 |
mgmt OBJECT IDENTIFIER .1.3.6.1.2 |
mib-2 OBJECT IDENTIFIER .1.3.6.1.2.1 |
system OBJECT IDENTIFIER .1.3.6.1.2.1.1 |
sysDescrA textual description of the entity. This value
should include the full name and version
identification of the system's hardware type,
software operating-system, and networking
software. It is mandatory that this only contain
printable ASCII characters.ro DisplayString .1.3.6.1.2.1.1.1 |
sysObjectIDThe vendor's authoritative identification of the
network management subsystem contained in the
entity. This value is allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides an
easy and unambiguous means for determining `what
kind of box' is being managed. For example, if
vendor `Flintstones, Inc.' was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
Router'.ro OBJECT IDENTIFIER .1.3.6.1.2.1.1.2 |
sysUpTimeThe time (in hundredths of a second) since the
network management portion of the system was last
re-initialized.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.1.3 |
sysContactThe textual identification of the contact person
for this managed node, together with information
on how to contact this person.rw DisplayString .1.3.6.1.2.1.1.4 |
sysNameAn administratively-assigned name for this
managed node. By convention, this is the node's
fully-qualified domain name.rw DisplayString .1.3.6.1.2.1.1.5 |
sysLocationThe physical location of this node (e.g.,
`telephone closet, 3rd floor').rw DisplayString .1.3.6.1.2.1.1.6 |
sysServicesA value which indicates the set of services that
this entity primarily offers.
The value is a sum. This sum initially takes the
value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing
functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering
application services would have a value of 72
(2^(4-1) + 2^(7-1)). Note that in the context of
the Internet suite of protocols, values should be
calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)
For systems including OSI protocols, layers 5 and
6 may also be counted.ro INTEGER .1.3.6.1.2.1.1.7 |
interfaces OBJECT IDENTIFIER .1.3.6.1.2.1.2 |
ifNumberThe number of network interfaces (regardless of
their current state) present on this system.ro INTEGER .1.3.6.1.2.1.2.1 |
ifTableA list of interface entries. The number of
entries is given by the value of ifNumber. SEQUENCE OF IfEntry .1.3.6.1.2.1.2.2 |
ifEntryAn interface entry containing objects at the
subnetwork layer and below for a particular
interface. IfEntry .1.3.6.1.2.1.2.2.1 |
ifIndexA unique value for each interface. Its value
ranges between 1 and the value of ifNumber. The
value for each interface must remain constant at
least from one re-initialization of the entity's
network management system to the next re-
initialization.ro INTEGER .1.3.6.1.2.1.2.2.1.1 |
ifDescrA textual string containing information about the
interface. This string should include the name of
the manufacturer, the product name and the version
of the hardware interface.ro DisplayString .1.3.6.1.2.1.2.2.1.2 |
ifTypeThe type of interface, distinguished according to
the physical/link protocol(s) immediately `below'
the network layer in the protocol stack.ro Enumeration .1.3.6.1.2.1.2.2.1.3 |
ifMtuThe size of the largest datagram which can be
sent/received on the interface, specified in
octets. For interfaces that are used for
transmitting network datagrams, this is the size
of the largest network datagram that can be sent
on the interface.ro INTEGER .1.3.6.1.2.1.2.2.1.4 |
ifSpeedAn estimate of the interface's current bandwidth
in bits per second. For interfaces which do not
vary in bandwidth or for those where no accurate
estimation can be made, this object should contain
the nominal bandwidth.ro Gauge .1.3.6.1.2.1.2.2.1.5 |
ifPhysAddressThe interface's address at the protocol layer
immediately `below' the network layer in the
protocol stack. For interfaces which do not have
such an address (e.g., a serial line), this object
should contain an octet string of zero length.ro PhysAddress (SNMPv2-TC) .1.3.6.1.2.1.2.2.1.6 |
ifAdminStatusThe desired state of the interface. The
testing(3) state indicates that no operational
packets can be passed.rw Enumeration .1.3.6.1.2.1.2.2.1.7 |
ifOperStatusThe current operational state of the interface.
The testing(3) state indicates that no operational
packets can be passed.ro Enumeration .1.3.6.1.2.1.2.2.1.8 |
ifLastChangeThe value of sysUpTime at the time the interface
entered its current operational state. If the
current state was entered prior to the last re-
initialization of the local network management
subsystem, then this object contains a zero
value.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.2.2.1.9 |
ifInOctetsThe total number of octets received on the
interface, including framing characters.ro Counter .1.3.6.1.2.1.2.2.1.10 |
ifInUcastPktsThe number of subnetwork-unicast packets
delivered to a higher-layer protocol.ro Counter .1.3.6.1.2.1.2.2.1.11 |
ifInNUcastPktsThe number of non-unicast (i.e., subnetwork-
broadcast or subnetwork-multicast) packets
delivered to a higher-layer protocol.ro Counter .1.3.6.1.2.1.2.2.1.12 |
ifInDiscardsThe number of inbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being deliverable to a
higher-layer protocol. One possible reason for
discarding such a packet could be to free up
buffer space.ro Counter .1.3.6.1.2.1.2.2.1.13 |
ifInErrorsThe number of inbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.ro Counter .1.3.6.1.2.1.2.2.1.14 |
ifInUnknownProtosThe number of packets received via the interface
which were discarded because of an unknown or
unsupported protocol.ro Counter .1.3.6.1.2.1.2.2.1.15 |
ifOutOctetsThe total number of octets transmitted out of the
interface, including framing characters.ro Counter .1.3.6.1.2.1.2.2.1.16 |
ifOutUcastPktsThe total number of packets that higher-level
protocols requested be transmitted to a
subnetwork-unicast address, including those that
were discarded or not sent.ro Counter .1.3.6.1.2.1.2.2.1.17 |
ifOutNUcastPktsThe total number of packets that higher-level
protocols requested be transmitted to a non-
unicast (i.e., a subnetwork-broadcast or
subnetwork-multicast) address, including those
that were discarded or not sent.ro Counter .1.3.6.1.2.1.2.2.1.18 |
ifOutDiscardsThe number of outbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being transmitted. One
possible reason for discarding such a packet could
be to free up buffer space.ro Counter .1.3.6.1.2.1.2.2.1.19 |
ifOutErrorsThe number of outbound packets that could not be
transmitted because of errors.ro Counter .1.3.6.1.2.1.2.2.1.20 |
ifOutQLenThe length of the output packet queue (in
packets).ro Gauge .1.3.6.1.2.1.2.2.1.21 |
ifSpecificA reference to MIB definitions specific to the
particular media being used to realize the
interface. For example, if the interface is
realized by an ethernet, then the value of this
object refers to a document defining objects
specific to ethernet. If this information is not
present, its value should be set to the OBJECT
IDENTIFIER { 0 0 }, which is a syntatically valid
object identifier, and any conformant
implementation of ASN.1 and BER must be able to
generate and recognize this value.ro OBJECT IDENTIFIER .1.3.6.1.2.1.2.2.1.22 |
at OBJECT IDENTIFIER .1.3.6.1.2.1.3 |
atTableThe Address Translation tables contain the
NetworkAddress to `physical' address equivalences.
Some interfaces do not use translation tables for
determining address equivalences (e.g., DDN-X.25
has an algorithmic method); if all interfaces are
of this type, then the Address Translation table
is empty, i.e., has zero entries.deprecated SEQUENCE OF AtEntry .1.3.6.1.2.1.3.1 |
atEntryEach entry contains one NetworkAddress to
`physical' address equivalence.deprecated AtEntry .1.3.6.1.2.1.3.1.1 |
atIfIndexThe interface on which this entry's equivalence
is effective. The interface identified by a
particular value of this index is the same
interface as identified by the same value of
ifIndex.rwdeprecated INTEGER .1.3.6.1.2.1.3.1.1.1 |
atPhysAddressThe media-dependent `physical' address.
Setting this object to a null string (one of zero
length) has the effect of invaliding the
corresponding entry in the atTable object. That
is, it effectively dissasociates the interface
identified with said entry from the mapping
identified with said entry. It is an
implementation-specific matter as to whether the
agent removes an invalidated entry from the table.
Accordingly, management stations must be prepared
to receive tabular information from agents that
corresponds to entries not currently in use.
Proper interpretation of such entries requires
examination of the relevant atPhysAddress object.rwdeprecated PhysAddress (SNMPv2-TC) .1.3.6.1.2.1.3.1.1.2 |
atNetAddressThe NetworkAddress (e.g., the IP address)
corresponding to the media-dependent `physical'
address.rwdeprecated NetworkAddress .1.3.6.1.2.1.3.1.1.3 |
ip OBJECT IDENTIFIER .1.3.6.1.2.1.4 |
ipForwardingThe indication of whether this entity is acting
as an IP gateway in respect to the forwarding of
datagrams received by, but not addressed to, this
entity. IP gateways forward datagrams. IP hosts
do not (except those source-routed via the host).
Note that for some managed nodes, this object may
take on only a subset of the values possible.
Accordingly, it is appropriate for an agent to
return a `badValue' response if a management
station attempts to change this object to an
inappropriate value.rw Enumeration .1.3.6.1.2.1.4.1 |
ipDefaultTTLThe default value inserted into the Time-To-Live
field of the IP header of datagrams originated at
this entity, whenever a TTL value is not supplied
by the transport layer protocol.rw INTEGER .1.3.6.1.2.1.4.2 |
ipInReceivesThe total number of input datagrams received from
interfaces, including those received in error.ro Counter .1.3.6.1.2.1.4.3 |
ipInHdrErrorsThe number of input datagrams discarded due to
errors in their IP headers, including bad
checksums, version number mismatch, other format
errors, time-to-live exceeded, errors discovered
in processing their IP options, etc.ro Counter .1.3.6.1.2.1.4.4 |
ipInAddrErrorsThe number of input datagrams discarded because
the IP address in their IP header's destination
field was not a valid address to be received at
this entity. This count includes invalid
addresses (e.g., 0.0.0.0) and addresses of
unsupported Classes (e.g., Class E). For entities
which are not IP Gateways and therefore do not
forward datagrams, this counter includes datagrams
discarded because the destination address was not
a local address.ro Counter .1.3.6.1.2.1.4.5 |
ipForwDatagramsThe number of input datagrams for which this
entity was not their final IP destination, as a
result of which an attempt was made to find a
route to forward them to that final destination.
In entities which do not act as IP Gateways, this
counter will include only those packets which were
Source-Routed via this entity, and the Source-
Route option processing was successful.ro Counter .1.3.6.1.2.1.4.6 |
ipInUnknownProtosThe number of locally-addressed datagrams
received successfully but discarded because of an
unknown or unsupported protocol.ro Counter .1.3.6.1.2.1.4.7 |
ipInDiscardsThe number of input IP datagrams for which no
problems were encountered to prevent their
continued processing, but which were discarded
(e.g., for lack of buffer space). Note that this
counter does not include any datagrams discarded
while awaiting re-assembly.ro Counter .1.3.6.1.2.1.4.8 |
ipInDeliversThe total number of input datagrams successfully
delivered to IP user-protocols (including ICMP).ro Counter .1.3.6.1.2.1.4.9 |
ipOutRequestsThe total number of IP datagrams which local IP
user-protocols (including ICMP) supplied to IP in
requests for transmission. Note that this counter
does not include any datagrams counted in
ipForwDatagrams.ro Counter .1.3.6.1.2.1.4.10 |
ipOutDiscardsThe number of output IP datagrams for which no
problem was encountered to prevent their
transmission to their destination, but which were
discarded (e.g., for lack of buffer space). Note
that this counter would include datagrams counted
in ipForwDatagrams if any such packets met this
(discretionary) discard criterion.ro Counter .1.3.6.1.2.1.4.11 |
ipOutNoRoutesThe number of IP datagrams discarded because no
route could be found to transmit them to their
destination. Note that this counter includes any
packets counted in ipForwDatagrams which meet this
`no-route' criterion. Note that this includes any
datagarms which a host cannot route because all of
its default gateways are down.ro Counter .1.3.6.1.2.1.4.12 |
ipReasmTimeoutThe maximum number of seconds which received
fragments are held while they are awaiting
reassembly at this entity.ro INTEGER .1.3.6.1.2.1.4.13 |
ipReasmReqdsThe number of IP fragments received which needed
to be reassembled at this entity.ro Counter .1.3.6.1.2.1.4.14 |
ipReasmOKsThe number of IP datagrams successfully re-
assembled.ro Counter .1.3.6.1.2.1.4.15 |
ipReasmFailsThe number of failures detected by the IP re-
assembly algorithm (for whatever reason: timed
out, errors, etc). Note that this is not
necessarily a count of discarded IP fragments
since some algorithms (notably the algorithm in
RFC 815) can lose track of the number of fragments
by combining them as they are received.ro Counter .1.3.6.1.2.1.4.16 |
ipFragOKsThe number of IP datagrams that have been
successfully fragmented at this entity.ro Counter .1.3.6.1.2.1.4.17 |
ipFragFailsThe number of IP datagrams that have been
discarded because they needed to be fragmented at
this entity but could not be, e.g., because their
Don't Fragment flag was set.ro Counter .1.3.6.1.2.1.4.18 |
ipFragCreatesThe number of IP datagram fragments that have
been generated as a result of fragmentation at
this entity.ro Counter .1.3.6.1.2.1.4.19 |
ipAddrTableThe table of addressing information relevant to
this entity's IP addresses. SEQUENCE OF IpAddrEntry .1.3.6.1.2.1.4.20 |
ipAddrEntryThe addressing information for one of this
entity's IP addresses. IpAddrEntry .1.3.6.1.2.1.4.20.1 |
ipAdEntAddrThe IP address to which this entry's addressing
information pertains.ro IpAddress .1.3.6.1.2.1.4.20.1.1 |
ipAdEntIfIndexThe 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.ro INTEGER .1.3.6.1.2.1.4.20.1.2 |
ipAdEntNetMaskThe subnet mask associated with the IP address of
this entry. The value of the mask is an IP
address with all the network bits set to 1 and all
the hosts bits set to 0.ro IpAddress .1.3.6.1.2.1.4.20.1.3 |
ipAdEntBcastAddrThe value of the least-significant bit in the IP
broadcast address used for sending datagrams on
the (logical) interface associated with the IP
address of this entry. For example, when the
Internet standard all-ones broadcast address is
used, the value will be 1. This value applies to
both the subnet and network broadcasts addresses
used by the entity on this (logical) interface.ro INTEGER .1.3.6.1.2.1.4.20.1.4 |
ipAdEntReasmMaxSizeThe size of the largest IP datagram which this
entity can re-assemble from incoming IP fragmented
datagrams received on this interface.ro INTEGER .1.3.6.1.2.1.4.20.1.5 |
ipRouteTableThis entity's IP Routing table. SEQUENCE OF IpRouteEntry .1.3.6.1.2.1.4.21 |
ipRouteEntryA route to a particular destination. IpRouteEntry .1.3.6.1.2.1.4.21.1 |
ipRouteDestThe destination IP address of this route. An
entry with a value of 0.0.0.0 is considered a
default route. Multiple routes to a single
destination can appear in the table, but access to
such multiple entries is dependent on the table-
access mechanisms defined by the network
management protocol in use.rw IpAddress .1.3.6.1.2.1.4.21.1.1 |
ipRouteIfIndexThe index value which uniquely identifies the
local interface through which the next hop of this
route should be reached. The interface identified
by a particular value of this index is the same
interface as identified by the same value of
ifIndex.rw INTEGER .1.3.6.1.2.1.4.21.1.2 |
ipRouteMetric1The primary routing metric for this route. The
semantics of this metric are determined by the
routing-protocol specified in the route's
ipRouteProto value. If this metric is not used,
its value should be set to -1.rw INTEGER .1.3.6.1.2.1.4.21.1.3 |
ipRouteMetric2An alternate routing metric for this route. The
semantics of this metric are determined by the
routing-protocol specified in the route's
ipRouteProto value. If this metric is not used,
its value should be set to -1.rw INTEGER .1.3.6.1.2.1.4.21.1.4 |
ipRouteMetric3An alternate routing metric for this route. The
semantics of this metric are determined by the
routing-protocol specified in the route's
ipRouteProto value. If this metric is not used,
its value should be set to -1.rw INTEGER .1.3.6.1.2.1.4.21.1.5 |
ipRouteMetric4An alternate routing metric for this route. The
semantics of this metric are determined by the
routing-protocol specified in the route's
ipRouteProto value. If this metric is not used,
its value should be set to -1.rw INTEGER .1.3.6.1.2.1.4.21.1.6 |
ipRouteNextHopThe IP address of the next hop of this route.
(In the case of a route bound to an interface
which is realized via a broadcast media, the value
of this field is the agent's IP address on that
interface.)rw IpAddress .1.3.6.1.2.1.4.21.1.7 |
ipRouteTypeThe type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively dissasociates the destination
identified with said entry from the route
identified with said entry. It is an
implementation-specific matter as to whether the
agent removes an invalidated entry from the table.
Accordingly, management stations must be prepared
to receive tabular information from agents that
corresponds to entries not currently in use.
Proper interpretation of such entries requires
examination of the relevant ipRouteType object.rw Enumeration .1.3.6.1.2.1.4.21.1.8 |
ipRouteProtoThe routing mechanism via which this route was
learned. Inclusion of values for gateway routing
protocols is not intended to imply that hosts
should support those protocols.ro Enumeration .1.3.6.1.2.1.4.21.1.9 |
ipRouteAgeThe number of seconds since this route was last
updated or otherwise determined to be correct.
Note that no semantics of `too old' can be implied
except through knowledge of the routing protocol
by which the route was learned.rw INTEGER .1.3.6.1.2.1.4.21.1.10 |
ipRouteMaskIndicate the mask to be logical-ANDed with the
destination address before being compared to the
value in the ipRouteDest field. For those systems
that do not support arbitrary subnet masks, an
agent constructs the value of the ipRouteMask by
determining whether the value of the correspondent
ipRouteDest field belong to a class-A, B, or C
network, and then using one of:
mask network
255.0.0.0 class-A
255.255.0.0 class-B
255.255.255.0 class-C
If the value of the ipRouteDest is 0.0.0.0 (a
default route), then the mask value is also
0.0.0.0. It should be noted that all IP routing
subsystems implicitly use this mechanism.rw IpAddress .1.3.6.1.2.1.4.21.1.11 |
ipRouteMetric5An alternate routing metric for this route. The
semantics of this metric are determined by the
routing-protocol specified in the route's
ipRouteProto value. If this metric is not used,
its value should be set to -1.rw INTEGER .1.3.6.1.2.1.4.21.1.12 |
ipRouteInfoA reference to MIB definitions specific to the
particular routing protocol which is responsible
for this route, as determined by the value
specified in the route's ipRouteProto value. If
this information is not present, its value should
be set to the OBJECT IDENTIFIER { 0 0 }, which is
a syntatically valid object identifier, and any
conformant implementation of ASN.1 and BER must be
able to generate and recognize this value.ro OBJECT IDENTIFIER .1.3.6.1.2.1.4.21.1.13 |
ipNetToMediaTableThe IP Address Translation table used for mapping
from IP addresses to physical addresses. SEQUENCE OF IpNetToMediaEntry .1.3.6.1.2.1.4.22 |
ipNetToMediaEntryEach entry contains one IpAddress to `physical'
address equivalence. IpNetToMediaEntry .1.3.6.1.2.1.4.22.1 |
ipNetToMediaIfIndexThe interface on which this entry's equivalence
is effective. The interface identified by a
particular value of this index is the same
interface as identified by the same value of
ifIndex.rw INTEGER .1.3.6.1.2.1.4.22.1.1 |
ipNetToMediaPhysAddressThe media-dependent `physical' address.rw PhysAddress (SNMPv2-TC) .1.3.6.1.2.1.4.22.1.2 |
ipNetToMediaNetAddressThe IpAddress corresponding to the media-
dependent `physical' address.ro IpAddress .1.3.6.1.2.1.4.22.1.3 |
ipNetToMediaTypeThe type of mapping.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipNetToMediaTable. That is, it effectively
dissasociates the interface identified with said
entry from the mapping identified with said entry.
It is an implementation-specific matter as to
whether the agent removes an invalidated entry
from the table. Accordingly, management stations
must be prepared to receive tabular information
from agents that corresponds to entries not
currently in use. Proper interpretation of such
entries requires examination of the relevant
ipNetToMediaType object.rw Enumeration .1.3.6.1.2.1.4.22.1.4 |
ipRoutingDiscardsThe number of routing entries which were chosen
to be discarded even though they are valid. One
possible reason for discarding such an entry could
be to free-up buffer space for other routing
entries.ro Counter .1.3.6.1.2.1.4.23 |
icmp OBJECT IDENTIFIER .1.3.6.1.2.1.5 |
icmpInMsgsThe total number of ICMP messages which the
entity received. Note that this counter includes
all those counted by icmpInErrors.ro Counter .1.3.6.1.2.1.5.1 |
icmpInErrorsThe number of ICMP messages which the entity
received but determined as having ICMP-specific
errors (bad ICMP checksums, bad length, etc.).ro Counter .1.3.6.1.2.1.5.2 |
icmpInDestUnreachsThe number of ICMP Destination Unreachable
messages received.ro Counter .1.3.6.1.2.1.5.3 |
icmpInTimeExcdsThe number of ICMP Time Exceeded messages
received.ro Counter .1.3.6.1.2.1.5.4 |
icmpInParmProbsThe number of ICMP Parameter Problem messages
received.ro Counter .1.3.6.1.2.1.5.5 |
icmpInSrcQuenchsThe number of ICMP Source Quench messages
received.ro Counter .1.3.6.1.2.1.5.6 |
icmpInRedirectsThe number of ICMP Redirect messages received.ro Counter .1.3.6.1.2.1.5.7 |
icmpInEchosThe number of ICMP Echo (request) messages
received.ro Counter .1.3.6.1.2.1.5.8 |
icmpInEchoRepsThe number of ICMP Echo Reply messages received.ro Counter .1.3.6.1.2.1.5.9 |
icmpInTimestampsThe number of ICMP Timestamp (request) messages
received.ro Counter .1.3.6.1.2.1.5.10 |
icmpInTimestampRepsThe number of ICMP Timestamp Reply messages
received.ro Counter .1.3.6.1.2.1.5.11 |
icmpInAddrMasksThe number of ICMP Address Mask Request messages
received.ro Counter .1.3.6.1.2.1.5.12 |
icmpInAddrMaskRepsThe number of ICMP Address Mask Reply messages
received.ro Counter .1.3.6.1.2.1.5.13 |
icmpOutMsgsThe total number of ICMP messages which this
entity attempted to send. Note that this counter
includes all those counted by icmpOutErrors.ro Counter .1.3.6.1.2.1.5.14 |
icmpOutErrorsThe number of ICMP messages which this entity did
not send due to problems discovered within ICMP
such as a lack of buffers. This value should not
include errors discovered outside the ICMP layer
such as the inability of IP to route the resultant
datagram. In some implementations there may be no
types of error which contribute to this counter's
value.ro Counter .1.3.6.1.2.1.5.15 |
icmpOutDestUnreachsThe number of ICMP Destination Unreachable
messages sent.ro Counter .1.3.6.1.2.1.5.16 |
icmpOutTimeExcdsThe number of ICMP Time Exceeded messages sent.ro Counter .1.3.6.1.2.1.5.17 |
icmpOutParmProbsThe number of ICMP Parameter Problem messages
sent.ro Counter .1.3.6.1.2.1.5.18 |
icmpOutSrcQuenchsThe number of ICMP Source Quench messages sent.ro Counter .1.3.6.1.2.1.5.19 |
icmpOutRedirectsThe number of ICMP Redirect messages sent. For a
host, this object will always be zero, since hosts
do not send redirects.ro Counter .1.3.6.1.2.1.5.20 |
icmpOutEchosThe number of ICMP Echo (request) messages sent.ro Counter .1.3.6.1.2.1.5.21 |
icmpOutEchoRepsThe number of ICMP Echo Reply messages sent.ro Counter .1.3.6.1.2.1.5.22 |
icmpOutTimestampsThe number of ICMP Timestamp (request) messages
sent.ro Counter .1.3.6.1.2.1.5.23 |
icmpOutTimestampRepsThe number of ICMP Timestamp Reply messages
sent.ro Counter .1.3.6.1.2.1.5.24 |
icmpOutAddrMasksThe number of ICMP Address Mask Request messages
sent.ro Counter .1.3.6.1.2.1.5.25 |
icmpOutAddrMaskRepsThe number of ICMP Address Mask Reply messages
sent.ro Counter .1.3.6.1.2.1.5.26 |
tcp OBJECT IDENTIFIER .1.3.6.1.2.1.6 |
tcpRtoAlgorithmThe algorithm used to determine the timeout value
used for retransmitting unacknowledged octets.ro Enumeration .1.3.6.1.2.1.6.1 |
tcpRtoMinThe minimum value permitted by a TCP
implementation for the retransmission timeout,
measured in milliseconds. More refined semantics
for objects of this type depend upon the algorithm
used to determine the retransmission timeout. In
particular, when the timeout algorithm is rsre(3),
an object of this type has the semantics of the
LBOUND quantity described in RFC 793.ro INTEGER .1.3.6.1.2.1.6.2 |
tcpRtoMaxThe maximum value permitted by a TCP
implementation for the retransmission timeout,
measured in milliseconds. More refined semantics
for objects of this type depend upon the algorithm
used to determine the retransmission timeout. In
particular, when the timeout algorithm is rsre(3),
an object of this type has the semantics of the
UBOUND quantity described in RFC 793.ro INTEGER .1.3.6.1.2.1.6.3 |
tcpMaxConnThe limit on the total number of TCP connections
the entity can support. In entities where the
maximum number of connections is dynamic, this
object should contain the value -1.ro INTEGER .1.3.6.1.2.1.6.4 |
tcpActiveOpensThe number of times TCP connections have made a
direct transition to the SYN-SENT state from the
CLOSED state.ro Counter .1.3.6.1.2.1.6.5 |
tcpPassiveOpensThe number of times TCP connections have made a
direct transition to the SYN-RCVD state from the
LISTEN state.ro Counter .1.3.6.1.2.1.6.6 |
tcpAttemptFailsThe number of times TCP connections have made a
direct transition to the CLOSED state from either
the SYN-SENT state or the SYN-RCVD state, plus the
number of times TCP connections have made a direct
transition to the LISTEN state from the SYN-RCVD
state.ro Counter .1.3.6.1.2.1.6.7 |
tcpEstabResetsThe number of times TCP connections have made a
direct transition to the CLOSED state from either
the ESTABLISHED state or the CLOSE-WAIT state.ro Counter .1.3.6.1.2.1.6.8 |
tcpCurrEstabThe number of TCP connections for which the
current state is either ESTABLISHED or CLOSE-
WAIT.ro Gauge .1.3.6.1.2.1.6.9 |
tcpInSegsThe total number of segments received, including
those received in error. This count includes
segments received on currently established
connections.ro Counter .1.3.6.1.2.1.6.10 |
tcpOutSegsThe total number of segments sent, including
those on current connections but excluding those
containing only retransmitted octets.ro Counter .1.3.6.1.2.1.6.11 |
tcpRetransSegsThe total number of segments retransmitted - that
is, the number of TCP segments transmitted
containing one or more previously transmitted
octets.ro Counter .1.3.6.1.2.1.6.12 |
tcpConnTableA table containing TCP connection-specific
information. SEQUENCE OF TcpConnEntry .1.3.6.1.2.1.6.13 |
tcpConnEntryInformation about a particular current TCP
connection. An object of this type is transient,
in that it ceases to exist when (or soon after)
the connection makes the transition to the CLOSED
state. TcpConnEntry .1.3.6.1.2.1.6.13.1 |
tcpConnStateThe state of this TCP connection.
The only value which may be set by a management
station is deleteTCB(12). Accordingly, it is
appropriate for an agent to return a `badValue'
response if a management station attempts to set
this object to any other value.
If a management station sets this object to the
value deleteTCB(12), then this has the effect of
deleting the TCB (as defined in RFC 793) of the
corresponding connection on the managed node,
resulting in immediate termination of the
connection.
As an implementation-specific option, a RST
segment may be sent from the managed node to the
other TCP endpoint (note however that RST segments
are not sent reliably).rw Enumeration .1.3.6.1.2.1.6.13.1.1 |
tcpConnLocalAddressThe local IP address for this TCP connection. In
the case of a connection in the listen state which
is willing to accept connections for any IP
interface associated with the node, the value
0.0.0.0 is used.ro IpAddress .1.3.6.1.2.1.6.13.1.2 |
tcpConnLocalPortThe local port number for this TCP connection.ro INTEGER .1.3.6.1.2.1.6.13.1.3 |
tcpConnRemAddressThe remote IP address for this TCP connection.ro IpAddress .1.3.6.1.2.1.6.13.1.4 |
tcpConnRemPortThe remote port number for this TCP connection.ro INTEGER .1.3.6.1.2.1.6.13.1.5 |
tcpInErrsThe total number of segments received in error
(e.g., bad TCP checksums).ro Counter .1.3.6.1.2.1.6.14 |
tcpOutRstsThe number of TCP segments sent containing the
RST flag.ro Counter .1.3.6.1.2.1.6.15 |
udp OBJECT IDENTIFIER .1.3.6.1.2.1.7 |
udpInDatagramsThe total number of UDP datagrams delivered to
UDP users.ro Counter .1.3.6.1.2.1.7.1 |
udpNoPortsThe total number of received UDP datagrams for
which there was no application at the destination
port.ro Counter .1.3.6.1.2.1.7.2 |
udpInErrorsThe number of received UDP datagrams that could
not be delivered for reasons other than the lack
of an application at the destination port.ro Counter .1.3.6.1.2.1.7.3 |
udpOutDatagramsThe total number of UDP datagrams sent from this
entity.ro Counter .1.3.6.1.2.1.7.4 |
udpTableA table containing UDP listener information. SEQUENCE OF UdpEntry .1.3.6.1.2.1.7.5 |
udpEntryInformation about a particular current UDP
listener. UdpEntry .1.3.6.1.2.1.7.5.1 |
udpLocalAddressThe local IP address for this UDP listener. In
the case of a UDP listener which is willing to
accept datagrams for any IP interface associated
with the node, the value 0.0.0.0 is used.ro IpAddress .1.3.6.1.2.1.7.5.1.1 |
udpLocalPortThe local port number for this UDP listener.ro INTEGER .1.3.6.1.2.1.7.5.1.2 |
egp OBJECT IDENTIFIER .1.3.6.1.2.1.8 |
transmission OBJECT IDENTIFIER .1.3.6.1.2.1.10 |
snmp OBJECT IDENTIFIER .1.3.6.1.2.1.11 |
snmpInPktsThe total number of Messages delivered to the
SNMP entity from the transport service.ro Counter .1.3.6.1.2.1.11.1 |
snmpOutPktsThe total number of SNMP Messages which were
passed from the SNMP protocol entity to the
transport service.ro Counter .1.3.6.1.2.1.11.2 |
snmpInBadVersionsThe total number of SNMP Messages which were
delivered to the SNMP protocol entity and were for
an unsupported SNMP version.ro Counter .1.3.6.1.2.1.11.3 |
snmpInBadCommunityNamesThe total number of SNMP Messages delivered to
the SNMP protocol entity which used a SNMP
community name not known to said entity.ro Counter .1.3.6.1.2.1.11.4 |
snmpInBadCommunityUsesThe total number of SNMP Messages delivered to
the SNMP protocol entity which represented an SNMP
operation which was not allowed by the SNMP
community named in the Message.ro Counter .1.3.6.1.2.1.11.5 |
snmpInASNParseErrsThe total number of ASN.1 or BER errors
encountered by the SNMP protocol entity when
decoding received SNMP Messages.ro Counter .1.3.6.1.2.1.11.6 |
snmpInTooBigsThe total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`tooBig'.ro Counter .1.3.6.1.2.1.11.8 |
snmpInNoSuchNamesThe total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`noSuchName'.ro Counter .1.3.6.1.2.1.11.9 |
snmpInBadValuesThe total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`badValue'.ro Counter .1.3.6.1.2.1.11.10 |
snmpInReadOnlysThe total number valid SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`readOnly'. It should be noted that it is a
protocol error to generate an SNMP PDU which
contains the value `readOnly' in the error-status
field, as such this object is provided as a means
of detecting incorrect implementations of the
SNMP.ro Counter .1.3.6.1.2.1.11.11 |
snmpInGenErrsThe total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field is
`genErr'.ro Counter .1.3.6.1.2.1.11.12 |
snmpInTotalReqVarsThe total number of MIB objects which have been
retrieved successfully by the SNMP protocol entity
as the result of receiving valid SNMP Get-Request
and Get-Next PDUs.ro Counter .1.3.6.1.2.1.11.13 |
snmpInTotalSetVarsThe total number of MIB objects which have been
altered successfully by the SNMP protocol entity
as the result of receiving valid SNMP Set-Request
PDUs.ro Counter .1.3.6.1.2.1.11.14 |
snmpInGetRequestsThe total number of SNMP Get-Request PDUs which
have been accepted and processed by the SNMP
protocol entity.ro Counter .1.3.6.1.2.1.11.15 |
snmpInGetNextsThe total number of SNMP Get-Next PDUs which have
been accepted and processed by the SNMP protocol
entity.ro Counter .1.3.6.1.2.1.11.16 |
snmpInSetRequestsThe total number of SNMP Set-Request PDUs which
have been accepted and processed by the SNMP
protocol entity.ro Counter .1.3.6.1.2.1.11.17 |
snmpInGetResponsesThe total number of SNMP Get-Response PDUs which
have been accepted and processed by the SNMP
protocol entity.ro Counter .1.3.6.1.2.1.11.18 |
snmpInTrapsThe total number of SNMP Trap PDUs which have
been accepted and processed by the SNMP protocol
entity.ro Counter .1.3.6.1.2.1.11.19 |
snmpOutTooBigsThe total number of SNMP PDUs which were
generated by the SNMP protocol entity and for
which the value of the error-status field is
`tooBig.'ro Counter .1.3.6.1.2.1.11.20 |
snmpOutNoSuchNamesThe total number of SNMP PDUs which were
generated by the SNMP protocol entity and for
which the value of the error-status is
`noSuchName'.ro Counter .1.3.6.1.2.1.11.21 |
snmpOutBadValuesThe total number of SNMP PDUs which were
generated by the SNMP protocol entity and for
which the value of the error-status field is
`badValue'.ro Counter .1.3.6.1.2.1.11.22 |
snmpOutGenErrsThe total number of SNMP PDUs which were
generated by the SNMP protocol entity and for
which the value of the error-status field is
`genErr'.ro Counter .1.3.6.1.2.1.11.24 |
snmpOutGetRequestsThe total number of SNMP Get-Request PDUs which
have been generated by the SNMP protocol entity.ro Counter .1.3.6.1.2.1.11.25 |
snmpOutGetNextsThe total number of SNMP Get-Next PDUs which have
been generated by the SNMP protocol entity.ro Counter .1.3.6.1.2.1.11.26 |
snmpOutSetRequestsThe total number of SNMP Set-Request PDUs which
have been generated by the SNMP protocol entity.ro Counter .1.3.6.1.2.1.11.27 |
snmpOutGetResponsesThe total number of SNMP Get-Response PDUs which
have been generated by the SNMP protocol entity.ro Counter .1.3.6.1.2.1.11.28 |
snmpOutTrapsThe total number of SNMP Trap PDUs which have
been generated by the SNMP protocol entity.ro Counter .1.3.6.1.2.1.11.29 |
snmpEnableAuthenTrapsIndicates whether the SNMP agent process is
permitted to generate authentication-failure
traps. The value of this object overrides any
configuration information; as such, it provides a
means whereby all authentication-failure traps may
be disabled.
Note that it is strongly recommended that this
object be stored in non-volatile memory so that it
remains constant between re-initializations of the
network management system.rw Enumeration .1.3.6.1.2.1.11.30 |
dot1dBridge OBJECT IDENTIFIER .1.3.6.1.2.1.17 |
newRootThe newRoot trap indicates that the sending agent
has become the new root of the Spanning Tree; the
trap is sent by a bridge soon after its election
as the new root, e.g., upon expiration of the
Topology Change Timer immediately subsequent to
its election. TRAP-TYPE .1.3.6.1.2.1.17.0.1 |
topologyChangeA topologyChange trap is sent by a bridge when
any of its configured ports transitions from the
Learning state to the Forwarding state, or from
the Forwarding state to the Blocking state. The
trap is not sent if a newRoot trap is sent for the
same transition. TRAP-TYPE .1.3.6.1.2.1.17.0.2 |
dot1dBase OBJECT IDENTIFIER .1.3.6.1.2.1.17.1 |
dot1dStp OBJECT IDENTIFIER .1.3.6.1.2.1.17.2 |
dot1dSr OBJECT IDENTIFIER .1.3.6.1.2.1.17.3 |
dot1dTp OBJECT IDENTIFIER .1.3.6.1.2.1.17.4 |
dot1dStatic OBJECT IDENTIFIER .1.3.6.1.2.1.17.5 |
snmpDot3RptrMgt OBJECT IDENTIFIER .1.3.6.1.2.1.22 |
rptrHealthThe rptrHealth trap conveys information related
to the operational status of the repeater. This
trap is sent only when the oper status of the
repeater changes.
The rptrHealth trap must contain the
rptrOperStatus object. The agent may optionally
include the rptrHealthText object in the varBind
list. See the rptrOperStatus and rptrHealthText
objects for descriptions of the information that
is sent.
The agent must throttle the generation of
consecutive rptrHealth traps so that there is at
least a five-second gap between them. TRAP-TYPE .1.3.6.1.2.1.22.0.1 |
rptrGroupChangeThis trap is sent when a change occurs in the
group structure of a repeater. This occurs only
when a group is logically or physically 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 rptrGroupChange traps for the same
group so that there is at least a five-second gap
between them. TRAP-TYPE .1.3.6.1.2.1.22.0.2 |
rptrResetEventThe rptrResetEvent trap conveys information
related to the operational status 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 [IEEE 802.3 Std], when triggered by a
management command (e.g., an SNMP Set on the
rptrReset object).
The agent must throttle the generation of
consecutive rptrResetEvent traps so that there is
at least a five-second gap between them.
The rptrResetEvent 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 rptrOperStatus object as an
optional object with its coldStart and warmStart
trap PDUs.
The rptrOperStatus object must be included in the
varbind list sent with this trap. The agent may
optionally include the rptrHealthText object as
well. TRAP-TYPE .1.3.6.1.2.1.22.0.3 |
rptrBasicPackage OBJECT IDENTIFIER .1.3.6.1.2.1.22.1 |
rptrRptrInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.1.1 |
rptrGroupCapacityThe rptrGroupCapacity 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 rptrGroupCapacity.
Some groups may not be present in the repeater, in
which case the actual number of groups present
will be less than rptrGroupCapacity. The number
of groups present will never be greater than
rptrGroupCapacity.
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.ro INTEGER .1.3.6.1.2.1.22.1.1.1 |
rptrOperStatusThe rptrOperStatus object indicates the
operational state of the repeater. The
rptrHealthText 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).ro Enumeration .1.3.6.1.2.1.22.1.1.2 |
rptrHealthTextThe health text object is a text string that
provides information relevant to the operational
state of the repeater. Agents may use this string
to provide detailed information on current
failures, including how they were detected, and/or
instructions for problem resolution. The contents
are agent-specific.ro DisplayString .1.3.6.1.2.1.22.1.1.3 |
rptrResetSetting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std].
Setting this object to noReset(1) has no effect.
The agent will always return the value noReset(1)
when this object is read.
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.
As a result of this action a rptrResetEvent trap
should be sent.rw Enumeration .1.3.6.1.2.1.22.1.1.4 |
rptrNonDisruptTestSetting this object to selfTest(2) causes the
repeater to perform a agent-specific, non-
disruptive self-test that has the following
characteristics: a) The nature of the tests is
not specified. b) The test does not change the
state of the repeater or management information
about the repeater. c) The test does not inject
packets onto any segment. d) The test does not
prevent the relay of any packets. e) The test
does not interfere with management functions.
After performing this test the agent will update
the repeater health information and send a
rptrHealth trap.
Setting this object to noSelfTest(1) has no
effect. The agent will always return the value
noSelfTest(1) when this object is read.rw Enumeration .1.3.6.1.2.1.22.1.1.5 |
rptrTotalPartitionedPortsThis 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.2.1.22.1.1.6 |
rptrGroupInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.1.2 |
rptrGroupTableTable of descriptive and status information about
the groups of ports. SEQUENCE OF RptrGroupEntry .1.3.6.1.2.1.22.1.2.1 |
rptrGroupEntryAn entry in the table, containing information
about a single group of ports. RptrGroupEntry .1.3.6.1.2.1.22.1.2.1.1 |
rptrGroupIndexThis object identifies the group within the
repeater for which this entry contains
information. This value is never greater than
rptrGroupCapacity.ro INTEGER .1.3.6.1.2.1.22.1.2.1.1.1 |
rptrGroupDescrA 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. Plug-in Module, Rev
A' or 'Barney Rubble 10BASE-T 4-port SIMM socket
Version 2.1' are examples of valid group
descriptions.
It is mandatory that this only contain printable
ASCII characters.ro DisplayString .1.3.6.1.2.1.22.1.2.1.1.2 |
rptrGroupObjectIDThe 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 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.2.1.22.1.2.1.1.3 |
rptrGroupOperStatusAn 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.2.1.22.1.2.1.1.4 |
rptrGroupLastOperStatusChangeAn object that contains the value of sysUpTime at
the time that the value of the rptrGroupOperStatus
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.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.22.1.2.1.1.5 |
rptrGroupPortCapacityThe rptrGroupPortCapacity 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
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.2.1.22.1.2.1.1.6 |
rptrPortInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.1.3 |
rptrPortTableTable of descriptive and status information about
the ports. SEQUENCE OF RptrPortEntry .1.3.6.1.2.1.22.1.3.1 |
rptrPortEntryAn entry in the table, containing information
about a single port. RptrPortEntry .1.3.6.1.2.1.22.1.3.1.1 |
rptrPortGroupIndexThis object identifies the group containing the
port for which this entry contains information.ro INTEGER .1.3.6.1.2.1.22.1.3.1.1.1 |
rptrPortIndexThis object identifies the port within the group
for which this entry contains information. This
value can never be greater than
rptrGroupPortCapacity for the associated group.ro INTEGER .1.3.6.1.2.1.22.1.3.1.1.2 |
rptrPortAdminStatusSetting 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.2.1.22.1.3.1.1.3 |
rptrPortAutoPartitionStateThe 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.ro Enumeration .1.3.6.1.2.1.22.1.3.1.1.4 |
rptrPortOperStatusThis 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 change to
notOperational(2) soon after.ro Enumeration .1.3.6.1.2.1.22.1.3.1.1.5 |
rptrMonitorPackage OBJECT IDENTIFIER .1.3.6.1.2.1.22.2 |
rptrMonitorRptrInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.2.1 |
rptrMonitorTransmitCollisionsThis 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).
The approximate minimum time for rollover of this
counter is 16 hours.ro Counter .1.3.6.1.2.1.22.2.1.1 |
rptrMonitorGroupInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.2.2 |
rptrMonitorGroupTableTable of performance and error statistics for the
groups. SEQUENCE OF RptrMonitorGroupEntry .1.3.6.1.2.1.22.2.2.1 |
rptrMonitorGroupEntryAn 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. RptrMonitorGroupEntry .1.3.6.1.2.1.22.2.2.1.1 |
rptrMonitorGroupIndexThis object identifies the group within the
repeater for which this entry contains
information.ro INTEGER .1.3.6.1.2.1.22.2.2.1.1.1 |
rptrMonitorGroupTotalFramesThe 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 rptrMonitorPortReadableFrames
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.ro Counter .1.3.6.1.2.1.22.2.2.1.1.2 |
rptrMonitorGroupTotalOctetsThe 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 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 is 58 minutes.ro Counter .1.3.6.1.2.1.22.2.2.1.1.3 |
rptrMonitorGroupTotalErrorsThe 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
rptrMonitorPortTotalErrors counters for all of the
ports in the group.ro Counter .1.3.6.1.2.1.22.2.2.1.1.4 |
rptrMonitorPortInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.2.3 |
rptrMonitorPortTableTable of performance and error statistics for the
ports. SEQUENCE OF RptrMonitorPortEntry .1.3.6.1.2.1.22.2.3.1 |
rptrMonitorPortEntryAn entry in the table, containing performance and
error statistics for a single port. RptrMonitorPortEntry .1.3.6.1.2.1.22.2.3.1.1 |
rptrMonitorPortGroupIndexThis object identifies the group containing the
port for which this entry contains information.ro INTEGER .1.3.6.1.2.1.22.2.3.1.1.1 |
rptrMonitorPortIndexThis object identifies the port within the group
for which this entry contains information.ro INTEGER .1.3.6.1.2.1.22.2.3.1.1.2 |
rptrMonitorPortReadableFramesThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.3 |
rptrMonitorPortReadableOctetsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.4 |
rptrMonitorPortFCSErrorsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.5 |
rptrMonitorPortAlignmentErrorsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.6 |
rptrMonitorPortFrameTooLongsThis 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.
The approximate minimum time for rollover of this
counter is 61 days.ro Counter .1.3.6.1.2.1.22.2.3.1.1.7 |
rptrMonitorPortShortEventsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.8 |
rptrMonitorPortRuntsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.9 |
rptrMonitorPortCollisionsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.10 |
rptrMonitorPortLateEventsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.11 |
rptrMonitorPortVeryLongEventsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.12 |
rptrMonitorPortDataRateMismatchesThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.13 |
rptrMonitorPortAutoPartitionsThis 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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.14 |
rptrMonitorPortTotalErrorsThe 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:
rptrMonitorPortFCSErrors,
rptrMonitorPortAlignmentErrors,
rptrMonitorPortFrameTooLongs,
rptrMonitorPortShortEvents,
rptrMonitorPortLateEvents,
rptrMonitorPortVeryLongEvents, and
rptrMonitorPortDataRateMismatches.
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.ro Counter .1.3.6.1.2.1.22.2.3.1.1.15 |
rptrAddrTrackPackage OBJECT IDENTIFIER .1.3.6.1.2.1.22.3 |
rptrAddrTrackRptrInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.3.1 |
rptrAddrTrackGroupInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.3.2 |
rptrAddrTrackPortInfo OBJECT IDENTIFIER .1.3.6.1.2.1.22.3.3 |
rptrAddrTrackTableTable of address mapping information about the
ports. SEQUENCE OF RptrAddrTrackEntry .1.3.6.1.2.1.22.3.3.1 |
rptrAddrTrackEntryAn entry in the table, containing address mapping
information about a single port. RptrAddrTrackEntry .1.3.6.1.2.1.22.3.3.1.1 |
rptrAddrTrackGroupIndexThis object identifies the group containing the
port for which this entry contains information.ro INTEGER .1.3.6.1.2.1.22.3.3.1.1.1 |
rptrAddrTrackPortIndexThis object identifies the port within the group
for which this entry contains information.ro INTEGER .1.3.6.1.2.1.22.3.3.1.1.2 |
rptrAddrTrackLastSourceAddressThis object is the SourceAddress of the last
readable frame (i.e., counted by
rptrMonitorPortReadableFrames) received by this
port.ro MacAddress (SNMPv2-TC) .1.3.6.1.2.1.22.3.3.1.1.3 |
rptrAddrTrackSourceAddrChangesThis counter is incremented by one for each time
that the rptrAddrTrackLastSourceAddress 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.ro Counter .1.3.6.1.2.1.22.3.3.1.1.4 |
experimental OBJECT IDENTIFIER .1.3.6.1.3 |
private OBJECT IDENTIFIER .1.3.6.1.4 |
enterprises OBJECT IDENTIFIER .1.3.6.1.4.1 |
lanart OBJECT IDENTIFIER .1.3.6.1.4.1.712 |
laMib1 OBJECT IDENTIFIER .1.3.6.1.4.1.712.1 |
laProducts OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1 |
laTpHub OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1 |
laTpHub1 OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.1 |
etm120x OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.1.12 |
etm160x OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.1.16 |
etm240x OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.1.24 |
laTpHub2 OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.2 |
ete120x OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.2.12 |
ete160x OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.2.16 |
ete240x OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.2.24 |
laTpHub3 OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.3 |
bbAui OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.3.0 |
bbAuiTp OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.3.1 |
bbAuiBnc OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.3.2 |
bbAuiTpBnc OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.3.3 |
bbAui10BASE-FL OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.1.1.3.4 |
laHubMib OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.2 |
laSys OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.2.1 |
laSysConfigSetting this object to save(1) will save all
configuration variables to non-volatile memory.
Setting this object to load(2) will configure
the hub according to the stored configuration.
Setting this object to factory(3) will configure
the hub according to the factory settings.
A return value of ok(4) means the non-volatile memory
is operational.
A return value of failed(5) means the non-volatile
memory has failed.rw Enumeration .1.3.6.1.4.1.712.1.2.1.1 |
laJoystickSetting this object to disabled(2) prevents
use of the four-position switch on the front
panel. Resetting this object to enabled(1)
allows use of the switch.rw Enumeration .1.3.6.1.4.1.712.1.2.1.2 |
laLinkAlertSetting this object enables or disables the
LinkALERT feature of the backbone 10BASE-T
or 10BASE-FL port.
A return value of not-applicable indicates that
none of the backbone ports feature LinkALERT.rw Enumeration .1.3.6.1.4.1.712.1.2.1.3 |
laTpPort OBJECT IDENTIFIER .1.3.6.1.4.1.712.1.2.2 |
laTpPortTableTable of descriptive and status information about
the ports. SEQUENCE OF LaTpPortEntry .1.3.6.1.4.1.712.1.2.2.1 |
laTpPortEntryAn entry in the table, containing information
about a single port. LaTpPortEntry .1.3.6.1.4.1.712.1.2.2.1.1 |
laTpPortGroupIndexThis object identifies the group containing the
port for which this entry contains information.ro INTEGER .1.3.6.1.4.1.712.1.2.2.1.1.1 |
laTpPortIndexThis object identifies the port within the group
for which this entry contains information.ro INTEGER .1.3.6.1.4.1.712.1.2.2.1.1.2 |
laTpLinkTestSetting this object to disabled(2) disables the
link test feature. This may be useful for
interoperation with pre-10BASE-T equipment.
Setting this object to enabled(1) enables the
feature.
A return value of failed(3) indicates a link test
failure for this port.
A return value of not-applicable(4) indicates that
the specified port does not have a link test.rw Enumeration .1.3.6.1.4.1.712.1.2.2.1.1.3 |
laTpAutoPolaritySetting this object to disabled(2) disables the
auto polarity test for this port.
Setting this object to enabled(1) enables the feature.
A return value of corrected(3) indicates that the
polarity test has sensed a reversal on the receive
wiring pair, and has corrected this fault by inverting
its receive signal.
A return value of not-applicable(4) indicates that
the specified port does not support polarity correction.rw Enumeration .1.3.6.1.4.1.712.1.2.2.1.1.4 |