Help please! BACS4 cannot find local host on a brand new PER710

Networking

Networking
Learn how to modernize & transform the network with the latest solutions from Dell Data Center, Campus and Wireless networking solutions.

Help please! BACS4 cannot find local host on a brand new PER710

This question is answered

Hi,

We've just purchased three PowerEdge R710 servers from Dell with an aim to host a Hyper-V VM on each.

We are trying to use BACS4 to team network ports together, say two for the VM and two for the host OS. However BACS4 can't access the Broadcom BCM5709C. It launches with an empty Hosts node. If you try to add a host using "localhost" an error immediately appears:

"Unable to establish connection to host: localhost. Please check network communication."

The program also fails to connect when I attempt to use 127.0.0.1, ::1, the current IP address of the server and the name of the server. All of the above are pingable, however.

The Discover Hosts option doesn't find anything either.

We haven't done much at all with the server other than joining it to our domain, enabling RDC, installing Windows Updates, Symantec Endpoint Protection and the Hyper-V role.

It seems to me that the BACS4 software has been installed incorrectly or is incompatible with the network card installed in the server. I've seen a few people on Broadcom's forums suffering the same thing but with no real explanation for the cause of this error.

Has anyone here had any experience of this and how best to fix it?

Thanks,

Paul Collin

Verified Answer
  • Sorry, I've realised I've probably put this on the wrong forum. I've also managed to fix the problem by installing the latest version of the Broadcom Management Programs from the Broadcom website. (v15.0.15.1 worked for me. v15.0.14.1 was the offending version that came with the server.)

    Apologies for the hassle! Feel free to delete this thread unless it is of some use elsewhere.

    Thanks,

    Paul

All Replies
  • Sorry, I've realised I've probably put this on the wrong forum. I've also managed to fix the problem by installing the latest version of the Broadcom Management Programs from the Broadcom website. (v15.0.15.1 worked for me. v15.0.14.1 was the offending version that came with the server.)

    Apologies for the hassle! Feel free to delete this thread unless it is of some use elsewhere.

    Thanks,

    Paul