VMware Cloud Community
TheAngryHeretic
Contributor
Contributor

ESXi 5.5 & The vCenter Server Appliance

We have recently installed ESXi 5.5 and the vCenter Linux Appliance.  The ESXi server is set up the way the documentation says, with multiple networks assign for different tasks, service console, vMotion, storage, etc.  I "THINK" everything is set up correctly, but I can not get my vCenter Appliance to see the ESXi server.  The network that the ESXi host is on, is not listed as an available option when I add a NIC to the vCenter Appliance. 

On previous versions of ESX, the network that the ESX host was available when I needed to add a NIC to the vCenter server.  Is there something that I am missing?  Does this sound like an issue anyone else has had? Or am I just missing a simple step?

MJ

Reply
0 Kudos
5 Replies
OscarDavey
Hot Shot
Hot Shot

hummm sounds like a license problem , did you check that everything is ok with license ?

Let me know

Best regards

Yours, Oscar

Reply
0 Kudos
abhilashhb
VMware Employee
VMware Employee

Are you able to ping the esxi host from vcenter and vice versa? What does it say when you try to add a host?

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

Reply
0 Kudos
TheAngryHeretic
Contributor
Contributor

Yeah, the licenses are ok.  I checked that a few times, and all seems to be in order.

Thanks. 

Reply
0 Kudos
TheAngryHeretic
Contributor
Contributor

The only way I am able to ping the license server is if I add a new port group to the network that the management console is on.  But when I add that port group, then add the network to the vCenter server, I get an error on port 902.  My assumption is that the additional port group that I added to the management console network is unecessary.

Thanks for the assist.

Reply
0 Kudos
Babbage
Contributor
Contributor

TheAngryHeretic wrote:

We have recently installed ESXi 5.5 and the vCenter Linux Appliance.  The ESXi server is set up the way the documentation says, with multiple networks assign for different tasks, service console, vMotion, storage, etc.  I "THINK" everything is set up correctly, but I can not get my vCenter Appliance to see the ESXi server.  The network that the ESXi host is on, is not listed as an available option when I add a NIC to the vCenter Appliance.

On previous versions of ESX, the network that the ESX host was available when I needed to add a NIC to the vCenter server.  Is there something that I am missing?  Does this sound like an issue anyone else has had? Or am I just missing a simple step?

MJ

I'm kind of a VMware newb..  but I had an issue where I put ESXi 5.5 on a new box (70,400 Mhz)  downloaded the Linux VM web vsphere management client
(a pig BTW even with 8 cpus - Running on a dedicated 512Gb Samsung 840 Pro SSD local - not remote Sata 6G drive )

I tried to put them on the same IP address.  Now I have the Esxi host at 192.168.1.75 and Vsphere running on 192.168.1.76.  When I first signed into it and tried to add a host, make datacenter etc it looped back to itself and said it couldn't manage it (add it to Vsphere) - Not sure if this applies...

For me ESXi and vSphere share the same phyiscal Gig nic and I have seperate Intel 350 dual nic (still need to setup LACP on phyiscal switch) and plan to use that pipe for my VM's.

Not to hijack, but I used new Vsphere webclient (again Suse VM Template) to make a new vswitch, added my two active (not used) nics - went through the wizzard, it finished and now the web gui doesn't show it - BUT THE OLD WINDOWS BASED vSphere client shows the 2 vswitches and all the nics correctly.

I am really trying to use this new "circus" web crap but I don't trust it. It seems to be over laden, slow and buggy.  This on a brand new kick ass server running NO other VM's - just the "vSphere web management deal"

Anyone else care to comment on this area?

Reply
0 Kudos