Getting these log messages:



May 28 00:15:04 hostname snmpd[1699]: SNMPD_SEND_FAILURE: jnx_netsnmp_udp_send: send message (100.92.175.137) failure: Operation not permitted
                
May 28 00:15:06 hostname snmpd[1699]: SNMPD_SEND_FAILURE: jnx_netsnmp_udp_send: send message (172.28.132.141) failure: Operation not permitted
                
May 28 00:15:07 hostname snmpd[1699]: SNMPD_SEND_FAILURE: jnx_netsnmp_udp_send: send message (100.92.175.137) failure: Operation not permitted
                
May 28 00:15:09 hostname snmpd[1699]: SNMPD_SEND_FAILURE: jnx_netsnmp_udp_send: send message (172.28.132.141) failure: Operation not permitted
                
May 28 00:15:10 hostname snmpd[1699]: SNMPD_SEND_FAILURE: jnx_netsnmp_udp_send: send message (100.92.175.137) failure: Operation not permitted
                
May 28 00:15:12 hostname snmpd[1699]: SNMPD_SEND_FAILURE: jnx_netsnmp_udp_send: send message (172.28.132.141) failure: Operation not permitted

Operation not permitted logs appear, and SNMP is properly configured.

Operation not permitted error logs are related to a firewall filter blocking inbound or outbound UPD port 161 / 162.

If the customer has an outbound filter in set like this one:

 lo0 {

    unit 0 {

      family inet {

        filter {

          input PROTECT-RE-IN;

          output PROTECT-RE-OUT;

        }

        /* Loopback 0 equiv */

        address 123.123.123.123{

          primary;

          preferred;

        }

        address 123.123.123.123/32;

      }

Consider deactivating both filters temporarily to see if the issue if fixed and then look into fixing the filters. There shouldn't be an outbound filter on the loopback interfaces.