HP 3PAR Solaris Implementation Guide

NOTE: This section does not apply to Solaris 11.
There is a delay of fp_offline_ticker before fp tells fcp about the link outage (default 90
seconds). There is a further delay of fcp_offline_delay before fcp offlines LUNs (default 20
seconds). You can change these setting by making the necessary edits to the /kernel/drv/
fcp.conf and /kernel/drv/fp.conf files.
For example, you could edit the fcp.conf file with the following fcp_offline_delay setting
to change the timer to 10 seconds:
fcp_offline_delay=10;
Setting this value outside the range of 10 to 60 seconds will log a warning message to the /var/
adm/messages file.
Also edit the fp.conf file with the following fp_offline_ticker setting to change the timer
to 50:
fp_offline_ticker=50;
Setting this value outside the range of 10 to 90 seconds will log a warning message into the /var/
adm/messages file.
In the example above, the settings will reduce the timer by a total of (20 – 10) + (90 – 50) = 50
seconds.
Starting from Solaris StorageTek™ SAN 4.4.11 and Solaris™ 10 U3, these parameters are made
tuneables. They can be tuned by modifying the respective driver.conf file. The range of allowed
values has been chosen considering the FC standards limits. Both can be tuned down - but not
below 10 seconds (the driver code will either enforce a minimum value of 10 seconds, or issue a
warning at boot time, or both).
WARNING! Tuning these parameters may cause adverse affect on the system. If you are optimizing
your storage configuration for stability, we recommend staying with the default values for these
tuneables. Any changes to these tuneables are made at your risk, and could have unexpected
consequences (e.g., fatal I/O errors when attempting to perform online firmware upgrades to
attached devices, or during ISL or other SAN reconfigurations). Changes could also affect system
performance due to excessive path failover events in the presence of minor intermittent faults etc.
You may need to test any changes for your standard config/environment and specific tests, and
determine the best 'tradeoff' between a quicker fail over and resilience to transient failures.
See the following website for the implications of changes to your host server.
Oracle
CAUTION: It is not presently possible on Solaris to lower I/O stalls on iSCSI attached array paths
due to a Solaris related bug (Bug ID: 6497777). Until a fix is available in Solaris 10 update 9,
the connection timeout is fixed at 180 seconds and cannot be modified.
38 Configuring the Host for a Fibre Channel Connection