Alias in SCO network configuration


 
Thread Tools Search this Thread
Operating Systems SCO Alias in SCO network configuration
# 1  
Old 04-13-2009
Lightbulb 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!!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. SCO

SCO 5.0.7 Configuration

Hi, I am really new to the forum and for SCO as well. I have a burning situation here to know how to configure below list of hardware into SCO 5.0.7!! EQUINOX 990209-1 ELS 16 PORT TERMINAL SERVER and Seagate DAT Scorpion 24 - Tape drive ( 12 GB / ) DDS-3 SCSI Can Any One Please Help Me... (11 Replies)
Discussion started by: Kanthi Kiran
11 Replies

2. Solaris

Problem in network configuration

Hi everybody, I have a very strange problem ; if somebody could help me it would be very kind. I'll try to explain my problem. I have 2 unix machines absolutely identical running solaris 9. For network reasons I need to change the IP address of the 2 machines. I proceed exactly the same on the... (11 Replies)
Discussion started by: aribault
11 Replies

3. Solaris

Network configuration

Hi I have installed Solaris 5.10 on Intel x86 machine (standalone). I want to access internet through solaris. How should I configure the network? Is static IP or DHCP advisable? (5 Replies)
Discussion started by: johnl
5 Replies

4. UNIX for Dummies Questions & Answers

network configuration

I am using solaris 10, my internet works alright but each time i reboot i keep loosing my connection. I will have to use the ifconfig iprb0 192.168.1.xx netmask 255.255.255.0 up and Route add default 192.168.1.xxx command to gain back my internet. I know there is a better way of addressing... (1 Reply)
Discussion started by: seyiisq
1 Replies

5. SCO

Network Configuration

I have a SCO 5.07 Server and I am trying to get it on my network. I have edited the /etc/hosts file and /etc/rc2.d/s99route . I has connectivity on the NIC card but not sure if I am forgetting another file. Thanks! (2 Replies)
Discussion started by: andrewd
2 Replies

6. SCO

SCO Unix Network Configuration

Hello Guys, We have an old PC running on SCO Unix V. Is there any sites where i can get manual/procedures on how to install and configure Network. Thanks (2 Replies)
Discussion started by: nrcuevas
2 Replies

7. Solaris

network configuration

hi again... i configured my network settings sometiime ago using the sys-unconfig command.the active link was rtls0. there was some problem with the network so i changed the ISP. now when im trying to reconfigure the system wit sys-unconfig, it tries to configure the network on rtls1 (and shows... (1 Reply)
Discussion started by: strider
1 Replies

8. IP Networking

ifconfig: difference between creating logical or alias network interface

Hi guys, I have set up multiple virtual FTP servers on a server through one physical NIC. I believe there are to ways; setting logical or alias ip's. I would like to know what is the difference between setting up a logical ip or setting up an alias ip to a physical network interface? Some links to... (5 Replies)
Discussion started by: zaff
5 Replies

9. UNIX for Dummies Questions & Answers

Internet Configuration in SCO 5.05

Hi, I'm trying to configure SCO's internet manager for access to the internet. However, when I start the config program, my desktop turns black & white (unless I minimize communicator's window -- then it turns back to normal). I type in the user id and password and it looks as if the... (1 Reply)
Discussion started by: gseyforth
1 Replies

10. HP-UX

HP-UX Network Configuration

Hi, I have installed a HP-UX B.11.00 U 9000/800 Server in one of the domain. And I'm also able to telnet/ping into this server from systems in the same domain. But I'm not able to telnet/ping into this server from a different domain. So, what shoud need to do to achieve this... (6 Replies)
Discussion started by: S.Vishwanath
6 Replies
Login or Register to Ask a Question
uname(1)							   User Commands							  uname(1)

NAME
uname - print name of current system SYNOPSIS
uname [-aimnprsvX] uname [-S system_name] DESCRIPTION
The uname utility prints information about the current system on the standard output. When options are specified, symbols representing one or more system characteristics will be written to the standard output. If no options are specified, uname prints the current operating sys- tem's name. The options print selected information returned by uname(2), sysinfo(2), or both. OPTIONS
The following options are supported: -a Prints basic information currently available from the system. -i Prints the name of the platform. -m Prints the machine hardware name (class). Use of this option is discouraged. Use uname -p instead. See NOTES section below. -n Prints the nodename (the nodename is the name by which the system is known to a communications network). -p Prints the current host's ISA or processor type. -r Prints the operating system release level. -s Prints the name of the operating system. This is the default. -S system_name The nodename may be changed by specifying a system name argument. The system name argument is restricted to SYS_NMLN characters. SYS_NMLN is an implementation specific value defined in <sys/utsname.h>. Only the super-user is allowed this capability. This change does not persist across reboots of the system. Use sys-unconfig(1M) to change a host's name per- manently. -v Prints the operating system version. -X Prints expanded system information, one information element per line, as expected by SCO UNIX. The displayed information includes: o system name, node, release, version, machine, and number of CPUs. o BusType, Serial, and Users (set to "unknown" in Solaris) o OEM# and Origin# (set to 0 and 1, respectively) EXAMPLES
Example 1 Printing the OS name and release level The following command: example% uname -sr prints the operating system name and release level, separated by one SPACE character. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of uname: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. SYSV3 This variable is used to override the default behavior of uname. This is necessary to make it possible for some INTERACTIVE UNIX Systems and SCO UNIX programs and scripts to work properly. Many scripts use uname to determine the SYSV3 type or the version of the OS to ensure software is compatible with that OS. Setting SYSV3 to an empty string will make uname print the following default values: nodename nodename 3.2 2 i386 The individual elements that uname displays can also be modified by setting SYSV3 in the following format: os,sysname,node,rel,ver,mach os Operating system (IUS or SCO). sysname System name. node Nodename as displayed by the -n option. rel Release level as displayed by the -r option. ver Version number as displayed by the -v option. mach Machine name as displayed by -m option. Do not put spaces between the elements. If an element is omitted, the current system value will be used. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
arch(1), isalist(1), sys-unconfig(1M), sysinfo(2), uname(2), nodename(4), attributes(5), environ(5), standards(5) NOTES
Independent software vendors (ISVs) and others who need to determine detailed characteristics of the platform on which their software is either being installed or executed should use the uname command. To determine the operating system name and release level, use uname -sr. To determine only the operating system release level, use uname -r. Notice that operating system release levels are not guaranteed to be in x.y format (such as 5.3, 5.4, 5.5, and so forth); future releases could be in the x.y.z format (such as 5.3.1, 5.3.2, 5.4.1, and so forth). In SunOS 4.x releases, the arch(1) command was often used to obtain information similar to that obtained by using the uname command. The arch(1) command output "sun4" was often incorrectly interpreted to signify a SunOS SPARC system. If hardware platform information is desired, use uname -sp. The arch -k and uname -m commands return equivalent values; however, the use of either of these commands by third party programs is dis- couraged, as is the use of the arch command in general. To determine the machine's Instruction Set Architecture (ISA or processor type), use uname with the -p option. SunOS 5.11 17 Sep 2003 uname(1)