Sponsored Content
Operating Systems Solaris It is possible to install Solaris Cluster on ESXI host ? Post 303040598 by penchev on Friday 1st of November 2019 10:12:34 AM
Old 11-01-2019
It is possible to install Solaris Cluster on ESXI host ?

I try many time to install and configure Solaris Cluster on ESXI, but i received the same transport error between. When i set manuel private (net1,net2) ip config i have ping between nodes.


Quote:
"Probes were sent out from all transport adapters configured for this
node ("node1"). But, they were not seen by any of the other nodes.
This may be due to any number of reasons, including improper cabling
or a switch which was confused by the probes.
You can either attempt to correct the problem and try the probes again
or manually configure the transport.
Code:
--node1
 
net0 - public

net1 - private

 net2 - private


--node2
 
net0 - public

net1 - private

net2 - private

on ESXI i created vSwitch1 (net1/net1) / vSwitch2 (net2/net2)

Last edited by penchev; 11-01-2019 at 11:36 AM..
 

8 More Discussions You Might Find Interesting

1. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. Filesystems, Disks and Memory

Veritas Storage Foundation basic and Core cluster solaris 10 release 7 install

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)
Discussion started by: tristezo2k
1 Replies

3. Solaris

Solaris Cluster Install Hangs

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)
Discussion started by: bluescreen
2 Replies

4. Solaris

Frequent crashes in ESXi virtual Solaris machine

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)
Discussion started by: christr
4 Replies

5. Shell Programming and Scripting

Install vib on 200 esxi hosts

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)
Discussion started by: tdubb123
1 Replies

6. Red Hat

Esxi INTEL cpu vs esxi AMD cpu

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)
Discussion started by: guy3145
2 Replies

7. SCO

Install SCO 5.0.7 on ESXi 6.0

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)
Discussion started by: Kanthi Kiran
3 Replies

8. UNIX for Beginners Questions & Answers

Solaris 11.4 on ESXi 6.5 suddenly boot-looping

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
DIETFORWARDER(1)														  DIETFORWARDER(1)

NAME
dietForwarder - DIET tool to manage ssh tunnels between DIET components NAME
dietForwarder - Tool for creating DIET forwarders. Forwarders are special components that serve as proxies and manage ssh tunnels between DIET components in complex networks. SYNOPSYS
dietForwarder [options] ... DESCRIPTION
Deploying DIET on heterogeneous networks that are not reachable by means other than ssh tunnels is a delicate task. DIET forwarders are special DIET components that serve as proxies between DIET components by creating ssh tunnels. dietForwarder is a command to instantiate DIET forwarders. Forwarders simplify the maintenance of ssh tunnels between DIET components, thus improving DIET's scalability and ease of configuration in complex network topologies. Before starting a DIET forwarder, you must: o launch omniNames on the local and remote hosts; o launch the remote peer, specifying its name and network configuration only; o launch the local peer and give it the remote peer's name, the ssh connection's details, the remote port to use and the 'pass -C' option to create the ssh tunnel. [Remark: forwarders must be launched before the DIET hierarchy.] OPTIONS
--name [name] String identifying the forwarder. --peer-name [name] String identifying its peer on the other network. --ssh-host [host] Host hosting the ssh tunnel. --ssh-login [login] Login used to establish the ssh connection (default: current user login). --ssh-key [/path/to/ssh/key] Path to the ssh key (the private one!) used to establish the ssh connection (default: $HOME/.ssh/id_rsa). --remote-port [port] Port the ssh host is listening on. --remote-host [host] Host to which the connection is made by the tunnel (corresponds to ssh options -L and -R). --nb-retry [nb] Number of times that the local forwarder will try to bind itself to the remote forwarder (default: 3). --peer-ior [IOR] Passes the remote forwarder's IOR. By default, the local forwarder will retrieve its peer's IOR. --tunnel-wait [seconds] Set the number of seconds to wait before considering that the tunnel has been created. EXAMPLE
Here is a simple configuration example: o We have two domains: net1 and net2. Forwarders will be launched on hosts fwd.net1 and fwd.net2. o There's no link between hosts fwd.net1 and fwd.net2 but users may access fwd.net2 from fwd.net1 using a ssh connection. o Let's call the fwd.net1 forwarder Fwd1 and the fwd.net2 forwarder Fwd2. o One SeD lives in fwd.net2 while the rest of the DIET hierarchy lives on the net1 domain. Command line for launching Fwd1 fwd.net1$ dietForwarder --name Fwd1 --peer-name Fwd2 --ssh-host fwd.net2 --ssh-login dietUser --ssh-key id rsa net2 --remote-port 50000 Command line to launch Fwd2 fwd.net2$ dietForwarder --name Fwd2 RATIONALE
DIET uses CORBA as its communication layer. While it is a flexible and robust middleware, it remains hard to deploy DIET on heterogeneous networks that are not reachable except through ssh tunnels. DIET forwarders help the administrator to configure their grid without manually setting-up ssh tunnels, which is arguably neither simple nor scalable. DIET forwarders make it very easy to configure networks with such topologies. LICENSE AND COPYRIGHT
Copyright (C)2011, GRAAL, INRIA Rhone-Alpes, 46 allee d'Italie, 69364 Lyon cedex 07, France all right reserved <diet-dev@ens-lyon.fr> License This program is free software: you can redistribute it and/or mod- ify it under the terms of the GNU General Public License as pub- lished by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. AUTHORS
GRAAL INRIA Rhone-Alpes 46 allee d'Italie 69364 Lyon cedex 07, FRANCE Email: <diet-dev@ens-lyon.fr> WWW: http://graal.ens-lyon.fr/DIET SEE ALSO
omniNames(1), DIETAgent(1) BUGS
On some systems, forwarder rules will not work unless you use IP addresses instead of hostnames. AUTHOR
haikel.guemar@sysfera.com License: GPLv3 COPYRIGHT
DIET developers 0.1 2011-01-10 DIETFORWARDER(1)
All times are GMT -4. The time now is 01:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy