Hi Amar, The claim that TIPC is compatible between different kernel versions is true, and we always test for backwards compatibility when we introduce changes that may cause compatibility problems. However, you kernel 3.2.0 i on node 1.1.6 is *very* old, and I don't think anybody of us is testing this far back before we release.
The changes between the versions is substantial, (yes, I know I should have changed module version, I will do that soon), and I think there is a risk we might have run into an unknown compatibility issue here. One thing is puzzling me in the dump from node 1.1.1: why is the bearer disabled and enabled repeatedly? If you have done that manually, it is completely consistent with what you see on the other node. But I guess it can't be that simple? Regards ///jon On 11/15/2016 05:15 AM, Amar Nv wrote: > Hello, > > I am trying to bring up a cluster of 2 nodes hosted on different > environments. > > > > *NODE1 TIPC Node-addr > (6)*root@host1:/lib/modules/3.2.0-29-generic/kernel/net/tipc# > modinfo tipc.ko > filename: tipc.ko > version: 2.0.0 > license: Dual BSD/GPL > description: TIPC: Transparent Inter Process Communication > srcversion: A0CB14DDCCCBB1ABAE73386 > depends: > intree: Y > vermagic: 3.2.0-29-generic SMP mod_unload modversions > > > > *NODE2 TIPC Node-addr (1)*root@host2:/lib/modules/4.6.0-rc6/kernel/net/tipc# > modinfo tipc.ko > filename: /lib/modules/4.6.0-rc6/kernel/net/tipc/tipc.ko > version: 2.0.0 > license: Dual BSD/GPL > description: TIPC: Transparent Inter Process Communication > srcversion: C58612B2A6F6FABF1EF75CE > depends: udp_tunnel,ip6_udp_tunnel > intree: Y > vermagic: 4.6.0-rc6 SMP mod_unload modversions > > > > > *Node 1 Kernel logs* > Nov 15 15:40:09 7311-6 kernel: [598187.276986] TIPC: Established link > <1.1.6:base-1.1.1:base> on network plane A > Nov 15 15:40:09 7311-6 kernel: [598187.277100] TIPC: Resetting link > <1.1.6:base-1.1.1:base>, requested by peer > Nov 15 15:40:09 7311-6 kernel: [598187.277103] TIPC: Lost link > <1.1.6:base-1.1.1:base> on network plane A > Nov 15 15:40:09 7311-6 kernel: [598187.277106] TIPC: Lost contact with > <1.1.1> > Nov 15 15:40:09 7311-6 kernel: [598187.656616] TIPC: Established link > <1.1.6:base-1.1.1:base> on network plane A > Nov 15 15:40:09 7311-6 kernel: [598187.656687] TIPC: Resetting link > <1.1.6:base-1.1.1:base>, requested by peer > Nov 15 15:40:09 7311-6 kernel: [598187.656689] TIPC: Lost link > <1.1.6:base-1.1.1:base> on network plane A > Nov 15 15:40:09 7311-6 kernel: [598187.656691] TIPC: Lost contact with > <1.1.1> > > > > *Node 2 Kernel logs*Nov 15 15:39:03 7470-1 kernel: [452484.786678] tipc: > Activated (version 2.0.0) > Nov 15 15:39:03 7470-1 kernel: [452484.786713] NET: Registered protocol > family 30 > Nov 15 15:39:03 7470-1 kernel: [452484.786813] tipc: Started in single node > mode > Nov 15 15:39:03 7470-1 kernel: [452484.907687] Started in network mode > Nov 15 15:39:03 7470-1 kernel: [452484.907693] Own node address <1.1.1>, > network identity 1061 > Nov 15 15:39:03 7470-1 kernel: [452484.907759] Enabled bearer <eth:base>, > discovery domain <1.1.0>, priority 10 > Nov 15 15:40:09 7470-1 kernel: [452551.143276] Disabling bearer <eth:base> > Nov 15 15:40:09 7470-1 kernel: [452551.254557] Left network mode > Nov 15 15:40:10 7470-1 kernel: [452551.310490] NET: Unregistered protocol > family 30 > Nov 15 15:40:10 7470-1 kernel: [452551.310502] tipc: Deactivated > Nov 15 15:40:47 7470-1 kernel: [452588.331653] tipc: Activated (version > 2.0.0) > Nov 15 15:40:47 7470-1 kernel: [452588.331688] NET: Registered protocol > family 30 > Nov 15 15:40:47 7470-1 kernel: [452588.331790] tipc: Started in single node > mode > Nov 15 15:40:47 7470-1 kernel: [452588.432707] Started in network mode > Nov 15 15:40:47 7470-1 kernel: [452588.432713] Own node address <1.1.1>, > network identity 1061 > Nov 15 15:40:47 7470-1 kernel: [452588.432781] Enabled bearer <eth:base>, > discovery domain <1.1.0>, priority 10 > Nov 15 15:41:53 7470-1 kernel: [452654.591363] Disabling bearer <eth:base> > Nov 15 15:41:53 7470-1 kernel: [452654.713347] Left network mode > Nov 15 15:41:53 7470-1 kernel: [452654.761326] NET: Unregistered protocol > family 30 > Nov 15 15:41:53 7470-1 kernel: [452654.761340] tipc: Deactivated > > > >From the tcpdump capture - I see a "Link State" message with type RESET is > sent from Node2. > I confirm the TIPC address is same on both the nodes. > > Please suggest, > 1. Does the TIPC protocol works between 2 kernels as stated above? > 2. How can we determine the reason for RESET trigger by Node2 - Any other > debugging ideas ? > > Thanks, > Amar > ------------------------------------------------------------------------------ > _______________________________________________ > tipc-discussion mailing list > tipc-discussion@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tipc-discussion ------------------------------------------------------------------------------ _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
