Sun Cluster3.2 on Vmware Server2.0

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Sun Cluster3.2 on Vmware Server2.0
# 1  
Old 12-04-2009
Sun Cluster3.2 on Vmware Server2.0

I'm trying to configure sun cluster 3.2 on vmware server 2.0 on windows xp host with solaris 10x86 guests VM3 and VM4 and i 'm running scinstall from VM4 .. it fails with following error
Code:
Initializing cluster name to "laptop" ... done
Initializing authentication options ... done
Initializing configuration for adapter "e1000g1" ... done
Initializing configuration for adapter "e1000g2" ... done
Initializing configuration for switch "switch1" ... done
Initializing configuration for switch "switch1" ... failed

Log file - /var/cluster/logs/install/scinstall.log.3003


Failed to configure "VM3".

Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Can we add Oracle ASM in sun cluster3.3 or 4.0 in failover mode

Hi I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies

2. Solaris

Sun Cluster3.2 And Oracle10g

I want to configure Sun Cluster3.2 with Oracle10g ... i created 4 resources namely , logical host, sotrage, oracle -server & Listener .. all work fine butoracle resource does not come up .. though i can bring up the oracle outside sun cluster. node1:/>clrg online ora-rg clrg: (C450598) On... (1 Reply)
Discussion started by: fugitive
1 Replies

3. Solaris

Ping Sun Solaris 10 on VmWare

Hi, i installed Sun Solaris 10 on VmWare Workstation 6.5 on my Windwos Vista PC. I would to ping solaris virtual machin froma my pc, but i can't do that. Can help me?! I'm sorry for my bad English. akela87 (2 Replies)
Discussion started by: akela87
2 Replies

4. Solaris

Global device issue in sun cluster3.2

In my 2 node cluster (sun cluster3.2) running on x86 VMs. One of my nodes VM1 does not have the global devices populated due to which i cannot failover my file system to node VM1 , what could be the reason for this and how can i rectify it ? VM1:/>cd /dev/global -bash: cd: /dev/global: No... (1 Reply)
Discussion started by: fugitive
1 Replies

5. Solaris

sun cluster3.2, d3 and d8 are shown as failed

Hello, This is a 2 node sun cluster 3.2 on solaris 10(x86) I am using an unique ~512M disk (c0d1) on each node and slice 6 on this disk for globaldevices. While everything looks like fine, the 'Fail' is bothering me. @ tommy_sun1 @tommy_sun -bash-3.00# cldevice refresh... (10 Replies)
Discussion started by: upengan78
10 Replies

6. Solaris

Adding new Hdd in sun 10 with vmware workstation

hi, i am using vmware workstation 6.0 and i installed sun solaris 10. when i add new hard disk(vm->>settings->>add). when i start the system and try to use format command there i only see my old one hdd (new added hdd is not showing). but my new hdd is showing at the bottom right as a icon where... (2 Replies)
Discussion started by: Anand15880
2 Replies

7. Solaris

Can not detect NIC on Sun 9 in VMware

Dear All, I had install SUn 9/05 on vmware workstation 6.5.0. Before install I see OS detect NIC, but after install I don't see any NIC. I have attack some picture to show my problem. Could someone have experience to help me resolve. I'm newbee in this unix eviroment. Thanks Hoavn (2 Replies)
Discussion started by: hoavn
2 Replies

8. Solaris

cant setup network Sun Solaris 10 on Vmware

Hi all, I have install sun solaris 10 on vmware server and i cant ping the solaris guest machine from the host and vice versa. The enable network card in the host machine is an wifi card so I know that i can't use bridged network from Vmware. I tried to use host or NAT but it seem not to work... (1 Reply)
Discussion started by: papiseckfr
1 Replies

9. Solaris

How to install Sun Solaris 10 inside VMware Workstation 5.5

Some members asked about this way, click Here u will find what u want (1 Reply)
Discussion started by: Sound Of Wisdom
1 Replies
Login or Register to Ask a Question
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)