topic Re: SDM Command failed. in Disk Enclosures

SDM Command failed.

Hai Nguyen_1 — Tue, 01 Oct 2002 13:54:11 GMT

Folks,

Four months ago, I was able to install the SDM software and use "launcher" to configure two new LUNs in the VA7100. I was able to use "armdsp -i" to view the status of the array as well. But now I am no more able to use launcher, nor armdsp, nor cvui to view the configuration/status of this array.

I got the following error when using launcher:

102. An error occurred while trying to connect to the database. No devices will be shown. Error getting database reference.

And:

Init error for device: localhost: . Init Error: Initial Device Exception. Verify device is powered on and connected.

Using "armdsp -i", I received this error:

Failed to open target localhost: Error logging in: Timeout expired.

The serviceguard packages have no problem seeing the LUNS and activating them.

I have tried armdiscover with no success (it could not see any device!!!). My last solution is to remove the SW, clean up /opt/sanmgr, /var/opt/sanmgr, and /etc/opt/sanmgr then reinstall the SW. However, I am open to your suggestions before I try this option last.
Thanks.

Hai

Re: SDM Command failed.

Vincent Fleming — Tue, 01 Oct 2002 14:28:05 GMT

Please check your configuration... specifically, do you lave a LUN 0 that is small (say, 10MB) that is write/configure for all hosts, and also check your LUN Security settings.

What does armdiscover say?

Re: SDM Command failed.

Hai Nguyen_1 — Tue, 01 Oct 2002 14:38:17 GMT

Vincent,

Thanks for your reply.

LUN0 is 50MB, used for nothing but communication with the server. Security settings by default is disabled and I believe that it remains disabled.

And here is the output of armdiscover:

Failed to obtain remote database interface to host: localhost

Hai

Re: SDM Command failed.

Vincent Fleming — Tue, 01 Oct 2002 15:09:55 GMT

Something's amiss...

I haven't seen that message before, but knowing that the arm commands can and do talk over TCP/IP at times and there's a reference to "localhost" and databases in the message, I think you've got something going wrong with your networking, or at least with the networking configuration of the arm commands...

What version of Command View SDM do you have? What kind of host is this running on? What other hosts to you have in your environment? Do you have CommandView on more than one host?

Re: SDM Command failed.

Hai Nguyen_1 — Tue, 01 Oct 2002 17:57:18 GMT

Vincent,

- SDM version: 1.04 loaded only on rp5450 with VA7100 attached.
- Platform: HP-UX 11.0
- Server: rp5450

Anyway, I have solved the problem which has something to do with "localhost".

My lookup order is "files dns". I noticed that localhost. can be resolved by DNS. As soon as I used only "files" for lookup, armdsp and launcher were back to work. That will be my workaround when I need to configure more LUNs...

Hai

Re: SDM Command failed.

Vincent Fleming — Tue, 01 Oct 2002 18:24:41 GMT

Aha!

Your DNS should not resolve localhost... that's an error in your DNS configuration. Check your DNS server's config. You should not have an A record for localhost.

...I suppose if you used this:

127.0.0.1 IN A localhost

it *might* work, though.

Good luck!

Re: SDM Command failed.

Hai Nguyen_1 — Tue, 01 Oct 2002 18:31:32 GMT

Vincent,

I did check with a DNS/BIND document and I am convinced that "localhost" is a valid entry in DNS (DNS and BIND by O'Reilly) whether or not SDM likes it.

Hai

Re: SDM Command failed.

Paul Barmettler — Wed, 02 Oct 2002 07:01:12 GMT

Hi Hai,

maybe it's a silly question. But can you see anything from the VA when you use "ioscan"?

Re: SDM Command failed.

Hai Nguyen_1 — Wed, 02 Oct 2002 10:50:57 GMT

Neuhaus,

Yes, ioscan shows all the LUNs on VA7100.

Hai

Re: SDM Command failed.

Vincent Fleming — Wed, 02 Oct 2002 11:30:03 GMT

Hai,

"localhost" is a "special" name in TCP/IP, and according to the RFCs, must always be 127.0.0.1 on every host. If your DNS is returning any other address for "localhost", then you have a problem in your DNS configuration. "localhost" is a synonym for the current host, like a loopback interface.

If your DNS is configured to give any other address for localhost, I would think you would have other software act strangely as well as the arm commands.

I suppose it's valid to have a "localhost" entry in your DNS, (as long as it's 127.0.0.1) but it's very non-standard. Normally, it appears only in /etc/hosts. This is mostly due to performance reasons - it's faster to resolve the address from /etc/hosts than it is to talk to a DNS server.

Good luck!

Re: SDM Command failed.

Aaron Sheard — Fri, 04 Apr 2003 12:55:34 GMT

I am now having the same problem. How was this issue resolved?

TIA

Aaron

Re: SDM Command failed.

Eugeny Brychkov — Fri, 04 Apr 2003 13:19:44 GMT

Hai,
try the following actions:
1. /opt/sanmgr/hostagent/sbin/HA_trigger stop
2. /opt/sanmgr/hostagent/sbin/dial_trigger stop
3. find file 'DeviceDBFile' and move it (or rename) to another location;
4. /opt/sanmgr/hostagent/sbin/dial_trigger start
5. /opt/sanmgr/hostagent/sbin/HA_trigger start
and then try armdiscover, armdsp -i and armdsp -a
Eugeny

Re: SDM Command failed.

David Reno — Thu, 10 Apr 2003 23:27:10 GMT

Where can I get the software installed into the /opt/sanmgr? It doesn't seem to exist on my hosts.

My HP-UX version is:
HPUX11i-OE-MC B.11.11.0209 HP-UX Mission Critical Operating Environment Component

Re: SDM Command failed.

Aaron Sheard — Fri, 11 Apr 2003 04:34:05 GMT

make sure the two required daemons are running. The start scripts are located in /opt/sanmgr/hostagent/sbin

They are called HA_trigger and dial_trigger.

i would suggest a stop/start on each of those and make sure they start correctly, and then do an armdiscover

Re: SDM Command failed.

Aaron Sheard — Fri, 11 Apr 2003 04:34:13 GMT

Re: SDM Command failed.

Aaron Sheard — Fri, 11 Apr 2003 04:34:16 GMT

Re: SDM Command failed.

Eugeny Brychkov — Fri, 11 Apr 2003 04:42:31 GMT

One copy of CV was shipped with your VA. If you lost it (CD) then call HP - neither CV nor Autopath nor SecureManager are not available for download
Eugeny

Re: SDM Command failed.

Andrey Pevnev — Wed, 07 Sep 2005 05:27:12 GMT

I have the same problem :((

bash-3.00# armdsp -i
Error logging in: TIMEOUT EXPIRED
bash-3.00# armdiscover
This could take several minutes ...

Failed to obtain remote database interface to host: localhost
bash-3.00# ping localhost
PING localhost: 64 byte packets
64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms

----localhost PING Statistics----
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0

I've done that you suggested:

bash-3.00# /opt/sanmgr/hostagent/sbin/HA_trigger stop

ERROR: Failed to stop HostAgent normally. Try to kill the process
NOTE: killing zombie jre thread 1562
NOTE: HostAgent has stopped
bash-3.00# /opt/sanmgr/hostagent/sbin/dial_trigger stop
NOTE: Stopping diald. Please wait...
NOTE: dial stopped.

bash-3.00# mv /var/opt/sanmgr/commandview/server/data/DeviceDBFile /var/opt/sanmgr/commandview/server/data/DeviceDBFile.bak

bash-3.00# /opt/sanmgr/hostagent/sbin/HA_trigger start
NOTE: Starting HostAgent
NOTE: HostAgent started
bash-3.00# /opt/sanmgr/hostagent/sbin/dial_trigger start
NOTE: Starting diald....
NOTE: Done...

But it's still doesn't work :( :(

Maybe any other ideas?

Re: SDM Command failed.

Torsten. — Wed, 07 Sep 2005 05:48:46 GMT

Andrey,

please start your own thread!

T.