[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] IP Resource behavior with Red Hat Cluster



Hi

I chose my IP resource as 192.168.13.15, I had eth3 configured on
192.168.13.1 but it still failed with error -

Dec 27 17:35:32 datablade1 clurgmgrd[31853]: <err> Error storing ip: Duplicate
Dec 27 17:36:55 datablade1 clurgmgrd[31853]: <notice> Starting
disabled service service:service1
Dec 27 17:36:55 datablade1 clurgmgrd[31853]: <notice> start on ip
"192.168.13.15/24" returned 1 (generic error)
Dec 27 17:36:55 datablade1 clurgmgrd[31853]: <warning> #68: Failed to
start service:service1; return value: 1

Below is set of interfaces -

eth0      Link encap:Ethernet  HWaddr 00:10:18:66:15:70
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::210:18ff:fe66:1570/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:125 errors:0 dropped:0 overruns:0 frame:0
          TX packets:305 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:32679 (31.9 KiB)  TX bytes:42477 (41.4 KiB)
          Interrupt:177 Memory:98000000-98012800

eth1      Link encap:Ethernet  HWaddr 00:10:18:66:15:72
          inet addr:192.168.11.1  Bcast:192.168.11.255  Mask:255.255.255.0
          inet6 addr: fe80::210:18ff:fe66:1572/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1237019 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1919245 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:183885611 (175.3 MiB)  TX bytes:337885336 (322.2 MiB)
          Interrupt:154 Memory:9a000000-9a012800

eth2      Link encap:Ethernet  HWaddr 00:10:18:66:15:74
          inet addr:192.168.12.1  Bcast:192.168.12.255  Mask:255.255.255.0
          inet6 addr: fe80::210:18ff:fe66:1574/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:419008 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:26822898 (25.5 MiB)  TX bytes:5992 (5.8 KiB)
          Interrupt:185 Memory:94000000-94012800

eth3      Link encap:Ethernet  HWaddr 00:10:18:66:15:76
          inet addr:192.168.13.1  Bcast:192.168.13.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:162 Memory:96000000-96012800


On Sat, Dec 25, 2010 at 6:34 AM, Jakov Sosic <jakov sosic srce hr> wrote:
> On 12/24/2010 05:46 PM, Parvez Shaikh wrote:
>> Hi Jakov
>>
>> Thank you for your response. My two hosts have multiple network
>> interfaces or ethernet cards. I understood from your email, that the
>> IP corresponding to "cluster node name" for both hosts, should be in
>> the same subnet before a cluster could bring virtual IP up.
>
> No... you misunderstood me. I meant that if the virtual address is
> 192.168.25.X, than you have to have interface on each node that is set
> up with the ip address from the same subnet. That interface does not
> need to correspond to the cluster node name. For example:
>
> node1 - eth0 - 192.168.1.11 (netmask 255.255.255.0)
> node2 - eth0 - 192.168.1.12 (netmask 255.255.255.0)
>
> IP resource - 192.168.25.100
>
>
> Now, how do you expect the cluster to know what to do with IP resource?
> On which interface can cluster glue 192.168.25.100? eth0? But why eth0?
> And what is the netmask? What about routes?
>
> So, you need to have for example eth1 on both machines set up in the
> same subnet, so that cluster can glue IP address from IP resource to
> that exact interface (which is set up statically). So you also have to
> have for example:
>
> node1 - eth1 - 192.168.25.47 (netmask 255.255.255.0)
> node2 - eth1 - 192.168.25.48 (netmask 255.255.255.0)
>
> Now, rgmanager will know where to activate IP resource, because
> 192.168.25.100 belongs to 192.168.25.0/24 subnet, which is active on
> node1/eth1 and node2/eth2.
>
> If you were to have another IP resource, for example 192.168.240.44, you
> would need another interface with another set of static ip addresses on
> every host you intend to run IP resource on...
>
>
> I hope you get it correctly now.
>
>
>
>
>
> --
> Jakov Sosic
> www.srce.hr
>
> --
> Linux-cluster mailing list
> Linux-cluster redhat com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]