Child pages
  • NetApp Storage Configuration
Skip to end of metadata
Go to start of metadata

Admin Guide 3. Storage: NetApp

Supported NetApp Configurations

Abiquo supports NetApp storage in two different configurations:

  1. Physical vFiler 0
  2. vFilers

Physical vFiler 0

Using the NetApp device directly with vfiler0 only means you can work directly with the NetApp. This gives access to the aggregates in vFiler0, which are automatically detected by Abiquo and assigned to Abiquo storage pools.

vFilers

Using multiple vFilers on NetApp storage. You can add each vFiler as a storage device with the following constraints:

  • you can only have one username and password per vFiler in Abiquo
  • each vFiler must have a separate management IP and it will also have its own separate Service IP

Abiquo will detect the data volumes created in the vFiler by the Storage Administrator and assign each one to a separate Abiquo storage pool. Each storage pool can be assigned to tier (see  Storage Pool Allocation). Abiquo will create virtual storage volumes as LUNs on the data volumes.

Configuration Diagrams

The following diagram shows the two NetApp configurations supported by Abiquo:

See also VMware ESX and ESXi Cloud Node Configuration.

NetApp Authorization Credentials

The NetApp Authorization Credentials are now added in the GUI when you add the NetApp storage device. Abiquo supports one user and password per vFiler storage device. As of version 2.0, you cannot add the NetApp user and password to the abiquo.properties file.

Enable HTTP for port 80 in the filers for management

To enable HTTP, enter the following commands in the NetApp CLI.

options httpd.enable on
options httpd.admin.enable on

Alternatively, you can enable HTTP in the Filer (the web interface of the NetApp).
Go to HTTP and set the option HTTP Enabled to Yes.

Enable the iSCSI initiator

Use the following command in the NetApp CLI.

options iscsi.enable on

Alternatively, you can enable iSCSI in the Filer.
Go to LUNs then Enable/disable and set the option Enable iSCSI to Enable.

NetApp Configuration in ESX and ESXi

Enable iSCSI on the ESX/ESXi host

Log into the VMware Infrastructure Client

Follow the instructions in the order shown in the picture above:

  1. Select your Host or Cluster (depending on your configuration);
  2. Click on the "Configuration" tab;
  3. Click on "Storage Adapters" on the left;
  4. Choose the iSCSI Software Adapter;
  5. Click on "Properties".

Make sure the adapter is enabled.
If not, click "Configure", then click OK.

Enter a name and alias or leave the default ones.
This is going to be your ESX(i) host IQN.
Tick the checkbox to enable the adapter.

Reconfigure NetApp Initiator Groups

Only for Previously Configured NetApp Devices

This section only applies to NetApp devices that have already been configured outside of Abiquo.

If you have previously used the NetApp storage with a hypervisor host outside of Abiquo, the host's IQN may have been added to another initiator group, so Abiquo will not be able to automatically add it to "abiGroup". You must reconfigure the NetApp before you can use the NetApp with Abiquo. The hypervisor IQNs must all be in the same group. If this group is not called abiGroup, then you must set group name in the Abiquo properties files.

  1. Open your browser and access the Netapp filer manager screen (http://<Filer_IP>/na_admin/ and click on FilerView).
  2. Navigate to LUNS > Initiator groups. Check that all the hypervisor IQNs are in the same initiator group. If some hypervisors do not appear here, you do not need to add them.
  3. If the initiator group is not named "abiGroup", do these steps:
    1. Using an ssh terminal, access your Abiquo Remote Services Server and edit the file /opt/abiquo/config/abiquo.properties.
    2. Add the following line or modify it your desired initiator group name:

      Add to /opt/abiquo/config/abiquo.properties
      abiquo.storagemanager.netapp.initiatorGroupName = "myGroup"
      
    3. Then restart the tomcat service using:

      # service abiquo-tomcat restart
      

 

  • No labels