跳至主要內容

Link Monitor 服务器权重

2026/6/25Link Monitor7.X.X大约 3 分钟

Link Monitor 服务器权重

FortiOS 7.0.1 之前，Link Monitor 在所有探测服务器都不可达时才判定为失败。FortiOS 7.0.1 起，Link Monitor 支持为每个探测服务器配置独立权重，并通过 fail-weight 设置整体失败阈值。当不可达服务器的权重总和达到或超过失败阈值时，Link Monitor 才判定为失败，并触发静态路由更新或级联接口更新。

config system link-monitor
    edit <name>
        set srcintf <interface>
        set server-config {default | individual}
        set fail-weight <integer>
        config server-list
            edit <id>
                set dst <address>
                set weight <integer>
            next
        end
    next
end
参数说明
server-config default使用传统服务器配置方式，不为单个服务器设置独立权重。
server-config individual使用 server-list 配置多个探测服务器，并为每个服务器设置权重。
fail-weightLink Monitor 判定为失败所需的故障权重阈值。
server-list探测服务器列表。每个服务器通过 dst 指定目标地址，通过 weight 指定故障权重。

配置示例

以下拓扑中，FortiGate 通过路由器访问两个探测服务器：服务器 1 为 10.10.100.22，服务器 2 为 10.10.100.55。

Link Monitor 多服务器权重拓扑

故障权重未达到阈值

此示例中，服务器 2 不可达，但服务器 2 的权重为 30，小于 fail-weight 40，因此 Link Monitor 仍保持 alive。

  1. 配置 Link Monitor 服务器权重。

    config system link-monitor
    edit "test-1"
        set srcintf "port22"
        set server-config individual
        set gateway-ip 10.10.202.1
        set failtime 3
        set fail-weight 40
        config server-list
            edit 1
                set dst "10.10.100.22"
                set weight 60
            next
            edit 2
                set dst "10.10.100.55"
                set weight 30
            next
        end
    next
end

  2. 让服务器 2 探测失败后，查看 Link Monitor 状态。

    # diagnose sys link-monitor status test-1
Link Monitor: test-1, Status: alive, Server num(2), HA state: local(alive), shared(alive)
Flags=0x1 init, Create time: Fri Jun  4 17:23:29 2021
Source interface: port22 (14)
Gateway: 10.10.202.1
Interval: 500 ms
Service-detect: disable
Diffservcode: 000000
Class-ID: 0
Fail-weight (40): not activated
  Peer: 10.10.100.22(10.10.100.22)
        Source IP(10.10.202.2)
        Route: 10.10.202.2->10.10.100.22/32, gwy(10.10.202.1)
        protocol: ping, state: alive
                Latency(Min/Max/Avg): 0.417/0.585/0.530 ms
                Jitter(Min/Max/Avg): 0.007/0.159/0.057
                Packet lost: 0.000%
                Number of out-of-sequence packets: 0
                Fail Times(0/3)
                Packet sent: 239, received: 236, Sequence(sent/rcvd/exp): 240/240/241
  Peer: 10.10.100.55(10.10.100.55)
        Source IP(10.10.202.2)
        Route: 10.10.202.2->10.10.100.55/32, gwy(10.10.202.1)
        Fail weight 30 applied
        protocol: ping, state: dead
                Packet lost: 100.000%
                Number of out-of-sequence packets: 0
                Recovery times(0/5) Fail Times(1/3)
                Packet sent: 239, received: 3, Sequence(sent/rcvd/exp): 240/4/5

故障权重达到阈值

此示例中，服务器 2 不可达，服务器 2 的权重为 50，已经达到 fail-weight 40，因此 Link Monitor 判定为 dead。

  1. 调整服务器权重。

    config system link-monitor
    edit "test-1"
        set srcintf "port22"
        set server-config individual
        set gateway-ip 10.10.202.1
        set failtime 3
        set fail-weight 40
        config server-list
            edit 1
                set dst "10.10.100.22"
                set weight 30
            next
            edit 2
                set dst "10.10.100.55"
                set weight 50
            next
        end
    next
end

  2. 让服务器 2 探测失败后，查看 Link Monitor 状态。

    # diagnose sys link-monitor status test-1
Link Monitor: test-1, Status: dead, Server num(2), HA state: local(dead), shared(dead)
Flags=0x9 init log_downgateway, Create time: Fri Jun  4 17:23:29 2021
Source interface: port22 (14)
Gateway: 10.10.202.1
Interval: 500 ms
Service-detect: disable
Diffservcode: 000000
Class-ID: 0
Fail-weight (40): activated
  Peer: 10.10.100.22(10.10.100.22)
        Source IP(10.10.202.2)
        Route: 10.10.202.2->10.10.100.22/32, gwy(10.10.202.1)
        protocol: ping, state: alive
                Latency(Min/Max/Avg): 0.393/0.610/0.520 ms
                Jitter(Min/Max/Avg): 0.009/0.200/0.095
                Packet lost: 0.000%
                Number of out-of-sequence packets: 0
                Fail Times(0/3)
                Packet sent: 680, received: 677, Sequence(sent/rcvd/exp): 681/681/682
  Peer: 10.10.100.55(10.10.100.55)
        Source IP(10.10.202.2)
        Route: 10.10.202.2->10.10.100.55/32, gwy(10.10.202.1)
        Fail weight 50 applied
        protocol: ping, state: dead
                Packet lost: 100.000%
                Number of out-of-sequence packets: 0
                Recovery times(0/5) Fail Times(1/3)
                Packet sent: 680, received: 3, Sequence(sent/rcvd/exp): 681/4/5
最近更新: