Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Community/Discussion/General/Disabling QNET comms on a single interface/List of Posts
Forum Topic - Disabling QNET comms on a single interface: (7 Items)
   
Update
Daniel Fearon
09/30/2009 5:04 AM
post39040
Disabling QNET comms on a single interface   
I am running a network of Virtual Machines (built on ESX4.0) using QNX 6.4.1.

There a 6 QNX VMs each with a host only interface on which they can communicate. The majority of the traffic is QNET and
 broadcast Ethernet traffic so keeping it internal to the host only network is key.

On one of the VMs I have a second bridged interface allowing me to telnet and hop to each of the 6 VM machines from a 
LAN, enabling CLI access, log retrieval etc.

The problem I'm experiencing is that the QNET comms on this dual interface machine is being flooded out both interfaces,
 but I want to keep this to the host only network only.

So, my question is whether it is possible to disable QNET comms on one specfic interface with QNX. And if so, how is 
this achieved? I am also open to any other suggestions you might have.


Thanks,
Danny
Xiaodan Tang(deleted)
09/30/2009 9:20 AM
post39064
RE: Disabling QNET comms on a single interface   
You probably can't "Disable" QNET comms on one interface, but what you
can do, is to "bind" QNET comms on specific interface. You do this by
pass "bind=en0" (assume en0 is the interface you want to use QNET)
option, when you load the QNET. (like: io-pkt-v4-hc -p qnet bind=en0)

-xtang

> -----Original Message-----
> From: Daniel Fearon [mailto:community-noreply@qnx.com]
> Sent: September 30, 2009 5:05 AM
> To: general-community
> Subject: Disabling QNET comms on a single interface
> 
> I am running a network of Virtual Machines (built on ESX4.0) using QNX
> 6.4.1.
> 
> There a 6 QNX VMs each with a host only interface on which they can
> communicate. The majority of the traffic is QNET and broadcast
Ethernet
> traffic so keeping it internal to the host only network is key.
> 
> On one of the VMs I have a second bridged interface allowing me to
telnet
> and hop to each of the 6 VM machines from a LAN, enabling CLI access,
log
> retrieval etc.
> 
> The problem I'm experiencing is that the QNET comms on this dual
interface
> machine is being flooded out both interfaces, but I want to keep this
to
> the host only network only.
> 
> So, my question is whether it is possible to disable QNET comms on one
> specfic interface with QNX. And if so, how is this achieved? I am also
> open to any other suggestions you might have.
> 
> 
> Thanks,
> Danny
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post39040
Daniel Fearon
09/30/2009 10:15 AM
post39074
Re: RE: Disabling QNET comms on a single interface   
Thank you for your response, which I've attempted to follow. So far, I've been unsuccessful in getting Qnet to bind to 
the en0 interface.

Below is a run down of the steps I took to achieve this:

# cd /usr/qnx641/target/qnx6/x86/boot/build/
# vi qnxbasesmp.build

Change the existing entry below to what you have suggested (further below):

"mount -Tio-pkt lsm-qnet.so" 
becomes... "mount -Tio-pkt -p bind=en0 lsm-qnet.so"
(note - i have tried -p bind=en0 before and after lsm-qnet.so)

Write changes to the file and then create a new ifs image, which is loaded on the next startup:
# mkifs qnxbasesmp.build /.boot/qnxbasesmp.ifs


Can you confirm that I'm using the correct parameters you have suggested, and if this is the correct location to be 
calling them? I think it's quite close and sounds like a very plausible solution, so any further assistance to get there
 would be greatly appreciated.


Thanks,
Danny
Xiaodan Tang(deleted)
09/30/2009 10:18 AM
post39075
RE: RE: Disabling QNET comms on a single interface   
Okay, if you are mounting qnet later, you should use command line like
this:

	# mount -Tio-pkt -o bind=en0 lsm-qnet.so

Also, please double check "en0" is the interface you want QNET running
on, depends on how you setup the vmware, it might in a different name.

-xtang

> -----Original Message-----
> From: Daniel Fearon [mailto:community-noreply@qnx.com]
> Sent: September 30, 2009 10:16 AM
> To: general-community
> Subject: Re: RE: Disabling QNET comms on a single interface
> 
> Thank you for your response, which I've attempted to follow. So far,
I've
> been unsuccessful in getting Qnet to bind to the en0 interface.
> 
> Below is a run down of the steps I took to achieve this:
> 
> # cd /usr/qnx641/target/qnx6/x86/boot/build/
> # vi qnxbasesmp.build
> 
> Change the existing entry below to what you have suggested (further
below):
> 
> "mount -Tio-pkt lsm-qnet.so"
> becomes... "mount -Tio-pkt -p bind=en0 lsm-qnet.so"
> (note - i have tried -p bind=en0 before and after lsm-qnet.so)
> 
> Write changes to the file and then create a new ifs image, which is
loaded
> on the next startup:
> # mkifs qnxbasesmp.build /.boot/qnxbasesmp.ifs
> 
> 
> Can you confirm that I'm using the correct parameters you have
suggested,
> and if this is the correct location to be calling them? I think it's
quite
> close and sounds like a very plausible solution, so any further
assistance
> to get there would be greatly appreciated.
> 
> 
> Thanks,
> Danny
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post39074
Daniel Fearon
09/30/2009 10:47 AM
post39079
Re: RE: RE: Disabling QNET comms on a single interface   
Perfect!

That was exactly the entry I required... and now after changing this, I no longer have my unwanted Qnet traffic flooding
 the LAN via the en1 interface.

Thanks for your help.

Danny
Mario Charest
09/30/2009 10:50 AM
post39081
RE: RE: RE: Disabling QNET comms on a single interface   
Have you tried using the e1000 driver with ESX 4.0.  Check this forum there is a thread about it.  I could get it to 
work with VMWARE 6.5 but our ESX is version 3.5.  We assume that is why it didn`t work.

I read that this driver perform much better than the pcamd driver.  There is also a specific driver from vmware that was
 posted in this same thread, but same thing, couldn`t get it working in ESX 3.5

Curious to see if it works with ESX 4.0

> -----Original Message-----
> From: Daniel Fearon [mailto:community-noreply@qnx.com]
> Sent: Wednesday, September 30, 2009 10:48 AM
> To: general-community
> Subject: Re: RE: RE: Disabling QNET comms on a single interface
> 
> Perfect!
> 
> That was exactly the entry I required... and now after changing this, I
> no longer have my unwanted Qnet traffic flooding the LAN via the en1
> interface.
> 
> Thanks for your help.
> 
> Danny
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post39079
>
Daniel Fearon
10/01/2009 6:03 AM
post39158
Re: RE: RE: RE: Disabling QNET comms on a single interface   
Hi Mario,

Apologies, I've not had any experience so far in testing e1000 driver with ESX 4.0.

If I do have any requirement to test this in the near future, I will let you know the outcome.

Regards,
Danny

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems