HP Proliant DL580 G4
-
@george1421 I didn’t want unmanaged switches so I have some managed. The Server has one network adapter as main, two again on mobo and a scsi network card with one more. Yes I had some hp dx2300 and (some laptops).
-
@firej8 said in HP Proliant DL580 G4:
@george1421 I didn’t want unmanaged switches so I have some managed. The Server has one network adapter as main, two again on mobo and a scsi network card with one more. Yes I had some hp dx2300 and (some laptops).
So I think that switches aren’t a problem because with the same switches or with same topology the pc clients working.
-
@firej8 If you plug a pc client into the same jack that went to the DL580, it works? We need to eliminate the “network” as the issue.
The next step after the network has been eliminated is to boot this dl580 using a live linux cd. You can use ubuntu desktop live, or linux mint 18.2 any where you can boot and get to a linux command prompt.
Once booted with a linux live dvd, then we can check to see if plugging in one network port will get an ip address.
-
@firej8 RAID is definitely an issue. Search the forums for ‘raid’ and you will find some suggestions on how to make this work. But focusing on the network/PXE boot for now is a good idea!
As I found out here there seems to be an “Embedded Dual NC371i Multifunction Gigabit Network Adapter” in that server. But I cannot find out what exact ethernet chip that is. Some say it’s a broadcom chip but I find different hints as well. Please boot a linux system (possibly live linux DVD) on that server, run
lspci -nn | grep netand post the full text or a picture of the output here. -
Moderator’s note: These may not be related, but cross linking threads: https://forums.fogproject.org/topic/10564/failed-to-get-an-ip-via-dhcp
-
@george1421 I test the client with the same cable on the same switch I get this :
-
@sebastian-roth I booted with a fedora 26 x64 live DVD. I got this:
-
@firej8 I just noticed that in one of the pictures you send in the intial post shows
bzImage32... ok. I don’t think this is actually causing the issue but it seems like iPXE does not recognize the system as 64 bit and therefore a 32 bit kernel is handed over.Drivers for those cards have been in the kernel for a very long time (BCM5706 - bnx2 and BCM5703 - tigon3). I don’t see why this could be an issue of missing drivers as we see that the NICs (
eth0, ...) are recognized and udhcpc tries to get an IP on those interfaces.I think we need to tackle this by looking at the actual network packets. As you seem to cover all the IPs in pictures I guess you are not happy to share a wireshark/tcpdump packet capture file with us?! But I don’t really see another way of finding what’s wrong. Anyone got another idea?
-
@firej8 Lets make sure I understand this.
You have 2 different computers plugged into the same cable and both have issues getting dhcp address (that is the message that ipxe is saying in your picture of the client.
If this is true, I’m still leaning towards a spanning tree issue.
Bad cable perhaps?
-
@sebastian-roth this picture you are talking about was old, when I tried yesterday the post was bzImage… ok .
Would you give me the instructions to get some sample of the packet capture you want? -
@firej8 if your fog server and pxe booting client are on the same subnet you can use the fog server to eves drop on the pxe booting process. Here is a tutorial: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
Upload the pcap file to a google drive or dropbox. If you are uncomfortable posting the link to the form use the forum direct message and send the link to either Sebastian or myself and we’ll take a look at the pcap and keep it private. When we have an answer then you are free to tear down the pcap from your google drive.
