Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

NorthStar Controller Troubleshooting Overview

 

In the Web UI, the Dashboard View and Event View (Applications>Event View) provide information that can help with troubleshooting.

For additional information to help identify and troubleshoot issues with the Path Computation Server (PCS) or NorthStar Controller application, you can access the log files.

Note

If you are unable to resolve a problem with the NorthStar Controller, we recommend that you forward the debug files generated by the NorthStar Controller debugging utility to JTAC for evaluation. Currently all debug files are located in subdirectories under the u/wandl/tmp directory.

You can use either of the following methods to collect debug files:

  • Log in to the NorthStar Controller Java Client Operator UI as administrator and click Collect Debug Traces. The NorthStar Controller generates a debug file, for example, NS-Trace-2015-04-10T22-18-55.919.tbz.

  • Log in to the NorthStar Controller CLI, and execute the command u/wandl/bin/system-diagnostic.sh filename.

    The output is generated and available from the /tmp directory in the filename.tbz2 debug file.

Table 1 lists the NorthStar Controller log files most commonly used to identify and troubleshoot issues with the PCS and PCE. All log files are located under the /opt/northstar/logs directory.

Table 1: NorthStar Controller Log Files

Log FilesDescription

cassandra.msg

Log events related to the cassandra database.

configServer.msg

Log files related to maintaining LSP configuration states in NorthStar Controller. LSP configuration states are updated by collecting show commands and NETCONF provisioning.

ha_agent.msg

HA coordinator log.

mlAdaptor.log

Interface to transport controller log.

netconfd.msg

Log files related to communication between NorthStar Controller and devices via NETCONF sessions.

net_setup.log

Configuration script log.

nodejs.msg

Log events related to nodejs.

pcep_server.log

Log files related to communication between the PCC and the PCE in both directions.

pcs.log

Log files related to the PCS, which includes any event received by PCS from Toposerver and any event from Toposerver to PCS including provisioning orders. This log also contains any communication errors as well as any issues that prevent the PCS from starting up properly.

rest_api.log

Logs files of REST API requests.

toposerver.log

Log files related to the topology server.

Contains the record of the events between the PCS and topology server, the topology server and NTAD, and the topology server and the PCE server

Note: Any message forwarded to the pcshandler.log file is also forwarded to the pcs.log file.