While creating Zone cluster getting error Post: 303016866

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Veritas Cluster for Oracle on Soalris Zone

Hi, Does anyone has idea how to implement Veritas Cluster Server 5.3 (SF 5.3) for Oracle 10g on Solaris Zone (Containers). Please let me know any of you folks have worked on similar implementation and if you could pass on some information related to it. BR, Shreeram Rane

2. Solaris

Creating A Solaris Zone - Unable to install - Are network settings required?

Hi i have created a solaris zone but have not yet connected any network cables for this new zone, can i set the zone up without running the command 'add net' and not adding an ip or physical interface? i tried to add dummy internet settings and get this zonecfg:coddr> add net...

3. Solaris

Applying Recommended Patch Cluster to Whole Root Zone

Hi there, Apologies if this question has been asked and answered already but I've not been able to find the thread. Question: Is it possible to apply the Solaris 10 Recommended Patch Cluster to a whole root (non-global) zone locally? I.E. apply the patch cluster from the non-global in...

4. Solaris

High Availability zone on Sun Cluster

HI Experts, Could some one help me in configuring high availability zone on Sun Cluster Reg: Sudhan

5. Solaris

Zone failes to boot due to mount issue, dir exists in zone.

I have two physical servers, with zones that mount local storage. We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point). It failed to mount on every boot because the directory existed in the zone. I...

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

7. Solaris

Help needed for patching on zone cluster

Hi All, Below is the configuration of my sun cluster. root@glob-one # clzc status === Zone Clusters === --- Zone Cluster Status --- Name Node Name Zone HostName Status Zone Status ---- --------- ------------- ------ ----------- data ...

8. Solaris

Zone Cluster Question

I have a question about losing a node in a zone cluster. Hopefully I can explain enough for someone to answer. Let's say I have a zone cluster spread over 3 physical nodes. If Node1 crashes, would I be correct in assuming I would lose all zones on Node1? If I lost Node1 below, would I lose...

9. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently...

LEARN ABOUT SUNOS

tor-resolve

TOR-RESOLVE(1)							    Tor Manual							    TOR-RESOLVE(1)

NAME

       tor-resolve - resolve a hostname to an IP address via tor

SYNOPSIS

       tor-resolve [-4|-5] [-v] [-x] hostname [sockshost[:socksport]]

DESCRIPTION

       tor-resolve is a simple script to connect to a SOCKS proxy that knows about the SOCKS RESOLVE command, hand it a hostname, and return an IP
       address.

       By default, tor-resolve uses the Tor server running on 127.0.0.1 on SOCKS port 9050. If this isn't what you want, you should specify an
       explicit sockshost and/or socksport on the command line.

OPTIONS

       -v
	   Display verbose output.

       -x
	   Perform a reverse lookup: get the PTR record for an IPv4 address.

       -5
	   Use the SOCKS5 protocol. (Default)

       -4
	   Use the SOCKS4a protocol rather than the default SOCKS5 protocol. Doesn't support reverse DNS.

SEE ALSO

       tor(1), torify(1).

       See doc/socks-extensions.txt in the Tor package for protocol details.

AUTHORS

       Roger Dingledine <arma@mit.edu>, Nick Mathewson <nickm@alum.mit.edu>.

AUTHOR

       Peter Palfrader
	   Author.

Tor								    09/26/2014							    TOR-RESOLVE(1)