SAP LaMa 3.0 Std reporting DBStatus read-only in SQL AOAG

[darenaddison]

Hi,

Our SAP R/3 landscape is built on MS Windows 2012r2 / MS SQL server 2012r2. For Pre-Production and Production we use MS SQL Always-On Availability Group clusters to provide highly available database and Central Instance services.
When connecting SAP LaMa to the database nodes, the databases are discovered, but as per design only the Active node is allowed to be Read-Write and the Passive node is Read-only.
This configuration is reported as a warning in SAP LaMa.

I would prefer not to suppress the DBSTATUS metric, but I do not see any other way to avoid the warnings.
Is there a better way?
Does anyone else use this configuration? How do other people handle this scenario?

Thanks,

Daren Addison.

[darenaddison]

Hi Kaushik,

Thanks for your quick response.

This method did work when first discovering connections were made to the database nodes, but having failed all instances to the other nodes we have these warnings.

We run services from either node with preference equal on cluster resources, what was discovered as secondary could be made primary and vice versa.

This is particularly of interest when we use SAP LaMa to control the planned outages for operating systems patching, the cluster resources will failover to the other nodes at least every 6-8 weeks.

Are there any other methods we could consider to keep the dashboard warning free?

We need to be able to see clearly that all instances are online following a planned outage, currently the warnings are a distraction.

Thanks,

Daren

[kaus19d]

Hi Daren,

Generally, if your regular tasks are getting obstructed by warnings, we can always select the Ignore Warning option. Generally while discovering, we make the 1st node as primary & so discover the 1st node on cluster as primary & likewise at the same time secondary as secondary host. While performing operations, once the activeTOpassive switch is done via Lama, at that time Lama already understands the secondaryHOST as primary & likewise the 1st ActiveNode at that time gets automatically recognised as passive node

If you have a demo system, you try this operation also

Thanks,

Kaushik

[kaus19d]

Hi,

If your 1st DB instance is set as primary & discovered as primary, i would suggest at that time of discovery to discover the passive node as secondary host while discovering & it will be fine

Thanks,

Kaushik