Boot failure on V6.2-1H2
- VolkerHalle
- Topic Author
- Visitor
14 years 9 months ago #4858
by VolkerHalle
Replied by VolkerHalle on topic RE: $ UCX SHOW VERSION ?
Kinsa,
if OpenVMS patches have helped, how about UCX patches ?
Does @UCX$CONFIG and re-configuring the interface detect and accept EWA0 as WE0 ?
Please also take the time and check the EWA0 interface details on your original Alpha system. The idea of hardware emulation is to - whenever possible - make NO changes to the operating system and applications, when moving from the real system to the emulated system.
Volker.<hr>
if OpenVMS patches have helped, how about UCX patches ?
Does @UCX$CONFIG and re-configuring the interface detect and accept EWA0 as WE0 ?
Please also take the time and check the EWA0 interface details on your original Alpha system. The idea of hardware emulation is to - whenever possible - make NO changes to the operating system and applications, when moving from the real system to the emulated system.
Volker.<hr>
Please Log in or Create an account to join the conversation.
- kinsa
- Topic Author
- Visitor
14 years 9 months ago #4859
by kinsa
Replied by kinsa on topic RE: $ ucx show version
Volker,
This is what I had installed:
< class='quote'>ALPCLUSIO01_062
ALPBOOT12_062
ALPBOOT13_062
ALPCPU0C09_062
ALPCPU0D05_062
ALPCPU1501_062
ALPCPU1603_062
ALPCPU1A02_062
ALPCPU1B03_062
ALPCPU906_062
ALPCPU0907_062
ALPLAN05_062
UCXECO_41_10
< class='quote'>Does @UCX$CONFIG and re-configuring the interface detect and accept EWA0 as WE0 ?
There is no problem during configuration, only during the TCPIP startup.
< class='quote'>%UCX-I-DEFINTE, Defining interfaces
%UCX-E-INVINTER, Error defining interface: WE0
-UCX-I-ACPQIO, Failure on Internet ACP QIO
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
%UCX-E-INVINTERNAM, Invalid interface name
-UCX-I-DRIVERQIO, Failure on Internet driver QIO
-UCX-E-INVNETMASK, Invalid network mask
%UCX-E-DELINTER, Error deleting interface: WE0
-UCX-I-ACPQIO, Failure on Internet ACP QIO
-UCX-E-INVINTERNAM, Invalid interface name
< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>$ ucx show version
Digital TCP/IP Services for OpenVMS Alpha Version V4.1 - ECO 10
on a AlphaServer 400 4/166 running OpenVMS V6.2-1H3
<br><br><br></code>
Kinsa.
[b:]UPDATE[/b:]
The reason why it doesn't work:
< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>
SDA> SHOW LAN/DEV=EW
-- EWA Device Information 24-APR-2010 07:31:24 --
LSB address 80A05C80 Driver code address 8087CAE8
Driver version 0A010001 06020008 Device1 code address 00000000
Device1 version 00000000 00000000 Device2 code address 00000000
Device2 version 00000000 00000000 LAN code address 8087C820
LAN version 00A30002 06020089 DLL type CSMACD
Device name EW_TULIP MOP name EWA
MOP ID 203 HW serial Not supplied
HW version 02000041 Promiscuous mode OFF
Controller mode NORMAL Promiscuous UCB 00000000
Internal loopback ON All multicast state OFF
Hardware address None CRC generation mode ON
Physical address None Full Duplex Enable OFF
Active unit count 0 Full Duplex State OFF
Line speed 100
Flags: 00000000
Char: 00000000
<br><br><br></code>
It is recognized as EW_TULIP card.<hr>
This is what I had installed:
< class='quote'>ALPCLUSIO01_062
ALPBOOT12_062
ALPBOOT13_062
ALPCPU0C09_062
ALPCPU0D05_062
ALPCPU1501_062
ALPCPU1603_062
ALPCPU1A02_062
ALPCPU1B03_062
ALPCPU906_062
ALPCPU0907_062
ALPLAN05_062
UCXECO_41_10
< class='quote'>Does @UCX$CONFIG and re-configuring the interface detect and accept EWA0 as WE0 ?
There is no problem during configuration, only during the TCPIP startup.
< class='quote'>%UCX-I-DEFINTE, Defining interfaces
%UCX-E-INVINTER, Error defining interface: WE0
-UCX-I-ACPQIO, Failure on Internet ACP QIO
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
-SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
%UCX-E-INVINTERNAM, Invalid interface name
-UCX-I-DRIVERQIO, Failure on Internet driver QIO
-UCX-E-INVNETMASK, Invalid network mask
%UCX-E-DELINTER, Error deleting interface: WE0
-UCX-I-ACPQIO, Failure on Internet ACP QIO
-UCX-E-INVINTERNAM, Invalid interface name
< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>$ ucx show version
Digital TCP/IP Services for OpenVMS Alpha Version V4.1 - ECO 10
on a AlphaServer 400 4/166 running OpenVMS V6.2-1H3
<br><br><br></code>
Kinsa.
[b:]UPDATE[/b:]
The reason why it doesn't work:
< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>
SDA> SHOW LAN/DEV=EW
-- EWA Device Information 24-APR-2010 07:31:24 --
LSB address 80A05C80 Driver code address 8087CAE8
Driver version 0A010001 06020008 Device1 code address 00000000
Device1 version 00000000 00000000 Device2 code address 00000000
Device2 version 00000000 00000000 LAN code address 8087C820
LAN version 00A30002 06020089 DLL type CSMACD
Device name EW_TULIP MOP name EWA
MOP ID 203 HW serial Not supplied
HW version 02000041 Promiscuous mode OFF
Controller mode NORMAL Promiscuous UCB 00000000
Internal loopback ON All multicast state OFF
Hardware address None CRC generation mode ON
Physical address None Full Duplex Enable OFF
Active unit count 0 Full Duplex State OFF
Line speed 100
Flags: 00000000
Char: 00000000
<br><br><br></code>
It is recognized as EW_TULIP card.<hr>
Please Log in or Create an account to join the conversation.
- VolkerHalle
- Topic Author
- Visitor
14 years 9 months ago #4860
by VolkerHalle
Replied by VolkerHalle on topic RE: DE500 not recognized by 'older' VMS versions
Kinsa,
the Stromasys CHARON-AXP/SMA help says this:
< class='quote'>
<model> specifies the emulated NIC (DE435/DE450/DE500) default is DE435 because older versions of VMS and DUnix do not recognize the newer ones
And there seems to be some truth in this ...
So the 'OpenVMS version supported' statement for FreeAXP .271 should be further qualified with the minimum version and patch level required for support of the emulated LAN interface.
Volker.
the Stromasys CHARON-AXP/SMA help says this:
< class='quote'>
<model> specifies the emulated NIC (DE435/DE450/DE500) default is DE435 because older versions of VMS and DUnix do not recognize the newer ones
And there seems to be some truth in this ...
So the 'OpenVMS version supported' statement for FreeAXP .271 should be further qualified with the minimum version and patch level required for support of the emulated LAN interface.
Volker.
Please Log in or Create an account to join the conversation.
- Bruce Claremont
- Topic Author
- Visitor
14 years 9 months ago #4861
by Bruce Claremont
Replied by Bruce Claremont on topic RE: Boot failure on V6.2-1H2
Earlier I stated I had successfully installed and configured VMS 6.2 and VMS 6.2-1H3 with DECnet and TCP/IP from VMS installation ISO's. I've gone back and re-tested under 271 and the NIC does not show up under either O/S. Sorry for the misstatement (which I've removed). We're working on the issue, which likely is related to an issue with the NIC under OSF/1 3.2C.
Please Log in or Create an account to join the conversation.
Moderators: iamcamiel
Time to create page: 0.206 seconds