Sponsored Content
Operating Systems Solaris scconf crash: registering a Veritas local disk on Sun Cluster (localonly=true) Post 302347718 by gxmsgx on Wednesday 26th of August 2009 09:25:07 AM
Old 08-26-2009
Quote:
Originally Posted by Alessio Dini
it seems that is a bug mmm
If you try the registration with clsetup?
Is Vxvm 5.* ?
Hi Alessio,
thanks for reply.

VxVM 5.0: I've tried with:
Code:
 # cldg create -t vxvm -p localonly=true -n clab1 DGLOCAL

(the same command used by clsetup) this not explodes but fails ...without error output

/var/adm/messages
Code:
Aug 26 14:47:47 clab1 Cluster.CCR: [ID 801593 daemon.notice] stdout: 
Aug 26 14:47:47 clab1 Cluster.CCR: [ID 801593 daemon.notice] stderr:

I try to investigate better with truss and watching the CCR ...to be continued
 

9 More Discussions You Might Find Interesting

1. Solaris

veritas cluster

Hi I want to install VCS 5 on solaris 10 the product states it needs 3 nic cards. how to install it if I have 2 cards only (this is just for demo)? thank you for your help. (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

2. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

3. Solaris

Veritas Cluster

Can I make a veritas cluster on Sun vertual box or Vmwere. Please help me. (4 Replies)
Discussion started by: saga499
4 Replies

4. Solaris

True or false ? - Sun cluster 3.2 U3 questions...

I'm using clustered zones on my machine. i'm only at the test phase of my design and ultimately the oracle zones will be using VxVM. When the testing phase is complete, VxVM will be used in the containers. It is necessary for VxVM to run in the global zone for the containers to use it (is... (5 Replies)
Discussion started by: frustin
5 Replies

5. Solaris

Veritas Cluster

How to create your cluster members routes and manual nat, and proxy. (2 Replies)
Discussion started by: padmaja@tech
2 Replies

6. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

7. Solaris

Veritas disk group not the same on each cluster node.

Need help getting all disk devices back on node 2 the same as node 1. Recently Veritas and/or Sun cluster got wrecked on my 2 node Sun cluster after installing the latest patch cluster. I backed out the patches and then node 2 could see only half of the devices and Veritas drives (though format... (0 Replies)
Discussion started by: buggin
0 Replies

8. Solaris

Sun cluster 4.0 - zone cluster failover doubt

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)
Discussion started by: NVA
0 Replies

9. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
scconf_dg_rawdisk(1M)					  System Administration Commands				     scconf_dg_rawdisk(1M)

NAME
scconf_dg_rawdisk - add, change or update raw-disk device group configuration SYNOPSIS
scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true] scconf -a -D type=rawdisk, [generic_options] [,globaldev=gdev1,globaldev=gdev1,...] [,localonly=true | false] scconf -c -D name=diskgroup,autogen=true scconf -r -D device_service_name [,nodelist=node[:node]...] [,globaldev=gdev1,...] 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 following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. The scconf_dg_rawdisk utility adds, changes or updates raw-disk device group configuration A raw disk is a disk that is not being used as part of a volume manager volume or metadevice. Raw-disk device groups allow you to define a set of disks within a disk device group. At system boot, by default, a raw-disk device group is created for every Disk ID pseudo driver (DID) device in the configuration. By con- vention, the raw-disk device group names are assigned at initialization and are derived from the DID names. For every node added to a raw- disk disk device group, the scconf utility verifies that every device in the group is physically ported to the node. The scconf -a (add) command can be used to create a raw-disk device group with multiple disk devices configured in it. A raw-disk device group is created for every disk device in the cluster at boot time. Before you can add a new raw-disk device group, devices to be used in the new group must be removed from the device group created at boot time. Then a new raw-disk device group can be created containing these devices. This is accomplished by creating a list of these devices in the globaldev option of scconf along with a potential primary node preference list in the nodelist option. If the device group already exists, only new nodes and global devices will be added and nodes or devices which are part of an existing device group will be ignored. If the preferenced suboption is not given with the-a option to create a new device group, then it is, by default, false. However, if the preferenced suboption is specified for the existing device group with a value of true or false, an error is returned. This is done in order to maintain the existing nodelist preference state. If a device group should be mastered by only a particular node then it should be configured with the otheroption set to localonly=true. Only one node can be specified in the node list to create a localonly device group. The scconf -c (change) command is used to change the order of the potential primary node preference, to enable or disable failback, to set the desired number of secondaries, and to add more global devices to the device group. If you want to change the order of node preference list, then all the nodes currently existing in the device group must be specified in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced suboption to true. If the preferenced suboption is not specified with the change, the already established true or false setting is used. New nodes cannot be added using the change form of the command. Change option can also be used for changing a device group to localonly device group and vice-versa. To change a device group to a localonly device group, set otheroption to localonly=true. Specify localonly=false to set it back to not the localonly device group. nodelist must already be set to a list of one node, or an error results. It is legal to specify a nodelist with the change form of the command, when you set localonly to true. This is, however, redundant, since the list can only contain the single node that is already configured. It would be an error to specify any other than the node that is already configured. The scconf -r (remove) command can be used to remove the nodes, global devices, and the device group name from the cluster device-group configuration. If nodes or global devices are specified with the device-group name, they are removed from the device group first. After the last device and node are removed from the device group, the device group is also removed from cluster configuration. If only the name of the device group is given (no nodes or devices at all), the entire device group is removed. If a raw-disk device name is registered in a raw-disk device group, then it cannot be registered in a Solaris Volume Manager device group or a VERITAS Volume Manager device group. OPTIONS
See the scconf(1M) man page for the list of supported generic options. The following action options are used to describe the actions performed by the command. Only one action option is allowed in the command. The following action options are supported: -a Add a new raw-disk device group to the cluster configuration. You can also use this option to change the device group configuration. -c Change the ordering of the node preference list, change preference and failback policy, change the desired number of secondaries, and also add more devices to the device group with the globaldev option. It is also used to set a device group as local only. -r Remove the raw-disk device group name from the cluster. The autogen flag is an indicator of the scconf command. This command does not list devices with the autogen property unless the -v command line option is used. When a device is used with the change form of the scconf command, the device's autogen property is reset, or set to false, unless autogen=true is also specified. EXAMPLES
Example 1 Using scconf Commands The following scconf commands create a raw-disk device group, change the order of the potential primary nodes, change preference and fail- back policy, change the desired number of secondaries, and remove the raw-disk device group from the cluster configuration. host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1:host2:host3,preferenced=false,failback=enabled, numsecondaries=,globaldev=d1,globaldev=d2 host1# scconf -a -D type=rawdisk,name=rawdisk_groupname, nodelist=host1,globaldev=d1,globaldev=d2,localonly=true, globaldev=d1,globaldev=d2 host1# scconf -c -D name=rawdisk_groupname, nodelist=host3:host2:host1,preferenced=true,failback=disabled, numsecondaries=2,globaldev=d4,globaldev=d5 host1# scconf -c -D name=rawdisk_groupname,localonly=true host1# scconf -r -D name=rawdisk_groupname host1# scconf -r -D name=rawdisk_groupname,nodelist=host1,host2 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), attributes(5) Sun Cluster 3.2 13 Aug 2007 scconf_dg_rawdisk(1M)
All times are GMT -4. The time now is 08:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy