In order to determine what exactly might be causing the clog in the SNMP engine, we need to gather an SNMP stack output while the issue is occurring. To gather this stack you need to do issue the below command:
CR-NMS-2811#show proc cpu sort | inc CPU|PID|SNMP ENG CPU utilization for five seconds: 2%/0%; one minute: 1%; five minutes: 1% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 303 137304 51825 2649 0.00% 0.01% 0.00% 0 SNMP ENGINE
Then, using the PID you get in return (in my case 303) get an SNMP stack this way:
The above stack with only 4 RA's means the engine is idle. You want to get several of these over 2 or 3 second intervals until you see a longer list of RA's and the list is repeating itself. This means it is stuck there.
I can decode that stack and check exactly where the problem is. You might just want to log a putty with all the outputs you get. I also need the full "show version" of this device to decode.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...