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-set-up-your-network.md
+9-19Lines changed: 9 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,8 +147,6 @@ Use the following tables to ensure that required firewalls are open on your work
147
147
|--|--|--|--|--|--|--|
148
148
| HTTPS | TCP | Out | 443 | Access to Azure | Sensor |OT network sensors connect to Azure to provide alert and device data and sensor health messages, access threat intelligence packages, and more. Connected Azure services include IoT Hub, Blob Storage, Event Hubs, and the Microsoft Download Center.<br><br>**For OT sensor versions 22.x**: Download the list from the **Sites and sensors** page in the Azure portal. Select an OT sensor with software versions 22.x or higher, or a site with one or more supported sensor versions. Then, select **More options > Download endpoint details**. For more information, see [Sensor management options from the Azure portal](how-to-manage-sensors-on-the-cloud.md#sensor-management-options-from-the-azure-portal).<br><br>**For OT sensor versions 10.x**: `*.azure-devices.net`<br> `*.blob.core.windows.net`<br> `*.servicebus.windows.net`<br> `download.microsoft.com`|
149
149
150
-
151
-
152
150
### Sensor access to the on-premises management console
153
151
154
152
| Protocol | Transport | In/Out | Port | Used | Purpose | Source | Destination |
@@ -196,32 +194,24 @@ This section provides troubleshooting for common issues when preparing your netw
196
194
197
195
1. Connect a monitor and a keyboard to the appliance.
198
196
199
-
1. Use the *support* user and password to sign in.
197
+
1. Use the **support** user* and password to sign in.
200
198
201
199
1. Use the command **network list** to see the current IP address.
202
200
203
-
4. If the network parameters are misconfigured, use the following procedure to change it:
204
-
205
-
1. Use the command **network edit-settings**.
206
-
207
-
1. To change the management network IP address, select **Y**.
208
-
209
-
1. To change the subnet mask, select **Y**.
201
+
4. If the network parameters are misconfigured, sign into the OT sensor as the **cyberx_host** user* to re-run the OT monitoring software configuration wizard. For example:
210
202
211
-
1. To change the DNS, select **Y**.
203
+
```bash
204
+
root@xsense:/# sudo dpkg-reconfigure iot-sensor
205
+
```
212
206
213
-
1. To change the default gateway IP address, select **Y**.
207
+
The configuration wizard starts automatically. For more information, see [Install OT monitoring software](../how-to-install-software.md#install-ot-monitoring-software).
214
208
215
-
1. For the input interface change (for sensor only), select **Y**.
216
-
217
-
1. For the bridge interface, select **N**.
218
-
219
-
1. To apply the settings, select **Y**.
220
-
221
-
5. After you restart, connect with user support, and use the **network list** command to verify that the parameters were changed.
209
+
5. Restart the sensor machine and sign in with the **support** user*. Run the **network list**command to verify that the parameters were changed.
222
210
223
211
6. Try to ping and connect from the GUI again.
224
212
213
+
(*) For more information, see [Default privileged on-premises users](roles-on-premises.md#default-privileged-on-premises-users).
214
+
225
215
### Appliance isn't responding
226
216
227
217
1. Connect with a monitor and keyboard to the appliance, or use PuTTY to connect remotely to the CLI.
0 commit comments