MN and OP are the code names for the vSphere releases and should probably not have been used in the driver name.
But it seems that the first one is for ESXi 5.5 and the second one for ESXi 5.0 and 5.1
Thanks man! Never heard of VMware using "code names" for vSphere releases...
Its an internal thing and usually are not exposed outside the company.
So now in the current StorCLI release LSI has
And of course there is absolutely NO explanation ANYWHERE from LSI whether i should choose MN or NDS.
it is now september 2015
We are faced with MN and NDS
We are attempting to install to esxi 6.0.0.whatever
We are guessing that NDS is the v6 version. If it works, we won't be posting. If it fails, we'll let you know the next step
NDS = Native Driver Stack I think. The NDS VIB is relevant to the VMware proprietary native driver API. storcli NDS is not tied to an ESXi version but I believe it only works with ESXi 6 native drivers since 5.x didn't have native drivers?
I don't know what NM and OP stand for, but I believe MN VIB is for the legacy vmklinux drivers.
The OP binary (pre-VIB) is for the pre-ESXi hypervisor with hypervisor command shell supporting standard Linux ELF binaries (esx 2.x – 3.x 32-bit I believe, but I’m not sure. Regardless, it is all but irrelevant as it is not in widespread production today)