Bridge Aggregation (ESXi) ping to Windows single port fails

[DeepakAshwath]

Hi All,

We have a HP 5900 switch where in 3 ports are aggregated and connected to a ESXi where the iphash setting has been done at the vSwitch level and at the Management Network level.

Now we have a windows machine connected to the same switch, the VLANs allowed are same for both ESXi and windows but once IPs has been assigned, the machines are not pingable to each other

Any configuration mismatch that could be possible, please post your opinions

Thanks

[DeepakAshwath]

I found that the mac-address learned by the switch appears for some time and disappears after sometime as shown below

[HP5900]display mac-address interface Bridge-Aggregation 45
MAC Address      VLAN ID    State            Port/NickName            Aging
[HP5900]

[HP5900]display mac-address interface Bridge-Aggregation 45
MAC Address      VLAN ID    State            Port/NickName            Aging
a0d3-c101-b15c   1          Learned          BAG45                   Y

However when the mac appears, the ping to the windows host still fails.

[sdide]

Hi,

Could you tell us a bit more about the setup?

A windows host cannot ping what? A guest on the vmware, or the vmware management.

Normally a windows host do not care for trunks, but expexts untagged traffic, whereas vmware (which has a built in switch - probably expect trunks ).

So if you could post the configuration of the two ports (the BAGG to the vmware, and the interface to the windows host.)

that would be most helpful in debugging.

Regards,

[DeepakAshwath]

Thanks for your reply sdide.

The ESXi bridge-aggregation is as below

interface Bridge-Aggregation30
 description Server1_vSw0
 port link-type trunk
 port trunk permit vlan 1 B C D
 port trunk pvid vlan D

In the above, vlan 1 is the interface allowed for windows as well

interface GigabitEthernet1/0/32

 port link-type trunk
 port trunk permit vlan 1

VLAN 1 is what is allowed on bridge-aggregation 30 and on the 1/0/32 port.

If 1/0/32 is made as an access port then also it is not able to ping to ESXi

How can I get the connection established between these machines on VLAN 1

VLAN 1 is internal network/private network

We are trying to ping from windows to ESXi management

Your help is appreciated, thank you

[sdide]

Hi,

I think you need to make the port for the windows host an access port.

interface te1/0/32

 port link-mode bridge

 port link-type access

 port access vlan 1

 quit

Regards.

/Søren

[DeepakAshwath]

Thanks sdide

I did try making the port where windows is connected to access port but they do not ping to each other

however, ping from switch to ESXi host and ping from switch to windows machine works fine.

ESXi and windows is in VLAN-1, but both the machines are not able to ping to each other, ESXi NIC ports are in aggregation in the HP5900 switch. ESXi has standard switches and guess that does not require LACP config. Please help.

[johnk3r]

There may be problem of VLAN or Promiscuous mode in ESX ...

[sdide]

Hi

You say:

"ESXi has standard switches and guess that does not require LACP config. Please help."

It does however require configuration (as far as i can read). You must configure the vswitch to use LACP, and you must ensure that you use the same hashing algorithm in both ends.

http://pubs.vmware.com/vsphere-55/topic/com.vmware.vsphere.networking.doc/GUID-0D1EF5B4-7581-480B-B99D-5714B42CD7A9.html

 Regards.

[Vince-Whirlwind]

Do you really need to have the same hashing algorith at both ends?

[sdide]

hi Vince,

The standard doesn't seem to require it. 

The reason i wrote it was just because the link on configuring vmware mentioned it. Not sure why they require it.

Regards.

[Vince-Whirlwind]

That's interesting.

I don't believe VMWare's advice is true, but there might some very interesting reason for it....

I'll have to have a play with that to see if I can figure out why they might recommend it.