Menu
▾
▴
Re: [tipc-discussion] Request: Unable to config second node on same machine
|
From: Suryanarayana G. <SGa...@go...> - 2010-08-25 10:20:09
|
Hi Naresh, Comments inline. Regards Surya > -----Original Message----- > From: nar...@wi... [mailto:nar...@wi...] > Sent: Wednesday, August 25, 2010 2:25 PM > To: Suryanarayana Garlapati; tip...@li... > 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. > >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. > > Best regards > Naresh Kamboju > > > ________________________________________ > From: Suryanarayana Garlapati [SGa...@go...] > Sent: Wednesday, August 25, 2010 11:54 AM > To: Naresh Kamboju (WT01 - GMT-Telecom Equipment); tipc- > dis...@li... > Subject: RE: [tipc-discussion] Request: Unable to config second node on > same machine > > Hi naresh, > On a single node, you will not be able to create two nodes of tipc. > You can attach multiple interfaces as follows. > > tipc-config -netid=1234 -a=1.1.1 -be=eth:eth0,eth:eth1 > > but not as you had done. > > Regards > Surya > > > > -----Original Message----- > > From: nar...@wi... [mailto:nar...@wi...] > > Sent: Wednesday, August 25, 2010 11:01 AM > > To: tip...@li... > > Subject: [tipc-discussion] Request: Unable to config second node on > > same machine > > > > Hello, > > > > I have inserted default tipc.ko module from > > /lib/modules/2.6.31.xxx/kernel/net/tipc/tipc.ko and Configured tipc- > > config. > > able to make a connection between eth0 of machine to eth0 of other > > machine and eth1 of machine to eth1 other machine. > > i could not make and configure two nodes in the same machine. > > > > # insmod-tipc > > # ./tipc-config -netid=1234 -addr=1.1.1 -be=eth:eth0 > > # ./tipc-config -netid=1234 -addr=1.1.2 -be=eth:eth1 > > operation not supported (cannot change node address once assigned) > > #rmmod tipc > > > > > > # insmod-tipc > > # ./tipc-config -netid=1234 -addr=1.1.1 -be=eth:eth1 > > # ./tipc-config -netid=1234 -addr=1.1.2 -be=eth:eth0 > > operation not supported (cannot change node address once assigned) > > #rmmod tipc > > > > Please give me information regarding, > > which parameter i need to change or configure to enable second Node > > support on the same Machine. > > > > Best regards > > Naresh kamboju > > > > --------------------------------------------------------------------- > -- > > ------- > > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > > Be part of this innovative community and reach millions of netbook > > users > > worldwide. Take advantage of special opportunities to increase > revenue > > and > > speed time-to-market. Join now, and jumpstart your future. > > http://p.sf.net/sfu/intel-atom-d2d > > _______________________________________________ > > tipc-discussion mailing list > > tip...@li... > > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > > Please do not print this email unless it is absolutely necessary. > > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > addressee(s) and may contain proprietary, confidential or privileged > information. If you are not the intended recipient, you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately and destroy all copies of this message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient > should check this email and any attachments for the presence of > viruses. The company accepts no liability for any damage caused by any > virus transmitted by this email. > > www.wipro.com |
