• Conviértase en un profesional en el portal de soporte
• Descargar
• Imprimir
• Mis descargas ()

• Soporte
• Documentación técnica
• Foglight for SNMP 5.9.5
• Foglight for SNMP 5.9.5 - User and Reference Guide

Foglight for SNMP 5.9.5 - User and Reference Guide

Navegación de contenido  

Using Foglight for SNMP to monitor devices

Installing or upgrading Foglight for SNMP Foglight for SNMP navigation basics Understand monitoring with both host and SNMP agents Multiple Foglight Agent Manager instances SNMP discovery

SNMP discovery on Linux requirements

Using sudo to configure Secure Launcher permissions

Running SNMP discovery Ineligible devices

SNMP communities and credentials

Accessing the Manage all credentials wizard Managing SNMP V1 or V2c community strings Managing the SNMP V3 credentials Changing an SNMP device credential

Managing monitor configurations Configuring SNMP agent properties Changing the GenericSNMPTrapAgent port Viewing SNMP monitored hosts

Hosts monitored by both an Infrastructure and SNMP agent Hosts monitored only by SNMP Hosts monitored only by an Infrastructure agent

Generating reports Foglight for SNMP reference

Overview tab Networking tab

Pre-defined Foglight for SNMP network monitors

Disk Volumes tab Running Processes tab Installed Applications tab Custom Properties tab

• Visualización de Temas 5 - 8 de 31

×

Multiple Foglight Agent Manager instances

Having multiple Foglight Agent Manager instances is supported for Foglight for SNMP.

When you run an SNMP discovery, a specific Foglight Agent Manager is selected to monitor the discovered devices. Each set of devices that you discover can be monitored by a specific Agent Manager. A device can be monitored by one Foglight Agent Manager instance only.

Related topic:

•	Running SNMP discovery

SNMP discovery

Foglight for SNMP uses SNMP to discover devices in a network and then to provide a complete set of attributes for each discovered device. This type of network discovery gathers data relating to hardware, software, and processes for each device, and identifies devices by responding status, protocols, type, and operating system.

Running an SNMP discovery completes the following activities:

•	Deploys the agent package to the selected Foglight Agent Manager instance.

•	Creates the discovery agent (GenericDiscoveryAgent) on the Foglight Agent Manager instance, if one does not exist.

•	Discovers devices in a network.

•

Creates SNMP monitoring agent instances based on the OS types of the devices selected for discovery. For example, if you choose discovered devices that have Linux® and Windows® operating systems, a GenericSNMPWindowsAgent instance and a GenericSNMPLinuxAgent instance is created in that Foglight Agent Manager to monitor those devices respectively.

Next step:

•	Running SNMP discovery.

SNMP discovery on Linux requirements

Foglight for SNMP running on Linux requires that you allow Foglight Agent Manager root or administrator access to start the Agent Manager’s ICMPService. Perform one of the following in this order of preference.

•	On a more advanced Linux system, assign CAP_NET_RAW capability to the ICMPService to allow this access.

•	Configure sudo to allow udp2icmp helper application to run as root.

•	Edit the sudoers file for your system to allow <fglam_home>/client/*/bin/udp2icmp to be run as root by the Foglight user. For detailed steps, see Using sudo to configure Secure Launcher permissions.

•	Provide Foglight Agent Manager with root permissions (not recommended).

Next step:

•	Running SNMP discovery

Using sudo to configure Secure Launcher permissions

This section contains instructions for using sudo to give agents elevated permissions. Use one of the following two methods: the configuration interface or the fglam.config.xml file.

To set up secure launcher permissions using the configuration interface and sudo:

1	Follow the instructions in the Launching the Agent Manager Installation Interface or Configuring the Agent Manager from the Command-Line topics in the Foglight Agent Manager Guide.

2	Navigate to the Configure Secure Launcher or Secure Launcher step.

3	Set the path to point to the sudo executable. This executable is typically located in /usr/bin/sudo (the default path provided by the Agent Manager installer).

4	Exit from the configuration interface as described in Launching the Agent Manager Installation Interface or Configuring the Agent Manager from the Command-Line topics in the Foglight Agent Manager Guide.

5	Edit the sudoers file for your system to allow <fglam_home>/client/<fglam_version>/bin/fog4_launcher to be run as root by a specific user, without requiring a password, and only for the agents that require root privileges.

For example, to allow the user foglight to run fog4_launcher for two specific agents without being prompted for a password:

foglight    ALL = NOPASSWD:  \

/<fglam_home>/client/*/bin/fog4_launcher /<fglam_home>/state/default/<cartridge>/*/bin/<agent> ?*@?* bin/<agent>, \

/<fglam_home>/client/*/bin/fog4_launcher /<fglam_home>/state/default/<cartridge>/*/bin/<agent2> ?*@?* bin/<agent2>

The example above also limits the acceptable arguments to match the expected pattern when the Agent Manager runs the agents.

6	Edit the sudoers file for your system to allow <fglam_home>/client/*/bin/udp2icmp to be run as root by a specific user, without requiring a password. This is required for ICMP ping service.

See the Foglight for Infrastructure User and Reference Guide for detailed examples of how to edit the sudoers file to restrict the granted permissions to a specific set of agents.

 

TIP: For sudo configuration, it is a best practice to use a wildcard for the version-specific Agent Manager and cartridge directories, as shown in the example above. Using a wildcard in a path is described in the Sudoers Manual at: http://www.gratisoft.us/sudo/man/sudoers.html#wildcards Using a wildcard for the version-specific directories allows you to avoid updating each sudoers file that references these directories when you upgrade the Agent Manager or the agents.

If these permissions are no longer needed, remove the lines that you added to run fog4_launcher or udp2icmp with root permissions.

To set up secure launcher permissions using fglam.config.xml and sudo:

1	Navigate to <fglam_home>/state/default/config.

2	Open the fglam.config.xml file for editing.

3	Edit the <config:path> element under <config:secure-launcher> to point to the sudo executable. This executable is typically located in /usr/bin/sudo (the default path provided by the Agent Manager installer).

4	Edit the sudoers file for your system to allow <fglam_home>/client/<fglam_version>/bin/fog4_launcher to run as root by a specific user, without requiring a password, and only for the agents that require root privileges.

For example, to allow the user foglight to run fog4_launcher for two specific agents without being prompted for a password:

foglight    ALL = NOPASSWD:  \

/<fglam_home>/client/*/bin/fog4_launcher /<fglam_home>/state/default/<cartridge>/*/bin/<agent> ?*@?* bin/<agent>, \

/<fglam_home>/client/*/bin/fog4_launcher /<fglam_home>/state/default/<cartridge>/*/bin/<agent2> ?*@?* bin/<agent2>

The example above also limits the acceptable arguments to match the expected pattern when the Agent Manager runs the agents.

5	Edit the sudoers file for your system to allow <fglam_home>/client/*/bin/udp2icmp to be run as root by a specific user, without requiring a password. This is required for ICMP ping service.

See the Foglight for Infrastructure User and Reference Guide for detailed examples of how to edit the sudoers file to restrict the granted permissions to a specific set of agents.

 

TIP: For sudo configuration, it is a best practice to use a wildcard for the version-specific Agent Manager and cartridge directories, as shown in the example above. Using a wildcard in a path is described in the Sudoers Manual at: http://www.gratisoft.us/sudo/man/sudoers.html#wildcards Using a wildcard for the version-specific directories allows you to avoid updating each sudoers file that references these directories when you upgrade the Agent Manager or the agents.

Next step:

•	Running SNMP discovery

•  Anterior
• Visualización de Temas 5 - 8 de 31
• Siguiente 

Buscar este documento Buscar todos los documentos

×

 Bienvenido al portal de soporte

Puede encontrar ayuda de soporte en línea para el *producto* Quest en un sitio de soporte afiliado. Haga clic en Continuar para ser dirigido al contenido de soporte y a la asistencia adecuados para el *producto*.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center