RFC-1213-MIB

MIB Reference — IPNetwork Monitor

All MIBsRFC-1213-MIB

Category: IETF Standards

Description:

Provides MIB-II base management objects covering the system, interfaces, IP, ICMP, TCP, UDP, and SNMP groups.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
NetworkAddress
TimeTicks
mgmt

What Is RFC-1213-MIB?

RFC-1213-MIB is the standard IETF MIB (RFC 1213), universally known as MIB-II, defining the foundational system, interface, address-translation, IP, ICMP, TCP, UDP, EGP, transmission, and SNMP object groups implemented by virtually every SNMP-managed device. Its objects include the system group (sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation, sysServices), the interfaces group (ifNumber and the ifTable with ifIndex/ifDescr/ifType/ifMtu/ifSpeed/ifPhysAddress/ifAdminStatus/ifOperStatus/ifLastChange and traffic/error counters), and further groups for IP, ICMP, TCP, UDP, and EGP statistics. As the baseline management MIB it lets an administrator or NMS discover basic identity, uptime, and per-interface status/traffic on any compliant SNMP agent, forming the foundation nearly all monitoring tools build on. It is implemented by essentially every SNMP-capable network device, server, and appliance. This is the single most heavily searched foundational MIB in existence, since RFC 1213 (MIB-II) defines the baseline system/interface/IP/ICMP/TCP/UDP objects that virtually every SNMP-managed device on the internet implements.

IPNetwork Monitor allows you to monitor SNMP objects defined in RFC-1213-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • baseline system identity, uptime, and interface status/traffic

Supported Devices

  • Virtually every SNMP-capable network device, server, and appliance

Monitoring Examples

A monitoring tool queries sysUpTime and walks ifTable to establish basic reachability, uptime, and per-interface status for virtually any SNMP-managed device, using nothing but the universal RFC 1213 MIB-II.

OIDs
OID symbolicOID numericTypeAccessDescription
mib_21.3.6.1.2.1
system1.3.6.1.2.1.1
STR sysDescr1.3.6.1.2.1.1.1DisplayStringread-onlyA 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.
OID sysObjectID1.3.6.1.2.1.1.2OBJECT IDENTIFIERread-onlyThe 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'.
TIK sysUpTime1.3.6.1.2.1.1.3TimeTicksread-onlyThe time (in hundredths of a second) since the network management portion of the system was last re-initialized.
STR sysContact1.3.6.1.2.1.1.4DisplayStringread-writeThe textual identification of the contact person for this managed node, together with information on how to contact this person.
STR sysName1.3.6.1.2.1.1.5DisplayStringread-writeAn administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.
STR sysLocation1.3.6.1.2.1.1.6DisplayStringread-writeThe physical location of this node (e.g., `telephone closet, 3rd floor').
INT sysServices1.3.6.1.2.1.1.7INTEGERread-onlyA 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.
interfaces1.3.6.1.2.1.2
INT ifNumber1.3.6.1.2.1.2.1INTEGERread-onlyThe number of network interfaces (regardless of their current state) present on this system.
ifTable1.3.6.1.2.1.2.2not-accessibleA list of interface entries. The number of entries is given by the value of ifNumber.
ifEntry1.3.6.1.2.1.2.2.1not-accessibleAn interface entry containing objects at the subnetwork layer and below for a particular interface.
INT ifIndex1.3.6.1.2.1.2.2.1.1INTEGERread-onlyA 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.
STR ifDescr1.3.6.1.2.1.2.2.1.2DisplayStringread-onlyA 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.
INT ifType1.3.6.1.2.1.2.2.1.3INTEGERread-onlyThe type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack. Additional entries retrieved at iana.org.
INT ifMtu1.3.6.1.2.1.2.2.1.4INTEGERread-onlyThe 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.
GAU ifSpeed1.3.6.1.2.1.2.2.1.5Gaugeread-onlyAn 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.
PHY ifPhysAddress1.3.6.1.2.1.2.2.1.6PhysAddressread-onlyThe 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.
INT ifAdminStatus1.3.6.1.2.1.2.2.1.7INTEGERread-writeThe desired state of the interface. The testing(3) state indicates that no operational packets can be passed.
INT ifOperStatus1.3.6.1.2.1.2.2.1.8INTEGERread-onlyThe current operational state of the interface. The testing(3) state indicates that no operational packets can be passed.
TIK ifLastChange1.3.6.1.2.1.2.2.1.9TimeTicksread-onlyThe 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.
CTR ifInOctets1.3.6.1.2.1.2.2.1.10Counterread-onlyThe total number of octets received on the interface, including framing characters.
CTR ifInUcastPkts1.3.6.1.2.1.2.2.1.11Counterread-onlyThe number of subnetwork-unicast packets delivered to a higher-layer protocol.
CTR ifInNUcastPkts1.3.6.1.2.1.2.2.1.12Counterread-onlyThe number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
CTR ifInDiscards1.3.6.1.2.1.2.2.1.13Counterread-onlyThe 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.
CTR ifInErrors1.3.6.1.2.1.2.2.1.14Counterread-onlyThe number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
CTR ifInUnknownProtos1.3.6.1.2.1.2.2.1.15Counterread-onlyThe number of packets received via the interface which were discarded because of an unknown or unsupported protocol.
CTR ifOutOctets1.3.6.1.2.1.2.2.1.16Counterread-onlyThe total number of octets transmitted out of the interface, including framing characters.
CTR ifOutUcastPkts1.3.6.1.2.1.2.2.1.17Counterread-onlyThe total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.
CTR ifOutNUcastPkts1.3.6.1.2.1.2.2.1.18Counterread-onlyThe 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.
CTR ifOutDiscards1.3.6.1.2.1.2.2.1.19Counterread-onlyThe 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.
CTR ifOutErrors1.3.6.1.2.1.2.2.1.20Counterread-onlyThe number of outbound packets that could not be transmitted because of errors.
GAU ifOutQLen1.3.6.1.2.1.2.2.1.21Gaugeread-onlyThe length of the output packet queue (in packets).
OID ifSpecific1.3.6.1.2.1.2.2.1.22OBJECT IDENTIFIERread-onlyA 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 syntactically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
at1.3.6.1.2.1.3
atTable1.3.6.1.2.1.3.1not-accessibleThe 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.
atEntry1.3.6.1.2.1.3.1.1not-accessibleEach entry contains one NetworkAddress to `physical' address equivalence.
INT atIfIndex1.3.6.1.2.1.3.1.1.1INTEGERread-writeThe 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.
PHY atPhysAddress1.3.6.1.2.1.3.1.1.2PhysAddressread-writeThe 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.
IP atNetAddress1.3.6.1.2.1.3.1.1.3IpAddressread-writeThe NetworkAddress (e.g., the IP address) corresponding to the media-dependent `physical' address.
ip1.3.6.1.2.1.4
INT ipForwarding1.3.6.1.2.1.4.1INTEGERread-writeThe 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.
INT ipDefaultTTL1.3.6.1.2.1.4.2INTEGERread-writeThe 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.
CTR ipInReceives1.3.6.1.2.1.4.3Counterread-onlyThe total number of input datagrams received from interfaces, including those received in error.
CTR ipInHdrErrors1.3.6.1.2.1.4.4Counterread-onlyThe 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.
CTR ipInAddrErrors1.3.6.1.2.1.4.5Counterread-onlyThe 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.
CTR ipForwDatagrams1.3.6.1.2.1.4.6Counterread-onlyThe 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.
CTR ipInUnknownProtos1.3.6.1.2.1.4.7Counterread-onlyThe number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
CTR ipInDiscards1.3.6.1.2.1.4.8Counterread-onlyThe 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.
CTR ipInDelivers1.3.6.1.2.1.4.9Counterread-onlyThe total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
CTR ipOutRequests1.3.6.1.2.1.4.10Counterread-onlyThe 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.
CTR ipOutDiscards1.3.6.1.2.1.4.11Counterread-onlyThe 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.
CTR ipOutNoRoutes1.3.6.1.2.1.4.12Counterread-onlyThe 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.
INT ipReasmTimeout1.3.6.1.2.1.4.13INTEGERread-onlyThe maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
CTR ipReasmReqds1.3.6.1.2.1.4.14Counterread-onlyThe number of IP fragments received which needed to be reassembled at this entity.
CTR ipReasmOKs1.3.6.1.2.1.4.15Counterread-onlyThe number of IP datagrams successfully re- assembled.
CTR ipReasmFails1.3.6.1.2.1.4.16Counterread-onlyThe 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.
CTR ipFragOKs1.3.6.1.2.1.4.17Counterread-onlyThe number of IP datagrams that have been successfully fragmented at this entity.
CTR ipFragFails1.3.6.1.2.1.4.18Counterread-onlyThe 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.
CTR ipFragCreates1.3.6.1.2.1.4.19Counterread-onlyThe number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
ipAddrTable1.3.6.1.2.1.4.20not-accessibleThe table of addressing information relevant to this entity's IP addresses.
ipAddrEntry1.3.6.1.2.1.4.20.1not-accessibleThe addressing information for one of this entity's IP addresses.
IP ipAdEntAddr1.3.6.1.2.1.4.20.1.1IpAddressread-onlyThe IP address to which this entry's addressing information pertains.
INT ipAdEntIfIndex1.3.6.1.2.1.4.20.1.2INTEGERread-onlyThe 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.
IP ipAdEntNetMask1.3.6.1.2.1.4.20.1.3IpAddressread-onlyThe 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.
INT ipAdEntBcastAddr1.3.6.1.2.1.4.20.1.4INTEGERread-onlyThe 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.
INT ipAdEntReasmMaxSize1.3.6.1.2.1.4.20.1.5INTEGERread-onlyThe size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.
ipRouteTable1.3.6.1.2.1.4.21not-accessibleThis entity's IP Routing table.
ipRouteEntry1.3.6.1.2.1.4.21.1not-accessibleA route to a particular destination.
IP ipRouteDest1.3.6.1.2.1.4.21.1.1IpAddressread-writeThe 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.
INT ipRouteIfIndex1.3.6.1.2.1.4.21.1.2INTEGERread-writeThe 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.
INT ipRouteMetric11.3.6.1.2.1.4.21.1.3INTEGERread-writeThe 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.
INT ipRouteMetric21.3.6.1.2.1.4.21.1.4INTEGERread-writeAn 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.
INT ipRouteMetric31.3.6.1.2.1.4.21.1.5INTEGERread-writeAn 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.
INT ipRouteMetric41.3.6.1.2.1.4.21.1.6INTEGERread-writeAn 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.
IP ipRouteNextHop1.3.6.1.2.1.4.21.1.7IpAddressread-writeThe 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.)
INT ipRouteType1.3.6.1.2.1.4.21.1.8INTEGERread-writeThe 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.
INT ipRouteProto1.3.6.1.2.1.4.21.1.9INTEGERread-onlyThe 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.
INT ipRouteAge1.3.6.1.2.1.4.21.1.10INTEGERread-writeThe 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.
IP ipRouteMask1.3.6.1.2.1.4.21.1.11IpAddressread-writeIndicate 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.
INT ipRouteMetric51.3.6.1.2.1.4.21.1.12INTEGERread-writeAn 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.
OID ipRouteInfo1.3.6.1.2.1.4.21.1.13OBJECT IDENTIFIERread-onlyA 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 syntatcically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
ipNetToMediaTable1.3.6.1.2.1.4.22not-accessibleThe IP Address Translation table used for mapping from IP addresses to physical addresses.
ipNetToMediaEntry1.3.6.1.2.1.4.22.1not-accessibleEach entry contains one IpAddress to `physical' address equivalence.
INT ipNetToMediaIfIndex1.3.6.1.2.1.4.22.1.1INTEGERread-writeThe 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.
PHY ipNetToMediaPhysAddress1.3.6.1.2.1.4.22.1.2PhysAddressread-writeThe media-dependent `physical' address.
IP ipNetToMediaNetAddress1.3.6.1.2.1.4.22.1.3IpAddressread-writeThe IpAddress corresponding to the media- dependent `physical' address.
INT ipNetToMediaType1.3.6.1.2.1.4.22.1.4INTEGERread-writeThe 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.
CTR ipRoutingDiscards1.3.6.1.2.1.4.23Counterread-onlyThe 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.
icmp1.3.6.1.2.1.5
CTR icmpInMsgs1.3.6.1.2.1.5.1Counterread-onlyThe total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
CTR icmpInErrors1.3.6.1.2.1.5.2Counterread-onlyThe number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
CTR icmpInDestUnreachs1.3.6.1.2.1.5.3Counterread-onlyThe number of ICMP Destination Unreachable messages received.
CTR icmpInTimeExcds1.3.6.1.2.1.5.4Counterread-onlyThe number of ICMP Time Exceeded messages received.
CTR icmpInParmProbs1.3.6.1.2.1.5.5Counterread-onlyThe number of ICMP Parameter Problem messages received.
CTR icmpInSrcQuenchs1.3.6.1.2.1.5.6Counterread-onlyThe number of ICMP Source Quench messages received.
CTR icmpInRedirects1.3.6.1.2.1.5.7Counterread-onlyThe number of ICMP Redirect messages received.
CTR icmpInEchos1.3.6.1.2.1.5.8Counterread-onlyThe number of ICMP Echo (request) messages received.
CTR icmpInEchoReps1.3.6.1.2.1.5.9Counterread-onlyThe number of ICMP Echo Reply messages received.
CTR icmpInTimestamps1.3.6.1.2.1.5.10Counterread-onlyThe number of ICMP Timestamp (request) messages received.
CTR icmpInTimestampReps1.3.6.1.2.1.5.11Counterread-onlyThe number of ICMP Timestamp Reply messages received.
CTR icmpInAddrMasks1.3.6.1.2.1.5.12Counterread-onlyThe number of ICMP Address Mask Request messages received.
CTR icmpInAddrMaskReps1.3.6.1.2.1.5.13Counterread-onlyThe number of ICMP Address Mask Reply messages received.
CTR icmpOutMsgs1.3.6.1.2.1.5.14Counterread-onlyThe total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
CTR icmpOutErrors1.3.6.1.2.1.5.15Counterread-onlyThe 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.
CTR icmpOutDestUnreachs1.3.6.1.2.1.5.16Counterread-onlyThe number of ICMP Destination Unreachable messages sent.
CTR icmpOutTimeExcds1.3.6.1.2.1.5.17Counterread-onlyThe number of ICMP Time Exceeded messages sent.
CTR icmpOutParmProbs1.3.6.1.2.1.5.18Counterread-onlyThe number of ICMP Parameter Problem messages sent.
CTR icmpOutSrcQuenchs1.3.6.1.2.1.5.19Counterread-onlyThe number of ICMP Source Quench messages sent.
CTR icmpOutRedirects1.3.6.1.2.1.5.20Counterread-onlyThe number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.
CTR icmpOutEchos1.3.6.1.2.1.5.21Counterread-onlyThe number of ICMP Echo (request) messages sent.
CTR icmpOutEchoReps1.3.6.1.2.1.5.22Counterread-onlyThe number of ICMP Echo Reply messages sent.
CTR icmpOutTimestamps1.3.6.1.2.1.5.23Counterread-onlyThe number of ICMP Timestamp (request) messages sent.
CTR icmpOutTimestampReps1.3.6.1.2.1.5.24Counterread-onlyThe number of ICMP Timestamp Reply messages sent.
CTR icmpOutAddrMasks1.3.6.1.2.1.5.25Counterread-onlyThe number of ICMP Address Mask Request messages sent.
CTR icmpOutAddrMaskReps1.3.6.1.2.1.5.26Counterread-onlyThe number of ICMP Address Mask Reply messages sent.
tcp1.3.6.1.2.1.6
INT tcpRtoAlgorithm1.3.6.1.2.1.6.1INTEGERread-onlyThe algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
INT tcpRtoMin1.3.6.1.2.1.6.2INTEGERread-onlyThe 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.
INT tcpRtoMax1.3.6.1.2.1.6.3INTEGERread-onlyThe 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.
INT tcpMaxConn1.3.6.1.2.1.6.4INTEGERread-onlyThe 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.
CTR tcpActiveOpens1.3.6.1.2.1.6.5Counterread-onlyThe number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
CTR tcpPassiveOpens1.3.6.1.2.1.6.6Counterread-onlyThe number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
CTR tcpAttemptFails1.3.6.1.2.1.6.7Counterread-onlyThe 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.
CTR tcpEstabResets1.3.6.1.2.1.6.8Counterread-onlyThe number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
GAU tcpCurrEstab1.3.6.1.2.1.6.9Gaugeread-onlyThe number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
CTR tcpInSegs1.3.6.1.2.1.6.10Counterread-onlyThe total number of segments received, including those received in error. This count includes segments received on currently established connections.
CTR tcpOutSegs1.3.6.1.2.1.6.11Counterread-onlyThe total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
CTR tcpRetransSegs1.3.6.1.2.1.6.12Counterread-onlyThe total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
tcpConnTable1.3.6.1.2.1.6.13not-accessibleA table containing TCP connection-specific information.
tcpConnEntry1.3.6.1.2.1.6.13.1not-accessibleInformation 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.
INT tcpConnState1.3.6.1.2.1.6.13.1.1INTEGERread-writeThe 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).
IP tcpConnLocalAddress1.3.6.1.2.1.6.13.1.2IpAddressread-onlyThe 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.
INT tcpConnLocalPort1.3.6.1.2.1.6.13.1.3INTEGERread-onlyThe local port number for this TCP connection.
IP tcpConnRemAddress1.3.6.1.2.1.6.13.1.4IpAddressread-onlyThe remote IP address for this TCP connection.
INT tcpConnRemPort1.3.6.1.2.1.6.13.1.5INTEGERread-onlyThe remote port number for this TCP connection.
CTR tcpInErrs1.3.6.1.2.1.6.14Counterread-onlyThe total number of segments received in error (e.g., bad TCP checksums).
CTR tcpOutRsts1.3.6.1.2.1.6.15Counterread-onlyThe number of TCP segments sent containing the RST flag.
udp1.3.6.1.2.1.7
CTR udpInDatagrams1.3.6.1.2.1.7.1Counterread-onlyThe total number of UDP datagrams delivered to UDP users.
CTR udpNoPorts1.3.6.1.2.1.7.2Counterread-onlyThe total number of received UDP datagrams for which there was no application at the destination port.
CTR udpInErrors1.3.6.1.2.1.7.3Counterread-onlyThe number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
CTR udpOutDatagrams1.3.6.1.2.1.7.4Counterread-onlyThe total number of UDP datagrams sent from this entity.
udpTable1.3.6.1.2.1.7.5not-accessibleA table containing UDP listener information.
udpEntry1.3.6.1.2.1.7.5.1not-accessibleInformation about a particular current UDP listener.
IP udpLocalAddress1.3.6.1.2.1.7.5.1.1IpAddressread-onlyThe 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.
INT udpLocalPort1.3.6.1.2.1.7.5.1.2INTEGERread-onlyThe local port number for this UDP listener.
egp1.3.6.1.2.1.8
CTR egpInMsgs1.3.6.1.2.1.8.1Counterread-onlyThe number of EGP messages received without error.
CTR egpInErrors1.3.6.1.2.1.8.2Counterread-onlyThe number of EGP messages received that proved to be in error.
CTR egpOutMsgs1.3.6.1.2.1.8.3Counterread-onlyThe total number of locally generated EGP messages.
CTR egpOutErrors1.3.6.1.2.1.8.4Counterread-onlyThe number of locally generated EGP messages not sent due to resource limitations within an EGP entity.
egpNeighTable1.3.6.1.2.1.8.5not-accessibleThe EGP neighbor table.
egpNeighEntry1.3.6.1.2.1.8.5.1not-accessibleInformation about this entity's relationship with a particular EGP neighbor.
INT egpNeighState1.3.6.1.2.1.8.5.1.1INTEGERread-onlyThe EGP state of the local system with respect to this entry's EGP neighbor. Each EGP state is represented by a value that is one greater than the numerical value associated with said state in RFC 904.
IP egpNeighAddr1.3.6.1.2.1.8.5.1.2IpAddressread-onlyThe IP address of this entry's EGP neighbor.
INT egpNeighAs1.3.6.1.2.1.8.5.1.3INTEGERread-onlyThe autonomous system of this EGP peer. Zero should be specified if the autonomous system number of the neighbor is not yet known.
CTR egpNeighInMsgs1.3.6.1.2.1.8.5.1.4Counterread-onlyThe number of EGP messages received without error from this EGP peer.
CTR egpNeighInErrs1.3.6.1.2.1.8.5.1.5Counterread-onlyThe number of EGP messages received from this EGP peer that proved to be in error (e.g., bad EGP checksum).
CTR egpNeighOutMsgs1.3.6.1.2.1.8.5.1.6Counterread-onlyThe number of locally generated EGP messages to this EGP peer.
CTR egpNeighOutErrs1.3.6.1.2.1.8.5.1.7Counterread-onlyThe number of locally generated EGP messages not sent to this EGP peer due to resource limitations within an EGP entity.
CTR egpNeighInErrMsgs1.3.6.1.2.1.8.5.1.8Counterread-onlyThe number of EGP-defined error messages received from this EGP peer.
CTR egpNeighOutErrMsgs1.3.6.1.2.1.8.5.1.9Counterread-onlyThe number of EGP-defined error messages sent to this EGP peer.
CTR egpNeighStateUps1.3.6.1.2.1.8.5.1.10Counterread-onlyThe number of EGP state transitions to the UP state with this EGP peer.
CTR egpNeighStateDowns1.3.6.1.2.1.8.5.1.11Counterread-onlyThe number of EGP state transitions from the UP state to any other state with this EGP peer.
INT egpNeighIntervalHello1.3.6.1.2.1.8.5.1.12INTEGERread-onlyThe interval between EGP Hello command retransmissions (in hundredths of a second). This represents the t1 timer as defined in RFC 904.
INT egpNeighIntervalPoll1.3.6.1.2.1.8.5.1.13INTEGERread-onlyThe interval between EGP poll command retransmissions (in hundredths of a second). This represents the t3 timer as defined in RFC 904.
INT egpNeighMode1.3.6.1.2.1.8.5.1.14INTEGERread-onlyThe polling mode of this EGP entity, either passive or active.
INT egpNeighEventTrigger1.3.6.1.2.1.8.5.1.15INTEGERread-writeA control variable used to trigger operator- initiated Start and Stop events. When read, this variable always returns the most recent value that egpNeighEventTrigger was set to. If it has not been set since the last initialization of the network management subsystem on the node, it returns a value of `stop'. When set, this variable causes a Start or Stop event on the specified neighbor, as specified on pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor acquisition and a non-Idle peer to reinitiate neighbor acquisition. A stop event causes a non-Idle peer to return to the Idle state until a Start event occurs, either via egpNeighEventTrigger or otherwise.
INT egpAs1.3.6.1.2.1.8.6INTEGERread-onlyThe autonomous system number of this EGP entity.
transmission1.3.6.1.2.1.10
snmp1.3.6.1.2.1.11
CTR snmpInPkts1.3.6.1.2.1.11.1Counterread-onlyThe total number of Messages delivered to the SNMP entity from the transport service.
CTR snmpOutPkts1.3.6.1.2.1.11.2Counterread-onlyThe total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.
CTR snmpInBadVersions1.3.6.1.2.1.11.3Counterread-onlyThe total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version.
CTR snmpInBadCommunityNames1.3.6.1.2.1.11.4Counterread-onlyThe total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity.
CTR snmpInBadCommunityUses1.3.6.1.2.1.11.5Counterread-onlyThe 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.
CTR snmpInASNParseErrs1.3.6.1.2.1.11.6Counterread-onlyThe total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages.
CTR snmpInTooBigs1.3.6.1.2.1.11.8Counterread-onlyThe 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'.
CTR snmpInNoSuchNames1.3.6.1.2.1.11.9Counterread-onlyThe 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'.
CTR snmpInBadValues1.3.6.1.2.1.11.10Counterread-onlyThe 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'.
CTR snmpInReadOnlys1.3.6.1.2.1.11.11Counterread-onlyThe 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.
CTR snmpInGenErrs1.3.6.1.2.1.11.12Counterread-onlyThe 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'.
CTR snmpInTotalReqVars1.3.6.1.2.1.11.13Counterread-onlyThe 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.
CTR snmpInTotalSetVars1.3.6.1.2.1.11.14Counterread-onlyThe 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.
CTR snmpInGetRequests1.3.6.1.2.1.11.15Counterread-onlyThe total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInGetNexts1.3.6.1.2.1.11.16Counterread-onlyThe total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInSetRequests1.3.6.1.2.1.11.17Counterread-onlyThe total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInGetResponses1.3.6.1.2.1.11.18Counterread-onlyThe total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInTraps1.3.6.1.2.1.11.19Counterread-onlyThe total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpOutTooBigs1.3.6.1.2.1.11.20Counterread-onlyThe 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.'
CTR snmpOutNoSuchNames1.3.6.1.2.1.11.21Counterread-onlyThe total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'.
CTR snmpOutBadValues1.3.6.1.2.1.11.22Counterread-onlyThe 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'.
CTR snmpOutGenErrs1.3.6.1.2.1.11.24Counterread-onlyThe 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'.
CTR snmpOutGetRequests1.3.6.1.2.1.11.25Counterread-onlyThe total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutGetNexts1.3.6.1.2.1.11.26Counterread-onlyThe total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutSetRequests1.3.6.1.2.1.11.27Counterread-onlyThe total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutGetResponses1.3.6.1.2.1.11.28Counterread-onlyThe total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutTraps1.3.6.1.2.1.11.29Counterread-onlyThe total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.
INT snmpEnableAuthenTraps1.3.6.1.2.1.11.30INTEGERread-writeIndicates 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.

RFC description

Defines MIB-II base management objects for system, interfaces, IP, ICMP, TCP, UDP, and SNMP groups.

Start monitoring virtually every SNMP-capable network device, server, and appliance (baseline system/interface/protocol statistics) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download RFC-1213-MIB