DECnet Device Pt. 2
BrianNFO
DECnet, the following came up mixed in with the usual DECnet startup
messages...
%NCP-W-INVPVA, Invalid parameter value , Physical address
Line = ISA-0
%NCP-W-UNRCMP, Unrecognized component , Circuit
Circuit = ISA-0
So, something is still missing. Thoughts? I know the device, EZA0 is
functioning fine...Multinet is using it, and I can Telnet to the box.
On related note, I'm trying to recall which driver needs to be loaded to allow
you to do a CONNECT NODE from NCP to a terminal server.
Thanks.
Brian
Hoff Hoffman
In article <20000323143833...@ng-de1.aol.com>, bria...@aol.com (BrianNFO) writes:
:Well, I did as everyone suggested, and let netconfig run. Upon starting
:DECnet, the following came up mixed in with the usual DECnet startup
:messages...
:
:%NCP-W-INVPVA, Invalid parameter value , Physical address
:Line = ISA-0
:
:%NCP-W-UNRCMP, Unrecognized component , Circuit
:Circuit = ISA-0
:
:So, something is still missing. Thoughts? I know the device, EZA0 is
:functioning fine...Multinet is using it, and I can Telnet to the box.
You are likely having problems because you are running DECnet Phase
IV and are now trying to change the controller address -- after other
applications have accessed the controller. Now that you need to change
the address, either shut everything down that is trying to use the
controller and restart it, or (simpler) reboot the system. DECnet-Plus
does not require the controller address change -- which solves several
problems including this one...
:On related note, I'm trying to recall which driver needs to be loaded
:to allow you to do a CONNECT NODE from NCP to a terminal server.
What command are you using?
What error are you getting?
FYDRIVER is the usual culprit for SET HOST/DUP, but I was not
aware of any particular driver needed for MOP operations in NCP.
On OpenVMS V6.2 and later, seriously consider the use of LANCP
for MOP operations.
--------------------------- pure personal opinion ---------------------------
Hoff (Stephen) Hoffman OpenVMS Engineering hoffman#xdelta.zko.dec.com
Mark Berryman
>
> Well, I did as everyone suggested, and let netconfig run. Upon starting
> DECnet, the following came up mixed in with the usual DECnet startup
> messages...
>
> %NCP-W-INVPVA, Invalid parameter value , Physical address
> Line = ISA-0
This error means that DECnet is trying to set the MAC address of the
ethernet interface to a DECnet-specific value and failing. This failure
is almost always caused by the fact that some other protocol is already
using the interface in question.
You must either start DECnet first, or make sure that any protocols
started before DECnet are aware that DECnet is going to be running and
perform the MAC address change themselves (both Multinet and LAT have
this ability, for example).
If you want to start DECnet without rebooting and the MAC address has
not already been changed (the changed MAC address will be in the form of
AA-00-04-00-xx-xx) you must first shutdown any protocols already using
the interface before DECnet will start.
> %NCP-W-UNRCMP, Unrecognized component , Circuit
> Circuit = ISA-0
This error is most likely a result of the first error.
> On related note, I'm trying to recall which driver needs to be loaded to
> allow you to do a CONNECT NODE from NCP to a terminal server.
No additional driver is necesary. MOP console is available as soon as
DECnet is running (MOP download, however, requires some configuring -
even then no additional drivers are needed).
Mark Berryman
Mark.B...@Mvb.Saic.Com
Karl Rohwedder
BrianNFO wrote:
>
> Well, I did as everyone suggested, and let netconfig run. Upon starting
> DECnet, the following came up mixed in with the usual DECnet startup
> messages...
>
> %NCP-W-INVPVA, Invalid parameter value , Physical address
> Line = ISA-0
>
> %NCP-W-UNRCMP, Unrecognized component , Circuit
> Circuit = ISA-0
>
> So, something is still missing. Thoughts? I know the device, EZA0 is
> functioning fine...Multinet is using it, and I can Telnet to the box.
>
> On related note, I'm trying to recall which driver needs to be loaded to allow
> you to do a CONNECT NODE from NCP to a terminal server.
>
> Thanks.
>
> Brian
Hi Brian,
it looks, as if you've started another network protocol before
starting DECnet, always
start DECnet 1st, then TCPIP and/or LAT ...
--
mit freundlichen Gruessen | with best regards
Karl Rohwedder
iT-Ingenieurteam | Ellernbruch 11 | D-38112 Braunschweig
Telefon: 0531/515521 | Telefax: 0531/515531 | Mobil: 0172/5434843
E-Mail: rohw...@decus.decus.de | iT-In...@t-online.de
karl.ro...@it-ingenieurteam.de
DATEX-P: 4505018005::ROHWEDDER
steven...@quintiles.com
Karl Rohwedder (extern dot karl dot rohwedder at volkswagen dot de) wrote:
>it looks, as if you've started another network protocol before
>starting DECnet, always
>start DECnet 1st, then TCPIP and/or LAT ...
Contrary to popular belief, you can legally and effectively start LAT before
DECnet with DECnet phase IV.
This allows you to connect to a box via LAT if DECnet startup has blown up with
multiple errors and prevented the full startup sequence running. (Things are
obviously different in DECnet-Plus since the DECnet startup is part of the
initial start that's run before systartup_vms is processed).
Steve.
Hoff Hoffman
In article <802568AC.0...@qedilc01.qedi.quintiles.com>, steven...@quintiles.com writes:
:Contrary to popular belief, you can legally and effectively start LAT before
:DECnet with DECnet phase IV.
Depending on the LAT software version... Older LAT versions (those in
V5.5 and earlier; those versions using the FFI and not the VCI network
driver interface) are quite unable to permit DECnet Phase IV to change
the controller address, but later versions of various products including
LAT can better tolerate this. A workaround is the use of the CREATE LINK
/[NO]DECNET stuff, and to keep SCSSYSTEMID set correctly. (And some
people wonder why I always ask for the version number information. :-)
Antonio Carlini
>multiple errors and prevented the full startup sequence running. (Things are
>obviously different in DECnet-Plus since the DECnet startup is part of the
>initial start that's run before systartup_vms is processed).
Contrary to popular belief :-) you can play with logicals and stop DECnet-Plus
from starting up.
$ DEFINE/SYS/EXEC NET$IGNORE_DECNET TRUE
in SYLOGICALS.COM will prevent DECnet-Plus from being fired up automatically.
Then you can fire it up later in the startup, when you are good and ready.
Antonio
Antonio Carlini Mail: car...@true.lkg.dec.com
DECnet-Plus for OpenVMS Engineering
COMPAQ Reading, UK