Registering path information about compute nodes

Virtual Storage Platform One SDS Block Storage Administrator Guide
Version
1.17.x
Audience
anonymous
Part Number
MK-24VSP1SDS002-04

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.

  • Only portId is specified: The specified compute port is allocated to all the initiators of the intended compute nodes.

  • Both portId and hbaId are specified: The initiator specified by hbaId is allocated to the compute port specified by portId.

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, set up a path between the compute node and all computer ports to prevent I/O performance from being deteriorated.

  • When you apply iSCSI connection, the maximum number of TCP connections between a compute node and storage nodes is 128 per storage node. When you apply NVMe/TCP connection, the maximum number of TCP connections is 255 per compute port. If the upper limit is exceeded, connection between a compute node and storage nodes will be unsuccessful.

  • Required role: Storage

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

  • When registering compute node path information to a VPS: Scope of the VPS

  1. When registering compute node path information to a VPS, verify the registration-target VPS ID.

    If you want to specify a VPS by its name in the CLI, verify the VPS name.

    REST API: GET /v1/objects/virtual-private-storages

    CLI: vps_list

  2. 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

  3. 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

  4. When you specify the portId parameter, verify the ID of the compute port to be allocated to the intended compute node.

    REST API: GET /v1/objects/ports

    CLI: port_list

  5. 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. Also, you can specify the allocation-destination compute port by using the 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.

  6. 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.

  7. 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

  8. (Bare metal) Back up the configuration information.

    Perform this step by referring to Backing up the configuration information (Bare metal).

    If you continue operations with other procedures, you must back up the configuration information after you have completed all operations.