| Jordi,
I led the software effort that upgraded the DECagent 90 to Version 3.0.
I can't blame you for being disappointed in losing features. I don't
like to throw out functionality and reduce the number of modules that
can be managed, but the resources on the DECagent are very limited. It
is fixed with 512K of RAM, 256K of Flash, and 32K of non-volatile memory.
The purpose of the upgrade was to support the new MultiStack system,
and in particular to manage the new DECrepeater 90T-16. This software
had to be added on top of the existing code for managing in a DEChub
90, DEChub 900, and Standalone. And we had to continue managing the
existing products.
The Version 2.1 code used all but 16K of Flash. Into that 16K we would
have to place all the new functionality. Of course, it didn't all fit,
so we had to eliminate features that we felt were not absolutely
necessary. For example, with TFTP becoming an industry standard for
downline load of software, we decided it would be relatively safe to
remove the MOP downline load feature. It was a judgement call. By the
way, the final V3.0.1 image has just 195 bytes left in Flash! During
the development we had to go through several code reduction exercises.
There is NO spare room in that Flash.
Regarding the number of modules that can be managed, we are constrained
by two elements: the space in RAM to maintain cached status data, and
the space in non-volatile memory to save management sets through
resets. The DECrepeater 90T-16 significantly increased the amount of
status and management data per module, leaving us no choice but to
reduce the number of modules that could be managed.
My recommendation is the following: If you are using a DECagent 90 to
manage many remote communities through DECbridge 90s, or many
DECservers, use the V2.1 code. If your DECagent will be managing a
MultiStack or any DECrepeater 90T-16's in the local hub, use the V3.0
code. It is unfortunate that the agent can't do both jobs equally well
with one firmware image, but the fact is the agent is really being
called on to do far more than it was every designed to do!
Dave Walter
|
|
Thanks for your answer.
BUT this situation is extremely dangerous , I agree that releases notes
prevent everybody about restrictions, but you know that customer
usually don't read them and some of us neither.
Or other situation is when an agent should be swapped, the new one
comes from stockroom with latest firmware on it (the most of the
times).
What to do?
First I claim for firmware 2.1 on the net, just in case of a situation
as above.
Then, include in the HUBloader software utility a WARNING before
proceding with a DECagent90 upgrade.
My customers will appreciate this, and also my health.
Jordi Manchon
|
|
From: NETCAD::WALTER "08-May-1996 1702 -0400"
To: IB004::MANCHON
CC: NAC::FORREST,WALTER
Subj: RE: DECagent90 rev 2.1 on the net?
Jordi,
Currently, only Rev. 3.0.1 is publically available on ftp.digital.com.
I believe we can get Rev. 2.1 placed in an "old_firmware" directory,
but it won't happen immediately. In the meantime, you can copy Rev. 2.1
from the following VMS system:
NETCAD::PROJ$722:[ONEHUB.RELEASE.DENMA.V2_1]DENMA021.SYS
Regards,
Dave
|