Re: [tipc-discussion] help with tipc command

[Rune T. <ru...@in...>]

We use the netid param to separate different clusters on the same network, so I don't think I need the domain param anymore. I will attempt using it without the domain param and see if everything looks to work.
Just a leftover from 15 years of TIPC usage...

Tipc-config seems to work for all bearer ops, except for -b

Not working:
root@test10020u2:~# tipc-config -b
Bearers:
operation not supported
root@test10020u2:~# dmesg -c
root@test10020u2:~# uname -r
4.4.0-145-generic
root@test10020u2:~#

Working:
root@testrec198:~# tipc-config -b
Bearers:
eth:lo
eth:eth0
root@testrec198:~# uname -r
4.4.0-142-generic
root@testrec198:~#

root@testrec198:~# tipc-config -V
TIPC configuration tool version 2.1.1

So somewhere between 4.4.0-142 (I think it worked in -144 also) and -145 it stopped working.

-----Original Message-----
From: Jon Maloy <jon...@er...> 
Sent: Tuesday, April 16, 2019 15:02
To: Rune Torgersen <ru...@in...>; tip...@li...
Subject: RE: help with tipc command

Hi,
I tried it in my version (5.0) , and the parameter was accepted both as 1.1.0 and as 1001000, but the links didn't come up.
It is possible that we have broken something, as this parameter is regarded as obsolete, and not really anything we pay attention to during testing.
But of course it should work, just as tipc-config should continue working without any limitations.
I'll look into this later today, when I find some time.

Still, my first question is if you really need this setting. It is only needed when you are planning to have nodes interconnected on the same LAN/VLAN, but you still want to keep them isolated. Is that so?
And, if you need this isolation, you could use the network id (nowadays called cluster id)  instead.
Just give it a try, while I start some troubleshooting on my part.

BR
///jon



> -----Original Message-----
> From: Rune Torgersen <ru...@in...>
> Sent: 16-Apr-19 12:39
> To: Jon Maloy <jon...@er...>; tipc-
> dis...@li...
> Subject: RE: help with tipc command
> 
> Did find that site after a while.
> 
> However it only shows enable without the domain param.
> 
> I got "tipc bearer enable priority 5 media eth device eth2" to work but still get
> that error on " tipc bearer enable domain 1.1.0 priority 5 media eth device
> eth2"
> 
> Nowhere in the documentation does it show me the correct format for the
> domain param.
> 
> -----Original Message-----
> From: Jon Maloy <jon...@er...>
> Sent: Tuesday, April 16, 2019 11:16
> To: Rune Torgersen <ru...@in...>; tipc-
> dis...@li...
> Subject: RE: help with tipc command
> 
> Hi Rune,
> Have a look here:
> 
> http://tipc.io/getting_started.html
> 
> Hilsen
> ///jon
> 
> 
> > -----Original Message-----
> > From: Rune Torgersen <ru...@in...>
> > Sent: 16-Apr-19 11:41
> > To: tip...@li...
> > Subject: [tipc-discussion] help with tipc command
> >
> > I am trying to convert some scripts from using tipc-config to newer
> > tipc command  (no, not "ip tipc" yet as it is not available on Ubuntu 16.04).
> >
> > I was not planning g on doing this unit we moved to Ubuntu 18, but I
> > just noticed that with the lastest ubuntu 16.04 kernel (4.4.0-145)
> > tipc-config -b no longer works (worked on 4.4.0-143).
> >
> > I manager to figure out syntax for bearer disable, but have problems
> > with bearer enable.
> >
> >
> > Old command was
> > tipc-config -be=eth:eth2/1.1.0/5
> >
> > New is
> >
> > But gets an error
> > root@test10020u3:~# tipc bearer enable domain 1.1.0 priority 5 media
> > eth device eth2
> > error: Invalid argument
> > root@test10020u3:~# dmesg -c
> > [ 2896.786648] Bearer <eth:eth2> rejected, illegal discovery domain
> >
> >
> > Also, what would be the equivalents of:
> > tipc-config -netid=$netid
> > tipc-config -a=1.1.${unit}
> >
> >
> >
> >
> > _______________________________________________
> > tipc-discussion mailing list
> > tip...@li...
> > https://lists.sourceforge.net/lists/listinfo/tipc-discussion