VMware: Adding a new ESXi host

We have 3 ESXi hosts and vCenter running vSphere 5.0. One of the hosts failed, and we bought a new server to replace it.

Can you recommend any step-by-step guides on adding a new host into an existing environment.

We are also running NetApp FAS 2240 using NFS volumes.
LVL 8
pzozulkaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
1. Remove the existing failed host from vCenter Server.

2. Right Click your Datacenter or Cluster, and Click Add Host, enter the FQDN, and follow the wizard, using root username and password.

You will also want to ensure, you have the same network portgroup names, and vSwitches.

Also you will want to connect the ESXi host to your NetApp NAS NFS export.
0
pzozulkaAuthor Commented:
I guess my question was more of configuring the ESXi host. Adding it to vCenter is easy.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You will need to

1. Add Networking
2. Configure Datastores

have you never configured an ESXi host?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

pzozulkaAuthor Commented:
I have managed existing setups before, but from scratch only once about a year ago. So didn't want to miss anything critical.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What specific help do you need with your configuration?

you should be able to replicate from existing hosts, by checking configuration?
0
pzozulkaAuthor Commented:
From what I'm hearing my predecessors might have setup the networking incorrectly. I am looking for any recommendations and links to resources that show how to CORRECTLY setup networking on ESXi. Like a best practice guide or similar. In other words, should we use LACP or not, etc.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Best Practice, is to have redundancy for all management services.

e.g. two nics for Management, two nics for VMKernel, two nics for VM Network.

if you use VLANs in your organisation, this can be achieved with a large 4 nic trunk, and individual VLANs per service.

However, it's difficult to monitor traffic inside a VLAN on a trunk, unless you have the monitoring facilities to do this.

iSCSI uses Multipath, so no teaming required here, otherwise teaming policy for trunk ports, and use STATIC trunks.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
coolsport00Commented:
Well, here's the vSphere 5.1 Networking Guide:
http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-51-networking-guide.pdf

But, the question is how do you *want* your networking to be? If you, or fellow staff, think the network is config'd wrong, we need to start with how do you want it and you can post a screenshot of the ntwk config of the current Host(s) & we can see if that matches with what you're wanting to achieve.

Regards,
~coolsport00
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
also team across cards, do not team on the same network interface.
0
pzozulkaAuthor Commented:
networkingWe use HP ProCurve switches. Each NIC Team is connected to two different HP Core switches for redundancy.

* T=Tagged, U=Untagged (ex. T1000 = Tagged on VLAN 1000)

vmnic0: Switch 2, VLAN - T1000, T1001
vmnic1: Switch 2, VLAN - U1, T320, T400, T480, T646, T649, T1560
vmnic2: Switch 1, VLAN - T1002
vmnic3: DMZ Switch
vmnic4: Switch 2, VLAN - U1, T1002
vmnic5: Switch 1, VLAN - U1, T1000, T1001
vmnic6: N/A
vmnic7: Switch 1, VLAN - U1, T320, T400, T480, T646, T649, T1560

The reason everyone believes networking is configured wrong is two fold:

1) vSwitch0 has vmnic0 and vmnic5. vmnic0 is NOT untagged on VLAN 1 (Default VLAN), while vmnic5 IS untagged on VLAN1. Same thing with the other vSwitches.

2) As far as LACP, or Trunks, or NIC Teaming goes -- The Network admins are telling me on the switch side -- all ports are regular ports. So not trunks, LACP, or NIC teaming on the switch side. On the vSphere side, I'm seeing NIC teaming setup for each vSwitch.

For example, vmnic4 has this config on the switch:

interface C11
   name "ESX1-vmnic3"
   flow-control
   unknown-vlans Disable
exit
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Looks a mess

Vmnic 0 and 1 both port configs need to be the same or in a trunk
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I'm surprised you do not have network issues.
0
pzozulkaAuthor Commented:
There might be some inefficiencies such as not using trunks or LACP, but as far as actual problems (forgetting inefficiencies for a second), I'm not seeing anything critical here.

Where do you see the problem?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Ports in vSwitch need same config.
0
pzozulkaAuthor Commented:
vSwitch 0: vmnic 0 & 5 have nearly same config.

vSwitch 1: vmnic 2 & 4 have nearly same config.

vSwitch 2: vmnic 1 & 7 have identical configs.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I was referring to vSwitch0.

Have you tested nic failure with this configuration, and does it pass?

Your iSCSI config, is not setup correctly, because it's recommended to multipath, MPIO, not team.

setup as per my EE Article

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0

so if anything I would change iSCSI network configuration.

and then have a think about

1. VLANs for many nics

2. Trunks using static trunks and/or VLANs

3. leave as is.
0
pzozulkaAuthor Commented:
We use to have our NetApp connected via ISCSI, but that's no longer the case. It now connects via NFS to NFS volumes. I guess the previous admin didn't cleanup the network config.

Do you have a similar EE article for NFS network config?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
NFS configuration is easier.

follow my video...

http://andysworld.org.uk/2011/06/21/new-hd-video-adding-an-nfs-datastore-to-a-vmware-vsphere-esxesxi-4x-host-server/

this is the same for all versions of ESX/ESXi.

create the VMKernel Portgroup, and then run the wizard to connect to the NFS Export om the NetApp.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.