Hi,
I have a Redhat Cluster Suite with 2 nodes, using option "Multicast HeartBeating" on clumembd, whith default IP: 225.0.0.11
The cluster member names are:
# grep node /etc/hosts
192.168.100.1 node1
192.168.100.2 node2
My problem is that the Multicast IP is relating to other network... (1 Reply)
Hi
I'm completely new to Solaris Disk Suite. Where can I go and read up about it. I've seen consultants run the meta- commands, but it doesn't make any sense to me. I would like to learn how it works and how to use it.
Thanks (1 Reply)
I am new to Solaris so please bear with me. I have spent enough time searching to get somewhat of a grip here but I am not sure what to do next. I am trying to grow a file system on a Solaris 8 server.
B_root@server:>df -k
Filesystem kbytes used avail capacity Mounted on... (9 Replies)
Hi,
is it normal, that the IP alias (service IP) can't be seen with ifconfig -a , as eth0:1 for example
the IP is on the node, you can ping it, and open ports for that IP
look at this:
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback... (4 Replies)
HI
How can i configure fence_cisco_ucs with redhat cluster suite.
i was trying to configure fencing aganet with red ahat cluster suite
i issued command
# /usr/sbin/fence_vmware_soap -a 172.22.90.61 -l admin -p duc2Cisco -o reboot
then i got below error:
Failed: You have to... (0 Replies)
Discussion started by: bentech4u
0 Replies
LEARN ABOUT OPENSOLARIS
clinfo
clinfo(1M) System Administration Commands clinfo(1M)NAME
clinfo - display cluster information
SYNOPSIS
clinfo [-nh]
DESCRIPTION
The clinfo command displays cluster configuration information about the node from which the command is executed.
Without arguments, clinfo returns an exit status of 0 if the node is configured and booted as part of a cluster. Otherwise, clinfo returns
an exit status of 1.
OPTIONS
The following options are supported:
-h Displays the highest node number allowed to be configured. This is different from the maximum number of nodes supported in a given
cluster. The current highest configured node number can change immediately after the command returns since new nodes can be dynami-
cally added to a running cluster.
For example, clinfo -h might return 64, meaning that the highest number you can use to identify a node is 64. See the Sun Cluster 3.0
System Administration Guide for a description of utilities you can use to determine the number of nodes in a cluster.
-n Prints the number of the node from which clinfo is executed.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
This is usually because the node is not configured or booted as part of a cluster.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO attributes(5)SunOS 5.11 12 Mar 2002 clinfo(1M)