Zone Cluster Question Post: 302755119

Sponsored Content

Operating Systems Solaris Zone Cluster Question Post 302755119 by MasonJ on Saturday 12th of January 2013 12:07:27 AM

01-12-2013

Registered User

My initial assessment was something another called a cluster, but I'm not sure it's really set up that way logically.

My assumption is that there are multiple hosts running zones with the same application through a load balancer. I'm thinking there's a miscommunication of the cluster terminology.

I don't feel the Solaris setup is really anywhere near something like VMware HA. The applications running have their own cluster as well, but it's at the application level.

Everyone seems to think that a node failure won't affect a zone associated with the node. I don't believe that's true in this setup, but I need to confirm it.

I'm working on getting information from the managed environment, but I'm from a linux/windows background and am trying to wrap my head around Oracle's terminology.

The documents I've read about failover/scalable scenarios somewhat confuse me more since the "how-tos" and documentation really don't explain much from a logical/feature/why perspective. I get a few paragraphs and then the commands to implement something basic. I need to know the "why" before running commands.

All-in-all, I'm aware certain things are possible. From the most basic "cluster" set-up, do you think my assumption would be correct.

EDIT: In addition, do you know any way for me to verify the setup. I'm not currently able to run commands on the hosts, but I would be able to submit a ticket to have the commands run. I'm working on getting access to the systems now, but that has not happened.

MasonJ

View Public Profile for MasonJ

Find all posts by MasonJ

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Veritas Cluster for Oracle on Soalris Zone

Hi, Does anyone has idea how to implement Veritas Cluster Server 5.3 (SF 5.3) for Oracle 10g on Solaris Zone (Containers). Please let me know any of you folks have worked on similar implementation and if you could pass on some information related to it. BR, Shreeram Rane

2. Solaris

Some Question's about Zone

Hi all, i am new learner in Zoning and virtualization Technology and i have some question's about it i create zone using this step zonecfg -z app-apache create set zonepath=/zone_adm/app-apache add net set address=192.168.1.250 set physical=bge0 end set autoboot=true verify commit...

3. Solaris

Applying Recommended Patch Cluster to Whole Root Zone

Hi there, Apologies if this question has been asked and answered already but I've not been able to find the thread. Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in...

4. 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. Solaris

High Availability zone on Sun Cluster

HI Experts, Could some one help me in configuring high availability zone on Sun Cluster Reg: Sudhan

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

7. Solaris

Help needed for patching on zone cluster

Hi All, Below is the configuration of my sun cluster. root@glob-one # clzc status === Zone Clusters === --- Zone Cluster Status --- Name Node Name Zone HostName Status Zone Status ---- --------- ------------- ------ ----------- data ...

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

9. Solaris

While creating Zone cluster getting error

Hi I have created the zone cluster and its Resource group but while creating the resource I am getting the below error "clrs: (C779822) Resource type SUNW.HAStoragePlus is not registered" but HAStoragePlus Resource type is already register. Please help me to get out of this situation. ...

LEARN ABOUT OPENSOLARIS

scversions

scversions(1M)						  System Administration Commands					    scversions(1M)

NAME

       scversions - Sun Cluster version management

SYNOPSIS

       scversions [-c]

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  scversions	command  commits  the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
       arguments, the scversions command prints a message indicating whether a commitment is needed.

OPERANDS

       The following operands are supported:

       -c	    Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.

		    When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
		    into  the  cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
		    rectly with other nodes in the cluster.  When the cluster is in this state, some administrative actions might be disabled  and
		    some new functionality introduced in the upgrade might be unavailable.

		    When  you  run  this  command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
		    internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new  func-
		    tionality becomes available and any administrative restrictions are removed.

		    If	a  node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
		    command has no effect because the cluster is already running at the highest possible level of functionality.

		    If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
		    ple,  if  that  node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
		    sions.  You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.

EXIT STATUS

       0	    Success

       non-zero     Failure

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWsczu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       scinstall(1M)

Sun Cluster 3.2 						    17 Aug 2007 						    scversions(1M)