[ClusterLabs] Antw: Regarding IP tables and IP Address clone

Wed Dec 30 13:54:40 UTC 2015

>>>> Somanath Jeeva <somanath.jeeva at ericsson.com<http://clusterlabs.org/mailman/listinfo/users>> schrieb am 30.12.2015 um 11:34 in

>Nachricht <4F5E5141ED95FF45B3128F3C7B1B2A6721ABFE13 at eusaamb109.ericsson.se<http://clusterlabs.org/mailman/listinfo/users>>:

>> On 12/22/2015 08:09 AM, Somanath Jeeva wrote:

>>> Hi

>>> I am trying to use ip loadbalancing using cloning feature in pacemaker. but

>> After 15 min the virtual ip becomes unreachable. Below is the pacemaker

>> cluster config

>>>

>>>  # pcs status

>>> Cluster name: DES

>>> Last updated: Tue Dec 22 08:57:55 2015

>>> Last change: Tue Dec 22 08:10:22 2015

>>> Stack: cman

>>> Current DC: node-01 - partition with quorum

>>> Version: 1.1.11-97629de

>>> 2 Nodes configured

>>> 2 Resources configured

>>>

>>>

>>> Online: [ node-01 node-02 ]

>>>

>>> Full list of resources:

>>>

>>>  Clone Set: ClusterIP-clone [ClusterIP] (unique)

>>>      ClusterIP:0        (ocf::heartbeat:IPaddr2):       Started node-01

>>>      ClusterIP:1        (ocf::heartbeat:IPaddr2):       Started node-02

>>>

>>> #pcs config

>>> Cluster Name: DES

>>> Corosync Nodes:

>>>   node-01 node-02

>>> Pacemaker Nodes:

>>> node-01 node-02

>>>

>>> Resources:

>>>  Clone: ClusterIP-clone

>>>   Meta Attrs: clone-max=2 clone-node-max=2 globally-unique=true

>>>   Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2)

>>>    Attributes: ip=10.61.150.55 cidr_netmask=23 clusterip_hash=sourceip

>>>    Operations: start interval=0s timeout=20s (ClusterIP-start-timeout-20s)

>>>                stop interval=0s timeout=20s (ClusterIP-stop-timeout-20s)

>>>                monitor interval=5s (ClusterIP-monitor-interval-5s)

>>>

>>> Stonith Devices:

>>> Fencing Levels:

>>>

>>> Location Constraints:

>>> Ordering Constraints:

>>> Colocation Constraints:

>>>

>>> Cluster Properties:

>>>  cluster-infrastructure: cman

>>>  cluster-recheck-interval: 0

>>>  dc-version: 1.1.11-97629de

>>>  stonith-enabled: false

>>> Pacemaker and Corosync version:

>>> Pacemaker - 1.1.12-4

>>> Corosync  - 1.4.7

>>>

>>>

>>> Is the issue due to configuration error or firewall issue.

>>>

>>>

>>> With Regards

>>> Somanath Thilak J

>>>

>>> Hi Somanath,

>>>

>> The configuration looks fine (aside from fencing not being configured),

>> so I'd suspect a network issue.

>>

>> The IPaddr2 cloning relies on multicast MAC addresses (at the Ethernet

>> level, not multicast IP), and many switches have issues with that. Make

>> sure your switch supports multicast MAC (and if necessary, has it

>> enabled on the relevant ports).

>>

>> Some people have found it necessary to add a static ARP entry for the

>> cluster IP/MAC in their firewall and/or switch.

>

>> Hi ,

>>

>> It seems that the switches have multicast support enabled. Any idea on how

>> to trouble shoot the issue. I also tried adding the Multicast MAC to the ip

>> neigh tables. Still the Virtual IP goes down in 15 min or so.

>Did you try a "watch arp -vn" on your nodes to watch for changes (if you only have a few connections)?

I could not see my virtual ip in the arp -vn command output. Only if ass the static arp entry I can see the Virtual IP in the command o/p. I see the virtual ip and MAC only in iptables,ip addr,ip maddr commands

# service iptables status

Table: filter

Chain INPUT (policy ACCEPT)

num  target     prot opt source               destination

1    CLUSTERIP  all  --  0.0.0.0/0            10.61.150.55        CLUSTERIP hashmode=sourceip clustermac=51:33:83:16:0A:BF total_nodes=2 local_node=2 hash_init=0

2    ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy ACCEPT)

num  target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)

num  target     prot opt source               destination

1    ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0

# ip addr show bond0

6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP

    link/ether 00:0c:29:32:8d:b9 brd ff:ff:ff:ff:ff:ff

    inet 10.61.150.212/23 brd 10.61.151.255 scope global bond0

    inet 10.61.150.55/23 brd 10.61.151.255 scope global secondary bond0

    inet6 fe80::20c:29ff:fe32:8db9/64 scope link tentative dadfailed

       valid_lft forever preferred_lft forever

# ip maddr show bond0

6:      bond0

        link  51:33:83:16:0a:bf

        link  01:00:5e:01:01:02

        link  33:33:ff:32:8d:b9

        link  33:33:00:00:00:01

        link  33:33:00:00:02:02

        link  33:33:00:75:00:75

        link  01:00:5e:00:00:01

        inet  224.1.1.2

        inet  224.0.0.1

        inet6 ff02::1:ff32:8db9

        inet6 ff0e::75:75

        inet6 ff02::202

        inet6 ff02::1

>>

>>

>> Regards

>> Somanath Thilak J

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20151230/48c7a855/attachment.htm>