Why is HTTP 500 thrown in DDV when the SNMP location or any string contains any reserved (special) characters?
A. This occurs when the device SNMP location string is configured and contains reserved characters (for example, a pipe symbol (| or ^) characters). Reason: Since internal logic has used “|” and “^” characters for parsing, the string value contains any of these characters. Then the user might hit this 500 error. The solution or suggestion: It is better to not to use the special character “|” and “^” for any of the device values.
Related Questions
- Can we change without restrictions the location of any key text string in the templates? Or there are predefined mandatory locations for them in the templates?
- If the Location code is built right into the new account string, will this present a problem every time there is a change of address?
- Are there any special considerations that should be noted in determining a proper testing location for the PEA POD?
