Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > Adding storage arrays > NetApp Filer

NetApp Filer

Updated: June 16, 2017

Add your NetApp filer so SRM Profiler can query it directly. Find the information you need before you begin and steps for adding and configuring your NetApp filer. Review the NetApp Operations Manager section if you have many Filers to add to SRM Profiler.

Before you begin

  • Ensure that a SRM Profiler proxy agent is running on the server to be used to monitor your NetApp filer.
  • One or more SRM Profiler proxy agents for Windows/Unix/Linux must be used to perform File Analysis on a NetApp filer. Use Windows agents to perform analysis on CIFS shares and Unix/Linux agents to perform analysis on NFS mounts.
  • NetApp filer IP address.
  • NetApp filer login credentials, typically root or equivalent.
  • The selected SRM Profiler proxy agent is in the list of the filer's trusted hosts.
  • Windows Security Context: Please ensure that the SRM Profiler proxy agent service is running with the "Log On" rights of a Domain Account that has read access on the shares assigned to it via the 'Assign Shares' page.
  • Note: Operations Manager and DFM are used synonymously in SRM Profiler.

Adding NetApp filer

  • When adding a device, choose NetApp filer from the Choose your Array Type menu. Click OK.
  • Select Agent: Select a SRM Profiler proxy agent to monitor the device.
  • NetApp IP Address: Enter the NetApp filer IP address obtained above.
  • Device Display Name: Enter a descriptive name to identify the device.
  • Active: Uncheck this box if you want to stop collecting data for the device.
  • Cost Per GB: Optional - Enter the cost per gigabyte.
  • Click Next.

Configuring NetApp filer

Provide the appropriate information about the array you want to monitor. If you are unsure about a value, do not change the default value.

File:Success_Center/Reusable_content_-_InfoDev/SRM_Profiler/Add_NetApp_Filer/03000059_312x311.png

  • Status: Select On.
  • User Name: Enter the User Name obtained above.
  • Password: Enter the Password obtained above.
  • Transport Type: Choose HTTP or HTTPS.
  • Use Operations Manager: This field is set to False by default. When the flag is set to True, and a valid DFM Server IP Address is provided, SRM Profiler requests data from the NetApp Operations Manager. If the value is set to false, SRM Profiler queries the NetApp filer directly.

DFM Server and Operations Manager are used synonymously in SRM Profiler.

  • DFM Server IP Address: If you enter True for Use Operations Manager, enter the Operations Manager (DFM) IP address.
  • Advanced Fields: The Operations Manager Port and Data Window Size are advanced configuration fields.
  • Click Save to save the configuration and push it to the SRM Profiler proxy agent to begin monitoring the array.

Additional information

Versions/Models

All

Features

Asset
Storage
Performance

Requires SRM Profiler agent?

No

Prerequisites

  • IP Address of NetApp head/cluster node
  • Define user account on NetApp. Minimum access - a role with access to execute specific API calls. List available upon request. Usually provided just the root login
  • Add the SRM Profiler proxy agent to list of trusted hosts on the NetApp storage system
  • ONTAP 7.3.x: Turn off API XML validation on each NetApp filer (FAQ-132)
  • For ONTAP 8.1:
    • 7 Mode is required
    • Clustered Mode is not supported

Credentials

Account and password are stored in SRM Profiler database and configuration files on SRM Profiler proxy agent using custom encryption

Read/Write Actions

Read Only

Ports Used

  • 80 (HTTP)/443 (HTTPS) on NetApp head/cluster node
  • Any available for CIFS/NFS

Communication

  • See the SRM Profiler Ports section.
  • Can be HTTP/HTTPS between SRM Profiler proxy agent and the NetApp head/cluster node

Data Classification

  • CIFS Shares require a SRM Profiler Windows Agent and domain account to access the shares being analyzed
  • NFS Shares require a SRM Profiler Linux Agent and root access to shares being analyzed.
  • Occurs via SRM Profiler proxy agent

Requires SRM Profiler proxy agent?

Yes – Windows or Linux

 

 

Last modified
11:16, 26 Jun 2017

Tags

Classifications

Public