Cloud Services Appliance 4.3 - How To Add a Persistent Static Route

Version 11

    Verified Product Versions

    LANDESK Management Suite 2016.xLANDESK Endpoint Manager 2017.x

    Environment

     

    LANDesk Cloud Services Appliance 4.3

     

    Problem/Issue/Symptoms

     

    The Cloud Services Appliance is unable to talk with the Core
    The Cloud Services Appliance is unable to talk with the Internet

    The Cloud Services Appliance is correctly configured on the Core but is unable to activate online
    The Cloud Services Appliance has two network interfaces configured both with a gateway - only one is working

     

    Solution 1

     

    route add COREIP ethX

     

    ethX is the internal NIC. By default this is eth1, however on the VCSA it may be different. The highest numbered nic typically

     

    Example:

    route add 10.14.115.10 via eth1

     

    Solution 2

     

    Having two gateways configured on a single device simply doesn't work, as the device will just use one of the two,

    If the Cloud Services Appliance has two network interfaces configured, make sure the only one interface, the one talking to the internet, has a default gateway configured.


    Then, if the Core Server is on a different network segment than the Cloud Services Appliance, and the next hop to reach the Core server is different than the default gateway, you need to set up a static route to address the traffic to the core via the correct router/firewall.

     

    Static route configuration is stored in a /etc/sysconfig/network-scripts/route-interface file.
    For example, static routes for the eth0 interface would be stored in the /etc/sysconfig/network-scripts/route-eth0 file.

     

    Example

     

    Cloud Service Appliance with two network interfaces configured

     

    Interface eth2 connected towards the internet
    IP address 192.168.1.3 subnet mask 255.255.255.0 default gateway 192.168.1.1

     

    Interface eth3 connected towards the LAN and the Core Server
    IP adress 10.1.1.3 subnet mask 255.255.255.0 no default gateway, next hop to reach the Core 10.1.1.1

     

    Core Server with IP address 10.20.20.1 subnet mask 255.255.255.0

     

     

    csa_network_configuration.png

     

     

    What we need to do is configuring a static route to instruct the appliance to reach the network segment 10.20.20.0/24 via our next hop with IP address 10.1.1.1, for the interface eth3.

     

    WARNING: Because we are operating on the network configuration of the appliance, it's safe to operate directly on the device's console, or at least having the possiblity to physically reach the device with a local keyboard and monitor in case of the network connectivity problems and especially if the appliance is off site.

     

    1) Open the local console command line interface, press CTRL+ALT+F2 or open a SSH session to the appliance with an SSH client and elevate the command line with 'sudo su' and the admin password

    2) Create or update the file /etc/sysconfig/network-scripts/route-eth3 with the following line 10.20.20.0/24 via 10.1.1.1

    3) Reload your network configuration with the command service network reload

    4) Verify the new static route with the command route

    5) Verify you can correctly communicate wirth the appliance from the Core Server

     

     

    static_route.png