![]() Since you mention that this is a blade server, do you know if the blade chassis has HP Virtual Connect modules installed? These are often used instead of passthrough ethernet uplinks to help consolidate and virtualize the blade networking. This is something that may be unique to the HP blade chassis setup. So it seems likely that something on the system is telling CentOS that the MAC should be used but I'm not sure where. I've also completely reinstalled CentOS and the problem persists. Note that none of them pertain to the MAC that CentOS thinks should be there. When I check the port mapping for the device bay that belongs to the server, I see: Mezzanine Device Port: ENET1 I'm not sure where the 18:a9 MAC addresses are coming from. On the CenTOS host, I'm seeing this in ifconfig results (slightly modified to protect the innocent): eth0 HW 18:a9:05:71:xx:xc Where can I definitively confirm what the system sees at the MAC address? ifconfig -a shows the "incorrect" one. In fact, if I use the MAC address that shows up in the onboard administrator and try to hardcode it to the nic (under /etc/sysconfig/network-script/ifcfg-eth0), I get an error:ĭevice eth0 has different MAC address than expected. For some reason CentOS thinks the mac address for ETH0 is something (18:a9:05:71:xx:xc) but I'm not able to find that MAC at all on the on-board administrator. ![]() ![]() I've got a HP Proliant 460c blade server running CentOS 5.x. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |