secure path (spmgr) and hostname change

[Adam Garsha]

We changed our hostname a few weeks back on one of our HP-UX 11.11 boxes. Now, I note that 'spmgr display' doesn't work:

# spmgr display
Server: its-oa1.its.mu.edu Report Created: Thu, Sep 15 15:01:53 2005
Command: spmgr display
Error: This host is not authorized to connect to remote host.

Any ideas how to fix this?

[Sameer_Nirmal]

Is spagent is running?
You may need to restart the agent.

spmgr display will work only if spagent is running on the system. The agent provides all details to spmgr.

[Adam Garsha]

Yes, spagent is running. I think the hostname change is the cause.

[Sheriff Andy]

Is your new hostname in command view?

[Sheriff Andy]

I would also do a nslookup from both the sma and the host where you changed your hostname. I would do it by IP as well.

Is your old hostname still in dns? If so, you might want to have your dns people make the change so it will see your new hostname associated with the IP address.

You can always add the entry of your new host to your hosts file on your sma and see if that fixes the problem.

Best of luck.

[Uwe Zessin · Accepted solution]

There isn't much help in the documentation, but it sounds like you need to add the new system:

# spmgr client add its-oa1.its.mu.edu

and you should be able to remove the old entry:

# spmgr client delete "name"

There doesn't seem to be a way to list authorized clients (or it is not documented, can't try a 'client list/show' right now) :-(

----

Many commands of SPMGR _can_ work remotely, that's why this stuff is there:

# spmgr xyz.abc.com:display

and this has nothing to do with Command View or a storage management appliance (SMA).

[VEL_1]

Hope u can get solution from the following link:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=766197

[Sameer_Nirmal]

You need to restart the spagent using
#/sbin/init.d/spinit stop
#/sbin/init.d/spinit start

spmgr utility is capable to work on client-server basis. This utility can interact with other spagents running on different hosts.
One need to ensure the remote hosts are reachable from the spmgr host. I believe ( it is not documented though ) the spmgr simply uses the host's network configuration through spagent to know local as well as remote host details.

You can add those spagents as clients using
# spmgr add client

Another point is , spagent is keeping a binding to the host name and any network realted change. I belive that the error reflect the old host name given by spagent making spmgr belive it as remote host and it could not be found in real !!!

It is nothing to do with Command View or SMS appliance for sure.