MPIO Failed Paths Disappear


hi,

i testing new storage server on our san , having trouble mpio.  the storage server running comstar targeting software, luns being presented on fc.  after configuring mpio claim devices present server 2012 server, can see disks appropriate number of paths in round-robin active/active mode.  

the problem seeing--well, not sure unexpected--is when remove path disks, path removed mpio device.  if remove paths, disk disappears.  the failed paths not come pack until restart (initiator/server 2012) server.    

i think record of path persist in "failed" state until retry successful, in case path brought online.  

is there wrong mpio configuration?  or harware/storage server-side problem (details below)?  comstar, far can find, not have dsm.  

storage server:
- openindiana (current version)
- qlogic hbas on server/target
- emulex hbas on client/initiator
- hp brocade fc switches
- comstar targeting software 

my mpio settings (updated original posting):

pathverificationstate     : enabled
pathverificationperiod    : 5
pdoremoveperiod           : 1500
retrycount                : 300
retryinterval             : 5
usecustompathrecoverytime : disabled
custompathrecoverytime    : 40
disktimeoutvalue          : 60

thanks!


matthew


hi ,

i don't have hardware local test. please check following information?

1. if choose other loadbalancepolicy "fail on only" etc... same issue occur? 

2. if use same hardware on windows server 2008 r2, same issue occur?

3. hardware compatible windows server 2012 , latest?

thanks.

besides, " if remove paths, disk disappears" not clear this. if remove paths, there no path , disk may disappear. please detail steps? thanks. 


please remember click “mark answer” on post helps you, , click “unmark answer” if marked post not answer question. can beneficial other community members reading thread.




Windows Server  >  File Services and Storage



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client