The customer upgraded an MX204 device to 24.2R2.18 and after the upgrade they noticed new syslog messages which are constant related to SNMP Message Max size.
May 7 23:15:09 router snmpd[21585]: LIBJSNMP_NS_LOG_INFO: INFO: msgMaxSize from NMS:65507, session msgMaxSize 65507,
May 7 23:15:39 router last message repeated 2 times
May 7 23:16:09 router snmpd[21585]: LIBJSNMP_NS_LOG_INFO: INFO: msgMaxSize from NMS:2048, session msgMaxSize 65507,
May 7 23:16:09 router snmpd[21585]: LIBJSNMP_NS_LOG_INFO: INFO: msgMaxSize from NMS:65507, session msgMaxSize 65507,
May 7 23:16:39 router snmpd[21585]: LIBJSNMP_NS_LOG_INFO: INFO: saxatile from NMS:1500, session msgMaxSize 65507,
May 7 23:16:39 router snmpd[21585]: LIBJSNMP_NS_LOG_INFO: INFO: msgMaxSize from NMS:65507, session msgMaxSize 65507,
May 7 23:17:09 router last message repeated 2 times
May 7 23:18:39 router last message repeated 5 times
These are SNMP INFO level logs and provide additional information to the customer.
By default, SNMP message max size is 65507. With PR/1817865 fix, the system uses the minimum of the following two as max message size of packet to be sent out:
* (1) msgMaxSize received from NMS server
* (2) session's sndMsgMaxSize (configured by 'set snmp packet-size <>')
PR/1817865 Resolved-In
evo:24.2R2-EVO evo:24.4R1-EVO
junos:24.2R2 junos:24.4R1