XCOM for Linux 12.0 Docker new RHEL 9.x installation or migration

Products

XCOM Data Transport XCOM Data Transport - Linux PC

Issue/Introduction

This article provides further information on the steps required for a new XCOM for Linux 12.0 Docker installation under RHEL 9.x or the migration of an existing Docker installation from another Host OS to RHEL 9.x.
It refers to what is already documented in the current XCOM for Linux Install Using Docker documentation and also adds some more details.

Environment

XCOM™ Data Transport® for UNIX/Linux PC
XCOM for Linux 12.0 Docker Installation

Resolution

NOTE: A standard XCOM for Linux installation on RHEL 9.x requires PTF LU11905 to provide the systemd txpi services because xinetd is not available.
For a Docker installation the container comes with xinetd included so that PTF is not required.

Following XCOM 12.0 doc. page: Install Using Docker

1. Per page Installation Prerequisites install Docker and Docker Compose plugin using these steps: Install Docker Engine on RHEL
NOTE: If the directory containing executable docker-compose (/usr/libexec/docker/cli-plugins) is not in the PATH after the install then it will need to be added otherwise the XCOM Docker install will fail.

2. Per page Install XCOM Docker use the Broadcom Docker Repository option to install XCOM Docker and after the installation verify with command:
# docker images | grep -i xcom
xcom.packages.broadcom.com/caxcom/x86_64/caxcom 12.0.00-22042 144d6aa768ca 3 years ago 845MB

3. Start the container using "XCOMAdmin.sh start"
# cd /opt/CA/XCOMDocker
# ./XCOMAdmin.sh start
[2025-05-12 06:35:43] [INFO] main/280: Using the log file /opt/CA/XCOMDocker/logs/xcomadmin.log
[2025-05-12 06:35:43] [INFO] main/350: Using dockerimagetag.env file from /opt/CA/XCOMDocker/config directory
WARN[0000] /opt/CA/XCOMDocker/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 2/2
✔ Network xcomdocker_caxcom_network Created 0.1s
✔ Container xcomdocker-caxcom-1 S... 0.5s
WARN[0000] /opt/CA/XCOMDocker/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[2025-05-12 06:35:44] [INFO] DoStartup/252: Container ID: a9cf07d6a1136358abf7e249303ab6eba5ec9ebbd24f1b1769bdc9053f61fb65

4. After starting the container xcomd and xinetd should be automatically started as per doc page Configure XCOM Docker Containers.
To verify start a bash shell in the container and run the relevant commands.
# docker exec -it xcomdocker-caxcom-1 bash
[root@deb552536d35 XCOM]#

Run the ps command e.g.
[root@deb552536d35 XCOM]# ps -efw UID PID PPID C STIME TTY TIME CMD root 1 0 0 04:51 ? 00:00:00 /bin/bash bin/start.sh root 95 0 0 04:52 pts/0 00:00:00 bash root 189 1 0 04:56 ? 00:00:00 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid root 195 1 0 04:56 ? 00:00:00 /opt/CA/XCOM/sbin/xcomd -d9 root 618 95 0 05:09 pts/0 00:00:00 ps -efwRun the netstat command e.g.
[root@deb552536d35 XCOM]# netstat -nap | grep 804 tcp 0 0 0.0.0.0:8045 0.0.0.0:* LISTEN 189/xinetd tcp 0 0 0.0.0.0:8044 0.0.0.0:* LISTEN 189/xinetd tcp6 0 0 :::8047 :::* LISTEN 189/xinetd tcp6 0 0 :::8046 :::* LISTEN 189/xinetd

NOTE: On RHEL 9.x It has been observed that after the container is started there may be a delay of several minutes in the start of the xcomd and xinetd processes or if the xinetd process is immediately visible there is a delay in the 804* LISTEN ports being listed when using the netstat command.
XCOM Engineering are investigating this behaviour and this article will be updated will the result of that research.

Migrating/moving existing XCOM Docker container from another Host OS to RHEL 9.x

1. On the existing Host OS.
a. Stop the existing container and save the XCOM Docker image as a tar file e.g.
docker save xcom.packages.broadcom.com/caxcom/x86_64/caxcom > xcom_docker_image.tar
b. Backup the existing /opt/CA/XCOMDocker configuration directory:# cd /opt/CA# tar cvf XCOMDocker.tar XCOMDocker2. Binary copy both tar files to RHEL 9.x.
a. Load the XCOM Docker image:
docker load < xcom_docker_image.tarb. Copy the /opt/CA/XCOMDocker directory tar file to /opt/CA and untar it:
# cd /opt/CA# tar xvf XCOMDocker.tar

3. Verify the installtion:
# docker images | grep -i xcom
xcom.packages.broadcom.com/caxcom/x86_64/caxcom 12.0.00-22042 144d6aa768ca 3 years ago 845MB

4. As per the new installation start the container using "XCOMAdmin.sh start"
# cd /opt/CA/XCOMDocker
# ./XCOMAdmin.sh start
NOTE: If there is any network related error, the command "docker network prune" maybe need to resolve it (erases old network configuration and downloads it again).

Additional Information

If there are any issues with xinetd it can be stopped and started with debug i.e. "/usr/sbin/xinetd -d" to show additional output.