Since more or less the last two versions from end february and march I determine some Problems to monitor my HP P2000 Storage via SSH Sensor. Befor this Version it was run successful. Since the last to versions i got periodically errors the following errors :
SSH SAN Enclosure (Sensor) : SSHBase TOctCheckSSHSANEnclosure.ParseXML threw exception
SSH SAN Logical Disk (Sensor) : Wrong Data Format (code: PE216)
I'm login via ssh via Login and Password (WBEM Use Protocol: https with Ports 5988 or 5989) SSH Port 22 Run the command as the user connecting (default)
The test happens every hour and I did not change any configuration on P2000 Storage.
Does somebody have some recommendations or similar Problems with HP P2000 ?
thanks for any answers Thomas
Article Comments
Thx for your anwser. The interval is 60 minutes . The connection timeout was 60 sec and the shell timeout was 5 sec. I also tried now with connection timeout 90 sec an shell timeout 15 sec but still with the same issue or error message Wrong Data Format (code: PE216)
Mar, 2015 - Permalink
Hello
Can you please try restarting the SSH Controller on the SAN(s)? Please also add the ssh sensor anew.
Mar, 2015 - Permalink
Hi
Same problem here on an MSA2040. Periodically errors such as:
SSHBase Structural error in xml file
Falsches Datenformat / Wrong Data Format (Code: PE216)
SSHBase TOctCheckSSHSANEnclosure.ParseXML threw exception
Roman
(PRTG: 15.1.14.1710+)
Mar, 2015 - Permalink
Dear Roman
Please open the sensor settings and enable the setting "Write result to disk". When the sensor is in error state, please copy the file and send it to support@paessler.com for analysis.
Mar, 2015 - Permalink
hi, simliar problems here. Changing timeout settings doesn't make any difference. Readding sensors two. These happens on 2 monitored arrays. One is P2000 SAS, one is P2000 iSCSI, both G3. These errors are random. No particular pattern. Sometimes they work ok for a day or two, sometimes not. In general we find P2000 ssh sensors unreliable.
examples: SSHBase TOctCheckSSHSANEnclosure.ParseXML threw exception
SSHBase Junk after document element </RESPONSE>
Wrong Data Format (code: PE216)
Kind regards Marek
Mar, 2015 - Permalink
Dear Igmodo
We also need an example result when the sensor is in error state to investigate further.
Mar, 2015 - Permalink
PRTG version 15.1.15.2021/2022 comes with several stability improvements for SSH SAN sensors to avoid such errors. Please update PRTG if you run an older version.
Apr, 2015 - Permalink
I have upgraded to PRTG version 15.1.15.2021/2022, I changed the timeouts. Now I am in a warning state instead of error, but I am still getting the wrong data format error. I am also using an HP P2000.
May, 2015 - Permalink
Dear abettig
Please open the sensor settings and enable the setting "Write result to disk". When the sensor is in error state, please copy the file and send it to support@paessler.com for analysis.
Please also allow me to ask if you actually updated to the by now outdated 15.1.15 version, or if you updated to the current 15.2.16 version of PRTG. For log file analysis, it is important that we get the files of a recently released PRTG version.
May, 2015 - Permalink
Hello,
What interval are you using for this sensors? Could you try something like 15 minutes? Also, increase the connection timeout to 90 seconds and the shell timeout to 15 seconds (within the sensor settings).
Mar, 2015 - Permalink