RFVDB
asked on
HP Trunking to ESXi 5.1 - IP disconnect
Hi,
I have a weird anomaly with a brand new fresh install of ESXi 5.1 on two new Dell PowerEdge 1950s.
I setup the HP switch and ESXi networking just like the below link:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1004048&sliceId=1&docTypeID=DT_KB_1_1&dialogID=206986211&stateId=0%200%20202116152
The vsphere management IP is 192.168.5.16 on vlan 115 (this is a brand new subnet with no other conflicting IPs).
HP switch commands:
trunk 15-16 trk21 trunk
vlan 115 tagged trk21
I can't access 192.168.5.16, no ping, nothing.
I then change the IP address to 192.168.5.17 and whola, I'm able to ping and access it? Very weird.
On an identical server with identical HP switch trunking using trk20 I can ping it 192.168.5.15 and access vsphere via that IP address. I leave it overnight and come back in the morning and its no longer accessible with IP address 192.168.5.15, just for kicks I change it to 192.168.5.16 and its accessible for a while and then is inaccessible again?
In vsphere both hosts have the vswitch0 configured with the two NICs to be active and I only changed the load balancing to IP Hash. That's it.
Anybody have any clue?
- Jonathan
PS: Similar in a way to this issue in this thread that never got answered:
http://communities.vmware.com/thread/409288
I have a weird anomaly with a brand new fresh install of ESXi 5.1 on two new Dell PowerEdge 1950s.
I setup the HP switch and ESXi networking just like the below link:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1004048&sliceId=1&docTypeID=DT_KB_1_1&dialogID=206986211&stateId=0%200%20202116152
The vsphere management IP is 192.168.5.16 on vlan 115 (this is a brand new subnet with no other conflicting IPs).
HP switch commands:
trunk 15-16 trk21 trunk
vlan 115 tagged trk21
I can't access 192.168.5.16, no ping, nothing.
I then change the IP address to 192.168.5.17 and whola, I'm able to ping and access it? Very weird.
On an identical server with identical HP switch trunking using trk20 I can ping it 192.168.5.15 and access vsphere via that IP address. I leave it overnight and come back in the morning and its no longer accessible with IP address 192.168.5.15, just for kicks I change it to 192.168.5.16 and its accessible for a while and then is inaccessible again?
In vsphere both hosts have the vswitch0 configured with the two NICs to be active and I only changed the load balancing to IP Hash. That's it.
Anybody have any clue?
- Jonathan
PS: Similar in a way to this issue in this thread that never got answered:
http://communities.vmware.com/thread/409288
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.