Showing posts with label vsphere. Show all posts
Showing posts with label vsphere. Show all posts

Friday, February 7, 2014

NetApp Workflow Automation for VMware - Setup & Configuration

Welcome: To stay updated with all my Blog posts follow me on Twitter @arunpande !


In my previous blog post Monitoring NetApp Clustered Data ONTAP using Unified Manager 6.0 I have discussed the steps required to setup OnCommand Unified Manager and integrate it with LDAP. In this blog post I will discuss the setups required to install & configure NetApp OnCommand Workflow Automation (WFA). WFA is used to automate various storage provisioning & management tasks using role based user access. It can be further integrated with vCenter Orchestrator to provide end to end automation for NetApp & vSphere related tasks.
Install OnCommand Workflow Automation
Download WFA 2.1 from NetApp Support Site. Note that you need to have valid credentials to download this software. This installer is available as a 200 MB WFA-x64-V2.1.0.70.32-B2178337.exe file that can be installed on 64 –bit Windows OS. I have installed WFA on a Windows 2008 R2 virtual machine.


Launch the installer and click Next to continue.
 
Accept the license agreement and click Next to continue or change them if you are using custom HTTP and HTTPS ports.
 
Enter the username and password. NOTE: This username/password would be used to login to WFA using the Web browser.




Change the destination location if required else click Next to continue.



Review the information in this screen and click Next to continue.




This completes the installation of WFA.
Launch WFA using https://IPorFQDN of the server where you installed WFA. Ensure that the latest Adobe Flash Player is installed.
 
Login using the credentials provided during the installation
 
Setup OnCommand Workflow Automation
Launch the Setup Wizard
 
Select the version of OnCommand Unified Manager that has been installed. If you have not installed OnCommand Unified Manager (UM), you would have to pause the setup and install UM first. In my setup I chose UM 6.0 since I already have it installed.
 

For WFA to communicate with UM, you have to create a user account in UM.
 
If you have not created the user account in UM, login to UM and create the following 
database user account.
 
Enter the database user credentials for UM.



You will receive the following message when WFA is successfully connected to UM.
 
Enter the admin credentials of the cluster if you are using NetApp Clustered Data ONTAP.
 
Once the NetApp Storage is added successfully, you will receive the message. I strongly recommend that you visit the Workflow Automation community to understand more about this product.
 


Add additional Data Source
During the above setup, UM is added as a Data Source for WFA. If you want to automate vSphere Infrastructure tasks then you should also add the vCenter Server as a Data Source in WFA.
To add vCenter Server, navigate of Execution > Data Sources > Click to add a Data Source.
Enter the following information
  • Name: Descriptive name for the vCenter Server instance.
  • Data Source Type: Select VMware vCenter
  • Home Name: Enter the IP or FQDN
  • Port: Use the default port
  • User name & Password: Create a user name and assign it Read Only permissions for your vCenter Server. Enter the user name and password here.
IMPORTANT: You must install VMware PowerCLI on the server where WFA is installed; else the following error would be reported while adding vCenter Server as data source.
Unable to load VMware Poweshell Snapin
The data sources have now been added successfully.
 

Configure LDAP integration with OnCommand Workflow Automation
WFA supports LDAP integration to provide role based access. In this demo I am using Windows 2008 R2 Active Directory and will integrate my AD users with WFA.
To configure LDAP, navigate to Administration > WFA Configuration > LDAP




IMPORTANT: Do not change the attribute values for the following:
  • User name attribute
  • Group membership attribute
  • Mail attribute
  • Distinguished name attribute


You will find the above attributes in the Attribute Editor tab in user properties for all the users created in the AD.




Enter the LDAP Server in the following format if you are using default port 389
ldap://ip of fqdn of ad


If you are using a custom port change append :port# to the above address.


Provide the Group names in AD for WFA admins Groups. Now login using the AD user using DOMAIN\USER format.


Once you have successfully logged into WFA, navigate to Execution > Users and you will find that the AD user is now detected with LDAP value set to true.




With this you have completed the install and setup of WFA. You can now select the available workflows in Portal and start exploring them.


Friday, January 24, 2014

Perform Storage Maintenance on NetApp Clustered Data ONTAP with ZERO downtime

Welcome: To stay updated with all my Blog posts follow me on Twitter @arunpande !


I am writing this blog to share my experience about scheduling a maintenance activity on NetApp FAS3270 with Clustered DATA ONTAP. I had to reboot one node which was hosting 500 virtual machines across eight ESXi hosts.                                                                                                                                                                                                                                                          


When a storage administrator has to schedule a maintenance activity like firmware/hardware upgrade which requires a reboot he has the following options:



Work hard with Traditional Storage
  • Spend several minutes trying to shutdown the VMs on all eight ESXi hosts.
  • Make sure all VMs are powered off and there is no active I/O to avoid any application specific issues.
  • Reboot the Controller.
  • Again spend several hours trying to power on all the 500 virtual machines.
  • Spend hours working on your weekend trying to complete this maintenance


Work Smart with Clustered Data ONTAP
  • Use Clustered Data ONTAP with LIF migration and SFO (Storage Failover).
  • Perform takeover/give back of the controller.
  • No changes required in the vSphere Infrastrucutre
  • Migrate the LIFs back to the source node
  • Complete the maintenance within 10-15 minutes during production hours.


This is the procedure that I followed to perform this activity

 


I have the following cluster configured with 515 VMs


IMPORTANT: You don’t have to make any changes in your vSphere Infrastructure. You do NOT need any downtime for VMs.


The following activity has to be performed on your NetApp Storage


Make sure that the cluster is healthy.
f3270::> cluster show
Node                  Health  Eligibility
--------------------- ------- ------------
lab-filer1            true    true
lab-filer2            true    true
lab-filer3            true    true
lab-filer4            true    true
4 entries were displayed.


Check the Storage Failover settings
lab-f3270::> storage failover show
                             Takeover
Node           Partner        Possible State Description
-------------- -------------- -------- -------------------------------------
lab-filer1     lab-filer2     true     Connected to lab-filer2
lab-filer2     lab-filer1     true     Connected to lab-filer1
lab-filer3     lab-filer4     true     Connected to lab-filer4
lab-filer4     lab-filer3     true     Connected to lab-filer3
4 entries were displayed.


Enable Advanced mode
lab-f3270::> set adv


Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y


Check how many lifs are currently on this node
lab-f3270::*> network interface show -data-protocol nfs|iscsi|fcp -curr-node lab-filer4
           Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Lab_Vserver
           nfs_lif04    up/up    192.168.40.244/24  lab-filer4    i0a-400 true


Make sure that the LIF is migrated to another node in the cluster
lab-f3270::*> network interface migrate-all -node lab-filer4


lab-f3270::*> network interface show -data-protocol nfs|iscsi|fcp -curr-node lab-filer4
There are no entries matching your query.


IMPORTANT: Create LIF Failover groups to perform seamless migration of the LIFs during link failure and takeover. In this blog post I have shared the steps to perform link migration in case you have not configured Failover groups. I encourage that you configure failover groups, refer to the Clustered Data ONTAP ® 8.2 High-Availability Configuration Guide for detailed information.


Initiate the takeover of the controller to reboot it.
lab-f3270::*> storage failover takeover -ofnode lab-filer4


The controller now reboots
lab-filer4% Waiting for PIDS: /usr/sbin/ypbind 722.
Waiting for PIDS: /usr/sbin/rpcbind 688.
Terminated
.
Uptime: 112d2h54m45s
Top Shutdown Times (ms): {if_reset=1161, shutdown_wafl=223(multivol=0, sfsr=0, abort_scan=0, snapshot=0, start=62, sync1=77, sync2=4, mark_fs=80), wafl_sync_tagged=148, shutdown_raid=28, iscsimgt_notify_shutdown_appliance=22, shutdown_fm=15}
Shutdown duration (ms): {CIFS=2607, NFS=2607, ISCSI=2585, FCP=2585}
HALT:  HA partner has taken over (ic) on Fri Jan 24 04:08:38 EST 2014


System rebooting...


Once the reboot is complete and the storage is ready for give back, initiate the give back for this controller
lab-f3270::*> storage failover giveback -ofnode lab-filer4


Info: Run the storage failover show-giveback command to check giveback status.


Revert the lif back to its home node
lab-f3270::*> network interface revert -vserver Lab_Vserver -lif nfs_lif04


lab-f3270::*> network interface show -data-protocol nfs|iscsi|fcp -curr-node lab-filer4
           Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Lab_Vserver
           nfs_lif04    up/up    192.168.40.244/24  lab-filer4    i0a-400 true


Make sure that the cluster is healthy again. 

Within 10-15 minutes and the entire maintenance activity of rebooting the controller and making sure that its online was complete.


IMPORTANT: It’s important that you setup the cluster as per best practices, refer to Clustered Data ONTAP 8.2 Documentation for more information.