Integrate > Integrate Operations Agent with OMi

Integrate Operations Agent with OMi

If Operations Agent is installed on one of the master or worker nodes, additional steps are required to integrate Operations Agent with OMi .

Caution If the agent is installed on an external node instead, these steps are not required.

Configure the agent to use a different port than the one used by default, and configure OMi to use this non-default port:

  1. Make sure that your system has a virtual external hostname (for example kubecluster.example.com) which is different than the physical node name (for example dock.example.com).
    To do this, add an entry to the DNS server for the virtual hostname of the suite installation. This hostname must be resolvable for all agents that are installed on one of the Kubernetes nodes.
  2. Configure the Agent to use a different server port (for example 384):

    ovconfchg -ns bbc.cb -set SERVER_PORT 384

  3. Configure Operations Agent to use the virtual external hostname (kubecluster.example.com) as the management server name:

    opcactivate.sh -s <virtual_external_hostname>

  4. Configure OMi to connect to the master node with the specified port (for example 384):

    ovconfchg -ns bbc.cb.ports -set PORTS dock.example.com:384