Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 5.0Ap24 problems
I'm seeing this exact problem on one of my maxes as well. I have two
max4004's running 5.0Ap24. I'm also getting reports of users with static
ip's stating when they log on they can't get anywere and if they just wait
a few minutes, wella they are ok. Seems like it's taking the Maxes a while
to broadcast the route. I'm running OSPF with Rip tunred off.
SYSTEM IS UP: Index: 100 Load: tik.m40 Revision: 5.0Ap24
Date: 09/21/1997. Time: 01:33:30
WARNING: Index: 104 Load: tik.m40 Revision: 5.0Ap24
Date: 09/23/1997. Time: 12:41:29
Location: b017d170 b0076e78 b01a7dc8 b00cf948 b019e054 b005ab58
FATAL ERROR: Index: 8 Load: tik.m40 Revision: 5.0Ap24
Date: 09/23/1997. Time: 12:41:29
Location: b0092ad0 2e417400 b01a7e8c b00cf948 b019e054 b005ab58
SYSTEM IS UP: Index: 100 Load: tik.m40 Revision: 5.0Ap24
Date: 09/23/1997. Time: 12:44:15
OPERATOR RESET: Index: 99 Load: tik.m40 Revision: 5.0Ap24
Date: 09/23/1997. Time: 14:17:50
MENU Reset from unknown in security profile 1.
East County Internet Services, Inc
-Jess-
CFO
System Admin
On Wed, 24 Sep 1997, Jason Eggleston wrote:
> Hi,
>
> We have upgraded to 5.0Ap24 and are having some serious problems. We
> have to periodically reboot our MAX 2000 and MAX 4000, otherwise they
> stop accepting calls, or transmitting over ethernet.
>
> What should we do?
>
> Fatal log from MAX 4000: (the MAX 2000 didn't crash)
>
> FATAL ERROR: Index: 2 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 13:18:52
> Location: b01947bc b01357c8 b0047d6c b0056494 b0057bb4 b005473c
>
> SYSTEM IS UP: Index: 100 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 13:20:19
>
> WARNING: Index: 175 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 14:36:56
> Location: b0087260 b0128d84 b012fd04 b0127c0c b021a498 b00dfba8
>
> WARNING: Index: 175 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 14:38:27
> Location: b0087260 b0128d84 b012fd04 b0127c0c b021a498 b00dfba8
>
> FATAL ERROR: Index: 2 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 14:39:15
> Location: b01947bc b01357c8 b004d448 b004d078 b004cae8 b004ca74
>
> SYSTEM IS UP: Index: 100 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 14:40:41
>
> OPERATOR RESET: Index: 99 Load: tbi.m40 Revision: 5.0Ap13
> Date: 09/22/1997. Time: 21:02:13
> NVRAMCLEAR Reset from unknown in security profile 1.
>
> OPERATOR RESET: Index: 99 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/22/1997. Time: 21:03:39
> NVRAM was rebuilt
>
> SYSTEM IS UP: Index: 100 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/22/1997. Time: 21:04:38
>
> FATAL ERROR: Index: 29 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 09:45:06
> Location: b00417e8 b004194c b0088d18 00000000 b2807400 ffffffff
>
> SYSTEM IS UP: Index: 100 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 09:46:50
>
> WARNING: Index: 145 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 16:14:02
>
> OPERATOR RESET: Index: 99 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 16:14:52
> DEBUG Reset from unknown in security profile 1.
>
> SYSTEM IS UP: Index: 100 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 16:15:51
>
> FATAL ERROR: Index: 2 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 17:54:57
> Location: b0195d1c b0088a5c b0088a10 b01f2d24 b0088d18 00000000
>
> SYSTEM IS UP: Index: 100 Load: tbi.m40 Revision: 5.0Ap24
> Date: 09/23/1997. Time: 17:56:41
>
> --
> Jason Eggleston
> SysAdmin, Jet.Net Inc.
> ++ 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>
References: