TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908 (1392 Views)
Reply
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 1 of 13 (1,392 Views)
Accepted Solution

TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Last weekend we did an upgrade from OpenVMS 8.2 to 8.3 on an Alpha Cluster (2x ES47, 4x DS25, 1x AS400).

The cluster uses 2 system disks for SAN-boot and the AS400 (quorum node) uses its own local system disk.

After the upgrade we installed all available Patches including the ones for TCP/IP. Everything was done independently on the two SAN system disks and the quorums boot disk.

Everything looked well until we got to the point to start TCP/IP. There we found the following messages:

...

%TCPIP-I-DEFINTE, defining Interfaces

ioctl failed: status = 908

ifconfig: no such interface LE0

%SYSTEM-W-NOSUCHDEV, no such device available

%TCPIP-S-STARTDONE, TCP/IP Kernel startup complete

...

 

Doing a 'tcpip> show interface' only showed up LO0, whereas 'tcpip> show config interface' still showed the config for LO0, LE0 and WE1 as expected.

 

The failover Interface LLA0 which corresponds to LE0 and consists of EWA0 and EWC0 is still available in the system.

The symptoms look the same on all cluster nodes. None of the systems was able to start le0 and we1 TCPIP Interfaces.

 

Is there a known problem with such a config / upgrade ?

 

Since we were not able to get the TCP/IP config up and running, we had to go back and boot our alternate SAN system disks that kept a backup of the original 8.2. The system is now running fine with 8.2 as before. The 8.3 install is sleeping on the primary SAN boot disks waiting for good ideas...

 

Any help is greatly appreciated.

 

BR,

Michael

 

Please use plain text.
Honored Contributor
Volker Halle
Posts: 5,189
Registered: ‎04-26-2004
Message 2 of 13 (1,374 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Michael,

 

did you consider to run @TCPIP$CONFIG to check/list/re-define the interfaces ?

 

Does $ TCPIP LIST COM LL show the entry for the LAN failover device on the V8.3 system disk(s) ?

 

Volker.

Please use plain text.
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 3 of 13 (1,366 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Volker,

 

yes, we did run @TCPIP$CONFIG. I saw all the Configuration for the interfaces (same for '$tcpip show config interface'). I even removed the config for le0 on one node and reentered it. Unfortunately with no change.

 

We are going to prepare  a testsystem during the next days to check a few more things. Until then, I can not test anything, since the cluster is now running in production with 8.2.

I will collect any suggestion made until the testsystem is ready.

 

Michael

Please use plain text.
Honored Contributor
Volker Halle
Posts: 5,189
Registered: ‎04-26-2004
Message 4 of 13 (1,359 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Michael,

 

could you please report the patch level (OpenVMS and TCPIP), because if you see the LLA0 device on OpenVMS and TCPIP can't configure it, this will most likely be a TCPIP issue, if it's not configuration or logical name related.

 

Do you have console output available ? Did the LLA device form correctly during boot ? Are you running SCS via LLA0 ? Did other protocols (DECnet, LAT) work via LLA0 ?

 

Volker.

Please use plain text.
Honored Contributor
Hoff
Posts: 4,906
Registered: ‎01-29-2006
Message 5 of 13 (1,344 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Make sure you've followed any LANCP database upgrade requirements.  There was a manual upgrade sequence required within this version range, and failing to perform that step could cause some wonky behavior with the tool.

 

If that is not the trigger (and nobody pulls a rabbit out of their hat, here), then ring up HP support as that's the current escalation model for VMS support.

 

Please use plain text.
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 6 of 13 (1,275 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Hi !

 

Finally, our testsystem is ready and shows the same problem.

 

First I tried Hoff's suggestion and did

 $ LANCP
LANCP> CONVERT DEVICE_DATABASE
LANCP> SET ACP/STOP
LANCP> EXIT
$ @SYS$STARTUP:LAN$STARTUP

 

Unfortunately, the problem still persisted.

I then tried to reboot the system. Startup messages correctly report LLA0 to be configured:

%EWA0, Auto-negotiation mode set by console (EGA0_MODE)
%EWA0, DEGXA-TA located in 64-bit, 66-mhz PCI slot
%EWA0, Device type is BCM5703C (UTP) Rev A2 (10020000)
%EWB0, 100mbps_full_duplex mode set by console (EGB0_MODE)
%EWB0, DEGXA-TA located in 64-bit, 66-mhz PCI slot
%EWB0, Device type is BCM5703C (UTP) Rev A2 (10020000)
%EWB0, Link up: 100 mbit, full duplex, flow control disabled
%EWC0, Auto-negotiation mode set by console (EGC0_MODE)
%EWC0, DEGXA-TA located in 64-bit, 66-mhz PCI slot
%EWC0, Device type is BCM5703C (UTP) Rev A2 (10020000)
%LLA0, Logical LAN event at  6-JUL-2011 17:02:51.42
%LLA0, Logical LAN failset device created
%LLA0, Logical LAN event at  6-JUL-2011 17:02:51.43
%LLA0, Logical LAN failover devices all offline

Since I commented out the TCPIP-startup, I did it manually:

 

$ @sys$startup:tcpip$startup

%TCPIP-I-INFO, TCP/IP Services startup beginning at  6-JUL-2011 17:05:49.11
%TCPIP-I-NORMAL, timezone information verified

%RUN-S-PROC_ID, identification of created process is 20200435
%TCPIP-I-SETLOCAL, setting domain and/or local host
%TCPIP-I-STARTCOMM, starting communication
%TCPIP-I-SETPROTP, setting protocol parameters
%TCPIP-I-DEFINTE, defining interfaces
ioctl failed: status = 908
ifconfig: no such interface: LE0
%SYSTEM-W-NOSUCHDEV, no such device available
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
[...]

 

The error message still persisted. To check, wether all devices fail or if only LE0 bails out, I tried to configure WE2 and afterwards LE0 manually:

 

TCPIP> list comm ll
                    Communication Controller Configuration

Controller:  LL   Internet Interface:  L
                         Description:  LAN Failover Device
                                Type:  CLUSTER ETHERNET
TCPIP>show interface
                                                           Packets
Interface   IP_Addr         Network mask          Receive          Send     MTU

 LO0        127.0.0.1       255.0.0.0                   0             0    4096
TCPIP> show config interface

 Interface: LO0
   IP_Addr: 127.0.0.1         NETWRK: 255.0.0.0         BRDCST:

 Interface: LE0
   IP_Addr: 172.x.x.x      NETWRK: 255.255.255.0     BRDCST: 172.x.x.x

 Interface: WE2
   IP_Addr: 10.y.y.y        NETWRK: 255.255.0.0       BRDCST: 10.y.y.y

TCPIP> set interface we2 /host=ES47 /NETWORK_MASK=255.255.0.0 /BROADCAST_MASK=1
0.y.y.y

TCPIP> show interface
                                                           Packets
Interface   IP_Addr         Network mask          Receive          Send     MTU

 LO0        127.0.0.1       255.0.0.0                   0             0    4096
 WE2        10.y.y.y        255.255.0.0                 0             1    1500

TCPIP>set interface le0

%TCPIP-E-INVINTER, error defining interface: LE0
-TCPIP-I-DRIVERQIO, interface operation from internet driver QIO failed
-TCPIP-E-INVNETFLAG, invalid interface flags
ioctl failed: status = 908
ifconfig: no such interface: LE0
%SYSTEM-W-NOSUCHDEV, no such device available

 

LE0 still is not available. I concluded, that the problem must be related to the failover davice.

 

 $ mc lancp
LANCP> show device

ES47 Device Listing, volatile database (6-JUL-2011 17:13:07.44):
  Device
  ------
  EWA0
  EWB0
  EWC0
  LLA0
LANCP>show device lla0 /char

ES47 Device Characteristics LLA0 (6-JUL-2011 17:14:39.64):
                  Value  Characteristic
                  -----  --------------
                   1500  Device buffer size
                 Normal  Controller mode
               External  Internal loopback mode
      00-00-00-00-00-00  Default MAC address (Hardware LAN address)
                         Multicast address list
               Ethernet  Communication medium
      FF-FF-FF-FF-FF-FF  MAC address (Current LAN address)
                    128  Minimum receive buffers
                    256  Maximum receive buffers
                     No  Full duplex enable
                     No  Full duplex operational
      00-00-00-00-00-00  MAC address (Current LAN address)
            Unspecified  Line media type
                     10  Line speed (mbps)
               Disabled  Auto-negotiation
               Disabled  Flow control
               Disabled  Jumbo frames
                  "EWA"  Failover device
                  "EWB"  Failover device
    Disabled/No Failset  Logical LAN state
                      0  Failover priority
LANCP>

 

Since the device is disabled, I tried to anable it, but it threw an errormessage, that the device is either offline or not usable.

 

I then tried to remove the lla0 device useing purge & clear and rebooted. The device was no longer shown during system startup. Trying to recreate the lla0 device using

lancp> define device lla/failover=(ewa0,ewb0)/enable

didn't help, either.

 

I now found an old thread in ITRC ID=1035709 (which is no longer directly reachable but goole cache is your friend:-) with hints, that defining lla devices is not that straight forward as I expected. I will try to follow the suggestions there and see how far I will get.

 

Any suggestions are greatly welcome.

 

BR,

Michael

 

 

Please use plain text.
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 7 of 13 (1,273 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Since messages are limited to 20.000 characters, here is the top of the prod show history command in a seperate reply:

 

$ prod show hist
------------------------------------ ----------- ----------- --- -----------
PRODUCT                              KIT TYPE    OPERATION   VAL DATE
------------------------------------ ----------- ----------- --- -----------
DEC AXPVMS VMS83A_TDF V2.0           Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_MANAGE V4.0        Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_F11X V2.0          Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_ENCRYPT V2.0       Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_DDTM V2.0          Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_BACKUP V5.0        Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_ACRTL V7.0         Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_ACMELDAP V4.0      Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_TZ V1.0            Patch       Install     Val 02-JUL-2011
HP AXPVMS SSL V1.4-332               Full LP     Install     Val 02-JUL-2011
HP AXPVMS SSL V1.3-281               Full LP     Remove       -  02-JUL-2011
DEC AXPVMS TCPIP_NTP_PAT V5.6-9ECO5E Patch       Install     Val 02-JUL-2011
DEC AXPVMS TCPIP V5.6-9ECO5          Full LP     Install     Val 02-JUL-2011
DEC AXPVMS TCPIP V5.6-9              Full LP     Remove       -  02-JUL-2011
DEC AXPVMS JAVA142 V1.4-29           Full LP     Install     Val 02-JUL-2011
DEC AXPVMS JAVA142 V1.4-22           Full LP     Remove       -  02-JUL-2011
DEC AXPVMS DNVOSIECO03 V8.3          Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_SYS V19.0          Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_UPDATE V15.0       Patch       Install     Val 02-JUL-2011
DEC AXPVMS VMS83A_PCSI V3.0          Patch       Install     Val 02-JUL-2011
CPQ AXPVMS CDSA V2.2-271             Full LP     Install     (C) 02-JUL-2011
DEC AXPVMS DECNET_OSI V8.3           Full LP     Install     (C) 02-JUL-2011
DEC AXPVMS DWMOTIF V1.6              Full LP     Install     (C) 02-JUL-2011
DEC AXPVMS DWMOTIF_SUPPORT V8.3      Full LP     Install     (U) 02-JUL-2011
DEC AXPVMS OPENVMS V8.3              Platform    Install     (U) 02-JUL-2011
DEC AXPVMS TCPIP V5.6-9              Full LP     Install     (C) 02-JUL-2011
DEC AXPVMS VMS V8.3                  Oper System Install     (U) 02-JUL-2011
HP AXPVMS AVAIL_MAN_BASE V8.3        Full LP     Install     (U) 02-JUL-2011
HP AXPVMS KERBEROS V3.0-103          Full LP     Install     (C) 02-JUL-2011
HP AXPVMS SSL V1.3-281               Full LP     Install     (C) 02-JUL-2011
HP AXPVMS TDC_RT V2.2-107            Full LP     Install     (C) 02-JUL-2011

[...]

 

Please use plain text.
Honored Contributor
Volker Halle
Posts: 5,189
Registered: ‎04-26-2004
Message 8 of 13 (1,268 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Michael,

 

the console messages indicate, that LLA0 did NOT get correctly configured:

 

%LLA0, Logical LAN event at 6-JUL-2011 17:02:51.42
%LLA0, Logical LAN failset device created
%LLA0, Logical LAN event at 6-JUL-2011 17:02:51.43
%LLA0, Logical LAN failover devices all offline

 

Maybe delete (PURGE) EWA0, EWB0 and LLA0 from the LANCP database and create the LLA0 device again from scratch. Also check the SYS$MANAGER:LAN$ACP.LOG file for error messages.

 

Volker.

Please use plain text.
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 9 of 13 (1,259 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Volker,

 

thanks for the hint. We are going to setup the LLA device from scratch next week.

In the meantime, I can provide two parts from LAN$ACP.LOG:

 

preupdate (8.2):

type LAN$ACP.LOG;45

10-APR-2011 01:20:40.53 Defined LAN$DLL to be SYS$SYSROOT:[MOM$SYSTEM]

10-APR-2011 01:20:40.60 Found LAN device EWA0, hardware address 00-08-02-91-8A-

DF

10-APR-2011 01:20:40.60 Found LAN device EWB0, hardware address 00-08-02-91-8C-

54

10-APR-2011 01:20:40.60 Found LAN device EWC0, hardware address 00-08-02-91-8A-

EA

10-APR-2011 01:20:40.60 Found LAN device LLA0, hardware address AA-00-00-91-8C-

54

10-APR-2011 01:20:40.61 Node database file, LAN$NODE_DATABASE, not found

10-APR-2011 01:20:41.15 LANACP initialization complete

 

postupdate (8.3):

type LAN$ACP.LOG;46

2-JUL-2011 22:59:12.81 Defined LAN$DLL to be SYS$SYSROOT:[MOM$SYSTEM]

2-JUL-2011 22:59:12.82 Found LAN device EWA0, hardware address 00-08-02-91-8A-

DF

2-JUL-2011 22:59:12.82 Found LAN device EWB0, hardware address 00-08-02-91-8C-

54

2-JUL-2011 22:59:12.82 Found LAN device EWC0, hardware address 00-08-02-91-8A-

EA

2-JUL-2011 22:59:12.82 Found LAN device LLA0, hardware address 00-00-00-00-00-

00

2-JUL-2011 22:59:12.82 %EWA0, Auto-negotiation mode set by console (EGA0_MODE)

2-JUL-2011 22:59:12.82 %EWA0, DEGXA-TA located in 64-bit, 66-mhz PCI slot

2-JUL-2011 22:59:12.82 %EWA0, Device type is BCM5703C (UTP) Rev A2 (10020000)

2-JUL-2011 22:59:12.82 %EWB0, Auto-negotiation mode set by console (EGB0_MODE)

2-JUL-2011 22:59:12.82 %EWB0, DEGXA-TA located in 64-bit, 66-mhz PCI slot

2-JUL-2011 22:59:12.82 %EWB0, Device type is BCM5703C (UTP) Rev A2 (10020000)

2-JUL-2011 22:59:12.83 %EWC0, Auto-negotiation mode set by console (EGC0_MODE)

2-JUL-2011 22:59:12.83 %EWC0, DEGXA-TA located in 64-bit, 66-mhz PCI slot

2-JUL-2011 22:59:12.83 %EWC0, Device type is BCM5703C (UTP) Rev A2 (10020000)

2-JUL-2011 22:59:12.83 %LLA0, Logical LAN driver loaded. New device is LLA0

2-JUL-2011 22:59:12.83 %LLA0, Logical LAN failset devices are all offline for

LLA0

2-JUL-2011 22:59:12.83 %EWC0, Link up: 100 mbit, full duplex, flow control dis

abled

2-JUL-2011 22:59:12.83 %EWA0, Link up: 1000 mbit, full duplex, flow control di

sabled

2-JUL-2011 22:59:12.83 %EWB0, Link up: 1000 mbit, full duplex, flow control di

sabled

2-JUL-2011 22:59:12.83 Node database file, LAN$NODE_DATABASE, not found

2-JUL-2011 22:59:12.85 LANACP initialization complete

 

Michael

 

Please use plain text.
Honored Contributor
Volker Halle
Posts: 5,189
Registered: ‎04-26-2004
Message 10 of 13 (1,257 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Michael,

 

once the test system is up, invoke **bleep**/SYS and do a SDA> SHOW LAN to check, which protocols are running on the various LAN devices. If ANY protocols have been started on the LAN devices, which should be members of the LLA0 failover set, this won't work.

 

There are also a couple of caveats with VAXCLUSTER and NISCS_LOAD_PEA0 settings and LAN failover. Also check whether DLL has been enabled on those LAN devices.

 

Volker.

Please use plain text.
Honored Contributor
The Brit
Posts: 1,287
Registered: ‎06-18-2007
Message 11 of 13 (1,235 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Might be unrelated, however I had a similar problem when the devices were enabled for down-line loading.

 

try

LANCP>  show dev /dll

 

and if they show up as "enabled" then disable them (particularly in the Permanent DB.

 

Dave. 

Please use plain text.
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 12 of 13 (1,203 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Hi !

 

First I want to thank you for all the tips. We were able to reproduce the problem on our test system (ES47).  Last week we managed to get the interfaces up and running again on the test system.

We are going to implement the change in the production system in first week of August.

 

Summary:

Initially the problem seemed to be related to a missing LE0 TCP/IP interface. Digging a little bit deeper, we found, that TCPIP could not use the failover device lla0. Looking at it using LANCP, the interface was defined and created during boot, but the participating physical interfaces EWA0 and EWB0 could not be added during boot.

 

Hoff suggested, to check for a manual procecdure required during upgrade  to OpenVMS 8.3.  According to http://h71000.www7.hp.com/doc/84final/6677/6677pro_install.htmlone

we might need to convert the LANCP device database manually doing

$ LANCP

LANCP> CONVERT DEVICE_DATABASE

LANCP> SET ACP/STOP

LANCP> EXIT

$ @SYS$STARTUP:LAN$STARTUP

 

but this didn’t fix the problem.

 

Checking patchlevels of OpenVMS and TCPIP didn’t get the thing done either.

 

Dave suggested to check, whether downlineload (MOP) is enabled on the interfaces, but doing a ‘mc lancp show dev /dll’ showed, that DLL on all interfaces was disabled.

 

The best hint came from Volker Halle and an old ITRC thread I was only able to find using google cache ‘Can't start LAN failover’. Volker suggested to remove LLA0 completely and rebuilt the setup from scratch. Unfortunately, this wasn’t possible while booting in normal mode, since the physical interfaces are in use by some protocols. This can be checked by

$ ananlyze/sys

SDA> show lan

(Volker, in your post the analyze was replaced by ‘**bleep**’, I suspect you abbreviated it…)

 

We then tried to boot minimum (STARTUP_P1 = “min”) which prevented other protocols than SCA to start (SCA doesn’t harm here).

Purging and clearing lla0 from permanent and volatile lancp databases removed all reminiscences to this interface.

Now recreating the interface using

LANCP> define dev lla0/failover=(ewa0,ewb0)/ena

LANCP> set dev lla0/failover=(ewa0,ewb0)/ena

 

still produced an error

%LANCP-E-LLANACT, LAN device active, cannot be added to or removed from Logical LAN LLA0

 

but continuing with

LANCP> set device lla0 /update/vola

 

and then rebooting back to normal startup did the trick. With this reboot, LLA0 was not only created but was able to attach to a physical interface.

 

%LLA0, Logical LAN event at 12-JUL-2011 12:46:41.41

%LLA0, Logical LAN failset device created

%LLA0, Logical LAN event at 12-JUL-2011 12:46:41.42

%LLA0, Logical LAN failover device added to failset, EWA0

%LLA0, Logical LAN event at 12-JUL-2011 12:46:41.42

%LLA0, Logical LAN failover device added to failset, EWB0

%LLA0, Logical LAN event at 12-JUL-2011 12:46:41.42

%LLA0, Logical LAN failset device connected to physical device EWB0

 

The last line was the one that was missing and caused the problem.

At this point, TCPIP no longer complained about LLA0 being offline and started with its original config.

 

 Thanks again for you help.

 

Michael

 

Please use plain text.
Occasional Advisor
mkrauss
Posts: 9
Registered: ‎03-06-2007
Message 13 of 13 (1,107 Views)

Re: TCPIP interfaces le0 + we1 missing after upgrade to 8.3 / ioctl failed: status = 908

Spoiler
 

Hi all,

 

today we wer successful in implementing the change in the production environment. Just deleting and recreating lla0 from scratch fixed the problem. It is important to do the LANCP set/def commands while booted minimum (Startup_P1 = "min"). Otherwise the physical failover devices (e.g. ewa0, ewb0) will be blocked by running protocols.

I really can't tell what has happened, but it is fixed now.

 

Best regards,

Michael

 

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation