05-04-2018
Long time since i used one of those.
Only thing i can do is pop a two node cluster and virtualbox and test following documentation.
If i catch some time during this weekend i'll give a shot, since i need an iscsi setuped for that as well.
Regards
Peasant.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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 (1 Reply)
Discussion started by: Shreeram Rane
1 Replies
2. Solaris
Hi
i have created a solaris zone but have not yet connected any network cables for this new zone,
can i set the zone up without running the command 'add net' and not adding an ip or physical interface?
i tried to add dummy internet settings and get this
zonecfg:coddr> add net... (4 Replies)
Discussion started by: newbiesolaris10
4 Replies
3. Solaris
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... (3 Replies)
Discussion started by: nm146332
3 Replies
4. Solaris
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. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
6. Solaris
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
7. Solaris
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 ... (0 Replies)
Discussion started by: milindphanse604
0 Replies
8. Solaris
I have a question about losing a node in a zone cluster. Hopefully I can explain enough for someone to answer.
Let's say I have a zone cluster spread over 3 physical nodes. If Node1 crashes, would I be correct in assuming I would lose all zones on Node1?
If I lost Node1 below, would I lose... (4 Replies)
Discussion started by: MasonJ
4 Replies
9. Solaris
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
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)