Skip to main content
Network

TP-Link Switch

Monitor JetStream and Omada switch CPU, memory, PoE budget, and required uplinks over SNMP.

The TP-Link Switch check monitors JetStream/Omada switches over SNMP: one-minute CPU utilization, memory utilization, PoE budget consumption and power, PoE faults, and selected uplinks. It runs every 5 minutes by default on an octoja agent with Windows, Linux, or macOS, on x64 or ARM64.

Prerequisites

  • An online octoja agent that can reach the switch's management address on UDP 161, or your configured SNMP port.
  • SNMP enabled on the switch, with read-only v1, v2c or v3 credentials and access allowed from the executing agent. Use a version supported by the device firmware; do not point the check at the Omada controller.
  • Firmware that exposes the relevant TP-Link MIBs. An SNMP response alone does not establish that CPU, memory, or PoE values are available. See TP-Link's MIB downloads.

The check reads values; it does not configure the switch. Prefer authenticated, encrypted SNMPv3 where supported. A v1/v2c community travels unencrypted; replace the public default on the device and in octoja.

Steps

  1. Open the executing device under Devices, then Checks → Add Check, and select TP-Link Switch. See Activate your first check for the assignment workflow.
  2. Enter the switch's management hostname or IP under Host / IP, and matching SNMP credentials.
  3. Set thresholds and, optionally, Required links. Enter exact ifDescr names or ifIndex values obtained from the device's IF-MIB; these are not fixed port numbers shared by all models.
  4. Click Add Check. After a run, confirm that the expected metrics appear and inspect any unavailable-metric warning.

You can instead register the switch as an agentless network device with a monitoring asset. Add the check to that switch's Checks tab. Its own IP address is used automatically; when SNMP is configured on the network device, its connection settings override the check-level SNMP fields. Thresholds and required links remain check settings.

Settings

FieldTypeRequiredDefaultDescription
Host / IPStringYes—The switch's management address, without https://.
SNMP versionSelectNov2cv1, v2c or v3; match the firmware's enabled version. Choose v1 only if the device does not offer v2c.
SNMP portIntegerNo161UDP port, from 1 to 65535.
Community (v1/v2c)StringNopublicRead community; visible for v1 and v2c.
Username (v3)StringFor v3—SNMPv3 user.
Authentication protocolSelectNoSHA-1None, SHA-1, or SHA-256; visible for v3.
Authentication passwordPasswordWith authentication—Required unless authentication is None.
Privacy protocolSelectNoAES-128None, AES-128, AES-192, or AES-256; visible with authentication.
Privacy passwordPasswordWith encryption—Required unless privacy is None.
Required linksList of stringsNoEmptyExact IF-MIB ifDescr names, case-sensitive, or ifIndex values. Unselected ports do not alarm.
CPU warning (%) / CPU critical (%)IntegerNo85 / 95CPU utilization; each value must be 1–100.
Memory warning (%) / Memory critical (%)IntegerNo85 / 95Memory utilization; each value must be 1–100.
PoE budget warning (%) / PoE budget critical (%)IntegerNo85 / 95Used PoE budget as a percentage of its limit; each value must be 1–100.

Reaching a threshold is enough to trigger its status. If warning exceeds critical, the check orders the pair from lower to higher. Selecting None for authentication hides the privacy fields and disables encryption. MD5 and DES are not offered.

Results

The highest severity determines the overall result. CPU and memory are reported per discovered unit, not assumed to have index 1. PoE supports the TP-Link L2 scalar and L3 unit-table layouts; power is shown in watts. SNMP uptime is shown in days and is not an Internet-connectivity test.

ResultMeaning and next action
OKReturned metrics are below thresholds and selected links are up. Verify that your expected metrics are present.
WarningA warning threshold was reached, or an expected CPU/memory reading is missing or invalid. Check firmware/MIB support rather than treating missing values as zero. Partial or invalid returned PoE readings also warn.
CriticalA critical threshold was reached, a required link is missing/down, a PoE fault is reported, or SNMP did not respond. Inspect the affected unit/port; for no response, check UDP access, community, and device access rules.
ErrorConfiguration, SNMP authentication/access, or protocol processing failed. Read the error, then check credentials, enabled protocols, and valid input values.

PoE overload, short circuit, nonstandard powered device, high/low voltage, hardware fault, and overtemperature are Critical. A PoE port being off, starting, or on is not itself a fault. A missing status for a selected link warns rather than pretending the link is up.

FAQ

PoE is optional. If the device exposes no supported PoE data, the check omits it without an alarm. This can mean a non-PoE switch or unavailable PoE MIB support; it does not prove that a PoE-capable switch's power system is healthy.

No. It does not poll chassis temperature or fans. A reported PoE overtemperature fault is a PoE state, not a chassis temperature measurement. Required links test interface state only; use a separate reachability or service check for Internet access.