> For the complete documentation index, see [llms.txt](https://nso-docs.cisco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nso-docs.cisco.com/guides/resources/man/ncs-collect-tech-report.1.md).

# ncs-collect-tech-report

`ncs-collect-tech-report` - Command to collect diagnostics from an NCS installation.

## Synopsis

`ncs-collect-tech-report [--install-dir InstallDir] [--full] [--num-debug-dumps Integer]`

## Description

The `ncs-collect-tech-report` command can be used to collect diagnostics from an NCS installation. The resulting diagnostics file contains information that is useful to Cisco support to diagnose problems and errors.

If the NCS daemon is running, runtime data from the running daemon will be collected. If the NCS daemon is not running, only static files will be collected.

## Options

`[ --install-dir InstallDir ]`

> Specifies the directory for installation of NCS static files, like the `--install-dir` option to the installer. If this option is omitted, `/opt/ncs` will be used for \<InstallDir>.

`[ --full ]`

> This option is used to also include a full backup (as produced by [ncs-backup(1)](/guides/resources/man/ncs-backup.1.md)) of the system. This helps Cisco support to reproduce issues locally.

`[ --num-debug-dumps Count ]`

> This option is useful when a resource leak (memory/file descriptors) is suspected. It instructs the `ncs-collect-tech-report` script to run the command `ncs --debug-dump` multiple times.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nso-docs.cisco.com/guides/resources/man/ncs-collect-tech-report.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.