Network Cabinet Monitoring & Control

Do More Than Monitor Network Cabinets — Protect Them Automatically

Temperature increases and Internet failures in network cabinets, server rooms, security infrastructure and remote communication sites can directly affect critical services. NetRelay can combine environmental monitoring and network availability checks so physical and software actions can be triggered automatically when problems occur.

Continuously Monitor Cabinet Temperature

A suitable temperature sensor can monitor the environment inside the cabinet. When temperature exceeds the configured threshold, NetRelay can automatically activate a fan or ventilation system through a relay output.

For example, a fan can start above 30°C and stop once temperature returns to a safe level.

Stable Temperature Control with Hysteresis

Separate ON and OFF thresholds can prevent frequent relay switching. For example, activate cooling above 30°C and stop cooling below 26°C.

Multi-Level Temperature Alarms

• 30°C: Automatically start cabinet cooling.
• 35°C: Generate a high-temperature warning.
• 40°C: Activate the critical alarm relay and notify responsible personnel.

Automatically Monitor Internet Connectivity

Network monitoring and Ping Watchdog functions can regularly verify Internet connectivity and the availability of critical IP devices such as gateways, modems, routers, access points, NVR systems and servers.

Trigger an Alarm Relay When Internet Connectivity Fails

When connectivity remains unavailable for the configured period, a NetRelay output can operate as a physical alarm relay.

The output can trigger a warning beacon, siren, external alarm panel, GSM device or another system using a dry-contact input.

Example Internet Failure Workflow

Condition: Multiple consecutive connectivity checks fail.

Action 1: Create an Internet outage event.

Action 2: Activate the alarm relay.

Action 3: Send a notification to the central system.

Action 4: Record the outage start time.

When connectivity returns: Deactivate the alarm relay, record recovery time and send a recovery notification.

Avoid False Alarms from Temporary Packet Loss

A single failed ping should not necessarily be treated as an Internet outage. Multiple failed checks can be required before declaring a fault, helping prevent unnecessary alarms caused by short packet-loss events.

Use Multiple Targets

Monitoring several local and external IP targets can help distinguish Internet service failures from gateway or individual-device failures.

Send Notifications

Temperature and network events can be forwarded through MQTT, HTTP or central management software to e-mail, SMS, mobile notification or alarm platforms.

Use an Independent Notification Channel During Internet Failure

When the primary Internet connection is completely unavailable, cloud-based notification services using the same connection may also be unreachable. Critical installations can use independent GSM/LTE modems, SMS gateways or secondary WAN connectivity.

A NetRelay alarm output can also trigger the dry-contact input of an external GSM alarm device, allowing SMS notifications to be sent independently from the failed Internet connection.

Attempt Automatic Recovery Before Escalation

NetRelay can also perform corrective actions. If connectivity remains unavailable, a separate relay can power-cycle a modem or router. After the configured recovery period, connectivity can be checked again.

Escalate Only When Automatic Recovery Fails

If connectivity returns after an automatic restart, the incident can be recorded as automatically resolved. If the failure remains, the event can be escalated to technical personnel.

Monitor Cabinet Door Access

Magnetic contacts connected to digital inputs can record network cabinet door openings and forward these events to the central system.

Monitor UPS and Power Status

Suitable dry-contact outputs from UPS systems and power equipment can be connected to NetRelay digital inputs to monitor mains failure, UPS operation and general alarm conditions.

A Real Network Cabinet Scenario

Consider a remote network cabinet with a temperature sensor, door contact and UPS alarm connected to NetRelay. The Internet gateway and main router are also monitored through Ping Watchdog.

When cabinet temperature exceeds 30°C, RELAY1 starts the fan. When temperature falls below 26°C, cooling stops automatically.

If Internet connectivity fails for the configured number of checks, RELAY2 activates the alarm output and the central system receives an outage event. Optionally, RELAY3 can restart the modem or router.

When connectivity returns, the alarm output is cleared and total outage duration is recorded. Door openings and UPS alarms are stored as separate events.

Generate Historical Reports

• Cabinet temperature history
• Minimum, maximum and average temperatures
• Critical temperature events
• Cooling fan activation count
• Total fan runtime
• Internet outage start and recovery times
• Total daily and monthly downtime
• Network uptime and downtime reports
• Automatic modem/router restart history
• Alarm relay activity
• Notification history
• UPS alarm history
• Cabinet door access history

Identify Recurring Problems

Historical data can reveal cabinets that repeatedly overheat, Internet connections that frequently fail or locations experiencing recurring UPS alarms, helping teams address underlying infrastructure issues.

Combine Network and Environmental Monitoring

Multiple NetRelay devices can send temperature, connectivity, alarm and relay data through MQTT or HTTP to a central dashboard.

Start cooling when temperature rises, trigger an alarm relay when Internet connectivity fails, notify the responsible team and record every event for historical analysis. Turn network cabinets into intelligent field points that automatically respond to problems with NetRelay.