Network issues with PersonalAlpha container

Gremlin,

I can assure you, that there is no EWA0 device on PersonalAlpha, only an ESA0 device. In TCPIP interface naming, you could only configure SE0 on PersonalAlpha and WE0 on FreeAXP.

You can easily confirm this with $ SHOW DEV EW and $ SHOW DEV ES
and $ TCPIP SHOW INT. If you use $ TCPIP SHOW CONF INT, you may well see both se0 and we0 in the permanent database on disk, but you'll get an error about a missing device, when starting TCPIP.

Please note that network card drivers (other than on OpenVMS) may get confused, when you're starting DECnet with Phase IV address, as the MAC address needs to be changed.

May I suggest, that you try to configure the TCPIP interface on both PersonalAlpha and FreeAXP to use DHCP for configuration of the IP address and parameters ? This is the most flexible solution and allows you to boot the same OpenVMS disk in both emulators. Alternatively, you could also define both interfaces with fixed addresses in the TCPIP database. You have to do these configurations inidually running under each emulator. You can even configure different hostnames with HOSTNAME.we0 and HOSTNAME.se0, so that your system shows up as PersonalAlpha.your.domain or freeaxp.your.domain depending on which emulator you boot your OpenVMS system disk on.

Volker.<hr>

Hi

They are already configured as fixed IP addresses and ESA0 is the correct device name - I am having finger troubles!!

DECnet may be the culprit - I don't remember anything in some documentation about it, now I suppose I need to find it. I remember the need to change the MAC address is there was more than one NIC configured for VMS, but I suspect there is only one EWA0. I am happy to boot this system under FreeAXP only, as long as I can sort out the network issue.

[edit] checked the documentation and it mentions MAC issues if there are multiple FreeAXP instances on a single network (not in this case), running on a wireless card (no) and running two NICs (no). Can't see how DECnet would be a problem on a single dedicated NIC with fixed IP addresses. Also, as cluster join messages aren't getting out, I guess the problem is not IP related - it must be much earlier and much deeper.<hr>

Gremlin,
I believe you have to have two network cards configured on your Fusion-based Windows system to use FreeAXP's networking driver to provide networking support to emulated environment. Under Parallels VM, I just add a second network adapter to my system configuration.

Hope that helps!
-Shane

Hi Shane

Thanks for that - Fusion has two adapters configured - one is the in-built Gigabit network port, shared by the Windows host. The other is a USB-CAT5 adapter that fusion sees and is also seen by the Windows host, but is not bound to anything within Windows. It is this adapter that is selected for exclusive use by FreeAXP.

Volker,

$ tcpip sho conf int

Interface: LO0
IP_Addr: 127.0.0.1 NETWRK: 255.0.0.0 BRDCST:

Interface: SE0
IP_Addr: 192.168.100.202 NETWRK: 255.255.255.0 BRDCST: 192.168.100.255

Interface: WE0
IP_Addr: 192.168.100.202 NETWRK: 255.255.255.0 BRDCST: 192.168.100.255

The system can ping itself, nothing else. Hosts and gateway are configured, as are DNS and routing. Remember, this is a PA image in which networking was fine until I tried to run it under FreeAXP. MAC address of EWA0 is 08-00-2b-de-50-00. There is no other identical MAC address on this network segment.

Cheers<hr>

Hi all

DECnet is emerging as the culprit....


LANCP&gt;

**** OpenVMS Alpha Operating System V8.3 - BUGCHECK ****

** Bugcheck code = 000007CC: NETDLLERR, DECnet Datalink Layer detected a fatal error
** Crash CPU: 00000000 Primary CPU: 00000000 Node Name: GAMMA
** Supported CPU count: 00000002
** Active CPUs: 00000000.00000001
** Current Process: NULL
** Current PSB ID: 00000001
** Image Name:

**** Starting compressed selective memory dump at 20-MAY-2010 22:52...

You are running FreeAXP 271, correct?