Jump to content
 English      
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
     Forums advanced search
HP.com Home
IT Resource Center Forums > Tru64 UNIX > system administration

redetect domain - This thread has been closed

» 

IT Resource Center

» Login
» Register
» My profile
» Search knowledge base
» Forums
» Patch database
» Download drivers, software and firmware
» Warranty check
» Support Case Manager
» Software Update Manager
» Training and Education
» More maintenance and support options
» Online help
» Site map

Member icons
 
 HP moderator  HP moderator
 Expert in this area  Expert in this area
Member status
ITRC Pro ITRC Pro
250 points
ITRC Graduate ITRC Graduate
500 points
ITRC Wizard ITRC Wizard
1000 points
ITRC Royalty ITRC Royalty
2500 points
ITRC Pharaoh ITRC Pharaoh
7500 points
Olympian Olympian
20000 points
1-Star Olympian 1-Star Olympian
40000 points
2-Star Olympian 2-Star Olympian
80000 points
»  How to earn points
»  Support forums FAQs
Question status
Magical answer Magical answer
Message with a response that solved the author's question
Favorites status
Add to my favorites Add to my favorites
Delete from my favorites Delete from my favorites
This thread has been closed Thread closed
 

Content starts here
   Create a new message    Receive e-mail notification if a new reply is posted  Reply to this message
Author Subject: redetect domain      Add to my favorites  This thread has been closed
admin1979
Nov 3, 2009 16:52:57 GMT   

Hello,

We have tru64 server. And it has 2 disk enclosures. Now the SCSI connection these disk enclosures lost for some time.
Now one of the domains present on these disk enclosures are inaccessible. Like this,

# showfdmn source_domain
showfdmn: unable to get info for domain 'source_domain'
showfdmn: error = I/O error

Now the SCSI connections are proper. We can also see all the required disks in scu show edt. But how do we make sure that the domain is recognised by the system. We have lsm and since lsm cannot access this domain the volume is disabled as well.
There mus be a way to redetect the domain by tru64 system.
Can someone help?

Thanx,
admin
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here


Sort Answers By: Date or Points
Venkatesh BL Expert in this area This member has accumulated 2500 or more points
Nov 4, 2009 04:53:20 GMT    Unassigned

If the disk and volume are 'detectable', then the domain will also be detectable. You must first try to enable the volumes that are used by this domain. After that, showfdmn will work fine.
admin1979
Nov 4, 2009 06:12:16 GMT    N/A: Question Author

Thanks for the reply. But the problem is , somehow LSM has put the sourcedg volume disabled.

# voldg list
NAME STATE ID
rootdg enabled 966101943.1025.bwgb550.vt.siemens.de
sourcedg disabled 1007210557.3627.bwgb550.vt.siemens.de
dokudg enabled 940102215.1973.bwgb550.vt.siemens.de
toolsdg enabled 944403128.1335.bwgb550.vt.siemens.de

And also the /etc/fdmns/source_domain
is only showing this and no disks,

SERVER1:/etc/fdmns/source_domain> ls -l
total 0
lrwxrwxrwx 1 root system 28 Apr 19 2003 sourcedg.vol_source->/dev/vol/sourcedg/vol_source

That means even though the disks are accessible by the system "scu show edt" , somehow LSM should recognise it.
Any thoughts?
Venkatesh BL Expert in this area This member has accumulated 2500 or more points
Nov 4, 2009 06:20:22 GMT    Unassigned

The devices won't be visible under /etc/fdmns directory when you are using LSM for the domain. So, your current task should be to 'enable' the volumes that are currently disabled. I will check and let you know if I find something.
admin1979
Nov 4, 2009 06:23:24 GMT    N/A: Question Author

Yes you are right. That is what I am trying to find out somehow to enable the volume which is disabled as the I/O was disturbed.
So now the situation is Disks are present, Data is present , rest all LSM is working. Only problem with the source_domain/sourcedg.

We wish to try out all the options before we decide to reboot. Please let us know if you have anything in mind.
Thanx.
Venkatesh BL Expert in this area This member has accumulated 2500 or more points
Nov 4, 2009 06:31:10 GMT    Unassigned

Hi,

Try this: http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/ARH9BDTE/TITLE.HTM

There is a 'Troubleshooting' section as well.

Good luck!
admin1979
Nov 4, 2009 06:32:59 GMT    N/A: Question Author

Its V4.0D , let me go through the required section in it.

Thinking of volrecover command maybe. Dont know the implications though.
Venkatesh BL Expert in this area This member has accumulated 2500 or more points
Nov 4, 2009 06:54:32 GMT  5 pts

4.0D is out of support :(

4.0F manual is available here: http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/AQ3NCETE/TITLE.HTM
admin1979
Nov 4, 2009 06:56:36 GMT    N/A: Question Author

I know :( ...but trying to match 4.0F so far.
Lets see. Will volrestore for that specific domain work here as we have the backup taken of the working LSM?
admin1979
Nov 5, 2009 08:26:03 GMT   Thread closed by author  

Thanx
 
Create a new message    Receive e-mail notification if a new reply is posted   Reply to this message
 
 
Printable version
Privacy statement Using this site means you accept its terms
© 2009 Hewlett-Packard Development Company, L.P.