Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for Storage Management Shared 6.0.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

Requirements for NetApp Filers

Your environment must meet the following requirements:

•
Foglight for Storage Management requires an account with the appropriate defined role access capabilities to enable DataONTAP® API.
•
For supported versions of DATA ONTAP and Cluster Mode (C-Mode), see Appendix: Supported Storage Devices Table .
•
For general access, the following permissions are required for the accounted used for monitoring:
•
login-http-admin - allows connection to the NetApp storage via HTTP.
•
system-api-list - allows querying for the list of available API methods available
•
security-api-vfiler - allows the execution of API commands to retrieve vFiler unit information.
•
"api-*" - allows the use of NetApp API calls for data collection
•
For limited access, different monitoring roles will need to be created depending on the NetApp system to which you are connecting. For information on how to create a read-only user to monitor a storage system in OnCommand System Manager, OnCommand Unified Manager or Performance Advisor, refer to your NetApp documentation. Foglight for Storage Management will never request or require write access to any filer components or services.
•
Foglight for Storage Management may execute some or all of the following calls when collecting data. Not all calls are available on all versions of Data ONTAP.
Table 10. List of calls

aggr-get-iter

lun-get-iter

qtree-list

aggr-list-info

lun-get-occupied-size

quota-report

aggr-space-get-iter

lun-get-serial-number

snapshot-delta-info

aggr-status-get-iter

lun-get-space-reservation-info

snapshot-get-reserve

cifs-share-get-iter

lun-list-info

snapshot-list-info

cifs-share-list-iter-end

lun-map-get-iter

snmp-get

cifs-share-list-iter-next

lun-map-list-info

snmp-get-next

cifs-share-list-iter-start

net-interface-get-iter

storage-disk-get-iter

cluster-identity-get

nfs-exportfs-list-rules

system-api-list

disk-list-info

nfs-exportfs-list-rules-2

system-get-info

fcp-adapter-get-iter

perf-object-counter-list-info

system-get-node-info-iter

fcp-adapter-list-info

perf-object-get-instances

system-get-ontapi-version

fcp-interface-get-iter

perf-object-get-instances-iter-end

system-get-version

fcp-node-get-name

perf-object-get-instances-iter-next

vfiler-list-info

fcp-port-name-get-iter

perf-object-get-instances-iter-start

volume-get-iter

igroup-get-iter

perf-object-instance-list-info

volume-get-root-name

iscsi-interface-get-iter

perf-object-instance-list-info-iter

volume-list-info

iscsi-node-get-name

portset-get-iter

volume-options-list-info

iscsi-service-get-iter

portset-list-info

vserver-get-iter

•
In 7-Mode, this command line can be used to create a role with only the limited permissions required for monitoring.
useradmin role add vfs_collector -a login-http-admin,api-system-get-version,api-system-get-info,api-system-get-ontapi-version,api-aggr-list-info,api-volume-list-info,api-volume-get-root-name,api-volume-options-list-info,api-qtree-list,api-quota-report,api-disk-list-info,api-cifs-share-list-iter-start,api-cifs-share-list-iter-next,api-cifs-share-list-iter-end,api-nfs-exportfs-list-rules,api-nfs-exportfs-list-rules-2,api-snapshot-delta-info,api-snapshot-get-reserve,api-snapshot-list-info,api-lun-map-list-info,api-lun-list-info,api-lun-get-occupied-size,api-lun-get-space-reservation-info,api-lun-get-serial-number,api-iscsi-node-get-name,api-fcp-node-get-name,api-fcp-adapter-list-info,api-portset-list-info,api-snmp-get,api-snmp-get-next,api-vfiler-list-info,api-perf-object-get-*,api-perf-object-counter-list-info,security-api-vfiler,api-perf-object-instance-list-info,api-system-api-list
Once the role is created, it must be associated with a group, and the group associated with a user. The NetApp documentation covers this in more detail: https://library.netapp.com/ecmdocs/ECMP1155684/html/GUID-20BAA16F-7411-45F1-84E8-4C6761D9B539.html
In cluster mode, the newer security login commands can be used to create a role with the appropriate permissions.
It is possible to create a read-only role and assign it to an account without specifically listing the commands required. This is done by first creating the role with the correct access permissions, and then creating a new user account associated with that role.
To create the rule, the following command is used:
security login role create -role vfs_collector -cmddirname DEFAULT -access readonly
This role will have read-only access to the default set of NetApp commands. Then a user can be created and associated with this role:
security login create -username vtest -application ontapi -authmethod password -role vfs_collector
If more fine-grained control over the permissions assigned is required, then the complete list of commands required will need to be granted individually. This is done by allowing read-only access to the command associated with each API call that the Foglight for Storage Management agent is required to make. The NetApp documentation should be consulted for more details.
The mapping of API permissions to NetApp commands is:
 
Table 11. Mapping of API permissions to NetApp commands
API Name
Command Line Permission

api-aggr-get-iter,

api-aggr-status-get-iter

storage aggregate show

api-aggr-space-get-iter

storage aggregate show-space

api-cifs-share-get-iter

vserver cifs share show

api-cluster-identity-get

cluster show

api-disk-list-info

storage disk show

api-fcp-adapter-get-iter

network fcp adapter show

api-fcp-interface-get-iter

vserver fcp interface show

api-fcp-port-name-get-iter

vserver fcp wwpn-alias show

api-iscsi-service-get-iter

vserver iscsi show

api-lun-get-iter

lun show

api-lun-map-get-iter

lun mapped show

api-net-interface-get-iter

network interface show

api-nfs-service-get-iter

vserver nfs show,

vserver nfs status

api-perf-object-counter-list-info

statistics catalog counter show

api-perf-object-get*

statistics show

api-perf-object-instance-list-info-iter

statistics catalog instance show

api-portset-get-iter

lun portset show

api-qtree-list-iter

volume qtree show

api-quota-report-iter

volume quota report

api-snapshot-*

volume snapshot show,

volume snapshot policy show

api-storage-disk-get-iter

storage disk show

api-system-get-node-info-iter

system node image show

api-system-get-version

version

api-volume-get-iter

volume show

api-vserver-get-iter

vserver show

igroup-get-iter

lun igroup show

A new role should be created:
security login role create -role vfs_collector -cmddirname "security login role show-ontapi" -access readonly
Each of the command line permissions will need to be assigned to the selected role in the following manner:
security login role create -role vfs_collector -cmddirname "storage aggregate show" -access readonly
Then a user created and associated with that role:
security login create -role vfs_collector -username vtest -application ontapi -authmethod password

 

* 
NOTE:  
•
In FIPS-compliant mode, you need to import the CA certificate or the self-signed certificate to the KeyStore of FglAM to use this option. For more information, see Managing certificates .
•
Storage agent only supports monitoring through IP address. Ensure that “Subject” or “Subject Alternative Name” field of the certificate includes the IP address of your device.

Configuring Agents to Monitor NetApp Filers

Configure an agent for each NetApp filer you want to monitor. For details, see Configuring Agents to Monitor Storage Devices.

Configuration Procedures

The preceding sections link to the folowing configuration procedures:

•
Configuring Agents to Monitor Storage Devices
•
Assigning Credentials
•
Resolving Connection Attempt Errors
•
Configuring the Hitachi Tuning Manager
•
Configuring Generic SMI-S Array Agent to Monitor Storage Devices
•
Managing certificates

Configuring Agents to Monitor Storage Devices

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 Agent for Storage Device Monitoring.
The Storage Device Setup dialog opens.
4
In the Add/Edit Agent section, select an agent manager host from the Agent Manager drop-down list.
5
In the Add/Edit Agent section, configure the agent settings:
a
Select the type of storage device from the Resource Type and Model drop-down lists, as indicated in Table 12.
b
In the IP Address field, type the IP address of the server hosting the agent manager.
c
If the Agent uses a non-default 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.
d
Specify a name for the agent in the Name field (optional).
e
Click Add.
The system checks the IP address. If the validation fails, check the IP address and ensure the device at the IP address is functioning.
The Credential Assignment Wizard opens.
6
Create or select a credential that contains the account information needed to access the storage device. For detailed information, see Assigning Credentials.
7
For Hitachi Data Systems AMS, USP, and VSP devices only: If you want to use the Hitachi Tuning Manager for collecting additional metrics, follow the instructions in Configuring the Hitachi Tuning Manager.
The new StorageAgentMaster Monitor Agent is added to the table at the bottom of the dialog.
8
If the agent is correctly configured, continue with Step 9.
If the agent is incorrectly configured, the Validated column provides details to help you troubleshoot the issue. For additional information, see Resolving Connection Attempt Errors.
9
Click OK to exist the Storage Device Setup dialog.
 
Table 12. Storage Device requirements
Type of Storage Device
Vendor
Resource Type field
Model field
FC Switches

Brocade SAN Switches

FC Switch

Brocade

 

Cisco SAN Switches

FC Switch

Cisco

Storage Arrays

Dell Compellent Arrays

Storage Array

Dell Compellent

 

Dell EqualLogic PS Series Array Groups

Storage Array

Dell EqualLogic

 

EMC CLARiiON CX Series Arrays (CLI)

Storage Array

EMC CLARiiON using CLI

 

EMC CLARiiON, VNX, or VMAX Storage Arrays (SMI-S)

Storage Array

EMC VNX/CLARiiON/VMAX - SMIS

 

EMC Isilon

Storage Array

EMC Isilon

 

Hitachi Data Systems AMS, USP, and VSP

Storage Array

HDS AMS/UPS/VSP

 

HP EVA Storage Arrays

Storage Array

HP EVA

 

HP 3PAR Arrays

Storage Array

HP 3PAR

Filers

NetApp Filers

Filer

NetApp

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation