mkpe

The mkpe command creates and copies PE packages from DS6000 nodes to the destination directory on a management node. The mkpe command is also used to create a PE package from the log and configuration files contained on the storage management console, and the package does not contain any files that are copied from the DS6000 nodes.

Read syntax diagramSkip visual syntax diagram
>>-mkpe--+---------+--+----------------+--+-----------+--------->
         '- -noftp-'  '- -retry--count-'  '- -smconly-'   

>--+---------------------------+--storage_image_ID-------------><
   '- -customer--customer_name-'                     

Parameters

Notes:
  1. This command can only be initiated from the DSCLI client installed locally on the management console connected to the target storage unit.
  2. You must have administrator authority to use the mkpe command.
  3. The PE package information is collected on the MC in subdirectory %MR1750_SM_HOME%\send2IBM. You use the mkpe command to collect the information and create the PE package which is then transferred using FTP to the IBM support Web address.
  4. PE package files that are successfully transferred to IBM support are automatically moved to the MC subdirectory, %MR1750_SM_HOME%\send2IBM\sent\.
  5. When there is a transfer failure (after attempts to use FTP for the designated number of times), you can use the sendpe command to send the package file later.
  6. The mkpe command is processed in the background on the storage server side. This processing can take more than an hour to complete. A message is displayed when the mkpe command is issued that indicates a period of time might pass before the command processing is completed. If you specify the -smconly parameter in your command, no message is displayed.
-noftp
(Optional) Specifies that the FTP transfer to IBM be disabled. The default is that the FTP transfer is enabled until this parameter is specified. You can send the PE package later by using the sendpe command when you specify the -noftp parameter.

A typical use of this parameter is when your MC is located in a network that does not have direct access to the Internet or to IBM support. Another use for this parameter might be when you are experiencing connection problems with IBM. You can create the PE package and send it later using the sendpe command.

Note: You cannot use the -noftp parameter with the -retry parameter.
-retry count
(Optional) Specifies that the FTP transfer to IBM be retried (after the original attempt fails) up to a maximum of three times. The default value is zero (no additional transfer attempts after the initial failure).
Note: You cannot use the -retry parameter with the -noftp parameter.
-smconly
(Optional) Specifies that a PE package be created that includes copies of the log and configuration files that are contained only on the MC. There are no files that are copied from the DS6000 storage nodes for inclusion in this PE package.
Note: You must include the -customer parameter when you use the -smconly parameter.
-customer customer_name
(Required when the -smconly parameter is specified) Specifies the customer name that is associated with the MC PE package. This name must be communicated to or received from IBM support because it is used to identify the PE package.
Note: The customer name can contain up to 15 alphanumeric or nonalphanumeric characters. The nonalphanumeric characters must be represented by an underscore. For example, if the original name is global2warm*hot, it is represented as global2warm_hot.
Example of a completed MC only pe package file:
1750511SMC0000.mine4results.000.NOPMH.051028223544.
cl0.SMCLog.zip
storage_image_ID
(Required) Specifies the storage image ID. A storage image ID consists of the manufacturer, machine type, and serial numbers.

Example

The following examples show how you might use the mkpe command in three different situations:

Invoking the mkpe command to create, copy and send a PE package from DS6000 nodes to IBM support
dscli>mkpe IBM.1750-68FA120 
The resulting output
Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 
DS: IBM.1750-68FA120
CMUC00246I mkpe: The task might take more than 1 hour to complete.
 The following PE package successfully generated and copied 
from 1750-68FA120:
	c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A.
IBM.0.NOPMH.20050328223544.cl0.pe.zip
	c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A.
IBM.0.NOPMH.20050328223807.cl1.pe.zip

	PE package successfully sent to IBM:
 	175051113AB15A.IBM.0.NOPMH.20050328223544.cl0.pe.zip

	PE package successfully sent to IBM:
  175051113AB15A.IBM.0.NOPMH.20050328223807.cl1.pe.zip


	mkpe successfully completed.
Invoking the mkpe command to create and copy a PE package from DS6000 nodes to the management console.
dscli>mkpe -noftp IBM.1750-68FA120 
The resulting output
Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 
DS: IBM.1750-68FA120
CMUC00246I mkpe: The task might take more than 1 hour to complete.
The following PE package successfully generated and copied from 
1750-68FA120:

	c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A.
IBM.0.NOPMH.20050328223544.cl0.pe.zip
	c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/175051113AB15A.
IBM.0.NOPMH.20050328223807.cl1.pe.zip

		mkpe successfully completed.
Invoking the mkpe command to create an MC PEpackage and send it to IBM with a retry count of 3:
dscli>mkpe –smconly 
–customer mine4results –retry 3 IBM.1750-68FA120 
The resulting output
Date/Time: Sun Jan 09 02:23:49 PST 2005 DS CLI Version: 5.0.0.0 
DS: IBM.1750-68FA120
 The following SMC PE package successfully generated:

	c:/Program_Files/IBM/DS6000StorageManager/SM/send2IBM/1750511SMC0000.
mine4results.000.NOPMH.051028223544.cl0.SMCLog.zip

	PE package successfully sent to IBM:
1750511SMC0000.mine4results.000.NOPMH.051028223544.
cl0.SMCLog.zip

	mkpe successfully completed.
Related tasks
Providing problem determination information using FTP
Providing problem determination information when FTP is not available
Related reference
offloadss
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2004, 2007. All Rights Reserved.