See inline On Thursday, April 28, 2016, Jon Maloy <jon.ma...@ericsson.com> wrote:
> > > > -----Original Message----- > > From: GUNA [mailto:gbala...@gmail.com <javascript:;>] > > Sent: Thursday, 28 April, 2016 17:43 > > To: tipc-discussion@lists.sourceforge.net <javascript:;> > > Subject: [tipc-discussion] Tipc: name table mismatch between different > cards in a > > system > > > > After upgraded CPU cards to 4.4.0 Kernel, there is table mismatch between > > CPU and IO cards. The IO Publication value = CPU Publication + 1 as you > see > > example below: > > > > In CPU (slot 2) > > > > Type Lower Upper Port Identity Publication > > > > 16789314 3201 3201 <1.1.6:1540208445> 1540208445 > > > > 16789823 4 4 <1.1.6:3035967304> 3035967304 > > > > 16832168 3201 3201 <1.1.6:723652841> 723652841 > > > > … > > > > > > > > In IO (slot10) > > > > 16789314 3201 3201 <1.1.6:1540208445> 1540208446 > > > > 16789823 4 4 <1.1.6:3035967304> 3035967305 > > > > 16832168 3201 3201 <1.1.6:723652841> 723652842 > > > > … > > This looks like another artefact of the problem we have in 4.4 with > corrupted entries, where old entries are not withdrawn, so the new ones > cannot replace them in "CPU", while it happens to work in "IO". If 1.1.6 > is "IO" or a third node this could make sense. 1.1.6 is node6 but I see similar for all other nodes as well. Ie: same for 1.1.2,1.1.3,....1.1.13. > This problem has been fixed in Ubuntu 16.04, but has not been released > yet. I would suggest you try 4.5 or 4.6rc4 to see if it disappears. > According to Rune Torgersen it is definitely working in 4.6. > > ///jon > > I could not move to new kernel now, but I could rebuild the 4.4.0 if I get the fix. If you are aware of the fix please let me know detail of the fix. > > > > > > All the entries are similar pattern in both IO & CPU. The CPU match with > > rest of the CPUs. > > > > > > The system runs on previous kernel did not see this issue. > > > > > > There are two links on IO and CPU cards. Both links are ACTIVE in IO and > > in CPU one ACTIVE and other STANDBY. > > > > Is that cause the issue? If so, is it possible to make both links to be > > ACTIVE ? > > > > > > // IO > > > > Link <1.1.10:eth0-1.1.2:p19p1> > > > > ACTIVE MTU:1500 Priority:10 Tolerance:1200 ms Window:50 packets > > > > Link <1.1.10:eth1-1.1.2:p19p2> > > > > ACTIVE MTU:1500 Priority:10 Tolerance:1200 ms Window:50 packets > > > > // CPU > > Link <1.1.2:p19p1-1.1.10:eth0> > > ACTIVE MTU:1500 Priority:10 Tolerance:1200 ms Window:50 packets > > > > Link <1.1.2:p19p2-1.1.10:eth1> > > STANDBY MTU:1500 Priority:10 Tolerance:1200 ms Window:50 packets > > > > thanks, > > > > Guna > > > ------------------------------------------------------------------------------ > > Find and fix application performance issues faster with Applications > Manager > > Applications Manager provides deep performance insights into multiple > tiers of > > your business applications. It resolves application problems quickly and > > reduces your MTTR. Get your free trial! > > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > _______________________________________________ > > tipc-discussion mailing list > > tipc-discussion@lists.sourceforge.net <javascript:;> > > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
