VMware Cloud Community
JarryG
Expert
Expert
Jump to solution

LSI VMware driver: "MN" versus "OP" ???

Can someone tell mi what the difference is between "VMware OP" and "VMware MN"? I want to download driver for my LSI raid-controller and there are two of them:

6.602.54.00.1_MR_VMware5_Driver_esx55_OP.tgz

6.602.54.00.1_MR_VMware5_Driver_esx5x_MN.tgz

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! 😉
Reply
0 Kudos
1 Solution

Accepted Solutions
Linjo
Leadership
Leadership
Jump to solution

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

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".

View solution in original post

Reply
0 Kudos
6 Replies
Linjo
Leadership
Leadership
Jump to solution

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

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
JarryG
Expert
Expert
Jump to solution

Thanks man! Never heard of VMware using "code names" for vSphere releases...

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! 😉
Reply
0 Kudos
Linjo
Leadership
Leadership
Jump to solution

Its an internal thing and usually are not exposed outside the company.

// JL

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
AnybodyM
Contributor
Contributor
Jump to solution

So now in the current StorCLI release LSI has

Vmware

Vmware-MN

Vmware-NDS

And of course there is absolutely NO explanation ANYWHERE from LSI whether i should choose MN or NDS.

Reply
0 Kudos
DerekShaw
Enthusiast
Enthusiast
Jump to solution

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

Reply
0 Kudos
Helevitia
Contributor
Contributor
Jump to solution

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)