| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2003.1 | Trigger the load from NCP | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Feb 13 1995 14:19 | 17 |
| Since you are able to NCP CONNECT to the bridges with V1.5 code, I'd say the
best thing to do is to just trigger a load from NCP directly. You need to
enable circuit service and then perform the load. Here's an example of the
commands that work for me:
$ NCP
NCP>set circuit qna-0 state off
NCP>set circuit qna-0 service ENABLE
NCP>set circuit qna-0 state on
NCP>load via qna-0 physical address 08-00-2b-2f-fd-57 from mom$load:dewgb310.sys
NCP>exit ^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
bridge's MAC addr. load file name
Note: make sure that the bridge does not have a password set or the above will
not work.
...Roger...
|
| 2003.2 | Thanks - I will give it a try | SVCVAX::GAMBARDELLA | Gamby Gumba | Mon Feb 13 1995 18:21 | 19 |
| Thanks, I will give that a try when I go out there this Friday. The customer
had some problems in the past updating firmware on 90 modules and will not
allow me to do try this until off hours and with a spare module in hand. I
also obtained a copy of flash.exe in case the bridge burbs in the middle of the
load - so I should be all set.
>>>NCP>load via qna-0 phys address 08-00-2b-2f-fd-57 from mom$load:dewgb310.sys
>>>NCP>exit ^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
>>> bridge's MAC addr. load file name
I never used this command before - I thought I would have to assign each
bridge a node name and decnet address to get the image loaded. This will
definitely save me some time.
Mike..
|
| 2003.3 | Get the mystery V3.9 release if possible | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Feb 14 1995 09:38 | 11 |
| Mike, since you need to upgrade the bridges anyway, you might want to consider
surfing through this conference for information about new DEWGB (and DEWGF)
firmware. There is a V3.9 available somewhere, but the folks who made the
changes and released the image have managed to keep its location a well-kept
secret, even from us engineering types.
FYI, you can certainly go through the excerise of assigning each bridge a DECnet
node name and address in order to load it. That's the "documented way" (heck, I
wrote the document!) but who reads documentation? :-)
...Roger...
|
| 2003.4 | | NPSS::JOHNSON | Mike J., Network Products Support | Tue Feb 14 1995 15:26 | 13 |
| Sorry Roger,
I thought we gave you a version at the same time NSTG got it for evaluation.
Anyway, starting with the obligatory message that the pointer being provided
here-with is for internal use only and we should all do our part to improve the
profitability of SSB by ordering "official" copies from them....
Copies of BOTH the release notes and the .TSK file can be found at:
NPSS::PUBLIC$DSK:[INTERCHANGE.DEWGB]
/mj
|
| 2003.5 | What to do with .TSK file | SVCVAX::GAMBARDELLA | Gamby Gumba | Wed Feb 15 1995 09:41 | 12 |
| OK - I would like to upgrade upgrade the bridges to the latest rev, so I
copied over the release notes and the .TSK files. However after reading
through the release notes I am not sure what to do with the .TSK file. I was
expecting a .SYS file. Do I have to compile the .TSK file first?
And more importantly - should I use this firmware at a customers site? I did a
directory of the public firmware directory @ftp.digital.com and it shows v3.1
as the latest version. I do not want to put an unsupported version at this
customers site.
...Mike
|
| 2003.6 | TSK :== SYS :== BIN | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Feb 15 1995 13:00 | 17 |
| You can load the TSK file just like a SYS or BIN file. Use NCP LOAD/TRIGGER or
DECndu Plus.
I'll let Mike respond to the question of "can I give V3.9 to my customer?"
(although I think he did that in .4). The V3.9 code will be included in the
next wave of hub firmware (provided we get the blessing of system test, etc.).
Incidentally, we will be standardizing the naming convention for all binary
firmware images distributed in the DEChub Consolidated Firmware Kit for the next
wave. Currently the DECagent 90 and DECbridge 90/90FL firmware images are SYS
files (and as you can see, Mike is releasing a new bridge image that is a TSK
file). For the next release of the firmware kit, all files will be BIN files as
there will be a new version of both the DECagent 90 and DECbridge 90 firmware.
The only exception will be the DECpacketprobe 90 firmware (it isn't a binary
file but a Motorola S-record file).
...Roger...
|