Unsolved

This post is more than 5 years old

6 Posts

2400

April 25th, 2008 03:00

Solaris 9, EMC Powerpath & lpfc.conf settings

Hi all,

We have run a few emcgrabs¿s from servers through the emc heat tool - looks like we have a few warning messages which I'd like your help with.

An example is the automap parameter; we use peristent bindings so AUTOMAP is set to 0 - the report recommends it should be set to 2. We also use Powerpath ver 4.5.1 and the report recommends we use 5.x. It also looks like some of the warnings are performance related.........

Our drivers are from Emulex - lpfc 6.11c and we are using Veritas software (volume mgr and cluster) at release 5.1.

Anyone advise if these mean that our configuration is supported or not?

Thanks in advance...
Divs

-------------------------------------------------------------------------------------------
NOTICE : Version of EMC PowerPath driver is 4.5.0_b169.
WARNING : The version of EMC PowerPath 4.5.0_b169 is not the latest version.
Upgrade to PowerPath package version 5.1.1_b007.

WARNING : ssd:ssd_max_throttle is not set.
WARNING : fcp:ssfcp_enable_auto_configuration not set.
WARNING : ssd:ssd_io_time not set for PowerPath and/or DMP.
WARNING : log-verbose set incorrectly to 0x0. Correct value is 0x10.
WARNING : lun-queue-depth set incorrectly to 30. Correct value is 20.
WARNING : tgt-queue-depth set incorrectly to 0. Correct value is 512.
WARNING : no-device-delay set incorrectly to 1. Correct value is 0 seconds - implies no delay to fail back an I/O when communication is lost to the device.
WARNING : Could not determine if scan-down setting is correct for topology of 0.
WARNING : linkdown-tmo set incorrectly to 30. Correct value is 60.
WARNING : nodev-tmo set incorrectly to 30. Correct value is 60 - hold all I/O errors on devices that disappear until timer expires.
WARNING : num-iocbs set incorrectly to 256. Correct value is 2048.
WARNING : num-bufs set incorrectly to 128. Correct value is 1024.
WARNING : This system appears to have been setup for persistent bindings by setting "fcp-bind" but the "automap" value is incorrectly set. Latest Emulex documentation now state that this value should be set to 2.

WARNING : Variable rscn-adisc is not set in file lpfc.conf.
WARNING : Variable check-cond-err is not set in file lpfc.conf.
WARNING : Variable dqfull-throttle is not set in file lpfc.conf.
WARNING : Variable fcpfabric-tmo is not set in file lpfc.conf.
WARNING : Variable fcp-on is not set in file lpfc.conf.
WARNING : Variable rscn-ns-delay is not set in file lpfc.conf.
WARNING : Variable zone-rscn is not set in file lpfc.conf.

26 Posts

April 25th, 2008 11:00

Two things to check...
1. Run your configuration thru PowerLink ELab tool. This will provide information which version of PowerPath and other software are supported, along with required patches.
2. For the Emulex setting need to download the "EMC Fibre Channel with
Emulex Host Bus Adapters in the Solaris Environment " Manual from Emulex and check the following:
Table 2-1 Emulex Driver Configuration File (lpfc.conf) Variables and
Recommended Settings (table_value)

Az2Mn

117 Posts

April 27th, 2008 16:00

It is generally a good idea to upgrade to the latest supported version of PowerPath. At the very least, you must run a supported version. Support for PowerPath 4.5 will discontinue by the end of 2008.

If you are using Emulex driver (i.e. not Sun's Leadville), you can skip all ssd* settings, but pay attention to sd* settings.

Incorrect timeout settings (such as linkdown-tmo) may lead to a problem during failover and should be fixed

Unless somebody analyzed performance on this host and came to a conclusion that some settings need to be changed, you should stick to EMC-recommended values.

I believe EMC/Emulex/Sun recommend switching to Leadville drivers. You can download the latest EMC-supported version from EMC portion of the Emulex web site - http://www.emulex.com/emc/support/index.jsp

For more information, please check Host Connectivity Guide for Solaris; always a good idea to check EMC Support Matrix (via eLab Interoperability Navigator) once a month.

6 Posts

April 28th, 2008 07:00

Thank you both.

Cheers,
Divs

2 Intern

 • 

131 Posts

April 28th, 2008 09:00

I personally would leave automap=0 (ie disabled). This prevents unwanted LUNs from being mapped if there are any zoning errors, thereby keeping the Solaris disk environment tidy.

The various timeout parameters must set correctly to be supported. In addition, PowerPath may not work correctly if the underlying drivers are not properly configured.

Marc

6 Posts

April 30th, 2008 08:00

I agree with you Marc, automap should be 0; however, we're being told by Emulex & EMC to set automap to 1 for a supported configuration.... this is only because recently, everytime we have had a Fabric RSCN on the SAN, disks on our Symmetrix DMX-2000 arrays go from being mapped to 'in transition' while the disks on our Symmetrix 8530 arrays stay mapped!!

This happens on servers using disks from both arrays..

Servers with leadville drivers are ok.

We have a large estate of servers using lpfc 6.11c so I'd better start working things out.

Thanks again,
Divya
No Events found!

Top