TIM to RSU REST Request not returning successful SNMP bindings about jpo-ode HOT 4 CLOSED

@mvs5465: "Looks like at least the communication to/from the RSU was successful, however sometimes the SNMP daemon will put the error inside of a message body and then still return that with success code 0. We can add some more verbose logging to figure out what’s happening."

from jpo-ode.

Currently we have hardcoded more verbose logging in the branch tim_debug.

We should consider adding a configuration property to toggle more verbose logging.

from jpo-ode.

Looks like this issue occurs when the message already exists in the RSU. To fix this, must set the message status to 6:
snmpset -v3 -u <username> -a MD5 -A <password> -l authNoPriv <ip> RSU-MIB::rsuSRMStatus.3 = 6

from jpo-ode.

As Matt said, I am able to complete sending a TIM to an RSU now as long as I disable an existing TIM with the same index. This has been resolved, thank you!

from jpo-ode.