{"id":36330,"date":"2022-08-18T12:13:05","date_gmt":"2022-08-18T11:13:05","guid":{"rendered":"https:\/\/www.n-able.com\/?p=36330"},"modified":"2022-08-18T12:13:05","modified_gmt":"2022-08-18T11:13:05","slug":"using-n-central-for-server-hardware-monitoring","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/it\/blog\/using-n-central-for-server-hardware-monitoring","title":{"rendered":"Using N‑central for Server Hardware Monitoring"},"content":{"rendered":"

While it is fair to say that in recent years we\u2019ve seen a shift to servers being deployed in the cloud through Microsoft Azure or AWS, I\u2019m sure if you\u2019re reading this today you still have a large percentage of physical servers under your management, including Hyper-V and ESXi hosts. N‑central\u2019s ESXi monitoring should automatically detect and monitor the hardware in these boxes, but what about the rest? In this blog we\u2019re going to look at how N‑able N‑central<\/span><\/a> can monitor these physical servers, so you can address detected issues before they cause the server to fail.<\/span><\/p>\n

To monitor the hardware on these servers<\/span><\/a>, you\u2019ll first need to prepare them by taking these steps:<\/span><\/p>\n

    \n
  1. Ensure that SNMP Services are added and running on each server, and note the community strings in use. N‑central only requires a string with read-only privileges, so you can add a string as \u201cpublic\u201d (or whatever you prefer) as long as you add the SNMP string to your discovery job.<\/span><\/li>\n
  2. Ensure that you select the Accept SNMP packets from any host option on the Security tab for SNMP Service Properties.<\/span><\/li>\n
  3. Depending on your servers\u2019 manufacturer, you\u2019ll need to install the following software packages on the appropriate servers and to verify that the software is working correctly:<\/span><\/li>\n<\/ol>\n