This is helpful. I am a storage admin working with a RHEL/Linux admin that reports hosts can not see LUN 0. All the other devs, 1 - 199, the host sees. I know the host could be configured to see LUN 0 or that the Admin could define it as another number - what do I tell him to do? Hosts are using native multi-pathing.
He is asking me to pull the devs and renumber them, by passing 0. I think he should edit the multipath files.
Did you try rebooting the host? Sometimes rebooting the host could help resolve the issue。
There may be compatibility issue with LUN 0 on some hosts. For example, when a VMware host sees a LUN Z, and the host is subsequently attached to a storage group with a real Host LUN 0, the VMware storage devices must be rescanned TWICE. The first rescan will delete the LUN Z, but it does not add the real Host LUN 0. A second rescan is necessary to put in place the real HLU LUN 0.
supersandwhich
26 Posts
0
November 4th, 2016 12:00
Hello:
This is helpful. I am a storage admin working with a RHEL/Linux admin that reports hosts can not see LUN 0. All the other devs, 1 - 199, the host sees. I know the host could be configured to see LUN 0 or that the Admin could define it as another number - what do I tell him to do? Hosts are using native multi-pathing.
He is asking me to pull the devs and renumber them, by passing 0. I think he should edit the multipath files.
any advisements or redirection is appreciated.
ECN-APJ
2 Intern
•
308 Posts
0
November 6th, 2016 22:00
heather_m
Did you try rebooting the host? Sometimes rebooting the host could help resolve the issue。
There may be compatibility issue with LUN 0 on some hosts. For example, when a VMware host sees a LUN Z, and the host is subsequently attached to a storage group with a real Host LUN 0, the VMware storage devices must be rescanned TWICE. The first rescan will delete the LUN Z, but it does not add the real Host LUN 0. A second rescan is necessary to put in place the real HLU LUN 0.