No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

RESTful API Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

This document describes the OPS APIs supported by the device, including OPS-supported operations, request examples, elements in the requests, response examples, elements in the responses, and response status codes.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuration Management

Configuration Management

System Startup Information

Operation

URI

Description

GET

/cfg/startupInfos/startupInfo

Obtain system startup information.

  • Request example
    <?xml version="1.0" encoding="UTF-8"?> 
    <startupInfo> 
    </startupInfo>
  • Response example (XML format)
    <?xml version="1.0" encoding="UTF-8"?> 
    <startupInfo> 
        <position></position> 
        <nextStartupFile>NULL</nextStartupFile> 
        <configedSysSoft>cfcard:/VRPV8.cc</configedSysSoft> 
        <curSysSoft>cfcard:/VRPV8.cc</curSysSoft> 
        <nextSysSoft>cfcard:/VRPV8.cc</nextSysSoft> 
        <curStartupFile>NULL</curStartupFile> 
        <curPatchFile>NULL</curPatchFile> 
        <nextPatchFile>NULL</nextPatchFile> 
    </startupInfo>

    Table 1 describes elements in responses.

    Table 3-110  Elements

    Element

    Description

    nextStartupFile

    Specifies the name of the configuration file for next startup.

    configedSysSoft

    Specifies the configured software package.

    curSysSoft

    Specifies the name of the current software package.

    nextSysSoft

    Specifies the name of the software package for next startup.

    curStartupFile

    Specifies the name of the current configuration file.

    curPatchFile

    Specifies the name of the current patch package.

    nextPatchFile

    Specifies the name of the patch package for next startup.

    Table 2 describes status codes in responses.

    Table 3-111  Status codes in responses

    Status Code

    Description

    200 OK

    The operation succeeded.

    400 Bad Request

    The request operation failed because the request is incorrect in syntax or the information attribute in the request is incorrect.

    500 Internal Server Error

    The request operation failed because of internal errors in services or unidentified processing errors.

Configuration File for Next Startup

Operation

URI

Description

POST

/cfg/setStartup

Specify the configuration file for next startup.

POST

/cfg/deleteStartup

Delete the configuration file for next startup.

POST

/cfg/deleteStartup

Delete the configuration file for next startup.

POST

/cfg/clearStartup

Cancels the configuration for the next file startup. After this parameter is specified, the system clears the current and next file startup configurations.

  1. Specify the configuration file for next startup.
    • Request example
      <?xml version="1.0" encoding="UTF-8"?> 
      <setStartup> 
          <fileName>cfcard:/vrpcfg.cfg</fileName> 
      </setStartup>

      Table 3 describes elements in requests.

      Table 3-112  Elements

      Element

      Description

      fileName

      Specifies the name of the configuration file for next startup. This parameter is mandatory.

    • Response example (XML format)
      <?xml version="1.0" encoding="UTF-8"?> 
      <ok/>

      Table 4 describes status codes in responses.

      Table 3-113  Status codes in responses

      Status Code

      Description

      200 OK

      The operation succeeded.

      400 Bad Request

      The request operation failed because the request is incorrect in syntax or the information attribute in the request is incorrect.

      500 Internal Server Error

      The request operation failed because of internal errors in services or unidentified processing errors.

  2. Delete the configuration file for next startup.
    • Request example
      <?xml version="1.0" encoding="UTF-8"?> 
      <deleteStartup> 
      </deleteStartup>
    • Response example (XML format)
      <?xml version="1.0" encoding="UTF-8"?> 
      <ok/>

      Table 5 describes status codes in responses.

      Table 3-114  Status codes in responses

      Status Code

      Description

      200 OK

      The operation succeeded.

      400 Bad Request

      The request operation failed because the request is incorrect in syntax or the information attribute in the request is incorrect.

      500 Internal Server Error

      The request operation failed because of internal errors in services or unidentified processing errors.

  1. Delete the configuration file for next startup.
    • Request example
      <?xml version="1.0" encoding="UTF-8"?> 
      <deleteStartup> 
      </deleteStartup>
    • Response example (XML format)
      <?xml version="1.0" encoding="UTF-8"?> 
      <ok/>

      Table 6 describes status codes in responses.

      Table 3-115  Status codes in responses

      Status Code

      Description

      200 OK

      The operation succeeded.

      400 Bad Request

      The request operation failed because the request is incorrect in syntax or the information attribute in the request is incorrect.

      500 Internal Server Error

      The request operation failed because of internal errors in services or unidentified processing errors.

  2. Clears the next file startup configuration.
    • Request example
      <?xml version="1.0" encoding="UTF-8"?> 
      <clearStartup> 
      </clearStartup>
    • Response example (XML format)
      <?xml version="1.0" encoding="UTF-8"?> 
      <ok/>

      Table 7 describes status codes in responses.

      Table 3-116  Status codes in responses

      Status Code

      Description

      200 OK

      The operation succeeded.

      400 Bad Request

      The request operation failed because the request is incorrect in syntax or the information attribute in the request is incorrect.

      500 Internal Server Error

      The request operation failed because of internal errors in services or unidentified processing errors.

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166567

Views: 30080

Downloads: 127

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next