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
hi
frnz, let me know how to configutre the veritas cluster.... (3 Replies)
Discussion started by: Kbharat20
3 Replies
2. High Performance Computing
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
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
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
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
How to create your cluster members routes and manual nat, and proxy. (2 Replies)
Discussion started by: padmaja@tech
2 Replies
7. Solaris
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
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
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
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
LEARN ABOUT CENTOS
sepolicy-network
sepolicy-network(8) sepolicy-network(8)
NAME
sepolicy-network - Examine the SELinux Policy and generate a network report
SYNOPSIS
sepolicy network [-h] (-l | -a application [application ...] | -p PORT [PORT ...] | -t TYPE [TYPE ...] | -d DOMAIN [DOMAIN ...])
DESCRIPTION
Use sepolicy network to examine SELinux Policy and generate network reports.
OPTIONS
-a, --application
Generate a report listing the ports to which the specified init application is allowed to connect and or bind.
-d, --domain
Generate a report listing the ports to which the specified domain is allowed to connect and or bind.
-l, --list
List all Network Port Types defined in SELinux Policy
-h, --help
Display help message
-t, --type
Generate a report listing the port numbers associate with the specified SELinux port type.
-p, --port
Generate a report listing the SELinux port types associate with the specified port number.
EXAMPLES
sepolicy network -p 22
22: tcp ssh_port_t 22
22: udp reserved_port_t 1-511
22: tcp reserved_port_t 1-511
sepolicy network -a /usr/sbin/sshd
sshd_t: tcp name_connect
111 (portmap_port_t)
53 (dns_port_t)
88, 750, 4444 (kerberos_port_t)
9080 (ocsp_port_t)
9180, 9701, 9443-9447 (pki_ca_port_t)
32768-61000 (ephemeral_port_t)
all ports < 1024 (reserved_port_type)
all ports with out defined types (port_t)
sshd_t: tcp name_bind
22 (ssh_port_t)
5900-5983, 5985-5999 (vnc_port_t)
6000-6020 (xserver_port_t)
32768-61000 (ephemeral_port_t)
all ports > 500 and < 1024 (rpc_port_type)
all ports with out defined types (port_t)
sshd_t: udp name_bind
32768-61000 (ephemeral_port_t)
all ports > 500 and < 1024 (rpc_port_type)
all ports with out defined types (port_t)
AUTHOR
This man page was written by Daniel Walsh <dwalsh@redhat.com>
SEE ALSO
sepolicy(8), selinux(8), semanage(8)
20121005 sepolicy-network(8)