Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 6.1.7 Microcode for Max
My brief experience with 6.1.7 on a 4000 was short and rather unpleasnt.
Max 4000
6 Mod-8 V.35 Modem Cards
No stack
2 PRI lines NI-2 through a 5ESS
Load: 6.1.7 fti.m40
Upgraded from: 6.1.3 fti.m40
Results.
As soon as the Max 4000 finished booting I started getting
Lan Security Errors out the wazoo. I also rececieved
in debug mode 10 of these:
MODEMDRV-4/6: Write failed at 3E397EFE, wrote 2c, read 2d
My radius server started erroring out with:
"Authenticate: i21025, id=101: No User Name"
I reloaded 6.1.3 and everything stabilized again. This Max 4000
had running 6.1.3 for 36 days before I attempted to load 6.1.7.
The reason for the upgrade was that we were getting random
reports of connection problems. We had no memory problems and
no IP pool leaks.
My experience with 6.1.7 on Max 1800s is peachy. There has been
no problems on the 5 1800s running 6.1.7. None of these 1800s running
6.1.7 have modem cards. Load: fbi.m18. The only problem we had
had was that originally we were told by Ascend Tech support to leave
the Directory # blank. As of V.6 point something, it is now required to
enter the Directory # to make a multi-line hunt group work. These are
used for Data calls only.
We have 1 Max 1800 with a 8 mod K56Flex modem pack. It is running
6.1.0 load: fbik.m18. No problems that I am aware here either of either.
Used for Analog calls only.
We have 1 Max 2000 with 2 12 mod K56Flex modem packs. It is also
running 6.1.0 load ftik.m20. No problems with it either that I am aware
of.
>From what I have read and my brief experience, if you are planning on 6.1.7
on a 4000, give yourself a root cannel with a Dremel tool instead. Thanks
again Ascend for another wonderful TAOS.
Mark E. Dunlap
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>