サポートと今すぐチャット
サポートとのチャット

Foglight for Storage Management Shared 4.7 - User and Reference 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 Collection Target Support Matrix 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 Online-Only Topics

Verifying StorageCollector/Generic SMIS Storage Agents are Collecting Storage Data

To begin, review the Foglight for Storage Management dashboards to verify you are monitoring the devices you want to monitor. You need the IP address of the Foglight for Storage Management Management Server and your user credentials from the person who installed and configured Foglight for Storage Management.

 
* 
NOTE: This procedure is intended for Foglight for Storage Management users with the roles of Storage Administrator, VMware Administrator and Hyper-V Administrator.
To log in and confirm the list of monitored devices:
1
Open a supported browser. For a list of supported browsers, see the System Requirements Guide.
2
In the navigation bar, type the IP address followed by the port number 8080. For example:
http://<Foglight for Storage Management_Management_Server_IP_Address>:8080
3
Log in to Foglight for Storage Management using your user credentials.
4
On the navigation panel, expand Dashboards.
These menu items are of particular interest for monitoring storage performance: Storage & SAN, VMware, Hyper-V and Infrastructure.
5
Expand Storage & SAN.
The following menu items are available:
•
Storage Capacity — Monitor your storage capacity by device type.
•
Storage Environment — Monitor storage devices in your storage environment.
•
Storage Explorer — Find and examine any storage device in your storage environment.
6
Click Storage Environment.
7
Ensure the Monitoring tab is selected.
8
Click the top half of each active tile and review the list of devices in the quick view.
9
If you do not see a storage device that you think should be monitored, review the list of configured Storage Collector agents.
f
On the Storage Environment dashboard, click the Administration tab.
 
* 
TIP: If you do not see the Administration tab, ask your Foglight for Storage Management Administrator to add the role Storage Administrator to your user account.
g
In the Storage Agents > StorageCollector Agents list, look for the Storage Collector agent that monitors the missing device or device type. When an agent monitors a device type, click the Edit icon to view a list of named devices in the Edit Agent Properties dialog box.
Or
In the Storage Agents > Generic SMIS Storage Agents list, look for the SMIS Storage agent that monitors the missing device or device type. When an agent monitors a device type, click the Edit icon to view a list of named devices in the Edit Agent Properties dialog box.
h
If a StorageCollector agent or Generic SMIS Storage agent does not exist for a device, or if the agent exists but it is disabled or its data collection is turned off, contact your Foglight for Storage Management Administrator. For instructions about agent tasks, see the Foglight for Storage Management Installation Guide.
10
Go to the dashboard for the storage device or switch and ensure that both performance and topology information have been submitted recently.

Collecting Storage Data for Virtualized Devices and Servers

To collect storage data for virtualized devices and servers:
1
On the navigation panel, expand the dashboard menu for your virtualization software. For example, either VMware or Hyper-V.
 
* 
TIP: If you do not see the VMware or Hyper-V menu, ask your Foglight for Storage Management Administrator to add the appropriate administrator role to your user account.
2
To verify the virtualization agents:
a
Click the Hyper-V or VMware Explorer.
The Explorer opens a Virtual Infrastructure Topology tree—displayed in the navigation panel below the list of Dashboards—that contains branches for each monitored vCenter or Hyper-V server. For detailed information about the dashboards available through this tool, see the Managing Virtualized Environments User and Reference Guide.
b
If the Virtual Infrastructure Topology list is empty, your Foglight for Storage Management Administrator needs to create a Performance agent to monitor at least one vCenter or Hyper-V server. For instructions, see the Foglight for Storage Management Installation Guide.
c
If the list is not empty, expand the tree and select a virtualization host or server.
d
Click the SAN Topology tab.
e
Verify that you can see the storage-side of the virtual infrastructure, identified by the icons that are circled in the following diagram. If these elements are missing, the Performance agent monitoring this host is not collecting the data necessary to make connections to storage and SAN data. To enable storage data collection, see Collecting Virtual Storage-to-SAN Relationships.
After you finish with Performance agents, review monitored hosts.
3
On the navigation panel, click Infrastructure.
a
In the Select a Service box, select All Hosts.
The tiles organize physical hosts by their operating system.
b
Click the Inferred tile.
The Inferred tile lists physical hosts that Foglight for Storage Management has inferred based on an analysis of the switch, array, and filer ports it is monitoring (a process called dependency processing). When physical hosts are connected to storage devices, you can drill down on a host and view connections in SAN Topology tabs.
c
If the Inferred tile does not show any inferred hosts, you may want to enable dependency processing to begin collecting the names of inferred hosts. For more information, see Inferring Physical-Host-to-Storage Relationships.
You have finished verifying that agents are collecting data.

Understanding Metric Data in Charts and Tables

In the Storage & SAN dashboards, charts and tables display metric data. Data is collected by Storage Collector agents, aggregated into collections, and the collections are published to the SAN & Storage dashboards at regular intervals. For more information about storage collection schedules and the type of data collected, see Modifying Data Collection Schedules.

The data displayed in charts and tables represents data for one or more intervals in the selected time range as follows:

•
Current. The value collected in the last interval in the selected time range. In charts, the last plotted value is the current value.
•
Period. Aggregated values for the entire selected time range. Period values are often used to provide context for current values.
•
Historical. Individual values for each collection interval in the selected time period. Historical values are often presented as datapoints in a plot chart or as sparklines to show how metrics changed over the time period.
•
Latest. Values in the latest collection interval available, irrespective of the selected time range. If data collection is enabled, this value reflects the latest collection. If data collection is disabled, this value represents the last collection made by the agent. Although latest values are tracked, the SAN & Storage dashboards do not display these values.

For indepth information about metrics, see http://communities.quest.com/docs/DOC-12862.

Values are not available (n/a) under the following circumstances:

•
The device vendor does not provide the necessary metric. In this case, the text n/p by vendor appears after the metric name in column headings.
•
A device is offline (reported in the State field).
•
A device is not actively being used, such as when a disk is configured as a spare (reported in the Used or Role fields).
•
For the Latency metric (which is a partially computed metric), when the operations/second value is very low, the latency metric may not be submitted during a collection interval.
•
If all other situations do not apply, then it is likely that data collection failed for some reason. If the current value is unavailable for a time range that occurs in the past, you can try changing the selected time range to end before or after the problem interval.

Modifying and Extending Data Collection

You can modify and extend data collection in the following ways. You may want to make these changes now, or adjust the settings in the future if you find a need.

 
Table 14. Data collection options
Options
Instructions

If not already enabled during installation, collect data about virtualization device-to-SAN relationships and display this information in SAN topology diagrams. Requires a VMware or Hyper-V Performance agent.

Collecting Virtual Storage-to-SAN Relationships

Infer connections from physical hosts to storage and show the connections in topology diagrams.

Inferring Physical-Host-to-Storage Relationships

Change the default collection interval.

Modifying Data Collection Schedules

Modify when rules trigger alarms (change threshold values) and add a list of email addresses to notify when alarms occur.

Managing Foglight for Storage Management Rules

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択