search cancel

No Logical Ports Listed (Capture Device not Initialized in Database)


Article ID: 106798


Updated On:


CA Application Delivery Analysis MTP (NetQoS / ADA)


During the VMTP software installation, the install *should* detect the type of Napatech card (4x1,8x1,2x10) and initialize the database appropriately.  If there is a problem during this step, the info in the database is not initialized and some manual steps are required to correct it.  The most likely reason that the Napatech card cannot be detected is that something came loose during shipment and the card needs to be reseated. 


Component: NQSAMP


  1. Log into the VMTP system.   Run the following commands to determine if the software can currently detect the Napatech card.  The following shows fully-qualified commands.  If you run them by cd’ing to the folder, make sure you qualify them with ./  (e.g. ./AdapterInfo).
               sudo   /opt/napatech/bin/AdapterInfo     

 you should see the card info; if this is an 8x1, you will be prompted for 0 or 1 to indicate the card.

               sudo   /opt/NetQoS/bin/nqnapautil  PortCount    

You should see something similar to ‘ PortCount=8,CardType=NT4’  (port count will vary..2,4,or 8; 2x10 will show CardType=NT20).
If either of the above commands indicate an error, then continue with Step 2.  If both work OK, go on to Step 3.
  1. Try unloading/reloading the Napatech driver.  You will need to put /sbin and /usr/sbin in the path since they are not there for the netqos account.
    • To see the path:  echo $PATH
    • To update the path:      export PATH=$PATH:/sbin:/usr/sbin
    • To unload the Napatech driver:    sudo /opt/napatech/bin/
    • To load the Napatech driver:    sudo /opt/napatech/bin/
If loading the driver indicates no problems, go back and try the commands in Step 1; if they are now successful continue with Step 3.

If loading the driver indicates errors, you may be able to get more information by typing ‘dmesg’ … all messages starting with ‘ntki’ are related t the Napatech driver.  At this point, the most likely cause is that the hardware may have come loose during shipment and needs to be reseated. 

Shutdown the VMTP machine (using  sudo /sbin/shutdown –h  now).  Open up the machine and reseat the card; if dmesg indicated any ntki errors related to SDRAM, reseat the memory module as well.  If this is an 8x1, reseat both the NT4E card and the expansion card as well as the ribbon cable connector.  After powering on the machine, go back to Step 1.
  1. Once the commands in Step 1 are successful, do the following to initialize the database and get things running.
  • To initialize the database:
    • sudo /opt/NetQoS/scripts/

You should see some messages indicating the database configuration is being created.This script also automatically adjusts the size of the /nqtmp/headers filesystem if needed.
  • On the VMTP web GUI, go to the Admin->Processes page and start the nqcapd process.  Also start the nqmetricd process if you had stopped that one.
  • Then go to the System Status page.   You should now see nqcapd running as well Capture Card port status and statistics.
If the above steps don’t resolve the problem, go to the web UI Admin -> System Logs page and generate a file for support so the problem can be investigated further.