Method 2 - McAfee Agent 5.6.0 and later
This method is intended for situations where the clients
can't discover the Relay Server. For example, situations where the Relay Server was in a different subnet that the UDP discovery broadcasts could not reach.
In this scenario, the details of the Relay Server are given to the client when the agent is installed. The details are specified in a command-line switch as follows:
FramePkg.exe /Install=agent /Relay="<relay server ip>:<port>"
install.sh -i -R <relay server ip>:<port>
Where:
- The <relay server ip> is the IP address of the Relay Server.
- The <port> is the TCP port to use for relaying.
Example: If your Relay Server's IP address was 192.168.1.100, and the TCP port for relaying was 8081, the command lines would be:
Windows:
FramePkg.exe /Install=agent /Relay="192.168.1.100:8081"
Non-Windows:
install.sh -i -R 192.168.1.100:8081
NOTE: You can specify multiple Relay Servers can be specified by providing their IP and port details separated by a semicolon.
Example:
FramePkg.exe /Install=agent /Relay="192.168.1.100:8081;192.168.1.150:8081;192.168.1.200:8081"
IMPORTANT:
- You can specify a maximum of 5 Relay Servers.
- Make sure that you specify the TCP relay port, not the broadcast port.
- Non-Windows command-line switches are case sensitive: Make sure that you specify -R.
NOTE: When the Relay Server has multiple Network Interface Cards (NICs), with different IP range, the following is observed:
Example:
- NIC1: 10.10.10.2 - Does not connect to ePO
- NIC2: 20.20.20.2 - Does connect to ePO
If MA is reinstalled on the client with the
Relay= switch, with the
NIC1 IP Relay Server address, the following is observed:
- The communication from the client to the Relay Server is successful,
- But, communication from the Relay Server to the ePO Server via NIC1 fails.
Example client installation command:
FramePkg.exe /Install=agent /Relay=10.10.10.2:8081