IBM Support

Collecting Data: Sending data to your PMR

Technote (troubleshooting)


Problem(Abstract)

Methods for how to send requested data to your PMR

Resolving the problem

Update: Please see the notification regarding our new certificate at the bottom of this article.

You can use the following methods to send/upload your data to your PMR.


Preferred Method: Upload via the Service Request Tool

Login through the Service Request Tool and upload the data directly to your PMR.


Method 1: Email attachments


Send the data as an attachment in response to an email from support from the ecurep.ibm.com system or as a new email to ibmsecurity_support@ecurep.ibm.com.

For this to work, your data attachments must be small enough to make it through most email systems (typically less than 10 GB), the email address to send to is ibmsecurity_support@ecurep.ibm.com, and the word "PMR" and your PMR number must be in the subject line.

For example:



Method 2: Use the web upload form.

If the file(s) is/are less than 2GB you can send/upload this data through the following web form:

http://192.109.81.20/app/upload

or more securely via;

https://192.109.81.20/app/upload (Note: you will be prompted by your browser to accept the self-signed security certificate)

For example:

Fill in your PMR's number (separated by commas), choose "Security" for "Upload is for", and put in your email address:



And then drag and drop the file(s) to be uploaded and click the Upload button:


Method 3: FTP

This method is useful for files of any size (especially files over 2GB in size)

Use the following steps from your command line to FTP the files (replace #####.###.### with your PMR number. Note: use periods to separate the numbers, not commas)

1. ftp ftp.ecurep.ibm.com
2. User: anonymous
3. Password: <your e-mail address>
4. cd toibm/tivoli
5. bin
6. put #####.###.###.zip
7. quit

Note: In order for the files to make it into your PMR on IBM's side. The files must begin with the PMR number separated with periods rather than commas. You can upload multiple files all named #####.###.###.zip and they will be renamed uniquely on our end so subsequent uploads will not overwrite existing uploads. However, to help us to distinguish which upload is for which data item requested you may want to name your files with the following naming convention: #####.###.###_<date>_<description>.zip. For example: 12345,678,000_02252015_ClientDiagnostics.zip

Note: You may find it easier to establish and maintain an FTP connection for transferring your data to the PMR using a GUI FTP application such as WinSCP, FileZilla, etc. instead of from the command line.


Method 4: IBM Secure Diagnostic Data Upload Utility (a Java utility)

IBM Secure Diagnostic Data Upload Utility


None of the previous methods work

If none of the previous methods work for you, please host your data on an FTP server or download site on your end and then notify the Support rep as to where and how the data can be accessed and downloaded.

Blue Diamond Customers

If you are a Blue Diamond customer, please follow the instructions for uploading your data found in your PMR.

Important Note: 6/14/2016

Please be advised that the certificate on our ftp.ecurep.ibm.com PMR upload server for secure uploads has changed.

Most of you who upload data to PMRs through the ECuRep via Secure FTP (FTPS) will be able to exchange these certificates by making a few mouse clicks when prompted.

Due to platform dependencies IBM System z (z/OS) you will need to replace hard code certificates in your systems to use secure ftp connections. zOS customers will require to replace the outdated certificate by a manual action to re-enable FTPS based data upload.

For problems using FTPS please go to the following website (http://www-05.ibm.com/de/support/ecurep/send_ftp.html#overlay-geotrust-certificate)
which contains the newly documented certificate

Look under the page section "Security protocol" where it states "When using MVS (OS/390, z/OS) FTP client, please be sure to obtain the CA ROOT Certificate from GeoTrust or view the certificate and installation instructions."

Note: Non-secure, standard FTP uploads to ECuRep are not affected by this exchange.

Document information

More support for: IBM BigFix family

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1697924

Modified date: 04 May 2017


Translate this page: