In order to gather the required data, the show tech command should be run from the ASA before and after the test. Therefore, the administrator can gather the required data in order to find the root cause. Most often the problem can be reproduced. Usually a network administrator is alerted to the problem when they perform a specific action, such as an FTP file transfer or an online speed test. In order to understand the exact cause of the problem, the data must show the actual TCP packets on the wire for that connection and how the network might affect them. TCP flows slow down when there is packet loss or packet delay on the network. Customer might raise a case with Cisco TAC because they believe the ASA caused the reduction in connection speed. The problem is the TCP throughput for connections that flow through the ASA is much lower than when the ASA is not in the connection path (or the connections are much slower than before the ASA was implemented in the network).įor example, a customer might replace a low-end D-Link router (or other routing device) with an ASA 5505 or an ASA 5510 however, once the router is replaced, connection speed is greatly reduced. Some customers might experience a problem when they first deploy an ASA or when they test new connectivity. If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. The information in this document is based on the Cisco Adaptive Security Appliance (ASA). There are no specific requirements for this document. This document describes how to troubleshoot Cisco Adaptive Security Appliance (ASA) throughput and connection speed issues.
0 kommentar(er)
