02-08-2011 01:11 AM - edited 03-01-2019 09:49 AM
Hello,
When trying to power on a blade, the following (attached) window appears and gets stuck.Could you help me out on this?
Also, I'd like to ask you around FCoE VLANs in UCS: do we have to pre-configure them in the LAN-CLOUD-VLANs in the UCS main configuration or it is not needed?
Thanks a lot,
Solved! Go to Solution.
02-08-2011 01:37 AM
Dani,
The boot order for that server has the EFI shell set above the other options.
Try this (assuming this server is not production).
Right Click on the server, select "Recover Server" - "Reset CMOS".
This should restore the default boot order.
As for the FCoE VLAN being defined in the LAN Clout - No, you do NOT need to define it as a VLAN there. Just define the FCoE VLAN in the SAN Cloud during VSAN creation and you're all set. This VLAN is strictly used for FCoE communication between the blades & interconnects. Highly suggest this is a dedicated VLAN and not shared with any of your data VLANs.
Regards,
Robert
02-08-2011 01:37 AM
Dani,
The boot order for that server has the EFI shell set above the other options.
Try this (assuming this server is not production).
Right Click on the server, select "Recover Server" - "Reset CMOS".
This should restore the default boot order.
As for the FCoE VLAN being defined in the LAN Clout - No, you do NOT need to define it as a VLAN there. Just define the FCoE VLAN in the SAN Cloud during VSAN creation and you're all set. This VLAN is strictly used for FCoE communication between the blades & interconnects. Highly suggest this is a dedicated VLAN and not shared with any of your data VLANs.
Regards,
Robert
02-08-2011 04:25 AM
Solved!!
Thanks a lot Robert,
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