Troubleshooting Trusted Network Connect Patch Management

Learn the possible causes for failure and the steps to troubleshoot the TNC Patch Management system.

To troubleshoot the TNC Patch Management system, verify the configuration settings that are listed in the following table.
Table 1. Troubleshooting the configuration settings for the TNC Patch Management systems
Problem Solution
TNC server is not starting or responding Complete the following procedure:
  1. Determine whether the TNC server daemon is running by entering the command:
    ps –eaf | grep tncsd
  2. Restart the server.

If that does not solve the problem, check the TNC server configuration file /etc/tnccs.conf to verify that the component parameter is set to SERVER.
The TNC Patch Management server is not starting or responding
  • Determine whether the TNC Patch Management server daemon is running by entering the following command:
    ps –eaf | grep tncpmd
  • Check the /etc/tnccs.conf configuration file for the component = TNCPM entry on the TNC Patch Management server.
TNC client is not starting or responding
  • Determine whether the TNC client daemon is running by entering the following command:
    ps –eaf | grep tnccd
  • Check the /etc/tnccs.conf configuration file for the component = CLIENT entry on the TNC client.
TNC IP referrer is not running on Virtual I/O Server > (VIOS )
  • Determine whether the TNC IP referrer daemon is running by entering the following command:
    ps –eaf | grep tnccsd
  • Check the /etc/tnccs.conf configuration file for the component = IPREF entry on VIOS .
Unable to configure a system as both a TNC server and client The TNC server and client cannot run simultaneously on the same system.
Daemons are running but verification does not happen Enable the log messages for the daemons. Set the level=info log in the /etc/tnccs.conf file. You can analyze the log messages.