×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
So, here is the solution to VMWare part of the issue:
On the wired network where I could access ASMI at the 10.0.10.2 address
but could not through the vHMC: I wasn't thinking through the network
routing correctly. Yes, I needed to connect to the FSP at 10.0.10.2 but
I needed to make sure the default gateway for the vHMC console was the
same as the default gateway as the host. The IP was set statically and
the VM was set to bridge mode but I am pretty sure that if it were
assigned by DHCP, it would still work. The things I missed was 1) The
vHMC doesn't need to be on the same network as IBM i and 2) because of
#1, I needed to make sure there was a gateway "out" to the IBM i.
On the wireless network at home with the VPN, the important things were:
1) Use NAT for the VM 2) Use the .2 host address of the NAT network
(mine was 192.168.47.2) as the gateway. In this case the vHMC used a
DHCP assigned address (got 192.168.47.129) but the default gateway
needed to be set to the .2 address that the VMware NAT router used.
Gateway was the key. With the NAT option on the wireless/VLAN setup
what was unclear to me was what IP address to use as the default gateway.
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Twitter - Sys_i_Geek IBM_i_Geek
On 12/31/2020 11:16 AM, Pete Helgren wrote:
Thanks....I hope to sort this out today while I have some time. When I
am on the laptop at home, I have access to everything on the 10.x.x.x
at work including accessing the ASMI at 10.0.10.2 AND when I am on the
wired network at work, the vHMC can connect to the FSP at 10.0.10.2.
So, if it were a firewall issue I think it wouldn't work while on the
wired network but I tried turning off the firewall and it made no
difference.
I'll figure it out and then post the results. I think it is *just* a
network config issue....I suspect something at the VMWare level but
not quite sure...
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Twitter - Sys_i_Geek IBM_i_Geek
On 12/30/2020 8:18 PM, Steinmetz, Paul via MIDRANGE-L wrote:
Pete,
If your on a different VLAN at home, there is a good chance it’s a
firewall issue, not sure which ports you need for this.
Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.