OID:1.0.8802.1.1.2.1.1.1

The interval at which LLDP frames are transmitted on behalf of this LLDP agent. The default value for lldpMessageTxInterval object is 30 seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system. REFERENCE IEEE 802.1AB-2005 10.5.3.3 DEFVAL { 30 }

OID:1.0.8802.1.1.2.1.1.2

The time-to-live value expressed as a multiple of the lldpMessageTxInterval object. The actual time-to-live value used in LLDP frames, transmitted on behalf of this LLDP agent, can be expressed by the following formula: TTL = min(65535, (lldpMessageTxInterval * lldpMessageTxHoldMultiplier)) For example, if the value of lldpMessageTxInterval is '30', and the value of lldpMessageTxHoldMultiplier is '4', then the value '120' is encoded in the TTL field in the LLDP header. The default value for lldpMessageTxHoldMultiplier object is 4. The value of this object must be restored from non-volatile storage after a re-initialization of the management system. REFERENCE IEEE 802.1AB-2005 10.5.3.3 DEFVAL { 4 }

OID:1.0.8802.1.1.2.1.1.3

The lldpReinitDelay indicates the delay (in units of seconds) from when lldpPortConfigAdminStatus object of a particular port becomes 'disabled' until re-initialization will be attempted. The default value for lldpReintDelay object is two seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system. REFERENCE IEEE 802.1AB-2005 10.5.3.3 DEFVAL { 2 }

OID:1.0.8802.1.1.2.1.1.4

The lldpTxDelay indicates the delay (in units of seconds) between successive LLDP frame transmissions initiated by value/status changes in the LLDP local systems MIB. The recommended value for the lldpTxDelay is set by the following formula: 1 <= lldpTxDelay <= (0.25 * lldpMessageTxInterval) The default value for lldpTxDelay object is two seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system. REFERENCE IEEE 802.1AB-2005 10.5.3.3 DEFVAL { 2 }

OID:1.0.8802.1.1.2.1.1.5

This object controls the transmission of LLDP notifications. the agent must not generate more than one lldpRemTablesChange notification-event in the indicated period, where a 'notification-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional changes in lldpRemoteSystemsData object groups occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of lldpStatsRemTableLastChangeTime to detect any missed lldpRemTablesChange notification-events, e.g. due to throttling or transmission loss. If notification transmission is enabled for particular ports, the suggested default throttling period is 5 seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system. DEFVAL { 5 }

OID:1.0.8802.1.1.2.1.2.1

The value of sysUpTime object (defined in IETF RFC 3418) at the time an entry is created, modified, or deleted in the in tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems. An NMS can use this object to reduce polling of the lldpRemoteSystemsData objects.

OID:1.0.8802.1.1.2.1.2.2

The number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.

OID:1.0.8802.1.1.2.1.2.3

The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects. This counter should be incremented only once when the complete set of information is completely deleted from all related tables. Partial deletions, such as deletion of rows associated with a particular MSAP from some tables, but not from all tables are not allowed, thus should not change the value of this counter.

OID:1.0.8802.1.1.2.1.2.4

The number of times the complete set of information advertised by a particular MSAP could not be entered into tables contained in lldpRemoteSystemsData and lldpExtensions objects because of insufficient resources.

OID:1.0.8802.1.1.2.1.2.5

The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired. This counter should be incremented only once when the complete set of information is completely invalidated (aged out) from all related tables. Partial aging, similar to deletion case, is not allowed, and thus, should not change the value of this counter.

OID:1.0.8802.1.1.2.1.2.6.1.1

The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpStatsTable.

OID:1.0.8802.1.1.2.1.2.6.1.2

The number of LLDP frames transmitted by this LLDP agent on the indicated port. REFERENCE IEEE 802.1AB-2005 10.5.2.1

OID:1.0.8802.1.1.2.1.2.7.1.1

The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpStatsTable.

OID:1.0.8802.1.1.2.1.2.7.1.2

The number of LLDP frames received by this LLDP agent on the indicated port, and then discarded for any reason. This counter can provide an indication that LLDP header formating problems may exist with the local LLDP agent in the sending system or that LLDPDU validation problems may exist with the local LLDP agent in the receiving system. REFERENCE IEEE 802.1AB-2005 10.5.2.2

OID:1.0.8802.1.1.2.1.2.7.1.3

The number of invalid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled. REFERENCE IEEE 802.1AB-2005 10.5.2.2

OID:1.0.8802.1.1.2.1.2.7.1.4

The number of valid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled. REFERENCE IEEE 802.1AB-2005 10.5.2.2

OID:1.0.8802.1.1.2.1.2.7.1.5

The number of LLDP TLVs discarded for any reason by this LLDP agent on the indicated port. REFERENCE IEEE 802.1AB-2005 10.5.2.2

OID:1.0.8802.1.1.2.1.2.7.1.6

The number of LLDP TLVs received on the given port that are not recognized by this LLDP agent on the indicated port. An unrecognized TLV is referred to as the TLV whose type value is in the range of reserved TLV types (000 1001 - 111 1110) in Table 9.1 of IEEE Std 802.1AB-2005. An unrecognized TLV may be a basic management TLV from a later LLDP version. REFERENCE IEEE 802.1AB-2005 10.5.2.2

OID:1.0.8802.1.1.2.1.2.7.1.7

The counter that represents the number of age-outs that occurred on a given port. An age-out is the number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired. This counter is similar to lldpStatsRemTablesAgeouts, except that the counter is on a per port basis. This enables NMS to poll tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems on the indicated port only. This counter should be set to zero during agent initialization and its value should not be saved in non-volatile storage. When a port's admin status changes from 'disabled' to 'rxOnly', 'txOnly' or 'txAndRx', the counter associated with the same port should reset to 0. The agent should also flush all remote system information associated with the same port. This counter should be incremented only once when the complete set of information is invalidated (aged out) from all related tables on a particular port. Partial aging is not allowed, and thus, should not change the value of this counter. REFERENCE IEEE 802.1AB-2005 10.5.2.2

OID:1.0.8802.1.1.2.1.3.1

The type of encoding used to identify the chassis associated with the local system. REFERENCE IEEE 802.1AB-2005 9.5.2.2

OID:1.0.8802.1.1.2.1.3.2

The type of encoding used to identify the chassis associated with the local system. REFERENCE IEEE 802.1AB-2005 9.5.2.2

OID:1.0.8802.1.1.2.1.3.3

The string value used to identify the system name of the local system. If the local agent supports IETF RFC 3418, lldpLocSysName object should have the same value of sysName object. REFERENCE IEEE 802.1AB-2005 9.5.6.2

OID:1.0.8802.1.1.2.1.3.4

The string value used to identify the system description of the local system. If the local agent supports IETF RFC 3418, lldpLocSysDesc object should have the same value of sysDesc object. REFERENCE IEEE 802.1AB-2005 9.5.7.2

OID:1.0.8802.1.1.2.1.3.5

The bitmap value used to identify which system capabilities are supported on the local system. REFERENCE IEEE 802.1AB-2005 9.5.8.1

OID:1.0.8802.1.1.2.1.3.6

The bitmap value used to identify which system capabilities are enabled on the local system. REFERENCE IEEE 802.1AB-2005 9.5.8.2

OID:1.0.8802.1.1.2.1.3.7.1.1

The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpLocPortTable.

OID:1.0.8802.1.1.2.1.3.7.1.2

The type of port identifier encoding used in the associated 'lldpLocPortId' object. REFERENCE IEEE 802.1AB-2005 9.5.3.2

OID:1.0.8802.1.1.2.1.3.7.1.3

The type of port identifier encoding used in the associated 'lldpLocPortId' object. REFERENCE IEEE 802.1AB-2005 9.5.3.2

OID:1.0.8802.1.1.2.1.3.7.1.4

The string value used to identify the 802 LAN station's port description associated with the local system. If the local agent supports IETF RFC 2863, lldpLocPortDesc object should have the same value of ifDescr object. REFERENCE IEEE 802.1AB-2005 9.5.5.2

OID:1.0.8802.1.1.2.1.3.8.1.1

The type of management address identifier encoding used in the associated 'lldpLocManagmentAddr' object. REFERENCE IEEE 802.1AB-2005 9.5.9.3

OID:1.0.8802.1.1.2.1.3.8.1.2

This table contains management address information on the local system known to this agent.

OID:1.0.8802.1.1.2.1.3.8.1.3

The total length of the management address subtype and the management address fields in LLDPDUs transmitted by the local LLDP agent. The management address length field is needed so that the receiving systems that do not implement SNMP will not be required to implement an iana family numbers/address length equivalency table in order to decode the management adress. REFERENCE IEEE 802.1AB-2005 9.5.9.2

OID:1.0.8802.1.1.2.1.3.8.1.4

The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the local system. REFERENCE IEEE 802.1AB-2005 9.5.9.5

OID:1.0.8802.1.1.2.1.3.8.1.5

The integer value used to identify the interface number regarding the management address component associated with the local system. REFERENCE IEEE 802.1AB-2005 9.5.9.6

OID:1.0.8802.1.1.2.1.3.8.1.6

The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the local system agent. REFERENCE IEEE 802.1AB-2005 9.5.9.8

OID:1.0.8802.1.1.2.1.4.1.1.1

A TimeFilter for this entry. See the TimeFilter textual convention in IETF RFC 2021 and http://www.ietf.org/IESG/Implementations/RFC2021-Implementation.txt to see how TimeFilter works. REFERENCE IETF RFC 2021 section 6

OID:1.0.8802.1.1.2.1.4.1.1.2

The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The lldpRemLocalPortNum identifies the port on which the remote system information is received. The value of this object is used as a port index to the lldpRemTable.

OID:1.0.8802.1.1.2.1.4.1.1.3

This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemIndex will wrap between reboots.

OID:1.0.8802.1.1.2.1.4.1.1.4

The type of encoding used to identify the chassis associated with the remote system. REFERENCE IEEE 802.1AB-2005 9.5.2.2

OID:1.0.8802.1.1.2.1.4.1.1.5

The type of encoding used to identify the chassis associated with the remote system. REFERENCE IEEE 802.1AB-2005 9.5.2.2

OID:1.0.8802.1.1.2.1.4.1.1.6

The type of port identifier encoding used in the associated 'lldpRemPortId' object. REFERENCE IEEE 802.1AB-2005 9.5.3.2

OID:1.0.8802.1.1.2.1.4.1.1.7

The type of port identifier encoding used in the associated 'lldpRemPortId' object. REFERENCE IEEE 802.1AB-2005 9.5.3.2

OID:1.0.8802.1.1.2.1.4.1.1.8

The string value used to identify the description of the given port associated with the remote system. REFERENCE IEEE 802.1AB-2005 9.5.5.2

OID:1.0.8802.1.1.2.1.4.1.1.9

The string value used to identify the system name of the remote system. REFERENCE IEEE 802.1AB-2005 9.5.6.2

OID:1.0.8802.1.1.2.1.4.1.1.10

The string value used to identify the system description of the remote system. REFERENCE IEEE 802.1AB-2005 9.5.7.2

OID:1.0.8802.1.1.2.1.4.1.1.11

The bitmap value used to identify which system capabilities are supported on the remote system. REFERENCE IEEE 802.1AB-2005 9.5.8.1

OID:1.0.8802.1.1.2.1.4.1.1.12

The bitmap value used to identify which system capabilities are enabled on the remote system. REFERENCE IEEE 802.1AB-2005 9.5.8.2

OID:1.0.8802.1.1.2.1.4.2.1.1

The type of management address identifier encoding used in the associated 'lldpRemManagmentAddr' object. REFERENCE IEEE 802.1AB-2005 9.5.9.3

OID:1.0.8802.1.1.2.1.4.2.1.2

This table contains one or more rows per management address information on the remote system learned on a particular port contained in the local chassis known to this agent.

OID:1.0.8802.1.1.2.1.4.2.1.3

The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the remote system. REFERENCE IEEE 802.1AB-2005 9.5.9.5

OID:1.0.8802.1.1.2.1.4.2.1.4

The integer value used to identify the interface number regarding the management address component associated with the remote system. REFERENCE IEEE 802.1AB-2005 9.5.9.6

OID:1.0.8802.1.1.2.1.4.2.1.5

The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the remote system agent. REFERENCE IEEE 802.1AB-2005 9.5.9.8

OID:1.3.6.1.2.1.1.1

A textual description of the entity. This value shouldinclude the full name and version identification ofthe system's hardware type, software operating-system,and networking software.

OID:1.3.6.1.2.1.1.2

The vendor's authoritative identification of thenetwork management subsystem contained in the entity.This value is allocated within the SMI enterprisessubtree (1.3.6.1.4.1) and provides an easy andunambiguous means for determining what kind of box' isbeing managed. For example, if vendor Flintstones,Inc.' was assigned the subtree 1.3.6.1.4.1.424242,it could assign the identifier 1.3.6.1.4.1.424242.1.1to its Fred Router'.

OID:1.3.6.1.2.1.1.3

The time (in hundredths of a second) since thenetwork management portion of the system was lastre-initialized.

OID:1.3.6.1.2.1.1.4

The textual identification of the contact person forthis managed node, together with information on howto contact this person. If no contact information isknown, the value is the zero-length string.

OID:1.3.6.1.2.1.1.5

An administratively-assigned name for this managednode. By convention, this is the node's fully-qualifieddomain name. If the name is unknown, the value isthe zero-length string.

OID:1.3.6.1.2.1.1.6

The physical location of this node (e.g., 'telephonecloset, 3rd floor'). If the location is unknown, thevalue is the zero-length string.

OID:1.3.6.1.2.1.1.7

A value which indicates the set of services that thisentity may potentially offer. The value is a sum.This sum initially takes the value zero. Then, foreach layer, L, in the range 1 through 7, that this nodeperforms transactions for, 2 raised to (L - 1) is addedto the sum. For example, a node which performs onlyrouting functions would have a value of 4 (2\^(3-1)).In contrast, a node which is a host offering applicationservices would have a value of 72 (2\&#94;(4-1) + 2\&#94;(7-1)).Note that in the context of the Internet suite ofprotocols, values should be calculated accordingly:layer functionality1 physical (e.g., repeaters)2 datalink/subnetwork (e.g., bridges)3 internet (e.g., supports the IP)4 end-to-end (e.g., supports the TCP)7 applications (e.g., supports the SMTP)For systems including OSI protocols, layers 5 and 6may also be counted.

OID:1.3.6.1.2.1.2.1

The number of network interfaces (regardless of theircurrent state) present on this system.A list of interface entries. The number of entries isgiven by the value of ifNumber.

OID:1.3.6.1.2.1.2.2.1.1

A unique value, greater than zero, for each interface. Itis recommended that values are assigned contiguouslystarting from 1. The value for each interface sub-layermust remain constant at least from one re-initialization ofthe entity's network management system to the next re-initialization.

OID:1.3.6.1.2.1.2.2.1.2

A textual string containing information about theinterface. This string should include the name of themanufacturer, the product name and the version of theinterface hardware/software.

OID:1.3.6.1.2.1.2.2.1.3

The type of interface. Additional values for ifType areassigned by the Internet Assigned Numbers Authority (IANA),through updating the syntax of the IANAifType textualconvention.

OID:1.3.6.1.2.1.2.2.1.4

The size of the largest packet which can be sent/receivedon the interface, specified in octets. For interfaces thatare used for transmitting network datagrams, this is thesize of the largest network datagram that can be sent on theinterface.

OID:1.3.6.1.2.1.2.2.1.5

An estimate of the interface's current bandwidth in bitsper second. For interfaces which do not vary in bandwidthor for those where no accurate estimation can be made, thisobject should contain the nominal bandwidth. If thebandwidth of the interface is greater than the maximum valuereportable by this object then this object should report itsmaximum value (4,294,967,295) and ifHighSpeed must be usedto report the interace's speed. For a sub-layer which hasno concept of bandwidth, this object should be zero.

OID:1.3.6.1.2.1.2.2.1.6

The interface's address at its protocol sub-layer. Forexample, for an 802.x interface, this object normallycontains a MAC address. The interface's media-specific MIBmust define the bit and byte ordering and the format of thevalue of this object. For interfaces which do not have suchan address (e.g., a serial line), this object should containan octet string of zero length.

OID:1.3.6.1.2.1.2.2.1.7

The desired state of the interface. The testing(3) stateindicates that no operational packets can be passed. When amanaged system initializes, all interfaces start withifAdminStatus in the down(2) state. As a result of eitherexplicit management action or per configuration informationretained by the managed system, ifAdminStatus is thenchanged to either the up(1) or testing(3) states (or remainsin the down(2) state).

OID:1.3.6.1.2.1.2.2.1.8

The current operational state of the interface. Thetesting(3) state indicates that no operational packets canbe passed. If ifAdminStatus is down(2) then ifOperStatusshould be down(2). If ifAdminStatus is changed to up(1)then ifOperStatus should change to up(1) if the interface isready to transmit and receive network traffic; it shouldchange to dormant(5) if the interface is waiting forexternal actions (such as a serial line waiting for anincoming connection); it should remain in the down(2) stateif and only if there is a fault that prevents it from goingto the up(1) state; it should remain in the notPresent(6)state if the interface has missing (typically, hardware)components.

OID:1.3.6.1.2.1.2.2.1.9

The value of sysUpTime at the time the interface enteredits current operational state. If the current state wasentered prior to the last re-initialization of the localnetwork management subsystem, then this object contains azero value.

OID:1.3.6.1.2.1.2.2.1.10

The total number of octets received on the interface,including framing characters.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.11

The number of packets, delivered by this sub-layer to ahigher (sub-)layer, which were not addressed to a multicastor broadcast address at this sub-layer.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.12

OID:1.3.6.1.2.1.2.2.1.13

The number of inbound packets which were chosen to bediscarded even though no errors had been detected to preventtheir being deliverable to a higher-layer protocol. Onepossible reason for discarding such a packet could be tofree up buffer space.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.14

For packet-oriented interfaces, the number of inboundpackets that contained errors preventing them from beingdeliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inboundtransmission units that contained errors preventing themfrom being deliverable to a higher-layer protocol.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.15

For packet-oriented interfaces, the number of packetsreceived via the interface which were discarded because ofan unknown or unsupported protocol. For character-orientedor fixed-length interfaces that support protocolmultiplexing the number of transmission units received viathe interface which were discarded because of an unknown orunsupported protocol. For any interface that does notsupport protocol multiplexing, this counter will always be0.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.16

The total number of octets transmitted out of theinterface, including framing characters.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.17

The total number of packets that higher-level protocolsrequested be transmitted, and which were not addressed to amulticast or broadcast address at this sub-layer, includingthose that were discarded or not sent.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.18

OID:1.3.6.1.2.1.2.2.1.19

The number of outbound packets which were chosen to bediscarded even though no errors had been detected to preventtheir being transmitted. One possible reason for discardingsuch a packet could be to free up buffer space.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.20

For packet-oriented interfaces, the number of outboundpackets that could not be transmitted because of errors.For character-oriented or fixed-length interfaces, thenumber of outbound transmission units that could not betransmitted because of errors.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.2.2.1.21

OID:1.3.6.1.2.1.2.2.1.22

OID:1.3.6.1.2.1.5.1

Total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.

OID:1.3.6.1.2.1.5.2

Number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length…

OID:1.3.6.1.2.1.5.3

Number of ICMP Destination Unreachable messages received.

OID:1.3.6.1.2.1.5.4

Number of ICMP Time Exceeded messages received.

OID:1.3.6.1.2.1.5.5

Number of ICMP Parameter Problem messages received.

OID:1.3.6.1.2.1.5.6

Number of ICMP Source Quench messages received.

OID:1.3.6.1.2.1.5.7

OID:1.3.6.1.2.1.5.8

Number of ICMP Echo (request) messages received.

OID:1.3.6.1.2.1.5.9

Number of ICMP Echo Reply messages received.

OID:1.3.6.1.2.1.5.10

Number of ICMP Timestamp (request) messages received.

OID:1.3.6.1.2.1.5.11

Number of ICMP Timestamp Reply messages received.

OID:1.3.6.1.2.1.5.12

Number of ICMP Address Mask Request messages received.

OID:1.3.6.1.2.1.5.13

Number of ICMP Address Mask Reply messages received.

OID:1.3.6.1.2.1.5.14

Total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOut…

OID:1.3.6.1.2.1.5.15

Number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This v…

OID:1.3.6.1.2.1.5.16

The number of ICMP Destination Unreachablemessages sent.

OID:1.3.6.1.2.1.5.17

The number of ICMP Time Exceeded messages sent.

OID:1.3.6.1.2.1.5.18

The number of ICMP Parameter Problem messagessent.

OID:1.3.6.1.2.1.5.19

The number of ICMP Source Quench messages sent.

OID:1.3.6.1.2.1.5.20

The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.

OID:1.3.6.1.2.1.5.21

The number of ICMP Echo (request) messages sent.

OID:1.3.6.1.2.1.5.22

The number of ICMP Echo Reply messages sent.

OID:1.3.6.1.2.1.5.23

The number of ICMP Timestamp (request) messages sent

OID:1.3.6.1.2.1.5.24

The number of ICMP Timestamp Reply messages sent

OID:1.3.6.1.2.1.5.25

The number of ICMP Address Mask Request messages sent

OID:1.3.6.1.2.1.5.26

The number of ICMP Address Mask Reply messages sent

OID:1.3.6.1.2.1.7.1

The total number of UDP datagrams delivered to UDPusers.Discontinuities in the value of this counter can occurat re-initialization of the management system, and atother times as indicated by discontinuities in thevalue of sysUpTime.

OID:1.3.6.1.2.1.7.2

The total number of received UDP datagrams for whichthere was no application at the destination port.Discontinuities in the value of this counter can occurat re-initialization of the management system, and atother times as indicated by discontinuities in thevalue of sysUpTime.

OID:1.3.6.1.2.1.7.3

The number of received UDP datagrams that could not bedelivered for reasons other than the lack of anapplication at the destination port.Discontinuities in the value of this counter can occurat re-initialization of the management system, and atother times as indicated by discontinuities in thevalue of sysUpTime.

OID:1.3.6.1.2.1.7.4

The total number of UDP datagrams sent from thisentity.Discontinuities in the value of this counter can occurat re-initialization of the management system, and atother times as indicated by discontinuities in thevalue of sysUpTime.

OID:1.3.6.1.2.1.7.5.1.1

The local IP address for this UDP listener. In the case of a UDP listener that is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.

OID:1.3.6.1.2.1.7.5.1.2

The local port number for this UDP listener.

OID:1.3.6.1.2.1.11.1

The total number of messages delivered to the SNMPentity from the transport service.

OID:1.3.6.1.2.1.11.3

The total number of SNMP messages which were deliveredto the SNMP entity and were for an unsupported SNMPversion.

OID:1.3.6.1.2.1.11.4

The total number of community-based SNMP messages (forexample, SNMPv1) delivered to the SNMP entity whichused an SNMP community name not known to said entity.Also, implementations which authenticate community-basedSNMP messages using check(s) in addition to matchingthe community name (for example, by also checkingwhether the message originated from a transport addressallowed to use a specified community name) MAY includein this value the number of messages which failed theadditional check(s). It is strongly RECOMMENDED thatthe documentation for any security model which is usedto authenticate community-based SNMP messages specifythe precise conditions that contribute to this value.

OID:1.3.6.1.2.1.11.5

The total number of community-based SNMP messages (forexample, SNMPv1) delivered to the SNMP entity whichrepresented an SNMP operation that was not allowed forthe SNMP community named in the message. The preciseconditions under which this counter is incremented(if at all) depend on how the SNMP entity implementsits access control mechanism and how its applicationsinteract with that access control mechanism. It isstrongly RECOMMENDED that the documentation for anyaccess control mechanism which is used to control accessto and visibility of MIB instrumentation specify theprecise conditions that contribute to this value.

OID:1.3.6.1.2.1.11.6

The total number of ASN.1 or BER errors encountered bythe SNMP entity when decoding received SNMP messages.

OID:1.3.6.1.2.1.11.30

Indicates whether the SNMP entity is permitted togenerate authenticationFailure traps. The value of thisobject overrides any configuration information; as such,it provides a means whereby all authenticationFailuretraps may be disabled.Note that it is strongly recommended that this objectbe stored in non-volatile memory so that it remainsconstant across re-initializations of the networkmanagement system.

OID:1.3.6.1.2.1.11.31

The total number of Confirmed Class PDUs (such asGetRequest-PDUs, GetNextRequest-PDUs,GetBulkRequest-PDUs, SetRequest-PDUs, andInformRequest-PDUs) delivered to the SNMP entity whichwere silently dropped because the size of a replycontaining an alternate Response Class PDU (such as aResponse-PDU) with an empty variable-bindings fieldwas greater than either a local constraint or themaximum message size associated with the originator ofthe request.

OID:1.3.6.1.2.1.11.32

The total number of Confirmed Class PDUs(such as GetRequest-PDUs, GetNextRequest-PDUs,GetBulkRequest-PDUs, SetRequest-PDUs, andInformRequest-PDUs) delivered to the SNMP entity whichwere silently dropped because the transmission ofthe (possibly translated) message to a proxy targetfailed in a manner (other than a time-out) such thatno Response Class PDU (such as a Response-PDU) couldbe returned.

OID:1.3.6.1.2.1.31.1.1.1.1

The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device’s console’. This might be a text name, such as le0' or a simple port number, such as 1', depending on the interface naming syntax of the device. If several entries in the ifTable together represent a single interface as named by the device, then each will have the same value of ifName. Note that for an agent which responds to SNMP queries concerning an interface on some other (proxied) device, then the value of ifName for such an interface is the proxied device’s local name for it. If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.

OID:1.3.6.1.2.1.31.1.1.1.2

The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.3

The number of packets, delivered by this sub-layer to ahigher (sub-)layer, which were addressed to a broadcastaddress at this sub-layer.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.4

The total number of packets that higher-level protocolsrequested be transmitted, and which were addressed to amulticast address at this sub-layer, including those thatwere discarded or not sent. For a MAC layer protocol, thisincludes both Group and Functional addresses.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.5

The total number of packets that higher-level protocolsrequested be transmitted, and which were addressed to abroadcast address at this sub-layer, including those thatwere discarded or not sent.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.6

The total number of octets received on the interface,including framing characters. This object is a 64-bitversion of ifInOctets.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.7

The number of packets, delivered by this sub-layer to ahigher (sub-)layer, which were not addressed to a multicastor broadcast address at this sub-layer. This object is a64-bit version of ifInUcastPkts.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.8

The number of packets, delivered by this sub-layer to ahigher (sub-)layer, which were addressed to a multicastaddress at this sub-layer. For a MAC layer protocol, thisincludes both Group and Functional addresses. This objectis a 64-bit version of ifInMulticastPkts.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.9

The number of packets, delivered by this sub-layer to ahigher (sub-)layer, which were addressed to a broadcastaddress at this sub-layer. This object is a 64-bit versionof ifInBroadcastPkts.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.10

The total number of octets transmitted out of theinterface, including framing characters. This object is a64-bit version of ifOutOctets.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.11

The total number of packets that higher-level protocolsrequested be transmitted, and which were not addressed to amulticast or broadcast address at this sub-layer, includingthose that were discarded or not sent. This object is a64-bit version of ifOutUcastPkts.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.12

The total number of packets that higher-level protocolsrequested be transmitted, and which were addressed to amulticast address at this sub-layer, including those thatwere discarded or not sent. For a MAC layer protocol, thisincludes both Group and Functional addresses. This objectis a 64-bit version of ifOutMulticastPkts.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.13

The total number of packets that higher-level protocolsrequested be transmitted, and which were addressed to abroadcast address at this sub-layer, including those thatwere discarded or not sent. This object is a 64-bit versionof ifOutBroadcastPkts.Discontinuities in the value of this counter can occur atre-initialization of the management system, and at othertimes as indicated by the value ofifCounterDiscontinuityTime.

OID:1.3.6.1.2.1.31.1.1.1.14

Indicates whether linkUp/linkDown traps should be generatedfor this interface.By default, this object should have the value enabled(1) forinterfaces which do not operate on 'top' of any otherinterface (as defined in the ifStackTable), and disabled(2)otherwise.

OID:1.3.6.1.2.1.31.1.1.1.15

An estimate of the interface's current bandwidth in unitsof 1,000,000 bits per second. If this object reports avalue of n' then the speed of the interface is somewhere inthe range of n-500,000' to n+499,999'. For interfaceswhich do not vary in bandwidth or for those where noaccurate estimation can be made, this object should containthe nominal bandwidth. For a sub-layer which has no conceptof bandwidth, this object should be zero.

OID:1.3.6.1.2.1.31.1.1.1.16

This object has a value of false(2) if this interface onlyaccepts packets/frames that are addressed to this station.This object has a value of true(1) when the station acceptsall packets/frames transmitted on the media. The valuetrue(1) is only legal on certain types of media. If legal,setting this object to a value of true(1) may require theinterface to be reset before becoming effective.The value of ifPromiscuousMode does not affect the receptionof broadcast and multicast packets/frames by the interface.

OID:1.3.6.1.2.1.31.1.1.1.17

This object has the value 'true(1)' if the interfacesublayer has a physical connector and the value 'false(2)'otherwise.

OID:1.3.6.1.2.1.31.1.1.1.18

This object is an 'alias' name for the interface asspecified by a network manager, and provides a non-volatile'handle' for the interface.On the first instantiation of an interface, the value ofifAlias associated with that interface is the zero-lengthstring. As and when a value is written into an instance ofifAlias through a network management set operation, then theagent must retain the supplied value in the ifAlias instanceassociated with the same interface for as long as thatinterface remains instantiated, including across all re-initializations/reboots of the network management system,including those which result in a change of the interface'sifIndex value.An example of the value which a network manager might storein this object for a WAN interface is the (Telco's) circuitnumber/identifier of the interface.Some agents may support write-access only for interfaceshaving particular values of ifType. An agent which supportswrite access to this object is required to keep the value innon-volatile storage, but it may limit the length of newvalues depending on how much storage is already occupied bythe current values for other interfaces.

OID:1.3.6.1.2.1.31.1.1.1.19

The value of sysUpTime on the most recent occasion at whichany one or more of this interface's counters suffered adiscontinuity. The relevant counters are the specificinstances associated with this interface of any Counter32 orCounter64 object contained in the ifTable or ifXTable. Ifno such discontinuities have occurred since the last re-initialization of the local management subsystem, then thisobject contains a zero value.

OID:1.3.6.1.2.1.31.1.5

The value of sysUpTime at the time of the last creation ordeletion of an entry in the ifTable. If the number ofentries has been unchanged since the last re-initializationof the local network management subsystem, then this objectcontains a zero value.A list of interface entries. The number of entries isgiven by the value of ifNumber. This table containsadditional objects for the interface table.

[