VMware Cloud Community
ChristianG
Contributor
Contributor

unable to connect using VIC or HTTP after upgrade / SSH OK

Hi,

I just did an upgrade to vi3.0.2 of an esx2.5.4 server using the boot CD.

After the restar, I cannot login to the MUI using http/https or VIC2 client.

I enable ssh root login and it's working great.

Sorry if the awnser is someware in the forum but I search for the las 30 minutes without any awnser that was working.

Regards.

Christian

Reply
0 Kudos
7 Replies
LarsLiljeroth
Expert
Expert

Hi

First try to remove the host from the VC and re add it, this should install the agent again. If it does not work you might have to uninstall the agent.

To find the version run this

rpm -qa | grep vpx

You will see the version like this

VC 2.0.1 = VMware-vpxa-2.0.1-32042 ( i dont have the 2.0.2 )

then run

rpm -e VMware-vpxa-XXXXX depending on the version.

Then re add it to VC

Hope it helps.

If not it might be a firewall issue on the host.

/ Lars

// Lars Liljeroth -------------- *If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Reply
0 Kudos
Texiwill
Leadership
Leadership

Hello,

There is no longer a MUI in VI3. You should be able to connect to http://esxservername/ and get the UI... But that is for managing VMs not configuring the ESX server.

You should be able to connect the VIC direct to the ESX server by using the root user and specifying the ESXServerName.

If you can not do either of these, login to the console and troubleshoot the network.....

esxcfg-vswif -l

esxcfg-route -l

esxcfg-vswitch -l

esxcfg-nics -l

ping outsideHostname

Best regards,

Edward

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos
ChristianG
Contributor
Contributor

Hello,

There is no longer a MUI in VI3. You should be able

to connect to http://esxservername/ and get the UI...

But that is for managing VMs not configuring the ESX

server.

You should be able to connect the VIC direct to the

ESX server by using the root user and specifying the

ESXServerName.

If you can not do either of these, login to the

console and troubleshoot the network.....

esxcfg-vswif -l

esxcfg-route -l

esxcfg-vswitch -l

esxcfg-nics -l

ping outsideHostname

Best regards,

Edward

Hi thanks to both of you for the reply.

For LarsLiljeroth , I forgot to mentionne that it is a stand alone server so there is no Virtual Center Agent.

So for the trouble shooting here's some awnser.

esxcfg-vswi -l :[/b]

Name Port Group IP Address Netmask Broadcast Enabled DHCP

vswif0 Legacy eth0 10.47.102.151 255.255.252.0 10.47.103.255 true false

esxcfg-route -l[/b]

VM Kernel Routes:

Network Netmask Gateway

default 0.0.0.0 Local Subnet

esxcfg-vswitch -l[/b]

Switch Name Num Ports Used Ports Configured Ports Uplinks

vSwitch0 64 0 64

PortGroup Name Internal ID VLAN ID Used Ports Uplinks

Legacy vmnet_0 portgroup1 0 0

Reseau ferme portgroup0 0 0

Switch Name Num Ports Used Ports Configured Ports Uplinks

vSwitch1 64 2 64 vmnic0

PortGroup Name Internal ID VLAN ID Used Ports Uplinks

Legacy vmnic0 portgroup3 0 0 vmnic0

10.47.x portgroup2 0 0 vmnic0

Switch Name Num Ports Used Ports Configured Ports Uplinks

vSwitch2 64 3 64 vmnic1

PortGroup Name Internal ID VLAN ID Used Ports Uplinks

Legacy eth0 portgroup4 0 1 vmnic1

esxcfg-nics -l[/b]

Name PCI Driver Link Speed Duplex Description

vmnic1 06:07.00 e1000 Up 1000Mbps Full Intel Corporation 8254NXX Gigabit Ethernet Controller

vmnic0 07:08.00 e1000 Up 1000Mbps Full Intel Corporation 8254NXX Gigabit Ethernet Controller

vmnic2 03:0b.00 3c90x Down 0Mbps Half 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC

ping my pc :[/b]

\[root@LSVMWTEST root]# ping fq001158

PING fq001158.my.domain.com (10.53.43.102) 56(84) bytes of data.

64 bytes from fq001158.my.domain.com (10.53.43.102): icmp_seq=0 ttl=126 time=0.613 ms

64 bytes from fq001158.my.domain.com (10.53.43.102): icmp_seq=1 ttl=126 time=0.342 ms

64 bytes from fq001158.my.domain.com (10.53.43.102): icmp_seq=2 ttl=126 time=0.463 ms

Pin, traceroute, and remote SSH console is wroking pretty good. I don't think it is a network problem...

Any other suggestions ?

Reply
0 Kudos
ChristianG
Contributor
Contributor

I tried to restart http and management services, disable the firewall, still the same problem.

service mgmt-vmware restart

service vmware-webAccess restart

esxcfg-firewall -u

esxcfg-firewall -allowOutgoing

esxcfg-firewall -allowIncoming

and "service --status-all |grep running give me

crond (pid 868) is running...

dcstor32d (pid 1667) is running

dcevt32d (pid 1883) is running

dcsnmp32d (pid 1957) is running

gpm (pid 822) is running...

omaws32 (pid 1987 1986) is running...

omsad32 (pid 1581) is running...

cimserver (pid 2348) is running...

portmap (pid 711) is running...

Ramchecker is not running

snmpd (pid 1632) is running...

sshd (pid 3299 3293) is running...

syslogd (pid 690) is running...

klogd (pid 694) is running...

VMware VMkernel authorization daemon is running (pid 2003).

webAccess (pid 4521) is running...

xinetd (pid 813) is running...[/code]

Reply
0 Kudos
PerryWhittle
Enthusiast
Enthusiast

you dont seem to have a vswitch configured for the "Service console" port group. You may want to check this

Please rememeber to award points if you found this helpful or correct
Reply
0 Kudos
bggb29
Expert
Expert

the vic replaced the mui as Ed pointed out.

When you connect to the server as above http://servername

where you able to download the virtual infrastructure client ?

If you open the downloaded client is it launching ?

are you on the same subnet as the esx server with the client ?

Is dns setup correctly for the server ?

Reply
0 Kudos
ChristianG
Contributor
Contributor

Hi,

I do know that VIC replace de MUI but there is still de /ui url available on VI3.

I did'nt find out how to configure the network that the http deamon is listening on. is httpd depending on vmkernel network ?

How to set those in command line ?

I did some test but I might have the wrong sequence.

The "Service console" was using "Legacy eth0" portgroup instead of a regular "Service Console" port group.

I recreat it as "Service Console" portgroup without any luck for the rest execpt the service console.

I was testing some upgrade sénario with this test, but it seem like a fresh install might be better than an upgrade install...

I migth do a clean install this mornig...

Reply
0 Kudos