OneView Monitor configuration limitations

book

Article ID: 53126

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) AXIOMATICS POLICY SERVER CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

Description:

In Siteminder 12.x, the OneView Monitor configuration UI has 2 options boxes:

  • Allow Incoming Remote Connections: Enable/Disable

  • Connect to Remote Port [host:port]: Enable (you can configure host:port)/Disable (you can't configure host:port)

In theory, you should have 4 configurations possible, but only 2 seem to work:

  • Allow Incoming Remote Connections enabled + Connect to Remote Port enabled.

  • Allow Incoming Remote Connections disabled + Connect to Remote Port enabled.

Why is it so?

Solution:

The way it works is the way it was designed.
The issue is with the UI: it should not give you the possibility to configure the OneView Monitor in any other way.

The way it works is that the port entered in the configuration file conapi.conf implies that the connect to remote is desired. If you deselect the connect to remote, it reverts to default once you save it (hit apply). On top of that, the OneView Monitor port for listening and for remote has to be the same for all the configuration.

Once you change the port in the configuration file, it will mean you want OneView to listen to that port AND connect to a remote host you specify which will listen on the SAME port number. You can say allowRemote=false and then what would happen is that it will only connect to remote and not listen.

You can only listen on the DEFAULT port 44449 without connecting to remote. but once you change this default port, there is no LISTENING ONLY.

It has to be one of the following configuration:

  • Allow Incoming Remote Connections enabled + Connect to Remote Port enabled.

  • Allow Incoming Remote Connections disabled + Connect to Remote Port enabled.

Environment

Release:
Component: SMPLC