Troubleshooting Commands
Use this topic to learn more about the Routing Director support and troubleshooting commands.
request deployment support information
The request
deployment
support information command displays an in-depth status report of your
Routing Director cluster configuration.
The show commands that are executed when you run the request
deployment
support information command are listed in Table 1.
|
Command |
Description |
|---|---|
|
Shows node information of your Routing Director cluster. |
|
|
Shows pod information of your Routing Director cluster. |
|
|
Shows namespace information of your Routing Director cluster. |
|
|
Shows storage and controller node information of your Routing Director cluster. |
|
|
Shows the version of your Routing Director cluster. |
|
|
Shows the version of pods in your Routing Director cluster. |
|
|
|
Shows the top pods of the |
|
Shows the top pods of the |
|
|
Shows the persistent volume (PV) and persistent volume claim (PVC) information. |
The request
deployment
support information command also runs many kubectl
commands. These commands provide you debugging information such as Helm deployment
service information for the NorthStar namespace, Kubernetes deployment information
for api-aggregator service, and so on.
request deployment troubleshooting information
The request
deployment
troubleshooting information command provides troubleshooting
information of the ems, foghorn,
insights, paa, trust, and
pathfinder Routing Director services.
To view the list of available services, run the following command:
user@node> request deployment troubleshooting information service ? Possible completions: ems ems service foghorn foghorn service insights insights service paa paa service pathfinder pathfinder service trust trust service
When you run the request
deployment
troubleshooting information command, a
troubleshooting_date_time.tar.gz
file is generated. You can share this file with the Juniper Technical
Assistance Center (JTAC) for further evaluation. This
.tar.gz file is saved in the
/root/troubleshooting/ directory.
The commands that are executed when you run the request
deployment
troubleshooting information command are listed in Table 2.
|
Command |
Description |
|---|---|
|
|
Generates log files of different services within the
|
|
|
Generates log files of different services within the
|
|
|
Generates a log file of the |
|
|
Generates log files of different services within the
|
|
|
Generates log files of different services within the
|
|
Generates a text file (JSON format) with Postgres information. |
Additional Debugging Commands
You can run commands to collect data from the Redis database, Kafka messages, service logs, and the time series database (TSDB). You can use this data to troubleshoot issues with your Routing Director cluster. These commands are not part of the Deployment Shell CLI troubleshooting commands, and must be run separately. Table 3 lists the commands.
|
Command |
Description |
|---|---|
|
Kafka |
|
|
Display possible completions for the |
|
|
|
Generate an output file of Kafka messages for a topic for a specified period of time. |
|
Insights Kafka |
|
|
Display possible completions for the |
|
|
|
Display |
|
Redis |
|
|
Display possible completions for the |
|
|
|
Display Redis key pattern information
for |
|
|
Generate an output file of Redis key pattern information
for |
|
Service Logs |
|
request
deployment
debug logs ? |
Display possible completions for the |
|
|
Generate a log file for a service within a namespace for the specified time period. |
|
TSDB |
|
|
Display possible completions for the |
|
|
|
Generate an output file of TSDB data for a particular device. |
|
Postgres |
|
|
Display possible completions for the |
|
|
|
Generate an output file of the measurement value information of the Postgres database. |