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..
Login or Register to Ask a Question

Previous Thread | Next Thread

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
Login or Register to Ask a Question
scprivipadm(1M) 					  System Administration Commands					   scprivipadm(1M)

NAME
scprivipadm - administer the private IP address range SYNOPSIS
scprivipadm -c netaddr=netaddr[,netmask=netmask] scprivipadm -c netaddr=netaddr[,maxnodes=nodes,maxprivatenets=privnets] scprivipadm -c netaddr=netaddr[,netmask=netmask,maxnodes=nodes,maxprivatenets=privnets] scprivipadm -p scprivipadm -R 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 scprivipadm command modifies the current IP address range that is assigned to the Sun Cluster private interconnect. All nodes in the cluster must be in noncluster mode before you run any form of this command. Run this command from one node in the cluster. The scprivipadm command takes as input the private network address. Optionally, the command also takes one or both of the following: o The netmask o The maximum number of nodes and the maximum number of private networks that are ever expected to be in the cluster The command then performs the IP address assignment for the physical adapters and the per-node IP addresses. You can use this command only in the global zone. OPTIONS
The following options are supported: -c Modifies the IP address range that is currently assigned to the cluster. Run the -c option on each node of the cluster. You can use this option only in the global zone. The -c option supports the following suboptions: netaddr=netaddr Specifies the private network address netmask=netmask Specifies the netmask maxnodes=nodes Specifies the maximum expected number of nodes in the cluster maxprivatenets=privnets Specifies the maximum expected number of private networks in the cluster The -c option performs the following tasks for each combination of suboptions: o If you specify the netaddr suboption alone, the command assigns the default netmask, 255.255.248.0, to the private interconnect. The default IP address range accommodates a maximum of 64 nodes and 10 private networks. o If you also specify the netmask suboption, the value that you specify must be equal to or greater than the default netmask. If the specified netmask is less than the default netmask, the command fails and exits with an error. If the specified netmask is equal to or greater than the default netmask, the command assigns the specified netmask to the private interconnect. The resulting IP address range can accommodate a maximum of 64 nodes and 10 private net- works. To assign a smaller IP address range than the default, specify the maxnodes and maxprivatenets suboptions. o If you also specify the maxnodes and maxprivatenets suboptions, the command calculates the minimum netmask to sup- port the specified number of nodes and private networks. The command then assigns the calculated netmask to the private interconnect. The maximum value for nodes is 64 and the minimum value is 2. The maximum value for privnets is 128 and the minimum value is 2. o If you also specify the netmask suboption as well as the maxnodes and maxprivatenets suboptions, the command calcu- lates the minimum netmask that supports the specified number of nodes and private networks. The command compares that calculation to the specified netmask. If the specified netmask is less than the calculated netmask, the com- mand fails and exits with an error. If the specified netmask is equal to or greater than the calculated netmask, the command assigns the specified netmask to the private interconnect. The maximum value for nodes is 64 and the minimum value is 2. The maximum value for privnets is 128 and the minimum value is 2. If the -c option fails, you must run the -R option on each node to repair the configuration before you rerun the -c option. Users other than superuser require solaris.cluster.modify Role-Based Access Control (RBAC) authorization to use this subcom- mand. See the rbac(5) man page. -R Repairs the cluster configuration. Use this option if the command fails while modifying the IP address range on the cluster nodes and the failure results in inconsistent cluster configuration on the nodes. You can use this option only in the global zone. Run the -R option on each node of the cluster. The -R option repairs the cluster configuration and removes any inconsistencies that were caused by a failure to modify the IP address range on all nodes. If you attempt to rerun the -c option without first running the -R option, the configuration change might again fail. Users other than superuser require solaris.cluster.modify Role-Based Access Control (RBAC) authorization to use this subcom- mand. See the rbac(5) man page. -p Displays the current private network address that is assigned to the private interconnect. Run the -p option from any node. You can use this option only in the global zone. The -p option prints the following information: o The private network address o The IP address range in the form of a netmask o The maximum number of nodes and the maximum number of private networks that can be supported by the IP address range Users other than superuser require solaris.cluster.read Role-Based Access Control (RBAC) authorization to use this subcommand. See the rbac(5) man page. To display the current private network address from a node that is in cluster mode, instead run the scconf -p command or the cluster show-netprops command. EXAMPLES
Example 1 Calculating a Custom Private IP Address Range The following command specifies the private network address 172.16.0.0 and calculates the netmask. The command specifies that the calcu- lated netmask must support up to sixteen nodes and up to four private networks in the cluster. # scprivipadm -c netaddr=172.16.0.0,maxnodes=16,maxprivatenets=4 Example 2 Specifying a Private Network Address and Netmask The following command specifies the private network address 172.16.0.0 and the netmask 255.255.248.0. # scprivipadm -c netaddr=172.16.0.0,netmask=255.255.248.0 EXIT STATUS
The scprivipadm command returns with a non-zero value if either of the following conditions occur: o Invalid arguments were provided. o The command was unable to successfully modify the IP address range on all nodes of the cluster. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cluster(1CL), scconf(1M), scinstall(1M), netmasks(4), networks(4), rbac(5) Sun Cluster Software Installation Guide for Solaris OS, Sun Cluster System Administration Guide for Solaris OS, System Administration Guide: IP Services NOTES
The superuser can run all forms of this command. Users other than superuser require RBAC authorizations. See the following table. +-------+---------------------------------------------------------+ |Option | RBAC Authorization | +-------+---------------------------------------------------------+ |-c | solaris.cluster.modify | +-------+---------------------------------------------------------+ |-R | solaris.cluster.modify | +-------+---------------------------------------------------------+ |-p | solaris.cluster.read | +-------+---------------------------------------------------------+ Sun Cluster 3.2 23 Jun 2006 scprivipadm(1M)