PRTG Paessler nms ağ yönetim sistemi All models error codes
Codes
- HL7Error codeSelect an .hl7 file from the list. This sensor sends it to the target device with every scanning interval. The list shows all files that are available in the \Custom Sensors\hl7 subfolder of the PRTG program directory on the probe system. For files to appear in this list, store them in this subfolder with the extension .hl7. To be accepted by the HL7 interface, your files must have the expected HL7 message format. PRTG comes with two sample .hl7 message files that you can use to test your HL7 monitoring and to have a look at the expected format. These files are in the \Custom Sensors\hl7 subfolder. You can override certain headers using the Message Header sensor setting. You cannot change this value after sensor creation
- OB1Error codeDefine a maximum cycle time for the program cycle organization block (OB1) in milliseconds. PRTG uses this value to calculate the value of the Cycle Ratio channel. Enter a positive integer. You cannot change this value after sensor creation
- OE5Error codeThis sensor only supports systems from the Dell EMC Unity family with Unity OE 5.x
- oft365Error codeThis sensor does not support Microsoft 365 mailboxes. If you want to monitor a Microsoft 365 mailbox, use the Microsoft 365 Mailbox1237 sensor
- S7Error codeThis sensor requires S7 Web API to be enabled on the device
- Top10Error codeOpen a dashboard view with different top 10 lists that show the highest uptime or downtime, ping response times, the bandwidth usage, website response times, the CPU usage, the disk usage, the memory usage, and the system uptime. Click to show top 10 lists for all sensors. Hover over Top 10 Lists to show other options. Follow the menu path that is specific to your setup to only view top 10 lists for a specific probe or group. The shown sensors are selected by default tags
- v1Error codeWe recommend that you use these sensor types for scenarios with thousands of sensors
- v2cError codeWe recommend that you select SNMP v2c (most common) or SNMP v3 in the credentials for SNMP devices 610 of the parent device (if supported by the target device). SNMP v1 does not support 64-bit counters, which might result in invalid data. For more information, see the Knowledge Base: SNMP Traffic sensor suddenly drops at 610Mbps
- v3Error codeSNMP v3 has performance limitations because of the use of encryption. Furthermore, keep in mind that SNMP v3, unlike SNMP v1 and v2c, does not scale with more CPU power. Because of this limitation, PRTG can only handle a limited number of requests per second so that you can use only a limited number of sensors using SNMP v3