After much hitting my head to the wall with this meesages
root@crasher /workzone/dvd4_sfb-sol_x64]#./installer -verbose -installonly
5.0MP3 Installation Program
Copyright (c) 2008 Symantec Corporation. All rights reserved. Symantec, the Symantec... (1 Reply)
Greetings Forumers!
I tried installing Solaris Cluster 3.3 today. I should say I tried configuring the Cluster today. The software is already installed on two systems. I am trying to configure a shared filesystem between two 6320 Blades. I selected the "Custom" install because the "Typical"... (2 Replies)
Anybody have any ideas on what could be causing this crash? This an x86 virtual machine I have running in ESXi at my house, so obviously no way to send the data to Oracle for analysis. Just curious if anyone has any ideas. I suspect motherboard problems with the x86 hardware, as I already... (4 Replies)
how do I remote install a vib on 200 esxi hosts ?
I need to ssh into the host
run this command
esxcli software vib install -v /tmp/vib --no-sig-check (1 Reply)
Hi
i have 2 esxi. one is amd based cpu and the other is intel based cpu.
i have a redhat linux machine that was created in amd cpu esxi, now i need to migrate it (powered off) to INTEL based esxi. will the redhat machine will be OK with that?
Thanks (2 Replies)
Hi All,
Can any one Explain Me Step by Step installing SCO 5.0.7v in ESXi 6.0 ??
When i was trying to install its is not booting into operating systems !!
showing an error no operating systems in media !!
Thanks in Advance!! Please take some time in helping me !!
Kanthi Kiran K (3 Replies)
Tl;dr Solaris 11.4 won't boot on 2 machines because of what I believe is network issues. Need to know where I can find more info to troubleshoot.
I have two Solaris 11.4 systems running on VMware ESXi 6.5u2, which have suddenly (and seemingly for no reason) started boot-looping.
Both of... (2 Replies)
Discussion started by: rking267
2 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)