After the IP address changes on the system where the vCenter Plug-in is installed, a re-registration of the vCenter Plug-in is needed to reflect the new IP address. Otherwise, the vCenter Plug-in keeps trying to connect to the old IP address.
This vCenter Plug-in system can be a dedicated machine, and is being referred to as the “Data Protection for VMware vCenter Plug-in Server”, in most IBM TSM4VE component overview images.
In this particular case, the vCenter Plug-in Server (in essence, an IBM WebSphere Application Server (eWAS) server) is directly running on the vStorage Backup Server (VBS), and not on a dedicated machine. In my experience, such a setup is quite common.
A regular de-installation and reinstallation of the “Data Protection for VMware vCenter plug-in” component of the “Tivoli Data Protection for VMware” package, does not solve the issue. The old IP address is still used. My guess is that this component also holds the “IBM WebSphere Application Server V8.0 – TSMVEplugin”, which needs to be made aware of the IP address change manually. During reinstallation the configuration file with the old IP address is retained and not updated.
I noticed that uninstalling the mentioned “Data Protection for Vmware vCenter plug-in” component of the “Tivoli Data Protection for VMware” package does sometimes, and sometimes does not, remove the vCenter Plug-in. When reinstalled, the vCenter Plug-in keeps referring to the old IP address. A reboot of the vCenter server or VBS server does not help.
In the Plug-in manager, a message such as “Unable to connect to TDP for VMware plugin” is displayed:
The following error occurred while downloading the script plugin from http://<old IP address> of the TDPVE plugin server):9080/TsmVMwareUI/plugin/config.xml:Unable to connect to the remote server
Below are the steps outlined to update the vCenter Plugin-in to reflect (and connect) to the IBM WebSphere Application Server (eWAS) at the new IP address. As stated above, a re-registration is needed after the IP address changes on the system where the TSM4VE vCenter Plug-in is installed.
To do this, two different methods are described. For both methods, you’ll need a vCenter account with administrative privileges within the VMware environment. If one method doesn’t work for you, try the other one.
- On the VBS (or the machine where the “Tivoli Data Protection for VMware” package is installed, open the Windows Services applet;
- Stop the “IBM WebSphere Application Server VX.X – TSMVEplugin” service;
C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VmwarePlugin
C:\Program Files\Common Files\Tivoli\TDPVMware\VmwarePlugin
The remainder of this article is written for Windows; check the manual for Linux (you’ll need ../java –jar reg.jar).
- Unregister/register the vCenter Plug-in;
- unregister_vcenter.cmd <vcenter hostname> <vcenter user ID> <vcenter user pw> <old IP address>
- register_vcenter.cmd <vcenter hostname> <vcenter user ID> <vcenter user pw> 9080 (or another GUI Web Server Port)
- Start the “IBM WebSphere Application Server VX.X – TSMVEplugin” service;
- Open vCenter and check the TSM4VE vCenter Plug-in.
If the vcenter hostname specified is a DNS name, note that the first DNS server is always queried. No cache involved.
Just to be sure, check the config.xml file in C:\IBM\tivoli\tsm\tdpvmware\ewas\profiles\TSMProfile\installedApps\tsmCell\TsmVMwareUIEAR.ear\TsmVMwareUI.war\plugin. It should reflect the new IP address.
For method #2, you’ll need VMware’s Managed Object Browser (MOB), as this cannot be done directly from the vSphere Client software. The MOB is a GUI that “allows you to navigate the objects on a server and to invoke methods. Any changes you make through the MOB take effect on the server”. Check the VMware vSphere Documentation Center for more information.
Remove the TSM4VE vCenter Plug-in:
- In a browser window, open a connection to https:\\vcenter\mob;
- Log in with administrative privileges;
- Under “Properties”, click content;
- Under “Properties”, click ExtensionManager;
- Under “Properties”, locate the extensionList line, that relates to the TSM4VE vCenter Plugin. It follows the naming format “extensionList[com.ibm.tsm.tdpvmware@<VBS server name>. You might click the line to gather more information. Note down the text between the brackets and the quotes – you’ll need it later;
- Under “Methods”, click UnregisterExtension;
- In the “Value” field, type the text between brackets;
- Click Invoke Method;
- The message “Method Invocation Result: void” should be displayed. If it does, the TSM4VE vCenter Plug-in was successfully removed and is no longer visible as a value in the extensionList of the ExtensionManager (see the previous steps). Also, the icon is removed from Solutions and Applications. and, it is removed from the Plug-in Manager (in vSphere: Plug-ins à Manage Plug-ins).
Now you can reinstall the TSM4VE vCenter Plug-in (“Data Protection for Vmware vCenter plug-in” component of the “Tivoli Data Protection for VMware” package):
Sources for this article:
Removing the VE Plugin from ‘Solutions and Applications’
Steps to unregister and register TSMVEplugin to vCenter Server
—- Tommy Hueber