Sponsored Content
Operating Systems Solaris High Availability zone on Sun Cluster Post 302508739 by DukeNuke2 on Tuesday 29th of March 2011 01:24:47 AM
Old 03-29-2011
and where is the problem? there are 3 different (if i remember right) configurations in the documentation for HA zones in solaris cluster...

Installing and Configuring Zones (Oracle Solaris Cluster Data Service for Solaris Containers Guide)
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

iscsi high availability

Hi, I want to set up a iscsi high availability with sheepdog distributed storage. Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies

2. 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

3. Red Hat

Red Hat High Availability (HA) Cluster

How can we implement a service in HA, which in not available in HA. like sldap or customize application. Requirement Details. NODE1 service slapd is running.(Require) NODE2 service slapd is running.(Require) on both the node replication is happening. Now here requirement is need... (2 Replies)
Discussion started by: Priy
2 Replies

4. Solaris

High availability

hi guys I posted problem last time I didn't find answer to my issue. my problem is as below: I have two servers which work as an actif/standby in high availability system. but when i use command HASTAT -a i have the following message: couldn' find actif node. the servers are sun... (1 Reply)
Discussion started by: zineb06
1 Replies

5. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
scnas(1M)						  System Administration Commands						 scnas(1M)

NAME
scnas - manage network-attached storage (NAS) device configuration data for Sun Cluster. SYNOPSIS
scnas [-H] scnas -a [-H] [-n] -h device-name -t device-type -o specific-options [-f input-file] scnas -c [-H] [-n ] -h device-name -o specific-options [-f input-file] scnas -p [-H] [-h device-name] [-t device-type] scnas -r [-H ] -h device-name 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 scnas command manages NAS devices in a Sun Cluster configuration. To manage NAS directories in the cluster, use the scnasdir command. You can use the scnas command to create the NAS device configuration, to update the NAS type-specific properties, and to remove the device configuration from Sun Cluster. The options to this command are processed in the order in which they are typed on the command line. The scnas command can only be run from an active cluster node. The results of running the command are always the same, regardless of the nodethat is used. All forms of the scnas command accept the -H option. Specifying -H displays help information. All other options are ignored. Help informa- tion is also printed when scnas is run without options. The NAS device must be set up before using the scnas command to manage a NAS device. Refer to the documentation for the particular NAS device for procedures for setting up a device. You can use this command only in the global zone. OPTIONS
Basic Options The following options are common to all forms of the scnas command: -H If this option is specified on the command line at any position, the command prints help information. All other options are ignored and are not executed. Help information is also printed if scnas is run with no options. You can use this option only in the global zone. -n If this option is specified on the command line at any position, the scnas command only checks the usage and does not write the config- uration data. If the -n option is specified with the -f option, the scnas command checks the input file for the password. The following options modify the basic form and function of the scnas command. None of these options can be combined on the same command line. -a Specifies the add form of the scnas command. You can use this option only in the global zone. The -a option can be used to add a NAS device into the Sun Cluster configuration. Depending on the type of your NAS device, you might have to set additional properties. These required properties are also explained in the -t option description in the "Additional Options" section. -c Specifies the change form of the scnas command. The -c option is used to change specific NAS device properties. You can use this option only in the global zone. -r Specifies the remove form of the scnas command. The -r option is used to remove the NAS device from the Sun Cluster configuration. You can use this option only in the global zone. Before removing a device, all its exported directories must be removed by using scnasdir. -p Specifies the print form of the scnas command. You can use this option only in the global zone. When no other options are given, the -p option prints a listing of all the current NAS devices configured in Sun Cluster and all their associated properties. This option can be used with additional options to query a particular device or a particular type of device. Additional Options The following additional options can be combined with one or more of the previously described basic options to configure all properties for a device. The device does not need to be online to use these options. Refer to the SYNOPSIS section to see the options that can be used with each form of scnas. The additional options are as follows: -h device-name Use this option to specify the name of the NAS device in the Sun Cluster configuration. The device name identifies the device and can be used to remotely access the device by using rhs or telnet. This device name must be specified for the add, change, and remove forms of the scnas command. -t device-type The NAS device type. You must specify this option when you add a NAS device to the Sun Cluster configuration. The NAS device type is identified by the vendor name. You can specify either sun for a NAS device from Sun Microsystems, Inc. or netapp for a NAS device from Network Appliance, Inc. Different types of NAS devices have different or in some cases, no properties. -o specific-options Use this option to provide the properties that are specific to a NAS device type. For example, the NAS device from Network Appliance, Inc. has the following property: -o userid=userid Note - You do not specify properties for the NAS device from Sun Microsystems, Inc. As this device does not have any properties, the -f and -o options do not apply. The userid property is used by the cluster to perform administrative duties on the device. When you add a userid to the device configu- ration, you are prompted for its password. You can also place the password in a text file and use it by specifying the -f option. -finput-file For security reasons, the password cannot be specified in command-line options. To keep the password secure, place it in a text file and specify the file by using the -f option. If you do not specify an input file for the password, the command prompts for the pass- word. Note - You do not specify properties for the NAS device from Sun Microsystems, Inc. As this device does not have any properties, the -f and -o options do not apply. Set permissions of the input file to readable by root and prohibit access by either group or world. In the input file, the password cannot be entered across multiple lines. Leading white spaces and tabs are ignored. Comments begin with an unquoted pound (#) sign, and continue to the next new line. The parser ignores all comments. When you use an input file for the device user password, the # sign cannot be part of the password. EXAMPLES
Example 1 Adding a NAS Device From Sun Microsystems, Inc. to a Cluster The following scnas command adds a Sun Microsystems, Inc. storage system to the Sun Cluster configuration. # scnas -a -h sunnas1 -t sun Example 2 Adding a NAS Device From Network Appliance, Inc. to a Cluster The following scnas command adds a Network Appliance, Inc. storage system to the Sun Cluster configuration. # scnas -a -h netapp1 -t netapp -o userid=root Please enter password: Example 3 Removing a NAS Device From a Cluster The following scnas command removes a NAS device from the Sun Cluster configuration. # scnas -r -h sunnas1 EXIT STATUS
The following exit values are returned: 0 The command executed successfully. nonzero An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clnasdevice(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scnasdir(1M) Sun Cluster 3.2 6 Sep 2007 scnas(1M)
All times are GMT -4. The time now is 02:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy