--- title: "Enable latency monitor" slug: "enable-latency-monitor-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:27:25Z published: 2026-11-19T12:27:25Z canonical: "docs.trellix.com/enable-latency-monitor-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Enable latency monitor You can use the following CLI commands to enable, set sensitivity level, and check the status of latency monitor feature. ### latency-monitor enable action This command enables latency monitoring in Sensor and also specifies the action to be performed if high latency is observed in the Sensor. The following are the actions that can be specified in this command: - alert-only — Generates an alert when a high latency is observed in the Sensor - put-in-layer2 — Generates an alert and also forwards the traffic to layer 2. Alerts that are generated can be seen in the **System faults** page in the Manager. **Syntax:** `latency-monitor enable action <alert-only | put-in-layer2>` This command should be executed with a parameter value, else the command is treated as invalid. > [!NOTE] > Note > > If layer2-forward is enabled, it is necessary to set the layer 2 mode as on. Otherwise, the layer2-forward action does not get executed. **Example:** `latency-monitor enable action alert-only` ### latency-monitor sensitivity-level This command configures the sensitivity level for latency management. **Syntax:** `latency-monitor sensitivity-level high` `latency-monitor sensitivity-level medium` `latency-monitor sensitivity-level low` ### latency-monitor restore-inline When a high latency is observed on the Sensor and the latency monitor is configured, the Sensor remains in layer 2 until a `layer2 mode deassert` is invoked or the Sensor reboots. This command allows the Sensor to come out of layer 2 mode without layer 2 deassert. The Sensor restores to inline from layer 2 if the following conditions are met: - The latency monitor has put the Sensor in layer 2 mode. - The Sensor is in good health. If the Sensor is in bad health, a deassert cannot be performed and the Sensor reboots. - A substantial amount of time has lapsed, as configured using this command, when the Sensor went into layer 2 due to latency. The default time to trigger an automatic layer 2 deassert is 10 minutes. If the latency continues to exist after the Sensor is restored to inline mode, the Sensor behaves according to the current setting of the latency monitor. **Syntax:** `latency-monitor restore-inline enable <10-60>` `latency-monitor restore-inline disable` | Parameter | Description | | --- | --- | | <10-60> | The time in minutes to trigger the restore inline from layer 2. It is counted since the time the Sensor moved into layer 2 state due to high latency. | The `latency-monitor status` command displays the status of the latency monitor feature, and the status of the restore-inline feature of the latency monitor. ### latency-monitor This command disables the latency monitoring feature or displays the status of latency monitoring feature. **Syntax:** `latency-monitor <disable | status>` **Default Value:** Latency monitoring feature is disabled by default. If disabled, latency monitoring feature does not generate any alert nor forward the traffic to layer 2 when high latency is observed. If latency monitoring is enabled, the following information is displayed. - latency monitoring status (enable or disable) - configured action (alert-only or layer2-forward)