Can't connect to management network on new install - Cisco 3850 w/LACP

[Konowl]

When we install a host at our organization, it's straight forward - install ESXI, configure the management network (accessible over two CNA cards in a ProLiant G9), connect to the environment and then move the NIC's over to the LAG's utilizing the same CNA cards.

We are now attempting to do the same thing on a new Cisco 3850 (in our PCI zone) with vSAN hosts.  Switch is a 24 port with RJ45 10 gig jacks with an SFP module - server is connected to the module.  Networking guys indicate the setup on the ports is the same as all the other servers - however, we cannot connect to the management network unless we disable LACP on these ports (which will not work for us as we only use these CNA cards).

Anyone else run into a similar situation at all?  We can't identify why we cannot connect at all, as the setup is the same for all our other hosts.

[hussainbte]

Please elaborate on "then move the NIC's over to the LAG's utilizing the same CNA cards."

share CNA model, ESXi version ..

[Konowl]

CNA cards are HP CN1100R on vSphere 6.5U1.

[Nick_Andreev · Accepted solution]

Hi Konowl,

Try the following:

• Confirm you're using HPE custom ESXi image
• CN1100R firmware is at least 7.13.xx (indicated in VMware HCL)

However, since NICs work outside of the LAG, it still sounds to me as a switch configuration issue.

As a side note, why do you require LAGs on your ESXi hosts? VMware already have multiple load-balancing policies available, that you can use to distribute network traffic between multiple uplink ports, without using port-channels.

[Konowl]

Thanks for your help; I explained this ticket to VMware and they said "nope that won't work" which was hilarious.  I said "shortest support call ever!" and then had to explain how it works NOW for us LOL.

In this instance we decided to skip LACP.

Thanks for your help.

[de0xyrib0se]

Had a similar issue and the answer support gave you is incorrect.

It works fine with LACP as long as you choose 'Route based on IP hash' for your load balancing algorithm.

I have an HP 1810 switch setup with a 4 port LACP trunk (in the HP world a trunk is EtherChannel) and my management network is humming along just fine.