--- title: "Conditions requiring a Sensor reboot" slug: "conditions-requiring-a-sensor-reboot-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:31:15Z published: 2026-11-19T12:31:15Z canonical: "docs.trellix.com/conditions-requiring-a-sensor-reboot-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. # Conditions requiring a Sensor reboot The following situations either cause or require a Sensor reboot. You have two options for rebooting the Sensor. You can reboot the Sensor from the Manager interface, or you can issue the `reboot` CLI command. > [!NOTE] > Note > > A Sensor reboot can take up to five minutes. - Issuing the following CLI commands causes an automatic reboot of the Sensor: - `resetconfig` - `deletesignatures` - `factorydefaults` For more information on the Sensor CLI commands, see the *CLI commands* section. - Changing the Sensor's management port IP address (IPv4 or IPv6) requires a manual reboot of the Sensor, before the change takes into effect. - Certain internal software errors can cause the Sensor to reboot itself. See a description of Sensor fault messages later in this chapter. - Enabling/disabling SSL requires a Sensor reboot. - Enabling/disabling parsing and detection of attacks in IPv6 traffic passing through the Sensor monitoring port requires a manual reboot of the Sensor. In the Manager user interface, you can enable/disable parsing and detection of attacks in IPv6 traffic with the **Scan IPv6 traffic for attacks** option from the **IP Settings** tab (**Devices** → **** → **Setup** → **Advanced** → **IP Settings**). For more information, see the topic *Configuring IP Settings for IPv4 and IPv6 traffic* in the *IPS Administration* section. - Upgrading Sensor software requires a manual reboot of the Sensor.