topic NIC not connected was the most problem in Operating System - OpenVMS

NIC not connected was the most problem

Lachnitt_1 — Wed, 28 Apr 2004 02:04:55 GMT

@All

The most problem was that the Interfaces, that i tried to configure in the Failoverset wasn't connected to the LAN.
And it seems that they will not be added, if they aren't connected.
I tried it with the connected EWA0 (a unsupported DE500) and it appears immediately after reboot!!!

So i'm continuing to configure it.
Thx at all for help.

Bye, Kuddel

Re: NIC not connected was the most problem

Keith Parris — Thu, 29 Apr 2004 09:55:16 GMT

I'm glad you got it working.

And I know it's far too easy to click on the "New Message" button in ITRC Forums when you really meant the "Reply" button. :-)

Re: NIC not connected was the most problem

Uwe Zessin — Thu, 29 Apr 2004 10:30:39 GMT

Ah, that is good to know - thanks for the info. Sometime it is an easy cause - 'did you plug it in?'.

I guess it is a good idea to implement a check of the failover setup at least after system boot. Otherwise a single failure gets unnoticed due to redundancy.

Does anybody know if it is possible to get at this information via $GETDVI? I have taken a short look at the arguments of F$GETDVI, but I did not see anything useful.

Re: NIC not connected was the most problem

Lachnitt_1 — Thu, 07 Oct 2004 03:50:22 GMT

closed