Guys. Im having some problems with an e1 card.... Shelf 1 slot 4 on e1 8 is going up and down..... Jan 5 20:27:14 200.52.83.195 1/4: Line 8 down Jan 5 20:27:16 200.52.83.195 1/4: Line 8 up Jan 5 20:27:20 200.52.83.195 1/4: Line 8 down Jan 5 20:27:26 200.52.83.195 1/4: Line 8 up Jan 5 20:27:31 200.52.83.195 1/4: Line 8 down Jan 5 20:27:33 200.52.83.195 1/4: Line 8 up Jan 5 20:27:42 200.52.83.195 1/4: Line 8 down Jan 5 20:27:44 200.52.83.195 1/4: Line 8 up Jan 5 20:27:50 200.52.83.195 1/4: Line 8 down Jan 5 20:28:01 200.52.83.195 1/4: Line 8 up Jan 5 20:28:06 200.52.83.195 1/4: Line 8 down Jan 5 20:28:09 200.52.83.195 1/4: Line 8 up Jan 5 20:28:17 200.52.83.195 1/4: Line 8 down Jan 5 20:28:20 200.52.83.195 1/4: Line 8 up Jan 5 20:28:27 200.52.83.195 1/4: Line 8 down Is there any way to trace this error back??? The media (e1) is ok so its something on the tnt.. It start doing it without config changes. Also, one more question... How can I -d or -u a particular e1 on a slot? And not the whole slot -d or -u? and how do I backup my entire tnt config??? And restore? Thx for all the help guys!! Saludos Anton Krall Director de Tecnología Inter.net México / Panamá Tel; 5241-7609 Directo Tel: 5241-7600 Conmutador Celular: 0445-105-5160 Mobile ICQ: 4979450 email: akrall at team.inter.net web: http://www.mx.inter.net Outside Mexico: Office: +52(555)241-7609 PBX: +52(555)241-7600 Mobile: +52(555)105-5160 Original > -----Original Message----- Original > From: owner-ascend-users at max.bungi.com Original > [mailto:owner-ascend-users at max.bungi.com] On Behalf Original > Of Simon Byrnand Original > Sent: Jueves, 03 de Enero de 2002 02:35 p.m. Original > To: cclements at cp-tel.net; ascend-users at max.bungi.com Original > Subject: Re: [Ascend] (ASCEND) Dial connect, then Original > instant disconnect. Original > Original > Original > At 10:48 3/01/02 -0600, Chris Clements wrote: Original > Original > >Max users, Original > > Original > > We have had some intermittent problems with Original > dial-in users connecting, Original > >authenticating, then instantly disconnecting. Is Original > there some facility Original > >in the max for logging this type of problem? What Original > could be some Original > >possible causes of this? Original > Original > Hi Chris, Original > Original > You could try enabling remote loging to a **ix box Original > and look at those logs, they're pretty detailed. (In Original > fact they're probably too verbose) On a MAX6000 its Original > under Ethernet -> Mod Config -> Log, enable Syslog, Original > Host is your **ix box, Port should be 514, and set Original > facility to something like Local0 that isn't used Original > already on the box that will be logging. Original > Original > You'll then have to enable remote reception on the Original > syslog daemon (just add -r to the startup command Original > line option in the Linux version) and add some Original > syslog.conf entries to catch local0, save them in a Original > seperate file (I used Original > /var/log/max.log) and prevent them from getting Original > logged into your mail /var/log/messages. (It would Original > probably pay to firewall port 514 to only allow Original > packets from your NAS, so other people cant send Original > your syslog daemon Original > junk) Original > Original > Or if you use radius, you can tail the detail file Original > for the NAS and watch out for Stop records for that Original > user and see what the disconnect cause is. Original > Original > Regards, Original > Simon Original > Original > Original > ++ Ascend Users Mailing List ++ Original > To unsubscribe: send unsubscribe to Original > ascend-users-request at bungi.com Original > Archives: http://www.nexial.com/mailinglists/ Original > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/