Menu
▾
▴
Re: [tipc-discussion] TIPC issue
|
From: Jon M. <jm...@re...> - 2023-03-31 20:36:48
|
Hi Nagendra, Sorry for not noticing this earlier. I will look into this next week. ///jon On 2023-03-13 12:58, Nagendra Kumar via tipc-discussion 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 tipctipc 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 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 |
