- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: SDM Command failed.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 06:54 AM
тАО10-01-2002 06:54 AM
SDM Command failed.
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:
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 07:28 AM
тАО10-01-2002 07:28 AM
Re: SDM Command failed.
What does armdiscover say?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 07:38 AM
тАО10-01-2002 07:38 AM
Re: SDM Command failed.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 08:09 AM
тАО10-01-2002 08:09 AM
Re: SDM Command failed.
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 10:57 AM
тАО10-01-2002 10:57 AM
Re: SDM Command failed.
- 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.
Hai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 11:24 AM
тАО10-01-2002 11:24 AM
Re: SDM Command failed.
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2002 11:31 AM
тАО10-01-2002 11:31 AM
Re: SDM Command failed.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2002 12:01 AM
тАО10-02-2002 12:01 AM
Re: SDM Command failed.
maybe it's a silly question. But can you see anything from the VA when you use "ioscan"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2002 03:50 AM
тАО10-02-2002 03:50 AM
Re: SDM Command failed.
Yes, ioscan shows all the LUNs on VA7100.
Hai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2002 04:30 AM
тАО10-02-2002 04:30 AM
Re: SDM Command failed.
"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!