Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
re: (ASCEND) tnt error
As for your LOG error indicating that it Can't read debug profile, there is
no problem and they just started showing up in the 2.x flavor for the TNT.
To make these errors go away, create a new debug profile for each card and
slot. To do this just login to the TNT with system rights and run "new
debug". A new debug profile will be read and you can then configure it for
a specific card and slot. Don't forget to write the new debug profile once
it has been modified.
As for the routing issue. Did you change any of your routing parameters?
The TNT will cache routes as it learns of them. If something changes, the
TNT will stumble a bit until it can refresh its cache. Usually, if I ever
do something that will affect the route table, I immediately followup with
a TNT reset.
Hope this helps.
Mitch
Semper Fi!
-------------
Original Text
From: Jesse Martinez <jmartine@ecis.com>, on 4/15/98 4:58 PM:
To: <ascend-users@bungi.com>
I just upgraded to 2.0.3 on my TNT and got this error after restoring
my config file via tftp.
----------------------------------------------------------------------------
----
LOG error, Shelf 1, Slot 2, Time: 20:27:44--
Can't read debug profile for 1/2
LOG error, Shelf 1, Slot 16, Time: 20:27:48--
Can't read debug profile for 1/16
The TNT would'nt route IP for about 20 minutes then it was flacky. I had
to reconfigure another port on the T1 card to get it to stablelize.
Any ideas.
-Jesse Martinez-
CEO
East County Internet Services, Inc.
Voice (925)706-4280
Fax (925)706-4282
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
_
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>