I have a Qnap 459 ProPlus.
I created 2 iSCSI targets.
Im trying to figure out how to get the specific target to the correct host.
Currently both targets are showing up on both hosts, which is incorrect, I want one target for each host and the other host shouldn't see the target which is not assigned to it.
I went under "Advanced ACL" and created non-default policy, added each target to the correct initiator in the policy and set the accessability/read/write flags accordingly, but still both hosts see both targets.
iSCSI lun presentation
-
- Getting the hang of things
- Posts: 58
- Joined: Tue Oct 23, 2012 8:11 am
- storageman
- Ask me anything
- Posts: 5507
- Joined: Thu Sep 22, 2011 10:57 pm
Re: iSCSI lun presentation
Once you've defined the LUN masking policy click which LUNs you want to apply policy to.
And once you click Yes if you want to change back to No you have to click "Cancel".
Diabolically unintuitive interface from Qnap here! They need help in commonsense way to design interfaces.
And once you click Yes if you want to change back to No you have to click "Cancel".
Diabolically unintuitive interface from Qnap here! They need help in commonsense way to design interfaces.
-
- Getting the hang of things
- Posts: 58
- Joined: Tue Oct 23, 2012 8:11 am
Re: iSCSI lun presentation
I defined a policy, then went into edit. Under the policy, I see the 2 luns, and assigned Read/Write to 'rwatkins' and Deny to 'dhall', and applied.
I did the same for the 'dhall' policy except that I reversed the lun assignments.
However, both PC's still see both luns when we rescan on the host.
I did the same for the 'dhall' policy except that I reversed the lun assignments.
However, both PC's still see both luns when we rescan on the host.
- storageman
- Ask me anything
- Posts: 5507
- Joined: Thu Sep 22, 2011 10:57 pm
Re: iSCSI lun presentation
Did you apply LUN masking after you'd already connected to hosts?
Try disconnecting the initators on the hosts then reconnect?
Sure you didn't give same IQN initiator to both policies?
It "should" work...
Last resort try stopping/starting ISCSI service.
Try disconnecting the initators on the hosts then reconnect?
Sure you didn't give same IQN initiator to both policies?
It "should" work...
Last resort try stopping/starting ISCSI service.