We experienced the packet loss with 9.0.9. Turning off the route cache or limiting it to 15000 helped keep the TNTs responsive on their own subnet, but copious rebooting and just watching a sniffer for infected customer's dialed up and disabling them is all we've come up with to help. The fact that people running 10.x.x don't seem to have this problem irritates the hell out of me. I don't remember once having anything being solved by Lucent the years I had a service contract. I either got help here or figured it out on my own. In several instances, doing the opposite of what they recommended was the solution. I'll be happy when the spare parts run out and we can replace these things. On Wed, Aug 27, 2003 at 01:54:28PM -0500, Ejay Hire wrote: > I am crossposting a message I sent to NANOG. We have had similar issues > on a crippling scale over the last few days, but it appears we have > finally resolved them. > > -----Forwarded Message----- > From: Ejay Hire > Sent: Wednesday, August 27, 2003 11:47 AM > To: 'Andy Walden'; Geo. > Cc: NANOG > Subject: RE: Max TNT ping thing > > Here is a summary of our experiences with the bug. > > Last Thursday, A TNTs with years of uptime rebooted. No cause was > apparent, and nothing relevant happened in the logs. On Friday, It > happened to a different TNT. This occurred with increasing frequency > over the weekend, and we didn't get a lot of sleep. We tried using a > filter in the tnt to block port 135 and 4444 to no avail, and then tried > a filter to block ICMP in the tnt also to no avail. Next, we removed > the tnt filters and tried rate-limiting ICMP to the TNT's. That didn't > work. Next we removed the rate-limit and applied the Cisco-supplied > anti-nachi route-map to the upstream interfaces facing the Tnt's. This > significantly reduced the problem, but we were still rebooting every 12 > hours or so. Disabling route-caching on the TNT stopped the rebooting > problem, but we were seeing 40% packet loss on one of the TNTs. (Note, > both TNT's have a Ds-3 of PRI's, and use the TNT-SL-E10-100 four port > Ethernet cards) The packet loss was only affecting one TNT, and we > discovered that it was running 9.0.6 while the unaffected box was > running 9.0.9. Upgrading the box to 9.0.9 fixed the packet loss issue. > We are currently up and haven't had any blips in 24 hours. (knock on > wood.) > > -Ejay > > -----Original Message----- > From: Chad Whitten [mailto:chadwick at nexband.com] > Sent: Tuesday, August 26, 2003 10:33 PM > To: Yogendra Joshi > Cc: ascend-users at max.bungi.com; > Subject: Re: (ASCEND) Serious problem with TNT > > I am having a similar problem. At first, I had 1 tnt rebooting itself > every few hours (always it seemed at peak traffic times) and the only > errors I would get would be related to the ethernet card. Now I have > another TNT doing the same thing. Both are running 7.2.3 TAOS, both > have > the 4 port ethernet cards. They are on different networks connecting to > different radius servers. The TNT that has just started acting up has > much lower usage (about 70 users at peak time) than the other TNT (400+ > at > peak time). > > The problem first appeared last week and has now spread to another > machine. I have one more TNT that isnt doing this and a bunch of > max2024's and max4048's that are fine. > > Very frustrating. Anyone else care to chime in? > > Chad Whitten > Network/Systems Administrator > neXband Communications > cwhitten at nexband.com > 601-944-4801 > > On Tue, 26 Aug 2003, Yogendra Joshi wrote: > > > > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ -- Denny Reiter denny at reiters.org So I don't hurt your feelings: happydenny at reiters.org The ability to quote is a serviceable substitute for wit. - Maugham ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/