When preparing the host to work with (infinihost settings check) InfiniBox, some additional software packages are required to be installed and some configuration must be applied.

The host readiness tool, infinihost, checks for the existence and correctness of the following items.

Software packages

General checks:

FC connectivity

• no mixed ports on multiple storage arrays - 3670213 Host initiator ports exclusivity test
• dual initiator to the InfiniBox - 3670216 Host should be connected through more than one initiator port
• multiple nodes connectivity - 3670219 Host should be connected to more than one Node of each InfiniBox
• not passing maximum paths - 13929579 Host has too many connected paths to InfiniBox
• large amount of volumes per host - 14942510 Host sees too many block devices

FC HBA

• verify that the HBA is supported within our support matrix (see: INFINIDAT software compatibility).

Devices

• volumes that don't have a multipath device - 1704801 Multipath device doesn't exist for volume
• all reported INFINIDAT LUNs have a block device - 22157347 Missing block devices
• path count for all INFINIDAT MPIO devices doesn't exceed - 22157362 Missing paths for MPIO devices

Linux checks:

multipath-tools

• multipathd is loaded at boot - 1704312 The multipath service must be loaded at boot time
• multipath kernel module is loaded - 1704319 The multipath kernel module must be loaded
• multipathd service is up - 1704315 The multipath-tools init service must be running
• configure multipath defaults  - 1704343 Recommended default attributes for multipath.conf
• configure multipath with INFINIDAT devices - 1704346 Recommended device settings for the multipath configuration file

• configure multipath blacklists - 1704349 Blacklists in multipath configuration file

• configure multipath blacklist of local devices - 7667992 Local blacklist in multipath configuration

FC HBA

• modify the driver parameters to take effect on a normal driver load and in initrd - 3670125 The HBA driver is not configured according to the best practices

iSCSI

• iSCSI initiator software is installed - 22155590 Installing the iSCSI Initiator on Linux
• node.startup = automatic in file /etc/iscsi/iscsid.conf - Linux iSCSI configuration should be set to automatic login
• node.leading_login = No in file /etc/iscsi/iscsid.conf - Linux iSCSI should not use leading login
• node.session.queue_depth = 128 in file /etc/iscsi/iscsid.conf - Linux iSCSI configuration should set queue depth to 128
  
• iscsid is running - Linux: The iSCSI service must be running
• iscsid automatically loads on boot - Linux: The iSCSI service must be loaded at boot time
• iSCSI name of the host is a valid IQN - 37430551 iSCSI name must be a valid IQN

Windows checks:

• set san policy to OnlineAll - 6360527 Settings Windows SAN Policy to Online
• disable auto-mount - 6360529 Windows Auto-mounter
• set windows disk timeout - 6360531 Windows Disk Timeout
• install windows MPIO feature - 6360514 Powertools requires Multipath IO Feature to be installed on Windows hosts
• configure MPIO claiming rule for NFINIDAT devices - 6360521 Claiming rules for Infinidat devices on Windows MPIO
• MPIO tuning - 6360525 Windows MPIO Tunable settings
• MPIO load balancing policies for NFINIDAT devices - 6360523 Load balancing policy for Infinidat devices on Windows MPIO
• iSCSI - set the iSCSI service to autostart  - 36274305 Windows iSCSI service should be configured to auto start
• iSCSI - start the iSCSI service - 36274299 Windows iSCSI service should be running
• iSCSI - set the iSCSI name of the host to a string that is a valid IQN format - 37430551 iSCSI name must be a valid IQN
  
  

Solaris checks:

• FC HBA driver attributes - 22155306 Solaris: HBA driver configuration best practices
• SCSI related kernel tunables - 22155306 Solaris: HBA driver configuration best practices
• SCSI generic is installed and loaded - 22155398 Solaris: Load SCSI generic module
• multipath is enabled - 22155391 Solaris multipath is enabled
  
  

AIX checks:

• FC HBA driver attributes - 24549072 Configuring the FC HBA driver according to the best practices
• ODM attributes - 24544210 AIX: Configuring the ODM
• message catalog is installed - 24544214 AIX: Installing the catalog file