Starting Qnet

To start Qnet, load the lsm-qnet.so shared object into the network manager.

The io-pkt* manager is a process that assumes the central role to load a number of shared objects. It provides the framework for the entire protocol stack and lets data pass between modules. In the case of native networking, the shared objects are lsm-qnet.so and networking drivers (devnp-*.so). The shared objects are arranged in a hierarchy, with the end user on the top, and hardware on the bottom.

Note:

It's possible to run more than one instance of io-pkt, but doing so requires a special setup. If you want to start io-pkt* “by hand,” you should slay the running io-pkt* first.
You can have at most one instance of Qnet running on a node, even if you're running more than one instance of io-pkt.

You can start the io-pkt* from the command line, telling it which drivers and protocols to load:

$ io-pkt-v4-hc -d abc100  -p qnet

This causes io-pkt-v4-hc to load the fictitious devnp-abc100.so Ethernet driver and the Qnet protocol stack.

Or, you can use the mount and umount` commands to start and stop modules dynamically, like this:

$ io-pkt-v6-hc 
$ mount -Tio-pkt devnp-abc100.so
$ mount -Tio-pkt lsm-qnet.so

To unload the driver, use the ifconfig destroy command.

Note: You can't unmount a protocol stack such as TCP/IP or Qnet.