Modifying settings of compute ports

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

Modify the settings of the intended compute port.

For iSCSI connection, you can use an iSNS server. For FC or NVMe/TCP connection, an iSNS server is unavailable.

Using an iSNS server (for iSCSI connection)

To use an iSNS server, make settings for the iSNS server.

Internet Storage Name Service (iSNS) is a naming service for iSCSI. By using iSNS, information about the initiator and the target (IP address, TCP port number, iSCSI name, and others) can be discovered without any settings.

CAUTION:

  • For the server address specified when registering an iSNS server, specify a network in the same segment that can be connected to the compute port.

  • If two compute ports exist on a storage node, both ports must have the same settings for the iSNS client function (such as enable/disable of the iSNS client function and information of the connection-target iSNS server). If different settings are used, information might not be correctly applied to the iSNS server.

  • Even when correct information is set, not all iSCSI targets might be correctly recognized in combinations of control ports and some iSNS servers. In such a case, add individual iSCSI targets manually.

With iSNS enabled in VSP One SDS Block, the following are supported by connecting with the iSNS server:

(1) Naming service
iSNS registers the initiator/target information on the network with the iSNS database and makes inquiries to the iSNS database at the request of the initiator or target.
(2) SCN (State Change Notification)
An SCN is a message to notify the initiator or target of changes in the iSNS database. When the initiator or target registers an SCN notification request, iSNS sends an SCN to the registered peer.
(3) ESI (Entity Status Inquiry)
iSNS supports ESI (Entity Status Inquiry), a heartbeat feature for the initiator and target. More specifically, iSNS sends an "ESI" to the initiator and target periodically. If no response is received for a certain number of ESIs due to a network failure or other failure, iSNS unregisters the initiator and target from the iSNS database.

When the type of compute ports is "target", all compute ports are registered with the iSNS server.

The following table lists the attributes registered in the iSNS server in the naming service.

Attribute name

Registration required

Attribute value type

Attribute value length

Description

Delimiter

-

Value

0

Delimiter. Used in a delimiter attribute.

Entity Identifier (EID)

Key

Character string

256

ID specifying an entity uniquely. Generated from a MAC address. Unique value for each physical port. The setting cannot be changed. The following defaults are set.

iqn.1994-04.jp.co.hitachi:rsd.sph.t.XXXXX.YYY

XXXXX: Serial number (0x0 to 0xFFFFF)

YYY: Port number (0x0 to 0x0FF)*

*If the storage software was upgraded from version 01.14.0x.xx or earlier, the port number range is from 0x0 to 0xFFF.

Entity Protocol

A

Value

4

Specify "2."

IP address

Key

IP address

IPv4 address: 16

IPv6 address: 40

Specify the IP address of the port.

Portal TCP/UDP Port

Key

Value

4

Specify the port number of the port.

ESI Interval

A

Value

4

ESI issuance interval (in seconds). Set 300 seconds.

ESI Port

Key

Value

4

ESI receive port number. Specify the value obtained when enabling the iSNS service for ISP4022.

SCN Port

Key

Value

4

SCN receive port number. Specify the value obtained when enabling the iSNS service for ISP4022.

iSCSI Name

Key

Character string

224

Specify the iSCSI name of the iSCSI target.

iSCSI Node Type

A

Value

4

Specify "Target" (0x00000001).

iSCSI Node Alias

Key

Character string

256

Specify the iSCSI alias of the iSCSI target.

iSCSI Node SCN Bitmap

Key

Value

4

Information received via an SCN. Set only bit 25 to ON to receive only the target information.

Key: Registered key attribute, A: Registered attribute

  • Required role: Storage

  1. Verify the ID of the intended compute port.

    If you use the CLI to specify a compute port by WWN or iSCSI name, check the WWN or iSCSI name of the compute port.

    REST API: GET /v1/objects/ports

    CLI: port_list

  2. Modify the settings of the intended compute port.

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

    If you use the CLI, you can specify the WWN or iSCSI name instead of the compute port ID.

    For iSCSI connection, configure settings for a nickname, iSCSI name, whether to enable or disable the iSNS client function, and iSNS server.

    For FC connection, configure settings for a nickname and network topology.

    Nickname

    • Each compute port must have a unique nickname.

    • Conventions to be followed when setting a nickname

      • Number of characters: 1 to 32

      • Characters that can be used: Numbers (0 to 9), uppercase alphabet (A to Z), lowercase alphabet (a to z), symbols (! # $ % & ' + - . = @ ^ _ { } ~ ( ) [ ] :)

    iSCSI name (for iSCSI connection)

    • The same iSCSI name as another compute port cannot be set.

    • The default name of the compute port added when a storage node is added cannot be set.

      Example: iqn.1994-04.jp.co.hitachi:rsd.sph.t.<ID-of-the-storage-cluster>.XXX

      Where, <ID-of-the-storage-cluster> is the hexadecimal notation of internalId obtained in Obtaining information about storage clusters.

    REST API: PATCH /v1/objects/ports/<id>

    CLI: port_set

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

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

  4. Obtain information about the intended compute port and verify the settings of the compute port.

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

    If you use the CLI, you can specify the WWN or iSCSI name instead of the compute port ID.

    REST API: GET /v1/objects/ports/<id>

    CLI: port_show

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