Here's more:
Bug Id: 4077132 Category: kernel Subcategory: tcp-ip State: evaluated Synopsis: ip_enable_group_ifs=0 doesn't pick default hostname. Description:
cu has multiple virtual interfaces designated for le0. This worked fine on 2.5.1. Cu upgraded to 2.6 and now finds that a new feature of 2.6 (interface groups) has begun selecting interfaces at random. Solaris 2.6, as it is shipped is supposed to operater this way to make load handling more efficient.
However, by setting the ndd option ip_enable_group_ifs to 0, it disables the interface groups functionality and allows 2.6 to operate like a 2.5.1 or previous OS release.
The problem is that when the interface groups are disabled, the hostname selected to handle network calls is the last hostname.le0:[0-9] file found. I tested this on my workstation and found that no matter what the last hostname.le0:? file was, the last file found would become the interface the system always used for network calls.
This is a bad thing for customers who use host authentication and have an ever-changing network...like webservers.
When interface groups are disabled, the loghost (hostname.le0) should be selected.
Work around:
Have the hostname.le0 host name be selected when the interface groups are disabled.
casper.dik@Holland 1997-10-02
[[ DELETED WRKAROUND ]] <--WHY?????????????????????????
This workaround works for EVERY SINGLE CASE I have seen to date.
Do not delete this workaround. Even if it only works part of the time, it is still better than nothing.
The workaround, as stated previously is to (prior to deletion):
1. cp hostname.<interface> (e.g. hostname.le0) to hostname.<interface>:99.
NOTE: You must use 99 because there will never, ever be a file listed in higher than that (unless there are over 1000 virtual interfaces, then 999 would need to be used).
2. verify that hostname.<interface>:99 matches the contents of /etc/nodename.
3. change the contents of hostname.<interface> to some other hostname.
Please do not delete this workaround. Even if it doesn't work all of the time, it is better than nothing.
It didn't work around the problem all of the time. <- see above
If deleting routes doens't work around theproblem that can only indicate that a routing problem has been introduced in 2.6, I can't quite put a finger on it yet.
If routing worked properly, the following should work around the problem:
ifconfig le0:X metric 100
or route delete <interface route>
However, since neither workaround works we do have a problem.
steve.hodnett@East 1997-10-23 Startup script workaround can be added to rc2.d
/etc/rc2.d/S70fixroutes #!/bin/sh # echo "Turning off ifgrps" /usr/sbin/ndd -set /dev/ip ip_enable_group_ifs 0 # echo "Removing Duplicate Virtual Interfaces Network routes" /usr/sbin/route delete net <ip#ofle0:1> <network#> /usr/sbin/route delete net <ip#ofle0:2> <network#> .... /usr/sbin/route delete net <ip#ofle0:xx> <network#>
casper.dik@Holland 1997-10-28
I deleted *MY* workaround because it didn't work.
The route delete workaround also doesn't work. Integrated in releases: Duplicate of: Patch id: See also: 4081315 Summary: