While I'm at it - enough with SNMP. Replace it all with node.js running on the networking device and using HTTPS as the transport and JSON as the message format.
I'm not sure how I feel about that. While returned json data is easier to handle, SNMP is generally considered as for management purposes and is permitted through our firewalls on that basis. HTTP/S is largely denied across the network so that users are pushed through a proxy. I'm sure there are a lot of other companies with a similar setup.
How would you differentiate user-requested HTTP/S data from API-requested HTTPS? Not without complicating things further than they need to be complicated.
As well as that.. what would be your solution to device-generated traps that are automatically sent without someone/something having requested that data?
SNMP is old and occasionally troublesome but it seems to work for the purpose it serves.
(Sorry if I'm not supposed to be replying to other peoples' topics, I'm new here. Am I supposed to not reply to other peoples' topics??)
