[HECnet] Nodelist errors from MIM::

[Steve Davidson]

Also,

It will skip your DECnet area so as NOT to damage the DECnet database of
clusters - if you chose to use DECnet as the transport.   That should not
normally be a problem because you are charged with managing your own
name and number space anyway.

-Steve 

-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::

Refresh my memory, how do I invoke that?

sampsa	<sampsa at mac.com>
mobile +358 40 7208932

On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:

Sampsa,

As long as your SCSSYSTEMID and your DECnet node number are in sync
you
can use NetUpdate from SGC:: or SG 

-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 2:57 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] Nodelist errors from MIM::

When I tried to update my nodelist just now on CHIMPY, I got a few
errors in Area 9.

Any ideas?

--- SNIP ----

CHIMPY$ mcr ncp copy known node from mim to both
%NCP-W-INVPVA, Invalid parameter value , Address



%NCP-W-INVPVA, Invalid parameter value , Address
Remote node =     9.1 (GEWT)


%NCP-W-INVPVA, Invalid parameter value , Address



%NCP-W-INVPVA, Invalid parameter value , Address
Remote node =     9.2 (MANDY)


%NCP-W-INVPVA, Invalid parameter value , Address



%NCP-W-INVPVA, Invalid parameter value , Address
Remote node =     9.4 (MINDY)