Captain
Captain
137 views

Operations connector Configuration change Tips

Jump to solution

Dear All,

Currently we have Operations connector installed for SCOM integration.Operations Connector is pointed to send data to Load balancer but now am planning to change it to Gateway server instead of Load balancer .Please let me know how to change the settings in connector.

 

In ovconfget ,it is showing license manager ,Certificate server and Management server as Load balancer name.Please let me know how to change all these settings since we are going to decomission the Load balancer 

 

What are the precautions I need to take before changing the settings

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

If you are changing a bunch of nodes or even just one node, from the OBM GW server you could run the "opr-agt -switch_manager -manager <yourGW.fqdn> -manager_id <`ovcoreid -ovrg server`>" command. That would change the license server, cert server, primary mgmtsv to yourGW.fqdn.

If you are just changing a single node rather than a bunch of nodes, you could run "opcactivate -srv <yourGW.fqdn>" locally on the managed node.

If you are just bypassing the LB to go directly to the GW, then I expect the other important stuff for secure datacomm will remain unchanged. Eg, all your policies are signed by the same manager, the sec.core.auth:MANAGER_ID remains unchanged (ie `ovcoreid -ovrg server` is unchanged - same DPS).

If you need to go via a proxy to communicate from the agent to the GW, you would need to update bbc.http:PROXY setting.  (ie, "ovconfchg -ns bbc.http -set PROXY ...")

What other precautions? Make the change on one node and test. Before making that change, do "ovconfget" to get the current settings.

CP.

View solution in original post

1 Reply
Micro Focus Expert
Micro Focus Expert

If you are changing a bunch of nodes or even just one node, from the OBM GW server you could run the "opr-agt -switch_manager -manager <yourGW.fqdn> -manager_id <`ovcoreid -ovrg server`>" command. That would change the license server, cert server, primary mgmtsv to yourGW.fqdn.

If you are just changing a single node rather than a bunch of nodes, you could run "opcactivate -srv <yourGW.fqdn>" locally on the managed node.

If you are just bypassing the LB to go directly to the GW, then I expect the other important stuff for secure datacomm will remain unchanged. Eg, all your policies are signed by the same manager, the sec.core.auth:MANAGER_ID remains unchanged (ie `ovcoreid -ovrg server` is unchanged - same DPS).

If you need to go via a proxy to communicate from the agent to the GW, you would need to update bbc.http:PROXY setting.  (ie, "ovconfchg -ns bbc.http -set PROXY ...")

What other precautions? Make the change on one node and test. Before making that change, do "ovconfget" to get the current settings.

CP.

View solution in original post

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.