Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
602 views

OMi in HA || Agent Buffering Issues

Jump to solution

Dear All,

We have OMi in HA mode.. 

OMi Version : 10.63

When secondary OMi is down.. automatically agents on both the gateways are going to buffering state and all the reporting agents are also going to buffering state.

Again when we start secondary OMi.. all the agents are getting back to normal state.

Any solution for this ?

Regards,

Manideep

 

Regards,

Manideep

#OMi #OperationsAgent

0 Likes
1 Solution

Accepted Solutions
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Hi,

There is issue with your NLB, check with your network team.

If they are not able to do then I can share NLB config document, email me on Mithilesh.Yadav@service-berry.com

 

View solution in original post

9 Replies
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Hi,

Can you please explain the architecture, how many GWs and DPs you have ?

Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

@Mithilesh_Yadav 

 

We have two OMi's in HA Mode, two servers.

GW & DPS on Primary Server

GW & DPS on Secondary Server

0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Hi,

There is issue with your NLB, check with your network team.

If they are not able to do then I can share NLB config document, email me on Mithilesh.Yadav@service-berry.com

 

View solution in original post

Highlighted
Super Contributor.
Super Contributor.

You need to add health check to NLB.

See 'Configure load balancing for gateway servers' Installation guide https://docs.microfocus.com/OMi/2019.05/OBM_Install_Upgrade/Content/OMi_install_upgr.htm

Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

@snikitin 

Hi Snikitin,

I didn't found any NLB related health check configuration in the provided document.

https://docs.microfocus.com/OMi/2019.05/OBM_Install_Upgrade/Content/OMi_install_upgr.htm

 

Regards,

Manideep

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Hi,

 

There will be three cause of this problem :

1st : LB configuration and 383 enabled for only secondary GW not for Primary as well running behind the LB.

2nd : check ovconfget setting and replace [sec.core.auth]  MANAGER=<secondary GW> instead of LB and see. If it will work then considered as LB issue.

3rd : Try bbcutilping to LB as well primary gateway with 383 port and see.

 

I hope above will help toward to resolution.


If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

Regards,

Hitesh Kumar
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

in my personal opinion the local Agent of any GW server should not point to the LB Adress, instead shuld point to the own GW server.

For me this solves some issues as my customers OMI Servers are located in a DMZ and so the LB Adrress handles only traffic from outside the DMZ.

 

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Yes, But ideally if you run the configure.wizard. It will replace LB FQDN automatically. 

In special case we can also divert through the their own gateway.


If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

Regards,

Hitesh Kumar
0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

@Mithilesh_Yadav 

Hi Mithilesh can you pls share those screen shots with me also pls we have same deployment and we are using f5 load balancer.

Is it possible to share screen shots of both end user lb and data collector lb configurations pls

2 OMi's in failover 

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.