Cisco Cisco Virtual Managed Services 1.02 Troubleshooting Guide
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
5. Network Services Orchestrator (NSO)
142
5.8 Troubleshooting
NSO Log Overview
NSO logs are stored in the following directory:
/var/log/ncs
.
Most of the log files are enabled in the
ncs.conf
file under the
/ncs-config/logs
section unless specified
otherwise.
Please refer to the "
" section in chapter 5.3 "NSO Configuration" for details on how to enable/disable
logs.
Note: If NSO is deployed in a clustered configuration, some of the following log and
trace files are specific to NSO Service or Device nodes, while others exist on both
trace files are specific to NSO Service or Device nodes, while others exist on both
nodes.
Audit Log
NSO Audit Log
audit.log
exists on both Service and Device nodes. It contains audit trails which track
changes that have been made to an NSO device.
Day 0 Server Access Logs
Day 0 Server Access Logs are stored in
day0server:<devicename>.access
file that contains Day 0 HTTP
server access logs.
It exists on both Service and Device nodes.
Developer Log
Developer log
devel.log
is a debug log for troubleshooting user-written Java code. It exists on both Service
and Device nodes. Check this log for problems with user- written code, etc. This log is enabled by default.
Developer log is used to troubleshoot HA-clustering issues.
Developer log is used to troubleshoot HA-clustering issues.
NCS Error Log
NCS error log is used for internal logging from the NCS daemon. It is used for troubleshooting the NCS
daemon itself. Enable this log when NSO crashes, reports an "Internal error," or the error is related to the
NCS daemon. This log creates at least three different files; all these files are needed to be able to read it. This
log is particularly useful for Cisco developers. It exists on both Service and Device nodes and is stored in
daemon itself. Enable this log when NSO crashes, reports an "Internal error," or the error is related to the
NCS daemon. This log creates at least three different files; all these files are needed to be able to read it. This
log is particularly useful for Cisco developers. It exists on both Service and Device nodes and is stored in
ncserr.log.1
in a binary format.