Re: [tipc-discussion] Request: Unable to config second node on same machine

[<nar...@wi...>]

Hi Surya,
Comments inline.

>> From: nar...@wi... [mailto:nar...@wi...]
>> Subject: RE: [tipc-discussion] Request: Unable to config second node on
>> same machine
>>
>> Hi Surya,
>>
>> Thanks for your quick reply.
>> >On a single node, you will not be able to create two nodes of tipc.
> >>You can attach multiple interfaces as follows
> >you mean to say that, from a Machine we can communicate to outer world
> >by using a single tipc node id irrespective of no of eth ports or MAC
>> ids.
>>
>Yes.
got it.
new learning for me. thanks

>> >tipc-config -netid=1234 -a=1.1.1 -be=eth:eth0,eth:eth1
>> this command will use the same node id and Ngbr Discovery is happening
>> by two MAC addresses as i could capture it from wireshark log.
>> # ./tipc-config -netid=1234 -addr=1.1.1 -be=eth:eth1,eth:eth0
>> TIPC: Own node address <1.1.1>, network identity 1234
>> TIPC: Enabled bearer <eth:eth1>, discovery domain <1.1.0>, priority 10
>> TIPC: Enabled bearer <eth:eth0>, discovery domain <1.1.0>, priority 10
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
>> TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
>>
>>
>> May i know use of having Duplicate entries?

>I guess you would had used the same 1.1.1 for the other machine as well,.
>Each machine should have unique id. Node A ->1.1.1, Node B->1.1.2 etc etc.
No.
the previous log was from a single machine with the same Node A 1.1.1 (eth0,eth1).

After configuring on the two machine with A->1.1.1(eth0,eth1)  B->1.1.2(eth0,eth1)
you can observe the MAC id difference and node.

TIPC: Started in network mode
TIPC: Own node address <1.1.1>, network identity 1234
TIPC: Enabled bearer <eth:eth0>, discovery domain <1.1.0>, priority 10
TIPC: Enabled bearer <eth:eth1>, discovery domain <1.1.0>, priority 10
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.2> using eth(00:0c:29:03:83:dc) seen on <eth:eth1>
TIPC: Duplicate <1.1.2> using eth(00:0c:29:03:83:dc) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Resetting link <1.1.1:eth0-1.1.2:>, peer interface address changed
TIPC: Resetting link <1.1.1:eth0-1.1.2:>, peer interface address changed
TIPC: Established link <1.1.1:eth1-1.1.2:eth0> on network plane B
TIPC: Resetting link <1.1.1:eth0-1.1.2:eth1>, peer interface address changed
TIPC: Duplicate <1.1.2> using eth(00:0c:29:03:83:dc) seen on <eth:eth1>
TIPC: Resetting link <1.1.1:eth0-1.1.2:eth1>, peer interface address changed
TIPC: Resetting link <1.1.1:eth0-1.1.2:eth1>, peer interface address changed
TIPC: Duplicate <1.1.2> using eth(00:0c:29:03:83:dc) seen on <eth:eth1>
TIPC: Established link <1.1.1:eth0-1.1.2:eth1> on network plane A
TIPC: Duplicate <1.1.2> using eth(00:0c:29:03:83:d2) seen on <eth:eth0>
TIPC: Duplicate <1.1.2> using eth(00:0c:29:03:83:dc) seen on <eth:eth1>
TIPC: Resetting link <1.1.1:eth0-1.1.2:eth1>, peer not responding
TIPC: Lost link <1.1.1:eth0-1.1.2:eth1> on network plane A
TIPC: Resetting link <1.1.1:eth1-1.1.2:eth0>, peer not responding
TIPC: Lost link <1.1.1:eth1-1.1.2:eth0> on network plane B
TIPC: Lost contact with <1.1.2>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:a0) seen on <eth:eth1>
TIPC: Duplicate <1.1.1> using eth(00:0c:29:48:17:aa) seen on <eth:eth0>

Because of the Duplication of nodes the network connection was not established.
continuously kernel msg are pop up (dmesg).

If that would the case then what could the advantages in having -be=eth:eth0,eth:eth1,...etc ?
As Per My Understanding to the point, If any of Ethernet interface goes down then other will act as backup Ethernet interface.
please correct me, if i am wrong.

I have started learning TIPC.
If you have any experimental commands or Doc, please share.

>> Best regards
>> Naresh Kamboju