FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
wmichael
Staff
Staff
Article Id 352712
Description This article describes how to configure a Link-Monitor with TWAMP protocol.
Scope FortiGate.
Solution

The Two-Way Active Measurement Protocol (TWAMP) is a protocol that is used for measuring network performance between devices.

 

The FortiGate link-monitor can be configured to use TWAMP.

 

  1. To configure a remote FortiGate to act as a TWAMP server.

 

config system probe-response

    set port <port>

    set mode twamp

    set security-mode authentication

    set password <password>

end

 

The probe response must be set to listen on the incoming interface:

 

config system interface

    edit "port5"

        set ip 10.103.0.2 255.255.255.0

        set allowaccess probe-response

    next

end

 

Note: ‘set allowaccess probe-response’ will only allow the probe-response and will overwrite other access configured on the interface.  If other access is required, such as ‘https’ or ‘ping’, this will have to be configured as well.  If ‘allowaccess’ is already configured for other types of access. then the ‘append’ command can be used to add the 'probe-response’

 

Example:

 

config system interface

    edit "port5"

        append allowaccess probe-response

    next

end

 

  1. Configure the link-monitor on the local FortiGate.  The port here must match the port used in step 1.

config system link-monitor

    edit "LM_TWAMP"

        set srcintf "port5"

        set server "10.103.0.2"

        set protocol twamp

        set port <port>

        set security-mode authentication

        set password <password>

    next

end

 

  1. Once the link monitor is configured, verify it is working with the ‘diagnose sys link-monitor status’ command.

diagnose sys link-monitor status

 

Link Monitor: LM_TWAMP, Status: alive, Server num(1), HA state: local(alive), shared(alive)

Flags=0x1 init, Create time: Fri Oct 25 17:23:08 2024

Source interface: port5 (7)

VRF: 0

Interval: 500 ms

Service-detect: disable

Diffservcode: 000000

Class-ID: 0

  Peer: 10.103.0.2(10.103.0.2)

        Source IP(10.103.0.1)

        Route: 10.103.0.1->10.103.0.2/32, gwy(10.103.0.1)

        protocol: twamp(9200), state: alive

                Latency(Min/Max/Avg): 0.323/0.845/0.495 ms

                Jitter(Min/Max/Avg): 0.001/0.400/0.093 ms

                Packet lost: 0.000%

                MOS: 4.404

                Number of out-of-sequence packets: 0

                Fail Times(0/5)

                Packet sent: 759, received: 758, Sequence(sent/rcvd/exp): 759/759/760

        Directional Stats:

          IN:

                Latency(Min/Max/Avg): 0.323/0.845/0.495 ms

                Jitter(Min/Max/Avg): 0.001/0.400/0.093 ms

                Packet lost: 0.000%

                MOS: 4.404

                Number of out-of-sequence packets: 0

                Peer packet sequence(current/exp): 759/760

          OUT:

                Latency(Min/Max/Avg): 0.000/0.000/0.000 ms

                Jitter(Min/Max/Avg): 0.000/0.000/0.000 ms

                Packet lost: 0.000%

                MOS: 4.404

                Number of out-of-sequence packets: 0

 

Related articles:

Technical Tip: Link monitor

Technical Tip: Configuring Performance SLA with TWAMP probes

Contributors