09-11-2015
Prevent crash dump when SG cluster node reboots
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey
10 More Discussions You Might Find Interesting
1. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
2. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
3. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
4. Solaris
My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary.
Thanks you.
Can I have any information about this ACT and SCAT... (2 Replies)
Discussion started by: csgonan
2 Replies
5. UNIX for Dummies Questions & Answers
Can anybody let me know the steps how can I produce a crash dump and then analyze it? (4 Replies)
Discussion started by: rupeshkp728
4 Replies
6. Solaris
Hi,
I'm running Solaris 10 with a zone called "testzone"
If I do a "reboot -d" on the host, as expected the kernet panics, reboots and creates a crash dump file in /var/crash
However no crash file is created in testzone.
My question is how can I tell if a zone crashs or shuts down... (4 Replies)
Discussion started by: fastexit
4 Replies
7. Solaris
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies
8. Solaris
Hi gurus,
I will be glad if anyone can help me with this:
How do you copy a crash dump file to send to your support provider?
Thanks lots guys. (1 Reply)
Discussion started by: cjashu
1 Replies
9. Solaris
Hello Guys,
I need a little help here. I have been studying crash dump and per what I am reading, you can dedicate a slice to use as a dump device. Now when you dedicate this slice, do you have to :
1) create a mount point?
2) add entry in /etc/vfstab?
3) is this slice wu or wm?
4) should... (3 Replies)
Discussion started by: cjashu
3 Replies
10. AIX
Dear all
i have two aix system
-Model : P770
-OS version: AIX 6.1
-patch level : 6100-07-04-1216
-ha version : HACMP v 6.1.0.8
-host : A, B
last Wednesday, my B system suddenly went down with crash dump. after 1 minute, A system went down with crash dump. I checked the dump of A-system... (6 Replies)
Discussion started by: tomato00
6 Replies
LEARN ABOUT OPENSOLARIS
scversions
scversions(1M) System Administration Commands scversions(1M)
NAME
scversions - Sun Cluster version management
SYNOPSIS
scversions [-c]
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
arguments, the scversions command prints a message indicating whether a commitment is needed.
OPERANDS
The following operands are supported:
-c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.
When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and
some new functionality introduced in the upgrade might be unavailable.
When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func-
tionality becomes available and any administrative restrictions are removed.
If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
command has no effect because the cluster is already running at the highest possible level of functionality.
If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.
EXIT STATUS
0 Success
non-zero Failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
scinstall(1M)
Sun Cluster 3.2 17 Aug 2007 scversions(1M)