skip to main content
Admin Guide > Appendix D: ICE Agent Operation
Appendix D: ICE Agent Operation
 
Installing ICE Agent
ICE Agent Requirements
Installing ICE Agent as a Native Command-Line Application
Installing ICE Agent as a Docker Container
Installing ICE Agent as a Linux Systemd Service
Verifying ICE Agent Installation
Troubleshooting Issues Reported by Doctor
Commanding ICE Agent
Understanding the structure of ICE Agent commands
ICE Agent Help Switch
Using Environment Variables
Using an Environment File
Using a Command File
‘For Engineering Use’ Warning
Determining your Installation ID
External Server Coasting
Deploying RP/SR/PS using Docker
Running Docker-Contained Server Components in the Background
Launching an External Patch Server via ICE Agent
An ICE Agent is a downloadable component with a command line interface that runs on Linux, Windows, or Mac operating systems. It is used to install and manage external (or satellite) server components, including the following:
*Rallypoints
*Patch Servers
*Static Reflectors
*Archiver Servers
ICE Agent is used for both Enterprise and Tactical modes.
In Enterprise mode, the ICE Server manages and provisions the ICE Agent, and the Agent may be deployed internally as a component running inside the Kubernetes cluster (ICE OS), or externally on an independent host system tethered to the managing ICE Server via an HTTPS network connection.
In Tactical mode, the ICE Agent runs independently of the ICE Server and services are configured using a simple web interface.
About ICE Agent
*ICE Agent is a critical component of Rallypoints, patch servers, static reflectors, and archiver servers.
*ICE Agents are typically deployed one per machine or VM, when installed as a native application. Docker is recommended for deployments that require multiple agents running on a single host.
*Each ICE Agent performs one function (such as patching, reflecting, or operating as a Rallypoint).
*In Enterprise mode, each ICE Agent is represented as a member server inside of a server group.
Radio and telephony gateways utilize the agent software internally but are installed and deployed exclusively via Docker. The instructions in this section do not apply to gateway; only to Rallypoints, static reflectors, archiver servers and patch servers.