I am new to VCS but having exposure on IBM HACMP. My doubt is, whether there is command or procedure for cluster sync and c-spoc like option in Veritas Cluster similar to HACMP.
Hello guys,
I have a question regarding link aggregation / trunking in Solaris 9
Sun Trunking does not come by default in Solaris 9 unlike Solaris 10 where we can use the "dladm" command to trunk 4 physical NIC interfaces together.
My question is in Solaris 9. Will the configurations of... (1 Reply)
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Hi - Please help me to understand the Veritas Cluster fail-over capability.
We configured oracle database file system on veritas cluster file system and it is automatically failing-over from node 1 to node 2.
Does Veritas cluster softward have any option to fail-back from node 2 to node 1... (6 Replies)
hi, dear all
I get a problem "VCS ERROR V-16-2-13077 " on VCS 4.1 for Solaris 10.
I can not offline the host2 when the raid is bad.
I don't know the reason and how to offline host2 and switch to host1.
please help me, thank you!
the message of engine_A.log is :
... (2 Replies)
I am looking for a checklist, to audit the existing VCS (veritas cluster) setup on Solaris platform.
Please let me know points/things that should be audited/verified. (0 Replies)
Dear Friends,
I am using Linux system where one nfs share has been configured with rw,sync options. But when I use to check with exportfs -v command it does not show me the sync option I enabled in /etc/exports
My doubt is whether I need to use any other command or other options to see... (2 Replies)
To find all the files in your home directory that have been edited in some way since the last tar file, use this command:
find . -newer backup.tar.gz
Is anyone familiar with an older solution?
looking to identify files older then 15mins across several directories.
thanks,
manny (2 Replies)
Hi all....I have a Sun Ultra2 that I want to use with my PC monitor. I have purchased an adapter that does not work and I was told I need to change my video card setting (if I can) to Separate Sync.....my Monitor product number ends in 1343......I am running SunOS 5.7 ......anyone have any ideas?
... (0 Replies)
clu_get_info(8) System Manager's Manual clu_get_info(8)NAME
clu_get_info - Gets information about a cluster and its members
SYNOPSIS
/usr/sbin/clu_get_info [-full] [-q] [-m memberid] [-raw] [-state]
OPTIONS
The -full option returns detailed information about all members in the cluster, or about one member if the -m memberid option is specified.
Suppresses output. Use this option when only the return value is of interest; for example, to determine whether the system is running as a
cluster member. When specified in combination with the -m option, the -q option can be used to determine whether a particular member of a
cluster is up or down. For example: # clu_get_info -q -m 2 && echo "Member 2 is a member of the cluster" Member 2 is a member of the clus-
ter The -m option returns information about the member specified by memberid. The -raw option returns detailed information about the clus-
ter and all members in the cluster in raw output, which is intended to be used as input to scripts. The -state option returns the state of
all members in the cluster in raw output. The states returned are: UP, DOWN, or NOT_CONF (not configured).
DESCRIPTION
When invoked on a member of a cluster, the clu_get_info command displays general information about the cluster and its members. The infor-
mation includes: The name of the cluster and the number of members configured in the cluster. The member ID of the member issuing the com-
mand. The device name and number of votes of the quorum disk, if configured. For each member, its member ID, host name, cluster intercon-
nect IP name, and current state (UP or DOWN).
When invoked on a system that is not a cluster member, the clu_get_info command prints an error message and exits.
The clu_get_info -full option displays additional information about the cluster. The information includes: Cluster incarnation -- A hexa-
decimal number used to uniquely identify the cluster. Cluster expected votes -- Number of votes expected when all configured cluster mem-
bers are up and any configured quorum disk is present. Current votes -- The number of votes contributed by current cluster members and the
quorum disk as seen by this member. Quorum votes -- The number of votes required for the cluster to be up and running.
The clu_get_info -full command also displays the following information for each member: Cluster interconnect IP address -- The IP address
of the cluster interconnect. Member base O/S version -- The version of the base operating system. Member cluster version -- The version
of the TruCluster Server software. Member running version -- The current running version of the TruCluster software, which returns one of
the following: INSTALLED -- the current running version; same as the member cluster version returned. BELOW INSTALLED -- one version below
the current running version returned in member cluster version; useful when performing a rolling upgrade. UNKNOWN -- the running version
is unknown. Member name -- The member name used by the connection manager (CNX) as a member identifier. Node votes -- The votes assigned
to this member (as set in the cluster_node_votes kernel attribute for the clubase subsystem). csid -- The cluster system identifier, which
is a unique hexadecimal number that identifies each member in a cluster.
The clu_get_info -raw option displays detailed information, in raw output, about all members in the cluster. This output is intended to be
used as input to scripts. Data is unlabeled, and data fields are separated by colons. The fields returned are the same as if specifying the
-full option only data is in raw format.
The clu_get_info -raw option returns a clusterwide information record and member-specific information records. A clusterwide information
record begins with the initiator C and returns data in the following order: Cluster name Number of members configured in this cluster Mem-
ber ID for this member Cluster incarnation Cluster expected votes Current votes Votes required for quorum Quorum disk Quorum disk votes
A member-specific information record begins with the initiator M and returns data in the following order: Member ID Host name Cluster
interconnect IP name Cluster interconnect IP address Member state Member base O/S version Member cluster version Member running version
Member name Member votes Csid
The clu_get_info -state option displays the state of all members in the cluster. Output is intended to be used by a script to determine
which cluster members are up, down, or not configured. Data is unlabeled, and data fields are separated by colons.
A state information record begins with the initiator S and returns the following output based on the configuration state of all members in
the cluster: UP -- The member ID is configured and up. DOWN -- The member ID is configured and down. NOT_CONF -- The member ID is not
configured in the cluster.
If a member of the cluster is down, clu_get_info displays UNKNOWN in various member fields. If the member is down and its /etc/rc.config
file contains illegal values, clu_get_info displays CONFIGURATION_ERROR in the related fields. An example is provided in the EXAMPLES sec-
tion.
EXIT STATUS
Success. The system is not a cluster member or an error has occurred.
EXAMPLES
The following command displays general information about the cluster and its members: # clu_get_info
Cluster information for cluster deli
Number of members configured in this cluster = 3
Memberid for this member = 1
Quorum disk = dsk4h
Quorum disk votes = 1
Information on each cluster member
Cluster memberid = 1
Hostname = polishham.zk4.com
Cluster interconnect IP name = polishham-mc0
Member state = UP
Cluster memberid = 2
Hostname = provolone.zk4.com
Cluster interconnect IP name = provolone-mc0
Member state = UP
Cluster memberid = 3
Hostname = pepicelli.zk4.com
Cluster interconnect IP name = pepicelli-mc0
Member state = UP
If one member of the cluster is down and its rc.config file contains illegal values, the following is displayed:
Cluster memberid = 2
Hostname = CONFIGURATION_ERROR
Cluster interconnect IP name = CONFIGURATION_ERROR
Member state = DOWN The following command displays general information about one member: # clu_get_info -m 1
Cluster memberid = 1
Hostname = polishham.zk4.com
Cluster interconnect IP name = polishham-mc0
Member state = UP The following command displays more information about all members in the cluster: # clu_get_info -full
Cluster information for cluster deli
Number of members configured in this cluster = 3
Memberid for this member = 1
Cluster incarnation = 0x7b5c2
Cluster expected votes = 3
Current votes = 3
Votes required for quorum = 2
Quorum disk = dsk4h
Quorum disk votes = 1
Information on each cluster member
Cluster memberid = 1
Hostname = polishham.zk4.com
Cluster interconnect IP name = polishham-mc0
Cluster interconnect IP address = 10.0.0.1
Member state = UP
Member base O/S version = Compaq Tru64 UNIX V5.0A
Member cluster version = TruCluster Server V5.0A
Member running version = INSTALLED
Member name: polishham
Member votes = 1
csid = 0x10001
Cluster memberid = 2
Hostname = provolone.zk4.com
Cluster interconnect IP name = provolone-mc0
Cluster interconnect IP address = 10.0.0.2
Member state = UP
Member base O/S version = Compaq Tru64 UNIX V5.0A
Member cluster version = TruCluster Server V5.0A
Member running version = INSTALLED
Member name: provolone
Member votes: 1
csid = 0x10002
Cluster memberid = 3
Hostname = pepicelli.zk4.com
Cluster interconnect IP name = pepicelli-mc0
Cluster interconnect IP address = 10.0.0.3
Member state = UP
Member base O/S version = Compaq Tru64 UNIX V5.0A
Member cluster version = TruCluster Server V5.0A
Member running version = INSTALLED
Member name: pepicelli
Member votes: 1
csid = 0x10003
If one member of the cluster is down and its rc.config file contains illegal values, the following is displayed:
Cluster memberid = 2
Hostname = CONFIGURATION_ERROR
Cluster interconnect IP name = CONFIGURATION_ERROR
Cluster interconnect IP address = CONFIGURATION_ERROR
Member state = DOWN
Member base O/S version = CONFIGURATION_ERROR
Member cluster version = CONFIGURATION_ERROR
Member running version = UNKNOWN
Member name = UNKNOWN
Member votes = UNKNOWN
csid = UNKNOWN The following command displays more information about a particular member of the cluster: # clu_get_info -full -m 1
Cluster memberid = 1
Hostname = polishham.zk4.com
Cluster interconnect IP name = polishham-mc0
Cluster interconnect IP address = 10.0.0.1
Member state = UP
Member base O/S version = Compaq Tru64 UNIX V5.0A
Member cluster version = TruCluster Server V5.0A
Member running version = INSTALLED
Member name: polishham
Member votes: 1
csid = 0x10001 The following command displays detailed information about all members in the cluster in raw output: # clu_get_info
-raw
C:deli:3:2:0x7b5c2:3:3:2:(null):0 M:1:polishham.zk4.com:polishham-mc0:10.0.0.1:UP:Compaq Tru64 UNIX V5.0A: TruCluster Server
V5.0A:INSTALLED:polishham:1:0x10001 M:2:provolone.zk4.com:provolone-mc0:10.0.0.2:UP:Compaq Tru64 UNIX V5.0A: TruCluster Server
V5.0A:INSTALLED:provolone:1:0x10002 M:3:pepicelli.zk4.com:pepicelli-mc0:10.0.0.3:UP:Compaq Tru64 UNIX V5.0A: TruCluster Server
V5.0A:INSTALLED:pepicelli:1:0x10003 The following command displays the state of all members in the cluster: # clu_get_info -state
S:NOT_CONF:UP:UP:UP:NOT_CONF:NOT_CONF:NOT_CONF:NOT_CONF
FILES
Run-time configuration file for each cluster member.
SEE ALSO
Functions: clu_get_info(3)
Files: rc.config(8)
TruCluster Server Administration Guide
clu_get_info(8)