Expected output results for HAGetFailoverConfig.
This document (000019613) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension 12
SUSE Linux Enterprise Server for SAP Applications 15
SUSE Linux Enterprise Server for SAP Applications 12
Situation
For example:
# sapcontrol -nr 01 -function HAGetFailoverConfig 23.04.2020 15:29:48 HAGetFailoverConfig OK HAActive: FALSE HAProductVersion: HASAPInterfaceVersion: HADocumentation: HAActiveNode:Expected Result:
# sapcontrol -nr 01 -function HAGetFailoverConfig 23.04.2020 15:28:06 HAGetFailoverConfig OK HAActive: TRUE HAProductVersion: SUSE Linux Enterprise Server for SAP Applications 12 SP4 HASAPInterfaceVersion: SUSE Linux Enterprise Server for SAP Applications 12 SP4 (sap_suse_cluster_connector 3.1.0) HADocumentation: https://www.suse.com/products/sles-for-sap/resource-library/sap-best-practices/ HAActiveNode: clusterAn2 HANodes: clusterAn2, clusterAn1
Resolution
1. If the cluster is in maintenance-mode (cib-bootstrap option "maintenance-mode=true", then the results will not show here as it considers HAActive is false and doesn't continue.
Please set maintenance-mode to false and perform tests again.
# crm configure property maintenance-mode=false2. If your hostnames (virtual or nodes) have a "-" in the name, it's possible the sap_suse_cluster_connector is not parsing them properly.
This has been resolved a maintenance package >= sap-suse-cluster-connector-3.1.1-11.1
3. The <sidadm> user was not added to the haclient group.
If my <sidadm> user was nw1adm, I would add it on each node in the cluster with the following command.
# usermod -aG haclient nw1adm
Cause
Additional Information
# sapcontrol -nr 01 -function HACheckConfig 23.04.2020 15:35:28 HACheckConfig OK state, category, description, comment SUCCESS, SAP CONFIGURATION, Redundant ABAP instance configuration, 0 ABAP instances detected SUCCESS, SAP CONFIGURATION, Redundant Java instance configuration, 0 Java instances detected SUCCESS, SAP CONFIGURATION, Enqueue separation, All Enqueue server separated from application server SUCCESS, SAP CONFIGURATION, MessageServer separation, All MessageServer separated from application server SUCCESS, SAP STATE, SCS instance running, SCS instance status ok SUCCESS, SAP CONFIGURATION, SAPInstance RA sufficient version (sapnw1ascs_NW1_01), SAPInstance includes is-ers patch SUCCESS, SAP CONFIGURATION, Enqueue replication (sapnw1ascs_NW1_01), Enqueue replication enabled SUCCESS, SAP STATE, Enqueue replication state (sapnw1ascs_NW1_01), Enqueue replication active SUCCESS, SAP CONFIGURATION, Enqueue replication HA polling (sapnw1ers_NW1_11), HA polling interface configuredExpected results for HACheckFailoverConfig
# sapcontrol -nr 01 -function HACheckFailoverConfig 23.04.2020 15:36:18 HACheckFailoverConfig OK state, category, description, comment SUCCESS, SAP CONFIGURATION, SAPInstance RA sufficient version, SAPInstance includes is-ers patch
Reference Documentation:
Best Practices for SAP:
https://documentation.suse.com/sbp/sap/
SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster With Simple Mount - Setup Guide:
https://documentation.suse.com/sbp/sap/html/SAP-S4HA10-setupguide-simplemount-sle15/index.html
Manual page sap_suse_cluster_connector(8)
(man 8 sap_suse_cluster_connector)
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000019613
- Creation Date: 24-Apr-2020
- Modified Date:02-Dec-2022
-
- SUSE Linux Enterprise High Availability Extension
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com