Chapter 1. Introduction

ESXi Introduction

Hx Workload Profiler is a VMware vCenter characterization tool that can estimate the compute, storage, and network usage of hosts and VMs across multiple vCenter deployments. The output of the tool can be fed into HxSizer product to size the HyperFlex cluster requirements. The workload requirements are estimated by the HxProfilertool.

Hx Workload Profiler key outputs:

- 30-day historic summary of host-level compute metrics

- Detailed compute, storage, and network metrics for hosts and VMs for all vCenters profiled

- Detailed time series data to analyze trends of key metrics in the UI

- Download of time series data of all key metrics

The Hx Workload Profiler tool is delivered as an OVA and can be used to monitor multiple vCenters simultaneously.

Chapter 2. System Requirements

- ESXi System Requirements

ESXi System Requirements

Requirement

Description

ESXi version

v5.5 or later

OVA size

- vCPU: 4

- RAM: 8 GB

- Disk: 100 GB (thin provisioning supported). It is recommended that you use thin provisioning while deploying the VM.

Scale for end-points

- Maximum number of simultaneous vCenters: 16

- Maximum number of hosts: 200

- Maximum number of VMs: 4000

Credentials

- Root/admin credentials

Browser support

- Chrome: Chrome version 50 or later

- Firefox: Unsupported

- IE: Unsupported

- Safari: Unsupported

Chapter 3. Setting Up the Virtual Appliance

- HX Profiler Software License

Logging in to the ESXi Profiler

The Hx Workload Profiler user interface (UI) uses system credentials for authentication.

Procedure

Step 1

To access the UI, launch a browser window and enter http://<IP> or http://<IP:8000> or http://<IP>/profiler/index.html or http://<IP:8000>/profiler/index.html, where the IP is the IP address of the VM.

The HX Profiler UI appears:

Step 2

When prompted, log in to the UI with the following credentials:

User name: monitoring

Password: <new password set during the install workflow>

Step 3

You can use the User Preference option in the top right corner of the UI to configure Language or Theme.

Click Cancel or Save to continue.

Step 4

When finished, you can end the user session by clicking Logout at the top right of the page.

HX Profiler Software License

The lifespan of the HX Profiler Software License is 45 days from the date of deployment. The HX Profiler displays a Software Expiration warning message after 30 days have elapsed after deployment.

Deploying the ESXi Virtual Machine

Procedure

Step 1

Log in to VMware vSphere Client.

Step 2

Select File > Deploy OVF Template.

Step 3

Select the OVA file you want to deploy from the Select an OVF template option.

Step 4

Click Next, review the OVF template details, and then click Next again.

Step 5

On the Select a name and folder page, specify the name and location for the virtual appliance, and then click Next.

Step 6

On the Select storage page, specify the storage for the configuration and disk files, and then click Next.

Step 7

On the Select networks page, specify the destination network for each source network, and then click Next.

You can configure either DHCP or a static IP address for the VM.

(Mandatory) You must change the system password for default user monitoring in the System Password fields.

Step 8

On the Ready to Complete page, review your deployment settings, select Power On After Deployment, and then click Finish.

What to do next

You must wait for the deployment task to complete. On completion, a successful deployment message displays.

If the IP address has not been assigned after the OVA deployment, reboot the HxProfiler VM.

Configuring and Using the ESXi Profiler Application

Perform the Hx Workload Profiler application configuration and operations from the web-based UI.

The following table shows the high-level steps for configuring the application.

Task

See

Addition of a poller, which is referred to as a workload or node.

Adding vCenter to the ESXi Profiler

Configuration of the profiling attributes.

Starting ESXi Data Profiling

Start the polling operation.

Starting the Profiler Service

Configuring and Using the Windows Bare Metal Profiler Application

Perform the Hx Workload Profiler application configuration and operations from the web-based UI.

The following table shows the high-level steps for configuring the application.

Task

See

Addition of a poller, which is referred to as a workload or node.

Adding Windows Bare Metal to the Profiler

Configuration of the profiling attributes.

Starting Windows Bare Metal Data Profiling

Start the polling operation.

Starting the Profiler Service

Configuring and Using the Linux Bare Metal Profiler Application

Perform the Hx Workload Profiler application configuration and operations from the web-based UI.

The following table shows the high-level steps for configuring the application.

Task

See

Addition of a poller, which is referred to as a workload or node.

Adding Linux Bare Metal to the Profiler

Configuration of the profiling attributes.

Starting Linux Bare Metal Data Profiling

Start the polling operation.

Starting the Profiler Service

Using the Profiler Service

The Hx Workload Profiler start and stop services use the profiler_service.sh command.

The following table shows the high-level steps for using the profile service.

Task

See

Starting the Profiler Service

Starting the Profiler Service

Stopping the Profiler Service

Stopping the Profiler Service

Restarting the Profiler Service

Restarting the Profiler Service

- Starting the Profiler Service

- Stopping the Profiler Service

- Restarting the Profiler Service

Starting the Profiler Service

To start the profiler service:

Procedure

Run the following command: sudo service hxpmonitor start.

Stopping the Profiler Service

Complete the following steps to stop the profiler service:

Procedure

Step 1

Run the following command: sudo service hxpmonitor stop.

Step 2

Run the following command: sudo service hxpcontroller stop.

Restarting the Profiler Service

Complete the following steps to restart the profiler service:

Procedure

Step 1

Run the following comand: sudo service hxpcontroller restart.

Step 2

Run the following comand: sudo service hxpmonitor restart.

Locating the ESXi Application Logs

You can find Hx Workload Profiler logs in the following locations:

Application Logs

Log

Path

Server

/home/monitoring/monitor/server.log

Controller

/home/monitoring/controller/logs/*

Monitor

/home/monitoring/monitor/monitor/monitor.log

Chapter 4. Configuring and Using the Profiler Application

Adding vCenter to the ESXi Profiler

At the first login following installation of Hx Workload Profiler, you are redirected to the landing page where you can find the + Add Workload option on the top right corner of the page. You can select vCenter, then you can add multiple vCenters.

To calculate the metrics for a host, the Profiler captures the metrics for all the VMs on the Host. You then need to select the VM to be profiled. By default none of the VM’s are selected.

The workflow includes:

- Node details tab: Records your vCenter details and then connects to the vCenter. If the connection succeeds, the Next button displays enabling you to select the hosts for profiling.

- Select Hosts tab: Provides the vCenter details in hierarchy of vCenter, Datacenters, Clusters, and Hosts, with the option to select hosts to Profile. Default: All hosts in vCenter are selected.

- Profiling Setting tab, which provides:

- Profile Name: for specifying the name of the profile which must be unique.

- Profile period: for specifying the period of profiling. Default value is 7days and the minimum value is 1day.

- Polling Interval: for specifies the frequency for which polling should occur.

- Quick Profile: for a quick estimate

- Detailed Profile: for detailed end-to-end profile results.

Procedure

Step 1

Log in to the Profiler. See Logging in to the ESXi Profiler.

Step 2

Follow the steps provided to enter values for the following options:

Item

Description

vCenter Name

Name of the vCenter you are adding.

User Name

Name of the user as part of the login credentials for the vCenter.

Note

HX Profiler uses VMware SDK to collect different performance metrics. To get the performance data, the user account connecting to the VMware vSphere must have administrator privileges.

Password

The password set as part of the login credentials for the vCenter.

Polling Interval

The interval at which you want polling to occur. The default is 20 seconds. You can change the interval to between 20-120 seconds, based on the number of hosts and VMs being polled in that vCenter.

Step 3

Click Start Profiling. The Profiler service starts automatically.

When the connection status indicates successful connection, click Next.

Step 4

On the Poll filter tab, review the hierarchy values.

Adding Windows Bare Metal to the Profiler

At the first login following installation of Hx Workload Profiler, you are redirected to + Add Workflow. You can select Windows Bare Metal to add Windows Bare Metal to the workload.

Procedure

Step 1

Log in to the Profiler.

Step 2

On the Node details tab, enter values for the following options:

Item

Description

Windows Cluster Name

Name of the cluster you are trying to add

Host Name/IP Address

To enter a single host / different IPs

IP Address Range

To enter a range of VM IPs

User Name

Login username for windows baremetal

Note

The username must have the administrator role assigned to it.

Password

Login password for windows baremetal

Polling Interval (seconds)

Default 20 seconds

Step 3

If you select the Host Name/IP address option, click Save. If the given credentials / IP is valid, then workload will be added successfully. In case of any error, recheck and update the provided details, then click Save to add the workload successfully.

Step 4

If you select the IP Address Range, click Validate. Given IP range and credentials are validated, and if any of the VMs are not reachable, any error details will be updated in tabular format.

Step 5

If no errors are observed, click Save. If there are errors, please check the respective error VM details, rectify them manually and then click on Revalidate. Click Save to add the workload.

Adding Linux Bare Metal to the Profiler

At the first login following installation of Hx Workload Profiler, you are redirected to + Add Workflow. You can select Linux Bare Metal to add Linux Bare Metal to the workload.

Procedure

Step 1

Log in to the Profiler.

Step 2

On the Node details tab, enter values for the following options:

Item

Description

Linux Cluster Name

Name of the cluster you are trying to add

Host Name/IP Address

To enter a single host / different IPs

IP Address Range

To enter a range of VM IPs

User Name

Login username for Linux baremetal

Password

Login password for Linux baremetal

Polling Interval

Default 20 seconds

Step 3

If you select the Host Name/IP address option, click Save. If the given credentials / IP is valid, then workload will be added successfully. In case of any error, recheck and update the provided details, then click Save to add the workload successfully.

Step 4

If you select IP Address Range, click Validate. Given IP range and credentials are validated, and if any of the VMs are not reachable, any error details will be updated in tabular format.

Step 5

If no errors are observed, click Save. If there are errors, please check the respective error VM details, rectify them manually and then click on Revalidate. Click Save to add the workload.

Starting ESXi Data Profiling

Following the successful addition of a vCenter Server, the new vCenter displays on the Data Inventory (home) page. You configure the profiling attributes by providing the profile name and duration.

Profiling Operation Options

Item

Description

Delete (trash can)

Deletes a previously added vCenter.

Edit (pen)

Edit vCenter properties to add or remove hosts for polling.

Stop ( || symbol)

Stops the profiling so you can resume it later.

Reset (refresh symbol)

Performs a reset operation, which creates a new profile and starts polling. When you trigger reset, the profiler stops the active/running profile and creates a new one. A prompt asks for confirmation.

View Collection

Opens the View Collection page so you can browse through the collected data as part of the profiling to review the HOST and VM level data.

Polling starts as soon as you enter the profiler name ,days and polling period.

Procedure

Step 1

In the dialog that displays, perform the following steps:

1. Enter a name for the profile.

2. Select a duration value from the Profiling Period down-drop list.

3. Click Ok.

Following successful profile creation, the Profiler begins polling the selected hosts and all the VMs on those hosts. When the polling starts, the data collector runs as a background process. The Datacenter Inventory page displays information about the hosts and polling, showing number of hosts and the status of the polling.

Step 2

(Optional) To stop an in-progress profiling operation so you can resume it later, see Stopping the Profiler Service.

Step 3

(Optional) To stop an in-progress profiling operation, click Reset. You can then start a new one.

Step 4

(Optional) To browse through the collected data, see Viewing an ESXi Collection.

Step 5

(Optional) To download profiling data, see Downloading ESXi Profiling Results.

Starting Windows Bare Metal Data Profiling

Following the successful addition of a Windows Bare Metal, the newly added Windows Bare Metal displays on the Data Inventory (home) page. You can configure the profiling attributes by providing the profiling name and duration.

Profiling Operation Options

Item

Description

Delete (trash can)

Deletes the selected Windows Bare Metal workload / node

Edit (pen)

Edit Windows Bare Metal to add / remove existing VM/hosts for profiling.

Stop ( || symbol)

Stops the profiling

Refresh

Performs a reset operation, which creates a new profile and starts the polling. When reset is clicked, profiler stops the active/running profile and creates a new one. A prompt asks for confirmation.

View Collection

Opens the View Collection page so you can browse through the collected data as part of the profiling to review the HOST and VM level data.

Procedure

Step 1

(Optional) To stop an in-progress profiling operation so you can resume it later, see Stopping the Profiler Service

Step 2

(Optional) To stop an in-progress profiling operation, click Reset. You can then start a new one.

Step 3

(Optional) To browse through the collected data, see Viewing an ESXi Collection.

Step 4

(Optional) To download profiling data, see Downloading ESXi Profiling Results.

Starting Linux Bare Metal Data Profiling

Following the successful addition of a Linux Bare Metal, the newly added Linux Bare Metal displays on the Data Inventory (home) page. You can configure the profiling attributes by providing the profiling name and duration.

Item

Description

Delete (trash can)

Deletes selected Linux Bare Metal workload / node

Edit (pen)

Edit Linux Bare Metal to add / remove existing VM/hosts for profiling.

Stop ( || symbol)

Stops the profiling

Refresh

Performs a reset operation, which creates a new profile and starts the polling. When reset is clicked, profiler stops the active/running profile and creates a new one. A prompt asks for confirmation.

View Collection

Opens the View Collection page so you can browse through the collected data as part of the profiling to review the HOST and VM level data.

Procedure

Step 1

(Optional) To stop an in-progress profiling operation so you can resume it later, see Stopping the Profiler Service

Step 2

(Optional) To stop an in-progress profiling operation, click Reset. You can then start a new one.

Step 3

(Optional) To browse through the collected data, see Viewing an ESXi Collection.

Step 4

(Optional) To download profiling data, see Downloading ESXi Profiling Results.

Downloading ESXi Profiling Results

Procedure

Step 1

On the Datacenter Inventory page, locate and select the profile whose data you want to download.

Step 2

Use the Download option to select one of the following:

Option

Description

All Data Collection

Downloads 30-day host summary, time series, and CVS for both the host and VM

Summary Report for HxSizer Upload

Collects the historic 30-day information from vCenter and does not require any active polling. The download provides the output in CSV format and can be directly uploaded to the Compute and Capacity Workload of HxSizer.

Profiler Sample Data

Downloads the sampled data for the selected profile in the following formats:

- Summarized host data (CVS)

- Summarized VM data (CVS)

- Time series data of host (zipped CSV file)

- Time series data of VM (zipped CSV file)

Profiler Summary PDF

PDF download

Step 3

You can still download the profiling results when viewing the compute, storage and network data of various hosts and VMs by clicking on the Download button on the top right corner of the UI.

Viewing ESXi Data Collections from vCenter Servers

The View Collection page has five tabs at the top left of the page, Overview, Host Compute Metrics, Host Storage Metrics, VM Compute Metrics, VM Storage Metrics. When clicked, they show summary data described in his section. The View Collection page also provides the summarized data for Compute Summary and Storage Summary of individual host and VMs. You can also fetch the data for specific period of profiling using the predefined filter present on the top right corner of the page with the minimum being 30minutes or the user can also use the time line to select the time period. The following sections describe the summary data shown through filter tool use and in that shown in each tab and view.

Host View Filter Options

Item

Description

Aggregation

Filters to view the summarizations based on peak or average selections. Your selection determines the display of the table metrics and trends. The summarized values represent the following:

- Peak: Peak value of all the metrics in the selected interval

- Average: Averages of all the values in the selected interval

You can filter Host metrics using the search option by host name only. For VM metrics, you can filter either by the Host name to which the VM belongs or directly with the VM name, using the search option.

Host and VM Summarized Metrics

Based on your time period and parameters selections, the Profiler computes and populates the compute and storage metrics. Metrics display for the following values:

Host View Compute Table

- Host_Name

- Processor Type

- Clock (GHz)

- #Physical Cores

- HT – ON/OFF

- CPU Util (MHz)

- CPU Util (%)

- #VMs

- vCPU of active VMs/pCore Ratio

- RAM (GB)

- RAM Util (GB)

- Network Throughput- Rx (Mbps)

- Network Throughput- Tx (Mbps)

Host View Storage Table

- Provisioned Capacity (TB)

- Used Storage Capacity (TB)

- Read Throughput (MBps)

- Write Throughput (MBps)

- Read (%)

- Write (%)

- Read IOPS

- Write IOPS

- Read Block Size (KB)

- Write Block Size (KB)

- Seq (%)

- Read Latency (ms)

- Write Latency (ms)

VM View Compute Table

- VM Name

- Status

- Host_Name

- vCPUs

- CPU Util (MHz)

- CPU Util (%)

- RAM (GB)

- RAM Util (GB)

- Network Throughput- Rx (Mbps)

- Network Throughput- Tx (Mbps)

VM View Storage Table

- VM Name

- Host_Name

- Disk Capacity (GB)

- Disk Used (GB)

- Read Throughput (MBps)

- Write Throughput (MBps)

- Read (%)

- Write (%)

- Read IOPS

- Write IOPS

- Read Block Size (KB)

- Write Block Size (KB)

- Seq (%)

- Read Latency (ms)

- Write Latency (ms)

Host and VM Trends

The View Collection page provides trend charts and an overview of various parameters at a host level and VM level for both compute and storage parameters. The overview provides information aggregate storage and compute matrix along with a 30-day sizing summary. You can view the trend charts by selecting the host or the VM from the table.

Metrics for the following values display in the trend charts:

Host View Compute Trends

- CPU Utilization (MHz)

- CPU Utilization (%)

- CPU Overprovisioning Ratio (%)

- RAM Utilization (%)

- RAM Overprovisioning Ratio (%)

- Receive Rate (Mbps)

- Transmit Rate (Mbps)

VM View Compute Trends

- Receive Rate (Mbps)

- Transmit Rate (Mbps)

Host and VM View Storage Trends

- Read Throughput (MBps)

- Write Throughput (MBps)

- Read Ratio

- Write Ratio

- Read IOPS

- Write IOPS

- Read Seq (%)

- Write Seq (%)

- Read Latency (ms)

- Write Latency (ms)

- Provisioned Capacity (TB)

- Used storage Capacity (TB)

Histogram Charts

- Read Block Size Histogram

- Write Block Size Histogram

Note

You can plot the storage parameter charts for two comparable charts either from the Trend Line chart or from the Histogram chart.

- Viewing an ESXi Collection

Viewing an ESXi Collection

You can also use the filter and search tool in the Hosts and VM views to display only those hosts and VMs that you want to see.

You can also use the filter tool in the Hosts and VM views to display only those hosts and VMs you want to see.

Procedure

Step 1

In the Datacenter Inventory page, click View Collection to browse through the collected data.

Step 2

In the View Collection page, select between Host Compute Metrics, Host StorageMetrics, VM Compute Metrics or VM Storage Metrics.

Step 3

In the Select VMs tab, select or unselect the toggle switch for the VMs you want to view, then click Next. All VMs are selected by default.

Step 4

To view data for a different time period, select from the options in the top right corner with the default minimum value of 30 minutes. Use the time slider above the fixed time period selection to view data for a specific time range from the selected time period.

Upload 30-Days Sizing Summary Report

You can upload the 30-Days Sizing Summary Report to the HxSizer application from HxProfiler. When the report upload is successful, a reference number is generated. View the history of uploads along with the reference number from the HxProfiler application. In addition to identifying the report, the refence number may be used to claim the scenario from the HxSizer application.

Perform the following steps in the Cisco HX Profiler dashboard to upload the 30-Days Sizing Summary report:

Procedure

Step 1

Click the Upload icon on the HX Profiler ribbon and select Upload To HXSizer. The Upload Summary Report To HXSizer window appears.

Step 2

Click the Browse button to navigate to the local .csv file that needs to be uploaded to the HXSizer portal.

1. Select the desired .csv file.

2. (Optional) To modify the csv file name, type a new name in the Rename selected .csv file name field.

3. Click Upload.

A reference number indicates a successful upload. Use the Copy button to copy the reference number and use it to claim the scenario in the HXSizer application.

Step 3

(Optional) View Upload History

1. Click the Upload icon on the HX Profiler ribbon and select Upload History to view the list of 30-Days sizing summary .csv files that have been uploaded to the sizer application from profiler.

Chapter 5. Monitoring Approach

- Download Quick Profile (30-Days) ESX Host Summary Statistics and Data

Download Quick Profile (30-Days) ESX Host Summary Statistics and Data

You can download the Quick Profile (30-days) ESX Host Summary statistics/data report from the Profiler Home page > Download Results option. To use this monitoring option, see Downloading Nutanix AHV Profiling Results for ESXi.

Report characteristics:

- Includes VM/host level compute and storage capacity metrics

- Does not include deep storage or compute metrics or metrics for individual VMs

- Data downloads in CSV format and can be uploaded to the Compute and Capacity workload in the Hx Sizer tool

Understanding the ESXi Profiler Data Collection Architecture

The Profiler connects to vCenter using the root admin credentials.

Architecture characteristics:

- The Profiler directly collects the vCenter Inventory information (Data Centers, Datastores, Clusters, Hosts, VMs, and basic metrics) and the compute metrics from vCenter itself.

- The Profiler also collects deep storage metrics for each VM and aggregates these metrics at a host-level.

- The vCenter does not directly maintain deep storage metrics. The Profiler software invokes vCenter to fetch this data from each individual host (using vSCSI) to obtain detailed data for each VM. The Profiler then summarizes the data from all VMs to build a host-level summary. For example, the software obtains maximum, minimum, and average values for metrics, such as latency, where as IOPS (Total Blocks/Interval) and throughput (Total Bytes/Interval) are average values only.

Performing ESXi Profiler VM Clean-up

After you complete your profiling activitites, follow the best practice of performing the Profiler VM clean-up to achieve a thorough shutdown and exit of the Profiler.

Procedure

Step 1

Download the profiled data with the following steps:

1. Launch the Profiler application.

2. Download the data (CSV format) from the Home page. See Downloading ESXi Profiling Results.

3. Save the CSV for further analysis.

Step 2

To stop the Profiler Service, run the following commands:

1. sudo service hxpmonitor stop

2. sudo service hxpcontroller stop

Step 3

Shut down the VM.

Step 4

Delete the VM if it is no longer required to profile the data for the environment.

Chapter 6. Troubleshooting

- Troubleshooting

Troubleshooting

Troubleshooting Section for vCenter

1. If the selected hosts are not reachable, then perform the following steps:

- Check the connection status of the hosts in vCenter.

- Make sure all the selected hosts connection status is Connected.

2. If you forgot the Profiler VM password, then perform the following step:

- Delete the old deployed machine and redeploy the new one.

Troubleshooting Section for Windows Bare Metal

1. When adding Windows Bare Metal Host, if you receive a Getting Invalid Username and Password Combination error, take the following steps in the Windows Bare Metal machine:

- Open Registry Editor: right click the Start button, select Run, type regedit and press Enter().

- Go to Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\AppCompat.

- Right click AppCompat -> New -> Dword.

- Enter RequireIntegrityActivationAuthenticationLevel as Value name.

- The Value Data should be Hexadecimal 0x00000000 (0).

Note

After setting this registry key, for it to take effect, you must restart your device.

Communications, Services, Bias-free Language, and Additional Information

- To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.

- To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.

- To submit a service request, visit Cisco Support.

- To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco Marketplace.

- To obtain general networking, training, and certification titles, visit Cisco Press.

- To find warranty information for a specific product or product family, access Cisco Warranty Finder.

Documentation Feedback

To provide feedback about Cisco technical documentation, use the feedback form available in the right pane of every online document.

Cisco Bug Search Tool

Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.

Bias-Free Language

The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on standards documentation, or language that is used by a referenced third-party product.

Full Cisco Trademarks with Software License

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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.

All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.

Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.

The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on standards documentation, or language that is used by a referenced third-party product.

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: https://www.cisco.com/c/en/us/about/legal/trademarks.html. 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. (1721R)