How to run an AppCritical Network Analysis test
The appCritical Network Analysis test will help identify issues in network performance between two systems. Performance is limited by the physical connection and depends on several factors including:
- The make/model of network cards.
- The mode/frame type configuration for the adapter.
- The connectivity equipment (hubs, switches, routers, and so on).
- Windows Settings.
- Local disk drives on the media server can usually be backed up at a faster than backing up remote servers across a network.
To run the application, please do the following:
Test to 192.168.1.1 failed. Could not connect to target.
Please check your target address.
1. Download the appCritical Standalone sequencer from the following link.
If the Linux distribution that is currently being used is not listed select Red Hat Enterprise Linux 4.0 (.tar.gz), this package works for most Linux distributions.
2. Open terminal then change directory to the directory the sas-linux.tar.gz file is located in. Then extract the files on the Linux machine that the test is going to be run on.
example: tar -zxf sas-linux.tar.gz
3. Verify the file sas-linux was extracted by running the command ls
4. Run the sequencer by using one of the following commands.
example: ./sas-linux 192.168.1.1
If Gigabit NIC cards are used, increase the burst size to 20 in order to get optimal results for high-speed paths: sas-linux <address_of_target_machine> -b 20
example: ./sas-linux 192.168.1.1 -b 20
5. When complete, the XML file(s) will be created in the "out" directory. Rename files to something meaningful, such as "Server3_to_Client.xml".
6. Optional: Compress (zip or tar/gzip) the XML files.
7. Contact technical support with the XML files from each server for review.
Appcritical Network test.
Also known as Apparent and AppNeta.