Sponsored Content
Full Discussion: veritas cluster
Operating Systems Solaris veritas cluster Post 302257231 by 22blaze on Tuesday 11th of November 2008 05:22:56 PM
Old 11-11-2008
NICs are not the limitation here, ports are. As reborg indicates if you have enough ports, you can set it up, you will just not have the ipmultinic resource.
You do need a minimum of 3 ports. The cluster private network requires 2 ports then you still need one port to communicate on your public network.
 

10 More Discussions You Might Find Interesting

1. Solaris

how to setup the veritas cluster

hi frnz, let me know how to configutre the veritas cluster.... (3 Replies)
Discussion started by: Kbharat20
3 Replies

2. High Performance Computing

veritas cluster forum

do you know where can i find forum for veritas hasf forum? thanks. (0 Replies)
Discussion started by: itik
0 Replies

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

4. Solaris

Veritas Cluster

Can I make a veritas cluster on Sun vertual box or Vmwere. Please help me. (4 Replies)
Discussion started by: saga499
4 Replies

5. Solaris

Veritas Cluster Server Question

Is it possible to configure veritas cluster server using 2 Ldoms on same host? I just want to test and learn VCS. We can do a cluster (sun cluster3.2 ) in a box using 2 Ldoms but i 'm not sure if thats possible with veritas cluster or not ? (1 Reply)
Discussion started by: fugitive
1 Replies

6. Solaris

Veritas Cluster

How to create your cluster members routes and manual nat, and proxy. (2 Replies)
Discussion started by: padmaja@tech
2 Replies

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

8. Solaris

suncluster co-existing with Veritas Cluster

have a pair of sun servers, wanting to test drive a 2-node cluster using both software.. would like disable one of these cluster software while the othe is running.. Is it feasible at all ?? (2 Replies)
Discussion started by: ppchu99
2 Replies

9. Solaris

Using ZFS with Veritas Cluster Server

Until I really began to explore the practical implications of using ZFS with VCS, I would not have necessarily realised the obstacles that would be put in my path. Data integrity is a must-have for storage in a shared host environment, so it surprised me to learn as I opened this particular... (0 Replies)
Discussion started by: cambridge
0 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
aconnect(1)						      General Commands Manual						       aconnect(1)

NAME
aconnect - ALSA sequencer connection manager SYNOPSIS
aconnect [-d] [-options] sender receiver aconnect -i|-o [-options] aconnect -x DESCRIPTION
aconnect is a utility to connect and disconnect two existing ports on ALSA sequencer system. The ports with the arbitrary subscription permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect. For example, to connect from port 64:0 to 65:0, run as follows: % aconnect 64:0 65:0 The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0). When another port (e.g. 65:1) is attached to the same sender port, the data is sent to both receiver ports. For disconnection, use -d option. % aconnect -d 64:0 65:0 The address can be given using the client's name. % aconnect External:0 Emu8000:1 Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000". Another function of aconnect is to list the present ports on the given condition. The input ports, which may become sender ports, can be listed with -i option. % aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 64: 'External MIDI-0' [type=kernel] 0 'MIDI 0-0 ' Similarly, to see the output ports, use -o flag. You can remove all existing exported connections using -x option. This function is useful for terminating the ALSA drivers, because the modules with sequencer connections cannot be unloaded unless their connections are removed. OPTIONS
CONNECTION MANAGEMENT -d, --disconnect Disconnect the given subscription. -e, --exclusive Connect ports with exclusive mode. Both sender and receiver ports can be no longer connected by any other ports. -r, --real queue Convert time-stamps of event packets to the current value of the given real-time queue. This is option is, however, not so useful, since the receiver port must use (not necessarily own) the specified queue. -t, --tick queue Like -r option, but time-stamps are converted to the current value of the given tick queue. LIST PORTS -i, --input List existing input (readable) ports. This option is exclusive to -o. -o, --output List existing output (writable) ports. This option is exclusive to -i. -l, --list List the current connection status. The connected and connecting ports from/to each port are listed together. The suffix flag [ex] means the connection is exclusive. The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion on the listed queue, respectively. REMOVE ALL CONNECTIONS -x, --removeall Remove all exported connections. SEE ALSO
aseqnet(1), aseqview(1) AUTHOR
Takashi Iwai <tiwai@suse.de> August 31, 2000 aconnect(1)
All times are GMT -4. The time now is 05:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy