Solved!
Go to SolutionTelemetry Collection Failure
Hello all, we are experiencing telemetry failure as shown in image below. The second image below says that there is a credential issue but I checked and the credentials are fine. I even reinputted the credenetials on Secure Connect Gateway and retested telemetry but no luck. Also, telemetry is failing on servers with iDRAC 7 and 8. I don't think iDRAC version is the cause since servers with iDRAC version 8 have telemetry working fine. Under iDRAC settings -> Network -> services, the configuration is the same for the working and non working servers. Also on iDRAC there is no mention of WSMAN protocol so I couldn't do anything about as suggested by the error. I really doubt that the login credentials are to blame here as I am able to login fine as an admin. Any clues or leads are appreciated, thank you!
0
0
Posted July 29th, 2026 15:33
Hello so the resolution for my case appears to be resetting the SCG VM. Also initially I did not have a credential profile assigned to the telemetry collection process but it was only after resetting the SCG VM that telemetry data collection worked across all devices. I appreciate all the help troubleshooting!
0
0
Posted April 13th, 2026 01:01
Hello, thank you for choosing Dell and welcome to our community!
To assist you further, could you please provide the following details:
- Your Service Tag – Please send this via direct message using the link below:
https://www.dell.com/community/en/direct-messaging
- The version of SCG you are currently using. Secure Connect Gateway 5.x — Virtual Edition Support Matrix | Dell US
Respectfully,
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!- Your Service Tag – Please send this via direct message using the link below:
0
0
Posted April 13th, 2026 15:02
Hello, thank you for the response, please see below for requested information:
1) Please see direct messages.
2)
for IP 10.12.14.107, that is PowerEdge R520, with iDRAC 7 version 2.65.65.65
for IP 10.12.14.27 that is PowerEdge R530, with iDRAC 8 version 2.86.86.86
for IP 10.12.14.154 that is NX3230 with iDRAC 8 version 2.83.83.83
I want to note that we have a NX3230 with iDRAC 8 version 2.83.83.83 that had successful (partial) collection of telemetry so I'm not sure if iDRAC version or Server type is the issue.
0
0
Posted July 27th, 2026 22:25
Hello thank you for the detailed response
1) The compatibility matrix shows no issue with my setup
2) I tested the ports using Test-NetConnection -ComputerName "host_name" -Port 443 mentioned in the link and port 135 is open on the target device. Port 22 and 443 are closed according to this command
3) I also tried the curl command you mentioned via command line and the output shows that:
- TCP reachability ✓
- TLS handshake (TLSv1.2, cipher negotiation, certificate exchange) ✓
- The web server responds correctly (302 redirect to login page) ✓
Also service module is not installed on any of the devices' iDRAC. I tested on another device and it was partially successful for telemetry data collection (also iDRAC8). Appreciate the continued support, will keep trying telemetry data collection on other devices to find a pattern
DELL-Joey C
Moderator
•
4170 Posts
•
20965 Points
0
0
Posted April 14th, 2026 05:38
Hi,
I gave a rought look at the compatibility guide here https://www.dell.com/support/manuals/en-us/secure-connect-gateway/scg_5.x_ve_sm/12th-generation-poweredge-servers?guid=guid-5fcf90c1-1bc5-41a1-b331-c10059a01b12&lang=en-us seems that the iDRAC version should be sufficient to get compatible with SCG.
Next is to check if the ports are open for different protocols: https://www.dell.com/support/manuals/en-us/secure-connect-gateway/scg_5.x_ve_sm/supported-servers?guid=guid-59624dd9-861d-457b-b358-87a9a01f6e6a&lang=en-us
After verifying the ports, you may try log in to the SCG virtual appliance CLI via SSH using your
rootcredentials, run a ping test to the target device. Since you the error points to WSMAN, try curl -k -v https://<target_device_IP>:443DELL-Joey C
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’ if I did.