Error While Try to Install PD Linux Agent behind NAT

[RudySiau]

hi,

i have a problem when try to install a PD Agent for Linux, the linux client server (2.6.18-128.1.6.el5 ) had a different segmentation IP address from the PDOS storage pool and there's a NAT there between them, also a firewall.
The routing is already configured and it already can communicate at each other (can ping IP and hostname).
firewall itself is already open for required port for PD agent to communicate. (last time i try to allowed any)

here is the problem when i run the installation file in the client:

# sh pdagent-Linux_2.6_x86-6.5.0.10534.run

=> Please wait while extracting 6.5.0.10534 installer package...


Symantec Installation Script
Copyright 1993 - 2008 Symantec Corporation, All Rights Reserved.

This script will enable you to install and configure either
the PureDisk deduplication option (PDDO plug-in) for NetBackup
or a PureDisk agent.

=> Where do you want to install PureDisk agent? (/opt):
=> Are you sure you want to install it in /opt? [y,n] y
=> Starting PureDisk agent installation
=> Checking for available space in /opt: => done.
=> Extracting package: => done.
=> Retrieving SPA server information from the configuration file: => done.
=> Please enter the IP address or hostname of your SPA server: 172.16.203.118
=> Please enter your SPA username: root
=> Please enter your SPA password:
=> Please re-enter your SPA password:
=> Testing connection with the SPA (172.16.203.118): => done.
=> Checking the SPA version: => done.
=> Creating directory /opt/pdag/var: => done.
=> Creating directory /opt/pdag/tmp: => done.
=> Creating directory /opt/pdag/var/srd: => done.
=> Creating directory /opt/pdag/var/rt: => done.
=> Creating directory /opt/pdag/var/run: => done.
=> Creating directory /opt/pdag/var/progress: => done.
=> Creating directory /opt/pdag/var/keys: => done.
=> Retrieving routing tables: failed
=> Routing tables retrieval failed. The pdregister tool returned
=> the following error:

Wed May 20 2009 10:23:48.587594 ERROR (4150683328): Network error during webservice call: error
Wed May 20 2009 10:23:48.588333 ERROR (4150683328): An error occured while retrieving webservice result.


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
An error occurred: Could not download routing tables, cannot continue.
Aborting script.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

=> File /opt/pdag/log/installation/2009-05-20_10h20_6.5.0.10534_pda_install.log
=> contains a trace of this installation.

could anyone tell help me with this?
any reply wold be appriciated.

Thanks,

Rudy

[scorpy_582]

Hi Rudy,

Try to register the client manually.

 pdregister --action=register --type=Agent --login=login --passwd=pwd --url=https://yourspa/spa/ws --todisk --mkdir
pdregister --action=certificate --type=Agent --todisk
pdregister --action=routingtables --type=Agent --todisk


Also, there is a technote that talks about this problem.

http://seer.entsupport.symantec.com/docs/314017.htm

Hope this helps you

[RudySiau]

Hi Scorpy,

yes, i already try the manual registration for the client, from the three steps above:

pdregister --action=register --type=Agent --login=login --passwd=pwd --url=https://yourspa/spa/ws --todisk --mkdir (SUCCESS)
pdregister --action=certificate --type=Agent --todisk (SUCCESS)
pdregister --action=routingtables --type=Agent --todisk (FAILED)

it's the same as the previous step that i run from the script, always failed when it try to do a routingtables, the log messages is the same.

the link you give me is not helping, since we don't use a domain here so there's no DNS problem.

but thanks for the reply...

anyone else that had this situation when performing installation for client behind the NAT?

please help, any information will be greatfull...

[Abesama]

If your SPA (Storage Pool Authority) and CR (Content Router) are separate, then verify name resolution is set up properly for the CR too.

That is, the agent will need to resolve the CR with right name / IP.

I did not have NAT, but I had problem trying to configure Puredisk agent to use it's backp-NIC, it did not like the routing table, either.

FYI - the routing table file will have something like this.

0000 ffff content_router_name 0

That's for a single-content-router SPA.

Cheers,

Abe