- 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
тАО04-04-2003 04:55 AM
тАО04-04-2003 04:55 AM
Re: SDM Command failed.
TIA
Aaron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2003 05:19 AM
тАО04-04-2003 05:19 AM
Re: SDM Command failed.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2003 04:27 PM
тАО04-10-2003 04:27 PM
Re: SDM Command failed.
My HP-UX version is:
HPUX11i-OE-MC B.11.11.0209 HP-UX Mission Critical Operating Environment Component
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2003 09:34 PM
тАО04-10-2003 09:34 PM
Re: SDM Command failed.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2003 09:34 PM
тАО04-10-2003 09:34 PM
Re: SDM Command failed.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2003 09:34 PM
тАО04-10-2003 09:34 PM
Re: SDM Command failed.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2003 09:42 PM
тАО04-10-2003 09:42 PM
Re: SDM Command failed.
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2005 10:27 PM
тАО09-06-2005 10:27 PM
Re: SDM Command failed.
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2005 10:48 PM
тАО09-06-2005 10:48 PM
Re: SDM Command failed.
please start your own thread!
T.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- « Previous
-
- 1
- 2
- Next »