VMware Cloud Community
mburutzis
Contributor
Contributor
Jump to solution

VUM plugin connecting to wrong IP

Hi all,

I am trying to activate my update manager plugin and keep getting a connection failure. When I look at the logs, I notice that it tries to connect to the second NIC on my VC server instead of the 1st NIC. Any idea on how to force it to use a specific IP?

Thanks,

Michael

Reply
0 Kudos
1 Solution

Accepted Solutions
AndreTheGiant
Immortal
Immortal
Jump to solution

Try to reinstall the VUM server and specify the right FQDN.

Also check DNS configuration to see if you have also some entries for the other IP.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro

View solution in original post

Reply
0 Kudos
9 Replies
vmroyale
Immortal
Immortal
Jump to solution

Hello and welcome to the forums.

You can modify the "C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml" file, to include the correct vCenter IP address.

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
Reply
0 Kudos
mburutzis
Contributor
Contributor
Jump to solution

i have already done this, but remote clients still try to connect with the wrong IP.

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

Have you restarted the VUM service?

During installation of the VUM service which resolution have you choose? IP, name, ?

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
mburutzis
Contributor
Contributor
Jump to solution

at the time of installation, we used the Production IP and name, because the other IP is used for the backup networks...

Is there a way to verify this? But the funny thing is, is that the client on the VC server works fine.

Keep in mind that the other clients are on a different subnet and it is accessible.

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

Try to reinstall the VUM server and specify the right FQDN.

Also check DNS configuration to see if you have also some entries for the other IP.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
mburutzis
Contributor
Contributor
Jump to solution

Can I reuse my DB after I reinstall? Are their any risks?

Reply
0 Kudos
anujmodi1
Hot Shot
Hot Shot
Jump to solution

VUM has its own database, it can be deleted anytime without any worries... So it can download the latest patches from internet and make database.

Anuj Modi,

If you found my answer to be useful, feel free to mark it as Helpful or Correct.

The latest blogs and articles on Virtulization:

http://communities.vmware.com/blogs/amodi

Anuj Modi, If you found my answer to be useful, feel free to mark it as Helpful or Correct. The latest blogs and articles on Virtulization: anujmodi.wordpress.com
mburutzis
Contributor
Contributor
Jump to solution

Alright, thanks Andre. I reinstalled Update Manager, without deleting the DB and reinstalled the plugin and it works great..

Woohoo!!! thanks andre and everyone who took the time to anser my question.

Reply
0 Kudos
silverline
Contributor
Contributor
Jump to solution

Just wanted to say that I also ran into this same issue and was able to resolve it by uninstalling and reinstalling the plugin with the FQDN instead ot the IP during initial setup.

Reply
0 Kudos