www.cisco.com Open in urlscan Pro
2a02:26f0:3500:893::b33  Public Scan

Form analysis
0 forms found in the DOM

Text Content

 * Skip to content
 * Skip to search
 * Skip to footer

 * Cisco.com Worldwide
 * Products and Services
 * Solutions
 * Support
 * Learn
 * Explore Cisco
 * How to Buy
 * Partners Home
 * Partner Program
 * Support
 * Tools
 * Find a Cisco Partner
 * Meet our Partners
 * Become a Cisco Partner

 * 
 * Support


CUSTOMER FILE UPLOADS TO CISCO TECHNICAL ASSISTANCE CENTER

Save
Log in to Save Content

Translations

Print


AVAILABLE LANGUAGES

 * Arabic - عربي
 * Brazil - Português
 * Canada - Français
 * China - 简体中文
 * China - 繁體中文 (臺灣)
 * Germany - Deutsch
 * Italy - Italiano
 * Japan - 日本語
 * Korea - 한국어
 * Latin America - Español
 * Netherlands - Nederlands

Updated:April 12, 2024
Document ID:1510676978683359
Bias-Free Language


BIAS-FREE LANGUAGE

The documentation set for this product strives to use bias-free language. For
the 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 RFP documentation, or language that is used by a
referenced third-party product. Learn more about how Cisco is using Inclusive
Language.


CONTENTS

Introduction
Overview
Support Case Manager File Upload
      Uploading a File to a Case
Customer eXperience Drive
      Service Summary
      Supported Protocols
      CXD Upload Token
      Retrieving the Upload Token for an SR
           Using SCM
           Using the API
      Uploading Files to CXD
           Using Desktop Clients
           Directly from a Cisco Device
           File Upload API
           Sample Python Code to use the PUT API
Email File Attachment Uploads
Encrypting Files
      Encrypting Files Using WinZip
      Encrypting Files Using Tar and OpenSSL
      Encrypting Files Using Gzip and GnuPG
Communicating the Password to the TAC Customer Support Engineer
Customer Case Attachments Data Management
Summary
Additional Information



INTRODUCTION

This document describes how to upload files to Cisco Technical Assistance Center
(TAC).


OVERVIEW

The TAC customer support engineers can assist you with resolving an issue in a
timely manner when they have relevant files attached to the issue. You have
several options to upload the files related to your issue. Some of these options
are less secure, and can lead to certain inherent risks, and each option has
limitations that you need to consider before deciding on an appropriate upload
option. Table 1 summarizes the available upload options with details on file
encryption capabilities, recommended files size limits, and other relevant
information.

Table 1. Available Upload Options

Available Option (In Order of Preference) Files are Encrypted in Transit Files
are Encrypted at Rest Recommended File Size Limit Support Case Manager (SCM)
How To
Yes
Yes
No limit
Customer eXperience Drive
How To
Yes*
Yes
No limit
Email to attach@cisco.com
How To
No**
Yes
20 MB or less based on customer mail server limits

*Applies to all protocols except FTP. When using FTP, it is highly recommended
that the data is encrypted before being uploaded.

**You must encrypt prior to transit. Secure transit is guaranteed only from the
point where the email/attachment reaches the Cisco network, not on the customer
network or email provider side.


SUPPORT CASE MANAGER FILE UPLOAD

The Support Case Manager (SCM) file upload method is a secure option for
uploading files to cases. The communication channel between your computing
device and Cisco is encrypted. Files uploaded through SCM are immediately linked
to the associated case and stored in an encrypted format.


UPLOADING A FILE TO A CASE

After you submit the case, you can upload files.

Step 1. Log in to SCM.

Step 2. In order to view and edit the case, click the case number or case title
in the list. The Case Summary page opens.

Step 3. Click Add Files in order to choose a file and upload it as an attachment
to the case. The system displays the SCM File Uploader tool.



Step 4. In the Choose Files to Upload dialog box, drag the files that you want
to upload or click inside to browse your local machine for files to upload.

Step 5. Add a description and specify a category for all files, or individually.

Note: In order to optimize the upload settings for your network condition,
click Optimize Upload Settings.

Step 6. Click Upload in order to start the upload process.



Step 7. Once all uploads are complete, you can close the window or click Add
More Files in order to upload more files.



Step 8. Uploaded files can be managed in the Attachments tab.



Return to Top


CUSTOMER EXPERIENCE DRIVE


SERVICE SUMMARY

The Customer eXperience Drive (CXD) is a multi-protocol file upload service with
no limitation on the uploaded file size. It helps Cisco customers with active
Service Requests (SRs) to upload data directly to a case using a unique set of
credentials created per SR. The protocols supported by CXD are natively
supported by Cisco products which allows for uploading directly from Cisco
devices to SRs.


SUPPORTED PROTOCOLS

Table 2 summarizes the protocols supported by CXD. It is worth noting that
regardless of the protocol used, there is no limit set on the uploaded file
size.

Table 2. CXD Supported Protocols

Name Protocol/Port Encrypted Data Channel Ports Notes Secure File Transfer
Protocol (SFTP)
TCP/22
Yes
N/A
  Secure Copy Protocol (SCP)
TCP/22
Yes
N/A
  Hyper Text Transfer Protocol over SSL (HTTPS)
TCP/443
Yes
N/A
Only API-based uploads are supported. File Transfer Protocol of SSL (FTPS)
Implicit
TCP/990
Yes
30000-40000
Firewalls cannot inspect FTPS, as the control channel is encrypted. Hence, the
firewall needs to allow outbound connectivity to the entire data channel port
range. File Transfer Protocol of SSL (FTPS) Explicit
TCP/21
Yes
30000-40000
File Transfer Protocol (FTP)
TCP/21
Yes
30000-40000
Cisco does not recommend using FTP at all, since the protocol does not support
encryption. If it must be used, data needs to be encrypted before transfer.

Firewalls must inspect FTP traffic to allow data channels to be properly
established. If FTP is not inspected throughout the network, firewalls need to
allow outbound connectivity to the entire data channel port range.


CXD UPLOAD TOKEN

CXD creates unique upload tokens per SR. The SR number and the token are used as
the username and password to authenticate to the service and subsequently upload
files to the SR.

Note: The token is for upload only and does not allow the user to access case
files, or even files currently being uploaded. If the user would like to view
case files, that can only be done in SCM.


RETRIEVING THE UPLOAD TOKEN FOR AN SR

USING SCM

When an SR is opened, users must create the upload token to upload the
attachment.

In order to retrieve/generate the upload token, complete these steps:

Step 1. Log in to SCM.

Step 2. In order to view and edit a case, click the case number or case title in
the list. The Case Summary page opens.

Step 3. Click the Attachments tab.

Step 4. Click Generate Token. Once the token is generated it is displayed next
to the Generate Token button.

Note: The username is always the SR number. The terms password and token refer
to the upload token, which is used as a password when prompted by CXD.

USING THE API

Customers utilizing the API can retrieve the token programmatically using the
Get Token API.

Note: An Okta Auth Token is required to call Cisco Get Token API. For details on
obtaining an Auth Token, consult the Cisco ServiceGrid documentation.

HTTP Method: POST

URL: https://cxd-token.cxapps.cisco.com/cxd/token/<SR_Number>

Header:

Table 3. Get Token API Header

Key Type Value
Content-Type
String
application/json
Authorization
String
Bearer <Auth Token>

Body:

Table 4. ServiceGrid GetUploadCredentials API Body

Key Type Value
username
String
Cisco.com username authorized to perform a file upload to the SR
email
String (Email Format)
Email address of the cisco.com username


UPLOADING FILES TO CXD

USING DESKTOP CLIENTS

In general, all the user needs to do is use a client, depending on the protocol,
to connect to cxd.cisco.com, authenticate using the SR number as the username
and the upload token as the password, and eventually upload a file. Depending on
the protocol and the client, the user steps can be different. It is always
recommended to refer to the client documentation for more details.

DIRECTLY FROM A CISCO DEVICE

All Cisco devices have built-in file transfer clients, usually utilized using a
copy or redirect command. Cisco equipment running on a Linux distribution
usually supports one or more of scp, sftp, and curl for SCP, SFTP, and HTTPS
integrations.

FILE UPLOAD API

The file upload API utilizes the HTTP PUT verb to upload files to CXD. For
maximum compatibility and simplicity of integration, the API is kept simple.

HTTP Method: PUT

URL: https://cxd.cisco.com/home/<destination file name>

Headers:

Table 5. CXD File Upload API Headers

Key Type Value
Authorization
String
Basic HTTP Auth String

The body is the file data itself. There are no fields or forms here, which makes
the request very simple.

SAMPLE PYTHON CODE TO USE THE PUT API

Note that the code assumes that the file is stored in the same path you are
running it from.

import requests
from requests.auth import HTTPBasicAuth

username = 'SR Number'
password = 'Upload Token'
auth = HTTPBasicAuth(username, password)

filename = 'showtech.txt'  # Destination filename
url = f'https://cxd.cisco.com/home/{filename}'

headers = {"Expect": "100-continue"}

file_path = 'Local Path to the File'

with open(file_path, 'rb') as f:
    r = requests.put(url + filename, f, auth=auth, headers=headers)
    if r.status_code == 201:
        print("File Uploaded Successfully")

Return to Top


EMAIL FILE ATTACHMENT UPLOADS

If SCM and CXD do not work for you, another alternate file upload method is
email file attachment upload. Note that this method is fundamentally insecure
and does not encrypt the file or the communication session used to transport the
file between the customer and Cisco. It is incumbent upon the customer to
explicitly encrypt files before the files are uploaded through email file
attachments. As an additional security best practice, any sensitive information
such as passwords need to be obfuscated or removed from any configuration file
or log that is sent over an insecure channel. For more information, see
Encrypting Files.

After the files are encrypted, upload additional information and files to the
case by sending the information via an email message to attach@cisco.com with
the case number in the subject line of the message, for example, subject = Case
xxxxxxxxx.

Attachments are limited to 20 MB per email update. Attachments submitted by
using email messages are not encrypted in transit, but are immediately linked to
the specified case and stored in an encrypted format.

Attach the file to an email message and send the message to attach@cisco.com as
shown in this screenshot.



The previous screenshot displays a Microsoft Outlook email that has an encrypted
ZIP file attachment, the correct To address, and a properly formatted Subject.
Other email clients need to provide the same functionality and perform just as
well as Microsoft Outlook.

Return to Top


ENCRYPTING FILES

The following examples show how to encrypt files by using three of the many
available options such as WinZip, Linux tar and openssl commands, and Linux Gzip
and GnuPG. A strong encryption cipher such as AES-128 needs to be used in order
to properly protect the data. If you are using ZIP, an application that supports
AES encryption must be used. Older versions of ZIP applications support a
symmetric encryption system that is not secure and is not to be used.


ENCRYPTING FILES USING WINZIP

This section demonstrates how to encrypt files by using the WinZip application.
Other applications provide the same functionality and perform as well as WinZip.

Step 1. Create a ZIP archive file. In the WinZip GUI, click New and follow the
menu prompts in order to create an appropriately named, new ZIP archive file.
The system displays the newly created ZIP archive file.



Step 2. Add the file(s) to be uploaded to the ZIP archive file and check the
Encrypt added files check box. From the main WinZip window, click Add and then
choose the file(s) to upload. The Encrypt added files check box must be checked.



Step 3. Encrypt the file by using the AES encryption cipher and a strong
password:

 1. Click Add in the file selection window in order to open the Encrypt window.
 2. In the Encrypt window, create an appropriately strong password. The password
    is shared with the case Customer Support Engineer owner, as discussed in
    Communicating the Password to the TAC Customer Support Engineer.
 3. Choose one of the AES Encryption methods.
 4. Click OK in order to encrypt the file(s) and display the main WinZip window.



Step 4. Verify that the file is encrypted. Encrypted files are marked with an
asterisk following the file name or a lock icon in the Encryption column.




ENCRYPTING FILES USING TAR AND OPENSSL

This section shows how to encrypt files by using the Linux command-line tar and
openssl commands. Other archive and encryption commands provide the same
functionality and perform just as well under Linux or Unix.

Step 1. Create a tar archive of the file and encrypt it through OpenSSL using
the AES cipher and a strong password as demonstrated in the following example.
The command output shows the combined tar and openssl command syntax to encrypt
the file(s) using the AES cipher.

[user@linux ~]$ tar cvzf - Data_for_TAC.dat | openssl aes-128-cbc -k
Str0ng_passWo5D | 
      dd of=Data_for_TAC.aes128 Data_for_TAC.dat
60+1 records in
60+1 records out


ENCRYPTING FILES USING GZIP AND GNUPG

This section demonstrates how to encrypt files by using the Linux command-line
Gzip and GnuPG commands. Other archive and encryption commands provide the same
functionality and perform just as well under Linux or Unix. The command output
shows how to use the gzip and gpg command syntax to encrypt the file(s) using
the AES cipher.

Step 1. Compress the file by using Gzip:

[user@linux ~]$ gzip -9 Data_for_TAC.dat

Step 2. Encrypt the file through GnuPG using the AES cipher and a strong
password:

user@linux ~]$ gpg –cipher-algo AES –armor –output Data_for_TAC.dat.gz.asc –symmetric Data_for_TAC.dat.gz

Step 3. Enter and confirm the strong password at the passphrase prompt:

Enter passphrase:
Repeat passphrase:

Return to Top


COMMUNICATING THE PASSWORD TO THE TAC CUSTOMER SUPPORT ENGINEER

When encrypting attachments, share the encrypting password with the case
Customer Support Engineer owner. As a best practice, use a method other than the
one used to upload the file. If you used an email message or FTPS to upload the
file, communicate the password out-of-band such as by telephone or SCM case
update.

Return to Top


CUSTOMER CASE ATTACHMENTS DATA MANAGEMENT

Files uploaded to the TAC FTP folder are managed in accordance with Cisco’s
policies. Documentation regarding data controls and retention can be found in
the TAC Privacy Data Sheet.

Return to Top


SUMMARY

Multiple options exist for uploading information to TAC to help them resolve
cases. SCM and Cisco’s HTML5 Upload tool both offer secure uploads through a
browser, while the CXD offers uploads through a browser, Web API, and multiple
protocols that are supported by different types of clients and Cisco devices.

If you cannot use SCM, Cisco HTML 5 File Upload Tool, or a protocol supported by
CXD that is not FTP as your file upload method, the least preferred file upload
options are FTP, using CXD, or an email message sent to attach@cisco.com. If you
use either of these options, it is strongly advised that you encrypt your files
before transit. For more information, see Encrypting Files. You need to employ a
strong password and communicate the password to the case Customer Support
Engineer out-of-band such as by telephone or SCM case update.

For the duration that a case is open and for a period up to 18 months following
final closure of a case, all files are instantly accessible from within the case
tracking system to authorized Cisco personnel.

 * After 18 months the files can be moved to archival storage.
 * At any time, an authorized customer contact can expressly request that a
   specific file be purged from a case.
 * Files in the FTP folder are retained for only four days.

Return to Top


ADDITIONAL INFORMATION

 * Accessing Cisco Technical Services
 * Cisco Worldwide Support Contacts
 * Cisco Technical Services Resource Guide
 * Cisco Conferencing Products
 * The GNU Privacy Guard
 * The OpenSSL Project
 * WinZip

This document is part of the Cisco Security Research & Operations.

This document is provided on an "as is" basis and does not imply any kind of
guarantee or warranty, including the warranties of merchantability or fitness
for a particular use. Your use of the information on the document or materials
linked from the document is at your own risk. Cisco reserves the right to change
or update this document at any time.

Return to Top


REVISION HISTORY

Revision Publish Date Comments
3.0
12-Apr-2024
Removed the Customer File Retention section and added the Customer Case
Attachments Data Management section.
2.0
01-Nov-2023
Removed the Case File Uploader section and updated the Customer eXperience Drive
section.
1.0
14-Nov-2017
Initial Release


WAS THIS DOCUMENT HELPFUL?

Yes No Feedback



CONTACT CISCO

 * Open a Support Case
 * (Requires a Cisco Service Contract)





Cookies allow us to optimise your use of our website. We also use third-party
cookies for advertising and analytics. Please read our Privacy Statement and
Cookie Notice for more information.
Manage cookie settings Reject Accept



CONSENT MANAGER



Your Opt Out Preference Signal is Honored


 * YOUR PRIVACY


 * STRICTLY NECESSARY COOKIES


 * PERFORMANCE COOKIES


 * TARGETING COOKIES


 * FUNCTIONAL COOKIES

YOUR PRIVACY

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. From the list on
left, please choose whether this site may use Performance and/or Targeting
Cookies. By selecting Strictly Necessary Cookies only, you are requesting Cisco
not to sell or share your personal data. Note, blocking some types of cookies
may impact your experience on the site and the services we are able to offer.

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms.    You can set your browser to
block or alert you about these cookies, but some parts of the site will not then
work. These cookies do not store any personally identifiable information.

PERFORMANCE COOKIES

Performance Cookies


These cookies provide metrics related to the performance and usability of our
site. They are primarily focused on gathering information about how you interact
with our site, including: page load times, response times, error messages, and
allowing a replay of a visitor’s interactions with our site, which enables us to
review and analyze visitor behavior, helping to improve site usability and
functionality. These cookies also allow us to count visits and traffic sources
so we can measure and improve the performance of our site. They help us to know
which pages are the most and least popular and see how visitors move around the
site. If you do not allow these cookies we will not know when you have visited
our site and will not be able to monitor its performance.

TARGETING COOKIES

Targeting Cookies


These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites.    They do not store directly personal
information, but are based on uniquely identifying your browser and internet
device. If you do not allow these cookies, you will experience less targeted
advertising.

FUNCTIONAL COOKIES

Functional Cookies


These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

Back Button


COOKIE LIST

Filter Button
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Clear
checkbox label label
Apply Cancel
Save Settings
Allow All