Security

Three days ago, everything was fine

Two days ago, my cacti-server started to draw blank grafs.

Messages at MX80:

Sep 24 16:59:30  jun-m9 mib2d[1242]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping.  Attempting to re-register.
Sep 24 17:01:30  jun-m9 snmpd[1243]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes
Sep 24 17:01:30  jun-m9 snmpd[1243]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes
Sep 24 17:10:50  jun-m9 mib2d[1242]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping.  Attempting to re-register.
Sep 24 17:12:50  jun-m9 snmpd[1243]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes
Sep 24 17:12:50  jun-m9 snmpd[1243]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes

And now

1.

show snmp mib walk 1.3.6.1.2.1.2 - void

but

show snmp mib walk 1.3.6.1.2.1.4 - good
(ipCidrRouteDest.1.8.101.0.255.255.255.0.0.87.245.255.93 = 1.8.101.0 , etc)

2. snmpwalk from inside (without mibs) - "Timeout: No Response from " after a certain number of lines  (random, may be 0, may be 200000)

Help me, please!

I had a similar problem, Nagios checks started failing and returning null values with similar log messages:

Jan 8 06:20:21 core-01 snmpd[1428]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 56 bytes, actually sent 8 bytes
Jan 8 06:20:21 core-01 snmpd[1428]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 48 bytes

Jan  8 08:00:18  core-01 pfed: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)

We did a force fail over to the redundant RE and it fixed the SNMP problems. Currently have a TAC case open with juniper hopefully they'll be able to determine if it's a hardware or software related issue.

Hi ,

What did JTAC told about the case.

Even I am also facing same the problem.

Jani

Hi,

I'm hitting the same issue. Did JTAC managed to resolve it?

Any updates from the TAC? 

We have solved the problem, by restarting pfed, then mib and snmp processes...