Forum Discussion

Dollypee's avatar
Dollypee
Moderator
11 years ago

VMware browse client list timing out with "socket time out error"

Master server : WIN2K8 Enter R2

No of VC servers: 15

VC versions: 4.1, 5.0

Netbackup version: 7.5.0.5

Trying to browse vmware clients list has been consistenly timing out with socket time out error. On the master server, bpvmutil process run for about 2hrs and completes. But whenever I tried to re-browse for client lists, it still kept timing out.

I found this TN about excluding VC you are not intrested in when browsing: http://www.symantec.com/business/support/index?page=content&id=TECH190396

But would like to know how to include these exclude list when you need to add VMs from them.

 

 

 

7.5
Backing Up
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    11 years ago

    Hi,

     

    Looking at that log there are many issues. Credential errors, hostname lookups resulting in 48, connections being forcibly closed, and connections just timing out.

     

    As we're not familiar with your environment, I would remove all the vcenters you've configure int credentials tab. Make sure you can resolve them, and vice versa, and then start adding them back one by one.

     

    Also make sure you've got the correct backup host selected in your policies.

     

    http://www.symantec.com/docs/TECH192643

     

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hi,

     

    You may want to increase your browse timeouts ( http://www.symantec.com/docs/HOWTO70895 ), and also at the "Reuse VM selection query results" option ( http://www.symantec.com/docs/HOWTO70977 ). In your environment which seems large, it might be a good idea to refresh the queries less frequently.

  • Dollypee's avatar
    Dollypee
    Moderator
    11 years ago

    Riaan, I have already increased the time out to 2800 with no postivie result. Also we are not using VIP query going by your TN.

    Here's the latest error ..After trying to browse for vm client " it timed out with error "Cannot connect on Socket .(25) . I have attached nbproxy logs. Still trying to also analize it. Please any help..

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago
    Is there a firewall anywhere in the picture? Have you tried to disable IP lookup?
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hi,

     

    Looking at that log there are many issues. Credential errors, hostname lookups resulting in 48, connections being forcibly closed, and connections just timing out.

     

    As we're not familiar with your environment, I would remove all the vcenters you've configure int credentials tab. Make sure you can resolve them, and vice versa, and then start adding them back one by one.

     

    Also make sure you've got the correct backup host selected in your policies.

     

    http://www.symantec.com/docs/TECH192643

     

  • Dollypee's avatar
    Dollypee
    Moderator
    11 years ago

    Team,

     

    This issue has been resolved. I deleted all the VCs and re-authenticate them one after the other. after then, I restarted netbacup services.

     

    Thank you all for your 24/7 support.

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Please clear the solution for your own post as you have followed Riaan's advice:

    .... I would remove all the vcenters you've configure int credentials tab. Make sure you can resolve them, and vice versa, and then start adding them back one by one.....

    Please mark Riaan's post as solution after you have cleared solution for your own post.

    Thanks.

     

  • Dollypee's avatar
    Dollypee
    Moderator
    11 years ago

    My bad. I had'nt even pay attention to Riann's reply. I had initially gone ahead to make use of my TEST domain environment to carry out this troubleshooting steps. Thanks all.