Chat now with support
Chat with Support

Foglight for SNMP 5.9.6 - User and Reference Guide

Running SNMP discovery

Prerequisites:
•
SNMP discovery on Linux requirements.
•
The SNMP credentials for the device being discovered.
•
The ports for the SNMP protocol (by default, 161) and SNMP traps (by default, 162) must be open, and not blocked by a firewall.
The SNMP protocol port can be changed during the discovery process. The SNMP trap port on the GenericSNMPTrapAgent can be changed in the agent properties. For more information, see Changing the GenericSNMPTrapAgent port
* 
IMPORTANT: On Linux® hosts, non-root users cannot bind to ports below 1024. The default port number for the SNMP traps is 162, so the port number must be changed.
To complete the agent configuration and discover devices:
1
On the navigation panel, under Dashboards, click Infrastructure.
2
On the Infrastructure Environment dashboard, click SNMP Hosts.
The Discover Device(s) interactive UI opens.
3
On the Select an Agent Manager page, select the Foglight Agent Manager instance that you want to use to monitor devices.
The SNMP discovery deploys the agent package to this Foglight Agent Manager instance. If a discovery agent does not exist on this Foglight Agent Manager instance, the GenericDiscoveryAgent is created.
4
On the Input Device Info page, discover the devices that you want to monitor with the selected Foglight Agent Manager.
a
In the IP Address to Discover section, add a single IP address or a range of IP addresses for discovery.
•
Click Add IP to specify an IP address and SNMP Port.
Or
•
Click Add IP Range to specify a range of IP addresses and an SNMP Port.
For example, an IP address range of 10.10.120.1 — 10.10.121.2 adds the following IP addresses: 10.10.120.1, 10.10.120.2, 10.10.121.1, and 10.10.121.2.
The SNMP port is the port number for the SNMP protocol on the device. The default is 161, but it can be changed to the value that was set when SNMP was configured on the device.
b
In the Exclude Criteria table, specify any IP addresses to exclude from discovery.
•
Click Add IP to specify the IP address that should be excluded.
 
* 
NOTE: Click Exclude Criteria to see a list of IP addresses that are excluded by default.
Or
•
Click Add IP Range to specify a range of IP addresses to exclude.
5
On the Assign Credential page, specify the SNMP credential version and the community string required to discover devices
•
Credential Version — The version of SNMP used to monitor the host.
•
Credential — SNMP community string. The default is public.
 
* 
NOTE: Click Manage all credentials to add Communities and Credentials. For information on how to add or remove Communities and Credentials, see Managing SNMP V1 or V2c community strings and Managing the SNMP V3 credentials.
6
The Discover Device(s) page opens refreshes to display a list of discovered and ineligible devices. For more information on ineligible devices, see Ineligible devices.
7
Select one or more devices for this Agent Manager to monitor.
 
* 
NOTE: You can provide an override name by editing the Override Name field. The name you supply is used as the identity of that host.
8
Click Finish.
At this step in the discovery, the following agents are created on the Foglight Agent Manager:
•
The GenericSNMPTrapAgent is created for the Foglight Agent Manger (if one did not exist).
* 
IMPORTANT: Linux non-root users cannot bind to ports below 1024. The default port number for the GenericSNMPTrapAgent is 162, so the port number must be changed for Linux hosts before devices can be monitored. For detailed information, see Changing the GenericSNMPTrapAgent port.
•
Monitoring agent instances for the OS types of the chosen discovered devices.
The following seven agents may be created, depending on the OS type of the discovered devices:
Table 1. Monitoring agent instances created during discovery
Agent name
Created for
Collector settings

GenericSNMPWindowsAgent

devices with Windows OS

Default enabled:
cpu, memory, diskVolumes, systemInfo, runningProcess, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration,availability, programInstalled, customProperties

GenericSNMPSolarisAgent

devices with Solaris OS

cpu, memory, diskVolumes, systemInfo, runningProcess, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration,availability, programInstalled, customProperties

GenericSNMPHPUXAgent

devices with HP-UX OS

cpu, memory, diskVolumes, systemInfo, runningProcess, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration,availability, customProperties

Disabled by default:
programInstalled

GenericSNMPAIXAgent

devices with AIX OS

cpu, memory, diskVolumes, systemInfo, runningProcess, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration,availability, programInstalled, customProperties

GenericSNMPLinuxAgent

devices with Linux OS

cpu, memory, diskVolumes, systemInfo, runningProcess, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration,availability, programInstalled, customProperties

GenericSNMPOtherAgent

Created if a host with an OS type is detected during discovery but the OS is not Windows, Linux, HPUX, Solaris, or AIX. The host is added to this agent for collection.

cpu, memory, systemInfo, availability customProperties, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration

Disabled by default:
programInstalled, runningProcess, diskVolumes

GenericSNMPInferredAgent

Created if an OS type for a host is not detected during discovery. The host is added to this agent for collection

cpu, memory, diskVolumes, systemInfo, customProperties, networkStatisticSummary, networkInterfacTraffic, networkInterfaceConfiguration, ipConfiguration, availability

Disabled by default:
programInstalled, runningProcess

Next steps:
•
To see the devices that you have discovered, see Viewing SNMP monitored hosts.
•
To investigate devices that could not be discovered, see Ineligible devices.

Ineligible devices

SNMP devices that are not discovered can be deemed ineligible for one of the following reasons:

•
The device is already being monitored by a Foglight Agent Manager.
For more information, see Multiple Foglight Agent Manager instances.
•
The host is unreachable and ICMP ping failed.
For more information, see SNMP discovery on Linux requirements.
•
SNMP failed either because of a request time out (for example, the specified credential is incorrect) or the target device does not support SNMP.
For more information, see SNMP communities and credentials.

SNMP communities and credentials

When you run SNMP discovery, specifying the correct device credentials is essential in order for Foglight for SNMP to access the devices in a network. When a device is discovered during a scan of the network, Foglight for SNMP adds it to the database. If the credentials are incorrectly set for that device, Foglight for SNMP cannot discover the device so that it can be monitored.

In the Discover Device(s) wizard, choose the correct credential for the devices in the network. Select a credential for one of the following protocols:

•
SNMP Version 1 Credential
•
SNMP Version 2c Credential
•
SNMP Version 3 Credential

From the Discover Device(s) wizard, you can add new credentials by clicking the Manage all credentials link. For more information, see Accessing the Manage all credentials wizard.

Related topics:
•
Managing SNMP V1 or V2c community strings
•
Managing the SNMP V3 credentials
•
Changing an SNMP device credential

Accessing the Manage all credentials wizard

* 
IMPORTANT: Add or remove credentials through the Manage all credentials wizard only.
To access the Manage all credentials wizard:
1
On the navigation panel, click Infrastructure.
2
On the Infrastructure Environment dashboard, click SNMP Hosts.
The Discover Device(s) wizard opens.
3
On the Select an Agent Manager page, select the Foglight Agent Manager instance that is monitoring the devices.
4
On the Input Device Info page, under IP Address to Discover, add either a single IP address and SNMP Port, or a range of IP addresses and SNMP Port.
5
On the Assign Credential page, click Manage all credentials.
6
To add or remove Communities and Credentials, follow the procedures in either Managing SNMP V1 or V2c community strings or Managing the SNMP V3 credentials.
 
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating