Sponsored Content
Operating Systems AIX How to configure new hdisk such that it has a gpfs fs on it and is added to a running gpfs cluster? Post 302514830 by acerworld on Monday 18th of April 2011 08:04:22 AM
Old 04-18-2011
Cool ... thats quite simple...
Its explained well here....
http://aix4you.com/howto/gpfs-nsd-an...tem-operations
Goto www.aix4you.com website... check Howto Section for GPFS...

Last edited by zaxxon; 04-18-2011 at 09:12 AM.. Reason: reformatted links
This User Gave Thanks to acerworld For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

two gpfs in one node issue

dear all can i create two gpfs in one node each gpfs is pointing to single hdiskpower (1 Reply)
Discussion started by: thecobra151
1 Replies

2. AIX

SSD with GPFS ?

Hi, does anyone here happen to know if I could run GLVM or GPFS on Solid State Disks? I have a high volume / high transaction Sybase HACMP cluster currently setup with SRDF to the DR datacentre. My business now considers to move everything to SSD storage but we still need to get the data to... (0 Replies)
Discussion started by: zxmaus
0 Replies

3. AIX

AIX GPFS Setup

:cool:Hello, can someone guide me how to create a GPFS filesystem, I've read a couple of redbooks however certain things are still not certain, like if you require to download files or licenses... any help would be appreciated! (2 Replies)
Discussion started by: ollie01
2 Replies

4. AIX

GPFS

Hello I am interested if anybody uses GPFS and is it must to have GPFS in the POWERHA environment? and can GPFS work as cluster active active or active passive thanks in advance (0 Replies)
Discussion started by: Vit0_Corleone
0 Replies

5. AIX

GPFS 3.3

Dear all for the last few days i was searching in IBM web site for GPFS 3.3 to upgrade my gpfs from 3.2 to 3.3 and i did not find the download link for the GPFS 3.3 in IBM website please can anyone give me the link . (4 Replies)
Discussion started by: thecobra151
4 Replies

6. AIX

Should GPFS be configured before/after configuring HACMP for 2 node Cluster?

Hi, I have a IBM Power series machine that has 2 VIOs and hosting 20 LPARS. I have two LPARs on which GPFS is configured (4-5 disks) Now these two LPARs need to be configured for HACMP (PowerHA) as well. What is recommended? Is it possible that HACMP can be done on this config or do i... (1 Reply)
Discussion started by: aixromeo
1 Replies

7. AIX

How to get rid of GPFS ?

Hi We are doing the migration of DMX3 disks to DMX4 disks using migratepv. We are not using GPFS but we have gpfs disks present in the server. Can anyone advise how to get rid of GPFS in both the servers cbspsrdb01 and cbspsrdb02. I will do migratepv for the other disks present in the servers... (2 Replies)
Discussion started by: newtoaixos
2 Replies

8. AIX

Questions about setting up GPFS

Hello, I need to test whether our product will work with GPFS filesystems and I have some questions regarding the setup: 1. Do I need to dedicate an entire hard disk if I want to have GPFS on it? Or can I somehow split a disk into 2 virtual disks, and only use 1 for gpfs? 2. If lspv returns... (4 Replies)
Discussion started by: bstring
4 Replies

9. AIX

GPFS is too slow after installtion

we have implement GPFS 3.5.0.10 with 4 nodes cluster AIX 6.1 TL8 and they VIO clients , after that we noticed a big delay while we execute any command like mmgetstate -a will take about 2.5 minutes . time mmgetstate -a Node number Node name GPFS state ... (3 Replies)
Discussion started by: thecobra151
3 Replies

10. AIX

Difference between NFS and GPFS

Hello Gurus, Could you please help me out of the difference between GPFS and NFS. Thanks- P (1 Reply)
Discussion started by: pokhraj_d
1 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)
All times are GMT -4. The time now is 01:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy