Power supplies? Hmmm, the power doesn't go out. Could a bad power supply cause routing problems? I've run fsck's on the flash card and it passes. Does replacing the DRAM card require a complete code and config update? On Thu, 14 Jun 2001, ISPstuff wrote: > Does this have dual power supplies? I would try a power supply and/or a > DRAM card. They are cheap and either could cause it. > > Tom > > At 08:25 AM 6/14/01 -0500, you wrote: > >Big picture: > > Max TNT - been in place and working for 1 1/2 to 2 years. > > 3 nailed t1's to central POP > > 5 switched t1's / 3 48mod modem cards > > 1 nailed t1 to remote POP > > 1 32idsl card (1 customer) > > 1 24sdsl card (serveral customers) > > dircode > > Flash card code directory: > > Card 1, directory size 16 > > 4ether2-card reg good 190478 Dec 8 1999 7.2.3e4 > > hdlc2-card reg good 689696 Dec 8 1999 7.2.3e4 > > 8t1-card reg good 208665 Dec 8 1999 7.2.3e4 > > csmx-card reg good 875687 Dec 8 1999 7.2.3e4 > > 32idsl-card reg good 618803 Dec 8 1999 7.2.3e4 > > 24sdsl-data-card reg good 545552 Dec 8 1999 7.2.3e4 > > shelf-controller reg good 1308931 Dec 8 1999 7.2.3e4 > > > >Problem > > About every two weeks for the last few months this tnt will stop > >routing. What I mean by stop routing is this: > > x -------------- y ---------- z > > remote pop the tnt NOC > > > >from z I can ping, traceroute and log into y no problem. but pinging x > >results in massive packet loss. > >ping from z to y = no packet loss, t1's have no errors, etc... > >ping from y to x = no packet loss, t1 has no errors, etc... > >ping from z to x = massive packet loss! traceroutes time out at y > >* note: it's not only the remote pop, I'm just using it for the example, > >but it is all remote links behind this tnt including dial-up customers. > > > >I can not find anything wrong on the tnt. No fatal history, no t1 errors > >nothing. Only thing that fixes it is a reboot. > > > >I could really use some suggestions to trouble shoot the problem. This > >week I have had to reboot it twice already. Its like this ascend/lucent > >equipment has a built in "old age" death code..... > > > >I am reluctant to update code since the revision thats on it has been > >working flawlessly for almost 2 years. Prior to which we had to replace > >the chassis and shelf controller, because they died.... > > > >Help! Anyone. > > > >Thanks :) > > > >***************************************** > >Mick Dobra > >Systems Administrator > >MTCO Communications > >1-800-859-6826 > >***************************************** > > > >++ Ascend Users Mailing List ++ > >To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > >Archives: http://www.nexial.com/mailinglists/ > > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > ***************************************** Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 ***************************************** ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/