cancel
Showing results for 
Search instead for 
Did you mean: 

Vstorage API and DFD

cgoliver
Level 5

Hello,

We are working a problem (error 25 "cannot connect on socket) with our DMZ esx hosts. They both fail during, what I refer to as stage one.

The firewalls are not recording any drops to either the master, proxy, vcenter, or the esx host.

 

Any help would be appreciated.

 

Thanks,

Chris

1 ACCEPTED SOLUTION

Accepted Solutions

cgoliver
Level 5

FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.

View solution in original post

6 REPLIES 6

Mark_Solutions
Level 6
Partner Accredited Certified

Can you ping in both directions - or at least resolve host names?

This includes the VMWare Backup Host which needs to be able to resolve all hosted clients on the ESX Server to back them up

Mark_Solutions
Level 6
Partner Accredited Certified

In addition to me previous post also remember that the ESX Servers themselevs have a built in firewall:

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

Please also confirm that all other setting and authentication have been set up in NetBackup - have you tested the credentials when they were added - or does it already work and this is just your DMZ firewalled ESX Servers having issues?

pikachu
Level 6
Employee Certified

just worked with chris...

  • switched policy over to manual instead of VIP
  • fails with status code 58
  • reverse lookup does not resolv back correctly
  • admin will work on hosts or dns fixes

cgoliver
Level 5

Had one of our Windows Admin remove the forward, but they didn't remove the reverse and now we two reverse records.

Mark_Solutions
Level 6
Partner Accredited Certified

You need to add them not remove them .. and they need to resolve according to the host name specified (VMHost name or VM Display name - which ever you have configured it for)

Just used hosts files on the VMware Backup host  - an entry for each hosted server on the ESX Server that matches the name shown when the policy runs

Hope this helps

cgoliver
Level 5

FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.