> I'm about to switch from an hp937 on mpe 5.0 to an hp939 on mpe 5.5.
> The 939 will be a complete replacement of the 937, using the same ip
> address, dtc's etc. One of the things that need to be done is getting
> the dtc's now on the 937 to work with the 939.
> Is it possible to configure the dtc's into the nmconfig of the 939,
> and after shutdown of the 937 bootup the 939 and doing a
> sysdiag/termdsm reset on the dtc's to get them to "load" from the 939?
> I'm not sure you can reset a dtc that hasn't been "seen" before by the
> system. The problem is that the dtc's are located in an area where I
> don't have readily access to, so powercycling them is not an option,
> unless absolutely necessary.

A reset from the new machine won't work; once a DTC accepts a download from
a particular machine, it won't listen to anyone else. You can configure them
into the new machine, but they'll need to be powered off to get them to
download from it.

You can, however:
 1) issue the :SYSDIAG >TERMDSM reset dt x command from the old machine
 2) wait about 5 seconds
 3) disconnect the network cable from the old machine
 4) attach the network cable to the new machine

Depending on the DTC model, it will take from 20 seconds to maybe a minute
after the reset is issued before the DTC asks for a download. By taking the
old machine off-line and substituting the new machine in its place, that
download will come from the new machine. If you have several DTCs, you'll
probably have to repeat the sequence for each DTC. Also, after the reset
command, TERMDSM expects to receive a status back from the DTC, and it might
complain if it doesn't get one.


Steve Dirickson   WestWin Consulting
(360) 598-6111    [log in to unmask]