Sponsored Content
Operating Systems Solaris Global device issue in sun cluster3.2 Post 302378681 by fugitive on Tuesday 8th of December 2009 12:54:22 PM
Old 12-08-2009
Global device issue in sun cluster3.2

In my 2 node cluster (sun cluster3.2) running on x86 VMs. One of my nodes VM1 does not have the global devices populated due to which i cannot failover my file system to node VM1 , what could be the reason for this and how can i rectify it ?

Code:
VM1:/>cd /dev/global
-bash: cd: /dev/global: No such file or directory
VM1:/>

Code:
VM2:/>cd /dev/global
VM2:/dev/global>ls
admin  dsk    rdsk   rmt
VM2:/dev/global>

Code:
VM2:/>clnode status

=== Cluster Nodes ===

--- Node Status ---

Node Name                                       Status
---------                                       ------
VM2                                             Online
VM1                                             Online

VM2:/>clq status

=== Cluster Quorum ===

--- Quorum Votes Summary from latest node reconfiguration ---

            Needed   Present   Possible
            ------   -------   --------
            2        3         3


--- Quorum Votes by Node (current status) ---

Node Name       Present       Possible       Status
---------       -------       --------       ------
VM2             1             1              Online
VM1             1             1              Online


--- Quorum Votes by Device (current status) ---

Device Name       Present      Possible      Status
-----------       -------      --------      ------
d3                1            1             Online

VM2:/>cldev status

=== Cluster DID Devices ===

Device Instance               Node              Status
---------------               ----              ------
/dev/did/rdsk/d2              VM1               Ok
                              VM2               Ok

/dev/did/rdsk/d3              VM1               Ok
                              VM2               Ok

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Changing boot device on a Sun box

I need to change the boot slice on a Sun box, more specifically the alias of "disk". When I do a printenv from the ok prompt, it lists "boot-device disk net", but when it boots, it is looking at the wrong slice on "disk" (3 Replies)
Discussion started by: 98_1LE
3 Replies

2. UNIX for Dummies Questions & Answers

Setting a boot device alias on Sun hardware

I watched this done a long time ago, but cannot find it anywhere. I need to alias the boot device "disk" to /sbus@7,0/QLGC,isp@0,10000/sd@c,0 I think I need to set "use-nvramrc?" to true, and then create an alias within the nvramrc to point disk to the boot disk, but this is the step I cannot... (3 Replies)
Discussion started by: 98_1LE
3 Replies

3. Solaris

sun cluster3.2, d3 and d8 are shown as failed

Hello, This is a 2 node sun cluster 3.2 on solaris 10(x86) I am using an unique ~512M disk (c0d1) on each node and slice 6 on this disk for globaldevices. While everything looks like fine, the 'Fail' is bothering me. @ tommy_sun1 @tommy_sun -bash-3.00# cldevice refresh... (10 Replies)
Discussion started by: upengan78
10 Replies

4. Solaris

Increasing Raw device Sun Cluster 3.0

Hi All , I would like to know the procedure for increasing shared volume space in sun cluster . Currently the configuration is like these . Main stripe oradb1/d91 2 1 /dev/did/rdsk/d35s0 1 /dev/did/rdsk/d36s0 =Total 49 Gb oradb1/d94 -p oradb1/d91 -o 88080480 -b 14680064 ==Total 7 GB... (4 Replies)
Discussion started by: sahil_shine
4 Replies

5. Virtualization and Cloud Computing

Sun Cluster3.2 on Vmware Server2.0

I'm trying to configure sun cluster 3.2 on vmware server 2.0 on windows xp host with solaris 10x86 guests VM3 and VM4 and i 'm running scinstall from VM4 .. it fails with following error Initializing cluster name to "laptop" ... done Initializing authentication options ... done Initializing... (0 Replies)
Discussion started by: fugitive
0 Replies

6. Solaris

Sun Cluster3.2 And Oracle10g

I want to configure Sun Cluster3.2 with Oracle10g ... i created 4 resources namely , logical host, sotrage, oracle -server & Listener .. all work fine butoracle resource does not come up .. though i can bring up the oracle outside sun cluster. node1:/>clrg online ora-rg clrg: (C450598) On... (1 Reply)
Discussion started by: fugitive
1 Replies

7. Red Hat

Device eth0 issue

Hi, I have just installed RHEL 5.4 on a BL430c-class server and I am attempting to connect to the network only when I try and start eth0, I get the following error? "Bringing up Interface eth0: hp device eth0 does not seem to be present, delaying initialization." I am using a HP... (18 Replies)
Discussion started by: Duffs22
18 Replies

8. Solaris

Emcpower0a device/lun is not visible in non global zone

Hi All Please find my zone configuration after add emcpower0a device zonecfg -z zone1 export create -b set zonepath=/zone/zone1 set autoboot=true set ip-type=shared add net set address=192.168.1.11/24 set physical=nxge2 set defrouter=192.168.1.1 end add device set... (4 Replies)
Discussion started by: sb200
4 Replies

9. Solaris

Can we add Oracle ASM in sun cluster3.3 or 4.0 in failover mode

Hi I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies
global_group(3erl)					     Erlang Module Definition						global_group(3erl)

NAME
global_group - Grouping Nodes to Global Name Registration Groups DESCRIPTION
The global group function makes it possible to group the nodes in a system into partitions, each partition having its own global name space, refer to global(3erl) . These partitions are called global groups. The main advantage of dividing systems to global groups is that the background load decreases while the number of nodes to be updated is reduced when manipulating globally registered names. The Kernel configuration parameter global_groups defines the global groups (see also kernel(7) , config(5) : {global_groups, [GroupTuple]} Types: * GroupTuple = {GroupName, [Node]} | {GroupName, PublishType, [Node]} * GroupName = atom() (naming a global group) * PublishType = normal | hidden * Node = atom() (naming a node) A GroupTuple without PublishType is the same as a GroupTuple with PublishType == normal . A node started with the command line flag -hidden , see erl(1) , is said to be a hidden node. A hidden node will establish hidden connec- tions to nodes not part of the same global group, but normal (visible) connections to nodes part of the same global group. A global group defined with PublishType == hidden , is said to be a hidden global group. All nodes in a hidden global group are hidden nodes, regardless if they are started with the -hidden command line flag or not. For the processes and nodes to run smoothly using the global group functionality, the following criteria must be met: * An instance of the global group server, global_group , must be running on each node. The processes are automatically started and syn- chronized when a node is started. * All involved nodes must agree on the global group definition, or the behavior of the system is undefined. * All nodes in the system should belong to exactly one global group. In the following description, a group node is a node belonging to the same global group as the local node. EXPORTS
global_groups() -> {GroupName, GroupNames} | undefined Types GroupName = atom() GroupNames = [GroupName] Returns a tuple containing the name of the global group the local node belongs to, and the list of all other known group names. Returns undefined if no global groups are defined. info() -> [{Item, Info}] Types Item, Info -- see below Returns a list containing information about the global groups. Each element of the list is a tuple. The order of the tuples is not defined. {state, State} : If the local node is part of a global group, State == synced . If no global groups are defined, State == no_conf . {own_group_name, GroupName} : The name (atom) of the group that the local node belongs to. {own_group_nodes, Nodes} : A list of node names (atoms), the group nodes. {synced_nodes, Nodes} : A list of node names, the group nodes currently synchronized with the local node. {sync_error, Nodes} : A list of node names, the group nodes with which the local node has failed to synchronize. {no_contact, Nodes} : A list of node names, the group nodes to which there are currently no connections. {other_groups, Groups} : Groups is a list of tuples {GroupName, Nodes} , specifying the name and nodes of the other global groups. {monitoring, Pids} : A list of pids, specifying the processes which have subscribed to nodeup and nodedown messages. monitor_nodes(Flag) -> ok Types Flag = bool() Depending on Flag , the calling process starts subscribing ( Flag == true ) or stops subscribing ( Flag == false ) to node status change messages. A process which has subscribed will receive the messages {nodeup, Node} and {nodedown, Node} when a group node connects or discon- nects, respectively. own_nodes() -> Nodes Types Nodes = [Node] Node = node() Returns the names of all group nodes, regardless of their current status. registered_names(Where) -> Names Types Where = {node, Node} | {group, GroupName} Node = node() GroupName = atom() Names = [Name] Name = atom() Returns a list of all names which are globally registered on the specified node or in the specified global group. send(Name, Msg) -> pid() | {badarg, {Name, Msg}} send(Where, Name, Msg) -> pid() | {badarg, {Name, Msg}} Types Where = {node, Node} | {group, GroupName} Node = node() GroupName = atom() Name = atom() Msg = term() Searches for Name , globally registered on the specified node or in the specified global group, or -- if the Where argument is not provided -- in any global group. The global groups are searched in the order in which they appear in the value of the global_groups configuration parameter. If Name is found, the message Msg is sent to the corresponding pid. The pid is also the return value of the function. If the name is not found, the function returns {badarg, {Name, Msg}} . sync() -> ok Synchronizes the group nodes, that is, the global name servers on the group nodes. Also check the names globally registered in the current global group and unregisters them on any known node not part of the group. If synchronization is not possible, an error report is sent to the error logger (see also error_logger(3erl) ). Failure: {error, {'invalid global_groups definition', Bad}} if the global_groups configuration parameter has an invalid value Bad . whereis_name(Name) -> pid() | undefined whereis_name(Where, Name) -> pid() | undefined Types Where = {node, Node} | {group, GroupName} Node = node() GroupName = atom() Name = atom() Searches for Name , globally registered on the specified node or in the specified global group, or -- if the Where argument is not provided -- in any global group. The global groups are searched in the order in which they appear in the value of the global_groups configuration parameter. If Name is found, the corresponding pid is returned. If the name is not found, the function returns undefined . NOTE
In the situation where a node has lost its connections to other nodes in its global group, but has connections to nodes in other global groups, a request from another global group may produce an incorrect or misleading result. For example, the isolated node may not have accurate information about registered names in its global group. Note also that the send/2,3 function is not secure. Distribution of applications is highly dependent of the global group definitions. It is not recommended that an application is distributed over several global groups of the obvious reason that the registered names may be moved to another global group at failover/takeover. There is nothing preventing doing this, but the application code must in such case handle the situation. SEE ALSO
erl(1) , global(3erl) Ericsson AB kernel 2.14.3 global_group(3erl)
All times are GMT -4. The time now is 04:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy