As mentioned before, io-pkt* is the framework used to connect drivers and protocols. In order to troubleshoot this, use the following pidin command:
$ pidin -P io-pkt-v4-hc mem
Look for the Qnet shared object in the output:
pid tid name prio STATE code data stack
118802 1 sbin/io-pkt-v4-hc 21o SIGWAITINFO 876K 672K 4096(516K)*
118802 2 sbin/io-pkt-v4-hc 21o RECEIVE 876K 672K 8192(132K)
118802 3 sbin/io-pkt-v4-hc 21r RECEIVE 876K 672K 4096(132K)
118802 4 sbin/io-pkt-v4-hc 21o RECEIVE 876K 672K 4096(132K)
118802 5 sbin/io-pkt-v4-hc 20o RECEIVE 876K 672K 4096(132K)
118802 6 sbin/io-pkt-v4-hc 10o RECEIVE 876K 672K 4096(132K)
libc.so.2 @b0300000 436K 12K
devnp-abc100.so @b8208000 40K 4096
lsm-qnet.so @b8213000 168K 36K
If the output includes an lsm-qnet.so shared object, Qnet is running.