After containers are deployed, use the available commands to check deployment status, collect logs, manage the container lifecycle (stop/restart/destroy), and so on.
Usage
dux [command] [flags]
Global Flags
-h, --help Print help information
-v, --verbose Show verbose logs
Available commands for --help
about Get legal and privacy information about Dux
cg CLI to deploy and manage Content Gateway containers
eic CLI to deploy and manage EIC containers
pacreader CLI to deploy and manage PAC Reader container
seg CLI to deploy and manage SEG containers
tunnel CLI to deploy and manage Tunnel containers
version Get the version of dux
| Operation | Purpose | Command(s) | Container Type |
|---|---|---|---|
| Check status | View deployment status, version, OS, and other key health check | dux status [flags] - get status of single/multiple container deploymentdux <container> status - get status by specifying the container type Example: dux cg status - get status of content gatewaydux status -p 10.87.132.110 - get status of a host/hosts by IP dux status -n 1 - get status of a specific host with node-number as listed in the manifest file | CG, SEG, Tunnel, EIC, PAC Reader |
| Fetch logs | Download log bundle (or docker logs if down) | dux logs [flags]Example: dux logs -p 1.2.3.4 -p 1.2.3.5 - fetch logs from a single deployment or multiple deployments by specifying IP in the order as per the manifestdux logs -n 2 -n 4 - fetch logs from a single deployment or multiple deployments by node-number in the order as per the manifestdux logs -n 1 -f - continuously view/follow the run logs of container for a specific node/host ip | CG, SEG, Tunnel, EIC, PAC Reader |
| Stop containers | Stop containers on target hosts | dux stopdux stop -p 1.2.3.4 - stop the deployment of container by specifying IP in the order as per the manifestdux stop -n 2 - stop the deployment of container by specifying node number in the order as per the manifest | CG, SEG, Tunnel, EIC, PAC Reader |
| Restart containers | Restart previously stopped containers | dux restart [flags]dux restart -y - restart container and auto-accept all prompts for y/n | CG, SEG, Tunnel, EIC, PAC Reader |
| Destroy containers | Stop and remove containers from host(s) | dux destroy [flags]dux destroy -n 4 - destroy the deployment of container by specifying node number in the order as per the manifest | CG, SEG, Tunnel, EIC, PAC Reader |
| Verbose output | Show detailed logs for any command | dux deploy -v | CG, SEG, Tunnel, EIC, PAC Reader |
| Interactive shell | Open a shell inside a container | dux exec-shell [flags]Example: dux exec-shell -n 1 | CG, SEG, Tunnel, EIC, PAC Reader |
| Fetch report | Fetch vpnreport of a container | dux report -r 1,6,10 - fetches the row numbers 1,6, and 10 from all hosts dux report - get vpnreport of containers deployed dux report -j - get vpnreport output as json format for processing | Tunnel |
Using about command to get legal and privacy information on dux
dux about
Copyright © 2024-2026 Omnissa. All rights reserved. This product is protected by copyright and intellectual property laws in the United States and other countries as well as by international treaties. Its use is subject to the legal terms in place between you and Omnissa.
• Omnissa's general and offering-specific legal terms for its products and services are available at: https://www.omnissa.com/legal-center/
• Omnissa's privacy notice for products and services is located at: https://www.omnissa.com/omnissa-products-services-privacy-notice/
• Omnissa's open-source software notices can be found at: https://www.omnissa.com/open-source-notices/
Commands specific to Tunnel container
dux tunnel --help
CLI to deploy and manage Tunnel containers
Usage:
dux tunnel [command]
Available Commands:
deploy Deploy Tunnel containers
destroy Destroy the Tunnel containers on the given hosts
exec-shell Open interactive shell with Tunnel container
extportscan Check for open ports in the external NIC of the Tunnel container hosts
init Create a manifest file for configuring Tunnel container details for deployment and management
list List/search sessions, flows, alerts or allowlist from Tunnel container logs
log-override Override log level in one or more Tunnel containers deployed
logs Get logs from the Tunnel containers deployed
report Fetch vpnreport of a Tunnel container
restart Restart the Tunnel container on given hosts
status Get the status of the Tunnel containers deployed
stop Stop the Tunnel containers on given hosts
Flags:
-h, --help Print help information
-v, --verbose Show verbose logs
Check for open ports in the external NIC of the Tunnel container hosts (extportscan)
If you are using a two-NIC configuration — one NIC for unauthenticated/external traffic (External NIC) and a second NIC for authenticated back-end traffic (Internal NIC), extportscan can be executed to validate for the following security issues in the external NIC/IP of the Tunnel host.
- Verify SSH is not listening on the external IP
To ensure SSH is not accessible through the external IP on your machine, SSH should be configured to only listen on specific interfaces (internal IP, or 127.0.0.1 or any IPs explicitly configured) and not on all interfaces - 0.0.0.0 or external IP. - Port Scan for External IP
Ensure port 22 (default SSH Port) is not open in the External IP. In addition, list all open ports for the user to check for any security issues. Note: External IP can be provided using themulti_nic_external_ipparameter on the manifest file.
Override log level in one or more Tunnel containers deployed
To change the log level in Tunnel Container, use the log-override command.
Example
dux log-override -n 1 -l 4 -d 10
Are you sure you want to set log level in the Tunnel containers deployed in the following hosts to "Debug" for 10 mins?
ip : 192.14.84.166 node-number : 1
Please confirm (y/n): y
Log-level was succesfully set to "Debug" in Tunnel container on 192.14.84.166
Enhancements to search and list records from Tunnel container logs
The dux list command can be used to search and list sessions, flows, alerts, or allowlist records from Tunnel server container logs. It provides various filtering options to narrow down the results based on user, destination, time range, and so on.
dux list --help
Global Flags:
-h, --help Print help information
-v, --verbose Show verbose logs
Examples
| Task | Command |
|---|---|
| List all records (alerts, sessions, and flows) | dux tunnel list --all |
List allowlist cache along with all records for node number 1 | dux tunnel list --allowlist-cache -n 1 |
| Filter records by destination | dux tunnel list --dest www.example.com |
| Filter records by user | dux tunnel list --user john |
| List alerts within a specific time range (RFC-3339 UTC) | dux tunnel list --alert --start 2025-03-20T04:00:00Z --end 2025-03-20T05:00:29Z |
Commands and flags specific to PAC Reader
Use the update command to update the PAC Reader container on a given host with new runtime values.
| Flag | Description |
|---|---|
-l, --log-level | Update log level for PAC Reader container Example --log-level 4 [debug=4, info=3, warn=2, error=2, off=0]) |
-a, --proxy-auth | Update proxy auth for PAC Reader container |
-r, --refresh int | Update pac refresh interval in seconds for PAC Reader container |
Examples
| Task | Command | Example |
|---|---|---|
| Update the log level on PAC Reader container | dux pacreader update -l 4 | Updating log level for PAC Reader container on 192.62.82.52 to level 5 PAC Reader container was successfully restarted on 192.62.82.52 |
| Update the refresh interval on PAC Reader container | dux pacreader update -r 300 | Updating pac refresh interval for PAC Reader container on 192.62.82.52 to 300 secondsPAC Reader container was successfully restarted on 192.62.82.52 |
| Update the proxy auth on PAC Reader container | dux pacreader update -a |
Cette page vous a-t-elle été utile ?