02-21-2012 06:22 PM
Hi All,
I'm running vcs and vxfs on solaris 10 with DMP. Recently we had an issue which all vx* command were hung.
It cause the several service group was unable to start. Not much thing i can check because all vx* command is not responding.
From /var/adm/messages, the repeating error comes out. It comes from all disk.
The version detail as below:-
Solved! Go to Solution.
02-22-2012 06:47 AM
Hello,
1. which storage is connected to server ?
2. are you sure that storage connectivity is all OK & no errors are seen on storage or fabric switch ?
3. when u restarted the node, did u face the problem immediately or you were able to run commands for sometime ?
4. Is this a new config or was working before ?
also paste following outputs (if commands work for sometime):
# ps -ef | grep -i vxconfigd
# vxdmpadm listenclosure all
# vxdmpadm listctlr all
#
Usually these issues I have seen because of SAN connectivity in background. If still you are unable to diagnose, you might need to enable additional logs by putting vxconfigd in debug mode (vxdctl debug 9) if command works .... or if issue is happening with start of server, you will need to edit the rc file for vxconfigd startup to enable extra logging.
output may be helpful by support to analyze.
Gaurav
02-21-2012 06:37 PM
i have check the fc, looks fine. I have tried to restart vxconfigd. uisng vxconfigd -k. But after that the services didnt start. I have rebooted the server. After a while the same problem comes again.
02-22-2012 06:47 AM
Hello,
1. which storage is connected to server ?
2. are you sure that storage connectivity is all OK & no errors are seen on storage or fabric switch ?
3. when u restarted the node, did u face the problem immediately or you were able to run commands for sometime ?
4. Is this a new config or was working before ?
also paste following outputs (if commands work for sometime):
# ps -ef | grep -i vxconfigd
# vxdmpadm listenclosure all
# vxdmpadm listctlr all
#
Usually these issues I have seen because of SAN connectivity in background. If still you are unable to diagnose, you might need to enable additional logs by putting vxconfigd in debug mode (vxdctl debug 9) if command works .... or if issue is happening with start of server, you will need to edit the rc file for vxconfigd startup to enable extra logging.
output may be helpful by support to analyze.
Gaurav