Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Mickey Mouse coded 6.1
Here's a little tip....it may not be associated with your problem
whatsoever, however, this threw me for a loop a while back and it took
me weeks to find out the problem. No help from Ascend and after I
informed them that this might be happening to a lot of their customers
they just ok thanks for the info.
It seems that the max would reboot with msgs just like below because
our UPS would do a self test. Funny thing...I never figured out
exactly what has happening but I could recreate it by running a self
test on the UPS. Just food for thought.
On Mon, 8 Jun 1998 10:11:22 -0700, you wrote:
>AT least you got a fatal-error, look at this:
>
>SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.1.0
> Date: 05/31/1998. Time: 14:37:23
>
>SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 12:51:24
>
>It just rebooted itself Saturday afternoon for no reason, not
>even an error code. And it wasn't power - it is plugged into
>the same UPS as another Max and a Cisco router. Only reason
>I knew is one of my software probes sounded the alarm. And
>the box isn't overloaded either - granted it has 3 PRI's and
>a nailed T1 that leads to another Max, but the 3 PRI's are the
>last in our hunt group so only handle the overflow when the
>primary is busy at this POP. And the T1 leads to a brand new
>POP that has less then 10 users at any given time. Normally
>only 20-30 calls handled at any given time. It also has it's
>own dial number so we can use it as our experimental box -
>like testing 6.1.0. As you can see run time was just under 6
>days. If a light loaded box is behaving this way...NO WAY I am
>going to put it on our primaries!
>
>Kevin? Mitch? Why no response so far from Ascend on 6.1.0
>and it's severe instability compared to the beta code?
>
>Randy E. Reinhardt - System Administrator
>Fax:702-851-6115 Email:randy@pyramid.net
>Pyramid.Net http://www.pyramid.net/
>2701 Conestoga Dr. #123 Carson City, NV. 89706
>Technical Support Mon-Fri:9AM-8PM Sat:10AM-1PM
>Phone:702-853-4227 Email:support@pyramid.net
>
>
>-----Original Message-----
>From: owner-ascend-users@max.bungi.com
>[mailto:owner-ascend-users@max.bungi.com]On Behalf Of Jason Nealis
>Sent: Saturday, June 06, 1998 8:37 PM
>To: ascend-users@bungi.com
>Subject: (ASCEND) Mickey Mouse coded 6.1
>
>
>
> Fellow Ascenders'
>
>Tonight things BLEW UP, In just a span of 45 minutes I had 4 boxes in
>all different sites, all in the front of the hunt group, All running
>6.1 reboot with errors.
>
>Look at a sample from this one box, It had a very rough time :
>
>FAT LOG
>-------
>
>SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.1.0
> Date: 06/04/1998. Time: 05:41:11
>
>WARNING: Index: 140 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 09:01:39
> Location: b001c944 b001cbfc b001cc1c b0055e20 b0056150 b0059368
>
>FATAL ERROR: Index: 8 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 18:33:46
> Location: b0062f74 1bb81bb8 b00123d4 b004bca4 00000000 00000000
>
>SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 18:36:57
>
>WARNING: Index: 175 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 21:46:19
> Location: b004a90c b00ce044 b00c630c b01753e4 b009acc8 b009998c
>
>WARNING: Index: 175 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 21:46:19
> Location: b004a90c b00c7428 b00ce078 b00c630c b01753e4 b009acc8
>
>WARNING: Index: 175 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 21:46:19
> Location: b004a90c b00c7428 b00ce078 b00c630c b01753e4 b009acc8
>
>WARNING: Index: 140 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 21:46:19
> Location: b001c944 b001cbfc b001cc1c b00d18b0 b0104fa8 b011712c
>
>FATAL ERROR: Index: 29 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 21:47:12
> Location: b0052c00 b0053130 b00593d0 b0059564 b0095970 b0095f24
>
>SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.1.0
> Date: 06/06/1998. Time: 21:50:23
>
>
>Let's count those up :Warning 140 , Warning 175 , Fatal 8 , Fatal 29.
>
>How can this escape regression testing? Does Ascend drug test? maybe it's
>time to pass the cup around the regression test lab, What really bothers
>me is I never saw any of these error in the private beta I participated
>in. What's the point of having a beta if you are going to change the code
>after before release?
>
>Jason Nealis
>Director Internet Operations / Network Access
>Erols Internet (An RCN Company)
>
>
>
>++ 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>
++ 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: