Installing ICAgent (Extra-Region Hosts)

Prerequisites

Before installing ICAgent, ensure that the time and time zone of your local browser are consistent with those of the host. If they are inconsistent, errors may occur during log reporting.

Installation Methods

There are two methods to install ICAgent.

Initial Installation (Linux)

1. Log in to the LTS console and choose Host Management > Hosts in the navigation pane.
2. Set Host to Extra-Region Hosts.
3. Set OS to Linux.
4. Set Network Connectivity. For extra-region hosts to report logs to LTS in the current region, you are advised to select Private line for higher stability and reliability.
   • If you select Public network, start from 6.
   • If you select Private line, start from 5.

5. Set LTS Backend Connection. If you select Private line in the previous step, the extra-region host cannot communicate with LTS in the current region by default, and ICAgent installed on the host cannot directly access the network segment used by the Huawei Cloud management plane to report logs. Therefore, you need to configure a network connection solution to use a jump server or VPCEP to connect to the LTS.
   • If you set LTS Backend Connection to VPCEP:
     Configure a VPCEP domain name. With the assistance of Huawei Cloud network engineers, configure DNS domain name resolution rules on the cloud outside the region to resolve VPCEP domain names to specified IP addresses. Then, copy the command as prompted on the Install ICAgent page.

     ping {VPCEP domain name}

     Run this command on the host you want to collect logs from. If the ping command succeeds, the network configuration is correct. Proceed to 6.

   • If you set LTS Backend Connection to Jump server:
     1. Create a Linux ECS as a jump server.

        Log in to the ECS console and create a Linux ECS. For details, see Purchasing an ECS. If you have an ECS that meets the requirements for use as a jump server, skip this step.

        

        • The minimum specifications for the ECS are 1 vCPU and 1 GB of memory. The recommended specifications are 2 vCPUs and 4 GB of memory. You are advised to use an image of CentOS 6.5 64bit or later version.
        • If the jump server communicates with the extra-region host over the public network, an EIP must be enabled. Conversely, when using a VPC peering connection, there is no need to enable an EIP.
        • The region of the jump server must be the same as the current region of LTS.
     2. Add security group rules for the jump server and enable the corresponding inbound ports to ensure data connectivity between the extra-region hosts and the jump server.
        1. Log in to the ECS console, check the ECS list, and locate the ECS that you created as the jump server.
        2. Click its name to go to the ECS details page. Click the security group name to access the security group details page.
        3. Click the Inbound Rules tab and click Add Rule. Set the ports by referring to Table 2. Set other parameters based on your network requirements. For details, see Adding a Security Group Rule.

           Table 2 Security group rule

           Action	Protocol	Port	Description
           Allow	TCP	8149,8102,8923,30200,30201,80	Ports used by ICAgent to send data to the jump server, ensuring data connectivity between hosts in other regions and the jump server.

     3. Return to the ECS list, locate the ECS created in 5.a, and view its private IP address and EIP (available if an EIP has been enabled).
     4. Go back to the LTS console. On the Install ICAgent page, enter the obtained private IP address of the jump server to generate its SSH tunneling command.
        

        The private IP address of the jump server refers to the internal IP address of the VPC where the jump server is located.

     5. On the Install ICAgent page, click Copy Command to copy the SSH tunneling command.

        ssh -f -N -L {Private IP address of the jump server}:8149:{LTS reporting IP address}:8149 -L {Private IP address of the jump server}:8102:{LTS reporting IP address}:8102 -L {Private IP address of the jump server}:8923:{LTS reporting IP address}:8923 -L {Private IP address of the jump server}:30200:{LTS reporting IP address}:30200 -L {Private IP address of the jump server}:30201:{LTS reporting IP address}:30201 -L {Private IP address of the jump server}:80:icagent-{Region}.{OBS domain}:80 {Private IP address of the jump server}

     6. Log in to the jump server as user root and run the copied SSH tunneling command:
     7. Run the netstat -lnp | grep ssh command to check whether the corresponding TCP ports are being listened to. If the command output similar to Figure 1 is returned, the ports are open.
        Figure 1 Open TCP ports
        
        

        If the jump server powers off and restarts, run the netstat -lnp | grep ssh command again.

     8. On the Install ICAgent page, enter the DC and the connection IP address of the jump server.
        • DC: Specify a name for the data center of the host so it is easier to find the host. Enter up to 64 characters. Use only digits, letters, hyphens (-), and underscores (_).

          Connection IP: If the jump server communicates with the extra-region host via EIP connection, enter the EIP of the jump server. Conversely, when using a VPC peering connection, enter the internal IP address (private IP address) of the VPC where the jump server locates. For the EIP and private IP address, see 5.c.

6. Obtain an AK/SK. For details, see How Do I Obtain an Access Key (AK/SK)? On the Install ICAgent page, copy the ICAgent installation command and replace the AK/SK in the command with the obtained one.
7. Log in to the extra-region host as user root (by using a remote login tool such as PuTTY) and run the copied command.

   When message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. You can then view the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.

   

   If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.

Initial Installation (Windows)

1. Log in to the LTS console and choose Host Management > Hosts in the navigation pane.
2. Set Host to Extra-Region Hosts.
3. Set OS to Windows.
4. Set Network Connectivity. Extra-region hosts report logs to LTS via a public network or a private line. The latter is recommended for higher stability and reliability.
   • If you select Public network, start from 6.
   • If you select Private line, start from 5.

5. Set LTS Backend Connection. If you select Private line in the previous step, the extra-region host cannot communicate with LTS in the current region by default, and ICAgent installed on the host cannot directly access the network segment used by the Huawei Cloud management plane to report logs. Therefore, you need to configure a network connection solution to use a jump server or VPCEP to connect to the LTS.
   • If you set LTS Backend Connection to VPCEP:
     Configure a VPCEP domain name. With the assistance of Huawei Cloud network engineers, configure DNS domain name resolution rules in other regions to resolve VPCEP domain names to specified IP addresses. Then, copy the command as prompted on the Install ICAgent page.

     ping {VPCEP domain name}

     Run this command on the host you want to collect logs from. If the ping command succeeds, the network configuration is correct. Proceed to 6.

   • If you set LTS Backend Connection to Jump server:
     1. Create a Linux ECS as a jump server.

        Log in to the ECS console and create a Linux ECS. For details, see Purchasing an ECS. If you have an ECS that meets the requirements for use as a jump server, skip this step.

        

        • The minimum specifications for the ECS are 1 vCPU and 1 GB of memory. The recommended specifications are 2 vCPUs and 4 GB of memory. You are advised to use an image of CentOS 6.5 64bit or later version.
        • If the jump server communicates with the extra-region host over the public network, an EIP must be enabled. Conversely, when using a VPC peering connection, there is no need to enable an EIP.
        • The region of the jump server must be the same as the current region of LTS.
     2. Add security group rules for the jump server and enable the corresponding inbound ports to ensure data connectivity between the extra-region hosts and the jump server.
        1. Log in to the ECS console, check the ECS list, and locate the ECS that you created as the jump server.
        2. Click its name to go to the ECS details page. Click the security group name to access the security group details page.
        3. Click the Inbound Rules tab and click Add Rule. Set the ports by referring to Table 3. Set other parameters based on your network requirements. For details, see Adding a Security Group Rule.

           Table 3 Security group rule

           Action	Protocol	Port	Description
           Allow	TCP	8149,8102,8923,30200,30201,80	Ports used by ICAgent to send data to the jump server, ensuring data connectivity between hosts in other regions and the jump server.

     3. Return to the ECS list, locate the ECS created in 5.a, and view its private IP address and EIP (available if an EIP has been enabled).
     4. Go back to the LTS console. On the Install ICAgent page, enter the obtained private IP address of the jump server to generate its SSH tunneling command.
        

        The private IP address of the jump server refers to the internal IP address of the VPC where the jump server is located.

     5. On the Install ICAgent page, click Copy Command to copy the SSH tunneling command.

        ssh -f -N -L {Private IP address of the jump server}:8149:{LTS reporting IP address}:8149 -L {Private IP address of the jump server}:8102:{LTS reporting IP address}:8102 -L {Private IP address of the jump server}:8923:{LTS reporting IP address}:8923 -L {Private IP address of the jump server}:30200:{LTS reporting IP address}:30200 -L {Private IP address of the jump server}:30201:{LTS reporting IP address}:30201 -L {Private IP address of the jump server}:80:icagent-{Region}.{OBS domain}:80 {Private IP address of the jump server}

     6. Log in to the jump server as user root and run the copied SSH tunneling command:
     7. Run the netstat -lnp | grep ssh command to check whether the corresponding TCP ports are being listened to. If the command output similar to Figure 2 is returned, the ports are open.
        Figure 2 Open TCP ports
        
        

        If the jump server powers off and restarts, run the preceding command again.

6. Click the link on the Install ICAgent page to download the ICAgent installation package.
7. Save the ICAgent installation package to a directory on the Windows host, for example, C:\ICAgent, and decompress the package.
8. Obtain an AK/SK and save it. For details, see How Do I Obtain an Access Key (AK/SK)?

   If you set LTS Backend Connection to Jump Server, you also need to set Connection IP.

   Connection IP: If the jump server communicates with the extra-region host via EIP connection, enter the EIP of the jump server. Conversely, when using a VPC peering connection, enter the internal IP address (private IP address) of the VPC where the jump server locates. For the EIP and private IP address, see 5.c.

9. On the Install ICAgent page, click Copy Command to copy the ICAgent installation command, and replace the AK/SK in the command with the obtained one.
10. Log in to the Windows host, open the Command Prompt, go to the directory where the ICAgent installation package is decompressed, and run the ICAgent installation command.

    If the message Service icagent installed successfully is displayed, the installation is successful. You can then view the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.

    

    If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.

Creating Multiple Jump Servers for Load Balancing Using ELB

A single jump server may encounter a single point of failure (SPOF), potentially leading to O&M instability. To mitigate this, you can create multiple jump servers and use ELB to distribute traffic among them, enhancing access reliability.

1. Create a Linux ECS as a jump server.

   Log in to the ECS console and create a Linux ECS. For details, see Purchasing an ECS. If you have an ECS that meets the requirements for use as a jump server, skip this step.

   

   • The minimum specifications for the ECS are 1 vCPU and 1 GB of memory. The recommended specifications are 2 vCPUs and 4 GB of memory. You are advised to use an image of CentOS 6.5 64bit or later version.
   • If the jump server communicates with the extra-region host over the public network, an EIP must be enabled. Conversely, when using a VPC peering connection, there is no need to enable an EIP.
   • The region of the jump server must be the same as the current region of LTS.

2. Add security group rules for the jump server and enable the corresponding inbound ports to ensure data connectivity between the extra-region hosts and the jump server.
   1. Log in to the ECS console, check the ECS list, and locate the ECS that you created as the jump server.
   2. Click its name to go to the ECS details page. Click the security group name to access the security group details page.
   3. Click the Inbound Rules tab and click Add Rule. Set the ports by referring to Table 4. Set other parameters based on your network requirements. For details, see Adding a Security Group Rule.

      Table 4 Security group rule

      Action	Protocol	Port	Description
      Allow	TCP	8149,8102,8923,30200,30201,80	Ports used by ICAgent to send data to the jump server, ensuring data connectivity between hosts in other regions and the jump server.

3. Return to the ECS list, locate the ECS created in 1, and view its private IP address and EIP (available if an EIP has been enabled).
4. Log in to the LTS console. In the navigation pane, choose Host Management > Hosts. Click Install ICAgent. On the displayed page, enter the private IP address of the jump server to generate the SSH tunneling command.
   

   The private IP address of the jump server refers to the internal IP address of the VPC where the jump server is located.

5. On the Install ICAgent page, click Copy Command to copy the SSH tunneling command.

   ssh -f -N -L {Private IP address of the jump server}:8149:{LTS reporting IP address}:8149 -L {Private IP address of the jump server}:8102:{LTS reporting IP address}:8102 -L {Private IP address of the jump server}:8923:{LTS reporting IP address}:8923 -L {Private IP address of the jump server}:30200:{LTS reporting IP address}:30200 -L {Private IP address of the jump server}:30201:{LTS reporting IP address}:30201 -L {Private IP address of the jump server}:80:icagent-{Region}.{OBS domain}:80 {Private IP address of the jump server}

6. Log in to the jump server as user root and run the copied SSH tunneling command.

7. Repeat the preceding steps to create multiple jump servers. Add them to the same VPC by selecting the same VPC for Network during their creation.
8. Log in to the ELB console and create a load balancer. For details, see Creating a Dedicated Load Balancer. When creating the load balancer, you should:
   1. Select the same VPC as that of the jump servers during network configuration.
   2. Create an EIP for connecting to the jump servers.
   3. Apply for the bandwidth based on the service requirements.

9. Add listeners for TCP ports 30200, 30201, 8149, 8923, 8102, and 80. For details, see Adding a TCP Listener.
10. Create a backend server group and add all jump servers in the group. For details, see Adding Backend Servers.
11. Return to the LTS console. On the Install ICAgent page, enter the EIP of the load balancer in Connection IP , copy the installation command, and run it on the extra-region host.

Inherited Installation (Linux)

Assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. To install ICAgent on other hosts one by one:

1. Run the following command on the host where ICAgent has been installed, where x.x.x.x is the IP address of the host you want to install ICAgent on.

   bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -ip x.x.x.x

2. Enter the password for user root of the host when prompted.
   

   • If the Expect tool is installed on the host that has ICAgent installed, the ICAgent installation should be able to complete without prompting you for a password. Otherwise, enter the password as prompted.
   • Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to remotely communicate with the remote host to install ICAgent.
   • If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.
3. When message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. Check the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.

Batch Inherited Installation (Linux)

Assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. In this case, you can follow the directions below to install ICAgent on other hosts in batches.

• The hosts must all belong to the same VPC and be on the same subnet.
• Python 3.* is required for batch installation. If you are prompted that Python cannot be found during ICAgent installation, install Python of a proper version on the host and try again.