Not receiving the request for snmp with multiple server polling

Other Northbound Interfaces
1

From snmp log we see, request is received at this time. This polling is happening for every 30 secs. we dont see the request getting generated from confd/devel.log. After running 2 to 5 days, cli becomes very slow. Can you please suggest what can be done here . With only snmp agent running things looks fine. But when run with multiple , this issue is happening.

2-Jul-2025::02:42:01.462 br-gru-gru09-sdwgw01-2 confd[5423]: snmp get-request reqid=38555064 172.24.211.210:57792 (INTEGER bgpPeerStatusState.75000.0.4.0.0.0.0.0.1.4.172.27.223.109.0.0)(INTEGER bgpPeerStatusState.75000.0.4.0.0.0.0.0.1.4.172.27.223.113.0.0)(INTEGER bgpPeerStatusState.75000.0.4.0.0.0.0.0.1.4.172.31.134.143.0.0)(INTEGER bgpPeerStatusState.75000.0.4.0.0.0.0.0.1.4.172.31.134.155.0.0)(INTEGER bgpPeerStatusState.75000.1.4.172.31.154.162.0.1.4.172.27.223.0.0.0)(INTEGER bgpPeerStatusState.75000.1.4.172.31.154.162.0.1.4.172.27.223.12.0.0)(INTEGER bgpPeerStatusState.75000.1.4.172.31.154.162.0.1.4.172.27.223.4.0.0)(INTEGER bgpPeerStatusState.75000.1.4.172.31.154.162.0.1.4.172.27.223.48.0.0)(INTEGER bgpPeerStatusState.75001.1.4.104.135.248.131.0.1.4.104.135.248.130.0.0)(INTEGER bgpPeerStatusState.75001.2.16.42.0.121.224.3.252.0.1.0.0.0.0.0.0.1.191.0.2.16.42.0.121.224.3.252.0.1.0.0.0.0.0.0.1.190.0.0)(INTEGER bgpPeerStatusState.75002.1.4.104.135.246.55.0.1.4.104.135.246.54.0.0)(INTEGER bgpPeerStatusState.75002.2.16.42.0.121.225.8.64.0.1.0.0.0.0.0.0.5.73.0.2.16.42.0.121.225.8.64.0.1.0.0.0.0.0.0.5.72.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.0.4.0.0.0.0.0.1.4.172.27.223.109.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.0.4.0.0.0.0.0.1.4.172.27.223.113.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.0.4.0.0.0.0.0.1.4.172.31.134.143.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.0.4.0.0.0.0.0.1.4.172.31.134.155.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.1.4.172.31.154.162.0.1.4.172.27.223.0.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.1.4.172.31.154.162.0.1.4.172.27.223.12.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.1.4.172.31.154.162.0.1.4.172.27.223.4.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75000.1.4.172.31.154.162.0.1.4.172.27.223.48.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75001.1.4.104.135.248.131.0.1.4.104.135.248.130.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75001.2.16.42.0.121.224.3.252.0.1.0.0.0.0.0.0.1.191.0.2.16.42.0.121.224.3.252.0.1.0.0.0.0.0.0.1.190.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75002.1.4.104.135.246.55.0.1.4.104.135.246.54.0.0)(Unsigned32 bgpPeerStatusOutPrfxesAdvertised.75002.2.16.42.0.121.225.8.64.0.1.0.0.0.0.0.0.5.73.0.2.16.42.0.121.225.8.64.0.1.0.0.0.0.0.0.5.72.0.0)(TimeTicks sysUpTime)(Counter32 ifInDiscards.11.)

we see from devel.log,

2-Jul-2025::02:41:01.250 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:6d 0 0}
2-Jul-2025::02:41:01.251 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:6d 0 0}
2-Jul-2025::02:41:01.253 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:71 0 0}
2-Jul-2025::02:41:01.254 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:71 0 0}
2-Jul-2025::02:41:01.255 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:8f 0 0}
2-Jul-2025::02:41:01.256 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:8f 0 0}
2-Jul-2025::02:41:01.256 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:9b 0 0}
2-Jul-2025::02:41:01.257 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:9b 0 0}
2-Jul-2025::02:41:01.258 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:00 0 0}
2-Jul-2025::02:41:01.259 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:00 0 0}
2-Jul-2025::02:41:01.260 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:04 0 0}

Next one came at,

2-Jul-2025::02:43:01.676 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c new_trans succeeded daemon id: 5 session id: 2083542 worker id: 26 2-Jul-2025::02:43:01.676 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:6d 0 0}
2-Jul-2025::02:43:01.678 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:6d 0 0}
2-Jul-2025::02:43:01.679 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:71 0 0}
2-Jul-2025::02:43:01.680 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1b:df:71 0 0}
2-Jul-2025::02:43:01.681 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:8f 0 0}
2-Jul-2025::02:43:01.682 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:8f 0 0}
2-Jul-2025::02:43:01.683 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:9b 0 0}
2-Jul-2025::02:43:01.684 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 unknown 00:00:00:00 0 ipv4 ac:1f:86:9b 0 0}
2-Jul-2025::02:43:01.684 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:00 0 0}
2-Jul-2025::02:43:01.685 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:00 0 0}
2-Jul-2025::02:43:01.686 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:04 0 0}
2-Jul-2025::02:43:01.687 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object succeeded for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:04 0 0}
2-Jul-2025::02:43:01.688 br-gru-gru09-sdwgw01-2 confd[5423]: devel-c get_object request for callpoint ‘oper-dc-bgp’ path /DC-BGP-MIB:DC-BGP-MIB/bgpPeerStatusTable/bgpPeerStatusEntry{75000 ipv4 ac:1f:9a:a2 0 ipv4 ac:1b:df:0c 0 0}

2

Hi,

Starting with the 30 second queries that don’t seem to show up in the devel.log, what does the audit.log have in for the new snmp queries. Are you still seeing them arrive every 30 seconds?

Best,
Scott

3

Thanks for the reply. Yes. we see queries coming at every 30 second frequency in snmp.log. Another thing is, snmpwalk works fine, but the problem seems to be happening with snmpbulkwalk -Cr50 -v2c -c public -M. Any suggestions where to look for.

4

If you are not seeing errors in any of the logs (are all logs turned on?), then are these requests queueing anywhere, i.e. if you stop the requests, do they continue for a while?

If neither of these two things are happening, I don’t know where the requests would be going.

What release are you running on?

Scott