Short answer: this is perfectly normal. What happened was that an IP address was added to the interface without a differentiating label.
Believe it or not, the "ifconfig" application is strongly discouraged because it has a tendency to dramatize situations like this. It would probably have been removed years ago if not for legacy support.
Anyway, if you want to understand a bit more about what is happening, take a look at this iproute2 documentation. They explain that although all alias addresses are secondary addresses, the inverse is not necessarily true.
Then try the following:
Code:
[root@uscltest2 ~]# ip addr show dev eth0
[root@uscltest2 ~]# ip addr add 10.200.218.86/24 broadcast 10.200.218.255 dev eth0
[root@uscltest2 ~]# ip addr
[root@uscltest2 ~]# ifconfig
[root@uscltest2 ~]# ip addr add 10.200.218.87/24 broadcast 10.200.218.255 label eth0:alias dev eth0
[root@uscltest2 ~]# ip addr
[root@uscltest2 ~]# ifconfig
You will notice that after the first add, the output of "ip addr" showed the address, but the output of "ifconfig" did not. Additionally, when you added a label the second time, the output of "ip addr" still shows the address, but the output of "ifconfig" also show our new label. (which only says "eth0:alias" because we told it to - it could literally be anything)
After this little demo, reset things to normal:
Code:
[root@uscltest2 ~]# ip addr del 10.200.218.86/24 dev eth0
[root@uscltest2 ~]# ip addr del 10.200.218.87/24 dev eth0
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 All,
One small request. In UNIX/LINUX we can have our own aliases in .bashrc file. My doubt is when we add a new alias and if it is tried in already opened terminals it will not work, may be it is not going to recognise. Bit when we use the same alias in new terminal it will work. I... (1 Reply)
HI All,
I have a small question/clarification/doubt . Does anyone know how to provide alias in the mails that come from Unix servers.
Like i have a Unix server that generates status mails every hour for a scheduled job , it sends me mails with status with the ID in from field as... (3 Replies)
Hi,
I am relatively new to Sun Solaris. I am installing 2 node cluster and when I was installing cluster suite 3.2 2/08, it is giving me this error as "Conflict - Incomplete version detected".
Please help me in this regard and also suggest me any valuable point to consider before going ahead... (3 Replies)
hi to all members in this forums .. Nice to meet you...
i only have a questions about command utility of "dd":
for example i will type:
pico trial
this is my file.
and save it and type chmod a+x trial
can there be a way that instead of typing:
dd if=trial of=trial.copy conv=ucase... (3 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)
Hello,
I need to rediret the directory location at run time as:-
If I type cd /dir1/dir2 then it should take me to /dir1/dir3 at run time.
Inside dir1, both dir2 and dir3 directories are present.
Could anyone guild me over it?
Thanks
Shubham (5 Replies)
Discussion started by: shubh05
5 Replies
LEARN ABOUT OPENSOLARIS
scversions
scversions(1M) System Administration Commands scversions(1M)NAME
scversions - Sun Cluster version management
SYNOPSIS
scversions [-c]
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
arguments, the scversions command prints a message indicating whether a commitment is needed.
OPERANDS
The following operands are supported:
-c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.
When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and
some new functionality introduced in the upgrade might be unavailable.
When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func-
tionality becomes available and any administrative restrictions are removed.
If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
command has no effect because the cluster is already running at the highest possible level of functionality.
If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.
EXIT STATUS
0 Success
non-zero Failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO scinstall(1M)Sun Cluster 3.2 17 Aug 2007 scversions(1M)
06-15-2010
It would probably have been removed years ago if not for legacy support.