HPE OneView
1758810 Members
3198 Online
108875 Solutions
New Discussion юеВ

Re: OneView web interface and server adding issues

 
clmueller
Occasional Advisor

Re: OneView web interface and server adding issues

Hi all,

I see the same behaviour with OV 6.6 Demoappliance on ESXi 7.0.2 

Installation works, Appliance can be configured with ESXi web console but access via http, https or ssh is not working. 

The appliance is able to ping the gateway and other VMs within the ESXi host.

Other VMs (e.g. ilo-Amplifier) works great on the same ESXi host and also access via https and ssh is possible.

ilo-Amp makes use of E1000 and OV appliance VMXNET3 as a major difference between the installations.

Networksettings are the same (mask, GW) and there is no firewall between the OV and my client.

Any ideas or known problems?

Kind regards 

Claus

clmueller
Occasional Advisor

Re: OneView web interface and server adding issues

...looks like that there is an issue with the static routes. Is there still no way to change them within the appliance (may via maintenance)? What are the netmasks for the 192.x.x.x and 172.16.x.x.x routes?

clmueller
Occasional Advisor

Re: OneView web interface and server adding issues

workaround with NAT between client and OV.

May it's worth to think it over if the internal routing of 172.16.0..0/12 and 192.0.0.0/8 is necessary or if it is a bug...

Kind regards

Claus

ChrisLynch
HPE Pro

Re: OneView web interface and server adding issues

OneView does not support NAT configurations, so that is not an option.  172.16.0.0/16 is used internally to the demo appliance and cannot be changed.  This has been standard behavior for all releases.


I am an HPE employee

Accept or Kudo