12-05-2008
Quote:
Originally Posted by
samar
Hi grus,
has anybody tried for Sun cluster interconnect normal cable ,, I mean not interconnect .. What do u think ..does it support this ?
Not long ago I tried Veritas cluster and its interconnections work great with normal cable .. I wonder what will Sun cluster say to it
)
on what kind of hardware do you try veritas cluster? modern hardware does a "autocrossover" even with a normal patch cable. so i think this is a hardware function and has nothing to do with the cluster software...
9 More Discussions You Might Find Interesting
1. High Performance Computing
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
2. IP Networking
Hi,
I'm trying to communicate two servers (HP DLProliant 380 G5) via a crossover cable, but I don't get them to ping each other.
I am working in RHEL 4.
These are the steps I've performed:
1) Plugged the crossover cables in eth2.
(note: The cable is brand new. Also I built one myself... (3 Replies)
Discussion started by: jrodriguez365
3 Replies
3. Solaris
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
4. Solaris
Hello
I have problem with scinstall. I found information that i should`t configure public network before using scinstall.
Each node configuration:
4 node, 3 network adapter on each node. 1 for public adapter and 2 for cluster interconnect. Two switches.
After scinstall first node is... (1 Reply)
Discussion started by: time0ut
1 Replies
5. Solaris
Any body can tell me where i can download sun cluster installation and configuration video.
is there any option to install cluster in 32 bit virtual machine.
please help (4 Replies)
Discussion started by: sunnybee
4 Replies
6. Solaris
Hi all,
I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly.
Here is my server T5440 info:
... (6 Replies)
Discussion started by: insatiable1610
6 Replies
7. 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
8. Hardware
Hello,
I have a spare SUN server X4200 with a DC PSU (oracle part number 300-2186)
The PSU is the one in the photo
I was looking in the net about what cable i can order but i couldn't find anything that fit there :)
Any idea?
Thanks! (2 Replies)
Discussion started by: @dagio
2 Replies
9. Solaris
Running Sun Cluster v3.2 it appears. Two clustered physcial servers both running Solaris 10.
Both servers run a number of Oracle DBs etc. BUT I'm a bit concerned that its been set up but will never switch in the even of failure of one of the hosts?
Some of the cluster groups we've... (3 Replies)
Discussion started by: psychocandy
3 Replies
LEARN ABOUT OPENSOLARIS
scsetup
scsetup(1M) System Administration Commands scsetup(1M)
NAME
scsetup - interactive cluster configuration tool
SYNOPSIS
scsetup [-f logfile]
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 scsetup command provides the following configuration capabilities, depending on what state the cluster is in when you issue the com-
mand:
o When you run the scsetup command at post-installation time, the command performs initial setup tasks, such as configuring quorum
devices and resetting the installmode property. If you did not use automatic quorum configuration when you created the cluster,
run the scsetup command immediately after the cluster is installed. Ensure that all nodes have joined the cluster before you run
the scsetup command and reset the installmode property.
If you used automatic quorum configuration when you created the cluster, you do not need to run the scsetup command after clus-
ter installation. The automatic quorum configuration feature also resets the installmode property of the cluster.
o When you run the command during normal cluster operation, the scsetup command provides a menu-driven utility. You can use this
utility to perform most ongoing cluster-administration tasks.
o When you issue the command from a node that is in noncluster mode, the scsetup utility provides a menu-driven utility for chang-
ing and displaying the private IP address range. You must reboot all nodes into noncluster mode before you start this form of
the scsetup utility.
You can issue the scsetup command from any node in the cluster.
You can use this command only in the global zone.
OPTIONS
The following options are supported:
-f logfile Specifies the name of a log file to which commands can be logged. If you specify this option, most command sets that
the scsetup utility generates are run and logged, or only logged, depending on user responses.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes.
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
Intro(1CL), cltelemetryattribute(1CL), cldevicegroup(1CL), clnode(1CL), clquorum(1CL), clreslogicalhostname(1CL), clresourcegroup(1CL),
clresourcetype(1CL), clressharedaddress(1CL), cluster(1CL),
Sun Cluster 3.2 18 Jul 2006 scsetup(1M)