Registering path information about compute nodes

Virtual Storage Platform One SDS Block Virtual Private Storage Administrator Guide

Version
1.15.x
Audience
anonymous
Part Number
MK-24VSP1SDS003-02

The maximum number of compute node path information items that can be registered is 4,096 per compute node, and 255 per compute port. The maximum number of path information items per compute node changes depending on the number of storage nodes, the number of storage node compute ports, and the number of initiators registered in a compute node.

Depending on how parameters portId and hbaId are specified, the following are possible:

  • Both portId and hbaId are omitted: All the initiators of the intended compute node are allocated to all the compute ports.

  • Only hbaId is specified: The specified initiator is allocated to all the compute ports.

CAUTION:
  • If you have changed the path information of a compute node, perform a rescan of the storage in that compute node before you start I/O operations.

  • If using VMware ESXi as a compute node, set up a path between the compute node and all computer ports. Unless all paths have been set, some volumes might be invisible from a compute node.

    If not using VMware ESXi as a compute node, it is also recommended to set up a path between the compute node and all computer ports to prevent I/O performance from being deteriorated.

  • Required role: VpsStorage

  • The information about the intended compute node and its initiator must be registered beforehand.

  1. Verify the ID of the intended compute node.

    If you use the CLI to specify a compute node by nickname, check the nickname of the compute node.

    REST API: GET /v1/objects/servers

    CLI: server_list

  2. When you specify the hbaId parameter, verify the ID of the initiator for the intended compute node.

    Run either of the following commands with the compute node ID specified.

    If you use the CLI, you can specify a nickname instead of the compute node ID.

    REST API: GET /v1/objects/servers/<id>/hbas

    CLI: hba_list

  3. Register compute node path information.

    Run either of the following commands with the compute node ID specified.

    If you use the CLI, you can specify a nickname instead of the compute node ID. You can also specify the compute port of the target behavior to which it is assigned by WWN or iSCSI Name instead of the ID.

    REST API: POST /v1/objects/servers/<id>/paths

    CLI: path_create

    Verify the job ID which is displayed after the command is run.

  4. Verify the state of the job.

    Run either of the following commands with the job ID specified.

    REST API: GET /v1/objects/jobs/<jobID>

    CLI: job_show

    If the job state is "Succeeded", the job is completed.

  5. Obtain a list of path information and verify that the intended path information is added.

    Run either of the following commands with the compute node ID specified.

    If you use the CLI, you can specify a nickname instead of the compute node ID.

    REST API: GET /v1/objects/servers/<id>/paths

    CLI: path_list