Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-16 Thread jumanjiman
G Date: Fri, 16 Jan 2009 23:21:41 To: linux clustering Subject: Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to -- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster -- Linu

RE: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-16 Thread Shaun Mccullagh
clustering Subject: Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to Sorry that repeated replies were posted, I must have clicked too many times. Just to verify, I'll just make a copy of existing file : cp -p /etc/sysconfig/network-sc

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-16 Thread sunhux G
Sorry that repeated replies were posted, I must have clicked too many times. Just to verify, I'll just make a copy of existing file : *cp -p /etc/sysconfig/network-scripts/ifcfg-eth0 * * /etc/sysconfig/network-scripts/ifcfg-eth0:1* Then edit ifcfg-eth0:1 to update it with the secondary IP addre

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications

2009-01-13 Thread Stewart Walters
sunhux G wrote: Thanks. What should I do to ensure that each time after the server is rebooted, this 2nd IP address stays : is there a config file somewhere that I must update or a startup script that get executed each time server is rebooted that will execute the commands? TIA On Tue, Jan 13,

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-13 Thread Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
How about looking here? http://www.redhat.com/docs/manuals/ Am Mittwoch, den 14.01.2009, 00:02 +0800 schrieb sunhux G: > Thanks. > > What should I do to ensure each time the server is booted up, > the 2nd IP address will stay. Which config file to edit or startup > script to create that will exe

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-13 Thread sunhux G
Thanks. What should I do to ensure each time the server is booted up, the 2nd IP address will stay. Which config file to edit or startup script to create that will execute the commands on each reboot? On Tue, Jan 13, 2009 at 8:18 PM, Василец Дмитрий wrote: > ifconfig eth0 192.168.1.1/24 up > i

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-13 Thread sunhux G
Thanks. What should I do to ensure that each time after the server is rebooted, this 2nd IP address stays : is there a config file somewhere that I must update or a startup script that get executed each time server is rebooted that will execute the commands? TIA On Tue, Jan 13, 2009 at 8:18 PM,

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-13 Thread sunhux G
Thanks. What should I do to ensure that each time after the server is rebooted, this 2nd IP address stays : is there a config file somewhere that I must update or a startup script that get executed each time server is rebooted that will execute the commands? TIA On Tue, Jan 13, 2009 at 8:18 PM,

Re: [Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-13 Thread Василец Дмитрий
ifconfig eth0 192.168.1.1/24 up ifconfig eth0:1 192.168.10.1/24 up В Втр, 13/01/2009 в 20:05 +0800, sunhux G пишет: > Hi, > > How can I create 2 separate IP addresses for one physical NIC > in RHES 4.5? > > I have 2 applicaitons, one Oracle & one UPS software & both > listens/bind to same tc

[Linux-cluster] 2 IP addrs on one NIC : for 2 applications listening on same tcp port to bind to

2009-01-13 Thread sunhux G
Hi, How can I create 2 separate IP addresses for one physical NIC in RHES 4.5? I have 2 applicaitons, one Oracle & one UPS software & both listens/bind to same tcp port number. Purpose is to have Oracle bind to one IP addr while UPS bind to the 2nd IP addr (ie the alias address as in Solaris).