Re: TNTs Rebooting, was RE: Weird network problems
On Thu, 21 Aug 2003, Geo. wrote: > Even a way to filter within the TNT would be useful if anyone has any ideas > on that. I've already placed filters in my cisco routers for the 92 byte I believe you want to to do this in the radius profile for each user. Similar to port-25 filtering, eh? > pings but that doesn't stop the ones that originate with the dialup user > from crashing the TNT. >
Re: TNTs Rebooting, was RE: Weird network problems
> > "...an intermittent problem that has been discovered to be affecting a > > specific type of network card used by some of the NAS devices that > > populate our network. The problem is exacerbated by the blaster worm and > > has been replicated by Lucent, our vendor and others. In order to resolve > > the issue, we are working with Lucent to test and deploy an emergency > > updated version of software to the affected NAS devices." Has anyone gotten a patch from Lucent yet for the Max TNT's? I need something, I've got a bunch of these and when a customer on the TNT has the worm the ping packets coming from his dialup are causing the TNT to crash. Even a way to filter within the TNT would be useful if anyone has any ideas on that. I've already placed filters in my cisco routers for the 92 byte pings but that doesn't stop the ones that originate with the dialup user from crashing the TNT. Geo.
Re: Weird network problems
> > Is anyone out there tracking down some weird network behavior yesterday > > and today? I'm not talking about ping traffic from the worm or anything > > like that, I'm seeing TNT MAX boxes go unpingable, arp broadcast storms, > > one way traffic blocks on T1's between cisco routers, stuff that I have > > not been able to explain yet. > > I'm seeing the exact same issues with the TNTs and am in the process of > trying to track down exactly what is causing it. So far no pattern has > emerged. go here http://www.cisco.com/warp/public/707/cisco-sn-20030820-nachi.shtml Implement the 92byte ping filter on all interfaces that are allowing the worm's pings thru, solved our problem perfectly. The problem is when the worm pings IP addresses that have nothing on them it creates the arp request, as the number of those requests build some devices can't handle it and it's crashing them. The TNT is one of the more braindead of those devices. I'd be interested in knowing what other devices are also failing from this. Geo.
Re: TNTs Rebooting, was RE: Weird network problems
On Wed, 20 Aug 2003, Andy Walden wrote: > Has anyone opened a ticket with Lucent about this? My initial feeling is > some traffic pattern, possibly a side affect of the recent instability, > could be causing it. Thanks. Lucent is aware of the problem and is working on a fix. One of our networks is O1 and they use massive amounts of TNTs. Excerpt from their announcement yesterday: "...an intermittent problem that has been discovered to be affecting a specific type of network card used by some of the NAS devices that populate our network. The problem is exacerbated by the blaster worm and has been replicated by Lucent, our vendor and others. In order to resolve the issue, we are working with Lucent to test and deploy an emergency updated version of software to the affected NAS devices." Jim -- See what ISP-Planet is saying about us! http://isp-planet.com/services/wholesalers/flexpop.html __ Jim Dawson [EMAIL PROTECTED] Flexpop/Navi.Nethttp://www.flexpop.net 618 NW Glisan St. Ste. 101 v. +1.503.517.8866 Portland, Or 97209 USA f. +1.503.517.8868 ~~
Re: TNTs Rebooting, was RE: Weird network problems
On Wed, 20 Aug 2003, Ejay Hire wrote: > In a word, Yes. We've got two TNT's that have been rock-solid for over > a year that have rebooted 6 times in two days. Any help at all would be > most appreciated. > Has anyone opened a ticket with Lucent about this? My initial feeling is some traffic pattern, possibly a side affect of the recent instability, could be causing it. Thanks. andy -- PGP Key Available at http://www.tigerteam.net/andy/pgp
Re: Weird network problems
> Is anyone out there tracking down some weird network behavior yesterday > and today? I'm not talking about ping traffic from the worm or anything > like that, I'm seeing TNT MAX boxes go unpingable, arp broadcast storms, > one way traffic blocks on T1's between cisco routers, stuff that I have > not been able to explain yet. I'm seeing the exact same issues with the TNTs and am in the process of trying to track down exactly what is causing it. So far no pattern has emerged. andy -- PGP Key Available at http://www.tigerteam.net/andy/pgp
TNTs Rebooting, was RE: Weird network problems
In a word, Yes. We've got two TNT's that have been rock-solid for over a year that
have rebooted 6 times in two days. Any help at all would be most appreciated.
Thanks in Advance,
Ejay Hire
-Original Message-
From: Geo. [mailto:[EMAIL PROTECTED]
Sent: Wed 8/20/2003 3:45 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Weird network problems
Is anyone out there tracking down some weird network behavior yesterday and
today? I'm not talking about ping traffic from the worm or anything like
that, I'm seeing TNT MAX boxes go unpingable, arp broadcast storms, one way
traffic blocks on T1's between cisco routers, stuff that I have not been
able to explain yet.
Just wondering if it's only me seeing this or if others are working on the
same sorts of issues.
I heard a rumor that ICG was also experiencing some strange network problems
so I figured it was time to post.
Geo.
Weird network problems
Is anyone out there tracking down some weird network behavior yesterday and today? I'm not talking about ping traffic from the worm or anything like that, I'm seeing TNT MAX boxes go unpingable, arp broadcast storms, one way traffic blocks on T1's between cisco routers, stuff that I have not been able to explain yet. Just wondering if it's only me seeing this or if others are working on the same sorts of issues. I heard a rumor that ICG was also experiencing some strange network problems so I figured it was time to post. Geo.
