Sponsored Content
Special Forums UNIX and Linux Applications High Performance Computing Normal (not crossover) cable for Sun cluster interconnect.. Post 302265063 by samar on Friday 5th of December 2008 01:30:17 PM
Old 12-05-2008
Tools Normal (not crossover) cable for Sun cluster interconnect..

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 Smilie)
 

9 More Discussions You Might Find Interesting

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

2. IP Networking

Two Servers via ethernet crossover cable

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

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

4. Solaris

Cluster interconnect, adapter configuration

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

Sun cluster

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

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

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

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... (0 Replies)
Discussion started by: NVA
0 Replies

8. Hardware

Cable for SUN x4200 DC

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

Sun cluster v3.2 - Is this right?

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
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)
All times are GMT -4. The time now is 05:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy