07-21-2003 08:23 AM - edited 03-09-2019 04:07 AM
I have my sensors hang every one-two days. Started to happened after upgrade to 4.1.1S37. The only workaround is to power-cycle/reset to a sensor!
Is anyone else observe the same?
08-09-2003 09:41 PM
Thank you Dmitri and Robert.
For Dmitri's sensor, let us watch his memory usage
and the 'sh in gr' stat of TCP queued to see if the
TCP queue growth problem happens there.
Robert, your memory situation does sound serious and
the TCP queued should NOT be staying around for more than a couple minutes. Just a quick note: the memory
status reported by 'sh ver' is not very accurate. It
does not show the main/cached/swap values that are important to determine the real memory usage. We use the service account tool 'top' for this.
Robert, please email me directly at kasper@cisco.com
and include your TAC contact CC'ed on the mail.
We will keep pressing on looking into these possible
bug areas.
-JK
08-28-2003 08:35 AM
I have the exact same problem. I can ping the device which is a 4230-FE. I cannot telnet or access the device at the console. The monitor is blank and not sleeping. I am in the process of upgrading the sensors from the old 2.5(S0).
08-29-2003 08:44 PM
Hi,
We have an engineering build we are distributing
on a case-by-case basis. It is a patch for sensorApp
with several defects fixed. It is running at
several sites and is operating correctly.
I can make this available to you.
Please open a TAC case and send me the case number
and your contact information to kasper@cisco.com
I will give you the download and install instructions.
Online this weekend.
-JK
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide