On Sun, 28 Mar 1999 21:34:21 GMT, [log in to unmask] (Danny A. van Delft)
wrote:

>Hi,
>
>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.
>
>TIA
>
>Danny A. van Delft   [log in to unmask]


Thank for all the replies, also for the emailed ones.

By the way, the DTC's are a mix of DTC48, DTC16, and DTC16/iX in
nmconfig parlance.

I had thought about pulling the network cable from the 937 just after
reset but thought there might be a more "elegant" way to do it. As I
had nothing to lose I just tried the following:
- configure the dtc's into the nmconfig of the 939, choose NOT to
effect the changes immediately.
- reboot the 939
- go into sysdiag > termdsm and, yes, reset a DTC.

Guess what happened: The DTC was reset, there was the "download
started for DTC ..." message on the console of the 939, but, suprise,
suprise, also on the console of the 937. After the usual delay the 939
declared a succesful load of the DTC, while the 937 complained after a
while: "download aborted". I repeated the process for the other dtc's
and they all loaded succesful from the 939.

Well, I might have been lucky, perhaps the 939 beat the 937 in
responding to the download request, but perhaps the dtc only listened
to the originating MAC address. Don't know, don't really care, but
willing to learn if someone has the answer. It makes you wonder
though, this is a potential security risc: anyone with a HP3000 and
knowledge of the DTC addresses can pull the rug under the legitimate
HP3000. Farfetched, I know.

In retrospect, I shouldn't have been suprised by the download started
message on the 937, as the dtc was also known (of course) to this
system.

Anyway, it shows that a DTC doesn't have to have been loaded by a
particular system for SYSDIAG>TERMDSM to be able to reset it.

Once again, thanks for the prompt replies.
Danny A. van Delft   [log in to unmask]