Home page logo

nanog logo nanog mailing list archives

FW: TNT issues "workaround"
From: "John Lord" <lord () allturbo com>
Date: Sat, 23 Aug 2003 13:31:44 -0400

I seem to be having the same or similar problems with my Cisco boxes
also , they either reboot or the pris hang , users get busy's but no one
is logged in at all , when I do a show isdn status it shows b channels
in use but no one on, the only way to fix is reboot the box , and it
seems to be timed , everyday at 1400 and 2200 hours , since Monday
anybody body heard of ciscos acting funny this week?

John Lord(lord () allturbo com)
It Manager
AllTurbo Internet Services Inc
410-213-9388 Office

-----Original Message-----
From: Brian Wallingford [mailto:brian () meganet net] 
Sent: Saturday, August 23, 2003 1:41 AM
To: nanog () merit edu
Subject: TNT issues "workaround"

I haven't seen specific details posted here, so:

Like many others, we've had a few TNTs online for years without hiccups
or reboots until this week.  Beginning late Sunday, we saw seemingly
random blade reboots, and total system crashes.  Errors ranged from
memory leaks to infinite loops on the controller blade, but all blades
susceptible.  HDLC2 blades seemed to be particularly vulnerable.

We saw boxes that had been rock-solid for very long periods suddenly
rebooting at periods ranging from 20 minutes to 4 hours, with no obvious
cause (i.e., nothing more specific than the above).  Border and core 
filtering of icmp echo * did little good.

On the suggestion of some folks on another list, and against my better
judgment, we disabled route caching in order to free up additional
memory (though memory did not appear fragmented).  This stabilized all
involved boxes, and surprisingly, did not result in significant
degradation of end user performance.

Granted, it's not a true fix, but it may get you a few extra Z's at


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]