Operating System - OpenVMS
1832585 Members
3396 Online
110043 Solutions
New Discussion

Re: NIC not connected was the most problem

 
Lachnitt_1
Frequent Advisor

NIC not connected was the most problem

@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
3 REPLIES 3
Keith Parris
Trusted Contributor

Re: NIC not connected was the most problem

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. :-)
Uwe Zessin
Honored Contributor

Re: NIC not connected was the most problem

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.
.
Lachnitt_1
Frequent Advisor

Re: NIC not connected was the most problem

closed