Eyeglass Isilon Edition Quick Start Guide for R1.3

Eyeglass Isilon Edition Quick Start Guide




Get your Eyeglass Isilon Edition up and running by following these easy steps!



System Requirements:

Isilon OneFS version: please refer to release notes

vSphere 5.0 or higher

 appliance requires:

     4 vCPU

     8 GB RAM (if large number of objects shares, quota,exports > than 15000 use 16G Note requires shutting down the VM and editing RAM and restart)

     80 GB disk

Chrome Browser (preferred)

Eyeglass Port Requirements: Eyeglass-Ports-Requirements


Feature Release Compatibility:


Feature

Source Cluster  Release

Target SyncIQ Cluster Release

 Configuration Replication

7.1.1.0

7.1.1.0

 Configuration Replication

7.1.1.1

7.1.1.1

 Configuration Replication

7.1.1.2

7.1.1.2

  Configuration Replication

 7.1.1.3

 7.1.1.3

  Configuration Replication

 7.1.1.4

 7.1.1.4

  Configuration Replication

7.1.1.5

7.1.1.5

 Configuration Replication

7.2.0.0

7.2.0.0, 7.2.0.1, 7.2.0.2

 Configuration Replication

7.2.0.1

7.2.0.1, 7.2.0.0, 7.2.0.2

Configuration Replication

 7.2.0.2

7.2.0.0, 7.2.0.1, 7.2.0.2



Additional Information for Eyeglass Isilon Edition can be found here:  The Details


  1. Download Eyeglass


Download Eyeglass from Superna web sitehttp://site.superna.net/products/eyeglass-isilon/igls-downloads

01.JPG

Enter your name and email. Link will be sent to email.

02.JPG


03.JPG


Open email from Superna.

04.JPG


Open link from email. Download process starts.

Unpack Superna_Eyeglass_1.3_Isilon_Edition.zip




  1. Deploy the Eyeglass Appliance


Eyeglass is delivered in an  OVF format for easy deployment in your vCenter environment.  Deploy the OVF and then follow the wizard to setup networking for this Linux appliance.  You will need to know:

  • subnet and network required so that appliance will have IP connectivity to the Isilon clusters that it is managing and the users that are using it

  • IP address for the appliance

  • Gateway

  • DNS server



Steps to Deploy the OVF with vSphere (skip these steps if familiar with OVF deployments)


OVF Deployment steps :

Step 1 : Download an ovf file from this address :

Step 2 : Download all the files located at this address:

Step 3 : Login to the Vcenter with appropriate login credentials.

Step 4 : Single click on VMware VSphere client on the Desktop. Login with appropriate login credentials.

Step 5 : Once logged in to VMware Vsphere client, you can see different Menus on the top left of the application. Next, go to the File menu and select Deploy OVF Template.


Eyeglass Isilon Edition Quick Start Guide for R1.1 1.png



Figure 1


Step 6 : Browse to the location of OVF files you downloaded in step 1 and 2. Select OK and then Next.




Eyeglass Isilon Edition Quick Start Guide for R1.1 2.png


Figure 2


Next, You will see the ovf template details. Verify the details and proceed forward by selecting Next. Notice download size to be under allocated disk size limit.

Step 7 : Choose a unique name for the virtual machine and select Inventory location for the deployed template. Once done, select Next.

Step 8 : Select the host/cluster where you want to run the deployed template and then Next.

Step 9 : Select the Resource pool within which you wish to deploy the template.

Step 10 : Select a destination storage for virtual machine files, select Next

Step 11 : Select Disk Format for the datastore you selected in previous step. The Disk Format you will see are:

a)   Thick Provision Lazy Zeroed (best practice): It creates virtual disk in default thick format. The space required for virtual disk is allocated during its creation time. Data remaining on physical device is not erased during creation but can be zeroed out on demand at a later time on first write from virtual machine.

b)   Thick Provision Eager Zeroed : In this provision too the space required for virtual disk is allocated at creation time. Unlike the flat format, the data remaining on physical device is zeroed out when the virtual disk is created. Creating disk in this format takes much longer than other type os disks.

c)    Thin Provision : This provision uses only the datastore space as the disk needs for its initial operations. If the thin disk needs more space later, it can grow to its maximum capacity and occupy all datastore space provisioned to it.

Step 12 : Select the network that the deployed template should use . Select Destination Network, a dropdown list will appear that shows list of available networks.

Step 13 : When done, click Next and you will see your deployment settings as you provisioned it to be. Verify the settings and if everything's ok, hit finish. You will see a Message Box being displayed that says "Deploying [name you gave for your virtual machine]". You can put a checkmark on "close this dialog when completed".

When the deployment process reaches 100 % the message box disappears which means the deployment has been completed.

Now, we should be able to see our virtual machine listed in Vsphere client

After deployment:

Step 1 : Right click on the virtual machine you just created. Select "Power On".  That will power on your VM.

Step 2 : Right click again on your VM and Select "Open Console" to access your machine.

Step 3: Now follow configuration steps to setup IP information on the appliance




Appliance Configuration (Yast)


Note: if you need to update the configuration at any time, ssh to the appliance admin user and then sudo su - to root and use the yast2 command to open the wizard.


The Eyeglass appliance is deployed by default with following user:

   admin/3y3gl4ss       >> can be used to login to the Eyeglass UI


Root user password is unique to the appliance and has no default. Follow the change root user procedure to change root.


! It is highly recommended to reset the default password after the appliance is deployed.






07.JPG

Provide host name. Domain Name is by default “site”.


07-2.JPG


Network screen. Choose Change. Network Interfaces.


07-3.JPG


07-4.JPG


In Network Settings screen open second tab Hostname/DNS.

Type DNS server ip. In this example: 192.168.1.250


IMPORTANT: If you are using hostname for source and target in your SyncIQ policies, the DNS information entered here must be able to resolve this host back to the Cluster IP Address in order for Eyeglass to perform configuration replication.  If the hostname cannot be resolved, Eyeglass will not create the associated configuration replication Job.


07-5.JPG


In Network Settings screen open third tab Routing.

Type default gateway. In this example: 192.168.4.1


07-6.JPG


In Network Settings screen open first tab Overview. Choose Edit.

07-7.JPG


In Network Card Setup screen, choose 2nd tab Address. Type IP Address of new Eyeglass VM and Hostname.

07-8.JPG


Next -  OK - Next




  1. Login to the Eyeglass UI


To login to the Eyeglass web UI, enter the following URL into your browser (Chrome preferred) replacing <Eyeglass IP address> with the real IP address assigned to the appliance:


https://<Eyeglass IP address>


You have 2 options for login authentication:


Local - Select Auth Type “Local” and use the admin user and password configured on the appliance

Default user/password:   admin / 3y3gl4ss


Isilon Cluster - Select Auth Type “Isilon Cluster” and enter IP address of an Isilon that Eyeglass has network connectivity with and a valid user and password configured for that Isilon Cluster and minimum privileges as documented here: http://documentation.superna.net/eyeglass-isilon-edition/tech-notes/eyeglass-authentication.



  1. Install License


Upload the license zip file provided to you by Superna:


NOTE: Do not unzip the license file.  Upload the zip file.


 




IMPORTANT: You will be asked to accept the Eyeglass EULA and Phone Home after selecting the Upload button.  

                     License will not be loaded unless EULA is accepted.






Minimum licenses you will need to get going:


Eyeglass

Isilon Configuration Replication - quantity 2

Issue emails on alarms - Enables email alarm notification

Monitor changes to data and report - Enables change management email report or viewing of change records on the Eyeglass UI


Additional licenses you might like to have:


Allow uploads to Log Insight - Enables Eyeglass logs to be processed by a 3rd party logging service such as VMware LogInsight.

Isilon RPO Reporting - Enables Eyeglass RPO reporting

Enable Directory Migration - Enables feature to copy directory data and configuration from one cluster to another

Issue tweets on Alarms - Enable feature to send alarm notification over secure twitter feed



  1. Provision Isilon Clusters


Important!  Configuration Replication Jobs for shares, exports and nfs alias protected by SyncIQ Policy automatically created and run after successful provisioning in Eyeglass.


Important!  Isilon cluster replication pairs must be running supported OneFS version as documented in the System Requirements / Feature Release Compatibility matrix.

.

From the Eyeglass UI add the Isilon Clusters between which Eyeglass will be replicating the share and export configuration data:







Note:

  • SmartConnect Service must be IP address format.  If SmartConnect not configured, IP address from any node in the Isilon cluster can be used to provision the cluster.

  • Maximum RPO Value is the Recovery Point Objective for the cluster in minutes.  If you are using the RPO feature, this target is used during RPO analysis.

              


Once the Isilon is added, Eyeglass will automatically run an inventory task to discover the Isilon components.  When completed, the discovered inventory can be seen in the Inventory View.





  1. Monitor Configuration Replication Status


Eyeglass Jobs


Once you have configured your Isilon cluster pair and the inventory task has completed, 3 Eyeglass Jobs are automatically created per SyncIQ Policy to replicate between the SyncIQ Policy defined source and target:


    1) Share/Export/nfs alias Configuration Replication Job         

  • associated shares & their configuration

  • associated exports & their configuration


        Eyeglass Configuration Replication Job Name convention:  < Isilon Cluster name >_< SyncIQ Policy name >

      

       Schedule: All share/export configuration replication Jobs execute on a 5 minute schedule.


    2) Zone Replication Job (when associated Zone is NOT the System Zone)

  • associated Zone & it's configuration

      Eyeglass Zone Job Name convention: < Isilon Cluster name >_< SyncIQ Policy name >-< ZONES >


       Schedule:  Zone replication jobs are disabled by default.  They can be run automatically by selecting the Job and then changing status to Enabled from the Jobs / Job Definitions / Select a bulk action menu .


    3) Quota Configuration Replication Job

  • associated quotas & their configuration


      Eyeglass Quota Job Name convention = Isilon Cluster name_SyncIQ Policy name_quotas)

      

      Schedule: Auto-created quota configuration replication Jobs do not run automatically.  They are run on-demand as required.


In order for Eyeglass to be able to execute the configuration replication for the shares/exports/nfs alias/quotas that have been detected for the SyncIQ policies, a few things do have to be in place:

  • directories associated with the shares/exports/quotas must exist on the target Isilon cluster as defined in the SyncIQ policy

  • Zones associated with the shares/exports/quotas must exist on the target Isilon cluster as defined in the SyncIQ policy OR the associated Zone replication Job must be enabled


To view the Eyeglass Jobs created, check out the DR Dashboard window:






Eyeglass Job DR Status


The DR Status provides you with a quick and easy way to assess your Disaster Recovery status.  


DR Status is “OK” when all of the conditions below are met:

  • Your SyncIQ Policy is enabled

  • Your SyncIQ Policy Last Started and Last Success timestamp are identical

  • Your Eyeglass configuration replication Job is enabled

  • Your Eyeglass configuration replication Job Last Run and Last Success timestamp are identical

  • Your Eyeglass configuration replication Job Audit Status is OK


DR Status is “Pending” when either of conditions below are met:

  • Eyeglass configuration replication Job is new and has not been run yet

  • Eyeglass configuration replication Job has been successfully executed but not audited


DR Status is “Error” when any of the conditions below are met:

  • SyncIQ Policy Last Run was not successful

  • Eyeglass configuration replication Job Last Run was not successful

  • Eyeglass configuration replication Job Audit was not successful



DR Status is “Disabled” when either of the conditions below are met:

  • SyncIQ Policy is disabled

  • Eyeglass configuration replication Job is disabled


DR Status is “SyncIQ Running” when all of the conditions below are met:

  • SyncIQ Policy is in "Running" state

  • Your Eyeglass configuration replication Job is enabled

  • Your Eyeglass configuration replication Job Last Run and Last Success timestamp are identical

  • Your Eyeglass configuration replication Job Audit Status is OK


Note:  For the case where a SyncIQ Job has just completed running when Eyeglass checks the status, there may occur a case where the SyncIQ Job Last Success time is not populated when Eyeglass discovery occurs.  In this case the SyncIQ Job will show with Error in the DR Dashboard and empty Last Success time.  In this case, this condition is transient and will be cleared on the next Inventory task.


If any of these conditions is not met, the DR Status for the Job will be “ERROR” or “DISABLED” if disabled.



DR Dashboard Main Window


Column

Description

Notes

Name

Name of the Eyeglass configuration Replication Job

Eyeglass configuration replication Job created automatically for each SyncIQ Policy detected with exactly the same name + prefixed with Isilon Cluster name.

Quota Jobs are suffixed with “quotas”.

Source

The Isilon cluster that is the source configured in the SyncIQ Policy

Eyeglass Job will have same source

Destination

The Isilon cluster that is the target configured in the SyncIQ Policy

Eyeglass Job will have same target

DR Status

A status calculated by Eyeglass based on the SyncIQ Policy status and the Eyeglass Job status

Both the SyncIQ policy status and Eyeglass configuration replication status must be OK in order for overall DR Status to be OK.



Expand any Eyeglass Job to see the details:




DR Dashboard Configuration Replication Job Details

Column

Description

Notes

SyncIQ Policy

All information in the SyncIQ Policy details section comes from the Isilon Cluster itself

If this section is empty then the Job is a custom Eyeglass job not associated with a SyncIQ policy

Job Name

Name of the SyncIQ Policy

Same name on the Isilon cluster

Last Started

Date/time when the last SyncIQ Policy job was started

Information used to determine Overall DR Status

Last Success

Date/time when SyncIQ Policy last run successfully on the Isilon

Information used to determine Overall DR Status

Enabled

Indicates whether the Isilon SyncIQ policy is enabled


Eyeglass Configuration Replication

All information in the Eyeglass Configuration Replication details section comes from Eyeglass


Job Name

Name of the Eyeglass configuration Replication Job

Eyeglass configuration replication Job created automatically for each SyncIQ Policy detected with exactly the same name and prefixed with Isilon Cluster name.

Quota Jobs also suffixed with “quotas”.

Last Run

Date/time when the last Eyeglass configuration replication job was started

Information used to determine Overall DR Status

Last Success

Date/time when Eyeglass configuration replication job was last run successfully

Information used to determine Overall DR Status

Audit Status

Indicates status of the Eyeglass configuration replication job Audit  

After the Eyeglass configuration replication job has completed, Eyeglass performs an audit to compare source and destination configuration and ensure that replicated configurations are identical


Note: Zone configuration replication Job does not have an audit

Enabled

Indicates whether the Eyeglass configuration replication job is enabled




Manage Eyeglass Jobs


To manage your Eyeglass configuration replication Jobs or view the list of associated shares/exports/nfs alias/quotas, select Jobs.



If you see Job Type "AUTO” it means that this is a share/export/nfs alias configuration replication Job that was auto created by Eyeglass based on SyncIQ Policy of the same name.

>> These Jobs are run automatically on a 5 minute schedule.


If you see Job Type “CUSTOM” it means that this is a share/export/nfs alias configuration replication Job that was auto created manually in the Eyeglass web page.  A CUSTOM job was not created based on a SyncIQ Policy.

>> These Jobs are run automatically on a 5 minute schedule.


If you see Job Type “QUOTA” this is the quota configuration replication Job associated with the Eyeglass share/export configuration replication job with the same name.

>> QUOTA Jobs associated with an AUTO share/export configuration replication Job must be run on-demand manually as required.  They are not run automatically.


If you see Job Type "ZONES" this is the zone configuration replication Job associated with the Eyeglass share/export configuration replication job with the same name.

>> ZONES Jobs are disabled by default.  To run this Job you must select it and the Enable it.

   

IMPORTANT: Zone replication will add / update / delete zone information on the target cluster based on the source cluster.  A Zone deleted on the source cluster will also be deleted on the target cluster resulting in OneFS removing all associated shares/exports.


NOTE: When you run a QUOTA Job associated with an AUTO share/export configuration replication Job, the Job is based on the Eyeglass current inventory view.  If you have made a change in OneFS to a quota, the Eyeglass Inventory Task must have run (runs on a 5 minute schedule) prior to running the QUOTA job in order for the change to be applied on the target.


>> QUOTA Jobs associated with a CUSTOM share/export configuration replication Job are run automatically on same replication schedule as the associated CUSTOM share/export replication Job.





To see the shares/exports/nfs alias associated with your Eyeglass configuration replication Job, select the checkbox for your Job and then select the Select a bulk action button.  The Edit Configuration(s) option will take you to the Jobs - Edit Configuration(s) View window where you can expand the tree to see which shares and exports and nfs alias are associated with your job.




Follow the same steps for a Quota configuration replication Job to see which Quotas are associated with the Job.


Follow the same steps for a Zone configuration replication Job to see which Zones are associated with the Job.



To view a Job in progress select Running Jobs from the Jobs window.  In the bottom Job Details pane you will see the steps associated with the Job and the status for each step.




Troubleshooting Eyeglass Jobs


When a problem occurs, for a Job in progress the Running Jobs view will indicate at which step a problem occurred with a link to the information available for the error.




For a completed Job, the Eyeglass system alarm related to the failed Job may contain the extra information you need to troubleshoot the problem









The Details




How does Eyeglass determine uniqueness and equality between shares?

The combination of share name and zone name is the unique value that we use to determine if one share equals another.  This applies to records on the same cluster, as well as comparing shares between two Isilon clusters.


How does Eyeglass determine uniqueness and equality between exports?

The combination of all paths is used to determine if one export equals another.  For example, if the paths on an export are ["/ifs/data1", "/ifs/data2"], any export that exposes this exact combination of paths will be equal.  i.e. another export with ["/ifs/data2", and "/ifs/data1"] will also be considered equal.  Also, when doing replication from a source to a target, if the target has a modified path, we will have to know what that modified path is in order to calculate equality.  For example, a policy that replicates "/ifs/data/path1" to "/ifs/dr/data/path1" a source export with a path of ["/ifs/data/path1/export1"] will match a destination with a path of ["/ifs/dr/data/path1/export1"].  Note: it's possible for an Isilon admin to define two identical exports on the same path, with different user groups.  This configuration will not be supported in Release 1.


How does Eyeglass determine uniqueness and equality between zones?

Zone name is used to determine if one zone equals another.  This applies to records on the same cluster, as well as comparing zones between two Isilon clusters.



What configuration properties are replicated for Shares?

All configuration properties are replicated with the following exceptions:

  • local users & their permissions

  • filesystem users & their permissions


! SID for local and filesystem users are replicated but not mapped to users on the target. This means AD at the target cluster should be setup to resolve SID's using the same AD forest.


What configuration properties are replicated for Exports?

For exports, all configuration information is replicated to target with the following exceptions:

  • export id: Exports on source and target will not have the same export id.


What configuration properties are replicated for Quotas?

For quotas, all configuration information is replicated to target with the following exceptions:

  • Usage Accounting - include Snapshot Data (best practice to not replicate this setting with SyncIQ)

  • Usage Accounting - include Data-Protection Overhead (best practice to not replicate this setting with SyncIQ)


What configuration properties are replicated for Zones?

Following configuration properties are replicated for Zones other than the System zone:

  • Access Zone Name

  • Zone base directory

  • Authentication Providers (name only)

  • User Mapping rules (Isilon 7.1.x.x only)


! Authentication providers / Local providers must exist on the target to resolve the SID' used in share permissions and the filesystem ACL's.


How do I setup Eyeglass for Email Notification?


Enter the information for your email server in the Notification Center / Add Email Address window.



  • To: Enter the email address of the person who is to receive the email address

  • Host name: Enter the host name for your email server

  • Port: Enter the port which should be used for sending email

  • From: Enter the email address of the sender of the email.  Typically this is required to be a valid email address recognized by the email server.

  • Password (optiona): Enter password for From email address if required by your email server.

  • Enable TLS: Select the Enable TLS check box if your email server expects TLS communication.


NOTE: Use the Test Email Setting button to get error codes from the SMTP connection. The "no error" response indicates successful connection.  If error is returned the debug response should be sent to support.superna.net.




What are the Eyeglass System Alarms?


Refer to Eyeglass Isilon Alarm codes for the list of system alarms.



Eyeglass Appliance Networking Wizard


Once you have deployed the Eyeglass appliance, open a console window for the VM in vSphere.  What you will see is a wizard that can be used to setup the networking for the appliance.  To navigate in the wizard use these controls:


Tab - will move you between options

Enter - will select/unselect a checkbox, execute an option (for example, Next)

Arrow - will move between menus


Here are the basic steps to setup a working appliance with static IP address, subnet, gateway and DNS server information.  Additional configuration may be necessary depending on your environment.  If you need to do additional configuation, just remember the basic controls: Tab, Enter, Arrow.


  1. The first thing you see in the wizard is the Superna license agreement.  You must agree to the license to continue. Tab to the Yes, I Agree to the License Agreement and then Enter to select and then Tab to Next and Enter.

  2. In the Hostname and Domain Name window,

    1. Type in the hostname in the Hostname field.

    2. Tab and type in Domain Name.

    3. Tab and Enter to deselect Change Hostname via DHCP.

    4. Tab to Next and Enter to continue to next page.









  1. In the Network Configuration II window that opens Tab to Change and Enter to select.





  1. Select the Network Interfaces… option (default) and then Enter.





  1. In the Network Settings windows that opens you will see Overview selected.  Now Tab to Edit option and Enter.








  1. Now you are on the Network Card Setup window in the Address section.  Here you will configure the IP Address for your appliance, subnet mask and hostname.  Below are steps for Statically assigned IP address.   




  1. Tab until you are at the IP Address field. Type in the IP Address.

  2. Tab to the Subnet Mask field and type in the subnet mask.

  3. Tab to the Hostname field and enter the Hostname again.



  1. Tab to Next and Enter to continue to take you back to the Network Settings window.

  2. Arrow to Hostname/DNS and Enter.





  1. Tab to the Name Server 1 field and type in the IP address for your DNS server.  If you need to add multiple DNS server, use Tab to navigate to Name Server 2 and Name Server 3 and type in additional IP addresses.




  1. Tab back up to Hostname/DNS and the Arrow to Routing.

  2. Type in the Default IPv4 Gateway.





  1. Tab to OK and Enter.  This will take you back to the Network Configuration II window.  Tab to Next and Enter.  This will save your network configuration and take you to the login prompt.







  1. If setup correctly, you should see the IP address of your VM in the vSphere client and you should be able to open the Eyeglass login page with URL http:/<eyeglass appliance Ip address>.