Sysuptime

Author: t | 2025-04-24

I get the = same result: SNIP $ snmptranslate -Le sysUpTime sysUpTime: Unknown Object Identifier (Sub-id not found: (top) - = sysUpTime) $ snmptranslate -Le SNMPv2-MIB::sysUpTime SNMPv2-MIB::sysUpTime $=20 /SNIP HTH, Mike SysUpTime. Download SysUpTime for Windows to administer your network with advanced management features. SysUpTime has had 3 updates within the past 6 months.

sysuptime in snmp - Stack Overflow

Status changed. For example, if the interface's operating status changed 60 seconds after the device was rebooted, the ifLastChange value will be 600 (hundredths of seconds) until the operating status changes again.-SysUptime(1.3.6.1.2.1.1.3): This value represents the amount of time in hundredths of seconds that the system has been up.In order to calculate the Last Change value for the interface, ifLastChange is deducted from SysUptime. This gives us the amount of hundredths of a second since the change. We then compare that to the current date and time and we end up with the specific date and time of the change.The limitation of this calculation is that SysUptime rolls over at 4,294,967,296 hundredths of a second. When this occurs, deducting ifLastChange from SysUptime results in a negative number, which then ends up as a futuristic date.The only way around this is to reboot the device, which will reset all counters to 0.Also good link on this here: Thanks, Kev Also I suggest checking those OIDs above using Toolset MIB WALK\MIB Viewer, or even use NPM's UnDP Custom Poller.You can check values and Formula is: SysUpTime - IfLastChange = X Then DateTimeFunction(X) = Interface Last ChangeThe assumption is that IfLastChange should always be a smaller value than SysUpTime since surely an interface could not be up longer than the box it is on… But say for example if the SysUpTime value experiences a rollover we now have the scenario where SysUpTime is smaller than the value of IfLastChange. Our equation will now SNMP sysUpTime（OID 1.3.6.1.2.1.1.3.0） 时间戳信息解析遇到的问题 提示：sysUpTime： SNMP OID 1.3.6.1.2.1.1.3.0 计算出来的启动时间，与设备显示的不一致 SNMP V2C Trap 时间戳详细解析 最近计划通过SNMP Trap 获取设备的事件信息，发现Trap时候，设备会发生 OID = 1.3.6.1.2.1.1.3.0 的字段信息。 查资料，发现该OID表示MIB中的sysUpTime。 网络上查询该OID的定义解析： RFC1213 defines sysUpTime as a 32-bit counter in 1/100 second. From the RFC’s definition of sysUpTime: “The time (in hundredths of a second) since the network management portion of the system was last re-initialized.” 即是：该字段的值是32-bit 的计数器， 每1个单位，表示1秒的百分之一，即是0.01秒。 该计数器的值，是从设备启动后开始计数。 但是通过Trap收到的华为S9xxx设备发来的 sysUpTime ，与设备时间开机时间无法对上。 抓取到的 OID = 1.3.6.1.2.1.1.3.0 ， timeticks-value=4294967296 而通过display version, 显示设备启动时间： Quidway S9xxx Terabit Routing Switch uptime is 123 weeks, 5 days, 15 hours, 51 minutes 按照OID = 1.3.6.1.2.1.1.3.0的定义，4294967296应该是71 weeks 4294967296/100/(2436007) = 71.0146708994709 OID = 1.3.6.1.2.1.1.3.0 计算出来的启动时间，与设备显示的不一致。 这个问题困扰了很久。。。 OID = 1.3.6.1.2.1.1.3.0 计算出来的启动时间，与设备显示的不一致 提示：现网设备实际数据： 抓取到的 OID = 1.3.6.1.2.1.1.3.0 ， timeticks-value=4294967296 而通过display version, 显示设备启动时间： Quidway S9xxx Terabit Routing Switch uptime is 123 weeks, 5 days, 15 hours, 51 minutes 按照OID = 1.3.6.1.2.1.1.3.0的定义，4294967296应该是71 weeks 4294967296/100/(2436007) = 71.0146708994709 >>> 4294967296/100/(24*3600*7)71.0146708994709>>> 原因分析： 提示：SysUpTime MIB supports 32-bit (Timeticks)： SysUpTime MIB supports 32-bit = 2 to the 32nd power = 2^32 = 4294967296 (Timeticks) 32位的整数，最大表示是 2^32 = 4294967296 4294967296 最多表示 是 497天多一点，如果超过这个数值，计数器又从0开始计数。 >>> 2**32/100/(24*3600)497.1026962962963>>> All PacketWise images and models will have the same behavior after the sysUpTime value reaches 497 days, the sysUpTime polled value resets to zero (0). 解决方案： 提示：需要自己加上 n * 2**32 去计算 SysUpTime 如果一个设备启动时间特别长的话，设备通过Trap 发到接收器的 timeticks （OID = 1.3.6.1.2.1.1.3.0），需要加上 n * 2**32，再去计算设备的开机时间，从而再去计算trap信息的实际时间。 后记： 后面发现这个Trap接收到时间，实际也没什么意义了 因为Trap 收到的信息，是设备事件的信息，基本都是实时收到，在接收trap的程序上，记录接收的Trap消息的时间即可，无需通过这个 OID = 1.3.6.1.2.1.1.3.0 去计算了。。。

SysUpTime 5.3 Free Download

MIB overviewThis document provides information aboutthe management information bases (MIBs) available for the device, includingpublic and private MIBs. About MIBsMIB modules and MIBfilesA MIB is a collection of informationorganized hierarchically in a tree structure. Each node in a MIB is a managedobject uniquely identified by an object identifier (OID). An OID is a dottednumeric string that uniquely identifies the path from the root node to a leafnode. Collections of related objects are definedin MIB modules. Typically, each MIB module has a MIB file. You can run a MIBcompiler to compile the MIB files of the managed device into a visualized MIBtree for the ease of management, as shown in Figure 1.Figure 1 MIB treeafter compilationTypes of MIB objectsMIB objects are classified into scalarobjects, tabular objects, and notification objects. The SNMP manager can accessonly the instances of MIB objects.Scalar objectsScalar objects are single-instance objects.An example of a scalar object is sysUpTime, which contains only one objectinstance to store the time since the network management portion of the systemwas last initialized. The instance of a scalar object is identified by an indexvalue of 0. When the SNMP manager accesses the instance of a scalar object, theSNMP manager must add a suffix of .0 to the object identifier or object name,as shown below:Protocol version:SNMPv2cOperation:GetRequest binding:# Request sent by theSNMP manager1:sysUpTime.0 (TimeTicks) nullResponse binding:# Response sent bythe SNMP agent (the device)1:sysUpTime.0 (TimeTicks) 29 days15h:25m:15s.64th (256111564)Tabular objectsTabular objects define multiple relatedobjects in conceptual tables. You can think of a tabular object as a table inwhich. I get the = same result: SNIP $ snmptranslate -Le sysUpTime sysUpTime: Unknown Object Identifier (Sub-id not found: (top) - = sysUpTime) $ snmptranslate -Le SNMPv2-MIB::sysUpTime SNMPv2-MIB::sysUpTime $=20 /SNIP HTH, Mike

SysUpTime User Manual - Archive.org

Result in a negative value which when converted to a date/time format will give us an erroneous value in the future.So depending on SysUpTime and\or IfLastChange values having counter roller,Then you could experience such issues.Kev Hi Bryan, I am having this problem too, did you ever manage to implement a workaround or find a solution? This seems to me to be a poorly developed OID? Should ifLastChange not always get it's time reference straight from SysUpTime?! Can I ask also how did you manage to display the data on the node details page? That is to say how did you display the results of ifLastChange on node details page. I tried to add a resource to the page for a universal device poller, the only suitable one I could find was universal device poller summary chart but a chart is not the way to display such data. Any help greatly appreciated. Thanks!BryanBecker .1.3.6.1.2.1.1.3.0 snmpget snmpget retrieves data from an SNMP host. It makes a simple request that consists of three elements: where to retrieve information the administrative information associated with the request what information is required:# snmpget -v 2c -c demopublic test.net-snmp.org SNMPv2-MIB::sysUpTime.0 SNMPv2-MIB::sysUpTime.0 = Timeticks: (586731977) 67 days, 21:48:39.77 snmpgetnext The other main operation of the SNMP protocol for retrieving information is GETNEXT, implemented by the snmpgetnext tool. It retrieves similar types of information as snmpget, but from the next OID. It is useful to walk through a series of SNMP hosts and progressively get information from each device. Its syntax is identical to snmpget:# snmpgetnext -v 2c -c demopublic test.net-snmp.org sysUpTimeSNMPv2-MIB::sysUpTime.0 = Timeticks: (586978184) 67 days, 22:29:41.84 snmpwalk As a helper to walk a network, instead of launching snmpgetnext for each SNMP host, snmpwalk can be used to do it automatically: snmptable snmptable returns the content of an SNMP table, displaying it one row at a time: snmpset The SET operation of the SNMP protocol is used to modify information of an SNMP host, update its configuration, or control its behavior. It is implemented in the snmpset tool.One of many possible examples is how to set a random string to be returned when queried:$ snmpset -v 1 -c demopublic test.net-snmp.org ucdDemoPublicString.0 s "hi there!"$ snmpget -v 1 -c demopublic test.net-snmp.org ucdDemoPublicString.0UCD-DEMO-MIB::ucdDemoPublicString.0 = "hi there!" snmpbulkget The GETBULK operation available from SNMP v2 onward is implemented in the snmpbulkget tool. It is used to query a network of SNMP hosts rather than a single one.$ snmpbulkget -v2c -Cn1 -Cr5 -Os -c public zeus system ifTableIt will retrieve the variable system.sysDescr.0 and the first 5 objects of the ifTable.To retrieve multiple variables with a single command, snmpbulkwalk is a tool that allows you to run all the variables under a system:$ snmpbulkwalk

Re: sysUpTime returns an error

TP-Link Technologies Co., Ltd., is a Chinese manufacturer of computer networking products based. Available solutions TP-LINK SNMP 3rd party solutions This template is for Zabbix version: 7.2 Source: TP-LINK by SNMPOverviewLink to MIBs: device overview page: page (web): issuesDescription: 'Default sysLocation, sysName and sysContact is not filled with proper data. Real hostname and location can be found only in private branch (TPLINK-SYSINFO-MIB). Please check whether this problem exists in the latest firmware: 2.0.0 Build 20170628 Rel.55184 (Beta)device: T2600G-28TS 2.0Description: The Serial number of the product (tpSysInfoSerialNum) is missing in HW versions prior to V2_170323version: Prior to version V2_170323device: T2600G-28TS 2.0RequirementsZabbix version: 7.2 and higher.Tested versionsThis template has been tested on:T2600G-28TS revision 2.0 2.0.0 Build 20170628 Rel.55184 (Beta)ConfigurationZabbix should be configured according to the instructions in the Templates out of the box section.SetupRefer to the vendor documentation.Macros usedNameDescriptionDefault{$MEMORY.UTIL.MAX}90{$CPU.UTIL.CRIT}90{$SNMP.TIMEOUT}Time interval for the SNMP availability trigger.5m{$ICMP_LOSS_WARN}Warning threshold of ICMP packet loss in %.20{$ICMP_RESPONSE_TIME_WARN}Warning threshold of the average ICMP response time in seconds.0.15{$IFCONTROL}1{$IF.UTIL.MAX}95{$NET.IF.IFNAME.MATCHES}^.*${$NET.IF.IFNAME.NOT_MATCHES}Filter out loopbacks, nulls, docker veth links and docker0 bridge by defaultMacro too long. Please see the template.{$NET.IF.IFOPERSTATUS.MATCHES}^.*${$NET.IF.IFOPERSTATUS.NOT_MATCHES}Ignore notPresent(6)^6${$NET.IF.IFADMINSTATUS.MATCHES}^.*{$NET.IF.IFADMINSTATUS.NOT_MATCHES}Ignore down(2) administrative status^2${$NET.IF.IFDESCR.MATCHES}.*{$NET.IF.IFDESCR.NOT_MATCHES}CHANGE_IF_NEEDED{$NET.IF.IFTYPE.MATCHES}.*{$NET.IF.IFTYPE.NOT_MATCHES}CHANGE_IF_NEEDED{$NET.IF.IFALIAS.MATCHES}.*{$NET.IF.IFALIAS.NOT_MATCHES}CHANGE_IF_NEEDED{$IF.ERRORS.WARN}Warning threshold of error packet rate. Can be used with interface name as context.2ItemsNameDescriptionTypeKey and additional infoHardware model nameMIB: TPLINK-SYSINFO-MIBThe hardware version of the product.SNMP agentsystem.hw.modelPreprocessingDiscard unchanged with heartbeat: 1dHardware serial numberMIB: TPLINK-SYSINFO-MIBThe Serial number of the product.SNMP agentsystem.hw.serialnumberPreprocessingDiscard unchanged with heartbeat: 1dFirmware versionMIB: TPLINK-SYSINFO-MIBThe software version of the product.SNMP agentsystem.hw.firmwarePreprocessingDiscard unchanged with heartbeat: 1dHardware version(revision)MIB: TPLINK-SYSINFO-MIBThe hardware version of the product.SNMP agentsystem.hw.versionPreprocessingDiscard unchanged with heartbeat: 1dSNMP walk system CPUsDiscovering TPLINK-SYSMONITOR-MIB::tpSysMonitorCpuTable, displays the CPU utilization of all UNITs.SNMP agentsystem.cpu.walkSNMP walk memoryDiscovering TPLINK-SYSMONITOR-MIB::tpSysMonitorMemoryTable, displays the memory utilization of all UNITs.SNMP agentvm.memory.walkUptime (network)MIB: SNMPv2-MIBTime (in hundredths of a second) since the network management portion of the system was last re-initialized.SNMP agentsystem.net.uptime[sysUpTime.0]PreprocessingCustom multiplier: 0.01Uptime (hardware)MIB: HOST-RESOURCES-MIBThe amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.SNMP agentsystem.hw.uptime[hrSystemUptime.0]PreprocessingCheck for not supported value: any error⛔️Custom on fail: Set value to: 0Custom multiplier: 0.01SNMP traps (fallback)The item is used to collect all SNMP traps unmatched by other snmptrap itemsSNMP trapsnmptrap.fallbackSystem locationMIB: SNMPv2-MIBPhysical location of the node (e.g., equipment room, 3rd floor). If not provided, the value is a zero-length string.SNMP agentsystem.location[sysLocation.0]PreprocessingDiscard unchanged with heartbeat: 12hSystem contact detailsMIB: SNMPv2-MIBThe textual identification of the contact person for this managed node, together with information on how to

Download network monitoring software - SysUpTime

Seconds.0.15{$IFCONTROL}1{$IF.UTIL.MAX}95{$NET.IF.IFNAME.MATCHES}^.*${$NET.IF.IFNAME.NOT_MATCHES}Filter out loopbacks, nulls, docker veth links and docker0 bridge by defaultMacro too long. Please see the template.{$NET.IF.IFOPERSTATUS.MATCHES}^.*${$NET.IF.IFOPERSTATUS.NOT_MATCHES}Ignore notPresent(6)^6${$NET.IF.IFADMINSTATUS.MATCHES}^.*{$NET.IF.IFADMINSTATUS.NOT_MATCHES}Ignore down(2) administrative status^2${$NET.IF.IFDESCR.MATCHES}.*{$NET.IF.IFDESCR.NOT_MATCHES}CHANGE_IF_NEEDED{$NET.IF.IFTYPE.MATCHES}.*{$NET.IF.IFTYPE.NOT_MATCHES}CHANGE_IF_NEEDED{$NET.IF.IFALIAS.MATCHES}.*{$NET.IF.IFALIAS.NOT_MATCHES}CHANGE_IF_NEEDED{$IF.ERRORS.WARN}Warning threshold of error packet rate. Can be used with interface name as context.2ItemsNameDescriptionTypeKey and additional infoHardware model nameMIB: TPLINK-SYSINFO-MIBThe hardware version of the product.SNMP agentsystem.hw.modelPreprocessingDiscard unchanged with heartbeat: 1dHardware serial numberMIB: TPLINK-SYSINFO-MIBThe Serial number of the product.SNMP agentsystem.hw.serialnumberPreprocessingDiscard unchanged with heartbeat: 1dFirmware versionMIB: TPLINK-SYSINFO-MIBThe software version of the product.SNMP agentsystem.hw.firmwarePreprocessingDiscard unchanged with heartbeat: 1dHardware version(revision)MIB: TPLINK-SYSINFO-MIBThe hardware version of the product.SNMP agentsystem.hw.versionPreprocessingDiscard unchanged with heartbeat: 1dSNMP walk system CPUsDiscovering TPLINK-SYSMONITOR-MIB::tpSysMonitorCpuTable, displays the CPU utilization of all UNITs.SNMP agentsystem.cpu.walkSNMP walk memoryDiscovering TPLINK-SYSMONITOR-MIB::tpSysMonitorMemoryTable, displays the memory utilization of all UNITs.SNMP agentvm.memory.walkUptime (network)MIB: SNMPv2-MIBTime (in hundredths of a second) since the network management portion of the system was last re-initialized.SNMP agentsystem.net.uptime[sysUpTime.0]PreprocessingCustom multiplier: 0.01Uptime (hardware)MIB: HOST-RESOURCES-MIBThe amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.SNMP agentsystem.hw.uptime[hrSystemUptime.0]PreprocessingCheck for not supported value: any error⛔️Custom on fail: Set value to: 0Custom multiplier: 0.01SNMP traps (fallback)The item is used to collect all SNMP traps unmatched by other snmptrap itemsSNMP trapsnmptrap.fallbackSystem locationMIB: SNMPv2-MIBPhysical location of the node (e.g., equipment room, 3rd floor). If not provided, the value is a zero-length string.SNMP agentsystem.location[sysLocation.0]PreprocessingDiscard unchanged with heartbeat: 12hSystem contact detailsMIB: SNMPv2-MIBThe textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.SNMP agentsystem.contact[sysContact.0]PreprocessingDiscard unchanged with heartbeat: 12hSystem object IDMIB: SNMPv2-MIBThe 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 determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.SNMP agentsystem.objectid[sysObjectID.0]PreprocessingDiscard unchanged with heartbeat: 12hSystem nameMIB: SNMPv2-MIBAn administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.SNMP agentsystem.namePreprocessingDiscard unchanged with heartbeat: 12hSystem descriptionMIB: SNMPv2-MIBA textual description of the entity. This value shouldinclude the full name and version identification of the system's hardware type, software operating-system, andnetworking software.SNMP agentsystem.descr[sysDescr.0]PreprocessingDiscard unchanged with heartbeat: 12hSNMP agent availabilityAvailability of SNMP checks on the host. The value of this. I get the = same result: SNIP $ snmptranslate -Le sysUpTime sysUpTime: Unknown Object Identifier (Sub-id not found: (top) - = sysUpTime) $ snmptranslate -Le SNMPv2-MIB::sysUpTime SNMPv2-MIB::sysUpTime $=20 /SNIP HTH, Mike SysUpTime. Download SysUpTime for Windows to administer your network with advanced management features. SysUpTime has had 3 updates within the past 6 months.

sysUpTime - sys Up Time - rfc1213

Vendor documentation.Macros usedNameDescriptionDefault{$MEMORY.UTIL.MAX}90{$CPU.UTIL.CRIT}90{$SNMP.TIMEOUT}5m{$ICMP_LOSS_WARN}20{$ICMP_RESPONSE_TIME_WARN}0.15{$IFCONTROL}1{$IF.UTIL.MAX}95{$NET.IF.IFNAME.MATCHES}^.*${$NET.IF.IFNAME.NOT_MATCHES}Filter out loopbacks, nulls, docker veth links and docker0 bridge by defaultMacro too long. Please see the template.{$NET.IF.IFOPERSTATUS.MATCHES}^.*${$NET.IF.IFOPERSTATUS.NOT_MATCHES}Ignore notPresent(6)^6${$NET.IF.IFADMINSTATUS.MATCHES}^.*{$NET.IF.IFADMINSTATUS.NOT_MATCHES}Ignore down(2) administrative status^2${$NET.IF.IFDESCR.MATCHES}.*{$NET.IF.IFDESCR.NOT_MATCHES}CHANGE_IF_NEEDED{$NET.IF.IFTYPE.MATCHES}.*{$NET.IF.IFTYPE.NOT_MATCHES}CHANGE_IF_NEEDED{$NET.IF.IFALIAS.MATCHES}.*{$NET.IF.IFALIAS.NOT_MATCHES}CHANGE_IF_NEEDED{$IF.ERRORS.WARN}2ItemsNameDescriptionTypeKey and additional infoTP-LINK: Hardware model nameMIB: TPLINK-SYSINFO-MIBThe hardware version of the product.SNMP agentsystem.hw.modelPreprocessingDiscard unchanged with heartbeat: 1dTP-LINK: Hardware serial numberMIB: TPLINK-SYSINFO-MIBThe Serial number of the product.SNMP agentsystem.hw.serialnumberPreprocessingDiscard unchanged with heartbeat: 1dTP-LINK: Firmware versionMIB: TPLINK-SYSINFO-MIBThe software version of the product.SNMP agentsystem.hw.firmwarePreprocessingDiscard unchanged with heartbeat: 1dTP-LINK: Hardware version(revision)MIB: TPLINK-SYSINFO-MIBThe hardware version of the product.SNMP agentsystem.hw.versionPreprocessingDiscard unchanged with heartbeat: 1dTP-LINK: Uptime (network)MIB: SNMPv2-MIBThe time (in hundredths of a second) since the network management portion of the system was last re-initialized.SNMP agentsystem.net.uptime[sysUpTime.0]PreprocessingCustom multiplier: 0.01TP-LINK: Uptime (hardware)MIB: HOST-RESOURCES-MIBThe amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.SNMP agentsystem.hw.uptime[hrSystemUptime.0]PreprocessingCheck for not supported value⛔️Custom on fail: Set value to: 0Custom multiplier: 0.01TP-LINK: SNMP traps (fallback)The item is used to collect all SNMP traps unmatched by other snmptrap itemsSNMP trapsnmptrap.fallbackTP-LINK: System locationMIB: SNMPv2-MIBThe physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.SNMP agentsystem.location[sysLocation.0]PreprocessingDiscard unchanged with heartbeat: 12hTP-LINK: System contact detailsMIB: SNMPv2-MIBThe textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.SNMP agentsystem.contact[sysContact.0]PreprocessingDiscard unchanged with heartbeat: 12hTP-LINK: System object IDMIB: SNMPv2-MIBThe 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 determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.SNMP agentsystem.objectid[sysObjectID.0]PreprocessingDiscard unchanged with heartbeat: 12hTP-LINK: System nameMIB: SNMPv2-MIBAn administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.SNMP agentsystem.namePreprocessingDiscard unchanged with heartbeat: 12hTP-LINK: System descriptionMIB: SNMPv2-MIBA textual description of the entity. This value shouldinclude the full name and version identification of the system's hardware type, software operating-system, andnetworking software.SNMP agentsystem.descr[sysDescr.0]PreprocessingDiscard unchanged with heartbeat: 12hTP-LINK: SNMP agent availabilityAvailability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.Possible value:0 - not available1 - available2 - unknownZabbix internalzabbix[host,snmp,available]TP-LINK: ICMP