When querying SNMP on certain BGP neighbors, it reports weird results back.

.1.3.6.1.4.1.2636.5.1.1.2.1.1.1.11.0.1.74.125.52.61.1.74.125.52.62 =
"J}4>"
.1.3.6.1.4.1.2636.5.1.1.2.1.1.1.7.0.1.74.125.52.61.1.74.125.52.62 =
"J}4="

We have opened a case with Juniper and apparently this is correct, but it needs to be interpreted differently. This is the answer Juniper provides:

"I have got the confirmation from development it's working as per design.

In Snmp there is a convention that the string is rendered as a string when all of the bytes are in the ascii range,
otherwise they are rendered as hex bytes. Note that the correct values are returned.

snmpwalk -v2c -c Juniper 10.209.107.90 .1.3.6.1.4.1.2636.5.1.1.2.1.1.1.7
SNMPv2-SMI::enterprises.2636.5.1.1.2.1.1.1.7.0.1.74.125.52.61.1.74.125.52.62 = STRING: "J}4="
SNMPv2-SMI::enterprises.2636.5.1.1.2.1.1.1.7.0.1.192.168.10.18.1.192.168.10.7 = Hex-STRING: C0 A8 0A 12

As per convention Instead of Hex-STRING it is returning STRING for ip 74.125.52.61.
Since all the bytes in ip 74.125.52.61 are in ascii range.

if you convert STRING TO Hex-STRING you will get the proper output.

http://codebeautify.org/string-hex-converter

J}4= (STRING to HEX) 4a7d343d (HEX to ip) 74.125.52.61

if you convert this hex to ip you will get the proper result.

So basically it's working as per the standard convention and STRING is being returned instead of Hex-String.

Please check it on the NMS side, ideally your NMS server should have the logic to parse (STRING to HEX-STRING) correctly.

Let me know if you have any further queries."