LinkBack URL
About LinkBacksI have to ask why so many? I highly doubt it's the onboard, as of course they've been changed since replacing the motherboard. It could well be one of these PCI NICs causing the problems.There are two on board NICs and three PCI NICs.
I have to ask why so many? I highly doubt it's the onboard, as of course they've been changed since replacing the motherboard. It could well be one of these PCI NICs causing the problems.There are two on board NICs and three PCI NICs.
@tmcd35:
False positive from over zealous virus checker.
@tmcd35:
Useful Tool Gui
Just for testing purposes
tmcd35 (30th June 2009)
Don't worry, I already guessed before I posted that the LEA's bluecoat server was to blame. We blame it for just about everything else
Looks like a useful tool, I'll downloaded it at home tonight and give it a try tomorrow.
STATUS UPDATE: The three additional NIC's have been out all morning. So far 2 periods down and the server HAS NOT REBOOTED ONCE!
Of course we're probably just going through another quiet patch and whatever event is triggering the reboots hasn't happened in the past two and half hours. Bit suspicious that it was rebooting every 5 minutes before then though...
I'm going to give it till half way through period 4 then put the three cards back in ready for period 5. In theory - if its one of the NICs - I shouldn't get another reboot until after I put them back in, and most likely at the start of P5.
If this works I'll run the same test tomorrow to confirm, then add the cards one at a time to see if it's a particular card or a NIC config problem.
God knows. All three servers are the same. In all three cases the onboard NICs are bonded 2Gbps and are the only NICs actually being used.Originally Posted by Michael
I have 9 unrequired NICs taking up valuable IP space!?!
I think the last guy was starting to look into server Virtualisation. The three machines are of a good enough spec to use a s a jumping off point into this tech, and is something I'm looking into introducing later this year.
Even in a VM environment I couldn't see a need for more tha 4 NICs per server - 2Gbps bond data, 1Gbps SAN, 1Gbps (or even 100mbps) for IT management traffic.
The last guy put a lot of effort into redundancy, and I think he was spending the money on the kit while he had the chance.
@tmcd35:
Just use winrar or 7-zip to extract even though it is in a self extracting exe wrapper I personally like to extract to where I want it. It runs well across a network share also.
As you know it is just for testing purposes only if you like it then please purchase it.
If you don't need them, don't put them back in!God knows. All three servers are the same. In all three cases the onboard NICs are bonded 2Gbps and are the only NICs actually being used.
Weeelllll, here's the thing (I love to overly complicate matters
These machine that's playing up was to be (is to be) the first virtualised. The plan for October half term is to make a VM copy of the current running server then rebuild the physical box with Win2k8r2 Hyper-V.
I'd be looking at using atleast 4 NICs in each server (see above). So ideally I'd like to keep these in the server if they work.
If they are propper hp NICs they are likely to need a firmware upgrade too, put them in a workstation and upgrade them in that. This does not change the hardware identities and so there will be no driver concerns. Many other brands also support firmware upgrades on the higher end models that you would expet to find on a server.
One of the cards may be toast and so a firmware upgrade could help flush it out.
Unless I get a very unpleasant surprise in the morning this issue is now solved!
I want to thank everyone who contributed to this thread, you helped me sort out in my mind what I was doing, what I'd done and in some cases helped me view the problem from a different angle.
Okay, enough of the suspense - it was one of the NICs. No I have no idea which and I reliased (thanks Michael/Sysnack) that I pretty much don't have to worry which.
For what I want to do NIC wise in October I have at least two spare working 1Gbps NICs in the other two servers I can pinch and I have plenty of 100mbps NICs. Maybe one day I'll have a reason to test and find out which of the three NICs killed my server!
I downed the server at 1:30pm and put all three NICs back in. The system instantly blue screened. Took the NIC's out, no blue screen - windows boots. NICs back in and blue screening again.
Actually got additional information from the blue screen this time - NMI memory parity check error. But this only happens with the NICs in.
would be interesting to know if a firmware update will clear that error message or if its an actual memory error on the NIC in question.
The NIC's are el cheapo Realtek 8169 1Gbps desktop NIC's. Tbh i can't be asked to find out if a Firmware update is even available for them. As it stands we have plenty of spare 1Gbps (and if necessary 100mbps) NICs that one (or more) of these three being faulty doesn't effect our future plans in anyway.
The only thought I've had is - could the problem be with the PCI riser rather than one of the NIC's themselves. That would cause problems in October...
Not sure what a PCI Riser is unless you mean the PCI Slot ?
If im honest I would go with Intel for the network cards and ditch the realteks
Could be the riser but it could just as easily be one of the cards. The only way to test would be to put them in a different server and try. If I recall correctly there is not that much hardware in a 380 riser.
I would also look at ditching the realtec cards if you are going to put heavy usage over them as they will hit the CPU quite hard in comparision to fully accelerated cards. For stuff like iSCSI or heavy traffic/trunking this will burn lots of CPU cycles that would be far better applied to serving client requests. Something with full TCP/IP offload and - for iSCSI - iSCSI acceleration/HBA will end up providing you with a much better end result.
Remember that you can only team like network cards with the vendor apps so you would be able to trunk the two integrated ones with the hp app but would need to instal;l teh intel app to trunk the intel ones. This can also cause a bit of strife when the intel and hp teaming solutions get into an argument (read bluescreen hell).
tmcd35 (30th June 2009)
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
