remote server cannot access local depot

[Jerry_109]

# uname -a ; model
HP-UX B.11.11 U 9000/800/rp3410
root@[/var/adm/crash]

swlist -l depot

# Initializing...
# Target "airlock" has the following depot(s):
/var/opt/mx/depot11
/SCIF/Netscape
/SCIF
/var/swdepot/APPS/11.11
/tmp/cpm/patches/depot
/var/adm/crash/GOLDQPK11i
********************************
Hello HP,
I have listed my local depots above. I have a remote server that can only see :
" /var/opt/mx/depot11 "
Why can't the remote server access all local
depots ?

[Uday_S_Ankolekar]

You can try swlist -l product or swlist -l bundle.
swlist -l depot is not correct option for -l

-USA..

[Vincente Fernandes · Accepted solution]

From the remote server run
"swlist -l depot @airlock"
What error message do you get from the above command?
based on above output airlock i beleive is you depot server

[Florian Heigl (new acc)]

swlist -l depot @ ignite_server works fine for me :)

You could look into swacl settings, too.

[Jerry_109]

Sorry All,

I needed to add "airlock" to my hosts file.

[Biswajit Tripathy]

"swlist -l depot" is the correct option.

You can see the depots on "airlock" from a remote
server by running the following command on remote
server:
# swlist -l depot -s airlock

If this does not list the depots present on "airlock",
the possible causes can be

1) network problem (find it and fix it)

2) "swagentd" daemon not running on "airlock" (run
"/usr/sbin/swagentd -r")

3) Depots are present on "airlock", but not
registered. (Register the depot by running following
command on "airlock":
# swreg -l depot /depot/path

- Biswajit

[Florian Heigl (new acc)]

Ah - yes, they need to be able to talk names for SD :)
Sorry I didn't mention that in my post.

[Biswajit Tripathy]

Actually, you don't need to add "airlock" to the
/etc/hosts file. If DNS can resolv it, then it would be
fine too. If DNS does not resolv it, it should STILL be
fine if you use IP address of "airlock" instead of
hostname.

- Biswajit