Hello everyone, and welcome back to the blog!
Quick update: I've been helping a friend troubleshoot a frustrating connectivity issue with their SAP system on AWS. Every time the system reboots, the connection drops. Here's what we've tried so far.
sc create SAPRouter binPath="C:\saprouter\saprouter.exe service -r -R C:\saprouter\saprouttab" start=auto obj="NT AUTHORITY\LocalService"
As you can see the a new service called SAP Router is added as local service and it is managed by Windows.
3. Review the network configuration in AWS, the next image shows the architecture, there is a VPC with two subnets (one public and another private), the user access from Internet to connect with the Bastion Host and this one is used to redirect the traffic to the SAP server using the SAP Router:
To keep it simple, this is the checklist to complete the configuration:
4. An extra tip, to validate the connectivity from the Bastion host to the App server a simple test can be executed in AWS, go to VPC > Network Analyze > Reachability Analyzer > Create and analyze path, in source type select the Bastion instance and the target the App server with the port 3299, when the analyze is finished the path is showed with all network components in AWS.
This network configuration overview has been simplified for brevity. Further details can be provided upon request. Thank you.😊😎
References
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 34 | |
| 25 | |
| 17 | |
| 16 | |
| 16 | |
| 15 | |
| 13 | |
| 13 | |
| 12 | |
| 12 |