A company has implemented its ERP system on SAP S/4HANAon AWS. The system is based on Enqueue Standalone Architecture (ENSA2) and is highly available. As part of an availability test, the company failed over its system to secondary nodes in the second Availability Zone. When the system failed over, the initial licenses were no longer valid. What could be the reason for this behavior?
Select an option, then click Submit answer.
Reference / correct answer:
The company needs two separate sets of licenses for ASCS instances in each Availability Zone.
Most accepted answer: C. The company needs two separate sets of licenses for ASCS instances in each Availability Zone.
Community votes: B=1, C=1
Answer.C Every SAP system needs a central license, which is determined by the environment of the message server. Since SAP's high-availability (HA) solution stipulates 2 or more cluster nodes (host machines) where the message server is enabled to run, you have to order as many license keys as you have cluster nodes. When we receive confirmation from your vendor that you are implementing a switchover environment, we provide the required license keys for your system, 1 key for each machine. SAP has implemented a license mechanism for transparent and easy use with switchover solutions and clustered environments. Your customer key is calculated on the basis of local information on the message server host. This is the host machine where the ABAP central services instance (ASCS instance) runs. There is no license problem when only the database is switched over. upvoted 5 times
C. After failover you're expected to run with the temp license. Otherwise, a separate permanent license is needed on the DR instance. https://docs.aws.amazon.com/sap/latest/general/slas-licenses.html upvoted 2 times
Selected Answer: C C... Each ASCS node needs separate license.. upvoted 3 times
Selected Answer: B B: This option is incorrect because SAP licenses are typically bound to a system ID (SID), and are not bound to a specific machine or instance. In a High Availability setup, the SAP system, including the ASCS instances, has the same SID on both the primary and secondary nodes. Therefore, the same license should work for both nodes. SAP does not require separate licenses for each ASCS instance in each Availability Zone. The licensing of SAP systems is based on the SAPS (SAP Application Performance Standard) capacity of the system and the number of users that will be accessing the system, not the number of instances or servers that the system is running on. Therefore, having separate ASCS instances in different Availability Zones for High Availability purposes should not require additional SAP licenses. upvoted 1 times kaishin0527 3 years ago I mistakenly posted the reason why it is not C. I will repost it. upvoted 1 times kaishin0527 3 years ago The correct answer is B. "The cluster configuration is not correct." In a properly configured High Availability (HA) setup, SAP license keys (which are bound to the SAP System ID, not to a specific server or IP address) should remain valid after failover. If the license becomes invalid after failover, it likely indicates an issue with the cluster configuration. A common problem might be that the Secondary node was not properly recognized as a part of the cluster and thus when failover happened, it couldn't recognize the valid license. upvoted 1 times ... ...
I mistakenly posted the reason why it is not C. I will repost it. upvoted 1 times kaishin0527 3 years ago The correct answer is B. "The cluster configuration is not correct." In a properly configured High Availability (HA) setup, SAP license keys (which are bound to the SAP System ID, not to a specific server or IP address) should remain valid after failover. If the license becomes invalid after failover, it likely indicates an issue with the cluster configuration. A common problem might be that the Secondary node was not properly recognized as a part of the cluster and thus when failover happened, it couldn't recognize the valid license. upvoted 1 times ...
