XtremIO: Host Validation Script handling for NDU preparation

           

   Article Number:     536974                                   Article Version: 2     Article Type:    How To 
   

 


Product:

 

XtremIO Family,XtremIO X1,XtremIO HW Gen2 400GB,XtremIO HW Gen2 400GB Encrypt Capbl,XtremIO HW Gen2 400GB Encrypt Disable,XtremIO HW Gen2 400GB Exp Encrypt Disable,XtremIO HW Gen2 400GB Expandable,XtremIO HW Gen2 800GB Encrypt Capbl

 

Instructions:

 

 

The Host Configuration Validation Script (sometimes shortened to Host Validation Script, or HVS) is provided as a courtesy by Dell EMC, and is meant to make review of host configuration easier. In regards to an NDU, its primary most important uses are to look at host HBA timeouts and multipathing configuration. There are other important items that may be checked, though these will vary depending on the host type.    
   
    The script is a companion to the XtremIO Host Configuration Guide, and as such covers items ranging from important (preventing Data Unavailability) to minor (performance fine-tuning)   
   
    Note that our Support teams cannot perform configuration changes on hosts. If you need this kind of assistance, please reach out to your Dell EMC local team (performing host configuration may require paid services).   
   
    As a reminder, the scripts and procedures for running them can be found in the following articles:   
   
    XtremIO: Host Configuration Validation Script for ESX   
    XtremIO: Host Configuration Validation Script for Linux   
    XtremIO: Host Configuration Validation Script for Windows   
   
    There are a few items to remember when using these scripts in preparation for an NDU:   

         
  •         The scripts are only intended to be run on the host type they were designed for. As of this writing, only ESX, Linux, and Windows have a HVS available. Any other hosts will require manual review        
               
    •             As a guideline, if a host type has its own section in the XtremIO Host Configuration Guide, it is considered its own host type for the purpose of configuration.         
    •        
                  
  •    
   
         
  •         If the article has a prerequisites section, these must be applied/confirmed prior to running the script.     
  •    
   
         
  •         [Applies only to ESX] The script is, by default, designed to look at configuration for an XtremIO-only SAN. If the SAN environment contains multiple storage types that include non-XtremIO arrays, the script MUST use a parameter that validates against multi-storage environments. If this parameter is not used in an environment with multiple storage types, some of the output/recommendations will not be accurate and may provide improper recommendations. Consult the ESX validation script document in the link above for the proper parameter to use.     
  •    
   
         
  •         As a rule of thumb, any items flagged with PROBLEM should be fixed prior to an NDU to avoid Data Unavailability (see Notes section below for any specific clarifications). Any items flagged with WARNING or NOTICE will typically be items advising performance-tuning or efficiency recommendations; these are not critical to fix prior to an NDU, but are useful to resolve nonetheless. Some notice items may mention an item that could not be checked.        
               
    •             If there are any concerns about the applicability of the configuration requested by WARNING or NOTICE items to your SAN, this should be presented to account or local team, as there may be rare situations where a different configuration is deemed preferable for a specific SAN environment if validated beforehand (note: Support does not consult on different configuration, and will only recommend applying what is mentioned by the HVS script or the Host Configuration Guide).         
    •        
                  
  •    
                                                                                                                             

 

 

Notes:

 

 

If there are any questions about HVS output that is not present here, check the XtremIO Host Configuration Guide first to see if it is answered there.   
   
   
    Clarifications   
   
    Here are some examples of items that may appear, but where the recommendation may not be clear. Note: this is NOT an exhaustive list, as most issues mentioned in the script will state what the current setting is and advise on the recommended change.   
   
   
    PROBLEM: No XtremIO disks found   
   
    This is typically the result of XtremIO Volumes being deleted on the storage side, but the host not being updated to reflect these changes. Since the HVS is run on the host, it tries to find the volumes but they no longer exist on the array. This failure will not cause problems during an NDU, if verified as stated above.   
   
   
    PROBLEM: XtremIO datastores are set with "Public" locking mode and will not work with VAAI   
   
    If this problem is seen, it MUST be resolved! See KB 485682 for more details:  Increased risk of a system outage when VAAI and ATS are not enabled on hosts connected to XtremIO datastores   
   
   
    NOTICE: It appears the initial install of the cluster was pre XtremIO XIOS 4.X - therefore it is not possible to validate at least one live path exists to both Storage Controllers of the same XBrick   
   
    This means the script was unable to check host path redundancy to the storage. If this is seen, path redundancy will need to be manually checked on the host side.