|
Contents
- Configuring IP SLAs FTP Operations
- Finding Feature Information
- Restrictions for IP SLAs FTP Operations
- Information About IP SLAs FTP Operations
- FTP Operation
- How to Configure IP SLAs FTP Operations
- Configuring an FTP Operation on a Source Device
- Configuring a Basic FTP Operation on the Source Device
- Configuring an FTP Operation with Optional Parameters on the Source Device
- Scheduling IP SLAs Operations
- Troubleshooting Tips
- What to Do Next
- Configuration Examples for IP SLAs FTP Operations
- Example: Configuring an FTP Operation
- Additional References
- Feature Information for Configuring IP SLAs FTP Operations
Configuring IP SLAs FTP Operations
This module describes how to configure an IP Service Level Agreements (SLAs) File Transfer Protocol (FTP) operation to measure the response time between a Cisco device and an FTP server to retrieve a file. The IP SLAs FTP operation supports an FTP GET request only. This module also demonstrates how the results of the FTP operation can be displayed and analyzed to determine the capacity of your network. The FTP operation can be used also for troubleshooting FTP server performance.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Restrictions for IP SLAs FTP Operations
The IP SLAs FTP operation only supports FTP GET (download) requests.
Information About IP SLAs FTP Operations
FTP Operation
The FTP operation measures the round-trip time (RTT) between a Cisco device and an FTP server to retrieve a file. FTP is an application protocol, part of the Transmission Control Protocol (TCP)/IP protocol stack, used for transferring files between network nodes.
In the figure below Device B is configured as the source IP SLAs device and an FTP operation is configured with the FTP server as the destination device.
Connection response time is computed by measuring the time taken to download a file to Device B from the remote FTP server using FTP over TCP. This operation does not use the IP SLAs Responder.
Note | To test the response time to connect to an FTP port (Port 21), use the IP SLAs TCP Connect operation. |
Both active and passive FTP transfer modes are supported. The passive mode is enabled by default. Only the FTP GET (download) operation type is supported. The URL specified for the FTP GET operation must be in one of the following formats:
If the username and password are not specified, the defaults are anonymous and test, respectively.
FTP carries a significant amount of data traffic and can affect the performance of your network. The results of an IP SLAs FTP operation to retrieve a large file can be used to determine the capacity of the network but retrieve large files with caution because the FTP operation will consume more bandwidth. The FTP operation also measures your FTP server performance levels by determining the RTT taken to retrieve a file.
How to Configure IP SLAs FTP Operations
Configuring an FTP Operation on a Source Device
Note | There is no need to configure an IP SLAs responder on the destination device. |
Perform one of the following tasks:
- Configuring a Basic FTP Operation on the Source Device
- Configuring an FTP Operation with Optional Parameters on the Source Device
Configuring a Basic FTP Operation on the Source Device
DETAILED STEPS
Configuring an FTP Operation with Optional Parameters on the Source Device
DETAILED STEPS
Scheduling IP SLAs Operations
- ip sla schedule operation-number [life {forever | seconds}] [start-time {[hh:mm:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
- ip sla group schedule group-operation-number operation-id-numbers schedule-period schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life {forever | seconds}] [start-time{hh:mm[:ss] [month day | day month] | pending | now | after hh:mm[:ss]}]
DETAILED STEPS
Troubleshooting Tips
- If the IP SLAs operation is not running and not generating statistics, add the verify-data command to the configuration of the operation (while configuring in IP SLA configuration mode) to enable data verification. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.
- Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.
What to Do Next
To add proactive threshold conditions and reactive triggering for generating traps (or for starting another operation) to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section.
operation)
To display and interpret the results of an IP SLAs operation, use the show ip sla statistics command. Check the output for fields that correspond to criteria in your service level agreement to determine whether the service metrics are acceptable.
Configuration Examples for IP SLAs FTP Operations
Example: Configuring an FTP Operation
The following example shows how to configure an FTP operation from Device B to the FTP server as shown in the "FTP Operation" figure in the "Information About IP SLAs FTP Operation" section. The operation is scheduled to start every day at 1:30 a.m. In this example, the file named test.cap is to be retrieved from the host, cisco.com, with a password of abc using FTP in active mode.
Additional References
MIBs
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Configuring IP SLAs FTP Operations
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for the IP SLAs FTP Operation |
Feature Name |
Releases |
Feature Information |
---|---|---|
IP SLAs - FTP Operation |
12.2(31)SB2 12.2(33)SRB1 12.2(33)SXH 12.3(14)T Cisco IOS XE Release 2.1 15.0(1)S Cisco IOS XE Release 3.1.0SG |
The IP SLAs File Transfer Protocol (FTP) operation allows you to measure the network response time between a Cisco device and an FTP server to retrieve a file. |
IPSLA 4.0 - IP v6 phase2 |
15.2(3)T 15.2(4)S Cisco IOS XE release XE 3.7S 15.1(2)SG Cisco IOS XE Release 3.4SG |
Support was added for operability in IPv6 networks. The following commands are introduced or modified: ftp get (IP SLA), show ip sla configuration, show ip sla summary. |
IP SLAs VRF Aware 2.0 |
12.4(2)T 15.1(1)S 15.1(1)SY Cisco IOS XE Release 3.8S |
Support was added for IP SLAs VRF-aware capabilities for TCP connect, FTP, HTTP and DNS client operation types. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.