PowerVC

Hitachi Registration in PowerVC 2.0

By Preeti Duhan posted Thu March 18, 2021 06:40 AM

  

PowerVC Hitachi Registration

During 1.4.3 release we rolled out a blog that explained the procedure for registering Hitachi registration in PowerVC.

PowerVC 2.0.0, with its all new user interface and better options makes registering a storage driver much easier. In this blog, we will see the procedure for Hitachi Registration in 2.0.0 release, and the parameters required during registration. This blog also focuses on a couple of troubleshooting scenarios in case you come across any challenges while registration.

Requirements and recommendations

It is recommended to have the PowerVC management server running in the same geographic location as storage controller to reduce network latency.

Requirements:

    • Ensure that the server meets these recommendations from Hitachi:

      • Linux: The same version that PowerVC is using.

      • CPU: Dual-core processor (minimum). A quad-core or greater processor is recommended.

      • Physical memory: 1 GB (minimum). Four GB or more are recommended.

    • Download and install the Hitachi Configuration Manager REST API from the Hitachi Developer Network on an x86 virtual machine.

    • Configure secure communications between the PowerVC management server and the Configuration Manager REST API by configuring and installing an appropriate certificate. See "Setting up SSL communication" in the Hitachi Command Suite Configuration Manager REST API Reference Guide.

    • Register the Hitachi storage system with the Configuration Manager REST API server. For instructions, see the Hitachi Command Suite Configuration Manager REST API Reference Guide.

    • Before registering Hitachi storage in PowerVC, make sure you have one of the following storage pool combinations

 Table 1. Storage pool and thin pool selection matrix

Pool type

Supported as storage pool

Supported as thin pool

HDP

Yes

Yes

HDT

Yes

No

RT

Yes

No

HTI

No

Yes

Registering Hitachi storage device

To register Hitachi storage device, perform the following steps.

  1. Go to Storages > Storage list and click ‘Add ’.
Picture1.png

  1. Specify respective parameters of Hitachi Storage.



  1. Select ‘Hitachi Block Storage’ from the Type dropdown list. We can find attributes in detail below:

Hostname or IP address
Hostname or IP address of Hitachi storage provider which need to be added to PowerVC as Primary Hitachi Storage.
Display name
Name which need to be displayed in PowerVC Storage Provider page.
User ID
User ID which need to provide login access to Hitachi Storage.
Password
Password which is user to provide login access to Hitachi Storage.
REST API IP or Hostname
IP or Hostname of REST API Server, which can be one of the following:
  •  Direct REST Server, which is Hitachi integrated REST Server.
  •  REST CM Server, separate machine where REST Configuration Manager server is installed. REST CM Server can be configured                                   on either Linux or Windows. Link for REST CM Server Installation and configuration:  Configuration_Manager_REST_API
REST API Port
  • REST API port which is 443 for direct REST server
  • For REST CM server the default port number is 23451 for SSL communications and 23450 for non-SSL communications.
  • PowerVC only supports SSL communications, while using SSL port make sure have the necessary certificate registered on the Hitachi Storage system.
LDEV ID Range
Range in decimal values used for volume creation in Hitachi storage system.

Storage Model

Maximum number of volume per pool

VSP G130

2047

VSP G350 and VSP F350

16383

VSP G370 and VSP F370

32676

VSP G700 and VSP F700

49151

VSP G900, VSP F900 and VSP G1000/1500

63232

    • Fibre Channel port for PowerVC: The ports selected here during registration will only be used for PowerVC, where additional ports were not allowed later. So, need an attention during port selection.
    • Fibre Channel port for default storage template: Select the Fibre Channel ports which will be used in default storage template for the Hitachi storage provider in PowerVC. Have the required ports in “Selected Ports” session which will participate in default storage template creation and move other ports to “Available Ports” session.
      Note: This is the subset of the “Selected Ports” which should be used in the Storage template.
    • Hitachi Thin Pool: Select a Hitachi Thin pool which will be used for volume clones for Hitachi storage provider in PowerVC.
Hitachi Storage pool
Select a Hitachi storage pool which will be used for default storage template in PowerVC.
  1. Click on Add Storage. Storage will be registered in PowerVC. After successful registration of Hitachi Storage system in PowerVC, the new Hitachi storage provider will be visible in 'Storages' tab.

View Storage details

To view the details of the registered Hitachi storage:
  • Go to Storage -> Storage list -> <Registered storage >
 To get the detailed view, click on Hitachi Storage template.

De-register Hitachi storage device from PowerVC

To de-register Hitachi storage device from PowerVC, perform the following steps:

  • Select the Hitachi storage system from the table, which needs to be de-registered from PowerVC and click Remove Storage.

  • Below dialog appears if there is no volume managed by Hitachi Storage provide which is like to be de-registered. Click Remove to start the de-registration of Hitachi storage system from PowerVC.

Troubleshooting steps on Hitachi storage registration in PowerVC
This session covers the troubleshooting steps during registration fails on PowerVC for Hitachi Storage system. Mostly troubeshooting starts from analyzing the log files for cinder and following are the log file which need to referred for distinct errors;

  • /var/log/cinder/api.log
  • /var/log/cinder/volume-<hostname of storage>.log
  • /var/log/cinder/hbsd_debug.log
  • Troubleshooting scenario 1:

Problem Statement: Ldev range is not specified as per the storage model
Errors:
volume-<hostname of storage>.log

oslo_messaging.rpc.server HBSDError: Bad or unexpected response from the storage volume backend API: The REST API failed. (source: /ConfigurationManager/v1/objects/storages/882000453175/ldevs, ID: KART40046-E, message: The format of the string or the content specified in the request body is invalid. (details = The specified value is not supported for the specified storage system. (parameter name = endLdevId, specified value = 65278, storage device ID = 882000453175)), cause: , solution: Check and, if necessary, revise the specified request body so that the format and content are correct., code: {}, method: POST, url: httpspvc://9.47.81.158:23451/ConfigurationManager/v1/objects/storages/882000453175/ldevs, params: None, body: {'startLdevId': 0, 'endLdevId': 65278, 'byteFormatCapacity': '3G', 'isParallelExecutionEnabled': True, 'poolId': 1})

/var/log/cinder/hbsd_debug.log
{u'errorSource': '/ConfigurationManager/v1/objects/storages/882000453175/ldevs', u'messageId': u'KART40046-E', u'detailCode': u'40046E-0', u'message': u'The format of the string or the content specified in the request body is invalid. (details = The specified value is not supported for the specified storage system. (parameter name = endLdevId, specified value = 65278, storage device ID = 882000453175))', u'solution': u'Check and, if necessary, revise the specified request body so that the format and content are correct.'}

Solution:
Provide the correct ldev range for specific storage model.

Troubleshooting scenario 2:
Problem Statement:
Port security is disabled for FC ports which part of Port selection

Errors:
volume-<hostname of storage>.log


ERROR cinder.volume.manager [req-3fa037d6-abe7-4e30-a2ed-73ee2d4b56ce - - - - -] Failed to initialize driver.: HBSDError: Bad or unexpected response from the storage volume backend API: The resource Compute target ports was not found.
WARNING cinder.volume.drivers.hitachi.hbsd.hbsd_utils [req-a4675a55-e392-4ab1-a8b6-48b3afc7d58c - - - - -] MSGID0339-W: Port CL1-A will not be used because its settings are invalid. (portType: FIBRE, lunSecuritySetting: False, fabricMode: True, portConnection: PtoP)
WARNING cinder.volume.drivers.hitachi.hbsd.hbsd_utils [req-a4675a55-e392-4ab1-a8b6-48b3afc7d58c - - - - -] MSGID0339-W: Port CL3-A will not be used because its settings are invalid. (portType: FIBRE, lunSecuritySetting: False, fabricMode: True, portConnection: PtoP)
ERROR cinder.volume.drivers.hitachi.hbsd.hbsd_utils [req-a4675a55-e392-4ab1-a8b6-48b3afc7d58c - - - - -] MSGID0650-E: The resource Compute target ports was not found.
Solution:
Enable port secuity for FC ports which participate in registration to PowerVC.

0 comments
30 views

Permalink