Fujitsu ServerView Health (SNMP)

The Fujitsu ServerView Health (SNMP) check monitors the hardware health of Fujitsu PRIMERGY servers over SNMP — overall system status, CPU and mainboard, temperatures, fans, power supplies, memory, and RAID. It gives you early warning when a component starts to fail. The check runs on an agent device on Windows, Linux, or macOS (each in x64 and Arm64 builds) and queries the server over the network, every 15 minutes by default.

Prerequisites

• You need the Monitoring Check Management permission. Permissions are assigned under Administration → Groups.
• An octoja agent on a device with network access to the Fujitsu server.
• Fujitsu ServerView ServerControl 2 (SC2/SVS) and ServerView RAID agents installed and running on the server's operating system. ServerView Update Agent is not required for this check.
• SNMP enabled on the operating system and reachable on the configured SNMP port — UDP 161 by default — with a community string (v2c) or USM user and keys (v3).
• Point the check at the server's operating system address — not the iRMC management controller.

Steps

You can assign the check to a network device as well as to an agent device. On an agent device, add it to the device that reaches the Fujitsu server over the network.

1. Go to Devices and open the device that has network access to the Fujitsu server.
2. Click the Checks tab → Add Check → Fujitsu ServerView Health (SNMP).
3. Enter the server's hostname or IP address in the Server host / IP (OS, not iRMC) field. Use the address of the server's operating system, where the ServerView agents run.
4. Choose the SNMP version the server is configured for. For v2c, enter the SNMP Community. For v3, enter the user and select the authentication and privacy protocols and passwords.
5. (Optional) Set Extra temp warning cap (°C, 0 = off) in °C to add a single warning threshold on top of each sensor's own limits. Leave it at 0 to rely only on the thresholds the hardware reports.
6. Click Add Check.

After the first check interval, the result appears in the device's Checks tab.

Settings

The table lists every field in the order it appears in the check editor.

Temperatures use each sensor's own warning and critical limits as reported by the hardware. The extra temp warning cap is an additional, global safeguard and applies only to sensors that have not already reached their own warning or critical limit, so one sensor never counts twice.

Results

The overall result is the worst severity across every subsystem and sensor. An individual subsystem with ServerView status unknown remains visible in the result but does not increase the overall severity. An unknown overall status still produces a warning. Inspect individual components rather than treating OK as confirmation for every subsystem.

Collected metrics

The check reports:

• Server model and serial number
• Overall system status, and the CPU / Systemboard status read from the server's Systemboard subsystem
• Status for every subsystem the server's ServerView rollup reports, under the names ServerView itself uses
• Highest temperature and the sensor that reported it, plus warning and critical sensor counts
• Fan count and lowest fan speed (RPM)
• Power-supply count
• Total installed memory (GB)
• Per-disk name and capacity from ServerView RAID — the disk model stands in when the RAID agent reports no name

Tips

• The check reads its data from the Fujitsu ServerView agents on the server, so those agents must be installed — a bare SNMP service on the operating system is not enough.
• For a Hyper-V host running on the Fujitsu server, monitor the hypervisor separately with the Microsoft Hyper-V Host check.