04-03-2012 12:13 PM - edited 03-01-2019 10:21 AM
I have a B200M2 with two local disks in it. Presently, I am SAN booting all of my B200M2's. I would take out the local disk if I had some blanks to put in the blade, but I don't so I'm leaving them in. The service profile I have setup to provision my blades has the boot order using a boot policy that boots from SAN. It works without issue. I also use a Local Disk Configuration Policy that has no local storage. So this service profile template will not work with the B200M2 that has disk in it. So I cloned the service profile templace and just changed the Local Disk Configuration Policy to Nothing Selected. I can deploy the blade properly with this service profile template but I get an error from the blade saying Local Disk 1 on server 1/1 operability: inoperable and Local Disk 2 on server 1/1 operability: inoperable.
How do I get rid of this error? What am I don't wrong that is causing this error?
Solved! Go to Solution.
04-03-2012 11:06 PM
Hello Russ,
Do you have OS running on that blade ? UCSM version ?
If it is 2.0.1 and OS is not running on that blade, the alert might be due to following defect
Padma
04-03-2012 11:06 PM
Hello Russ,
Do you have OS running on that blade ? UCSM version ?
If it is 2.0.1 and OS is not running on that blade, the alert might be due to following defect
Padma
04-04-2012 08:38 AM
I'm on 2.0.1t and saw the issue prior to me installing an OS. The alarm disappeared after installing 2008R2. Thanks for the timely info.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide