Uploading the files required for initial configuration

REST API Reference Guide for Virtual Storage Platform 5000, Virtual Storage Platform E Series, and Virtual Storage Platform G/F Series

Version
93-07-0x
90-09-0x
88-08-10
Audience
anonymous
Part Number
MK-98RD9014-17
The following request uploads the files required for the initial configuration of storage systems. The files are uploaded from a REST API client to the storage system. In the request header of this API function, specify multipart/form-data for Content-Type.

For a list of storage systems that support this API, see Overview of the initial settings of a storage system.

If SSL communication is used between the storage system and the syslog server, run this API function to upload the required certificate file to the storage system in advance. After that, run the API function for setting the transfer destinations of the audit log. When you do so, the storage system will be set to use the uploaded certificate file for communication.

Important:
  • Only one file can be uploaded in one request.
  • If files with the same fileType attribute are already uploaded, the currently uploaded file will be overwritten by the file to be uploaded.

Execution permission

Audit Log Administrator (View & Modify)

Request header

In this API, the request body is sent in the format of multipart/form-data. Specify multipart/form-data for the Content-Type of the request header.

Request line

POST base-URL/v1/objects/actions/file-upload/invoke

Request message

Object ID

None.

Query parameters

None.

Body

Attribute

Type

Description

fileType

string

(Required) File type of the file to be uploaded

The specifiable values are as follows:
  • AuditSyslogPrimaryClientCertFile: Client certificate file of the syslog server to which audit log files are to be transferred (for the primary server)
  • AuditSyslogPrimaryRootCertFile: Root certificate file of the syslog server to which audit log files are to be transferred (for the primary server)
  • AuditSyslogSecondaryClientCertFile: Client certificate file of the syslog server to which audit log files are to be transferred (for the secondary server)
  • AuditSyslogSecondaryRootCertFile: Root certificate file of the syslog server to which audit log files are to be transferred (for the secondary server)

file

file

(Required) File to be uploaded

You can use the following characters:
  • Spaces
  • Alphanumeric characters
  • The following symbols:

    ! " # $ % & ' ( ) * + , - . : ; < = > ? @ [ \ ] ^ _ ` { | } ~

Response message

Body

None.

Status codes

For details on the status codes of the request for this operation, see the description of HTTP status codes.

If HTTP status code 502 is returned, make sure the file is correctly specified, and then run the API request again.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type: multipart/form-data" -H "Authorization:Session d7b673af189048468c5af9bcf3bbbb6f" -H "Expect:" -X POST -F "file=@C:\certfile.crt" -F "fileType=AuditSyslogPrimaryClientCertFile" https://192.0.2.100/ConfigurationManager/v1/objects/actions/file-upload/invoke

If you run a request in which multipart/form-data is specified for Content-Type, Expect: 100-continue might be automatically assigned to the header, depending on the specifications of the client software. For VSP E series, VSP G350, G370, G700, G900, VSP F350, F370, F700, F900 storage systems, depending on the specifications of the web server, this header might not be accepted. If the header is not accepted, a 417 error occurs, and the request fails. In this coding example, the Except header is specified to overwrite the automatically assigned header, thereby preventing this error.