Quantcast
Channel: VMware Communities : All Content - vSphere Upgrade & Install
Viewing all articles
Browse latest Browse all 3263

pNIC trunking, vSwitch config wrt vSphere 5.0 and 6.0

$
0
0

I'm presently configuring new HP switches to replace older HP switches.

The present three vSphere host pNICs are connected to one of the older switches.

 

Each host has two pNICs for management and vKernel traffic, teamed as active/active within vCenter.

Each host has two pNICs for production VM Network traffic, teamed as active/active in vCenter.

Finally, the HP SAN has its own connections to another physical HP switch in the same physical switch group.

Each host has two pNICs for SAN storage traffic, connected to the same switch as the SAN, teamed as active/active in vCenter.

 

For the new switches I plan to trunk as many ports as possible that are connected to the vSphere hosts, specifically the above-mentioned ports.

What settings must I know about within the vSphere host networking to configure??

 

Present configuration for the management/vKernel vSwitch0 is:

Promiscuous, MAC, Forged: Reject

NIC Teaming: Route based on originating virtual port ID, Link Status only, Notify: Yes, Fallback: Yes

 

Present configuration for the SAN storage vSwitch1 is:

Promiscuous, MAC, Forged: Reject

NIC Teaming: Route based on originating virtual port ID, Link Status only, Notify: Yes, Fallback: Yes

 

Present configuration for the production VM Network vSwitch2 is:

Promiscuous, MAC, Forged: Reject

NIC Teaming: Route based on originating virtual port ID, Link Status only, Notify: Yes, Fallback: Yes

 

Load balancing on all of them is Port ID.

 

If I trunk the vSwitch0, vSwitch1, vSwitch2 ports on the new HP switches, must I revise any of they above settings for vSphere 5.0??

 

The vSphere 5.0 hosts will be connected to the new HP switches for a short time, after which they will be replaced with vSphere 6.0 hosts, one at a time.

Do the vSphere 6.0 host vSwitches need any specific network configuration??

 

I finally found this article: VMware ESX, NIC Teaming, and VLAN Trunking with HP ProCurve · Scott's Weblog · The weblog of an IT pro specializing in v…


It says one should set the switch to route based on IP hash -- can I do this on the ESXi 5.0 host vSwitches without a reboot??

 

Thank you for reading this, Tom


Viewing all articles
Browse latest Browse all 3263

Trending Articles