T.R | Title | User | Personal Name | Date | Lines |
---|
300.1 | From the devos... | QUIVER::GAUDET | | Wed Jul 14 1993 10:22 | 17 |
| .0>> HW=XXX ROM=BLxx.xx SW=V1.1
This means that for obscure reasons the version information which is
stored in the NVRAM of the DECagent has been stepped on. There's a
couple of ways to correct the problem. The right way is to run the
manufacturing Final Quality Check (FQC) procedure from CCI to reload
the version information. Unfortunately, this will run all the
diagnostics and blow away any information you may have stored in NVRAM,
as well as reload the flash image. It also requires that a special
data file be present on a load host. The second way is a huge hack, so
I'd prefer to refrain from going into detail here about how to do this.
Contact me offline if you want more information.
BTW, there's no reason why a bogus DECagent version string should have
any effect on the ability to talk to the bridge.
...Roger...
|
300.2 | HW=XXX ROM=BLxx.xx SW=V1.1 | WARHED::NAEEM | | Wed Jul 14 1993 13:14 | 6 |
| I have two Decagent and they display HW=XXX ROM=BLxx.xx SW=V1.1.I have
Problem with both of them.This morning I got hold of another Agent
that displayed HW=D01 ROM=Bl05.00 SW=V1.0.I upgraded it to SW V1.1 & I
can talk to it from HUBWATCH(Windows & Ultrix).Where as I have problem
with the other two.
[End
|
300.3 | Try a factory reset | LEVERS::BENSON | DTN 227-3555 | Fri Jul 16 1993 12:21 | 2 |
| A factory reset will clean up the NVRAM (except for the HW and ROM
revisions). That will probably solve your problems.
|
300.4 | Decagent 90 HW=? & ROM=? | WARHED::NAEEM | | Tue Jul 20 1993 09:38 | 5 |
|
A Factory reset did not fix it.
Roger Gaudet privide ,know how, to fix this problem.
Thanks to roger.
Naeem.
|
300.5 | Please let me know if this happens to you | QUIVER::GAUDET | | Tue Jul 20 1993 12:03 | 6 |
| If anyone else experiences what Naeem saw with the HW and ROM versions,
I'd like to hear about it. I honestly can't think of a good reason why
having bogus version information would cause HUBwatch to be unable to
talk to the agent.
...Roger...
|