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/iot-edge/how-to-connect-downstream-device.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: How to configure downstream or leaf devices to connect to Azure IoT
4
4
author: kgremban
5
5
manager: philmea
6
6
ms.author: kgremban
7
-
ms.date: 09/07/2019
7
+
ms.date: 10/08/2019
8
8
ms.topic: conceptual
9
9
ms.service: iot-edge
10
10
services: iot-edge
@@ -178,18 +178,24 @@ This section introduces a sample application to connect an Azure IoT Java device
178
178
This section introduces a sample application to connect an Azure IoT Python device client to an IoT Edge gateway.
179
179
180
180
1. Get the sample for **send_message** from the [Azure IoT device SDK for Python samples](https://github.com/Azure/azure-iot-sdk-python/tree/master/azure-iot-device/samples/advanced-edge-scenarios).
181
-
2. Ensure that you are either running in an Edge container, or in a debug scenario, have the `EdgeHubConnectionString` and `EdgeModuleCACertificateFile` environment variables set.
181
+
2. Ensure that you are either running in an IoT Edge container, or in a debug scenario, have the `EdgeHubConnectionString` and `EdgeModuleCACertificateFile` environment variables set.
182
182
3. Refer to the SDK documentation for instructions on how to run the sample on your device.
183
183
184
184
185
185
## Test the gateway connection
186
186
187
-
This is a sample command that tests that everything has been set up correctly. You should see a message saying "verified OK".
187
+
Use this sample command to test that your downstream device can connect to the gateway device:
This command tests connections over MQTTS (port 8883). If you're using a different protocol, adjust the command as neccessary for AMQPS (5671) or HTTPS (433).
194
+
195
+
The output of this command may be long, including information about all the certificates in the chain. If your connection is successful, you'll see a line like `Verification: OK` or `Verify return code: 0 (ok)`.
0 commit comments