Foglight for Storage Management Shared 4.8.5 - User and Reference Guide

Installing External Agent Managers

If you are installing external Agent Managers, first ensure that the servers that host the external Agent Managers meet the requirements listed under Large Environment System Requirements and Requirements for Agent Managers. Then follow the instructions under “Installing external Agent Managers” in the Foglight Agent Manager Guide.

Creating a Lockbox for Foglight for Storage Management Credentials

Lockboxes enable you to store encrypted credentials in a central location and organize credentials into meaningful groups. A credential contains the user account information required to access a monitored device, such as a login name and password.

The Agent Manager has a default lockbox named System. You can use this lockbox, or you can create a separate lockbox to group the credentials used to access storage devices. If you want to create a lockbox, you should do it now, because when you begin configure Storage Collector Agents, the wizard prompts you to assign credentials in lockboxes.

Supporting an Environment with Separate Fabrics that have Duplicated WWNs

Foglight for Storage Management uses WWNs as unique identifiers for mapping SAN topologies.

If you are using HP Virtual Connect capability, or another similar product, to allow fabrics in different datacenters to use the same WWN ranges in your SANs, additional steps must be taken to allow a single Foglight installation to process the collected data properly.

The Storage & San > Storage Environment > Administration dashboard provides a task called Configure Duplicate WWN Support. Click on this task to display a dialog that will let you specify prefix values that Foglight will prepend to collected WWN values to create unique identifiers within Foglight.

The datacenters with overlapping WWN ranges must be configured with different FglAMs for each datacenter.

All the FglAMs that collect from devices that interconnect must be configured to use the same prefix. Typically this would be all the FglAMs supporting a physical location or datacenter. These identifiers will apply to storage devices and virtualization devices.

Failure to provide unique identifiers in this situation will result in incorrect topology diagrams being displayed, and it may also cause performance problems.

Configuring Storage Collector Agents

In this step, you configure Storage Collector Agents to monitor supported storage devices. A wizard leads you through the process. Depending on the storage device, the details of the process may be different, but the general activities remain the same.

The general workflow follows these steps:

To begin configuring a Storage Collector Agent (hereafter referred to simply as agent), select the target storage device from the following list. For each device, the collection method is described first, followed by requirements, and then the configuration procedure.

If you later need to edit an agent configuration, see Editing Configured Agents.