cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Add Virtual Machine Name - VMware

Brad714
Level 2

We have two data centers, each with their own vCenter server, we'll call them vCenter A and vCenter B. 
We also have two Netbackup 5230 Appliances at each location, we'll call them NBU A and NBU B.

I'm trying to add a Virtual Machine Names to Netbackup to perform VM level backups. NBU A can add vCenter A and B credentials without issue. NBU B times out when trying to add either. 

The exact error is "The operation timed out. The operation has exceeded the time out limit, though the service or daemon may still be processing the request. (195)"

We are using the same username/password for everything. It doesn't matter what credentials I use, a correct one or made up, both time out. From NBU B I'm able to ping and trace route both vCenter servers by both FDQN, shortname, and IP address. DNS, Gateway, and Hosts entries look identical on NBU A and B. 

Running each of these commands from each NBU appliance shows the same results. 
w3m https://<vCenter_name>/sdk
openssl s_client -connect <vCenter_name>:443
telnet <vCenter_name> 443

Properties of both Master Servers look the same. Same servers listed under Servers. Same servers listed until VMware Access Hosts. I've tried rebooting the NBU appliance several times. The only difference I can tell is that NBU A is running 7.7.3 and NBU B is running 7.7.2, but I can't imagine that's the cause. Anyone have any suggestions for me?

Thanks in advance!

1 ACCEPTED SOLUTION

Accepted Solutions
3 REPLIES 3

Thiago_Ribeiro
Moderator
Moderator
Partner    VIP    Accredited

eduncan
Level 5
Employee

Are you adding it using the Display Name, DNS, Hostname, etc?

Are you using the Manual Browse or the VMware Intelligent Policy?

If you are using Display Name, perform the following to increase performance.

http://www.veritas.com/docs/000015326

https://www.veritas.com/support/en_US/article.000023787

This did it for me, thank you! I'm including details for anyone else that finds this thread, since many other threads include broken links. 

The solution was to add the credentials through the command line rather than the GUI. 
https://www.veritas.com/support/en_US/article.000037730

To Display Virtual Machine Credentials: 
/usr/openv/volmgr/bin/tpconfig -dvirtualmachines 

To Add Virtual Machine Credentials: 
/usr/openv/volmgr/bin/tpconfig -add -virtual_machine <virtual_machine_name> -vm_user_id <user ID> -vm_type <virtual_machine_type> -requiredport <IP port number> -password <password

<virtual_machine_type> can be one of the following: 
"1", for VMware Virtual Center Servers 
"2", for VMware ESX Servers 
"3", for VMware Converter Servers 

To Update Virtual Machine Credentials: 
/usr/openv/volmgr/bin/tpconfig -update -virtual_machine <virtual_machine_name> -vm_user_id <user ID> -vm_type <virtual_machine_type> -requiredport <IP port number> -password <password

To Delete Virtual Machine Credentials: 
/usr/openv/volmgr/bin/tpconfig -delete -virtual_machine <virtual_machine_name> -vm_user_id <user ID> -vm_type <virtual_machine_type>

 

Spoiler