Example: Troubleshoot DCS
The Device Connectivity Service (DCS) is responsible for establishing and maintaining the connection to the SRX Series Firewall. The service handles requests for any interactions with the device, such as deploying configurations. Follow the steps in this topic to troubleshoot DCS.
Problem
The DCS is not operational. This issue may affect the capability of Juniper Security Director to communicate with managed firewalls and execute specific tasks such as remote management, monitoring, or integrating with other network services.
To check the status of services running on the VM, navigate to .
Solution
To resolve this issue, check the configuration settings, ensure that the service is enabled, and troubleshoot any underlying problems that might be causing the service to be inactive.
Follow the steps below to verify the status of the DCS service and its configuration. You can share this information with the Juniper Networks support team to troubleshoot any issues.
Check the status of all services using the CLI command
show service.show service 2025-01-08 11:23:58 UTC Name Age Ready ------------------------------------------------------------------- rke2-canal 1/1 2d3h metallb-speaker 1/1 2d3h dcs 0/0 2d3h …...............................
Run the command
show service | dcsto check the status of DCS service.show service | dcs dcs 0/0 2d3h
Check the number of healthy services using the command
show health apps.show health apps 2025-01-08 11:32:24 UTC Status: Running Faults: application/degraded/logapiserver - Application is in a degraded state. Apps: status: 39/40 services are healthy Bootservice: status: Service has completed successfully. Kubernetes: status: Service is active. System: address: 10.157.76.15 hostname: tejas-1295 uptime: 0 Days, 5 Hours, 14 Minutes, 5 Seconds $
Run the command
show pods list dcsto view the list of DCS pods and their statuses.show pods list dcs NAME READY STATUS RESTARTS AGE -------------------------------------------------------------------------------- dcs-85ccff4bbd-bp7xv 0/1 Inactive 0 30m dcs-85ccff4bbd-wg8qd 1/1 Running 0 42d dcs-copyiamsecret-0.0.4-g1bdf1d3e61-kzkkp 0/1 Completed 0 42d $
Check the configuration information about the DCS pod dcs-85ccff4bbd-bp7xv using the CLI command
show pods pod dcs-85ccff4bbd-bp7xv.show pods pod dcs-85ccff4bbd-bp7xv 2025-01-07 13:20:51 UTC ------------------------------- Describing pod: dcs-5956bf6bc6-9bzbf ------------------------------- Name: dcs-85ccff4bbd-bp7xv Namespace: ems Priority: 0 Service Account: dcs Node: tejas-1295/10.157.76.15 Start Time: Tue, 07 Jan 2025 13:19:22 +0000 Labels: app=dcs pod-template-hash=5956bf6bc6 Annotations: cni.projectcalico.org/containerID: c5a1bac65b9fc1bd6b648305464827494deccf841db6df8145063827cc65575d cni.projectcalico.org/podIP: 10.42.0.92/32 Status: Pending IP: 10.42.0.92 IPs: IP: 10.42.0.92 Controlled By: ReplicaSet/dcs-5956bf6bc6 Init Containers: init: Container ID: containerd://19be4dcfe71631a9b00e5da0eda69932644a0ffd2928a73d99151318dcb1cda3 Image: sdop-repo.local:5000/security-director-docker/airshipit/kubernetes-entrypoint:v1.0.0 Image ID: sdop-repo.local:5000/security-director-docker/airshipit/kubernetes-entrypoint@sha256:6111e651cef1d435c469df815271a0bb143ff0dbfbac3ceb84ce0a0d6cf0b87b Port: <none> Host Port: <none> Command: …...................................
Check the logs of the DCS pod dcs-85ccff4bbd-bp7xv using the CLI command
show logs pod dcs-85ccff4bbd-bp7xv.show logs pod dcs-85ccff4bbd-bp7xv 2025-01-08 16:41:30 UTC ------------------------------- Logs for pod: dcs-758b9cc77d-x2hzq ------------------------------- Defaulted container "dcs" out of: dcs, init (init) scav 0 KiB work, 60560 KiB total, 100% util scav 32 KiB work, 59792 KiB total, 98% util time="2025-01-08T12:04:05Z" level=info msg="initializing audit logger for host: auditlog.auditlog:9222" type=APPLOG time="2025-01-08T12:04:05Z" level=info msg="provider connecting to auditlog server: auditlog-central.auditlog:9222" type=APPLOG {"level":"info","msg":"Current log level is: info","time":"2025-01-08T12:04:05Z","type":"APPLOG"} …................................ {"level":"info","msg":"number of connections on each dcs pod is map[10.42.0.145:{0 0}]","time":"2025-01-08T16:44:05Z","type":"APPLOG"} {"level":"info","msg":"Updated connection details in HA cache.","time":"2025-01-08T16:44:05Z","type":"APPLOG"} {"level":"info","msg":"DCS client is already available in cache making use of it for endpoint 10.42.0.146:9222 ","time":"2025-01-08T16:44:05Z","traceid":"NO-REQUESTID","type":"APPLOG"} {"level":"info","msg":"number of connections on each dcs pod is map[10.42.0.145:{0 0} 10.42.0.146:{0 0}]","time":"2025-01-08T16:44:05Z","type":"APPLOG"} {"level":"info","msg":"Updated connection details in HA cache.","time":"2025-01-08T16:44:05Z","type":"APPLOG"} $Export the logs using the command
systemlogs export-log.systemlogs export-log feature-group Select the feature groups to be included in the log package service-group Select the service groups to be included in the log package timespan Limit logs for the days specified <cr>
$ systemlogs export-log service-group dcs timespan 1
Restart the service using the CLI command
service restart dcs.service restart dcs deployment.apps/dcs restarted
Run the command
show pods list dcsto view the list of DCS pods and their statuses.show pods list | dcs 2025-01-08 12:00:56 UTC ems dcs-85ccff4bbd-bp7xv 0/1 Init:0/1 0 4s ems dcs-85ccff4bbd-wg8qd 1/1 Running 0 6m23s
show pods list | dcs 2025-01-08 12:02:08 UTC ems dcs-85ccff4bbd-bp7xv 1/1 Running 0 76s ems dcs-85ccff4bbd-wg8qd 1/1 Running 0 7m35s
Check the stats of the DCS service using the command
show stats dcs.show stats dcs 2025-01-09 08:16:46 UTC NAME CPU(cores) MEMORY(bytes) dcs-758b9cc77d-65hzr 1m 16Mi dcs-758b9cc77d-pwgs4 1m 17Mi $
Check the details of the DCS service using the command
show service dcs.show service dcs Name: dcs Namespace: ems CreationTimestamp: Mon, 06 Jan 2025 07:40:17 +0000 Labels: app=dcs app.kubernetes.io/managed-by=Helm Annotations: deployment.kubernetes.io/revision: 1 meta.helm.sh/release-name: dcs meta.helm.sh/release-namespace: ems secret.reloader.stakater.com/reload: dcs-cert Selector: app=dcs Replicas: 2 desired | 2 updated | 2 total | 2 available | 0 unavailable StrategyType: RollingUpdate MinReadySeconds: 0 RollingUpdateStrategy: 25% max unavailable, 25% max surge Pod Template: Labels: app=dcs …........................................ NewReplicaSet: dcs-5956bf6bc6 (0/0 replicas created) Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ScalingReplicaSet 15m deployment-controller Scaled down replica set dcs-5956bf6bc6 to 0 from 2 $
If the service restarts successfully, DCS will resume normal operation. To verify the service status, go to .