- Gold, 750 points or more
While working with a third-party network device that uses the UCD-SNMP-MIB implementation, I'm observing the behavior that one each of "nsNotifyShutdown" and "coldStart" trap is generated, everytime snmpd receives "kill -HUP" to pick up config modifications. Does anyone know if this is the "correct / expected / normal" behavior? I mean I could see the rationale behind it (the assumption that snmpd is down due to device reboot), but OTOH it's sort of "crying wolf" when the physical device itself didn't actually reboot. I'd like to avoid creating this kind of "false" alarm, if possible.