TP-Link Gateway
Monitor Omada gateway SNMP availability and selected WAN/LAN links, and understand the limits of interface-state monitoring.
The TP-Link Gateway check monitors an Omada gateway's SNMP availability and selected WAN/LAN interface states using IF-MIB. It runs every 5 minutes by default on an octoja agent with Windows, Linux, or macOS, on x64 or ARM64. It does not monitor proprietary CPU/RAM values, routing, VPNs, or Internet reachability.
An up link is not proof of Internet access. A WAN interface can be up while upstream connectivity, DNS, or a service is unavailable. Add a separate Ping or SSL / HTTP check for the destination or service you need to verify.
Prerequisites
- An online octoja agent that can reach the gateway's management address on UDP 161, or your configured SNMP port.
- SNMP enabled on the gateway, read-only v1, v2c or v3 credentials, and access allowed from the executing agent. Match the version supported by the firmware; query the gateway, not the Omada controller.
- The exact IF-MIB
ifDescrname orifIndexvalue for each WAN/LAN link you require. Use an SNMP table walk ofifDescr(1.3.6.1.2.1.2.2.1.2) to discover these from the executing device. Do not assume that a particular index always means WAN1: interfaces depend on firmware and configured WAN VLANs. See TP-Link's gateway SNMP guidance.
Prefer authenticated, encrypted SNMPv3 where supported. A v1/v2c community travels unencrypted; replace the public default on the device and in octoja.
Steps
- Open the executing device under Devices, then Checks → Add Check, and select TP-Link Gateway. See Activate your first check for the assignment workflow.
- Enter the gateway's management address under Host / IP and matching SNMP credentials.
- Enter the discovered names or indices under Required links. Select at least one link; an empty selection produces Warning because no link health is configured.
- Click Add Check. After a run, confirm that each selected link has the expected name and state. Recheck your selections after firmware, port-role, or WAN VLAN changes.
You can instead register the gateway as an agentless network device with a monitoring asset. Add the check to the gateway's Checks tab. Its own IP address is used automatically; when SNMP is configured on the network device, its connection settings override check-level SNMP fields. Required links remain a check setting.
Settings
Selecting None for authentication disables encryption and hides privacy fields. MD5 and DES are not offered. Interface names are entered directly; do not expect a discovered-port picker populated by a previous check run.
Results
The highest severity determines the overall result. SNMP uptime is displayed in days. For selected links, only ifOperStatus = 1 means Up; other returned states are not accepted as healthy.
FAQ
Do unused ports or a standby WAN cause alarms?
Do unused ports or a standby WAN cause alarms?
Only links you select are evaluated. Leave unused ports unselected. Select a standby WAN only if its interface must remain up for your design; the check does not evaluate failover policy or distinguish an intentionally down link from a failed one.
Was this helpful?
More in Network
3CX Phone SystemBandwidthDNS ResolutionDNS Blacklist (RBL)Still need help? Ask the team