casutton Frequent Contributor.
Frequent Contributor.
964 views

SSPR VM Appliance setup - can't access website after install

I went through the simple forms and filled out the information using a static IP address. But when it completes, I cannot access anything via HTTP or HTTPS. I also noticed that there is a docker running inside the VM Appliance that has a 172.17.0.1 network. We are using 172.17.0/16 and 172.16.0/16 on our internal network. This could be causing issues? Anyone else run into this problem?
Tags (4)
0 Likes
2 Replies
casutton Frequent Contributor.
Frequent Contributor.

Re: SSPR VM Appliance setup - can't access website after ins

More information. I can only ping the server from our server vlan which is 172.16.0/16. From our workstation VLANS which are in the 172.17.0/16 range of IP addresses I cannot ping the server. I enabled ssh on the server. I get the same result. I can ssh into the server only from the server vlan of 172.16.0/16 but not from any of our 172.17 vlans. I can access https://servername:9443 only from the 172.16 vlan and not anything on 172.17. The appliance seems to be able to access the Internet fine. I was able to manually register the server via command line and run updates with zypper. No other issues like this exist on our network. After doing these tests I'm convinced that there must be some weird interaction with the Docker using the 172.17.0/16 network.
0 Likes
Knowledge Partner
Knowledge Partner

Re: SSPR VM Appliance setup - can't access website after install

On 07/27/2017 09:24 AM, casutton wrote:
>
> More information. I can only ping the server from our server vlan which
> is 172.16.0/16. From our workstation VLANS which are in the 172.17.0/16
> range of IP addresses I cannot ping the server. I enabled ssh on the
> server. I get the same result. I can ssh into the server only from the
> server vlan of 172.16.0/16 but not from any of our 172.17 vlans. I can
> access https://servername:9443 only from the 172.16 vlan and not
> anything on 172.17. The appliance seems to be able to access the
> Internet fine. I was able to manually register the server via command
> line and run updates with zypper. No other issues like this exist on our
> network. After doing these tests I'm convinced that there must be some
> weird interaction with the Docker using the 172.17.0/16 network.


Not being able to ping would, to me, mean a network firewall issue, not a
VM or host issue, since by default SLES allows pings through. If your
network blocks ICMP everywhere (a bad idea) then that may explain it, but
ICMP is not actually used for things like TCP, of course, so that may also
be a red herring; I only mention it because, combined with the inability
to get in other ways, it seems suspicious.

It may be worthwhile to look at the appliance's listening sockets, and
firewall configuration, after verifying network traffic can get there (see
you network or VM administrators, if not you).


sudo /usr/sbin/iptables-save
sudo /usr/sbin/ss -planeto | grep 'LISTEN '


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.