Chat now with support
Chat mit Support

Foglight for Storage Management Shared 6.1.0 - User Guide

Getting Started Configuring Agents to Monitor Storage Devices
Brocade SAN Switches Cisco SAN Switches Dell Compellent Arrays Dell EqualLogic PS Series Array Groups EMC CLARiiON CX Series Arrays (CLI) EMC CLARiiON, VNX, or VMAX Storage Arrays (SMI-S) EMC Isilon EMC VPLEX Hitachi Data Systems AMS, USP, and VSP HP EVA Storage Arrays HP 3PAR Arrays NetApp Filers Configuration Procedures
Managing Agents Using Foglight for Storage Management Monitoring Storage Performance Investigating Storage Devices Investigating Storage Components Investigating VPLEX Storage Troubleshooting Storage Performance Managing Data Collection, Rules, and Alarms Understanding Metrics Appendix: Supported Storage Devices Table Online-Only Topics

Resolving Connection Attempt Errors

If the agent’s attempt to connect and validate fails, the error message usually contains a suggested resolution. For example, you may need to fix credentials or release the lockbox.

If the connection is refused because the entered IP address is incorrect, you need to cancel the wizard, delete the agent, and restart the wizard using the correct IP address. If the port is wrong, you can click the value beside the Port field to correct the value.

If the problem cannot be resolved at this time, close the Storage Device Setup dialog. The configuration that has been done up to the point where the error occurred is saved. After resolving the problem, edit the agent configuration and validate the settings. For more information, see Editing Configured Agents.

Configuring the Hitachi Tuning Manager

To configure the Hitachi Tuning Manager:
1
On the second page of the Credential Assignment Wizard (available only for Hitachi Data Systems AMS, USP, and VSP devices), read the information provided.
2
If you want to use the Hitachi Tuning Manager for collecting additional metrics, check the Use HDS Tuning Manager checkbox.
3
If the Tuning Manager is not installed in the default path, type the installation Path.
4
Type the IP Address of the system on which HDS Tuning is installed. If left blank, then the IP address of the array or array manager is assumed.
5
Click Finish to complete the operation and return to the Storage Device Setup dialog.

Configuring Generic SMI-S Array Agent to Monitor Storage Devices

During this procedure, you configure the agent to use SMI-S to collect from the Array Management Host that monitors the arrays.

To configure an agent to monitor the storage device:
1
On the navigation panel, under Homes, click Storage Environment.
2
Click the Administration tab.
3
Click Configure SMIS Agent for Storage Device Monitoring.
The Storage Device Setup dialog opens.
4
In the Add SMIS Storage Agent section, select an agent manager host from the Agent Manager drop-down list.
5
In the Add SMIS Storage Agent section, configure the agent settings:
a
In the IP Address field, type the IP address of the server hosting the agent manager.
b
If the Agent uses a non-default (5988 or 5989) port, type the port number in the Port field. Ensure that this port is open and that traffic is permitted between the device and the Agent Manager host.
c
Check the HTTPs check-box if the Agent uses SSL connection.
d
Specify a name for the agent in the Name field (optional).
e
Click Add.
6
Create or select a credential that contains the account information needed to access the storage device. For more information, see Assigning Credentials.
7
Click OK to exit the Storage Device Setup dialog.

Managing certificates

Syntax Conventions

In order to successfully make use of the Foglight commands in your monitoring environment, review the syntax conventions before getting started. The syntax conventions are as follows:

•
Generic examples follow the UNIX path structure that uses forward slashes '/' to separate directories.
•
Platform-specific examples follow standard platform conventions. For example, UNIX-specific examples use forward slashes ‘/’ as directory delimiters, while Windows examples use backslashes ‘\’.
•
<foglight_home> is a placeholder that represents the path to the Foglight Management Server installation.
•
<foglight_agent_mgr_home> is a placeholder that represents the path to the Foglight Agent Manager installation. This can be the location of the Foglight Agent Manager installation on a monitored host, or the home directory of the Foglight Agent Manager that comes embedded with the Foglight Management Server. For example:
Path to the Foglight Agent Manager installation on a monitored host (Windows):
C:\Quest\Foglight_Agent_Manager
Path to the embedded Foglight Agent Manager installation (Windows):
C:\Quest\Foglight\fglam
•
Unless otherwise specified, Foglight commands are case-sensitive.
Managing certificates for FglAM

Foglight Evolve agents use Foglight Agent Manager (FglAM) to manage certificates for SSL encryption connection.

Prerequisite

All the certificate-related command line options require that FglAM be up and running.

Add a certificate

bin/fglam --add-certificate "user alias 1"=/path/to/certificate/file

•
Validate the certificate and ensure the following:
•
It is not expired.
•
It is an X.509 format.
•
FglAM requires the Base64 format. To verify if the certificate file is encoded with Base64, open the certificate with a notepad and the certificate should be similar to the following example:
-----BEGIN CERTIFICATE-----
XXXXXXXX=
-----END CERTIFICATE-----
* 
NOTE: If the certificate is not Base64 format, use openssl command to convert the certificate file into a Base64 file. Use either of the following commands depending on the source form:
openssl x509 -inform DER -in xxx.cer -out xxx.crt
or
openssl x509 -inform PEM -in xxx.cer -out xxx.crt
•
The alias is required and is used in the list and delete operations to refer to the certificate. It can be anything.
List installed certificates

bin/fglam --list-certificates

Print out a list of certificates and the aliases that refer to them.

Refer to the example output below:

List of installed certificates:
Alias Certificate Info
----- ----------------
user alias 1 XXXX
Delete a certificate

Remove a certificate referred to by an alias.

bin/fglam --delete-certificate "user alias 1"

A full example for managing certificate for FglAM
•
Add an example certificate into FglAM certificate store
C:\Quest\Foglight\fglam\bin>fglam.exe --add-certificate "Evolve-test"="D:/Evolve-test.crt"
…
2020-02-27 16:31:01.000 INFO [native] Certificate added: Certificate from
D:\Evolve-test.crt added as Evolve-test
•
List the example certificate in the FglAM certificate store
C:\Quest\Foglight\fglam\bin>fglam.exe --list-certificate
…
Alias Certificate
----- -----------
Evolve-test Issuer:
CN: XXX
•
Delete the example certificate from the FglAM certificate store
C:\Quest\Foglight\fglam\bin>fglam.exe --delete-certificate "Evolve-test"
…
2020-02-27 16:28:21.000 INFO [native] Certificate deleted: Certificate
Evolve-test deleted

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen