UNSOLVED
Path failover using powerpath5.2 sp1
I have 1 windows 2k3 Cluster ( Microsoft cluster ) with 2 nodes and with 2 HBA's each which see 17 storage devices from DMX -4 , zoned with 2 FA's in 2 diff fabric . 8c:1 and 9c:0 ..
Yesterday we had an an issue where our cisco 9513 switch module 1 failed , due to which servers were not showing as logged in to FAs. 9c:0 , so one path went down .. Though we have powerpath the other path didnt become active and the server lost all the storage disks..
i have check the powemt check_registration output and output is showing powerpath license applied with all capacbilties .
i have checked the powermt dispay dev=all output which is showing the policy set as SymmOpt for all the devices , i am wondering why the powerpath didnt do failover to the other available path thru FA 8c:1 ... i had to clear the dead paths thru powermt check and then reboot the server to see the devices in disk management and now those devices are getting used ..
Do i need to any other changes in powerpath config on the servers ?
download and run PowerPath Configuration Checker, see if it finds anything.
Question: What does PowerPath Configuration Checker (PPCC) do? Environment: EMC SW: PowerPath Environment: EMC SW: PowerPath Configuration Checker (PPCC) Fix: PPCC can help with:
- Planning configurations on hosts on which PowerPath is not currently installed. Using the -V x.x.x option, PPCC will validate the host configuration, noting software that may need to be upgraded, modified, or installed to support that particular PowerPath version.
- Upgrading or downgrading a host on which some version of PowerPath is installed. PPCC can identify components of the host configuration that may need to be changed when a different PowerPath version will be used.
- Diagnosing configuration problems or validating configurations on a host on which PowerPath has been installed or upgraded.
Notes: PPCC can currently check the following variables: - OS version, service packs, patches
- Machine architecture
- PowerPath version
- PowerPath efix
- PowerPath license and license policy
- I/O timeout
- EOL and EOSL date
- HBA model, driver, firmware
- Kernel version (Linux only)
- Symmetrix microcode, model, SYMAPI version
- CLARiiON model, API, failover mode, FLARE version, HBA
- Third party array support
- Upgrade path
- Veritas DMP version
- powermt custom file
SKT136306
31 Posts
114
0
Posted January 8th, 2010 22:00
at HBA level there settings like below and you may compare with a workign machine with a similar setup.I am not a Windows guy, but in UNIX there are time out settigng at the LUN/device level too.
Link donw time out
Port Down retry
Login retry count