Skip to main content

SNMP Object Identifiers

Basics and MIB Files

SNMP OID Basics

OID (Object Identifier) is the name for a numeric identifier that is unique for every value in SNMP. This identifier consists of numbers separated by points. The identifier of each child is formed by appending a point and a new number to the identifier of its parent, which naturally produces a tree structure. This tree is stored in the MIB (Management Information Base), which contains names and descriptions of these numeric identifiers.

Warning

Information about the router can be found in the mgmt and private parts of the tree. The private tree for Advantech routers is defined by MIB files accessible in the public repository here: https://bitbucket.org/bbsmartworx/snmp-mib/ (Requires RFC1155-SMI and RFC-1212 modules). These files are up-to-date and determinant. They are readable by any SNMP MIB browser and can be analyzed for exact information on the carried Base Types (data format) of OIDs.

Tips

  • All SNMP values are read-only by default, with the exception of two binary outputs: ioOut0 (.1.3.6.1.4.1.30140.2.3.2.0) and xccntOut1 (.1.3.6.1.4.1.30140.2.1.9.0). These two OIDs are read-write and may be modified via SNMP, provided that write access is enabled in the router's SNMP configuration settings.
  • The router supports SNMP versions v1, v2c, and v3.

Tree Structure

The figure below shows the basic tree structure that is used for creating all OIDs.

Basic Structure
Basic Structure

In the standard MIB tree, the mgmt item is further divided into the following groups:

OIDGroup nameNote
.1.3.6.1.2.1.1systemFor more information, see section System
.1.3.6.1.2.1.2interfacesFor more information, see section Interfaces
.1.3.6.1.2.1.3atNot supported by Advantech routers
.1.3.6.1.2.1.4ipFor more information, see section IP
.1.3.6.1.2.1.5icmpFor more information, see section ICMP
.1.3.6.1.2.1.6tcpFor more information, see section TCP
.1.3.6.1.2.1.7udpFor more information, see section UDP
.1.3.6.1.2.1.8egpNot supported by Advantech routers
.1.3.6.1.2.1.9transmissionNot supported by Advantech routers
.1.3.6.1.2.1.10snmpNot supported by Advantech routers

System

OIDObjectDescription
.1.3.6.1.2.1.1.1sysDescrA textual description of the entity. In Advantech routers, this includes the product name and firmware version.
.1.3.6.1.2.1.1.2sysObjectIDIdentification of the network management subsystem contained in the entity. Contains the OID of the product type in the private tree (see table below).
.1.3.6.1.2.1.1.3sysUpTimeThe time (in hundredths of a second) since the device was last re-initialized.
.1.3.6.1.2.1.1.4sysContactThe textual identification of the contact person, taken from the router’s Configuration (page Services, SNMP). If unknown, this is a zero-length string.
.1.3.6.1.2.1.1.5sysNameSystem name (from the SNMP configuration page). Otherwise, a zero-length string.
.1.3.6.1.2.1.1.6sysLocationThe physical location (from the SNMP configuration page). Otherwise, a zero-length string.
.1.3.6.1.2.1.1.7sysServicesA value indicating the set of services this entity primarily offers. In Advantech routers, the value is 4.

Interfaces

OIDTableDescription
.1.3.6.1.2.1.2.1ifNumberThe number of network interfaces (regardless of their current state).
.1.3.6.1.2.1.2.2ifTableA list of interface entries. This table includes properties for every interface. The number of rows equals the value of ifNumber.

ifTable is the parent element for the group ifEntry (OID .1.3.6.1.2.1.2.2.1), which includes scalar objects storing information about a particular interface. The interface types include:

  • eth*x — Ethernet interface:
    • eth0 — primary Ethernet interface,
    • eth1 — secondary Ethernet interface,
    • eth2 — tertiary Ethernet interface,
  • lan*x — xth single Ethernet port of a switch (from left to right),
  • mwan0 — primary Mobile WAN interface,
  • mwan1 — secondary Mobile WAN interface,
  • wlan*x — WiFi interface:
    • wlan0 — primary Access Point interface,
    • wlan02 — secondary Access Point interface,
    • wlan1 — primary Station interface,
    • wlan2 — tertiary Access Point interface,
    • wlan22 — quaternary Access Point interface,
    • wlan3 — secondary Station interface.

IP

OIDObjectDescription
.1.3.6.1.2.1.4.1ipForwardingIndicates whether this entity is acting as an IP gateway for datagrams that are received but not addressed to it.
.1.3.6.1.2.1.4.2ipDefaultTTLThe default Time-To-Live value inserted into the IP header for datagrams originated by this entity when no TTL is supplied by the transport layer.
.1.3.6.1.2.1.4.3ipInReceivesThe total number of input datagrams received from interfaces, including those received in error.
.1.3.6.1.2.1.4.4ipInHdrErrorsThe number of input datagrams discarded due to errors in their IP headers (e.g., bad checksums or format errors).
.1.3.6.1.2.1.4.5ipInAddrErrorsThe number of input datagrams discarded because the destination IP address was not valid for this entity.
.1.3.6.1.2.1.4.6ipForwDatagramsThe number of datagrams received that were not destined for this entity, prompting an attempt to forward them.
.1.3.6.1.2.1.4.7ipInUnknownProtosThe number of locally addressed datagrams that were discarded because the protocol was unknown or unsupported.
.1.3.6.1.2.1.4.8ipInDiscardsThe number of IP datagrams discarded despite no encountered errors (for example, due to a lack of buffer space).
.1.3.6.1.2.1.4.9ipInDeliversThe total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
.1.3.6.1.2.1.4.10ipOutRequestsThe total number of IP datagrams that local IP user protocols (including ICMP) supplied for transmission.
.1.3.6.1.2.1.4.11ipOutDiscardsThe number of output IP datagrams that were discarded (e.g., for lack of buffer space) even though no error was encountered.
.1.3.6.1.2.1.4.12ipOutNoRoutesThe number of IP datagrams discarded because no route could be found to transmit them.
.1.3.6.1.2.1.4.13ipReasmTimeoutThe maximum number of seconds that received fragments are held while awaiting reassembly.
.1.3.6.1.2.1.4.14ipReasmReqdsThe number of IP fragments received that required reassembly.
.1.3.6.1.2.1.4.15ipReasmOKsThe number of IP datagrams that were successfully reassembled.
.1.3.6.1.2.1.4.16ipReasmFailsThe number of failures detected by the IP reassembly algorithm (due to timeouts or errors).
.1.3.6.1.2.1.4.17ipFragOKsThe number of IP datagrams that have been successfully fragmented.
.1.3.6.1.2.1.4.18ipFragFailsThe number of IP datagrams discarded because they required fragmentation but could not be fragmented.
.1.3.6.1.2.1.4.19ipFragCreatesThe number of IP datagram fragments generated due to fragmentation.
.1.3.6.1.2.1.4.20ipAddrTableNot supported by Advantech routers.
.1.3.6.1.2.1.4.21ipRouteTableNot supported by Advantech routers.
.1.3.6.1.2.1.4.22ipNetToMediaTableNot supported by Advantech routers.
.1.3.6.1.2.1.4.23ipRoutingDiscardsNot supported by Advantech routers.

ICMP

OIDObjectDescription
.1.3.6.1.2.1.5.1icmpInMsgsThe total number of ICMP messages received (including those with errors).
.1.3.6.1.2.1.5.2icmpInErrorsThe number of ICMP messages received that contain errors (e.g., bad checksums, incorrect lengths).
.1.3.6.1.2.1.5.3icmpInDestUnreachsThe number of ICMP Destination Unreachable messages received.
.1.3.6.1.2.1.5.4icmpInTimeExcdsThe number of ICMP Time Exceeded messages received.
.1.3.6.1.2.1.5.5icmpInParmProbsThe number of ICMP Parameter Problem messages received.
.1.3.6.1.2.1.5.6icmpInSrcQuenchsThe number of ICMP Source Quench messages received.
.1.3.6.1.2.1.5.7icmpInRedirectsThe number of ICMP Redirect messages received.
.1.3.6.1.2.1.5.8icmpInEchosThe number of ICMP Echo Request messages received.
.1.3.6.1.2.1.5.9icmpInEchoRepsThe number of ICMP Echo Reply messages received.
.1.3.6.1.2.1.5.10icmpInTimestampsThe number of ICMP Timestamp Request messages received.
.1.3.6.1.2.1.5.11icmpInTimestampRepsThe number of ICMP Timestamp Reply messages received.
.1.3.6.1.2.1.5.12icmpInAddrMasksThe number of ICMP Address Mask Request messages received.
.1.3.6.1.2.1.5.13icmpInAddrMaskRepsThe number of ICMP Address Mask Reply messages received.
.1.3.6.1.2.1.5.14icmpOutMsgsThe total number of ICMP messages attempted to be sent (including those with errors).
.1.3.6.1.2.1.5.15icmpOutErrorsThe number of ICMP messages that were not sent due to errors (e.g., insufficient buffers).
.1.3.6.1.2.1.5.16icmpOutDestUnreachsThe number of ICMP Destination Unreachable messages sent.
.1.3.6.1.2.1.5.17icmpOutTimeExcdsThe number of ICMP Time Exceeded messages sent.
.1.3.6.1.2.1.5.18icmpOutParmProbsThe number of ICMP Parameter Problem messages sent.
.1.3.6.1.2.1.5.19icmpOutSrcQuenchsThe number of ICMP Source Quench messages sent.
.1.3.6.1.2.1.5.20icmpOutRedirectsThe number of ICMP Redirect messages sent (hosts typically send 0 redirects).
.1.3.6.1.2.1.5.21icmpOutEchosThe number of ICMP Echo Request messages sent.
.1.3.6.1.2.1.5.22icmpOutEchoRepsThe number of ICMP Echo Reply messages sent.
.1.3.6.1.2.1.5.23icmpOutTimestampsThe number of ICMP Timestamp Request messages sent.
.1.3.6.1.2.1.5.24icmpOutTimestampRepsThe number of ICMP Timestamp Reply messages sent.
.1.3.6.1.2.1.5.25icmpOutAddrMasksThe number of ICMP Address Mask Request messages sent.
.1.3.6.1.2.1.5.26icmpOutAddrMaskRepsThe number of ICMP Address Mask Reply messages sent.

TCP

OIDObjectDescription
.1.3.6.1.2.1.6.1tcpRtoAlgorithmThe algorithm used to determine the retransmission timeout for unacknowledged segments.
.1.3.6.1.2.1.6.2tcpRtoMinThe minimum retransmission timeout allowed (in milliseconds).
.1.3.6.1.2.1.6.3tcpRtoMaxThe maximum retransmission timeout allowed (in milliseconds).
.1.3.6.1.2.1.6.4tcpMaxConnThe maximum number of TCP connections supported. A value of -1 indicates a dynamic limit.
.1.3.6.1.2.1.6.5tcpActiveOpensThe number of times TCP connections have actively opened (transitioning from CLOSED to SYN-SENT).
.1.3.6.1.2.1.6.6tcpPassiveOpensThe number of times TCP connections have been passively opened (transitioning from LISTEN to SYN-RCVD).
.1.3.6.1.2.1.6.7tcpAttemptFailsThe number of failed attempts to establish a TCP connection.
.1.3.6.1.2.1.6.8tcpEstabResetsThe number of TCP connections that have been reset from the ESTABLISHED or CLOSE-WAIT states.
.1.3.6.1.2.1.6.9tcpCurrEstabThe current number of TCP connections in the ESTABLISHED or CLOSE-WAIT states.
.1.3.6.1.2.1.6.10tcpInSegsThe total number of TCP segments received, including erroneous segments.
.1.3.6.1.2.1.6.11tcpOutSegsThe total number of TCP segments sent (excluding pure retransmissions).
.1.3.6.1.2.1.6.12tcpRetransSegsThe total number of TCP segments retransmitted.
.1.3.6.1.2.1.6.13tcpConnTableNot supported by Advantech routers.
.1.3.6.1.2.1.6.14tcpInErrsNot supported by Advantech routers.
.1.3.6.1.2.1.6.15tcpOutRstsNot supported by Advantech routers.

UDP

OIDObjectDescription
.1.3.6.1.2.1.7.1udpInDatagramThe total number of UDP datagrams delivered to UDP users.
.1.3.6.1.2.1.7.2udpNoPortsThe number of UDP datagrams received for which there was no application at the destination port.
.1.3.6.1.2.1.7.3udpInErrorsThe number of UDP datagrams that could not be delivered for reasons other than the absence of an application.
.1.3.6.1.2.1.7.4udpOutDatagramsThe total number of UDP datagrams sent from this entity.
.1.3.6.1.2.1.7.5udpTableNot supported by Advantech routers.

Private Tree for Advantech Routers

This chapter describes the SNMP values specific to the Advantech Czech company (formerly Conel). The tree starts at OID = .1.3.6.1.4.1.30140 and can be interpreted as:

iso.org.dod.internet.private.enterprises.conel

The figure below shows the tree used for creating Conel OIDs for Advantech routers.

Private Tree for Advantech Routers
Private Tree for Advantech Routers

Tips

Subtrees mobile and mobile-2 are not available for routers that do not have a cellular module.

Product OIDs

For products manufactured by Advantech Czech (formerly Conel), the following range of OIDs is used in sysObjectID (see section System):

Warning

Note on the OID Scheme (.1.3.6.1.4.1.30140.1.X):

The meaning of the last value (X) in the OID string depends on the product generation:

  • Legacy Scheme (X < 1000): X is a sequential number assigned to older products (e.g., X=42 for the ICR-321x series).
  • New Scheme (X > 1000): For newly introduced products and selected existing models, X corresponds directly to the numeric product identifier (e.g., X=3211 for the ICR-3211). In this new scheme, the OID name follows the format routerICRX.
OIDNameProduct
.1.3.6.1.4.1.30140.1.1routerER75EDGE router ER75
.1.3.6.1.4.1.30140.1.2routerER75iEDGE router ER75i
.1.3.6.1.4.1.30140.1.3routerUR5UMTS router UR5
.1.3.6.1.4.1.30140.1.4routerUR5iUMTS router UR5i
.1.3.6.1.4.1.30140.1.5routerXR5iIndustrial router XR5i
.1.3.6.1.4.1.30140.1.6routerER75iV2EDGE router ER75i v2
.1.3.6.1.4.1.30140.1.7routerUR5V2UMTS router UR5 v2
.1.3.6.1.4.1.30140.1.8routerUR5iV2UMTS router UR5i v2
.1.3.6.1.4.1.30140.1.9routerXR5iV2Industrial router XR5i v2
.1.3.6.1.4.1.30140.1.10routerLR77V2LTE router LR77 v2
.1.3.6.1.4.1.30140.1.11routerCR10V2CDMA router CR10 v2
.1.3.6.1.4.1.30140.1.12routerUCR11V2CDMA/UMTS router UCR11 v2
.1.3.6.1.4.1.30140.1.13routerUR5iV2LHSPA+ router UR5i v2 Libratum
.1.3.6.1.4.1.30140.1.14routerSpectre3GHSPA+ router UR5i v2 SL for US
.1.3.6.1.4.1.30140.1.15routerSpectreRTIndustrial router XR5i v2 SL for US
.1.3.6.1.4.1.30140.1.16routerRR75iGSM-R router RR75i v2
.1.3.6.1.4.1.30140.1.17routerSpectreLTEATLTE router LR77 v2 SL for US AT&T
.1.3.6.1.4.1.30140.1.18routerXR5iV2EIndustrial router XR5i v2 Libratum
.1.3.6.1.4.1.30140.1.19routerBiviasV2HCTwin cellular module router Bivias v2 HC
.1.3.6.1.4.1.30140.1.20routerBiviasV2LCTwin cellular module router Bivias v2 LC
.1.3.6.1.4.1.30140.1.21routerSpectreLTEVZLTE router LR77 v2 SL for US Verizon
.1.3.6.1.4.1.30140.1.22routerBiviasV2LLTwin cellular module router Bivias v2 LL
.1.3.6.1.4.1.30140.1.23routerBiviasV2LHTwin cellular module router Bivias v2 LH
.1.3.6.1.4.1.30140.1.24routerBiviasV2HHTwin cellular module router Bivias v2 HH
.1.3.6.1.4.1.30140.1.25routerLR77V2LLTE router LR77 v2 Libratum
.1.3.6.1.4.1.30140.1.26routerSpectreV3HSPAnot launched
.1.3.6.1.4.1.30140.1.27routerSpectreV3LTELTE router SmartFlex
.1.3.6.1.4.1.30140.1.28routerSpectreV3CDMAnot launched
.1.3.6.1.4.1.30140.1.29routerSpectreV3ERTIndustrial router SmartFlex SR300
.1.3.6.1.4.1.30140.1.32routerSpectreV3TLTETwin module LTE router SmartMotion
.1.3.6.1.4.1.30140.1.35routerSpectreV3LTEUSLTE router SmartFlex for US
.1.3.6.1.4.1.30140.1.36routerSpectreV3LLTELTE router SmartStart
.1.3.6.1.4.1.30140.1.37routerSpectreV3LLTEUSLTE router SmartStart for US
.1.3.6.1.4.1.30140.1.38routerSpectreV3ERTUSnot launched
.1.3.6.1.4.1.30140.1.39routerSpectreV3LERTnot launched
.1.3.6.1.4.1.30140.1.40routerSpectreV3LERTUSnot launched
.1.3.6.1.4.1.30140.1.41routerSpectreV3TLTEUSnot launched
.1.3.6.1.4.1.30140.1.42routerICR321XLTE router ICR-321x
.1.3.6.1.4.1.30140.1.43routerICR323XLTE router ICR-323x
.1.3.6.1.4.1.30140.1.44routerICR324XLTE router ICR-324x
.1.3.6.1.4.1.30140.1.45routerICR320XLAN router ICR-320x
.1.3.6.1.4.1.30140.1.46routerICR383XLTE industrial router ICR-383x
.1.3.6.1.4.1.30140.1.47routerICR213XHSPA+ industrial router ICR-213x
.1.3.6.1.4.1.30140.1.48routerICR233XLTE industrial router ICR-233x
.1.3.6.1.4.1.30140.1.49routerICR440XLAN industrial router ICR-440x
.1.3.6.1.4.1.30140.1.50routerICR443XLTE industrial router ICR-443x
.1.3.6.1.4.1.30140.1.51routerICR444XLTE industrial router ICR-444x
.1.3.6.1.4.1.30140.1.52routerICR203XLTE industrial router ICR-203x
.1.3.6.1.4.1.30140.1.53routerICR204XLTE industrial router ICR-204x
.1.3.6.1.4.1.30140.1.54routerICR240XLAN industrial router ICR-240x
.1.3.6.1.4.1.30140.1.55routerICR243XLTE industrial router ICR-243x
.1.3.6.1.4.1.30140.1.56routerICR244XLTE industrial router ICR-244x
.1.3.6.1.4.1.30140.1.57routerICR201XLTE industrial router ICR-201X
.1.3.6.1.4.1.30140.1.58routerICR241XLTE industrial router ICR-241X
.1.3.6.1.4.1.30140.1.59routerICR445XLTE industrial router ICR-445X
.1.3.6.1.4.1.30140.1.60routerICR446XLTE industrial router ICR-446X
.1.3.6.1.4.1.30140.1.61routerICR250XLTE industrial router ICR-250X
.1.3.6.1.4.1.30140.1.62routerICR253XLTE industrial router ICR-253X
.1.3.6.1.4.1.30140.1.63routerICR254XLTE industrial router ICR-254X
.1.3.6.1.4.1.30140.1.64routerICR260XLTE industrial router ICR-260X
.1.3.6.1.4.1.30140.1.65routerICR263XLTE industrial router ICR-263X
.1.3.6.1.4.1.30140.1.66routerICR264XLTE industrial router ICR-264X
.1.3.6.1.4.1.30140.1.67routerICR270XLAN industrial router ICR-270X
.1.3.6.1.4.1.30140.1.68routerICR271XLTE industrial router ICR-271X
.1.3.6.1.4.1.30140.1.69routerICR273XLTE industrial router ICR-273X
.1.3.6.1.4.1.30140.1.70routerICR274XLTE industrial router ICR-274X
.1.3.6.1.4.1.30140.1.71routerICR280XLAN industrial router ICR-280X
.1.3.6.1.4.1.30140.1.72routerICR281XLTE industrial router ICR-281X
.1.3.6.1.4.1.30140.1.73routerICR283XLTE industrial router ICR-283X
.1.3.6.1.4.1.30140.1.74routerICR284XLTE industrial router ICR-284X
.1.3.6.1.4.1.30140.1.75routerICR410XLAN industrial router ICR-410X
.1.3.6.1.4.1.30140.1.76routerICR413XLTE industrial router ICR-413X
.1.3.6.1.4.1.30140.1.77routerICR414XLTE industrial router ICR-414X
.1.3.6.1.4.1.30140.1.78routerICR416X5G industrial router ICR-416X
.1.3.6.1.4.1.30140.1.79routerICR417X5G industrial router ICR-417X
.1.3.6.1.4.1.30140.1.80routerICR420XLAN industrial router ICR-420X
.1.3.6.1.4.1.30140.1.81routerICR423XLTE industrial router ICR-423X
.1.3.6.1.4.1.30140.1.82routerICR424XLTE industrial router ICR-424X
.1.3.6.1.4.1.30140.1.83routerICR426X5G industrial router ICR-426X
.1.3.6.1.4.1.30140.1.84routerICR427X5G industrial router ICR-427X
.1.3.6.1.4.1.30140.1.85routerICR160XLTE industrial router ICR-160X
.1.3.6.1.4.1.30140.1.86routerICR164XLTE industrial router ICR-164X
.1.3.6.1.4.1.30140.1.87routerICR170X5G industrial router ICR-170X
.1.3.6.1.4.1.30140.1.88routerICR174X5G industrial router ICR-174X
.1.3.6.1.4.1.30140.1.89routerICR447X5G industrial router ICR-447X
.1.3.6.1.4.1.30140.1.2452routerICR2452LAN industrial router ICR-2452
.1.3.6.1.4.1.30140.1.2701routerICR2701LAN industrial router ICR-2701
.1.3.6.1.4.1.30140.1.2734routerICR2734LTE industrial router ICR-2734
.1.3.6.1.4.1.30140.1.2834routerICR2834LTE industrial router ICR-2834
.1.3.6.1.4.1.30140.1.3211routerICR3211LTE industrial router ICR-3211
.1.3.6.1.4.1.30140.1.3231routerICR3231LTE industrial router ICR-3231
.1.3.6.1.4.1.30140.1.3232routerICR3232LTE industrial router ICR-3232
.1.3.6.1.4.1.30140.1.3241routerICR3241LTE industrial router ICR-3241

Protocols

XC-CNT

Tips

To use the xccnt part of the tree, you must use a v2 router with the XC-CNT interface (expansion board) installed and activated on the SNMP configuration page. See the Configuration Manual for v2 Routers for more details. It is possible to set the binary output xccntOut1 (.1.3.6.1.4.1.30140.2.1.9.0) via SNMP. Other values are read-only. The following range of OIDs is used for the CNT expansion port:

OIDNameDescription
.1.3.6.1.4.1.30140.2.1.1.0xccntAn1Analogy input AN1 (range 0-4095)
.1.3.6.1.4.1.30140.2.1.2.0xccntAn2Analogy input AN2 (range 0-4095)
.1.3.6.1.4.1.30140.2.1.3.0xccntCnt1Counter input CNT1 (range 0-4294967295)
.1.3.6.1.4.1.30140.2.1.4.0xccntCnt2Counter input CNT2 (range 0-4294967295)
.1.3.6.1.4.1.30140.2.1.5.0xccntBin1Digital input BIN1 (values 0,1)
.1.3.6.1.4.1.30140.2.1.6.0xccntBin2Digital input BIN2 (values 0,1)
.1.3.6.1.4.1.30140.2.1.7.0xccntBin3Digital input BIN3 (values 0,1)
.1.3.6.1.4.1.30140.2.1.8.0xccntBin4Digital input BIN4 (values 0,1)
.1.3.6.1.4.1.30140.2.1.9.0xccntOut1Digital output OUT1 (values 0,1)

M-BUS

Tips

The following range of OIDs is used for the M-BUS expansion port. It can be used only in v2 routers and requires enabling SNMP output on the SNMP configuration page (Enable M-BUS extension). There are 255 branches in the M-BUS tree. Each branch is defined by the M-BUS device address in hexadecimal (named mbus00 to mbusFF, corresponding to addresses 0 to 255). Every address branch carries the following range of OIDs:

OIDNameDescription
.1.3.6.1.4.1.30140.2.2.<address>.1.0IdNumberNumber of meter
.1.3.6.1.4.1.30140.2.2.<address>.2.0ManufacturerManufacturer
.1.3.6.1.4.1.30140.2.2.<address>.3.0VersionSpecified meter version
.1.3.6.1.4.1.30140.2.2.<address>.4.0MediumType of metered medium
.1.3.6.1.4.1.30140.2.2.<address>.5.0StatusErrors report
.1.3.6.1.4.1.30140.2.2.<address>.6.0VIF00Value information field
.1.3.6.1.4.1.30140.2.2.<address>.7.0Value00Output
.1.3.6.1.4.1.30140.2.2.<address>.8.0VIF011. VIF — value information field
.1.3.6.1.4.1.30140.2.2.<address>.9.0Value011. measured value
.........
.1.3.6.1.4.1.30140.2.2.<address>.100.0VIF2F47. VIF — value information field
.1.3.6.1.4.1.30140.2.2.<address>.101.0Value2F47. measured value

Where <address> is a number from 0 to 255 (usable addresses are 0 to 250; the remainder are reserved or used for broadcast).

Digital Input and Output

Tips

It is necessary to activate I/O reading on the SNMP page in the router's web interface. One digital output, ioOut0 (.1.3.6.1.4.1.30140.2.3.2.0), can be set via SNMP. All other values are read-only. The following range of OIDs is used for digital input and output:

OIDNameDescription
.1.3.6.1.4.1.30140.2.3.1.0ioBin0Digital input BIN0 (values 0,1)
.1.3.6.1.4.1.30140.2.3.2.0ioOut0Digital output OUT0 (values 0,1)
.1.3.6.1.4.1.30140.2.3.3.0ioBin1Digital input BIN1 (values 0,1)
.1.3.6.1.4.1.30140.2.3.4.0ioOut1Digital output OUT1 (values 0,1)
.1.3.6.1.4.1.30140.2.3.5.0ioBin2Digital input BIN2 (values 0,1)
.1.3.6.1.4.1.30140.2.3.6.0ioOut2Digital output OUT2 (values 0,1)
.1.3.6.1.4.1.30140.2.3.7.0ioBin3Digital input BIN3 (values 0,1)
.1.3.6.1.4.1.30140.2.3.8.0—N/A

Status

OIDNameDescription
.1.3.6.1.4.1.30140.3.1.0statusMBusOverload1M-BUS overload 1 (values 0,1)
.1.3.6.1.4.1.30140.3.2.0statusMBusOverload2M-BUS overload 2 (values 0,1)
.1.3.6.1.4.1.30140.3.3.0statusTemperatureInternal temperature¹
.1.3.6.1.4.1.30140.3.4.0statusVoltagePower voltage (input power supply)¹
.1.3.6.1.4.1.30140.3.5.0²statusRTCBatteryRTC backup battery state: 0 = unknown, 1 = ok, 2 = empty
.1.3.6.1.4.1.30140.3.6.0statusCPUUsageCPU Usage (in %)
.1.3.6.1.4.1.30140.3.7.0statusRAMUsageRAM Usage (in %)
.1.3.6.1.4.1.30140.3.8.0statusRAMUsedRAM Used (in bytes)
.1.3.6.1.4.1.30140.3.9.0statusRAMFreeRAM Free (in bytes)
.1.3.6.1.4.1.30140.3.10.0statusRAMTotalRAM Total (in bytes)

¹Information about power voltage and internal temperature is available only for routers with firmware 3.0.4 and later (and for v2 routers with an RB-v2-6 board or later). It is not supported by ICR-2[0|4|5|6]xx routers.

²Supported on routers of v3 platform only.

Mobile

OIDNameDescription
.1.3.6.1.4.1.30140.4.1.0mobileTechnologyValues 0–24, see Mobile Technology Values
.1.3.6.1.4.1.30140.4.2.0mobilePLMNOperator code
.1.3.6.1.4.1.30140.4.3.0mobileCellCell
.1.3.6.1.4.1.30140.4.4.0mobileChannelChannel
.1.3.6.1.4.1.30140.4.5.0mobileSignalStrengthSignal strength for cell (dBm)
.1.3.6.1.4.1.30140.4.6.0mobileChannelN1Adjacent channel No. 1
.1.3.6.1.4.1.30140.4.7.0mobileSignalStrengthN1Signal strength for adjacent channel No. 1
.1.3.6.1.4.1.30140.4.8.0mobileChannelN2Adjacent channel No. 2
.1.3.6.1.4.1.30140.4.9.0mobileSignalStrengthN2Signal strength for adjacent channel No. 2
.1.3.6.1.4.1.30140.4.10.0mobileChannelN3Adjacent channel No. 3
.1.3.6.1.4.1.30140.4.11.0mobileSignalStrengthN3Signal strength for adjacent channel No. 3
.1.3.6.1.4.1.30140.4.12.0mobileChannelN4Adjacent channel No. 4
.1.3.6.1.4.1.30140.4.13.0mobileSignalStrengthN4Signal strength for adjacent channel No. 4
.1.3.6.1.4.1.30140.4.14.0mobileChannelN5Adjacent channel No. 5
.1.3.6.1.4.1.30140.4.15.0mobileSignalStrengthN5Signal strength for adjacent channel No. 5
.1.3.6.1.4.1.30140.4.16.0mobileUpTimeTime since the connection was established
.1.3.6.1.4.1.30140.4.17.0mobileConnectTimestamp of the last connection (or 0)
.1.3.6.1.4.1.30140.4.18.0mobileDisconnectTimestamp when the connection was lost
.1.3.6.1.4.1.30140.4.19.0mobileCardSIM card number: primary (0), secondary (1), or tertiary (2)
.1.3.6.1.4.1.30140.4.20.0mobileIPAddressAssigned IP address (or zeros)
.1.3.6.1.4.1.30140.4.21.0mobileLatencyResponse time (valid only when sending a trap; otherwise 0)
.1.3.6.1.4.1.30140.4.22.0mobileReportPeriodReporting period to R-SeeNet
.1.3.6.1.4.1.30140.4.23.0mobileRegistrationNetwork registration state: unknown (0), idle (1), search (2), denied (3), home (4) or foreign (5)
.1.3.6.1.4.1.30140.4.24.0mobileOperatorMobile network operator
.1.3.6.1.4.1.30140.4.25.0mobileLACLocation Area Code
.1.3.6.1.4.1.30140.4.26.0mobileSignalQualitySignal quality of the selected cell
.1.3.6.1.4.1.30140.4.27.0mobileCSQSignal strength number (0 to 31)
.1.3.6.1.4.1.30140.4.28.0mobilePNOffset[obsolete] PN Offset (0 to 511)
.1.3.6.1.4.1.30140.4.29.0mobileBandCellular band
.1.3.6.1.4.1.30140.4.30.0mobileRSSIRSSI signal strength
.1.3.6.1.4.1.30140.4.31.0mobileRSCPRSCP signal strength
.1.3.6.1.4.1.30140.4.32.0mobileRSRPRSRP signal strength
.1.3.6.1.4.1.30140.4.33.0mobileRSRQRSRQ signal strength
.1.3.6.1.4.1.30140.4.34.0mobileEcIoEc/Io signal strength
.1.3.6.1.4.1.30140.4.35.0mobileNRBandNR Cellular band
.1.3.6.1.4.1.30140.4.36.0mobileNRChannelNR channel
.1.3.6.1.4.1.30140.4.37.0mobileNRRSSINR RSSI signal strength
.1.3.6.1.4.1.30140.4.38.0mobileNRRSRPNR RSRP signal strength
.1.3.6.1.4.1.30140.4.39.0mobileNRRSRQNR RSRQ signal strength
.1.3.6.1.4.1.30140.4.40.0mobileNRSINRNR SINR signal strength
.1.3.6.1.4.1.30140.4.41.0mobileSINRSINR signal strength
.1.3.6.1.4.1.30140.4.101.0mobile2TechnologySecond cellular module: Values 0–24, see Mobile Technology Values
.1.3.6.1.4.1.30140.4.102.0mobile2PLMNSecond cellular module: Operator code
.1.3.6.1.4.1.30140.4.103.0mobile2CellSecond cellular module: Cell
.1.3.6.1.4.1.30140.4.104.0mobile2ChannelSecond cellular module: Channel
.1.3.6.1.4.1.30140.4.105.0mobile2SignalStrengthSecond cellular module: Signal strength for cell (dBm)
.1.3.6.1.4.1.30140.4.106.0mobile2ChannelN1Second cellular module: Adjacent channel No. 1
.1.3.6.1.4.1.30140.4.107.0mobile2SignalStrengthN1Second cellular module: Signal strength for adjacent channel No. 1
.1.3.6.1.4.1.30140.4.108.0mobile2ChannelN2Second cellular module: Adjacent channel No. 2
.1.3.6.1.4.1.30140.4.109.0mobile2SignalStrengthN2Second cellular module: Signal strength for adjacent channel No. 2
.1.3.6.1.4.1.30140.4.110.0mobile2ChannelN3Second cellular module: Adjacent channel No. 3
.1.3.6.1.4.1.30140.4.111.0mobile2SignalStrengthN3Second cellular module: Signal strength for adjacent channel No. 3
.1.3.6.1.4.1.30140.4.112.0mobile2ChannelN4Second cellular module: Adjacent channel No. 4
.1.3.6.1.4.1.30140.4.113.0mobile2SignalStrengthN4Second cellular module: Signal strength for adjacent channel No. 4
.1.3.6.1.4.1.30140.4.114.0mobile2ChannelN5Second cellular module: Adjacent channel No. 5
.1.3.6.1.4.1.30140.4.115.0mobile2SignalStrengthN5Second cellular module: Signal strength for adjacent channel No. 5
.1.3.6.1.4.1.30140.4.116.0mobile2UpTimeSecond cellular module: Elapsed time since the connection was established
.1.3.6.1.4.1.30140.4.117.0mobile2ConnectSecond cellular module: Timestamp of the last connection (otherwise 0)
.1.3.6.1.4.1.30140.4.118.0mobile2DisconnectSecond cellular module: Timestamp of the last disconnection event
.1.3.6.1.4.1.30140.4.119.0mobile2CardSecond cellular module: SIM card number: primary (0), secondary (1) or tertiary (2)
.1.3.6.1.4.1.30140.4.120.0mobile2IPAddressSecond cellular module: Assigned IP address (or zeros)
.1.3.6.1.4.1.30140.4.121.0mobile2LatencySecond cellular module: Response time — valid only when sending trap (otherwise 0)
.1.3.6.1.4.1.30140.4.122.0mobile2ReportPeriodSecond cellular module: Period of sending reports to the R-SeeNet
.1.3.6.1.4.1.30140.4.123.0mobile2RegistrationSecond cellular module: State of the network registration: unknown (0), idle (1), search (2), denied (3), home (4) or foreign (5)
.1.3.6.1.4.1.30140.4.124.0mobile2OperatorSecond cellular module: Mobile network (operator) the router is connected to
.1.3.6.1.4.1.30140.4.125.0mobile2LACSecond cellular module: Location Area Code
.1.3.6.1.4.1.30140.4.126.0mobile2SignalQualitySecond cellular module: Signal quality of the selected cell
.1.3.6.1.4.1.30140.4.127.0mobile2CSQSecond cellular module: Signal strength number (0 to 31)
.1.3.6.1.4.1.30140.4.128.0mobile2PNOffsetSecond cellular module: PN Offset (0 to 511)
.1.3.6.1.4.1.30140.4.129.0mobile2BandSecond cellular module: Cellular band
.1.3.6.1.4.1.30140.4.130.0mobile2RSSISecond cellular module: RSSI signal strength
.1.3.6.1.4.1.30140.4.131.0mobile2RSCPSecond cellular module: RSCP signal strength
.1.3.6.1.4.1.30140.4.132.0mobile2RSRPSecond cellular module: RSRP signal strength
.1.3.6.1.4.1.30140.4.133.0mobile2RSRQSecond cellular module: RSRQ signal strength
.1.3.6.1.4.1.30140.4.134.0mobile2EcIoSecond cellular module: Ec/Io signal strength
.1.3.6.1.4.1.30140.4.135.0mobile2NRBandSecond cellular module: NR Cellular band
.1.3.6.1.4.1.30140.4.136.0mobile2NRChannelSecond cellular module: NR channel
.1.3.6.1.4.1.30140.4.137.0mobile2NRRSSISecond cellular module: NR RSSI signal strength
.1.3.6.1.4.1.30140.4.138.0mobile2NRRSRPSecond cellular module: NR RSRP signal strength
.1.3.6.1.4.1.30140.4.139.0mobile2NRRSRQSecond cellular module: NR RSRQ signal strength
.1.3.6.1.4.1.30140.4.140.0mobile2NRSINRSecond cellular module: NR SINR signal strength
.1.3.6.1.4.1.30140.4.141.0mobile2SINRSecond cellular module: SINR signal strength

Mobile Technology Values

ValueMeaning
0none
2gprs
4edge
6umts
8hsdpa
10hsupa
12hspa
14lte
16cdma
18evdo
20evdo0
22evdoA
24evdoB
26nbiot
28lteM
30nr5gNSA
32nr5gSA

Mobile-2

These OIDs are statistical values for the cellular connection. They provide analytic data for various periods. The items listed below for MobileToday serve as a template for corresponding groups such as MobileYesterday, MobileThisWeek, MobileLastWeek, MobileThisPeriod, and MobileLastPeriod.

MobileToday

OIDNameDescription
.1.3.6.1.4.1.30140.5.1.1.0mobileTodayRxPriReceived data — primary SIM card
.1.3.6.1.4.1.30140.5.1.2.0mobileTodayRxSecReceived data — secondary SIM card
.1.3.6.1.4.1.30140.5.1.3.0mobileTodayTxPriSent data — primary SIM card
.1.3.6.1.4.1.30140.5.1.4.0mobileTodayTxSecSent data — secondary SIM card
.1.3.6.1.4.1.30140.5.1.5.0mobileTodayConnectionsPriNumber of connections — primary SIM card
.1.3.6.1.4.1.30140.5.1.6.0mobileTodayConnectionsSecNumber of connections — secondary SIM card
.1.3.6.1.4.1.30140.5.1.7.0mobileTodayOnlinePriTime online for primary SIM card
.1.3.6.1.4.1.30140.5.1.8.0mobileTodayOnlineSecTime online for secondary SIM card
.1.3.6.1.4.1.30140.5.1.9.0mobileTodayOfflineTime in offline mode
.1.3.6.1.4.1.30140.5.1.10.0mobileTodayCellsNumber of cells during the period
.1.3.6.1.4.1.30140.5.1.11.0mobileTodaySignalAvgAverage signal strength
.1.3.6.1.4.1.30140.5.1.12.0mobileTodaySignalMinMinimum signal strength
.1.3.6.1.4.1.30140.5.1.13.0mobileTodaySignalMaxMaximum signal strength
.1.3.6.1.4.1.30140.5.1.14.0mobileTodayDateMinTimestamp for minimum signal strength
.1.3.6.1.4.1.30140.5.1.15.0mobileTodayDateMaxTimestamp for maximum signal strength
.1.3.6.1.4.1.30140.5.1.101.0mobile2TodayRxPriSecond cellular module: Received data — primary SIM card
.1.3.6.1.4.1.30140.5.1.102.0mobile2TodayRxSecSecond cellular module: Received data — secondary SIM card
.1.3.6.1.4.1.30140.5.1.103.0mobile2TodayTxPriSecond cellular module: Sent data — primary SIM card
.1.3.6.1.4.1.30140.5.1.104.0mobile2TodayTxSecSecond cellular module: Sent data — secondary SIM card
.1.3.6.1.4.1.30140.5.1.105.0mobile2TodayConnectionsPriSecond cellular module: Number of connections — primary SIM card
.1.3.6.1.4.1.30140.5.1.106.0mobile2TodayConnectionsSecSecond cellular module: Number of connections — secondary SIM card
.1.3.6.1.4.1.30140.5.1.107.0mobile2TodayOnlinePriSecond cellular module: Time online — primary SIM card
.1.3.6.1.4.1.30140.5.1.108.0mobile2TodayOnlineSecSecond cellular module: Time online — secondary SIM card
.1.3.6.1.4.1.30140.5.1.109.0mobile2TodayOfflineSecond cellular module: Time in offline mode
.1.3.6.1.4.1.30140.5.1.110.0mobile2TodayCellsSecond cellular module: Number of cells during the period
.1.3.6.1.4.1.30140.5.1.111.0mobile2TodaySignalAvgSecond cellular module: Average signal strength
.1.3.6.1.4.1.30140.5.1.112.0mobile2TodaySignalMinSecond cellular module: Minimum signal strength
.1.3.6.1.4.1.30140.5.1.113.0mobile2TodaySignalMaxSecond cellular module: Maximum signal strength
.1.3.6.1.4.1.30140.5.1.114.0mobile2TodayDateMinSecond cellular module: Timestamp for minimum signal strength
.1.3.6.1.4.1.30140.5.1.115.0mobile2TodayDateMaxSecond cellular module: Timestamp for maximum signal strength

MobileYesterday, MobileThisWeek, MobileLastWeek, MobileThisPeriod, and MobileLastPeriod use the same set of items with different OID base numbers.

Info

This group of OIDs stores the basic information about the router.

OIDNameDescription
.1.3.6.1.4.1.30140.6.1.0infoProductDesignation of the product
.1.3.6.1.4.1.30140.6.2.0infoFirmwareInformation about the firmware
.1.3.6.1.4.1.30140.6.3.0infoSNSerial number of the product
.1.3.6.1.4.1.30140.6.4.0infoIMEIIMEI number of the cellular module
.1.3.6.1.4.1.30140.6.5.0infoESN[obsolete] ESN number of the cellular module
.1.3.6.1.4.1.30140.6.6.0infoMEID[obsolete] MEID number of the cellular module
.1.3.6.1.4.1.30140.6.7.0infoICCIDICCID number of the SIM card used on the first cellular module
.1.3.6.1.4.1.30140.6.8.0infoIMSIIMSI number of the SIM card used on the first cellular module
.1.3.6.1.4.1.30140.6.9.0infoRevisionProduct revision, e.g. 2.0 for a product revision printed on the product as Rev.2.0.
.1.3.6.1.4.1.30140.6.10.0infoProfileCurrent active configuration profile (possible values: standard, alt1, alt2, alt3)
.1.3.6.1.4.1.30140.6.11.0infoCustomA custom field for user-defined purposes
.1.3.6.1.4.1.30140.6.12.0infoPNPart Number of the product
.1.3.6.1.4.1.30140.6.104.0info2IMEIIMEI number of the second cellular module
.1.3.6.1.4.1.30140.6.105.0info2ESNESN number of the second cellular module
.1.3.6.1.4.1.30140.6.106.0info2MEIDMEID number of the second cellular module
.1.3.6.1.4.1.30140.6.107.0info2ICCIDICCID number of the SIM card used on the second cellular module
.1.3.6.1.4.1.30140.6.108.0info2IMSIIMSI number of the SIM card used on the second cellular module

GPS

Warning

To use the GPS part of the SNMP tree, the router must support GPS functionality:

  • Starting with firmware version 6.6.0, GPS functionality is included as a standard feature. It can be configured via Configuration → Services → GNSS and partially through Configuration → Services → SNMP.
  • For firmware versions prior to 6.6.0, the GPS router app must be installed on the router. The app is available for download on our Engineering Portal — see the Router Apps page.

The following range of OIDs is used for sending GPS messages:

OIDNameDescription
.1.3.6.1.4.1.30140.7.1.0gpsTimeUTCCurrent time in hhmmss format (based on Coordinated Universal Time)
.1.3.6.1.4.1.30140.7.2.0gpsLatitudeGeographic coordinate specifying the north–south position (in degrees)
.1.3.6.1.4.1.30140.7.3.0gpsLongitudeGeographic coordinate specifying the east–west position (in degrees)
.1.3.6.1.4.1.30140.7.4.0gpsAltitudeAltitude above sea level (in meters)
.1.3.6.1.4.1.30140.7.5.0gpsSatellitesNumber of satellites visible to the router
.1.3.6.1.4.1.30140.7.6.0gpsFixStatusIndicates data availability and quality; 0 means no data, nonzero indicates valid data
.1.3.6.1.4.1.30140.7.7.0gpsSpeedOverGroundCurrent speed relative to Earth’s surface (in knots)
.1.3.6.1.4.1.30140.7.8.0gpsCourseOverGroundThe current course of movement relative to Earth’s surface (in degrees)
.1.3.6.1.4.1.30140.7.9.0gpsDateCurrent date in ddmmyy format

Usage on Advantech Routers

SNMP Configuration

This example shows basic SNMP configuration of the router. The SNMP Configuration page (see figure below) is accessible via the router’s Web interface under the Configuration section → Services. To enable SNMP, check the Enable SNMP agent box and click the Apply button. Optionally, you can fill in the Name, Location, and Contact information and configure other details.

Example of SNMP Configuration
Example of SNMP Configuration

OIDs in SNMP Trap

It is possible to enable the continuous, regular sending of SNMP traps to a supervisory system. On the SNMP page in the router, select Enable reporting to supervisory system, enter the IP address and time interval, and click Apply. The SNMP traps are sent at the configured interval, with a larger trap (containing more information) sent every 24 hours.

Every SNMP trap contains these OIDs:

  • .1.3.6.1.2.1.2.2.1.6.1 (ifPhysAddress)
  • .1.3.6.1.2.1.2.2.1.10.2 (ifInOctets)
  • .1.3.6.1.2.1.2.2.1.16.2 (ifOutOctets)
  • .1.3.6.1.4.1.30140.4.1.0 (mobileTechnology)
  • .1.3.6.1.4.1.30140.4.2.0 (mobilePLMN)
  • .1.3.6.1.4.1.30140.4.3.0 (mobileCell)
  • .1.3.6.1.4.1.30140.4.4.0 (mobileChannel)
  • .1.3.6.1.4.1.30140.4.5.0 (mobileSignalStrength)
  • .1.3.6.1.4.1.30140.4.6.0 (mobileChannelN1)
  • .1.3.6.1.4.1.30140.4.7.0 (mobileSignalStrengthN1)
  • .1.3.6.1.4.1.30140.4.8.0 (mobileChannelN2)
  • .1.3.6.1.4.1.30140.4.9.0 (mobileSignalStrengthN2)
  • .1.3.6.1.4.1.30140.4.10.0 (mobileChannelN3)
  • .1.3.6.1.4.1.30140.4.11.0 (mobileSignalStrengthN3)
  • .1.3.6.1.4.1.30140.4.12.0 (mobileChannelN4)
  • .1.3.6.1.4.1.30140.4.13.0 (mobileSignalStrengthN4)
  • .1.3.6.1.4.1.30140.4.14.0 (mobileChannelN5)
  • .1.3.6.1.4.1.30140.4.15.0 (mobileSignalStrengthN5)
  • .1.3.6.1.4.1.30140.4.16.0 (mobileUpTime)
  • .1.3.6.1.4.1.30140.4.17.0 (mobileConnect)
  • .1.3.6.1.4.1.30140.4.18.0 (mobileDisconnect)
  • .1.3.6.1.4.1.30140.4.19.0 (mobileCard)
  • .1.3.6.1.4.1.30140.4.21.0 (mobileLatency)
  • .1.3.6.1.4.1.30140.4.22.0 (mobileReportPeriod)
  • .1.3.6.1.4.1.30140.4.26.0 (mobileSignalQuality)
  • .1.3.6.1.4.1.30140.4.27.0 (mobileCSQ)
  • .1.3.6.1.4.1.30140.5.1.10.0 (mobileTodayCells)
  • .1.3.6.1.4.1.30140.3.3.0 (statusTemperature)
  • .1.3.6.1.4.1.30140.3.4.0 (statusVoltage)

The larger SNMP trap sent every 24 hours also contains these OIDs:

  • .1.3.6.1.4.1.30140.6.3.0 (infoSN)
  • .1.3.6.1.4.1.30140.6.4.0 (infoIMEI)
  • .1.3.6.1.4.1.30140.6.5.0 (infoESN)
  • .1.3.6.1.4.1.30140.6.6.0 (infoMEID)
  • .1.3.6.1.2.1.1.1.0 (sysDescr)
  • .1.3.6.1.2.1.1.5.0 (sysName)
  • .1.3.6.1.2.1.1.6.0 (sysLocation)

SNMP Capturing

You can access the router's SNMP tree using any SNMP MIB browser (for example, MG-SOFT or SnmpB shown on the figure below). Simply set the router's IP address in the browser, load the MIB files from the repository, and explore the SNMP OIDs and their corresponding values.

Example of MIB Browser
Example of MIB Browser

The path to private (Advantech routers) objects is:

iso → org → dod → internet → private → enterprises → conel

The path to basic information about the router is:

iso → org → dod → internet → mgmt → mib-2 → system