| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1736.1 | Need to enable circuit service on the VAX | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Nov 29 1994 20:54 | 21 |
| Check the following:
$ NCP SHOW KNOWN CIRCUITS CHAR
You must have "Service = enabled" in order for the VAX to respond to the load
request. If you do not, do the following (assume network circuit is QNA-0):
$ MCR NCP
NCP>SET CIRCUIT QNA-0 STATE OFF
NCP>SET CIRCUIT QNA-0 SERVICE ENABLE
NCP>SET CIRCUIT QNA-0 STATE ON
NCP>EXIT
NOTE: This will temporarily disconnect you from the network, so (1) do it quick
or, (2) put the above commands in a command file and execute (@) it. I do this
all the time and never lose network connectivity.
I think you already know this, but REPLY/ENABLE=NET does not enable the network
service. It only enables the logging of OPCOM messages to the VAX console.
...Roger...
|
| 1736.2 | additional information | TENNIS::KAM | Kam USDS (714)261-4133 (DTN 535) IVO | Wed Nov 30 1994 14:07 | 41 |
| I believe it is and here is the files in MOM$LOAD. Everything looks
correct. Am I missing something?
Regards,
kam
Circuit Volatile Characteristics as of 30-NOV-1994 08:00:16
Circuit = QNA-0
State = on
Service = enabled
Designated router = 16.1018 (IVONI2)
Cost = 4
Maximum routers allowed = 33
Router priority = 2
Hello timer = 15
Type = Ethernet
Adjacent node = 16.183 (BALBOA)
Listen timer = 45
Directory SYS$COMMON:[MOM$SYSTEM]
DENMA.NDU_SCRIPT;1 DENMA021.RELEASE_NOTES;1 DENMA021.SYS;2
DENMA021.SYS;1 DENMA_LOAD.SYS;1 DEWGB310.SYS;1 READ_ADDR.SYS;1
Total of 7 files.
>I think you already know this, but REPLY/ENABLE=NET does not enable the network
>service. It only enables the logging of OPCOM messages to the VAX console.
Shouldn't I be able to see the request and the results of that request?
When I boot satelites I do.
Regards,
kam
|
| 1736.3 | still no luck | TENNIS::KAM | Kam USDS (714)261-4133 (DTN 535) IVO | Wed Nov 30 1994 15:45 | 11 |
| Does the device have to be set back to the factory default e.g., NO
PASSWORD? I tried that and it didn't appear to work.
At the CCI prompt when I do a load DENMA_LOAD.SYS shouldn't I see a MOM
request?
Maybe my device is defective.
Regards,
kam
|
| 1736.4 | Strange problem ... let's see what the ROM version is | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Nov 30 1994 16:40 | 38 |
| The console password has no effect on the downline load process, so a
reset-to-factory is not required.
You should see the request at the VAX console when it is issued by the DECagent.
However, this does not happen immediately after the LOAD DENMA_LOAD.SYS command
is issued. The DECagent first requests an IEEE ISO8802 load (please don't ask,
it's just the way it was implemented in the ROM code). Then after 10 seconds or
so, it attempts an Ethernet load. At this point, if your VAX is configured to
accept requests (which is looks like it is) you should see the message on the
VAX console that a request has been made by the DECagent.
According to your base note, it does not seem to be getting beyond the ISO8802
load request. I am not sure why. Are you sure the network connection is OK?
DEChub 90 has a terminator on the side of the hub, etc. etc.? I have never seen
a case where it did not at least attempt an Ethernet load after the ISO8802 load.
Here is what a successful load should look like:
CCI>load denma_load.sys
DENMA -901- Initializing DECagent 90.
DENMA -953- Attempting to locate load host
[ISO8802]
DENMA -953- Attempting to locate load host
[ETHERNET]
DENMA -955- Host AA-00-04-00-B1-F0 located [ETHERNET]
DENMA -956- Requesting load from host AA-00-04-00-B1-F0
DENMA -903- Loading from host AA-00-04-00-B1-F0
DENMA -904- Image verification in progress.
DENMA -905- Image load completed.
%CCI-I-CRCCHK,attempting CRC check on image loaded
CCI>
One last thing. Can you tell me what the output of the CCI> SHOW SERVER command
says on this DECagent?
...Roger...
|
| 1736.5 | I conclude that the device is defective | TENNIS::KAM | Kam USDS (714)261-4133 (DTN 535) IVO | Wed Nov 30 1994 17:35 | 23 |
| CCI> show server provides the following in abbreviated format:
current hardware revision D01
current LANCE revision F
current romcode revision BL05.00
Something must be wrong with the DECagent 90. I borrow a DECagent 90
from the IS folks locally. However, there firmware was at V1.1. So I
didn't need step 1.4 e.g., load denma_load.sys. At NCP I just did a
LOAD NODE DENMA and after a few brain dead mistakes on my part it worked
and provided the menus according to the on-line documentation.
My conclusion is that I purchased this from Bill Seavers in November
1992 and I believe that it must of been an Engineering prototype or
something. In most cases it works but not the downloading. I'm trying
to get the local FS to replace it.
I don't think it's me and it's got to be the device.
Thanks for the support.
Regards,
kam
|
| 1736.6 | May be too late, but... | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Dec 19 1994 16:27 | 6 |
| To follow up on this note and note 1794, I had one other thought. Is it
possible that there is a bridge located between the DECagent and the load host
that is filtering the MOP protocol (60-01 and 60-02)? That's my last-ditch
guess as to why the load host would not be responding to the load requests.
...Roger...
|