HPE Nimble Storage Solution Specialists

NIMBLE_PSP_DIRECTED vs "iops=1"

 
rmay_bk
Valued Contributor

NIMBLE_PSP_DIRECTED vs "iops=1"

The NIMBLE_PSP_DIRECTED SATP rule automatically created by NCM does not appear to have any PSP options set.  Is "iops=1" implied with this rule or should I explicitly specify it?  I'm trying to get this rule into my host profiles so that future host remediations don't back out anything that might have been set by NCM.

Thanks! 

 

Capture.PNG

4 REPLIES 4
rmay_bk
Valued Contributor

Re: NIMBLE_PSP_DIRECTED vs "iops=1"

On the other hand, I've just spotted a five year-old thread where the results of "policy=iops;iops=0" (which effectively sets the round-robin technique to least queue depth) were very encouraging.  Whatever became of this?

 

mamatadesaiNim
HPE Blogger

Re: NIMBLE_PSP_DIRECTED vs "iops=1"

Can you please post the output of this command?

~ # esxcli storage nmp device list
HPE Nimble Storage
rmay_bk
Valued Contributor

Re: NIMBLE_PSP_DIRECTED vs "iops=1"

Looks like "iops=1" is implicit.  I guess I don't need to worry about the SATP rule in my host profiles.

 

Device Display Name: Nimble01WinSSD-bd18
Storage Array Type: VMW_SATP_ALUA
Storage Array Type Device Config: {implicit_support=on; explicit_support=off; explicit_allow=on; alua_followover=on; action_OnRetryErrors=off; {TPG_id=1,TPG_state=AO}{TPG_id=2,TPG_state=STBY}}
Path Selection Policy: NIMBLE_PSP_DIRECTED
Path Selection Policy Device Config: {policy=iops iops=1 bytes=0 useANO=0 isVvolPE=0 GROUP_ID=0 numIOsForIssueInq=10000 numIOsSinceLastInq=13 NUM_OF_MEM_ARRAY=1 SYNC_REPLICATED=0 lastPathIndex=1 NumIOsPending=0 numBytesPending=0 }
Path Selection Policy Device Custom Config:
Working Paths: vmhba1:C0:T7:L0, vmhba1:C0:T6:L0, vmhba2:C0:T7:L0, vmhba2:C0:T6:L0
Is USB: false

rmay_bk
Valued Contributor

Re: NIMBLE_PSP_DIRECTED vs "iops=1"

I've also discovered that NCM refrains from altering Disk.FailDiskRegistration and Scsi.CompareLUNNumber unless there's a Nimble volume present.  That explains why this, too, was missing from my extracted host profile.