Alias in SCO network configuration
We have many remote servers that are running different versions of the SCO operating system. The current server inventory includes the usage of SCO 3.2v5.0.5 3.2v5.0.6 and 3.2v5.0.7.
Recently, there have been some ongoing problems when a re-boot is done with some of these remote servers. Afetr the re-boot, we have run an "ifconfig -a" command, and we find an alias exists for the network address of the remote server. This problem is resolved when we mannually run an "ifconfig" command to remove the alias. We also run an "arp" command to clear it's settings.
What is needed to fix this problem for the longer term is not known because we do not know how an alias is being generated? When existing servers are up and running, there are no existing aliases in the network configurations. We did several scans of our existing servers, but have not yet been able to determine the root cause of this problem.
Would this problem show up in some configuration file such as /etc/rc2.d/S85tcp? Does the scoadmin command (for the network config mgr) need to be run to verify and to re-store the tcp settings? Should the SCO kernal be re-linked? Are there any other items that could be checked for a problem cause?
Any suggestions would be appreciated. Thanks!!
|
More UNIX and Linux Forum Topics You Might Find Helpful
Powered by 
04-13-2009
Hybrid Mode
