This article explains the scenario where we encounter the snmpd not running error.

In a virtual chassis setup, upon trying to kill the snmpd for all members the below error is seen on linecards.

error: Simple Network Management Protocol process is not running

In customer's environment it was a 4 member VC, in which FPC 0 was master and FPC 1 was backup. Rest of the 2 FPCs were linecards. The following was the output when trying to restart snmpd on all members of the VC:

 

>restart snmpd gracefully all-members

fpc0:

-----------------------------------------------------------

Simple Network Management Protocol process started, pid <>

fpc1:

-----------------------------------------------------------

Simple Network Management Protocol process started, pid <>

fpc2:

-----------------------------------------------------------

error: Simple Network Management Protocol process is not running

error: Simple Network Management Protocol process was not restarted

fpc3:

-----------------------------------------------------------

error: Simple Network Management Protocol process is not running

error: Simple Network Management Protocol process was not restarted

In a virtual chassis setup, the SNMPD runs only on routing-engine roles i.e, master and backup member. Thus, when we restart SNMPD for all members on the VC, the error is seen for linecard members which is an expected behavior.