- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- TCPIP interfaces le0 + we1 missing after upgrade t...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2011 09:14 AM
тАО07-04-2011 09:14 AM
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
Solved! Go to Solution.
- Tags:
- upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2011 11:28 PM
тАО07-04-2011 11:28 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2011 01:15 AM
тАО07-05-2011 01:15 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2011 01:45 AM
тАО07-05-2011 01:45 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2011 04:01 AM
тАО07-05-2011 04:01 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2011 05:00 AM
тАО07-08-2011 05:00 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2011 05:01 AM
тАО07-08-2011 05:01 AM
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
[...]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2011 05:13 AM
тАО07-08-2011 05:13 AM
SolutionMichael,
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2011 08:57 AM
тАО07-08-2011 08:57 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2011 09:24 AM
тАО07-08-2011 09:24 AM
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.