Visit Our UNIX and Linux User Community


Sun cluster 4.0 - zone cluster failover doubt


 
Thread Tools Search this Thread
Operating Systems Solaris Sun cluster 4.0 - zone cluster failover doubt
# 1  
Old 08-09-2012
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 both. (Global zone and container zone).

(3) Can i have the cluster installed only in the zone and not the Global zone.

Kindly clarify the basics for me.
Thank you...

Thx,
NVA

Last edited by DukeNuke2; 08-09-2012 at 07:56 PM..

Previous Thread | Next Thread
Test Your Knowledge in Computers #929
Difficulty: Medium
Vernor Vinge's novel A Deepness in the Sky describes a spacefaring trading civilization thousands of years in the future that still uses the Unix epoch.
True or False?

10 More Discussions You Might Find Interesting

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

2. Red Hat

Linux Cluster failover issue

Hi Guys, I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me. How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies

3. Solaris

Solaris Cluster Failover based on scan rate

Dear Experts, If there is a possible Solaris Cluster failover to second node based on scan rate? I need the documentation If solaris cluster can do this. Thank You in Advance Edy (3 Replies)
Discussion started by: edydsuranta
3 Replies

4. Solaris

High Availability zone on Sun Cluster

HI Experts, Could some one help me in configuring high availability zone on Sun Cluster Reg: Sudhan (3 Replies)
Discussion started by: sudhan143
3 Replies

5. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards (3 Replies)
Discussion started by: sidharthmellam
3 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

Sun Cluster 3.1 failover

Hi, We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover? Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies

8. High Performance Computing

Veritas Cluster Server Management Console IP Failover

I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier. Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies

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

10. High Performance Computing

sun Cluster resource group cant failover

I have rcently setup a 4 node cluster running sun cluster 3.2 and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename> this worked ok. theni I tried to siwitch the zone to node a thei work... (14 Replies)
Discussion started by: lesliek
14 Replies
sccheck(1M)						  System Administration Commands					       sccheck(1M)

NAME
sccheck - check for and report on vulnerable Sun Cluster configurations SYNOPSIS
sccheck [-b] [-h nodename[,nodename]...] [-o output-dir] [-s severity] [-v verbosity] sccheck [-b] [-W] [-h nodename[,nodename]...] [-o output-dir] [-v verbosity] 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 sccheck utility examines Sun Cluster nodes for known vulnerabilities and configuration problems, and it delivers reports that describe all failed checks, if any. The utility runs one of these two sets of checks, depending on the state of the node that issues the command: o Preinstallation checks - When issued from a node that is not running as an active cluster member, the sccheck utility runs pre- installation checks on that node. These checks ensure that the node meets the minimum requirements to be successfully configured with Sun Cluster software. o Cluster configuration checks - When issued from an active member of a running cluster, the sccheck utility runs configuration checks on the specified or default set of nodes. These checks ensure that the cluster meets the basic configuration required for a cluster to be functional. The sccheck utility produces the same results for this set of checks regardless of which cluster node issues the command. The sccheck utility runs configuration checks and uses the explorer(1M) utility to gather system data for check processing. The sccheck utility first runs single-node checks on each nodename specified, then runs multiple-node checks on the specified or default set of nodes. Each configuration check produces a set of reports that are saved in the specified or default output directory. For each specified node- name, the sccheck utility produces a report of any single-node checks that failed on that node. Then the node from which sccheck was run produces an additional report for the multiple-node checks. Each report contains a summary that shows the total number of checks executed and the number of failures, grouped by check severity level. Each report is produced in both ordinary text and in XML. The DTD for the XML format is available in the /usr/cluster/lib/sccheck/checkre- sults.dtd file. The reports are produced in English only. The sccheck utility is a client-server program in which the server is started when needed by the inetd daemon. Environment variables in the user's shell are not available to this server. Also, some environment variables, in particular those that specify the non-default locations of Java and Sun Explorer software, can be overridden by entries in the /etc/default/sccheck file. The ports used by the sccheck utility can also be overridden by entries in this file, as can the setting for required minimum available disk space. The server logs error messages to syslog and the console. You can use this command only in the global zone. OPTIONS
The following options are supported: -b Specifies a brief report. This report contains only the summary of the problem and the severity level. Analysis and recommendations are omitted. You can use this option only in the global zone. You need solaris.cluster.system.read RBAC authorization to use this command option. See rbac(5). -h nodename[,nodename]... Specifies the nodes on which to run checks. If the -h option is not specified, the sccheck utility reports on all active cluster mem- bers. You can use this option only in the global zone. This option is only legal when issued from an active cluster member. -o output-dir Specifies the directory in which to save reports. You can use this option only in the global zone. The output-dir must already exist or be able to be created by the sccheck utility. Any previous reports in output-dir are overwritten by the new reports. If the -o option is not specified, /var/cluster/sccheck/reports.yyyy-mm-dd:hh:mm:ss is used as output-dir by default, where yyyy-mm- dd:hh:mm:ss is the year-month-day:hour:minute:second when the directory was created. -s severity Specifies the minimum severity level to report on. You can use this option only in the global zone. The value of severity is a number in the range of 1 to 4 that indicates one of the following severity levels: 1. Low 2. Medium 3. High 4. Critical Each check has an assigned severity level. Specifying a severity level will exclude any failed checks of lesser severity levels from the report. When the -s option is not specified, the default severity level is 0, which means that failed checks of all severity levels are reported. The -s option is mutually exclusive with the -W option. -v verbosity Specifies the sccheck utility's level of verbosity. You can use this option only in the global zone. The value of verbosity is a number in the range of 0 to 2 that indicates one of the following verbosity levels: o 0: No progress messages. This level is the default. o 1: Issues sccheck progress messages. o 2: Issues Sun Explorer and more detailed sccheck progress messages. You need solaris.cluster.system.read RBAC authorization to use this command option. See rbac(5). The -v option has no effect on report contents. -W Disables any warnings. The report generated is equivalent to -s 3. You can use this option only in the global zone. The -W option is mutually exclusive with the -s option. The -W option is retained for compatibility with prior versions of the sccheck utility. You need solaris.cluster.system.read RBAC authorization to use this command option. See rbac(5). EXIT STATUS
The following exit values are returned: 0 The command completed successfully. No violations were reported. 1-4 The code indicates that the highest severity level of all violations was reported. 100+ An error has occurred. Some reports might have been generated. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu, SUNWscsck | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ FILES
/etc/default/sccheck /usr/cluster/lib/sccheck/checkresults.dtd /var/cluster/sccheck/reports.yyyy-mm-dd:hh:mm:ss SEE ALSO
Intro(1CL), explorer(1M), sccheckd(1M), scinstall(1M), attributes(5) Sun Cluster Software Installation Guide for Solaris OS, Sun Cluster System Administration Guide for Solaris OS Sun Cluster 3.2 19 Sep 2006 sccheck(1M)

Featured Tech Videos