Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Release 6.1.7
On Fri, 2 Oct 1998, Richard Johnsson wrote:
> Thanks for the info. I, too, have had very good luck with 6.1b2 (uptime 124
> days now) and have been reluctant to move to a production release. I guess
> I'll just stay with the beta until I need something new.
>
> At 09:16 AM 10/2/98 -0400, Jim Howard wrote:
> >At 16:27 1998/09/30 +0200, Sándor FülöpbPZw wrote:
> >>I want to get the 56k up to V.90, which is the most stable software that is
> >>v.90 capable.
> >
> >I use OSPF, no stacking, mixed ISDN and modems.
> >I had very good experiences with 6.1b2, and IMHO you don't want
> >to even think about 6.0.x or earlier...
> >I had bad experiences with 6.1.3, so I upgraded to 6.1.7
> >which was even worse (crashing every day, or every other day)
> >
> >so I moved up to 7.0b4 on the first 4048 in my hunt group
> >last thursday, and have not had a single problem since.
> >I will be upgrading all my boxes now to 7.0b4.
> >
> >OPERATOR RESET: Index: 99 Load: ftik.m40 Revision: 7.0b4
> > Date: 09/23/1998. Time: 13:28:06
> > NVRAM was rebuilt
> >
> >SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 7.0b4
> > Date: 09/23/1998. Time: 13:29:28
> >
> >ascend% sh up
> >system uptime: up 8 days, 18 hours, 44 minutes, 49 seconds
The only problem I have seen with 6.1.7 in my environment (Max6000, E1
PRI, RIP-v2 send only, very limited stacking, mixed ISDN/Analog) is that
two boxes locked out the D-channel on one of their PRIs after about 14
days uptime. Rebooting the box sorted it.
Otherwise it's been fine.
I have also been running the 7.0b tree on a public testing box (another
Max6000 separate from the main pool), and 7.0b6 is looking good at the
moment (touch wood).
Mike
++ 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: