Wireless Access

We are able to ping, we have DNS set up, but not able to connect over any web browser. the server is able to ping out fine, the OVA installed fine on our VMs, its just over HTTPS, we cannot connect it it.

What did we overlook?

Try running amp_enable from the CLI.

I ran it, still no response. Sorry.

Have you tried "service httpd start " ?

I get this. (See file attached)

From the device you are trying to connect from, can you try to telnet to server using port 443? This will test connectivity and ensure nothing is blocking it.

That did not work. From my last post, it looks like something is wrong with the ethernet connection. Its not connecting properly, but its able to be ping-ed

Our posts crossed over the wire!

You might want to open up a TAC case. Looks like there is another service that is using port 443.

Thanks, Will do.

I'd be interested in knowing which process is tying up the port.

Is there anything additional in the logs?

  /var/log/httpd/error_log

  /var/log/low_level_service_watcher

You may want to try the following:

1.  # amp_disable

2.  # service httpd restart

3.  # service pound restart

4.  # amp_enable

---------> this method restarts the web servers used by AMP, hopefully releasing and renewing the port.

If that doesn't work and you don't care about root cause, a server reboot would definitely do the trick to release the port for apache (may have to issue another amp_enable after a reboot).

I am still unable to acess the server after running the commands.

This is what I get.

How long did you wait before trying to access the web UI?  After amp_enable, it can take 5-10 minutes for the process to get going.  Check the currently running daemons:

# daemons

-single run of currently running daemons

# wd

-refreshing view of currently running daemons

-alias for 'watch daemons'

If you see more than 10 daemons running, then I'd expect the UI to be reachable.  The only times that the UI isn't reachable when 10 daemons or more are running is when the disk space is completely full (df -h)

turns out we had an old ACL on the servers IP address that caused it to be able to ping, and that was it. We got rid of the ACL and fixed it. Sorry everyone.

We had to install Apache. -It was downloaded and all of the file were there but apache was just not installed.