Skip to main content

VIO - Storage Configuration

Setting MPIO parameters at various levels:


1.  At the physical adapter (FC) level on VIOS:
For all fscsi devices on VIOS, set dyntrk=yes and fc_err_recvo=fast_fail
fc_err_recov will fila any I/Os immediately if the adapter detects a link event, such as a lost link between a storage device and a switch.  The 'fast_fail' setting is recommended only for a dual VIOS configuraiton.  

dyntrk attribute allows the VIOS to tolerate cabling changes in the SAN.  

*Both VIOS need to be restarted for these changes to take effect. 


2.  To all the disks on VIOS:

alogrithm=load_balance (round robin - per best practices guide)
reserve_policy=no_reserve
hcheck_mode=nonactive
hcheck_interval=60

3.  At the VIO Client level:
vscsi devices in the client (virtual adapter)
vscsi_path_to=30

All the devices in the client: 
algorithm=failover
reserve_policy=no_reserve
hcheck_mode=nonactive - Specifying 'nonactive means that healthcheck commands are sent down paths that have no active I/O, including paths with state of failed. 
hcheck_interval=60


  


Popular posts from this blog

Commands to restart RMC connection (t...

Commands to restart RMC connection (to HMC from LPAR) It has become very common with the IBM HMC to LPAR (logical/micro partition) communication to drop for unknown reasons.  Most of the time this is not a problem unless there is a need to do a dynamic logical partition operation (or DLAPR operation to add/remove resources on the fly).  This will become evident during the DLPAR operation when HMC complains about having no RMC connection to LPAR in operation.  When this happens run the following commands on the LPAR in question before reattemping the operation.  The DLPAR operation will still work with out this connection, but the LPAR needs a restart to see the change in the resources.  Restart the RMC connection on the LPAR: # /usr/sbin/rsct/install/bin/recfgct # /usr/sbin/rsct/bin/rmcctrl -p Verify the connection by running: lsrsrc IBM.ManagementServer This will show the HMC IP/hostname and the LPAR information.

Network throughput test between 2 AIX servers

The easiest way to test throughput between 2 AIX servers is to do a FTP test, generating data transfer with ‘dd’ command.  This will provide the throughput/speed for the specified amount of data transfer: #src-system> ftp dst-system … … ftp>  put "|dd if=/dev/zero bs=32k count=10000" /dev/null 200 PORT command successful. 150 Opening data connection for /dev/null. 10000+0 records in 10000+0 records out 226 Transfer complete. 327680000 bytes sent in 1.406 seconds (2.277e+05 Kbytes/s) local: |dd if=/dev/zero bs=32k count=10000 remote: /dev/null ftp>bye   This is the same test IBM recommends in the redbook and also during a support call

HP-UX tape configuration

Here are few commands to configure tape drives in HP-UX 1.  Scan for new devices: # ioscan –fnC tape 2.  List tape drives currently recognized by the OS (without performing an actual hardware scan) # ioscan –fnkC tape 3.  remove all the special files used by the tape drives # rmsf  /dev/rmt/* 4.  Recreate the specil files for the tape drives # insf –C tape –e 5.  Remove a tape drive (that has a NO_HW state) # rmsf –H 0/7/1/0.1.24.255.5.5.0 Find the WWN for the HBAs: # ioscan –fnkC fc # fcmsutil /dev/fcd0 Find the WWN for the tape drives connected to the HBA: # fcmsutil /dev/fcd0 get remote all   **These are just a handful of commands to deal with the tape drives.  Not to be used as a procedure