| Author |
ESXi FreeAXP Networking |
maveri
Member
Posts: 19
Joined: 23.04.08 |
| Posted on April 04 2014 12:23 |
|
|
I'm trying to get ESXi 5.1 and FreeAXP to work
Details:
OpenVMS 8.4
ESXi 5.1
HP Microsever 16gb N54L
E1000 network card
Promiscious mode selected
I have even tried adding a second nic and binding them but alas i cannot get OpenVMS network to communication beyond itself
There is only 1 physical nic on the HP server but as far as OpenVMS is concerned, that should be hidden from it
Any tips or troubleshooting hints greatly appreciated |
|
|
| Author |
RE: ESXi FreeAXP Networking |
maveri
Member
Posts: 19
Joined: 23.04.08 |
| Posted on April 06 2014 00:18 |
|
|
I have also followed the instructions as listed in the User guide but to no avail
I have tried all sorts of combinations of turning off all protocols on the nics to enabling some on one and none on the other to everything being switched off but alas, nothing
I can ping my gateway from the windows client on the esxi host but cannot ping the VMS box nor on the VMS box ping the windows client and/or the gateway
VMS passes the networking test in tcp and can ping itself via loopback but beyond this nothing
I should have mentioned, my setup is as follows
OpenVMS 8.4
Windows XP 32 bit
FreeAXP
FreeAXP works fine on my laptop (Windows 7, 32 bit) and I'm sure I've run it before on Windows XP 32 bit |
|
|
| Author |
RE: ESXi FreeAXP Networking |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on April 06 2014 04:34 |
|
|
It sounds like an issue between the virtual NIC/network and the real network.
Are you using an E1000 NIC type on the virtual NIC?
If you allow DHCP to assign an address to the virtual NIC, can you ping back and forth between the Windows virtual host and another system? |
|
|
| Author |
RE: ESXi FreeAXP Networking |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on April 06 2014 04:39 |
|
|
Once you have confirmed communications via Windows, than try it via FreeAXP. If FreeAXP still cannot communicate to the outside world, try these two things:
- Leave TCP/IP up on the Windows side on the NIC and test FreeAXP.
- Take the virtual NIC MAC address and add it to the FreeAXP NIC definition in the FreeAXP configuration file. |
|
|
| Author |
RE: ESXi FreeAXP Networking |
maveri
Member
Posts: 19
Joined: 23.04.08 |
| Posted on April 15 2014 20:11 |
|
|
Sorry for the slow feedback!
My problem seemed to be related to TCP on OpenVMS in the end
My setup is as follows
ESXi 5.1 - HP Microserver
VM instance - Windows XP 32 bit (can ping gateway router ok), E1000 nic
FreeAXP - OpenVMS 8.4 (could not ping gateway router)
In the end I installed OpenVMS 8.4 from scratch and vola, everything works - go figure!
For the sake of others, the nic on the Windows XP instance is set to tcpip enabled with automatic address selection and consequently the Windows XP instance has one IP address dished out by my router and my OpenVMS 8.4 instance has another ip address (in the same subnet) assigned by myself
This combination works :-)
Appreciate the feedback Bruce
I like FreeAXP, it enables more devices than other free Alpha emulators - not that I'm using them all at the moment
EDIT:
Edited by maveri on April 16 2014 09:01 |
|
|
| Author |
RE: ESXi FreeAXP Networking |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on April 16 2014 01:32 |
|
|
|
Thanks for the feedback and installation tips. Glad to hear everything is working. |
|
|
| Author |
RE: ESXi FreeAXP Networking |
maveri
Member
Posts: 19
Joined: 23.04.08 |
| Posted on April 16 2014 09:02 |
|
|
One small update (tried editing my previous post but it kept dying)
For those having issues trying to then ftp to your FreeAXP instance and find that you don't get an ftp response, I found this registry hack worked (From Hoffman labs site)
http//labs.hoffmanlabs.com/node/1813:
The information is related to using FreeAXP on a system with a shared network card etc
The crux of the fix is below - for the conditions related to it see the url link above to ensure you are not applying a fix to a problem you may not have!
------------- snip -----------
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Click Edit, point to New, and then click DWORD Value.
4. Type DisableTaskOffload as the entry name, and then press ENTER.
5. Right-click DisableTaskOffload, and then click Modify.
6. In the Value data box, type a value of 1, and then click OK.
7. Quit Registry Editor.
8. Restart your computer.
------------ end snip -------- |
|
|
