Cannot communicate with Linux (Redhat, Ubuntu, CentOS, Solaris, etc.)
- Please check the Compatibility and Interoperability Matrix and verify that the Operating System you are trying to protect is listed.
- The Unitrends Client Agent is installed at /usr/bp/. If missing packages (dependencies) are encountered, it must be resolved. In some cases, you may need to resolve 32-bit and 64-bit dependencies.
- A common mistake is to install the wrong package. For example, while Novel OES resides on SUSE based, the installer is NOT the same. There is a dedicated installer for Novel OES which includes the TSA security module, that is not included in the SUSE package. The Novel OES installed (oes_cnt) is all that is needed (as long as you have your dependencies).
- During the installation process, the option that a Firewall exists should have been chosen which sets the port to 1745 for data transfer. If this did not occur (or if a communication/permissions issue prevented it), the change may not have been implemented. Please check the /usr/bp/bpinit/master.ini file and ensure the data= port has been set to 1745. Save that file and restart the Unitrends agent (usually bpinetd <new *nix systems> but could be xinetd <older>). If you do not see it, you can issue this command from your SSH connection to create the entry for you:
/usr/bp/bin/bputil -p “Configuration Options” data 1745 /usr/bp/bpinit/master.ini
- At the minimum, TCP ports 1743 (Unitrends to Client Agent comms) and port 1745 (data transfer) must be allowed bidirectional. The port range is from 1744-1749. However, if you can allow communications between the Linux server and the Unitrends system, you can eliminate firewall issues right away.
- Once you have configured everything as needed, consider rebooting the Linux systems. Sometimes, an underlying Linux process is holding the completion of the install/setup. This is rare, but can occur.
A missed step in the configuration process or permissions issue prevented changes from being implemented.