Re: [tipc-discussion] TIPC issue

[Jon M. <jm...@re...>]

On 2023-04-04 20:30, Jon Maloy wrote:
>
>
> On 2023-03-16 12:03, Nagendra Kumar via tipc-discussion wrote:
>>   Hi Jon/Tuong/Tung/Hoang/Thang,Is there any thoughts on the below 
>> email trails??
>> Thanks-Nagendra
>>      On Monday, 13 March, 2023 at 10:59:45 pm IST, Nagendra Kumar via 
>> tipc-discussion <tip...@li...> wrote:
>>      Sending it again.....
>>      On Friday, 10 March, 2023 at 11:49:59 am IST, Nagendra Kumar 
>> <nag...@ya...> wrote:
>>     Hi,We are trying to use TIPC on RHEL8.4 to manually communicate 
>> OpenSAF nodes, using TIPC instead of TCP.
>> OpenSAF is designed to work with TIPC but only as L2 and, in this 
>> case, we need IP routing. That's why we are configuring it manually.
>> I am using the following script to start and configure TIPC:#!/bin/bash
>> SLOT_ID=$(cat "/etc/opensaf/slot_id")DEV=eno1
>> modprobe tipc
>
>> tipc node set netid 1111tipc node set address 1.1.$SLOT_IDtipc node 
>> set identity $(hostname)tipc bearer enable media udp device $DEV name 
>> $(hostname)tipc media set mtu 9000 media udp
>> (Configuring TIPC with UDP we get TIPC traffic between nodes of 
>> different cabinets)
>>   They have all run the same script. Sometimes it happens to some and 
>> sometimes it happens to others doing exactly the same. In this case 
>> procs and ssaf(pics attached) are in different VLANs. When they are 
>> in the same VLAN, they always work correctly.
>>
> I notice that you are setting both 'tipc node set address' and 'tipc 
> node set identity'.  You only set one or the other, never both, since 
> setting an address will create an identity and vice versa.
> This should not really cause any trouble, -the value you set first 
> will cause that the second one will be ignored.
> I will still recommend that you remove one of those and try again, 
> before I spend and more time on this.
>
> Cheers
> ///jon

Hi again,
There is a commit upstream, commit 
c244c092f1ed2acfb5af3d3da81e22367d3dd733 ("tipc: fix unexpected link 
reset due to discovery messages") that is fixing an issue with link 
dicovery that seems related.
It has not yet been backported to rhel-8.4, but it can be cherry-picked 
cleanly if you want to try.
It all depends on whether you build own kernels, of course...

Regards
///jon


>
>>
>> I don't know if it's a network or software problem as communications 
>> are working fine.
>> RHEL version: Red Hat Enterprise Linux release 8.4 (Ootpa)
>> Kernel version: 4.18.0-305.el8.x86_64
>> TIPC version: Built-in kernel module
>>
>>
>>       Thank you !-Nagendra
>>    _______________________________________________
>> tipc-discussion mailing list
>> tip...@li...
>> https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>>    _______________________________________________
>> tipc-discussion mailing list
>> tip...@li...
>> https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>