VUM could have introduced a port conflict with V4V services. You could double-check the firewall/port reqs to see if there is a conflict. Using that logic, I'd suggest pulling it off that vCenter and seeing how that impacts the V4V services then bouncing vCenter to get a fresh service start... just a thought. You can always test this in a lab first, as usually bouncing vCenter gets mixed emotions from your management/users.
↧