Monitors nothing other than Network Interfaces

 Home  Previous  Next

This is typically an "SNMP" issue. Many manufacturer-provided hardware agents use the SNMP technology (DELL OpenManage, HP Insight Management, Fujitsu-Siemens Serverview and for example). Since Hardware Sentry gathers hardware information from these agents, you need to enable and properly configure the SNMP layer on the managed servers if an SNMP-based agent is running on them.

However sometimes, like in the case of HP® (Compaq®) ProLiant® servers, the network interface is detected through other protocols and therefore displays in the PATROL Console/Central view whilst no other hardware component gets detected by Hardware Sentry – simply because it cannot communicate with the managed element. So enabling and authorizing the managed server to communicate through the SNMP protocol is essential.

Starting with Windows Server 2003, the SNMP service is not configured to allow the "public" community by default. As a consequence, even if the SNMP service is properly installed and the hardware agent properly running, Hardware Sentry is not able to gather any hardware information from the SNMP agent.

Therefore, on Windows Server 2003 computers that run an SNMP-based hardware agent (DELL OpenManage, HP Insight Management or Fujitsu-Siemens Serverview), you first need to install the SNMP service (not installed by default) and then configure it to allow a community to access the SNMP agent.

1.In the Services administrative tool, right-click the SNMP service > Properties. Click the Security tab:

w2k3snmp1

2.Click on the Add button and enter a community name that will be allowed to access the SNMP agent (READ ONLY):

w2k3snmp2

3.Click OK. The new settings are taken into account immediately. Hardware Sentry will automatically detect the community string that you entered in the security settings of the SNMP service.