Provides details displayed on the Cisco RADKit service in Cisco SD-WAN Manager.
By verifiying Cisco RADKit service in Cisco SD-WAN Manager , you can confirm the Cisco RADKit Service's operational status (enabled or disabled).
This section provides the steps to verify whether the Cisco RADKit service in Cisco SD-WAN Manager is enabled or disabled.
Before you begin
-
Ensure you have CLI access to Cisco SD-WAN Manager .
Procedure
From the CLI interface of Cisco SD-WAN Manager , execute the following command:
request nms container-manager diagnostics
NMS container manager
Checking container-manager status
Listing all images
------------------------
REPOSITORY TAG IMAGE ID CREATED SIZE
sdwan/reporting latest 10d3363a0c7c 15 hours ago 941MB
sdwan/messaging-server 0.20.0 30547ceba4b9 15 hours ago 150MB
sdwan/radkit 1.8.6rc1 5ebe514b17d4 15 hours ago 782MB
sdwan/cluster-orchestrator 1.0.1 5aa1fd0e8e18 15 hours ago 669MB
sdwan/configuration-db 4.4.38 d6b9eb6fd60e 15 hours ago 548MB
sdwan/olap-db 24.3.6.48 219369311a35 15 hours ago 409MB
sdwan/cloudagent-v2 1.0.0 a56c3552ab49 15 hours ago 703MB
sdwan/upgrade-coordinator 2.0.0 d95f20da260b 15 hours ago 141MB
sdwan/application-server 24.0.1 7d505d68bf3f 15 hours ago 1.15GB
sdwan/coordination-server 3.8.4 91b45542b9e2 15 hours ago 346MB
sdwan/vault 1.0.1 b2323a89ada8 2 weeks ago 511MB
sdavc 4.7.0 d1512d663ac7 7 weeks ago 749MB
sdavc-gw 4.7.0 4ed15cea64ee 7 weeks ago 463MB
Listing all containers
------------------------
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ed8024e0dbb5 sdwan/messaging-server:0.20.0 "/bin/bash /entrypoi…" 6 minutes ago Up 6 minutes (healthy) 127.0.0.1:4222->4222/tcp, 127.0.0.1:6222->6222/tcp, 127.0.0.1:8222->8222/tcp messaging-server
9013b37451d9 sdwan/olap-db:24.3.6.48 "/usr/bin/tini -- /e…" 6 minutes ago Up 6 minutes (healthy) 127.0.0.1:8123->8123/tcp, 127.0.0.1:9363->9363/tcp olap-db
95fea11679e7 sdwan/cloudagent-v2:1.0.0 "./entrypoint.sh" 6 minutes ago Up 6 minutes (healthy) 127.0.0.1:9051-9052->9051-9052/tcp cloudagent-v2
2e534bbea1af sdwan/reporting:latest "/usr/bin/tini -g --…" 6 minutes ago Up 6 minutes 80/tcp, 127.0.0.1:9080->9080/tcp reporting
b25381e8e543 sdwan/coordination-server:3.8.4 "/docker-entrypoint.…" 6 minutes ago Up 6 minutes (healthy) 127.0.0.1:2181->2181/tcp, 127.0.0.1:2888->2888/tcp, 127.0.0.1:3888->3888/tcp, 127.0.0.1:4888->4888/tcp coordination-server
0b696e5f38d5 sdwan/vault:1.0.1 "docker-entrypoint.s…" 6 minutes ago Up 6 minutes (healthy) 8200/tcp, 127.0.0.1:8201-8202->8201-8202/tcp vault
3c7254a24f5a sdavc:4.7.0 "/usr/local/bin/sdav…" 6 minutes ago Up About a minute (healthy) 127.0.0.1:10503->8080/tcp, 127.0.0.1:10504->8443/tcp sdavc
944e74177a8f sdavc-gw:4.7.0 "/bin/bash -c 'exec …" 6 minutes ago Up 6 minutes (healthy) 127.0.0.1:8444->8444/tcp, 127.0.0.1:10501->8080/tcp, 127.0.0.1:10502->8443/tcp, 127.0.0.1:10000->50000/udp sdavc-gw
0c9c29dbf0a8 sdwan/configuration-db:4.4.38 "/usr/bin/tini -g --…" 6 minutes ago Up 6 minutes (healthy) 127.0.0.1:2004->2004/tcp, 127.0.0.1:5000->5000/tcp, 127.0.0.1:6000->6000/tcp, 127.0.0.1:6362->6362/tcp, 127.0.0.1:6372->6372/tcp, 127.0.0.1:7000->7000/tcp, 127.0.0.1:7473-7474->7473-7474/tcp, 127.0.0.1:7687-7688->7687-7688/tcp configuration-db
c7fe7153a21a sdwan/application-server:24.0.1 "/usr/bin/tini -g --…" 6 minutes ago Up 6 minutes (healthy) base-application-server
6c8f3ec5103f sdwan/cluster-orchestrator:1.0.1 "/entrypoint.sh" 7 minutes ago Up 7 minutes (healthy) 127.0.0.1:9090->9090/tcp, 127.0.0.1:9099->9099/tcp cluster-orchestrator
Docker info
------------------------
Client:
Context: default
Debug Mode: false
Server:
Containers: 11
Running: 11
Paused: 0
Stopped: 0
Images: 13
Server Version: 23.0.6
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: local
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: b1624c3628954e769dd50783b63823040b2db38c.m
runc version: v1.1.14-0-g2c9f5602-dirty
init version: b9f42a0-dirty
Security Options:
seccomp
Profile: builtin
Kernel Version: 6.6.21-yocto-standard
Operating System: viptela 20.18.1 (scarthgap)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 23.48GiB
Name: vm
ID: 7f6e3203-ad3a-40af-aacd-21e43cbe1c9c
Docker Root Dir: /var/lib/nms/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
What to do next
Analyse the output within the Listing all containers section; the radkit container will be listed there Cisco RADKit service if is enabled.
For detailed information on Cisco RADKit user operations, see the documentation: https://radkit.cisco.com/docs/control_api/control_api.html#user-operations.