NetworkCheck Utility (not only) for SAP Mobile Platform
Ever greater focus on network communication
When dealing with any complex system landscape, network communication problems are one of the challenges companies face to keeping their system functional. Adding mobile technology to the mix puts an ever greater focus on network communication and implies the occasional need to trace issues.
To detect and find any interruption in network communication is very challenging. Sometimes when you are involved in a complex problem, going back to the basic and thinking outside the box is the key to figure out the problem and the cause: This is why SAP Active Global Supported created the NetworkCheck utility!
SAP was working on a very difficult situation when the SAP Mobile Platform (SMP) server was failing to be part of the cluster. This issue was happening randomly. We figured out after debugging that this issue was related to a network problem, ant that our solution – SMP – was working just fine.
In order for us to prove our theory, we developed a tool called NetworkCheck utility.
NetworkCheck utility is intended for customers and partners to analyze the behavior of their networks, to identify issues that cause TCP/IP socket collection failures and breakages. Such network issues can adversely impact many SAP solutions, and it is valuable to have an utility that is independent of the SAP solutions so that customers and partners can clearly differentiate network issues from SAP issues. This utility was indeed developed by SAP.
NetworkCheck Utility published on github
Because of the success that we had with this tool, SAP decided to share it with the community. This tool is available in the SAP Open Source community
under the section “SMPServer Utilities.“
This tool does not depend on any specific products. If you are trying to prove if there is a network communication problem across the machines, or VMs,
then this tool is the one for you. All the details and how to run this utility are located in the github link that was provided above.
Here is a quick example of what this tool will do:
- Each second, each host will send a single byte to each other host, and then try to read a one byte response.
- Errors are reported if the tool:
- Cannot connect from one host to another
- Gets an error when writing one-byte request to another host.
- Gets an error when reading one-byte response from another host.
- Takes more than 10 seconds to read one-byte response from another host.