What should I do if the status of TFTP and SCP servers is Not Running?

Steps to follow if the TFTP and SCP servers in the Site24x7 On-Premise Poller are not running

If you have chosen the TFTP and SCP protocols for network configuration management, the status of the TFTP and SCP servers should be Running for configuration backups to happen properly. If the status is Not Running , follow the steps below.

Windows

  1. From your Windows machine, open Resource Monitor as an administrator.
  2. Click the Network tab.
  3. In the Port column under the Listening Ports section, check ports 22 and 69 for the SCP and TFTP servers, respectively.
  4. Make a note of the PID for each port.
    Port 22
    Port 69
  5. To stop a running process in Windows:
    1. Run  Task Manager as an administrator.
    2. Click the Details tab.
    3. Search for the process with the PID that you noted above.

    4. Right-click the process and select Properties .

    5. Check the process location and verify if it is important. 

    6. If not, right-click the process and select End process tree .
  6. Restart the On-Premise Poller for the changes to take effect. 

Linux

The SCP server is not running

The default SSH service used for remote login to the server on which the On-Premise Poller is installed runs on port 22. A conflict arises when another process uses the same port. Due to this, the SCP server status is shown as Not Running .
To resolve this issue, you must replace the SSH port number used for remote server login. Changing the port may impact your remote login to the server. So, we recommend using the SSH/TELNET or SSH - TFTP/TELNET - TFTP protocol before changing the SSH service port. As another option, you can try using the On-Premise Poller on a Windows server.
Nevertheless, if you must use the SCP protocol, follow the steps given below.
  1. Select an unused port between 1024 and 65535. In this example, we will select port 2222. To verify if it is available, execute the following command on the terminal: 
    sudo netstat -tulpn | grep ':2222'
    If the port is available, it will not be listed when the command is executed. Otherwise, select a different port within the specified range. 
  2. Next, we will change the default port 22 to 2222. For this, you must open the port in the firewall also.
    Notes Updating the SSH service port without opening the new port in the firewall might result in losing the remote connection to the server. Execute the appropriate command according to the Linux flavor and firewall type
    1. For Uncomplicated Firewall (UFW) in Ubuntu-based systems:
      1. To open the port, execute the following command:
        sudo ufw allow [port-number]
        For example: sudo ufw allow 2222
      2. After adding the port to the firewall, restart the UFW service to apply the changes by executing the following command:
        sudo systemctl restart ufw
    1. For firewalld in CentOS- and RHEL-based systems:
      1. To open the port, execute the following command:
        sudo firewall-cmd --zone=public --add-port=[port-number]/[protocol] --permanent
        For example: sudo firewall-cmd --zone=public --add-port=2222/tcp --permanent
      2. Restart the firewalld service with the following command:
        sudo systemctl restart firewalld
  3. If you are using a SELinux-based system, execute the following command in addition to the previous commands:
    semanage port -a -t ssh_port_t -p tcp [port_number]
    For example: semanage port -a -t ssh_port_t -p tcp 2222
  4. Next, open the /etc/ssh/sshd_config file.
  5. Search for the #Port 22 line and add the line Port 2222 below it.
  6. Save the file.
  7. Then, reload the SSH service by executing the following command:
    sudo systemctl restart sshd
  8. Before closing this session, try connecting to the remote host with the newly configured port using the following command:
    ssh {user}@{server_ip} -p 2222
    If you still face any issues, delete the line added in step 5 and reload the SSH service as stated in step 7. After this, contact your sysadmin with the details to change the SSH service port. 
  9. Restart the On-Premise Poller for the changes to take effect. 

The TFTP server is not running

This issue occurs when port 69 is already occupied by another process. You must end any unnecessary process using this port to resolve this issue. 
  1. Execute the following command to list all the programs on port 69 and fetch the process ID:
    sudo netstat -tulpn | grep ':69'
    Here, the process ID is 5908.
  2. To know more about this process, execute the following command:
    ps aux | grep '5908'
  3. If the process is not required and is not related to the On-Premise Poller, verify it with your sysadmin, then end it by using the following command:
    kill -9 '5908'
  4. Restart the On-Premise Poller for the changes to take effect. 
  1. Enabling Network Configuration Manager