Link to home
Start Free TrialLog in
Avatar of jskfan
jskfanFlag for Cyprus

asked on

Management Interface of ESXi Host

Management Interface of ESXi Host
in the scenario where I have 2 physical Network Adapters on the ESXi host.
I will go to DCUI and assign Ip address 192.168.1.10 to ESXi Host.Then I will team up both Physical Adapters. on the Vswitch all VM Ports as well as VMkernel ports will use the 2 Physical Nics as one Teamed Nic.
So The 2 physical Nics will act as one Trunk Port . I mean Whatever Vlan the VMs are on, should be accessed from the other side of the Network (Assuming the configuration on the physical Switches is setup properly).
Now when accessing the Managemnt Interface of the ESXi host, will that be just like accessing the VM on the ESXi host? I mean the connection will still go through the Trunk port (the Teamed up Nics)? or shoudl I dedicated one Physical NIC, just for the Management Interface of the ESXi host ?

Thank you
SOLUTION
Avatar of Mr Tortu(r)e
Mr Tortu(r)e
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I agree with Mr.Hancock, this is the way we have done it.  I will only add that we did this is large part not for performance, but security, to truly isolate the management side from public access.

But I do like mrtortur idea of active-passive on one and passive-active on the other.  I had not thought of that, learn something new every day :)

My ¢2
Avatar of jskfan

ASKER

mrtortur

If you Team up the Physical Nics, and one of them Fails, then I believe you still have redundancy. correct ?
So, if you put VM port group as well as VMkernel port group, to go through the Teamed Nics..there still should be redundancy,  you just do not get separation of traffic...
Assuming there is budget restriction and the company cannot afford more than 2 physical Nics by ESX host (:-)..
The Teamed up NICs will still work OK
If you Team up the Physical Nics, and one of them Fails, then I believe you still have redundancy. correct ?

if you have two nics, and one fails, how do you have any redundancy ? 2-1 = 1 ? 1 nic left!

if that nic fails, you no longer have any contact to the Management Network, which maybe okay, because you could access the console via iLo/iDrac/IPM etc

If you have budget restrictions, then you have to lose resilience and redundancy.

But most Production servers come with at least 2 network interfaces at present, and some with four. (4).

You have to make best use for your organisation.
Avatar of jskfan

ASKER

Andrew
If you Team up the Physical Nics, and one of them Fails, then I believe you still have redundancy. correct ?

The Nics are teamed up. if one fails, the other should still work until you replace the failed one...
If so why would you go with Standby..

I guess What mrtortur was referring to in his comment, is using one Active and one Standby for some traffic and Vice-versa for other type of traffic, This will help to separate traffic types, and at the same time, if one NIC fails , the other Nic will still carry all Traffic unseparated of course.
The Nics are teamed up. if one fails, the other should still work until you replace the failed one...
If so why would you go with Standby..

Correct. The majority of our clients, do not see the benefit or worth, and cost of keeping a port in standby, if you've gone to the trouble of cabling it up, connecting it and configure a physical switch port.

You may as well, have both Active/Active, to give you more bandwidth and resilience at the same time.

Most of our clients, if not all do this.

Active/Standby was used many years ago, (circa 2000), when physical switch configurations were not as advanced, or you could not trunk ports on your physical switches, again many options available for different network environments.

and considering the cost of 10GBe nics, you would never waste one in standby!
Avatar of jskfan

ASKER

By the way the Nic teaming configuration on ESX..is it something you configure with the ESX Vendor teaming software as well as within Vsphere client (you make both Nics Active)

OR

Just within Vsphere client only (you make both Nics Active)
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskfan

ASKER

and then further configuration on the physical switches. (inbound traffic).
I believe Port Aggregation (Etherchannel) on the Physical Switch Trunk Ports should do the job
Yes, that is a function that can do the job.
Avatar of jskfan

ASKER

Thank you