SD across network?

[joe_91]

Team:

How is that it is possible to do swlist over a network on to a box on which you do not even have an ID? Can someone please explain the mechanism?

Thanks
Joe.

[Anil C. Sedha]

Hi Joe,

If you want to do a swlist over a network, the command to do it is

swlist @ boxname:/depotpath

But, now if you don't even have an id, you can however try this. Are you on the same network as that box.

This is tricky but try the command above.

[Stefan Farrelly]

Yes. You do NOT need an account/login to do this.

The sw command you invoke merely talks to the running swagentd daemon via a TCP port running on the remote server across the network.

You can see the daemon normally running on all HP servers;
ps -ef | grep swagentd

If the serverd daemon isnt running then you cant do any remote sw commands to it, otherwise it simply sites there listening on a particular TCP port for anyone to send sw commands to it.

[steven Burgess_2]

Hi Jo

Try the ip address

HTH

Steve

[steven Burgess_2]

Joe

Ignore, completely misread the question

Steve

[Anil C. Sedha]

Joe,

If you don't need a login as per other syad's listed here, the command i gave you should work fine.

Try it out....

And don't forget to assign points for answers which help you in the true sense

[Sanjay_6]

Hi,

Try

swlist @remote_server_name:/

remote_server_name should be resolvable by your system.

If not use the remote server ip address in place of remote_server_name.

you can use the -l patch or other option with swlist command fore patch swlist or things like that.

Hope this helps.

regds

[joe_91]

Hi All:

I guess i have to reframe the question.

how is that it is possible to do a swlist -l product @ remote-host-name even without having ID on that box? I mean to ask what is the mechanism behind.

Thanks
Joe.

[Rich Wright]

SD is a client/server type application.
A daemon listens to a port and acts on and responds to commands.

Rich

[Ted Ellis_2]

are you interested in locking it down ... at least to limit access to only the root user... or just gathering background info?

[MANOJ SRIVASTAVA]

if you can go to the box on the network then why not run the commnad form the box , or do a remsh boxname :swlist xxxxxx



Manoj Srivastava

[Mateja Bezjak]

Hi Joe,

SD depends on DNS. So, if you run swlist @ remote_host, the name will first get resolved. Just like if you run nslookup hostname and nslookup IP, both should show the same thing if DNS is configured properly.

Regards,
Mateja

[Wodisch]

Hey Joe,

"Software Distributor" uses the DCE Remote Procedure Calls, and does not need you to be logged in on the remote machine. You *do* need to have read-permission on the remote machine, but that is turned on by default. Check (on the remote machine) with:
swacl -l root @ /

It should show that "any_other" has "r" (and maybe "t") permission.

Then on that remote machine the so-called "depot" has to be "registered", which you can do with the followinf command:
swreg -l depot /your/local/depot/path

And on your local machine you can list the registered depots (but only those) with:
swlist -l depot @ remote-machine-address-or-hostname

And to install something from such a depot you have to use the option "-s remote-host:/remote/depot" with your "swinstall" command.

HTH,
Wodisch

[Giri Sekar. · Accepted solution]

Hi:


The answer given by Wodisch explains how the SD works (DCE RPC) but if you need to get an Information about a remote box say..
swlist -l patch -a state -a date @ |grep 18543

then it reads the /var/adm/sw/security/secrets
file. It is actually shipped with default value and can be changed for site specific considerations. If you happen to change the default value then these commands would not work across the network.

Giri.

[joe_91]

Hi Giri:

Thanks. That answers my question. I changed that file and i am not able to swlist on a remote box.Great List. Thanks

Joe.