HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Blade PXE boot + Virtual Connect

 
chuckk281
Trusted Contributor

Blade PXE boot + Virtual Connect

Karene had a PXE Boot question:

 

******************************

 

I’m an Learning&Development Technical trainer,

One of my student said he could only do Virtual Connect PXE boot from LOM1a on all his FlexNICs – do you know/heard about this? Normal behavior? Is there a way to make it otherwise? (not sure of the entire story – again this is a scenario posed by a student in one of my class).

 

On the same topic, although you can select any NIC on a server to do pxe-boot from Virtual Connect Manager, would this only work if your NIC is enabled in RBSU to do PXE (I doubt that)? Or would VCM force the system to by-pass what is configured in RBSU (mostly what I would expect)? I have no equipment, so I can’t test…

 

***********************

 

Hongjun had the answer:

 

************************

 

Hi Karene,

 

VC 3.10/3.15 User Guide - http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02516247/c02516247.pdf

Page 108

Only the first FlexNIC on each physical port of a Flex-10 device can be used for PXE boot. Virtual Connect cannot enable PXE boot on the remaining FlexNICs of a physical port.

 

 

If you set first FlexNIC as “enabled” for PXE, it’ll overwrite what’s defined in BIOS. Page 108 also talks about this.

 

**********************

 

Any other comments or suggestions? Thanks to Hongjun for the answer.