We're running the script start-all and stop-all script and we don'tsee the OneView Monitor starting nor stopping.
Once we run stop-all script, after the Policy Server stoppedcompletely, we still see the ports 44449 and 44450 open.
How can we fix this ?
At first glance, the OneView Monitor has a component that runs onTomcat Server, which communicate with the Policy Server on ports (bydefault 44450). And when you start the Policy Server with the out ofthe box start-all script, it start the Policy Server and the OneViewMonitor client that will give the data to the OneView Monitorapplication that runs on Tomcat.
I've tried this scenario on my lab :
- Tomcat down;- Start the Policy Server with start-all script;- I see the ports 44449 and 44450 open on tcp;- Stop the Policy Server with stop-all script;- I see the ports 44449 and 44450 getting closed;
KB : KB000129574
Thank you for sharing this tip with the community Patrick!
Tech Tip : CA Single Sign-On : OneView Monitor port 44450 still open after Policy Server down