You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md
+42-4Lines changed: 42 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Manage individual sensors
3
3
description: Learn how to manage individual sensors, including managing activation files, certificates, performing backups, and updating a standalone sensor.
4
-
ms.date: 11/09/2021
4
+
ms.date: 03/10/2022
5
5
ms.topic: how-to
6
6
---
7
7
@@ -288,7 +288,31 @@ The console will display restore failures.
288
288
289
289
## Update a standalone sensor version
290
290
291
-
The following procedure describes how to update a standalone sensor by using the sensor console.
291
+
This procedure describes how to update a standalone sensor version. If you are upgrading from a version higher than 22.1.x, you can jump straight to [Update your sensor software version](#update-your-sensor-software-version).
292
+
293
+
However, if you're upgrading from a version earlier than 22.1.x, make sure to [Download a new activation file for version 22.1.x or higher](#download-a-new-activation-file-for-version-221x-or-higher) before you upgrade, and then [reactivate your sensor](#reactivate-your-sensor-for-version-221x-or-higher) after upgrading.
294
+
295
+
Updates from legacy versions may require a series of upgrades. For example, if you still have a sensor version 3.1.1 installed, you'll need to first upgrade to version 10.5.5, and then to a 22.x version.
296
+
297
+
### Download a new activation file for version 22.1.x or higher
298
+
299
+
Version [22.1.x ](release-notes.md#update-to-version-221x) is a large upgrade with more complicated background processes. You should expect this upgrade to take more time than earlier upgrades have required.
300
+
301
+
1. Update your firewall rules between the sensor and the Azure portal. For more information, see [Sensor access to Azure portal](how-to-set-up-your-network.md#sensor-access-to-azure-portal).
302
+
303
+
1. In Defender for IoT, select **Sites and sensors** on the left.
304
+
305
+
1. Select the site where you want to update your sensor, and then navigate to the sensor you want to update.
306
+
307
+
1. Expand the row for your sensor, select the options **...** menu on the right of the row, and then select **Prepare to update to 22.x**.
308
+
309
+
:::image type="content" source="media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png" alt-text="Screenshot of the Prepare to update option." lightbox="media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png":::
310
+
311
+
1. In the **Prepare to update sensor to version 22.X** message, select **Let's go**.
312
+
313
+
1. When the new activation file is ready, download it and verify that the sensor status has switched to **Pending activation**.
314
+
315
+
### Update your sensor software version
292
316
293
317
1. In the Azure portal, go to **Defender for IoT** > **Getting started** > **Updates**.
294
318
@@ -308,10 +332,24 @@ The following procedure describes how to update a standalone sensor by using the
308
332
309
333
:::image type="content" source="media/how-to-manage-individual-sensors/defender-for-iot-version.png" alt-text="Screenshot of the upgrade version that appears after you sign in.":::
310
334
311
-
If you're upgrading from version 10.5.x to version 22.x, make sure to reactivate your sensor. For more information, see [Reactivate a sensor for upgrades to version 22.x from a legacy version](how-to-manage-sensors-on-the-cloud.md#reactivate-a-sensor-for-upgrades-to-version-22x-from-a-legacy-version).
335
+
### Reactivate your sensor for version 22.1.x or higher
336
+
337
+
If you're upgrading from a legacy version to version 22.1.x or higher, make sure to reactivate your sensor using the activation file you downloaded earlier.
338
+
339
+
1. On your sensor, select **System settings > Sensor management > Subscription & Mode Activation**.
312
340
313
-
After upgrading to version 22.1.x, the new upgrade log can be found at the following path, accessed via SSH and the *cyberx_host* user: `/opt/sensor/logs/legacy-upgrade.log`.
341
+
1. In the **Subscription & Mode Activation** pane that appears on the right, select **Select file**, and then browse to and select your new activation file.
314
342
343
+
1. In Defender for IoT on the Azure portal, monitor your sensor's activation status. When the sensor is fully activated:
344
+
345
+
- The sensor's **Overview** page shows an activation status of **Valid**.
346
+
- In the Azure portal, on the **Sites and sensors** page, the sensor is listed as **OT cloud connected** and with the updated sensor version.
347
+
348
+
Your legacy sensors will continue to appear in the **Sites and sensors** page until you delete them. For more information, see [Manage on-boarded sensors](how-to-manage-sensors-on-the-cloud.md#manage-on-boarded-sensors).
349
+
350
+
> [!NOTE]
351
+
> After upgrading to version 22.1.x, the new upgrade log can be found at the following path, accessed via SSH and the *cyberx_host* user: `/opt/sensor/logs/legacy-upgrade.log`.
352
+
>
315
353
## Forward sensor failure alerts
316
354
317
355
You can forward alerts to third parties to provide details about:
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-sensors-on-the-cloud.md
+5-28Lines changed: 5 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,36 +79,13 @@ In such cases, do the following:
79
79
80
80
### Reactivate a sensor for upgrades to version 22.x from a legacy version
81
81
82
-
This procedure describes how to reactivate a sensor specifically when upgrading to version 22.x from version 10.5.x.
82
+
If you are updating your sensor version from a legacy version to 22.1.x or higher, you'll need a somewhat different activation procedure than for earlier releases.
83
83
84
-
**To reactivate your sensor after a legacy upgrade**:
84
+
Make sure that you've started with the relevant updates steps for this update. For more information, see [Update a standalone sensor version](how-to-manage-individual-sensors.md#update-a-standalone-sensor-version).
85
85
86
-
1. Make sure that your sensor is fully upgraded. For more information, see [Update a standalone sensor version](how-to-manage-individual-sensors.md#update-a-standalone-sensor-version).
87
-
88
-
1. In Defender for IoT, select **Sites and sensors** on the left.
89
-
90
-
1. Select the site where you want to update your sensor, and then navigate to the sensor you want to update.
91
-
92
-
1. Expand the row for your sensor, select the options **...** menu on the right of the row, and then select **Prepare to update to 22.x**.
93
-
94
-
:::image type="content" source="media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png" alt-text="Screenshot of the Prepare to update option." lightbox="media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png":::
95
-
96
-
1. In the **Prepare to update sensor to version 22.X** message, select **Let's go**.
97
-
98
-
1. When the new activation file is ready, download it and verify that the sensor status has switched to **Pending activation**.
99
-
100
-
1. Use your newly downloaded activation file to activate your upgraded sensor.
101
-
102
-
1. On your sensor, select **System settings > Sensor management > Subscription & Mode Activation**.
103
-
104
-
1. In the **Subscription & Mode Activation** pane that appears on the right, select **Select file**, and then browse to and select your new activation file.
105
-
106
-
1. In Defender for IoT on the Azure portal, monitor your sensor's activation status. When the sensor is fully activated:
107
-
108
-
- The sensor's **Overview** page shows an activation status of **Valid**.
109
-
- In the Azure portal, on the **Sites and sensors** page, the sensor is listed as **OT cloud connected** and with the updated sensor version.
110
-
111
-
Your legacy sensors will continue to appear in the **Sites and sensors** page until you delete them. For more information, see [above](#manage-on-boarded-sensors).
86
+
> [!NOTE]
87
+
> After upgrading to version 22.1.x, the new upgrade log can be found at the following path, accessed via SSH and the *cyberx_host* user: `/opt/sensor/logs/legacy-upgrade.log`.
-[Upgrade to version 22.1](#upgrade-to-version-221)
47
+
-[CLI command updates](#cli-command-updates)
48
+
-[Update to version 22.1.x](#update-to-version-221x)
48
49
-[New connectivity model and firewall requirements](#new-connectivity-model-and-firewall-requirements)
49
50
-[Protocol improvements](#protocol-improvements)
50
51
-[Modified, replaced, or removed options and configurations](#modified-replaced-or-removed-options-and-configurations)
51
52
53
+
### New sensor installation wizard
54
+
55
+
Previously, you needed to use separate dialogs to upload a sensor activation file, verify your sensor network configuration, and configure your SSL/TLS certificates.
56
+
57
+
Now, when installing a new sensor or a new sensor version, our installation wizard provides a streamlined interface to do all these tasks from a single location.
58
+
59
+
For more information, see [Defender for IoT installation](how-to-install-software.md).
60
+
52
61
### Sensor redesign and unified Microsoft product experience
53
62
54
63
The Defender for IoT sensor console has been redesigned to create a unified Microsoft Azure experience and enhance and simplify workflows.
@@ -159,15 +168,7 @@ The sensor console's **Custom alert rules** page now provides:
159
168
160
169
:::image type="content" source="media/how-to-manage-sensors-on-the-cloud/protocol-support-custom-alerts.png" alt-text="Screenshot of the updated Custom alerts dialog. "lightbox="media/how-to-manage-sensors-on-the-cloud/protocol-support-custom-alerts.png":::
161
170
162
-
### New sensor installation wizard
163
-
164
-
Previously, you needed to use separate dialogs to upload a sensor activation file, verify your sensor network configuration, and configure your SSL/TLS certificates.
165
-
166
-
Now, when installing a new sensor or a new sensor version, our installation wizard provides a streamlined interface to do all these tasks from a single location.
167
-
168
-
For more information, see [Defender for IoT installation](how-to-install-software.md).
169
-
170
-
### Containerized sensor installation
171
+
### CLI command updates
171
172
172
173
The Defender for Iot sensor software installation is now containerized. With the now-containerized sensor, you can use the *cyberx_host* user to investigate issues with other containers or the operating system, or to send files via FTP.
173
174
@@ -181,23 +182,26 @@ As part of the containerized sensor, the following CLI commands have been modifi
The `sudo cyberx-xsense-limit-interface-I eth0 -l value` CLI command was removed. This command was used to limit the interface bandwidth that the sensor uses for day-to-day procedures, and is no longer supported.
187
188
188
189
For more information, see [Defender for IoT installation](how-to-install-software.md) and [Work with Defender for IoT CLI commands](references-work-with-defender-for-iot-cli-commands.md).
189
190
190
-
### Upgrade to version 22.1
191
+
### Update to version 22.1.x
191
192
192
-
Upgrade your sensor versions directly to 22.1. Make sure that you've downloaded and upgraded your sensor machine, and then reactivated your sensor from the Azure portal using the new activation file.
193
+
To use all of Defender for IoT's latest features, make sure to update your sensor software versions to 22.1.x.
193
194
194
-
For more information, see:
195
-
196
-
-[Update a standalone sensor version](how-to-manage-individual-sensors.md#update-a-standalone-sensor-version)
197
-
-[Reactivate a sensor for upgrades to version 22.x from a legacy version](how-to-manage-sensors-on-the-cloud.md#reactivate-a-sensor-for-upgrades-to-version-22x-from-a-legacy-version)
195
+
If you're on a legacy version, you may need to run a series of updates in order to get to the latest version. You'll also need to update your firewall rules and re-activate your sensor with a new activation file.
198
196
199
197
After you've upgraded to version 22.1.x, the new upgrade log can be found at the following path, accessed via SSH and the *cyberx_host* user: `/opt/sensor/logs/legacy-upgrade.log`.
200
198
199
+
For more information, see [Update a standalone sensor version](how-to-manage-individual-sensors.md#update-a-standalone-sensor-version).
200
+
201
+
> [!NOTE]
202
+
> Upgrading to version 22.1.x is a large update, and you should expect the update process to require more time than previous updates.
203
+
>
204
+
201
205
### New connectivity model and firewall requirements
202
206
203
207
With this version, users are only required to install sensors and connect to Defender for IoT on the Azure portal. Defender for IoT no longer requires you to install, pay for, or manage an IoT Hub.
@@ -528,4 +532,4 @@ In sensor and on-premises management console Alerts, the term Manage this Event
528
532
529
533
## Next steps
530
534
531
-
[Getting started with Defender for IoT](getting-started.md)
535
+
[Getting started with Defender for IoT](getting-started.md)
0 commit comments