Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (ASCEND) 5.0Ai13 Fatal Error's



Not here, in fact I like p13 code so far:

action:sho uptime
system uptime: up 5 days, 17 hours, 30 minutes, 32 seconds
action:

We ran p5 previous to p13 with very long uptimes. OSPF was OK in p5 for
our use too. OSPF works fine in p13 (without STUBS of course)  This box
is part of a 12 max core group, and it get hit pretty hard:

SYSTEM IS UP:  Index: 100  Load: tim.m40 Revision: 5.0Ap5
        Date: 04/08/1997.       Time: 20:12:54

OPERATOR RESET:  Index: 99  Load: tim.m40 Revision: 5.0Ap5
        Date: 06/17/1997.       Time: 22:44:39
        NVRAMCLEAR Reset from unknown in security profile 1.

OPERATOR RESET:  Index: 99  Load: tik.m40 Revision: 5.0Ap13
        Date: 06/17/1997.       Time: 22:45:42
        NVRAM was rebuilt

The reset was from the software upgrade last week.  And like the bunny,
it's still goin'!

Best regards,

Dave Van Allen - You Tools Corporation/FASTNET(tm)
dave@fast.net (610)289-1100 http://www.fast.net
FASTNET - PA/NJ/DE Business Internet Solutions


>-----Original Message-----
>From:	Chris Fairbanks [SMTP:chrisf@winterlan.com]
>Sent:	Monday, June 23, 1997 2:34 PM
>To:	'ascend-users@bungi.com'
>Subject:	(ASCEND) 5.0Ai13 Fatal Error's
>
>I was wondering if anyone else has seen this problem.  As you can see
>from the fatal history, we were running 5.0Ap5.  The Max4000 was up for
>two months with out ever being down before the upgrade.  The reason we
>upgraded was to hopefully fix some weirdness we were seeing with OSPF,
>but so far all we have seen is a reboot about every other day.  
>
> 
>SYSTEM IS UP:  Index: 100  Load: ti.m40 Revision: 5.0Ap5
>        Date: 04/18/1997.       Time: 14:19:50
> 
>OPERATOR RESET:  Index: 99  Load: ti.m40 Revision: 5.0Ap5
>        Date: 06/18/1997.       Time: 13:36:38
>        NVRAMCLEAR Reset from unknown in security profile 1.
> 
>OPERATOR RESET:  Index: 99  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/18/1997.       Time: 13:37:50
>        NVRAM was rebuilt
> 
>SYSTEM IS UP:  Index: 100  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/18/1997.       Time: 13:38:35
> 
>SYSTEM IS UP:  Index: 100  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/18/1997.       Time: 13:39:54
> 
>FATAL ERROR:  Index: 1  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/19/1997.       Time: 11:55:54
>        Location: b00da2e0 b00da86c b01b1990 b004017c b00402a4 b0042068
> 
>SYSTEM IS UP:  Index: 100  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/19/1997.       Time: 11:57:21
> 
>FATAL ERROR:  Index: 1  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/21/1997.       Time: 09:43:22
>        Location: b00da2e0 b00da86c b01b1990 b004017c b00402a4 b0042068
> 
>SYSTEM IS UP:  Index: 100  Load: ti.m40 Revision: 5.0Ai13
>        Date: 06/21/1997.       Time: 09:44:49
> 
>
>=-=-=-=-=-=-=-=-=-=-=
>Chris R. Fairbanks
>Network Engineer
>
>WinterLAN, Inc.
>2910 Telegraph Ave.
>Berkeley, CA 94705
>Voice +1.510.486.1812
>Fax   +1.510.486.1796
>http://www.wli.net/
>
>
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
>or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>