Overview

To troubleshoot the network, flexiManage provides information and notification on various components of the system:

  • Ability to view the status of each inventory such devices, tunnels, configuration, interfaces, static routes, etc
  • Get notifications for network misbehavior
  • Ability to view the jobs sent to the device - including the request and response for each job
  • Ability to view the flexiEdge device logs
  • Ability to view the flexiEdge device configuration

In cases a device doesn’t register or doesn’t connect, there are troubleshooting tools from the flexiEdge device terminal:

  • Check the flexiEdge device logs
  • Check the flexiEdge device configuration
  • Debug routing protocols
  • Packet traces

Refer to other troubleshooting pages for more details.

Common Issues:

Device registration failure

  • Symptom: Device not shown in the inventory devices

  • Verify:

    • The account has reached the 3 free device limit and a valid payment method wasn’t added to the account
    • The correct token is installed in /etc/flexiwan/agent/token.txt
    • No firewall that inspect the https and websocket certificates
    • Run fwsystem_checker and make sure the hardware and software configuration are fine
    • Check the log using “tail -100 /var/log/flexiwan/agent.log” verify if any error reported
    • Try to start or reset the flexiEdge device:
    • To start: “fwagent start”
    • To reset: “fwagent reset”
    • Try to restart the flexiwan-router service: “sudo systemctl restart flexiwan-router”

No interfaces for device

  • Symptom: The flexiManage Device -> Interfaces tab does not show any interfaces

  • Verify:

    • Check the existence of PCI interfaces using the command: “lspci -vnn”. If no PCI interfaces are available, it requires to modify the network adaptor to be PCI based
    • Check if the interfaces assigned to DPDK using the command: “dpdk-devbind -s”. If interfaces are bound to DPDK, run “fwagent stop” followed by “fwagent start”

Device not connect

  • Symptom: flexiEdge device is registered but is not getting to connected state

  • Verify:

    • Device approved in flexiManage
    • Run fwsystem_checker and make sure that the hardware and software configurations are correct
    • Check the log using “tail -100 /var/log/flexiwan/agent.log” verify if any error reported

Update device failed

  • Symptom: modify device or interface configuration failed

  • Verify:

    • Check the Troubleshoot -> Jobs for failures

Device fails to start

  • Symptom: start device failed

  • Verify:

    • Run fwsystem_checker and make sure the hardware and software configurations are correct
    • Check the Troubleshoot -> Jobs for failures
    • Check the logs by getting the device logs using the logs tab, verify if any error reported
    • Check the device configuration using the device configuration tab, check if any wrong configuration exists. To reset the configuration on the device run: “fwagent reset -s”

Tunnel errors

  • Symptom: Tunnel creation failed

  • Verify:

    • Check Troubleshoot -> Jobs for failures
    • Check if “Public IP” is required in the device configuration. Public IP is required when connecting via the public
    • Verify that the WAN interface has no routing enabled
    • Verify that the LAN interface has “OSPF” enabled
    • Verify that there is no overlap of LAN subnets
    • Check the device connectivity
    • Check the logs by getting the device logs using the logs tab, verify if any error reported
    • Check the device configuration using the device configuration tab, check if any wrong configuration exists. To reset the configuration on the device run: “fwagent reset -s”
    • Try to delete and add the tunnel