Re: [Pacemaker] IPaddr2 between eth1 e bond1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/10/13 23:27, Andreas Kurz wrote: On 2013-10-05 02:04, Charles Mean wrote: Hello guys, I have a cluster with 2 nginx sharing one VIP: primitive VIP_AD_SRV ocf:heartbeat:IPaddr2 params ip=X.Y.Z.W cidr_netmask=30 nic=eth1 op monitor interval=1s The problem is that I have replaced on of those two server and the new one can't connect over eth1 just over bond1, so, when I move the resource to this new server it creates a virtual interface at eth1 and I never reach it. Is there a way to solve this situation ? Simply don't specify nic if you don't have several interfaces in the same network. The resource agent will find the interface by looking at interfaces having already an IP in the same network configured ... no matter whether they are simple/bond/bridges/vlan interfaces. So the bellow is wrong? Just wondering here. primitive ip_virtual0 ocf:heartbeat:IPaddr2 \ params nic=vlan10 ip=192.168.35.10 cidr_netmask=28 \ op monitor interval=10s When vlan10 also uses IP 192.168.35.4/28, 192.168.35.10 is my tgtd IP. # ip addr show vlan10 9: vlan10@bond0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 9000 qdisc noqueue state UP link/ether 00:1e:67:6b:f7:14 brd ff:ff:ff:ff:ff:ff inet 192.168.35.4/28 brd 192.168.35.15 scope global vlan10 inet 192.168.35.10/28 brd 192.168.35.15 scope global secondary vlan10 inet6 fe80::21e:67ff:fe6b:f714/64 scope link valid_lft forever preferred_lft forever Kind regards, Jelle de Jong -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iJwEAQECAAYFAlJSuVQACgkQ1WclBW9j5HmsMwP+IU2bH7rTTj6jKg4B23o8fN7K QQAxlkaBa4QvfbASkSzmXHwPMnLVqaTrWNRKa58EYXrNoMkTSbGGKYlQK1CLSQcR QHe0USxZdPHDJmj6N/NYlfuZKLW1UL0iGyf98rc8g2KF4cXAsnvlnrT/rK7TNQCt CREYUZL8xQsb9XENM7o= =2yxN -END PGP SIGNATURE- ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] IPaddr2 between eth1 e bond1
Am Montag, 7. Oktober 2013, 15:38:32 schrieb Jelle de Jong: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/10/13 23:27, Andreas Kurz wrote: On 2013-10-05 02:04, Charles Mean wrote: Hello guys, I have a cluster with 2 nginx sharing one VIP: primitive VIP_AD_SRV ocf:heartbeat:IPaddr2 params ip=X.Y.Z.W cidr_netmask=30 nic=eth1 op monitor interval=1s The problem is that I have replaced on of those two server and the new one can't connect over eth1 just over bond1, so, when I move the resource to this new server it creates a virtual interface at eth1 and I never reach it. Is there a way to solve this situation ? Simply don't specify nic if you don't have several interfaces in the same network. The resource agent will find the interface by looking at interfaces having already an IP in the same network configured ... no matter whether they are simple/bond/bridges/vlan interfaces. So the bellow is wrong? Just wondering here. primitive ip_virtual0 ocf:heartbeat:IPaddr2 \ params nic=vlan10 ip=192.168.35.10 cidr_netmask=28 \ op monitor interval=10s When vlan10 also uses IP 192.168.35.4/28, 192.168.35.10 is my tgtd IP. # ip addr show vlan10 9: vlan10@bond0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 9000 qdisc noqueue state UP link/ether 00:1e:67:6b:f7:14 brd ff:ff:ff:ff:ff:ff inet 192.168.35.4/28 brd 192.168.35.15 scope global vlan10 inet 192.168.35.10/28 brd 192.168.35.15 scope global secondary vlan10 inet6 fe80::21e:67ff:fe6b:f714/64 scope link valid_lft forever preferred_lft forever Kind regards, Jelle de Jong Looks OK. -- Dr. Michael Schwartzkopff Guardinistr. 63 81375 München Tel: (0163) 172 50 98___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] IPaddr2 between eth1 e bond1
On 2013-10-05 02:04, Charles Mean wrote: Hello guys, I have a cluster with 2 nginx sharing one VIP: primitive VIP_AD_SRV ocf:heartbeat:IPaddr2 params ip=X.Y.Z.W cidr_netmask=30 nic=eth1 op monitor interval=1s The problem is that I have replaced on of those two server and the new one can't connect over eth1 just over bond1, so, when I move the resource to this new server it creates a virtual interface at eth1 and I never reach it. Is there a way to solve this situation ? Simply don't specify nic if you don't have several interfaces in the same network. The resource agent will find the interface by looking at interfaces having already an IP in the same network configured ... no matter whether they are simple/bond/bridges/vlan interfaces. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now Thank you ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org signature.asc Description: OpenPGP digital signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] IPaddr2 between eth1 e bond1
Am Freitag, 4. Oktober 2013, 21:04:13 schrieb Charles Mean: Hello guys, I have a cluster with 2 nginx sharing one VIP: primitive VIP_AD_SRV ocf:heartbeat:IPaddr2 params ip=X.Y.Z.W cidr_netmask=30 nic=eth1 op monitor interval=1s The problem is that I have replaced on of those two server and the new one can't connect over eth1 just over bond1, so, when I move the resource to this new server it creates a virtual interface at eth1 and I never reach it. Is there a way to solve this situation ? Thank you hi, yes, it is possbile to solve that problem. But it is a little bit tricky and you need to play with the XML config file. No shell (pcs, crm) I would know of supports that feature. For details see: http://clusterlabs.org/doc/en-US/Pacemaker/1.1- crmsh/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html The example given uses different ports on the cluster nodes, but it also works for different interface names on the nodes. ON the other hand, you could the resource figure out the interface by itself via the routing lookup. If the nodes have a dedicated IP address in the net of the VIP it should work automagically. Greetings, -- Dr. Michael Schwartzkopff Guardinistr. 63 81375 München Tel: (0163) 172 50 98___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
