UCS Manager Configuration Failure, boot-dev-no-support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2021 02:44 PM
With our new B200-M5 blades, we are running into a "service profile *server name* configuration failed due to boot-dev-no-support" error. The results of this seems to be that we can't mount a virtual CD/DVD in the KVM console. Has anyone else ran into this?
- Labels:
-
UCS Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2021 02:51 PM
Since the service profile is failing to configure, its likely causing the failure of mounting CD/DVD.
Can you please confirm where you are attempting to boot from and the configured boot order in the service profile?
Are you setting this up in UCSM mode? What other errors do you see? Usually this error is indicating a boot order device that cannot be configured correctly based on the hardware/software combination.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2021 02:55 PM
I'm not too sure on the UCSM mode, what is the best way to check? But I'm also getting 2 "link-down" errors and 2 "vif down" errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2021 03:03 PM
Thanks, can you send me a screen capture of the boot order from the service profile and confirm the boot device you are attempting to install to?
You are likely using UCSM mode if you are not managing these devices through Cisco's Intersight cloud.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2021 05:56 AM
Here it is!
We do have Intersight, but we aren't currently using it on these new installs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2021 06:46 AM
Okay, looks like you are attempting to create a boot policy for M.2 disk. Take a look at these and they should be able to help:
