failSAFE IP fails to start

[Ziggy Filek]

I have Ethernet interface WE0 already configured with an address 10.171.2.7/24. I used TCPIP$CONFIG to configure interface WE1 with an address 10.171.2.23/24. TCPIP$CONFIG entered that into permanent configuration, but the interface was not immediately visible using $TCPIP SHOW INTERFACE. I therefore ran:
$TCPIP SET INTERFACE WE0 /host=10.171.2.23/network_mask=255.255.255.0
Now the interface would show up.
Then I defined an alias on it:
$ifconfig we1 alias 10.171.2.7
$ifconfig -a
. . .

WE0: flags=c43
*inet 10.171.2.7 netmask ffffff00 broadcast 10.171.2.255 ipmtu 1500

WE1: flags=c43
Standby addresses:
inet 10.171.2.7 netmask ffffff00 broadcast 10.171.2.255 (on HNAC WE0)
*inet 10.171.2.23 netmask ffffff00 broadcast 10.171.2.255 ipmtu 1500

I ran option 5 of TCPIP$CONFIG to enable and start failSAFE IP on this particular node. It seemingly worked fine, but I did not seem to see any TCPIP$FSAFE.. processes, so I tried the following:
HNAC..SYSTEM> @TCPIP$FAILSAFE_STARTUP
%TCPIP-I-SERVEXISTS, TCPIP$FAILSAFE already started
HNAC..SYSTEM> @TCPIP$FAILSAFE_SHUTDOWN
%TCPIP-I-SERVSTOPPED, FAILSAFE service already stopped
%TCPIP-I-INFO, service disabled
%TCPIP-I-INFO, logical names deleted
%TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$FAILSAFE.EXE deinstalled
%TCPIP-S-SHUTDONE, TCPIP$FAILSAFE shutdown completed
HNAC..SYSTEM>reply/enable
HNAC..SYSTEM> @TCPIP$FAILSAFE_STARTUP
%TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$FAILSAFE.EXE installed
%TCPIP-I-INFO, logical names created
%%%%%%%%%%% OPCOM 21-DEC-2006 13:51:38.98 %%%%%%%%%%%
Message from user INTERnet on HNAC
INTERnet ACP Activate FAILSAFE Server

%%%%%%%%%%% OPCOM 21-DEC-2006 13:51:38.98 %%%%%%%%%%%
Message from user INTERnet on HNAC
INTERnet ACP NOLISTEN Process creation success: Service - FAILSAFE

%TCPIP-I-INFO, service enabled
%TCPIP-S-STARTDONE, TCPIP$FAILSAFE startup completed
HNAC..SYSTEM>
%%%%%%%%%%% OPCOM 21-DEC-2006 13:51:39.04 %%%%%%%%%%%
Message from user INTERnet on HNAC
INTERnet ACP Error during process startup, Nolisten Service Disabled - FAILSAFE
Server

HNAC..SYSTEM>
%%%%%%%%%%% OPCOM 21-DEC-2006 13:51:39.04 %%%%%%%%%%%
Message from user INTERnet on HNAC
INTERnet ACP Deactivate FAILSAFE Server

HNAC..SYSTEM>

Please note, how it first complains about the service already being started, and then about service already being stopped.

This drives me crazy: I did not do anything against the documentation guidelines

Anybody has any ideas?

Thanks!

Ziggy

[David B Sneddon]

Since you made the changes using TCPIP$CONFIG,
have you rebooted -- I don't know if you can
do this stuff on-the-fly.

Dave

[Steven Schweda]

> [...] have you rebooted [?]

Stopping and starting the TCP/IP stuff
should be adequate. A complete reboot
should not be needed (but it should work,
too).

[David B Sneddon]

Stopping and starting the TCP/IP stuff
should be adequate. A complete reboot
should not be needed (but it should work,
too).


Whilst I agree that a reboot is a bit drastic,
I must confess to being less than impressed by
things of late -- especially TCP/IP stuff and
for something like this which is likely to be
seen as a major configuration change, I would
personally do a reboot.
(Purely personal opinion)

Dave

[Andy Bustamante]

What version of VMS and TCPIP are you running? Is your Alpha in a cluster? Are you running the dedicated lock manager?

$ show system /proc=LCKMGR_SERVER
$ TCPIP SHOW VERSION

There is an issue with failSAFE in TCPIP 5.4 and the dedicated lock manager. I have the fix running on top of ECO 5, this is probably in ECO 6 which is the latest patch kit for 5.4. The fix was availble in 2005.


Andy

[Mrityunjoy Kundu · Accepted solution]

Ziggy i think you follow the steps ---
at first you delete sys$system:tcpip*.dat which includes tcpip$configuration.dat,tcpip$host.dat,tcpip$network.dat,tcpip$proxy.dat,tcpip$route.dat and tcpip$service.dat. After that you run sys$manager:tcpip$config.com
It will open a MENU to configure CORE, Server, Clients and optional components.

TCP/IP Network Configuration Procedure
:
:
:
HP TCP/IP Services for OpenVMS Configuration Menu
:
:
:
Enter configuration option: 1

Select 1 for Core configuration. It will open a MENU

HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
:
:
Enter configuration option: 2

Select 2 to configure interfaces

INTERFACE Configuration

The Ethernet devices on your system are:⠦⠦.
:
Start of configuration questions for Internet interface IE0.
:
IE0 is the Ethernet device EIA0:
:
Enter configuration option: 1
Select 1 to configure manually.

Enter fully qualified host name: ABCXYZ

Enter Internet address: 10.172.2.7

Enter Internet network mask for ABCXYZ: 255.255.255.0

Enter broadcast mask for ABCXYZ: 10.255.255.255

The following parameters will be used to define the Internet interface IE0:
:
:
:
* Is this above correct [YES]: Y

Failsafe IP
:
:
:
* Configure failover target for failsafe IP [NO]: YES
:
Interfaces available for failover are:

IE1 IE2 IE3

Enter an interface for failSAFE IP: IE1

Interfaces available for failover are:

IE2 IE3

Enter an interface for failSAFE IP:

* Continue configuring interfaces for failSAFE IP [NO]: N
:
:
End of configuration questions for Internet interface IE0.
:

after that you run tcpip$shudown.com and then start the network with tcpip$startup.com

then the following command shows
$ifconfig -a
WE0: flags=c43
*inet 10.171.2.7 netmask ffffff00 broadcast 10.171.2.255 ipmtu 1500

WE1: flags=c43
Failsafe IP addresses:
inet 10.171.2.7 netmask ffffff00 broadcast 10.171.2.255 (on HNAC WE0)

Thanks

[Ziggy Filek]

Thank you everybody for your time. I managed to start the service without re-booting. The reason it would not start turned out to be quite prosaic... Whoever originally installed VMS turned the diskquota on the system disk. When I gave the user[TCPIP$FAILSAFE] 10k block quota with 50k overdraft it started to work. It needs approx 7,000 blocks to live. I figured it out, because the log files promised by the documentation weren't there and I guessed the reason. No system message whatever indicated a quota problem.

Once again, thank you guys for your help.

Ziggy