Hitachi Server Adapter for Microsoft Windows PowerShell … · MK-92ADPTR061-03 Hitachi Server...

MK-92ADPTR061-03

Hitachi Server Adapter for Microsoft Windows PowerShell®

User’s Guide

v01.3.0

Platform Support

Software Requirements

Getting Help

Contents

FASTFIND LINKS

Contents 2

Hitachi Server Adapter for Microsoft Windows PowerShell® v01.3.0 User’s Guide

© 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced

or transmitted in any form or by any means, electronic or mechanical, including

photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without

notice and assumes no responsibility for its use. This document contains the most

current information available at the time of publication. When new or revised

information becomes available, this entire document will be updated and distributed to

all registered users.

Some of the features described in this document might not be currently available. Refer

to the most recent product announcement for information about feature and product

availability, or contact Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and

conditions of the applicable Hitachi Data Systems Corporation agreements. The use of

Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other

countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve,

Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON,

FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS6000, S/390, System z9, System z10,

Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.

All other trademarks, service marks, and company names in this document or website

are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

https://portal.hds.com/

MK-92ADPTR061-03

Contents

Contents ........................................................................................ 3

Preface .......................................................................................... 9

Intended Audience ................................................................................... 10

Software Version ...................................................................................... 10

Release Notes .......................................................................................... 10

Document Organization ............................................................................ 10

Document Conventions ............................................................................. 11

Convention for Storage Capacity Values ..................................................... 12

Getting Help ............................................................................................ 12

Comments ............................................................................................... 13

1 About the Hitachi Server Adapter ................................................ 15

Introduction ............................................................................................. 16

Architecture ............................................................................................. 16

PowerShell Cmdlet Support ....................................................................... 17

PowerShell Cmdlet Support Continued ....................................................... 17

Other cmdlets .......................................................................................... 18

Cmdlets that Support the Quanta Server .................................................... 20

Contents 4


2 System Requirements and Installation ....................................... 21

System Requirements ............................................................................... 22

Supported Hardware ....................................................................................... 22

Supported Software ........................................................................................ 22

Installing and Configuring HCSM ..................................................................... 23

Install HCSM .................................................................................................. 23

Configure HCSM for Blade Servers ................................................................... 23

Configure HCSM for Rack Servers .................................................................... 26

Installation .............................................................................................. 27

Uninstallation ........................................................................................... 28

Requirements for Using the Adapter Cmdlets .............................................. 28

3 Microsoft Azure Service Management Automation using Hitachi Storage Adapter .......................................................................... 29

Prerequisites .................................................................................................. 29

Importing the Hitachi Storage module into Azure Automation ............................ 29

Creating Runbook for Hitachi Storage Tasks in Azure Automation ...................... 31

Deleting the Hitachi Storage Module from Azure Automation ............................. 34

4 Performing Operations for Microsoft Windows PowerShell ......... 36

Starting the Adapter Software ................................................................... 37

Common Parameters ................................................................................ 37

Adapter Cmdlets....................................................................................... 37

Add-BladeChassis ........................................................................................... 38

Get-BladeChassis ............................................................................................ 39

Remove-BladeChassis ..................................................................................... 42

Set-ChassisLIDOff........................................................................................... 44

Set-ChassisLIDOn ........................................................................................... 45

Get-Fan ......................................................................................................... 46

Get-FCSwitch ................................................................................................. 49

Get-LANSwitch ............................................................................................... 50

Add-QuickLPAR .............................................................................................. 52

Get-LPAR ....................................................................................................... 54

Remove-LPAR ................................................................................................ 57

Set-LPARActivate ........................................................................................... 59

Set-LPARDeactivate ........................................................................................ 60

Set-LPARReactivate ........................................................................................ 61

Get-LPARBootOrder ........................................................................................ 62

SetLPARMemory ............................................................................................ 63

Get-LPARDedicatedNICPort ............................................................................. 63

Add-LPARDedicatedNICPort ............................................................................ 64

Remove-LPARDedicatedNICPort ...................................................................... 66

ColdMigrate-Lpar ........................................................................................... 67

Migrate-Lpar .................................................................................................. 68

Get-IOcardFirmwareInfo ................................................................................. 69

Update-ChassisFirmware ................................................................................ 71

Update-BladeFirmware ................................................................................... 72

Update-IOCardFirmware ................................................................................. 73

Get-LPARSharedFCPort ................................................................................... 74

Remove-LPARSharedFCPort ............................................................................ 76

Add-LPARVirtualNICPort ................................................................................. 78

Get-LPARVirtualNICPort .................................................................................. 80

Remove-LPARVirtualNICPort ........................................................................... 82

Get-ManagementModule ................................................................................. 84

Get-PowerSupply ........................................................................................... 86

Add-Server .................................................................................................... 88

Get-Server ..................................................................................................... 92

Remove-Server .............................................................................................. 96

Get-ServerEFI ................................................................................................ 98

Disable-ServerForcePXE ................................................................................ 100

Enable-ServerForcePXE ................................................................................ 102

Get-ServerHBAPort ....................................................................................... 103

Set-ServerLIDOff .......................................................................................... 105

Set-ServerLIDOn .......................................................................................... 106

Get-ServerLPARFCPort .................................................................................. 107

Get-ServerLPARNICPort ................................................................................ 109

Contents 6


Get-ServerMACLastSet .................................................................................. 111

Disable-ServerMAC ....................................................................................... 113

Set-ServerMAC ............................................................................................. 115

Get-ServerNICPort ........................................................................................ 117

Set-ServerPowerOff ...................................................................................... 119

Set-ServerPowerOn ...................................................................................... 120

Set-ServerPowerReset .................................................................................. 122

Set-ServerWDSDeploy .................................................................................. 123

Get-ServerWWNLastSet ................................................................................ 127

Disable-ServerWWN ..................................................................................... 129

Set-ServerWWN ........................................................................................... 130

Get-LPARDedicatedFCPort ............................................................................. 133

Add-LPARDedicatedFCPort ............................................................................ 134

Remove-LPARDedicatedFCPort ...................................................................... 136

Set-LPARBootOrder ...................................................................................... 137

Get-LPARMemory ......................................................................................... 139

Set-LparMemory ........................................................................................... 140

Get-LPARCPU ............................................................................................... 142

Set-LPARCPU ............................................................................................... 143

Get-ServerLparPhysicalCPU ........................................................................... 145

Get-ServerLparCPUGroup .............................................................................. 147

Get-ServerBootOrder .................................................................................... 148

Set-ServerBootOrder..................................................................................... 150

Get-QuantaCPU ............................................................................................ 151

Get-QuantaMemory ...................................................................................... 153

Get-QuantaFan ............................................................................................. 154

Get-QuantaSystemStatus .............................................................................. 155

Get-QuantaServer......................................................................................... 157

Set-QuantaBootOrder ................................................................................... 158

5 Logging and Troubleshooting .................................................... 159

Logging ................................................................................................. 160

Log Files ................................................................................................ 161

Log Setting ............................................................................................ 162

Log Rotation ................................................................................................ 162

Troubleshooting ..................................................................................... 163

Error Messages ...................................................................................... 164

6 Glossary ..................................................................................... 187

Contents 8


MK-92ADPTR061-03

Preface

This guide provides the installation instructions and explains how to use Hitachi

Server Adapter for Microsoft Windows PowerShell®

This preface includes the following information:

Intended Audience

Software Version

Release Notes

Document Organization

Document Conventions

Convention for Storage Capacity Values

Getting Help

Comments

Note The use of Hitachi Server Adapter for Microsoft Windows PowerShell® and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data

Systems.

Preface 10


Intended Audience

System Administrators can learn about installing and configuring Hitachi Server

Adapter for Microsoft Windows PowerShell.®

Software Version

This document revision applies to the following revisions:

Hitachi Server Adapter for Microsoft Windows PowerShell, v01.3.0.

Release Notes

With this User’s Guide is a separate release notes document, which may

contain product information and requirements that became available after this guide was published. Be sure to review the release notes before installation.

Document Organization

The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter.

The first page of each chapter provides links to the sections in that chapter.

Chapter Description

About the Hitachi Server Adapter

Provides an overview of the Hitachi Server Adapter for Microsoft Windows PowerShell and describes the

specifications and operations.

System Requirements and Installation

Specifies the system requirements and provides instructions for preparing for Hitachi Server Adapter for Microsoft Windows PowerShell.

Performing Operations for

Microsoft Windows PowerShell

Provides instructions for performing Hitachi Server Adapter for Microsoft Windows PowerShell operations.

Logging and Troubleshooting

Describes the error messages and troubleshooting.

Glossary Definitions for acronyms and terms found in this guide.

Document Conventions

This document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text

provided by the user or system. Example: copy source-file target-file

Note: Angled brackets (<>) also indicate variables.

screen/code Indicates text on the screen or that you enter. Example: # pairdisplay -g oradb

<> angled brackets

Indicates a variable, which is a placeholder for actual text

provided by the user or system. Example: # pairdisplay -g <group>

Note: Italic font also indicates variables.

[ ] square brackets

Optional values. Example: [a | b] indicates that you can select a, b, or nothing.

{ } braces Required or expected values. Example: { a | b } indicates that you must select either a or b.

| vertical bar A choice between two or more options or arguments. Examples:

[a | b] indicates that you can select a, b, or nothing.

{ a | b } indicates that you must select either a or b.

This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important and/or additional information.

Tip Provides helpful information, guidelines, or suggestions

for performing tasks more effectively.

Caution Warns the user of adverse conditions and/or

consequences (for example, disruptive operations).

Preface 12


Icon Label Description

WARNING Warns the user of severe conditions and/or consequences (for example, destructive operations).

Convention for Storage Capacity Values

Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values:

Physical Capacity Unit Value

1 KB 1,000 bytes

1 MB 1,0002 bytes

1 GB 1,0003 bytes

1 TB 1,0004 bytes

1 PB 1,0005 bytes

1 EB 1,0006 bytes

Logical storage capacity values (e.g., logical device capacity) are calculated

based on the following values:

Logical Capacity Unit Value

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

1 BLOCK 512 BYTES

Getting Help

The Hitachi Data Systems Support Center staff is available 24 hours a day,

seven days a week. Provisions for patches and fixes are restricted to normal business hours, 8 a.m. to 5 p.m. PST.

To reach us, please visit the support Web site for current telephone numbers

and other contact information: http://www.hds.com/services/support/. If you purchased this product from an authorized HDS reseller, contact that reseller

for support.

Before calling the Hitachi Data Systems Support Center, please provide as much information about the problem as possible, including:

http://www.hds.com/services/support/

The circumstances surrounding the error or failure.

The exact content of any error message(s) displayed on the host system(s).

Comments

Please send us your comments on this document: [email protected].

Include the document title, number, and revision, and refer to specific section(s) and paragraph(s) whenever possible.

Thank you! (All comments become the property of Hitachi Data Systems

Corporation.)

mailto:[email protected]

About the Hitachi Server Adapter 15

Hitachi Server Adapter for Microsoft Windows PowerShell® User’s Guide

About the Hitachi Server Adapter

This chapter describes the Hitachi Server Adapter for Microsoft Windows

PowerShell® software:

Introduction

PowerShell Cmdlet Support

16 About the Hitachi Server Adapter


Introduction

Hitachi Server Adapter for Microsoft Windows PowerShell® allows Hitachi

Server administrators to extend the Microsoft Windows PowerShell window with Hitachi Server management functionality. The Adapter provides cmdlets

designed to manage Hitachi servers.

Using the Adapter and other cmdlets, an administrator can create scripts to automate complex operation tasks. In addition, an administrator can filter,

sort, and group server information by piping the output of the Adapter cmdlets to other Windows PowerShell cmdlets. For quick access to a cmdlet,

see Table 1.

Note The use of Hitachi Server Adapter for Microsoft Windows PowerShell® and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data

Systems.

Architecture

Figure 1 illustrates the Hitachi Server Adapter for Microsoft Windows

Powershell adapter architecture.

Figure 1. Hitachi Adapter Architecture

The Hitachi Adapter provides the option of using HTTP or Secure Sockets Layer

(SSL, or HTTPS) to communicate between the Adapter and the hardware

management tool Hitachi Compute System Manager (HCSM). Users can choose HTTP or HTTPS when provisioning blade and rack servers.

PowerShell Cmdlet Support

Table 1. Cmdlet Support Update from PowerShell Server

1 Add-BladeChassis * * * *

2 Get-BladeChassis * * * *

3 Remove-BladeChassis * * * *

4 Set-ChassisLIDOff * * *

5 Set-ChassisLIDOn * * *

6 Get-Fan * * * *

7 Get-FCSwitch * * * *

8 Get-LANSwitch * * * *

9 Add-QuickLPAR * *

10 Get-LPAR * *

11 Remove-LPAR * *

12 Set-LPARActivate * *

13 Set-LPARDeactivate * *

14 Set-LPARReactivate * *

15 Add-LPARSharedFCPort * *

16 Get-LPARSharedFCPort * *

17 Remove-LPARSharedFCPort

* *

18 Add-LPARVirtualNICPort * *

19 Get-LPARVirtualNICPort * *

20 Remove-LPARVirtualNICPort

* *

21 Get-ManagementModule * * * *

22 Get-PowerSupply * * * *

23 Add-Server * * * *

24 Get-Server * * * *

PowerShell Cmdlet Support Continued

No. CMDLET CB500 CB2500 CR210H CR220H

No. CMDLET CB500 CB2500 CR210H CR220H



25 Remove-Server * * * *

26 Get-ServerEFI * * * *

27 Disable-ServerForcePXE * * * *

28 Enable-ServerForcePXE * * * *

29 Get-ServerHBAPort * * - -

30 Set-ServerLIDOff * * * *

31 Set-ServerLIDOn * * * *

32 Get-ServerLPARFCPort * *

33 Get-ServerLPARNICPort * *

34 Get-ServerMACLastSet * * * *

35 Disable-ServerMAC * * * *

36 Set-ServerMAC * * * *

37 Get-ServerNICPort * * * *

38 Set-ServerPowerOff * * * *

39 Set-ServerPowerOn * * * *

40 Set-ServerPowerReset * * * *

Other cmdlets

No.

CMDLET CB500 CB2500 CR210H CR220H QuantaPlex QuantaGrid

41 Set-

ServerWDSDeploy

* * * *

42 Get-

ServerWWNLastSet

* * * *

43 Disable-ServerWWN

* * * *

44 Set-ServerWWN

* * * *

45 Get-

LparDedicatedFCPort

* * * *

46 Add-

LPARDedicatedFCPort

* * * *

47 Remove-

LPARDedicatedFCPort

* * * *

48 Get-

LPARBootOrder

* * * *

No.


49 Set-

LPARBootOrder

* * * *

50 Get-LPARMemory

* * * *

51 Set-LPARMemory

* * * *

52 Get-LPARCPU * * * *

53 Set-LPARCPU * * * *

54 Get-ServerLparPhysicalCPU

* * * *

55 Get-

ServerLparCPUGroup

* * * *

56 Get-

ServerBootOrder

* * * *

57 Set-

ServerBootOrder

* * * *

58 Get-

LPARDedicatedNICPort

* * * *

59 Add-


* * * *

60 Remove-


* * * *

61 Get-IOcardFirmwareInfo

* * * *

62 Update-

ChassisFirmware

* * * *

63 Update-

BladeFirmware

* * * *

64 Update-

IOCardFirmware

* * * *

65 Get-QuantaCPU

* *

66 Get-

QuantaMemory

* *

67 Get-QuantaFan

* *

68 Get- * *



No.


QuantaSystemStatus

69 Get-QuantaServer

* *

70 Set-

QuantaPowerOn

* *

71 Set-QuantaPowerOff

* *

72 Set-QuantaPower

Cycle

* *

Cmdlets that Support the Quanta Server

The following cmdlets supported the Quanta Server:

Get-QuantaCPU

Get-QuantaMemory

Get-QuantaFan

Get-QuantaSystemStatus


Get-QuantaServer

Set-QuantaPowerOn

Set-QuantaPowerOff

Set-QuantaPowerCycle

System Requirements and Installation 21


System Requirements and Installation

This chapter includes the following topics

System Requirements

Installation

Uninstallation

Requirements for Using the Hitachi Server Cmdlets

22 System Requirements and Installation


System Requirements

Note

This release supports only the software and hardware listed here. Please refer to the release notes for the latest information.

Supported Hardware

Hitachi Servers/Blades Server Firmware

Version

Supported

Hitachi CB 500 A0241-B-9901 X

Hitachi CB 2500 A0150-1356 X

Hitachi Blade 520 HB2 04-45 X



Hitachi Blade 520 XB1 07-36 X



Hitachi CR 220H 09-81 or newer X

Hitachi CR 210H 09-81 or newer X

QuantaPlex T41S-2U (Sino) 3.16.00 X

QuantaGrid 51B-2U (Nitro) 3.17.00 X

Supported Software

Operating Systems Supported

Microsoft Windows Server 2008 R2 Standard/Enterprise Edition

X

Microsoft Windows Server 2008 R2 DataCenter Edition X

Microsoft Windows Server 2012 R2 Standard Edition X

Microsoft Windows Server 2012 R2 Datacenter Edition X

Windows PowerShell Supported

2.0 X

3.0 X

Hitachi Computer Systems Manager Supported

Hitachi Computer Systems Manager Supported

Hitachi Computer Systems Manager v8.2.0-01 or later X

Installing and Configuring HCSM

Before the Hitachi Adapter can be installed, you must install and configure Hitachi Compute Systems Manager (HCSM) for blade servers and/or rack servers.

Install HCSM

For more information, see the Hitachi Command Suite: Compute Systems

Manager User Guide (MK-91HC194-08).

Configure HCSM for Blade Servers

To set up HCSM for Hitachi Compute Blade servers, you must configure the

chassis management modules. For each management module (SVP) used in a Hitachi Compute Blade chassis, configure the following:

A Hitachi Compute Systems Manager (HCSM) service

The IP address and port number for a HCSM host

Configure Chassis Management Modules

1. Access the Compute Blade chassis by entering the chassis IP address into

your browser.

The WebConsole login page opens.

2. Enter your user name and password.



The WebConsole Dashboard opens.

3. Select the Administration tab. In the left-hand navigation pane, select HCSM.

The HCSM Administration tab opens to the right.

4. Select the HCSM Service tab. Ensure that HCSM has been enabled.

5. If HCSM is disabled, click Edit.

6. In the Edit HCSM Settings dialog, select Enable and add your

credentials. Then click Confirm.



7. Select the HCSM Servers tab. Click Add.

The Add HCSM Manager Settings dialog opens.

8. To configure the HCSM host server, add its IP address and

Port number.

9. Select Confirm to save the management module settings.

Configure HCSM for Rack Servers

To set up HCSM to work with a Hitachi rack server, do the following:

1. Enter the IP address of the rack server into your browser. The rack server's Webconsole opens. Log in as an administrator.

10. Select the Administration tab, then on the left-hand menu select HCSM.

Installation

Note Before installing the Hitachi Server Adapter for Microsoft Windows PowerShell® software, verify that Windows PowerShell is already installed in the host. Otherwise, the installer fails.

1. Download the distribution pack that contains the Hitachi Server Adapter for Microsoft Windows PowerShell® software.

The distribution pack Hitachi-Server-PowerShell-setup(01.3.0)-(x64)-01.exe is available for download from the Hitachi Data Systems

Support Portal.

11. Double-click Hitachi-Server-PowerShell-setup(01.3.0)-(x64)-01.exe at its file location.

The Preparing to Install page of the Wizard appears. Follow the screen instructions.

12. When the program setup process completes, the Welcome screen

appears. Click Next.

13. Read the License Agreement carefully.

Optionally, use the Print button to print out a copy of the agreement.

14. Select I accept the terms of the license agreement and click Next.

15. Install the feature pack in the default folder and click Next or click the Browse button to locate a preferred folder.

16. Navigate to and select the preferred folder and click OK. Click Next.

17. Click Install to begin the installation.



The Setup Status screen is displayed as the installation progresses.

18. When installation is complete, click Finish.

Uninstallation

To remove the Hitachi Server Adapter for Microsoft Windows PowerShell®

software:

1. Open the Windows Control Panel, and double-click Add or Remove Programs.

19. Select Hitachi Server Adapter for Microsoft Windows PowerShell, and click Remove.

20. Follow the instructions on screen to remove the Hitachi software.

Requirements for Using the Adapter Cmdlets

Once the user has installed the Hitachi Server Adapter for Microsoft Windows

PowerShell software, it is ready to use.

Here are the requirements for using Hitachi Server cmdlets:

Access privileges: Make sure that you have access privileges to the Hitachi Computer Systems Manager before adding chassis systems to the PowerShell window.

Add a chassis or Server: The Get cmdlets (Get-BladeChassis,

Get-ManagementModule, and so on) function only after a chassis or server has been added to the current PowerShell console session using the Add-BladeChassis or Add-Server cmdlet.

Note For the PowerShell cmdlets to communicate with the Hitachi Computer Systems Manager, please open an appropriate port

(default: 22015) between the two servers.

Microsoft Azure Service Management Automation using Hitachi Storage

Adapter

Microsoft Azure Automation enables you to automate common tasks performed

in a cloud and enterprise environment. Automation enables performance improvement, time savings, and integrity of the task regimen. The automation

sets processes to occur at predefined times.

You can automate the process using the runbooks utility or automate configuration management using Desired State Configuration. The runbook

process is a series of actions that produce automated processes in Azure Automation. Runbooks in Azure Automation are based on Windows PowerShell

or Windows PowerShell Workflow, so they can perform identical tasks to PowerShell ones.

Prerequisites

1. Windows Azure Pack 3.29 or above

2. Service Provider Foundation that ships with System Center Orchestrator

2012R2

3. Service Management Automation solution that ships with System Center Orchestrator 2012R2

4. Microsoft SQL Server 2012 or above

5. System Center 2012 R2 Virtual Machine Manager

Importing the Hitachi Storage module into Azure Automation

Once the Hitachi Storage Adapter for Microsoft Windows PowerShell adapter is

installed, the Hitachi Storage module will be available in the location below in case of default installation.

30 Microsoft Azure Service Management Automation using Hitachi Storage Adapter


C:\Program Files\Hitachi\HiPSSnapin\SMA\Hitachi_Storage.zip

To import the Hitachi Storage module into Azure Automation, perform the following:

1. Go to the Microsoft Azure Portal and click Automation.

2. Click the Assets tab.

3. Click Import Module at the bottom of the screen.

4. Upload the Hitachi_Storage.zip file

5. Once the modules are extracted, it should be available in the Assets section as shown here.

Creating Runbook for Hitachi Storage Tasks in Azure Automation

To create a sample runbook for Hitachi Storage Operations in Azure Automation:

1. Go to the Microsoft Azure Portal and then Automation.

2. Click New to create a new runbook.

3. Click Quick Create and enter the Runbook details.

4. Once you have created a runbook version, click the newly created

runbook and select Author.

5. Click Draft.

6. Add the desired cmdlets to the workflow and click Save.



7. Click Test to test the workflow. Check the output pane for the results.



Deleting the Hitachi Storage Module from Azure Automation

To delete the Hitachi Storage Module from Azure Automation:

1. Go to the Microsoft Azure Portal and click on Automation.

2. Click the Assets tab, select Hitachi_Storage, and click Delete.

You have successfully deleted the Hitachi Storage Module from Azure Automation.

Performing Operations for Microsoft Windows PowerShell 36


Performing Operations for Microsoft Windows PowerShell

This chapter includes the following sections:

Starting the Adapter Software

Adapter Cmdlets

The Hitachi software includes a set of Hitachi Server cmdlets used to discover Hitachi computer system information. The cmdlets provides information about

chassis, blades, management modules, power supply, PCI slots, fans, and logical partitions.

Starting the Adapter Software

After installing the Hitachi Server Adapter for Microsoft Windows PowerShell software, you are ready to begin operations.

To start the software:

1. In the Windows Start menu, click Hitachi, and then click Hitachi Server

PowerShell Adapter.

The Windows PowerShell command console opens.

21. Add the desired Hitachi chassis to the current session, as described in the following section. Once a chassis has been added to the current

PowerShell session, you can use the other cmdlets to get specific information about the chassis.

Common Parameters

Each cmdlet has a set of common parameters. They are:

Debug

ErrorAction

ErrorVariable

OutBuffer

OutVariable

Verbose

WarningAction

WarningVariable

For more information, type get-help about_commonparameters in the

PowerShell console.

Adapter Cmdlets

The following cmdlets are organized in alphabetical order by the server component they affect. For example, all cmdlets affecting blade and chassis

(Add-BladeChassis, for example) are placed before Get-Fan, and Get-Fan is placed before Get-FCSwitch.

38 Performing Operations for Microsoft Windows PowerShell


Add-BladeChassis

The Add-BladeChassis cmdlet adds the specified chassis to the current PowerShell session. Specify the chassis by typing the chassis IP address in the

cmdlet input parameters.

Note

After the first instance, the user ID and password cached in the Windows registry are supplied for authenticated chassis.

Input Parameters

Parameter name

Alias Required? Description

ChassisIPAddress CIP Y The IP address of the Baseboard Management Controller (BMC) of the current chassis. The BMC runs independent of the blade

processor and of failures associated with it.

HCSMIPAddress HIP Y IP address of HCSM server. The IP

address must be in the following format: 192.168.120.155.

HCSMPort HPT N The valid range of this port number is between 1-65535. If

the value is not specified, 22016 will be used as default value.

HCSMProtocol HPL N Protocol of HCSM server. The value should be HTTPS or HTTP. If

the value is not specified, HTTPS is used as the default value.

HCSMUserCredential

HUC Y Specifies user credential for the authenticated chassis.

Syntax

For use with Hitachi chassis systems:

Add-BladeChassis -HCSMIPAddress <String> -HCSMPort <String> -

HCSMUserCredential PSUserCreditial -ChassisIPAddress

[<CommonParameters>]

Example and Execution Results

In the following example, the Add-BladeChassis cmdlet returns the information for the specified chassis after you add it to the PowerShell session.

$myusername=system

$mypasswd = ConvertTo-SecureString manager -AsPlainText -Force

$mycreds = New-Object System.Management.Automation.PSCredential

($myusername, $mypasswd)

Add-BladeChassis -HCSMIPAddress 172.17.37.40 -HCSMPort 22015 -

HCSMUserCredential $mycreds -ChassisIPAddress 172.17.37.225

Output

Get-BladeChassis

Get-BladeChassis displays the fan information of the specified chassis to the

current PowerShell session. Type the chassis IP address in the cmdlet input

parameters. If the chassis IP address is not provided, information about all registered chassis is displayed.

Syntax

Get-BladeChassis [–ChassisIPAddress] <IPAddress>

For more information, type Get-Help Get-BladeChassis in the PowerShell

console.



Input Parameters

Parameter name

Alias Required Description

ChassisIPAddress CIP Y The IP address of the Baseboard Management Controller (BMC) of the current chassis. The BMC runs

independent of the blade processor and of failures associated with it.

Output Items

Get-BladeChassis acquires information about all fans of the specified chassis

and displays the information in the PowerShell console.

Get-BladeChassis sends a collection of the output objects to the pipeline. The

output object type is FAN, with the properties listed below.

Property Description

ChassisModelName The model name of this chassis.

ChassisModelNumber The model number of this chassis.

ChassisName The name of the chassis: NORMAL, WARNING, FAIL, UNKNOWN

ChassisSerialNumber The serial number of this chassis.

ChassisStatus The working status of the chassis.

Possible values:

Running

Unknown

ChassisSystem Chassis system types

ChassisType Chassis Type

ChassisUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those

from third-party vendors.

Error The number of unconfirmed error alerts.

HealthStatus The working status of the chassis blade. Possible values: NORMAL, WARNING, FAIL, UNKNOWN

Information The number of unconfirmed information alerts.

LastRefreshed Last Refreshed

LidColor LID color:

BLUE

GREEN

RED


ORANGE

UNKNOWN

LidStatus LID status:

ON

OFF

BLINKING

SLOW_BLINKING

FAST_BLINKING

UNKNOWN

MaintenanceMode TRUE

FALSE

SVPDefaultGateway SVP default gateway

SVPIpAddress SVP IP Address

SVPSubnetMask SVP subnet mask

Warning The number of unconfirmed warning alerts.

WebConsoleUrl The URL of web console


In the following example, Get-BladeChassis returns information for the

specified chassis.

Command

Get-BladeChassis -ChassisIPAddress 172.17.37.225

Output



Remove-BladeChassis

Remove-BladeChassis removes a given chassis from the registered resource

list. Specify the chassis by typing the chassis IP address in the cmdlet input

parameters.

Note The cmdlets automatically removes all blades of this chassis from the registered resources while removes the give chassis.

Syntax

Remove-BladeChassis -ChassisIPAddress <IPAddress>

For more information, type Get-Help Remove-BladeChassis in the PowerShell

console.

Input Parameters

Parameter name


ChassisIPAddresss CIP Y The IP address of the Baseboard

Management Controller (BMC) of the current chassis. The BMC runs independent of the blade processor

and of failures associated with it.

Output Items

Remove-BladeChassis enables you to remove a given chassis from the

registered resource list and displays the result information in the PowerShell console.

Remove-BladeChassis sends a collection of the output objects to the pipeline.

The output object type is a result record, with the properties listed in the following table.

Property name Description

Message When result is Failed, an error message is placed

here.

Multiple results are combined with separator ','.

Result Completed

Failed

ResultCode The code of this result from HCSM server.


In the following example, the Remove-BladeChassis cmdlet returns the

information for the result after you remove a given chassis.

Remove-BladeChassis -ChassisIPAddress 172.17.37.225

Output



Set-ChassisLIDOff

Set-ChassisLIDOff turns off the ID LED on the chassis of the server. When

the LED illuminates, it enables you to identify a specific chassis in a large group

of servers.

Syntax

Set-ChassisLIDOff –ChassisIPAddress <IPAddress>

For more information, type Get-Help Set-ChassisLIDOff in the PowerShell

console.

Input Parameters

Parameter name


ChassisIPAddress CIP Y The IP address of the Baseboard Management

Controller (BMC) of the current chassis. The BMC runs


Output Items

Set-ChassisLIDOff turns off the LID of the given chassis and displays the

resulting information in the PowerShell console.

Set-ChassisLIDOff sends a collection of the output objects to the pipeline.



Message The HCSM returns a message.

ResultCode The HCSM returns a result code record.

ResultToken The HCSM returns a result token.


In the following example, the Set-ChassisLIDOff cmdlet returns a result

record for the specified chassis.

Command

Set-ChassisLIDOff -ChassisIPAddress 172.17.37.225

Output

Set-ChassisLIDOn

Set-ChassisLIDOn illuminates the ID LED on the chassis of the server. The ID

LED enables you to identify a specific chassis in a large collection of servers.

Syntax

Set-ChassisLIDOn –ChassisIPAddress <IPAddress>

For more information, type Get-Help Set-ChassisLIDOn in the PowerShell

console.

Input Parameters

Parameter name


ChassisIPAddress CIP Y The IP address of the Baseboard Management Controller (BMC) of the current chassis. The BMC runs independent of the blade processor


Output Items

Set-ChassisLIDOn cmdlet enables you to turn on the LID of the given chassis

and displays the result information in the PowerShell console.



Set-ChassisLIDOn cmdlet sends a collection of the output objects to the

pipeline. The output object type is a result record, with the properties listed in

the following table.


Message HCSM-returned messages.

ResultCode HCSM-returned result code.

ResultToken HCSM-returned result token.


In the following example, the Set-ChassisLIDOn cmdlet returns a result record

for the specified chassis.

Command

Set-ChassisLIDOn -ChassisIPAddress 172.17.37.225

Output

Get-Fan

Get-Fan displays the fan information of a specified chassis to the current

PowerShell session. Specify the chassis by typing the chassis IP, view information about fan components of all registered chassis.

Syntax

Get-Fan –ChassisIPAddress <IPAddress>

For more information, type Get-Help Get-Fan in the PowerShell console.

Input Parameters

Parameter name

Alias Y/N

Description

ChassisIPAddress

CIP Y The IP address of the Baseboard Management Controller (BMC) of the

Parameter name

Alias Y/N

Description

current chassis. The BMC runs independent of the blade processor and of failures associated with it.

Output Items

Get-Fan acquires information about all fans of the specified chassis and

displays the information in the PowerShell console.

Get-Fan sends a collection of the output object to the pipeline. The output

object type is FAN, with the properties listed in the following table.


ChassisUniqueKey Unique alphanumeric string ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and

switch modules, including those from third-party vendors.

HealthStatus The working status of the chassis. Possible values: NORMAL, WARNING,

FAIL, UNKNOWN

InstallStatus Install status: INSTALL. NOT_INSTALL, NA

PowerStatus Power status: ON, OFF, UNKNOWN

SlotNo The number of the slot that the fan module is installed.


In the following example, the Get-Fan cmdlet returns real-time fan module

information for the specified chassis.

Command

Get-Fan -ChassisIPAddress xx.xx.xx.xx



Output

Get-FCSwitch

Get-FCSwitch acquires information about all fiber-channel switches in the

specified chassis and displays the information in the PowerShell console.

Syntax

Get-FCSwitch –ChassisIPAddress <IPAddress>

For more information, type Get-Help Get-FCSwitch in the PowerShell console.

Input Parameters

Parameter name

Alias Y/N Description

ChassisIPAddress CIP Y The IP address of the Baseboard Management Controller (BMC) of the

current chassis. The BMC runs independent of the blade processor and

of failures associated with it.

Output Items

Get-FCSwitch acquires information about all fiber-channel switches in the

specified chassis and displays the information in the PowerShell console.

Get-FCSwitch sends a collection of the output object to the pipeline. The

output object type is FAN, with the properties described in the following table.


DefaultGateway Default Gateway

FirmwareVersion The version of the firmware.


InstallStatus Install Status: INSTALL, NOT_INSTALL, NA

IPAddress IP address

LidColor Lid color: BLUE, GREEN, RED, ORANGE, UNKNOWN

LidStatus Lid status: ON, OFF, BLINKING, SLOW_BLINKING, FAST_BLINKING, UNKNOWN

MaintenanceMode Maintenance Mode: TRUE, FALSE

ModelNumber Model number

PowerStatus Power Status: ON, OFF, Unknown

SerialNumber The serial number of this switch module.

SlotNo The slot number of this switch module.

SubnetMask Subnet mask

SwitchType Example:




8Gb FC SW, Unknown

SwitchUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic

Computers), and switch modules, including those from third-party vendors.


In the following example, the Get-FCSwitch cmdlet returns the FC switch

module information for the specified chassis.

Command

Get-FCSwitch -ChassisIPAddress 172.17.37.225

Get-LANSwitch

Get-LANSwitch acquires information about all LAN switches of the specified

chassis and displays the information in the PowerShell console.

Syntax

Get-LANSwitch –ChassisIPAddress <IPAddress>

For more information, type Get-Help Get-LANSwitch in the PowerShell

console.

Input Parameters

Parameter name

Alias Y/N Description

ChassisIPAddress CIP Y The IP address of the Baseboard Management Controller (BMC) of the

current chassis. The BMC runs independent of the blade processor and of failures

associated with it.

Output Items

Get-LANSwitch sends a collection of the output object to the pipeline. The

output object type is LAN switch, with the properties listed in the following table.


DefaultGateway Default Gateway




IpAddress IP address


LidStatus Lid status: ON, OFF, BLINKING, SLOW_BLINKING, FAST_BLINKING, UNKNOWN

MaintenanceMode MaintenanceMode: TRUE, FALSE



SerialNumber The serial number of this switch module.

SlotNo The slot number of this switch module.

SubnetMask Subnet mask

SwitchType Example:

1Gb LAN SW,

1/10Gb LAN SW,

10Gb DCB Switch Module,

LAN pass through,

1Gb 40 ports LAN SW,

Unknown

SwitchUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and switch

modules, including those from third-party vendors.




In the following example, Get-LANSwitch returns real-time FC switch


Command

Get-LANSwitch -ChassisIPAddress 172.17.37.225

Output

Add-QuickLPAR

Add-QuickLPAR creates multiple logical partitions using predefined default

settings (2GB RAM, dedicated CPU allocation, and two virtual NICs). Use the following pre-defined default settings:

2GB RAM

If the segment 1a/1b exists, it will create VNIC0/1 and relates them with the segment accordingly.

Syntax

Add-QuickLPAR [–ServerIPAddress] <IPAddress> [–NumberOfLpars]

<Int> [–FirstLparNo] <Int> [–SaveConfig] <Boolean>

For more information, type Get-Help Add-QuickLPAR in the PowerShell

console.

Input Parameters


FirstLparNo First logical partition number

NumberOfLpars Number of logical partitions

SaveConfig Save the config

ServerIPAddress The IP address of the Baseboard Management Controller (BMC) of the current blade server. The

BMC runs independent of the blade processor and of failures associated with it.

Output Items

Add-QuickLPAR creates multiple logical partitions using predefined default

settings (2GB RAM, dedicated CPU allocation, and two virtual NICs). Use the following pre-defined default settings:

2GB RAM

If the segment 1a/1b exists, it will create VNIC0/1 and relates them with the segment accordingly.

If the server is allowed to create a shared Fibre Channel (FC) port, two VFCs (virtual Fibre Channels) are created. The server searches for unused VFCs and chooses the VFC with the smallest PCI slot number. One VFC is selected from

one port.

If the segment 1a/1b exists, it creates VNIC0/1 and relates them with the

segment accordingly.



The Add-QuickLPAR cmdlet sends a collection of the output objects to the

pipeline. The output object type is a result record with the properties listed in



Message When result is Failed, an error message

is placed here.


Result Completed

Failed



In the following example, the Add-QuickLPAR cmdlet returns logical partition

information for the specified blade.

Command

Add-QuickLPAR -ServerIPAddress xx.xx.xx.xx –NumberOfLpars 3 –

FirstLparNo 12

Output

Get-LPAR

Get-LPAR acquires information about all logical partitions of the specified blade

server and displays the information in the PowerShell console.

Syntax

Get-LPAR [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-LPAR in the PowerShell console.

Input Parameters

Parameter Alias Required? Description

ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs


Output Items

Get-LPAR sends a collection of the output object to the pipeline. The output

object type is logical partition, which has the following properties:


ActivationOrder Activation Order. It should be integer or *

AutoClearSystemEventLog Auto Clear System EventLog

CPUAllocation CPU Allocation

CPUAllocationRatio CPU Allocation Ratio

CPUGroup You can restrict the use of physical processors for a group of LPARs by forming a group of physical processors.

The minimum number of processors you can have in a CPUGroup is one.

You can assign any number of processors

to a physical processor group. A processor with no processor number defined belongs to the processor group

"0".

CPUIdleDetection A shared mode LPAR, which enables its idle detection does not use so much CPU power compared to the allocated

rate. Because of this reduced consumption, the LPAR provides

processor time to another shared mode LPAR that requires it. The busy shared mode LPAR that takes over

the processor time can use more processor-time than the allocation rate.

As a result, the system can use CPU time more efficiently.

CPUPerformanceCapping With the processor capping function on, the shared mode LPAR does not take on the unused (idle) capacity of other

LPARs even if the LPAR requires more




performance than its allocation rate (busy status). Because of the unused

capacity, the LPAR's processor-time never uses more

processor-time the allocation rate, even if it is busy.

Default value: true

Error Error Count

Information Information Count. The count of the information level message. Lpar Manager generates three levels of messge(error, warning, information)


LPARManagerId The ID of the LPAR Manager.

LPARName Logical Partition name

LPARNo Logical Partition number

LPARStatus Logical Partition Status. i.e., ACT:Activated

DEACT:Deactivated

MemoryNode Memory Node number

MemorySizeInMB Memory Size

MigrationStatus Migration status("NONE" "NEED" "FAILURE"

"INPROGRESS" "RECOVERING" "UNKNOWN")

NumberOfLogicalCPUs Number of Logical CPUs

ServerUniqueKey Unique ID among all of managed chassis,

servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party vendors.

VirtualConsole Virtual Console. It should be integer or *

Warning Warning Count


In the following example, the Get-LPAR cmdlet returns logical partition


Command

Get-LPAR -ServerIPAddress xx.xx.xx.xx

Output

Remove-LPAR

Remove-LPAR acquires information about all logical partitions of the specified

blade server and displays the information in the PowerShell console.

Syntax

Remove-LPAR [–ServerIPAddress] <IPAddress> [-LPARNo] Int

For more information, type Get-Help Remove-LPAR in the PowerShell console.



Input Parameters


LPARNo LN Y The number of the Logical Partition

ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of

the current blade server. The BMC runs independent of the blade processor and of failures

associated with it.

Output Items

Remove-LPAR sends a collection of the output objects to the pipeline. The

output object type is a result record, with the properties listed in the following table.


Message When result is Failed, an error message is placed here.

Multiple results are combined with

separator ','.

Result Completed

Failed



In the following example, the Remove-LPAR cmdlet returns logical partition


Command

Remove-LPAR -ServerIPAddress xx.xx.xx.xx –LparNo 12

Output

Set-LPARActivate

Set-LPARActivate enables you to activate the given logical partition and

displays the resulting information in the PowerShell console.

Syntax

Set-LPARActivate [–ServerIPAddress] <IPAddress> [–LparNo] <Int>

For more information, type Get-Help Set-LparActivate in the PowerShell

console.

Input Parameters


LparNo LN Y The number of the logical partition

ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs independent of the blade processor and of

failures associated with it.

Output Items

Set-LPARActivate sends a collection of the output objects to the pipeline. The



Message When result is "Failed", an error message is placed here.


separator ','.

Result "Completed"

"Failed"



In the following example, the Set-LPARActivate cmdlet activates the No.15

logical partition for the specified blade.

Command

Set-LPARActivate -ServerIPAddress xx.xx.xx.xx –LparNo 15



Output

Set-LPARDeactivate

Set-LPARDeactivate enables you to deactivate the given logical partition and

displays the result information in the PowerShell console.

Syntax

Set-LPARDeactivate [–ServerIPAddress] <IPAddress> [–LPARNo]

<Int>

For more information, type Get-Help Set-LPARDeactivate in the PowerShell

console.

Input Parameters


LparNo LN Y The number of the LPAR

ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs independent of the blade

processor and of failures associated with it.

Output Items

Set-LPARDeactivate sends a collection of the output objects to the pipeline.

The output object type is a result record, with the properties listed in the

following table.




Result "Completed"

"Failed"




In the following example, the Set-LPARDeactivate cmdlet deactivates the

No.15 logical partition for the specified blade.

Command

Set-LPARDeactivate -ServerIPAddress xx.xx.xx.xx –LPARNo 15

Output

Set-LPARReactivate

Set-LPARReactivate enables you to reactivate the given logical partition and

displays the result information in the PowerShell console.

Syntax

Set-LparReactivate [–ServerIPAddress] <IPAddress> [–LparNo]

<Int>

For more information, type Get-Help Set-LparReactivate in the PowerShell

console.

Input Parameters



ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC

runs independent of the blade processor and of failures associated

with it.



Output Items

Set-LPARReactivate sends a collection of the output object to the pipeline.





Result "Completed"

"Failed"

ResultCode The code of this result from HCSM

server.


In the following example, the Set-LPARReactivate cmdlet reactivates the

No.15 logical partition for the specified blade.

Command

Set-LPARReactivate -ServerIPAddress xx.xx.xx.xx –LparNo 15

Output

Get-LPARBootOrder

Get-LparBootOrder acquires information about boot orders of the specified

logical partition and displays the information in the PowerShell console.

Syntax

Get-LparBootOrder [–ServerIPAddress] <IPAddress> [–LparNo] <Int>

For more information, type Get-Help Get-LparBootOrder in the PowerShell

console.

Input Parameters





SetLPARMemory

Set-LparMemory acquires information about memory of the specified LPAR and


Syntax

Set-LparMemory [–ServerIPAddress] <IPAddress> [–LparNo] <Int>[-MemoryNodeNo <String>] [–MemorySizeInMB] <Int> [-SaveConfig]

For more information, type Get-Help Set-LparMemory in the PowerShell

console.

Input Parameters





MemorySizeInMB MS Y The size of memory.

SaveConfig SC N Save the config

Get-LPARDedicatedNICPort

Get-LPARDedicatedNICPort acquires information about all dedicated NIC ports

of the specified LPAR and displays the information in the PowerShell console.

Syntax

Get-LparDedicatedNICPort [–ServerIPAddress] <IPAddress> [–LparNo] <Int>

For more information, type Get-Help Get-LparDedicatedNICPort in the

PowerShell console.



Input Parameters




with it.


Output Items

Get-LPARDedicatedNICPort sends a collection of the output object to the




ServerUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic


LparNo Logical partition number

LparName Logical partition name

FormattedSlotNo Formatted Slot Number

SlotNo Slot Number

PortNo Port Number

PciNo PCI Number


In the following example, the Get-LparDedicatedNICPort cmdlet returns

logical partition information for the specified blade.

Command

Get-LparDedicatedNICPort -ServerIPAddress xx.xx.xx.xx Lparno 10

Add-LPARDedicatedNICPort

Add-LparDedicatedNICPort adds dedicated NIC ports to a specified logical

partition and displays the information in the PowerShell console. Also, all NIC ports of this dedicated NIC card will be assigned to the logical partition.

Syntax

Add-LparDedicatedNICPort [–ServerIPAddress] <IPAddress> [–LparNo] <Int> [-PCIDeviceNo] <Int> [-saveConfig] <Boolean>

For more information, type Get-Help Add-LPARDedicatedNICPort in the

PowerShell console.

Input Parameters

Parameter Alias Y/N Description

ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the

current blade server. The BMC runs independent of the blade processor



PCIDeviceNo Y Number Existing dedicated FC pci device No.

saveConfig Required Boolean Save the config

Output Items

Add-LPARDedicatedNICPort sends a collection of the output object to the





server.



Result "Completed"

"Failed"


In the following example, the Add-LparDedicatedNICPort cmdlet returns a

result message.

Command

Add-LparDedicatedNICPort -ServerIPAddress xx.xx.xx.xx –lparno 10 –PCIDeviceNo 5



Remove-LPARDedicatedNICPort

Remove-LparDedicatedNICPort removes dedicated NIC ports to a specified

logical partition and displays the information in the PowerShell console. Also, all

NIC ports of this dedicated NIC card will be removed from the LPAR.

Syntax

Remove-LparDedicatedNICPort [–ServerIPAddress] <IPAddress> [–LparNo] <Int> [-PCIDeviceNo] <Int> [-saveConfig] <Boolean>

For more information, type Get-Help Remove-LparDedicatedNICPort in the

PowerShell console.

Input Parameters





PCIDeviceNo The PCI device Number for the dedicated FC card

saveConfig Save the config

Output Items

Remove-LparDedicatedNICPort sends a collection of the output object to the

pipeline. The output object type is a result record with the properties listed in the following table.



Message When result is "Failed", an error

message is placed here.


Result "Completed"

"Failed"


In the following example, the Add-LparDedicatedNICPort cmdlet adds a

shared FC port on logical partition No.3.

Command

Remove-LparDedicatedNICPort -ServerIPAddress xx.xx.xx.xx –lparno 10 –PCIDeviceNo 5

ColdMigrate-Lpar

ColdMigrate-Lpar migrates a logical partition when it is inactive.

Syntax

ColdMigrate-Lpar [-SourceLparNo] <int32> -DestinationLparNo <int32> [-DestinationServerIP] <string> [-DestinationCpuGroup] <int32> -ActivateLparEnabled –ActivateTimeout <string> [-ServerIP] <string> [<CommonParameters>]

For more information, type Get-Help ColdMigrate-Lpar in the PowerShell

console.

Input Parameters


ServerIP SIP Y The BMC IP address of a blade server hosting the source Lpar

SourceLparNo SL Y Source Logical Partition Number

DestinationServerIP DL Y Destination Logical Partition Number

DestinationServerIP DIP Y The BMC IP address of the destination server

DestinationCpuGroup DCG Y CPU Group on Destination server

ActivateLparEnable ALE N Migration will be proceeded when

warning error occurs

ActivateTimeout ATO N Timeout interval for checking the target status after power controlling the target

Output Items

An output object which indicates the status and message about the operation.


In the following example, the ColdMigrate-Lpar cmdlet .



Command

Remo

Migrate-Lpar

Migrate-Lpar migrates an active Lpar.

Syntax

Migrate-Lpar [-SourceLparNo] <int32> -DestinationLparNo <int32> [-DestinationServerIP] <string> [-DestinationCpuGroup] <int32> [-TimeOutInSec <int32>] [-NetworkAssingManual] –SourceLpTempIpaddress <string> -SourceLpNic <string> -SourceLpTempSubnetMask <string> -DestLpNic <string> -DestLpTempIpaddress <string> -DestLpTempSubnetMask <string> -VlanID <int32> [-ServerIP] <string> [<CommonParameters>]

For more information, type Get-Help Migrate-Lpar in the PowerShell console.

Input Parameters


ServerIP -SIP Y The BMC IP address of a blade server hosting

source Lpar.

SourceLparNo -SL Y Source Logical Partition Number

DestinationLparNo -DL Y Destination Logical Partition

Number

DestinationServerIP -DIP Y The BMC IP address of the Destination

Server

DestinationCpuGroup -DCG Y The CPU Group on the Destination Server

TimeOutInSec -TO Y The timeout interval for checking the target status

NetworkAssignManual -NA Y Indicates whether sourc and destination LPAR Manager


migration networks are

configured manually

SourceLpTempIpaddress -STI Y when NetworkAssing

Manual is selected

Temporary IP address used by

Source Lpar Manager

SourceLpNic -SLN Y when

NetWorkAssing Manual is selected

Shared NIC

segment at source side

SourceLpTempSubnetMask -STM Y when NetWorkAssing

Manual is selected

Lpar Manager Temprorary

Subnet Mask

DestLpNic -DLN Y when NetWorkAssing Manual is selected

Shared NIC segment on the Destination Lpar

side

DestLpTempIpaddress -DTI Y when NetWorkAssing Manual is selected

The temporary IP address is used by the Destination

Lpar Manager

DestLpTempSubnetMask -DTM Y when NetWorkAssing Manual is selected

LPAR Manager Temporary Subnet Mask

VlanID -VI Y when NetWorkAssingManual

is selected

Specify the VLAN ID to use for the

temporary migration network


In the following example, the Migrate-Lpar cmdlet .

Command

Remo

Get-IOcardFirmwareInfo

Get-IOCardFirmwareInfo acquires information about the firmware information

of all available I/O cards of the specified server and displays the information in

the PowerShell console.



Syntax

Get-IOCardFirmwareInfo [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-IOCardFirmwareInfo in the

PowerShell console.

Input Parameters


ServerIPAddress SIP Y The IP address of the Baseboard Management

Controller (BMC) of the current blade server. The BMC runs independent of the

blade processor and of failures associated with it.

Output Items

Get-IOCardFirmwareInfo sends a collection of the output object to the




PartitionNumber Partition Number

ServerBladeNumber Blade Number

CardType Card Type (i.e., "ONBOARD"

"MEZZANINE""

"PCI_IOBD")

CardSlotNumber Card slot Number

CnaSettingSupport CNA configuration availability (i.e., "Enable"

"Disable")

IOFwUpdateSupport IO firmware updating availability (i.e.,

"Enable"

"Disable")

FwVersionSupport Availability of retrieving firmware version

(i.e., "Enable"

"Disable")

ControllerFwVersion A list of firmware version structure for all

contollers on the card. The structure includes

ControllerNumber and Firmware version(i.e., 4.1.334.2801)

CnaNicEightPortSettingSupport NicEightPortSetting availability (i.e., "Enable"

"Disable")


In the following example, the Get-IOCardFirmwareInfo cmdlet returns logical

partition information for the specified blade.

Command

Get-IOCardFirmwareInfo -ServerIPAddress xx.xx.xx.xx

Update-ChassisFirmware

Update-ChassisFirmware sends a firmware updating request of the specified

chassis and displays the information in the PowerShell console.

Syntax

Update-ChassisFirmware [–ChassisIPAddress] <IPAddress> –FirmwareFilePath <String>

For more information, type Get-Help Update-ChassisFirmware in the

PowerShell console.

Input Parameters


ChassisIPAddress SIP Y The IP address of the Baseboard Management

Controller (BMC) of the current blade server. The BMC runs


FirmwareFilePath FFP Y The path of the firmware file


PowerShell console.

Output Items

Update-ChassisFirmware sends a collection of output objects to the pipeline.

The output object type is a result record with the properties listed in the following table.



Message When result is "Failed", an error

message displays here.

Multiple results are combined with a separator character','.




In the following example, the Update-ChassisFirmware cmdlet sends the

firmware update request for the specified chassis.

Command

Update-ChassisFirmware -ServerIPAddress xx.xx.xx.xx –FirmwareFilePath C:\myfirmware.bin

Update-BladeFirmware

Update-BladeFirmware sends a firmware update request for the specified

blade and displays the information in the PowerShell console.

You must power down the current blade before issuing this cmdlet. The firmware will upload to the blade and will be applied after the next bootup.

Syntax

Update-BladeFirmware [–ServerIPAddress] <IPAddress> –FirmwareFilePath <String>

For more information, type Get-Help Update-BladeFirmware in the

PowerShell console.

Input Parameters


ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC)

of the current blade server. The BMC runs independent of the




PowerShell console.

Output Items

Update-BladeFirmware sends a collection of the output object to the pipeline.

The output object type is result record, with the properties listed in the table

below.






separator ','.


In the following example, the Update-BladeFirmware cmdlet sends the

firmware update request for the specified blade.

Command

Update-BladeFirmware -ServerIPAddress xx.xx.xx.xx –FirmwareFilePath C:\myfirmware.bin

Update-IOCardFirmware

Update-IOCardFirmware cmdlet sends a firmware update request for the IO

card of a specified blade and displays the information in the PowerShell

console.

Note that this cmdlet is only available for Hitachi I/O cards.

Before issuing this cmdlet, turn off the current blade. The firmware will upload

to the blade and will be applied at the next bootup.

Syntax

Update-IOCardFirmware [–ServerIPAddress] <IPAddress> –FirmwareFilePath <String>

For more information, type Get-Help Update-IOCardFirmware in the

PowerShell console.

Input Parameters


ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The






PowerShell console.

Output Items

Update-IOCardFirmware cmdlet sends a collection of output objects to the

pipeline. The output object type is result record, with the properties listed in the table below.






In the following example, Update-IOCardFirmware sends the firmware update

request for the specified blade.

Command

Update-IOCardFirmware -ServerIPAddress xx.xx.xx.xx –FirmwareFilePath C:\myfirmware.bin

Get-LPARSharedFCPort

Get-LPARSharedFCPort acquires information about all shared FC ports of the

specified logical partition and displays the information in the PowerShell

console.

Syntax

Get-LparSharedFCPort [–ServerIPAddress] <IPAddress> [–LparNo]

<Int>

For more information, type Get-Help Get-LPARSharedFCPort in the

PowerShell console.

Input Parameters


LparNo LN Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC



with it.

ServerIPAddress SIP Y The BMC IP address of a blade server

Output Items

Get-LPARSharedFCPort sends a collection of the output object to the pipeline.

The output object type is LPARSharedFCPort, which has the following

properties:


formattedSlotNo Formatted Slot No

lparName Logical partition name

lparNo Logical partition number

macAddress MACAddress (i.e., "XX:XX:XX:XX:XX:XX")

pciNo PCI Number

portNo Port Number

promiscuousMode Promiscuous Mode

Segment Network segment

serverUniqueKey Unique ID among all of managed chassis,

servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party vendors.

slotNo Slot Number

txRate TX Rate

vlanId VLAN ID

vlanTagType VLAN Tag Type

vnicNo vNIC Number


In the following example, the Get-LPARSharedFCPort cmdlet returns logical


Command

Get-LparSharedFCPort -ServerIPAddress xx.xx.xx.xx



Output

Remove-LPARSharedFCPort

Remove-LPARSharedFCPort removes a specified shared FC port on a given


Syntax

Remove-LPARSharedFCPort [–ServerIPAddress] <IPAddress> [–LparNo]

<Int> [–VNICNo] <Int> [-saveConfig] <Boolean>

For more information, type Get-Help Remove-LPARSharedFCPort in the

PowerShell console.

Input Parameters



PortNo PN Y The port number

SaveConfig SC N Save the configuration


current blade server. The BMC runs independent of the blade processor and


SlotNo SN Y The slot number

Output Items

Remove-LPARSharedFCPort sends a collection of the output objects to the






Result "Completed"

"Failed"

ResultCode The code of this result from the HCSM server.


In the following example, the Remove-LPARVirtualNICPort cmdlet returns


Command

Remove-LparSharedFCPort -ServerIPAddress xx.xx.xx.xx -LPARNo 15

-SlotNo E02 -PortNo 1 -SaveConfig $true

Output



Add-LPARVirtualNICPort

Add-LPARVirtualNICPort acquires information about all logical partitions of

the specified blade server and displays the information in the PowerShell

console.

Syntax

UnDef:

Add-LparVirtualNICPort -ServerIPAddress <IPAddress> -LparNo

<Int> -VNicNo <Int> -Segment <String> [-MacAddress <String>] -

UnDefVlan [-PromiscuousMode <String>] [-SaveConfig]

UnTag:


<Int> -VNicNo <Int> -Segment <String> [-MacAddress <String>] -

VlanID <Int> [-PromiscuousMode <String>] [-SaveConfig]

Tag:


<Int32> -VNicNo <Int> -Segment <String> [-MacAddress <String>] -

VlanIDList <List<Int>> [-PromiscuousMode <String>] [-SaveConfig]

For more information, type Get-Help Add-LPARVirtualNICPort in the

PowerShell console.

Undef Input Parameters


LparNo -LN Y Logical partition number

MACAddress -MAC N MAC address

PromiscuousMode -PM N Promiscuous mode

SaveConfig -SC N Save the config

Segment SM Y vNIC segment


TypeOfVlan TOV N Vlan setting

(UnDef

UnTag

Tag)

VlanIDList VIL N Vlan ID

VNicNo VNN Y Vnic Number

UnTag Input Parameters



MacAddress -MAC N MAC address

PromiscuousMode

-PM N Promiscuous mode


Segment -SM Y Vnic segment

ServerIPAddress

-SIP Y The BMC IP address of a blade server

VlanID -VI Y Vlan ID

VNicNo -VNN Y Vnic Number

Tag Input Parameters



MacAddress -MAC N Mac address(If the specified MAC address cannot be create, the system will automatically generates one MAC address)

PromiscuousMode

-PM N Promiscuous mode(

"Through"

Or "Restricted")


Segment -SM Y Vnic segment

ServerIPAddress

-SIP Y The BMC IP address of a blade server

VlanIDList -VIL Y The list of Vlan ID

VNicNo -VNN Y Vnic No.

Output Items

Add-LPARVirtualNICPort sends a collection of the output object to the

pipeline. The output object type is a result record, with the properties listed in the following table.




separator ','.




Result Completed

Failed



In the following example, the Add-LPARVirtualNICPort cmdlet returns logical


Command

Add-LPARVirtualNICPort -ServerIPAddress xx.xx.xx.xx –LparNo 16 –

VnicNo 6 –Segment 1a

Output

Get-LPARVirtualNICPort

Get-LPARVirtualPort acquires information about all virtual NIC ports of the

specified logical partition and displays the information in the PowerShell console.

Syntax

Get-LparVirtualNICPort [–ServerIPAddress] <IPAddress> [–LparNo]

<Int>

For more information, type Get-Help Get-LPARVirtualNICPort in the

PowerShell console.

Input Parameters


LparNo LN Y The number of the logical partition.



Output Items

Get-LPARVirtualNICPort sends a collection of the output object to the

pipeline. The output object type is logical partition, which has the following

properties:


Formattedslotno Formatted Slot Number

Lparname LPAR Name

Lparno LPAR Number

MACaddress MACAddress (i.e., XX:XX:XX:XX:XX:XX)

Pcino PCI Number

Portno Port Number

Promiscuousmode Promiscuous Mode

Segment Network segment

Serveruniquekey Unique ID among all of managed chassis, servers (Blades/Racks/Generic


Slotno Slot Number

TXrate TX Rate

Vlanid VLAN ID

Vlantagtype VLAN Tag Type

Vnicno vNIC Number


In the following example, the Get-LPARVirtualNICPort cmdlet returns logical




Command

Get-LPARVirtualNICPort -ServerIPAddress xx.xx.xx.xx

Output

Remove-LPARVirtualNICPort

Remove-LPARVirtualNICPort removes a specified virtual NIC port on a given


Syntax

Remove-LPARVirtualNICPort [–ServerIPAddress] <IPAddress> [–

LparNo] <Int> [–VNICNo] <Int> [-saveConfig] <Boolean>

For more information, type Get-Help Remove-LPARVirtualNICPort in the

PowerShell console.

Input Parameters




SaveConfig SC N Save the config. The default value is True.

ServerIPAddress

SIP Y The IP address of the Baseboard Management Controller (BMC) of the

current blade server. The BMC runs independent of the blade processor


VNICNo VNN Y The number of the logical partition

Output Items

Remove-LPARVirtualNICPort sends a collection of the output object to the







separator ','.

Result Completed

Failed


In the following example, the Remove-LPARVirtualNICPort cmdlet removes a

virtual NIC port on a given logical partition specified blade.

Command

Remove-LPARVirtualNICPort -ServerIPAddress xx.xx.xx.xx –LparNo

15 –VNICNo 1

Output



Get-ManagementModule

Get-ManagementModule acquires information about all management modules

of the specified chassis and displays the information in the PowerShell console.

Syntax

Get-ManagementModule –ChassisIPAddress] <IPAddress>

For more information, type Get-Help Get-ManagementModule in the

PowerShell console.

Input Parameters

Parameter name


ChassisIPAddress

CIP Y The IP address of the Baseboard Management Controller (BMC) of the current chassis. The BMC runs


Output Items

Get-ManagementModule sends a collection of the output object to the pipeline.

The output object type is management module, with the properties listed in the

following table.


Active Active Status:

ACTIVE,

NON_ACTIVE,

UNKNOWN

ChassisUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those from third-

party vendors.

DictionaryVersion






LidStatus Lid status: ON, OFF, BLINKING, SLOW_BLINKING, FAST_BLINKING,

UNKNOWN

MaintenanceDefaultGateway Maintenance Default Gateway

MaintenanceIpAddress Maintenance IP Address

MaintenanceMode MaintenanceMode: TRUE, FALSE

MaintenanceSubnetMask Maintenance subnet mask


ParameterVersion


SlotNo The slot number of this management module.

SVPDefaultGateway The default gateway of SVP.

SVPIpAddress The IP address of SVP.

SVPSubnetMask The subnet mask of SVP.




In the following example, the Get-ManagementModule cmdlet returns real-time


Command

Get-ManagementModule -ChassisIPAddress 172.17.37.225

Output

Get-PowerSupply

Get-PowerSupply acquires powersupply information of the specified chassis


Syntax

Get-PowerSupply –ChassisIPAddress <IPAddress>

For more information, type Get-Help Get-PowerSupply in the PowerShell

console.

Input Parameters


ChassisIPAddress CIP Y The IP address of the Baseboard Management Controller (BMC) of the current chassis. The BMC runs


Output Items

Get-PowerSupply sends a collection of the output objects to the pipeline. The

output object type is powersupply module, with the properties listed in the

following table.


ChassisUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party vendors.



ModelName Model name


ProductName Product name

SerialNumber Serial number

SlotNo The slot number of this management module.


In the following example, the Get-PowerSupply cmdlet returns power supply


Command

Get-PowerSupply -ChassisIPAddress xx.xx.xx.xx



Output

Add-Server

Add-Server adds the specified rack-mounted server to the current PowerShell

session. Specify the server by typing the server's LOM IP address in the cmdlet

input parameters.

Syntax

Add-Server –ServerIPAddress <IPAddress>

For more information, type Get-Help Add-Server in the PowerShell console.

Input Parameters


HCSMIPAddress HIP Y IP address of HCSM server. The IP address must be in the following

format: 192.168.120.155.

HCSMPort HPT N Port number of HCSM server. The


valid range of this port number is between 1-65535. If a value is not

specified, 22016 will be used as default value.

HCSMProtocol HPL N Protocol of HCSM server. The value should be HTTPS or HTTP. If the

value is not specified, HTTPS is used as the default value.

HCSMUserCredenti

al

HUC Y Specifies user credential for the

authenticated chassis.


runs independent of the blade processor and of failures associated with it.

Output Items

Add-Server sends a collection of output objects to the pipeline. The output

object type is Server, with the properties listed in the following table.


ChassisUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and switch


CPUCacheSizeInKB CPU Cache Size

CPUFrequencyInMHz CPU Frequency

CPUName CPU Name

CurrentEFIVersion EFI versions that are currently running.

CurrentFWVersion Firmware versions that are currently running.

CurrentLOMVersion LAN-on-motherboard versions that are currently running.

Error Error count

FirmwareRestartRequired TRUE: The blade requires reboot for making updated firmware effective.

FALSE: The updated firmware is already

effective.

HealthStatus The working status of the server. Possible values: NORMAL, WARNING, FAIL, UNKNOWN

Information Information Count





yyyy-mm-ddThh:mm:ss+TT:MM or

yyyy-mm-ddThh:mm:ss-TT:MM

LidColor LID Color

LidStatus LID Status

LOMDefaultGateway LOM (BMC) Default Gateway

LOMDhcpEnable LOM DHCP Enable Status:

TRUE

FALSE

LOMIpAddress LOM (BMC) IP Address

LOMSubnetMask LOM (BMC) Subnet Mask

MACType MAC Type:

Original

Additional

Unknown

MaintenanceMode Maintenance mode status

TRUE

FALSE

Manufacturer Manufacturer


NmColdStandby TRUE: The blade is used as an Active or Standby blade in the N+M Group.

FALSE: The blade is NOT used as an Active or Standby blade in the N+M Group.

NumberOfCores Number of cores per CPU

NumberOfCPUs Number of CPUs

OsMode OS Mode:

Basic

HVM

Unknown

PartitionNo Partition number

PartitionValid Validation of partition

PartitionWidth Number of server modules in this partition

PrimarySlot primary slot number of this partition

RemoteConsoleURL The URL of remote console.

ServerProductName Product name

ServerProductNumber Product number


ServerSerialNumber Unique number among Hitachi Chasis/Blade/Rack

ServerStatus Server Status

Running

Stopped

Unknown

ServerUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party vendors.

ServerUUID UUID

SlotWidth Number of slots in the chassis

UpdatingEFIVersion EFI versions that will be applied after rebooting server.

UpdatingFWVersion Firmware versions that will be applied after

rebooting server.

UpdatingLOMVersion LOM versions that will be applied after rebooting server.

Warning Warning count

WWNType WWN Type:

Original

Additional

Unknown


In the following example, the Add-Server cmdlet adds a server with a given IP

address and returns information about this server.

Command

Add-Server -ServerIPAddress 172.17.58.58 -HCSMIPAddress

172.17.58.202 -HCSM 22015 -HCSMProtocol http



Output

Get-Server

Get-Server acquires logical partition information for the specified chassis and


Syntax

Get-Server [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-Server in the PowerShell console.

Input Parameters



independent of the blade processor



Output Items

Get-Server sends a collection of the output objects to the pipeline. The output

object type is Management Module, with the properties listed in the following table.


BladeNumber Blade number

ChassisUniqueKey Unique alphanumeric string that acts as the ID for all of managed chassis, servers (Blades/Racks/Generic Computers), and switch


CPUCacheSizeInKB CPU Cache Size

CPUFrequencyInMHz CPU frequency

CPUName CPU name

CurrentEFIVersion EFI versions that are currently running.

CurrentFWVersion Firmware versions that are currently running.

CurrentLOMVersion LAN-on-motherboard versions that are currently running.

Error Error count

FirmwareRestartRequired TRUE: The blade requires reboot for making updated firmware effective.

FALSE: The updated firmware is already

effective.

HealthStatus The working status of the server. Possible values: NORMAL, WARNING, FAIL, UNKNOWN

Information Information Count


yyyy-mm-ddThh:mm:ss+TT:MM or

yyyy-mm-ddThh:mm:ss-TT:MM

LidColor LID Color

LidStatus LID Status

LOMDefaultGateway LOM (BMC) Default Gateway

LOMDhcpEnable LOM DHCP Enable Status:

TRUE

FALSE

LOMIpAddress LOM (BMC) IP Address

LOMSubnetMask LOM (BMC) Subnet Mask




MACType MAC Type:

Original

Additional

Unknown

MaintenanceMode Maintenance mode status

TRUE

FALSE

Manufacturer Manufacturer


NmColdStandby TRUE: The blade is used as Active or Standby blade in a N+M group.

FALSE: The blade is not used as Active or

Standby blade in a N+M group.

NumberOfCores Cores per CPU

NumberOfCPUs Number of CPUs.

OsMode OS Mode:

Basic

HVM

Unknown

PartitionNo Partition number

PartitionValid Validation of partition

PartitionWidth Number of server modules in this partition

PrimarySlot primary slot number of this partition

RemoteConsoleUrl The URL of the remote console.

ServerProductName Product name

ServerProductNumber Product Number

ServerSerialNumber Unique number among Hitachi Chassis/Blade/Rack

ServerStatus Server Status

Running

Stopped

Unknown

ServerUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party

vendors.

ServerUuid UUID

SlotNumber Slot number


SlotWidth Number of slots in the chassis

UpdatingEFIVersion EFI versions to be applied after rebooting server.

UpdatingFWVersion Firmware versions to be applied after rebooting server.

UpdatingLOMVersion LOM versions to be applied after rebooting server.

Warning Warning count

WWNType WWN Type:

Original

Additional

Unknown


In the following example, the Get-Server cmdlet returns information about a

given server

Command

Get-Server -ServerIPAddress 172.17.239.17



Output

Remove-Server

Remove-Server removes a given server from the registered resource list.

Specify the server by typing the server BMC IP address in the cmdlet input parameters.

Syntax

For use with Hitachi computer server systems:

Remove-Server -ServerIPAddress <IPAddress>

For more information, type Get-Help Remove-Server in the PowerShell

console.

Input Parameters


ServerIPAddress SIP Y IP address of a given server.

Output Items

Remove-Server sends a collection of the output objects to the pipeline. The

output object type is a result record, with the properties listed in the following

table.


Message When result is Failed, an error message

is placed here.


Result Completed

Failed



In the following example, the Remove-Server cmdlet returns the information

for the result after you remove a given chassis.

Command

Remove-Server -ServerIPAddress 172.17.37.163

Output



Get-ServerEFI

Get-ServerEFI enables you to check the current EFI settings of a given server

and displays the result information in the PowerShell console. Specify the

server by typing the server IP address in the cmdlet input parameters.

Syntax

Get-ServerEFI -ServerIPAddress <IPAddress>

For more information, type Get-Help Get-ServerEFI in the PowerShell

console.

Input Parameters


ServerIPAddress

SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs independent of the blade processor and

of failures associated with it.address of a given server.

Output Items

Get-ServerEFI sends a collection of the output objects to the pipeline. The

output object type is EFI Settings, with the properties listed in the following table.


Memory.MemoryMode The current value of Memory.MemoryMode.

Memory.MemoryMode.possibleValues One of the values included in this array can be set to

Memory.MemoryMode. Values depend on EFI firmware versions.

Memory.MemorySpeed The current value of Memory.MemorySpeed.

Memory.MemorySpeed.possibleValues

One of the values included in this array can be set to


Memory.MemorySpeed. Values depend on EFI firmware versions.

Memory.SocketInterleave The current value of Memory.SocketInterleave.

Memory.SocketInterleave.possibleValues

One of the values included in this array can be set to Memory.SocketInterleave. Values

depend on EFI firmware versions.

OperatingModes.DDRVoltageLevel The current value of OperatingModes.DDRVoltageLevel.

OperatingModes.DDRVoltageLevel.possibleValues

One of the values included in this array can be set to

OperatingModes.DDRVoltageLevel. Values depend on EFI firmware versions.

Processors.HardwarePrefetcher The current value of Processors.HardwarePrefetcher.

Processors.HardwarePrefetcher.possibleValues

One of the values included in this array can be set to Processors.HardwarePrefetcher.

Values depend on EFI firmware versions.

Processors.Hyper-Threading The current value of Processors.Hyper-Threading.

Processors.Hyper-Threading.possibleValues

One of the values included in this array can be set to Processors.Hyper-

Threading. Values depend on EFI firmware versions.

Processors.TurboMode The current value of the

Processorts.TurboMode.

Processors.TurboMode.possibleValues One of the values included in this array can be set to Processors.TurboMode. Values

depend on EFI firmware versions.

RASConfiguration.DeconfiguredMode The current value of RASConfiguration.DeconfiguredMode.

RASConfiguration.DeconfiguredMode.possibleValues

One of the values included in this array can be set to RASConfiguration.DeconfiguredMode.

Values depend on EFI firmware versions.




In the following example, the Get-ServerEFI cmdlet returns the information

for the result after you retrieve the EFI settings with a given server.

Command

Get-ServerEFI –ServerIPAddress 172.17.37.227

Output

Disable-ServerForcePXE

Disable-ServerForcePXE disables the ForcePXE boot on a specified server.

Specify the server by typing the server IP address in the cmdlet input parameters.

Note The forced PXE mode setting can be changed only if the server is powered off.

Syntax


Disable-ServerForcePXE -ServerIPAddress <IPAddress>

For more information, type Get-Help Disable-ServerForcePXE in the

PowerShell console.

Input Parameters



current blade server. The BMC runs independent of the blade processor and of failures associated with it.

Output Items

Disable-ServerForcePXE sends a collection of the output objects to the

pipeline. The output object type is a result record, with the properties listed in the following table.



Multiple results are combined with separator

','.

Result Completed

Failed



In the following example, the Disable-ServerForcePXE cmdlet returns the

information for the result after you disable the ForcePXE boot with a given

server.

Command

Disable-ServerForcePXE –ServerIPAddress 172.17.37.227

Output



Enable-ServerForcePXE

Enable-ServerForcePXE enables the ForcePXE boot on a specified server.

Specify the server by typing the server IP address in the cmdlet input

parameters.

Note The forced PXE mode setting can be changed only if the server is in power off status.

Syntax


Enable-ServerForcePXE -ServerIPAddress <IPAddress>

For more information, type Get-Help Enable-ServerForcePXE in the

PowerShell console.

Input Parameters


ServerIPAddress SIP Y IP address of a given server.

Output Items

Enable-ServerForcePXE sends a collection of the output objects to the






Result Completed

Failed



In the following example, the Enable-ServerForcePXE cmdlet returns the

information for the result after you enable the ForcePXE boot with a given server.

Command

Enable-ServerForcePXE –ServerIPAddress 172.17.37.227

Output

Get-ServerHBAPort

Get-ServerHBAPort acquires HBA port information for the specified server and


Syntax

Get-ServerHBAPort –ServerIPAddress <IPAddress>

For more information, type Get-Help Get-ServerHBAPort in the PowerShell

console.

Input Parameters




Output Items

Get-ServerHBAPort sends a collection of the output object to the pipeline. The

output object type is HBA Port module, with the properties listed in the

following table.


BusNumber Bus number




CardName Card name

CardSlotNumber Slot number

CardType Card Type:

MEZZANINE,

PCI,

ONBOARD

ControllerNumber Controller number

DeviceNumber Device number

FunctionNumber Function number

PortNumber Port number

ServerBladeNumber Blade number which has this NIC card.

ServerUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party

vendors.

WWNN WWNN

WWNNChangeFromDefault TRUE

FALSE

WWNnDuplication TRUE

FALSE

WWPN WWPN

WWPNChangeFromDefault TRUE

FALSE

WWPNDuplication TRUE

FALSE


In the following example, the Get-ServerHBAPort cmdlet returns HBA port

information for the specified server.

Command

Get-ServerHBAPort -ServerIPAddress 172.17.37.225

Output

Set-ServerLIDOff

Set-ServerLIDOff turns off the LID of the given server and displays the result

information in the PowerShell console.

Syntax

Set-ServerLIDOff –ServerIPAddress <IPAddress>

For more information, type Get-Help Set-ServerLIDOff in the PowerShell

console.

Input Parameters






Output Items

Set-ServerLIDOff sends a collection of the output object to the pipeline. The



Message The HCSM-returned messages.

ResultCode The HCSM-returned result code.

ResultToken The HCSM-returned result token.


In the following example, the Set-ServerLIDOff cmdlet returns the a result

record information for the specified server.

Command

Set-ServerLIDOff -ServerIPAddress 172.17.37.225

Output

Set-ServerLIDOn

Set-ServerLIDOn turns on the LID of the given server and displays the

resulting information in the PowerShell console.

Syntax

Set-ServerLIDOn –ServerIPAddress <IPAddress>

For more information, type Get-Help Set-ServerLIDOn in the PowerShell

console.

Input Parameters





Output Items

Set-ServerLIDOn sends a collection of the output object to the pipeline. The

output object type is a result record, with the properties listed in the following

table.


Message The HCSM returned messages.

ResultCode The HCSM returned result code.

ResultToken The HCSM returned result token.


In the following example, the Set-ServerLIDOn cmdlet returns a result record


Command

Set-ServerLIDOn -ServerIPAddress 172.17.37.225

Output

Get-ServerLPARFCPort

Get-ServerLparFCPort acquires information about all available FC ports for

the logical partition on the specified logical partition and displays the information in the PowerShell console.

Syntax

Get-ServerLparFCPort [–ServerIPAddress] <IPAddress>



For more information, type Get-Help Get-ServerLparFCPort in the

PowerShell console.

Input Parameters




Output Items

Get-ServerLparFCPort sends a collection of the output object to the pipeline.

The output object type is ServerLparFCPort, which has the following properties:


allocation Allocation

assignedLparNo Assigned LPAR No. (When this FC port is not assigned to any LPAR, the value is set to -1.

busNo Bus No

deviceName Device Name

devNo Dev No

formattedSlotNo Formatted Slot No

funcNo Func No

migrationWWNn Migration WWNN

migrationWWPN Migration WWPN

pciNo PCI No

portNo Port No

serverUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic Computers),

and switch modules, including those from third-party vendors.

slotNo Slot No

vendor Vendor

vfcId VFC ID

wwnn WWNN

wwpn WWPN


In the following example, the Get-ServerLPARFCPort cmdlet returns all

available FC ports for logical partition on the specified blade.

Command

Get-ServerLPARFCPort -ServerIPAddress xx.xx.xx.xx

Output

Get-ServerLPARNICPort

Get-ServerLPARNICPort acquires information about all available NIC ports for

logical partition on the specified server and displays the information in the

PowerShell console.

Syntax

Get-ServerLparNICPort [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-ServerLparNICPort in the

PowerShell console.



Input Parameters




Output Items

The Get-ServerLPARNICPort cmdlet sends a collection of the output object to

the pipeline. The output object type is ServerLparNICPort, which has the

following properties:


allocation Allocation

assignedLparNo Assigned LPAR No. (When this NIC port is not assigned to any LPAR, the value is

set to -1.)

busNo Bus Number

deviceName Device Name

devNo Dev Number

formattedSlotNo Formatted Slot Number

funcNo Func Number

packetFilter Packet Filter

pciNo PCI Number

portNo Port Number

serverUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including those from third-party vendors.

sharedNicNo Shared NIC Number

sharedNICSegment Shared NIC Segment

slotNo Slot Number

srIovSupport SR-IOV

Vendor Vendor

vfMACAddressEditable Vf MACAddress Editable

vfPrmRestrictEditable Vf Promiscuous mode restrict Editable

vfPrmThroughEditable Vf Promiscuous mode through Editable

vfTXRateEditable TX rate is editable

vfTXRateMax The max of TXrate


vfTXRateMin The minumum of TXrate

vfTXRateStep The step of TXrate

vfVlanTagEditable Vf vLAN Tag Editable

vfVlanUndeffEditable Vf vLAN Undefine Editable

vfVlanUntagEditable Vf vLAN Untag Editable


In the following example, the Get-ServerLPARNICPort cmdlet returns all

available NIC ports for logical partition on the specified blade.

Command

Get-ServerLparNICPort -ServerIPAddress xx.xx.xx.xx

Output

Get-ServerMACLastSet

Get-ServerMACLastSet retrieves the values that the most recently issued Set-ServerMAC cmdlet successfully sent to the server. The values may not be

effective on the EFI. To get the current MAC address for a given server, use



Get-ServerNICPort. The Get-ServerMACLastSet helps you know what value

has been successfully sent to the server as the additional MAC address last

time. If the server is a new blade, by default the last set value can be 0.

Note This cmdlet retrieves information from all NIC ports regardless of the existence of corresponding devices.

Syntax


Get-ServerMACLastSet -ServerIPAddress <IPAddress>

For more information, type Get-Help Get-ServerMACLastSet in the

PowerShell console.

Input Parameters


ServerIPAddress

SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs


Output Items

Get-ServerMACLastSet sends a collection of the output objects to the pipeline

and save the output to a given file. The output object type is NICPort, with the properties listed in the following table.


CardSlotNumber The number of the card slot.

CardType The type of the card.

ControllerNumber The number of the controller.

MACaddress The MAC address (i.e., 00:1f:67:0b:02:00).

OriginalMACAddress The original MAC address. If the NIC port does not exist, the value is

NULL.

PartitionNumber The number of the partition.

PortNumber The number of the port.

ServerBladeNumber The number of the server blade.


In the following example, the Get-ServerMACLastSet cmdlet returns the

information for the result after you check the result of last Set-ServerMAC cmdlet with a given server.

Command

Get-ServerMACLastSet –ServerIPAddress 172.17.37.227

Output

Disable-ServerMAC

Disable-ServerMAC disables the additional MAC addresses of all NIC ports by

resetting them to the original value on a specified server. Specify the server by

typing the server IP address in the cmdlet input parameters.

Note The resetting of server MAC addresses can be changed only if the server is powered off.

Syntax


Disable-ServerMAC -ServerIPAddress <IPAddress>



For more information, type Get-Help Disable-ServerMAC in the PowerShell

console.

Input Parameters


ServerIPAddress




Output Items

Disable-ServerMAC sends a collection of the output objects to the pipeline.

The output object type is a esult record, with the properties listed in the following table.




Result Completed

Failed



In the following example, the Disable-ServerForcePXE cmdlet returns the

information for the result after you disable the ForcePXE boot with a given

server.

Command

Disable-ServerMAC –ServerIPAddress 172.17.37.163

Output

Set-ServerMAC

Set-ServerMAC sets an additional MAC address for all NIC ports regardless of

whether these ports exist on a specified server. Specify the server by typing the server IP address in the cmdlet input parameters. A MAC address can be edited using the input parameters CardSlotNumber, PortNumber, and

ControllerNumber. One MAC address can be edited at a time.

Please note:

This cmdlet sets additional MAC addresses for all NIC ports regardless of whether corresponding devices exist. If you want to know what NIC ports exist or what MAC addresses are currently available, please

use Get-ServerNICPort to retrieve the information.

Users can specify only one MAC address at one time. If a user wants to specify multiple MAC addresses, please run this cmdlet multiple times.

This cmdlet does not check whether a MAC address is unique or has already been assigned.

All MAC addresses set for a NIC port become effective when the server is turned on.

When the Set-ServerMAC cmdlet is issued, the target server must be

in a Power Off status.

Please use Get-ServerMACLastSet cmdlet to get all MAC addresses

that have been set successfully last time, then select the MAC address you want to edit.

The server that set the MAC address using this cmdlet must be the same server that retrieved the MAC address information using the

Get-ServerMACLastSet cmdlet.

Syntax


Set-ServerMAC -ServerIPAddress <IPAddress> -ControllerNumber

<Int> -CardSlotNumber <Int> -PortNumber <Int> -MACAddress

<String>



For more information, type Get-Help Set-ServerMAC in the PowerShell

console.

Input Parameters


CardSlotNumber CSN Y Card Slot Number

ControllerNumber CTN Y Controller Number

MACAddress MAC Y Macaddress

PortNumber PN Y Port Number



Output Items

Set-ServerMAC sends a collection of the output objects to the pipeline. The

output object type is result record, with the properties listed in the following table.




separator ','.

Result Completed

Failed



In the following example, the Set-ServerMAC cmdlet returns the information

for the result after you disable the ForcePXE boot with a given server.

set-ServerMAC –ServerIPAddress 172.17.37.163 –ControllerNumber 0

–CardSlotNumber 1 –PortNumber 0 –MacAddress 00:5F:67:13:A7:0C

Output

Get-ServerNICPort

Get-ServerNICPort acquires information about the network interface card

(NIC) for the specified server.

Syntax

Get-ServerNICPort –ServerIPAddress <IPAddress>

For more information, type Get-Help Get-ServerNICPort in the PowerShell

console.

Input Parameters


ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs independent of the blade processor and of


Output Items

Get-ServerNICPort sends a collection of the output object to the pipeline. The

output object type is NIC port module, with the properties listed in the following table.


BusNumber Bus number

CardName Card name:

Example:

Emulex 10Gb 4-port converged network mezzanine card

CardSlotNumber Slot number

CardType Card Type:

MEZZANINE,

PCI,




ONBOARD

ChangeFromDefault TRUE

FALSE

ControllerNumber Controller number

DeviceNumber Device number

Duplication TRUE

FALSE

FunctionNumber Function number

MACAddress MAC address

PortNumber Port number

ServerBladeNumber The number of the blade where this NIC card is located.

ServerUniqueKey Unique ID among all of managed chassis, servers

(Blades/Racks/Generic Computers), and switch modules, including those

from third-party vendors.


In the following example, the Get-ServerNICPort cmdlet returns NIC


Command

Get-ServerNICPort -ServerIPAddress 172.17.239.17

Output

Set-ServerPowerOff

Set-ServerPowerOff powers off the given server and displays the result


Syntax

Set-ServerPowerOff –ServerIPAddress <IPAddress>

For more information, type Get-Help Set-ServerPowerOff in the PowerShell

console.

Input Parameters

Parameter Alias Deleted? Description



Output Items

Set-ServerPowerOff sends a collection of the output objects to the pipeline.

The output object type is result record, with the properties listed in the

following table.








In the following example, the Set-ServerPowerOff cmdlet returns result

record information for the specified chassis.

Command

Set-ServerPowerOff -ServerIPAddress 172.17.37.225

Output

Set-ServerPowerOn

Set-ServerPowerOn powers on the given server and displays the result


Syntax

Set-ServerPowerOn –ServerIPAddress <IPAddress>

For more information, type Get-Help Set-ServerPowerOn in the PowerShell

console.

Input Parameters

Parameter name

Alias Deleted? Description

ServerIPAddress


Parameter name

Alias Deleted? Description


Output Items

Set-ServerPowerOn sends a collection of the output object to the pipeline. The

output object type is result record, with the properties listed in the following

table.






In the following example, the Set-ServerPowerOn cmdlet returns a result

record information for the specified server.

Command

Set-ServerPowerOn -ServerIPAddress 172.17.37.225

Output



Set-ServerPowerReset

Set-ServerPowerReset resets the given server and displays the result


Syntax

Set-ServerPowerReset –ServerIPAddress <IPAddress>

For more information, type Get-Help Set-ServerPowerReset in the

PowerShell console.

Input Parameters

Parameter name




Output Items

Set-ServerPowerReset sends a collection of the output object to the pipeline.


following table.






In the following example, the Set-ServerPowerReset cmdlet returns a result

record information for the specified chassis.

Command

Set-ServerPowerReset -ServerIPAddress 172.17.37.225

Output

Set-ServerWDSDeploy

Set-ServerWDSDeploy adds the given Hitachi server as a pre-staged client to

the WDS server for Windows OS deployment with a specified OS image path

and an unattended answer file.

Prerequisites

1. Active Directory

To properly configure Active Directory with WDS, please execute the following steps.

To grant permission to approve a pending computer

Open Active Directory Users and Computers.

Right-click the OU where you are creating pre-staged computer accounts, and then select Delegate Control. On the first screen of the wizard,

click Next.

Change the object type to include computers. Add the computer object of the Windows Deployment Services server, and then click Next.

Select Create a Custom task to delegate.

Select Only the following objects in the folder. Then select the Computer Objects check box, select Create selected objects in this folder, and click Next.

In the Permissions box, select the Write all Properties check box, and click Finish.

22. DHCP

Note it is highly recommended to install the DHCP server on the same subnet or vLAN.

It is recommended to read the following Microsoft guidance for installing and configuring DHCP on Windows 2012 R2.

(Ref: https://technet.microsoft.com/en-

us/library/hh831825.aspx)

https://technet.microsoft.com/en-us/library/hh831825.aspx

https://technet.microsoft.com/en-us/library/hh831825.aspx



23. Windows 2012 R2 Based WDS

Note It is recommended to read the following Microsoft step-by-step guidance for installing and configuring WDS on Windows 2012

R2.

(Ref: https://technet.microsoft.com/en-us/library/jj648426.aspx)

24. Windows Remote Management is turned on in the WDS server

Note By default, Windows Remote Management is turned on in Windows 2012 R2. If Windows Remote Management is not turned on, it is recommended to read the following Microsoft

guidance for configuring Windows remote management.

(Ref: https://technet.microsoft.com/en-us/library/hh921475.aspx)

25. Remote Connections

For remote connections in a Workgroup-to-Workgroup/Domain scenario, the remote WDS server must be added to the Trusted Hosts list on the

source computer.

To add a remote WDS server to the Trusted Hosts list

To do this, run the following command on the source computer in a Command Prompt window that is opened with elevated user rights.

winrm set winrm/config/client @{TrustedHosts="WDS ServerName or

IP"}

(Please check the following Microsoft article for more information.

Ref: https://technet.microsoft.com/en-us/library/dd759202.aspx)

26. PXE Boot. The PXE boot settings of the Hitachi servers must be

configured appropriately.

27. Boot Image Path (Optional).

The Set-ServerWDSDeploy cmdlet does not verify whether the bootimagepath is valid. Please verify it with your WDS administrator.

28. Unattend answer file (Optional).

The Set-ServerWDSDeploy cmdlet does not verify whether the unattend answer file is valid. Verify it with your WDS administrator.

29. Microsoft tools for OS deployment. The following Microsoft article

introduces OS deployment tools including WDS and explains relationships and selection strategies for deployment tools.

https://technet.microsoft.com/en-us/library/hh921475.aspx)

https://technet.microsoft.com/en-us/library/hh921475.aspx)

Note It is recommended to read the following reference to understand Microsoft deployment technology.

(Ref: https://technet.microsoft.com/en-

us/windows/hh147630.aspx).

Set-ServerWDSDeploy creates a pre-staged client, defined as an account for a

computer within Active Directory Domain Services (ADDS). Use pre-staged clients to provision computer accounts before a server that runs Windows

Deployment Services installs the Windows 2012 R2 or Windows 2008 R2.

To create a pre-staged client, specify the MAC address associated with the computer, and a name for the computer. After the creation, you can reboot the

Hitachi server to start the OS deployment with WDS.

You also can specify the following:

o A server that runs Windows Deployment Services. The client contacts this server for the network boot program and boot image.

o A MAC address that presents the pre-staged client.

o A WDS session that connects to a WDS Windows 2012 R2 server.

o A device name that presents this client.

o A boot image for the client.

o A Windows Deployment Services answer file for the client.

Syntax

Set-ServerWdsDeploy -ServerIPAddress <IPAddress> -WDSSession

<PSSession> -MACAddress <String> -DeviceName <String> [-

BootImagePath <String> -WdsClientUnattend <String>]

Input Parameters


BootImagePath

BIP N Specifies a path to the boot image. This is the path to the boot image file for the computer.

DeviceName DN Y Specifies the name of the computer associated with the pre-staged client.

MACAddress MAC Y Specifies the MAC address of a given server.

ServerIPAddress

SIP Y IP address of a given server.

WdsClientUnattend

WCU N Specifies an answer file as a relative path from the RemoteInstall share. This file contains information for the

Windows Deployment Services client user interface screens, such as entering

https://technet.microsoft.com/en-us/windows/hh147630.aspx

https://technet.microsoft.com/en-us/windows/hh147630.aspx




credentials, choosing an install image, and configuring the disk.

WDSSession WS Y Specifies the session to a remote WD server.

Output Items

Set-ServerWDSDeploy sends a collection of the output objects to the pipeline.


following table.




Result Completed

Failed

ResultCode The code of this result from the WDS server.


In the following example, the Set-ServerWDSDeploy returns the information for

the result after you configure two blades as WDS client for Windows 2008R2 and Windows 2012R2 images, respectively.

Command

//Automatically install win2012R2 and win2008r2 on blade

#0(172.17.37.227) and blade#1(172.17.37.163)

$c=get-credential

$s=new-pssession -computername 172.17.37.56 -Credential $c

Set-ServerWDSDeploy -Serveripaddress 172.17.37.227 -WDSSession

$s -MACAddress 00008778970c -DeviceName blade00 -BootImagePath

Boot\x64\Images\win2012r2boot_2707946.wim -WdsClientUnattend

WdsClientUnattend\TestWin2012R2.xml

Set-ServerWDSDeploy -Serveripaddress 172.17.37.163 -WDSSession

$s -MACAddress 000087780FD0 -DeviceName blade01 -BootImagePath

Boot\x64\Images\win2008r2boot.wim -WdsClientUnattend

WdsClientUnattend\TestWin2008R2.xml

Get-ServerWWNLastSet

Get-ServerWWNLastSet enables you to retrieve the information that the most

recent successfully issued Set-ServerWWN cmdlet set for the server, although

the value may not be effective for the EFI.

To get the current WWN value for a given server, please use

Get-ServerHBAPort. Get-ServerWWNLastSet is supposed to be used for

helping you to know what value has been successfully set to the server as the

additional WWNs last time. If it is a new blade, the last set value can be 0 by default.

Note This cmdlet retrieves information from all of HBA ports regardless existence of corresponding devices.

Syntax


Get-ServerWWNLastSet -ServerIPAddress <IPAddress>



For more information, type Get-Help Get-ServerWWNLastSet in the

PowerShell console.

Input Parameters




Output Items

Get-ServerWWNLastSet sends a collection of the output objects to the pipeline

and saves the output to a given file. The output object type is HBAPort, with the properties listed in the following table.


cardSlotNumber The number of the card slot.

cardType The type of card—PCI, MEZZAZINE, or PCI IOBD

partitionNumber The number of the partition.

portNumber The number of the port.

serverBladeNumber The number of the server blade.

WWNN WWN (24:00:00:00:87:80:74:0b)

WWPN WWPN (24:00:00:00:87:80:74:0a)


In the following example, the Get-ServerWWNLastSet cmdlet returns the

information for the result after you check the result of last Set-ServerWWN

cmdlet with a given server.

Command

Get-ServerWWNLastSet –ServerIPAddress 172.17.37.227

Output

Disable-ServerWWN

Disable-ServerWWN disables the additional WWNs of all HBA ports by resetting

them to the original value on a specified server. Specify the server by typing the server IP address in the cmdlet input parameters.

Note The resetting of server WWN can be changed only if the server is in power off status.

Syntax

Disable-ServerWWN -ServerIPAddress <IPAddress>

For more information, type Get-Help Disable-ServerWWN in the PowerShell

console.

Input Parameters


ServerIPAddresss SIP Y The IP address of the Baseboard Management Controller (BMC) of the




Output Items

Disable-ServerWWN sends a collection of the output objects to the pipeline.





Result Completed

Failed


server.


In the following example, the Disable-ServerWWN cmdlet returns the

information for the result after you disable the ForcePXE boot with a given server.

Disable-ServerWWN –ServerIPAddress 172.17.37.163

Output

Set-ServerWWN

Set-ServerWWN sets additional WWNs for all Fibre Channel ports regardless of

whether the FC ports exist on a specified server. Specify the server by typing the server IP address in the cmdlet input parameters. Also, users can specify

one new WWPN and WWNN at a time using the -CardSlotNumber and –PortNumber parameters. Please note:

The Set-ServerWWN cmdlet sets additional WWNs for all FC ports

regardless of whether corresponding devices exist.

Users can specify only one pair of WWPNs and WWNNs at a time. To specify multiple WWNs, run this cmdlet multiple times.

The Set-ServerWWN cmdlet does not check consistency among

WWNs.

The value set for the FC port is applied when the server is turned on.

The target server must be in Power Off status when the Set-ServerWWN cmdlet is issued.

Use the Get-ServerWWNLastSet cmdlet to get values for all WWNs

that have been set most recently, then select the WWN address you want to edit.

Note The setting of server WWNs can be changed only if the server is powered off. This cmdlet does not check whether a WWN is

available or has been used. The WWN set to the HBA port is applied when the server is turned on. The server that set new

WWN address by this cmdlets must be the same server that

retrieved WWN address information using the Get-ServerWWNLastSet cmdlet. The WWN for the Hitachi "FIVE" FC

card must start with 2 or 5.

Syntax


Set-ServerWWN -ServerIPAddress <IPAddress> -CardSlotNumber <Int>

-PortNumber <Int> -WWPN <String> -WWNN <String>

For more information, type Get-Help Set-ServerMAC in the PowerShell

console.

Input Parameters


CardSlotNumber CSN Y Card Slot Number

PortNumber PN Y Port Number

ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server.

The BMC runs independent of the blade processor and of failures associated with it.

WWNN WNN Y WWNN

WWPN WPN Y WWPN

Output Items

Set-ServerWWN enables you to set a pair of WWPN and WWNN of a given port

of the given server to the given values and displays the result information in

the PowerShell console.



set-ServerWWN sends a collection of the output objects to the pipeline. The

output object type is result record, with the properties listed in the following

table.


Message When result is Failed, an error message is placed here. Multiple results are combined with separator ','.

Result Completed

Failed



In the following example, the Set-ServerMAC cmdlet returns the information

for the result after you disable the ForcePXE boot with a given server.

Set-ServerWWN –ServerIPAddress 172.17.37.215 –CardSlotNumber 2 –PortNumber 0 –WWPN 50:30:08:70:00:52:ad:35 –WWNN 50:30:08:07:00:52:ad:36

Output

Get-LPARDedicatedFCPort

Get-LparDedicatedFCPort acquires information about all dedicated FC ports

of the specified logical partition and displays the information in the PowerShell

console.

Syntax

Get-LparDedicatedFCPort [–ServerIPAddress] <IPAddress> [–LparNo] <Int>

For more information, type Get-Help Get-LparDedicatedFCPort in the

PowerShell console.

Input Parameters




LPARNo LN Y The number of the logical partition

Output Items

Get-LparDedicatedFCPort sends a collection of the output object to the

pipeline. The output object type is logical partition, which has the following properties:


ServerUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic Computers),

and switch modules, including those from third-party vendors.

LparNo Logical Partition Number

LparName Logical Partition Name

FormattedSlotNo Formatted Slot No.

SlotNo Slot No.

PortNo Port No.

PciNo PCI No.

Wwpn WWPN

Wwnn WWNN




BootAvailability Boot Availability


In the following example, the Get-LparDedicatedFCPort cmdlet returns


Command

Get-LparDedicatedFCPort -ServerIPAddress xx.xx.xx.xx –lparno 10

Output

Add-LPARDedicatedFCPort

Add-LparDedicatedFCPort adds dedicated FC ports to a specified logical

partition and displays the information in the PowerShell console. Also, all FC

ports of this dedicated FC card will be assigned to the logical partition.

Syntax

Add-LparDedicatedFCPort [–ServerIPAddress] <IPAddress> [–LparNo] <Int> [-PCIDeviceNo] <Int> [-saveConfig] <Boolean>

For more information, type Get-Help Add-LparDedicatedFCPort in the

PowerShell console.

Input Parameters


ServerIPAddress -SIP Y The IP address of the Baseboard Management Controller (BMC) of the

current blade server. The BMC runs independent of the blade processor and of



PCIDeviceNo Y Number Existing dedicated FC pci device No.

BootPorts BP N The port can be used for boot(e.x, 0,1. Please seprare the portnumber by comma). Also, only Hitachi

FC card can configure bootable dedicated FC port.

SaveConfig Boolean Save the config

Output Items

Add-LparDedicatedFCPort cmdlet adds dedicated FC ports to a specified

logical partition and displays the information in the PowerShell console. Also, all FC ports of this dedicated FC card will be assigned to the LPAR.

The Add-LparDedicatedFCPort sends a collection of the output object to the

pipeline. The output object type is result record, with the properties listed in the table below.



Message The console displays an error

message when the command fails.

Result "Completed"

"Failed"




In the following example, the Add-LparDedicatedFCPort cmdlet returns


Command

Add-LparDedicatedFCPort -ServerIPAddress xx.xx.xx.xx –lparno 10 –PCIDeviceNo 5

Output

Remove-LPARDedicatedFCPort

Remove-LparDedicatedFCPort removes dedicated FC ports to a specified

logical partition and displays the information in the PowerShell console. Also, all FC ports of this dedicated FC card will be removed from the logical partition.

Syntax

Remove-LparDedicatedFCPort [–ServerIPAddress] <IPAddress> [–LparNo] <Int> [-PCIDeviceNo] <Int> [-saveConfig] <Boolean>

For more information, type Get-Help Remove-LparDedicatedFCPort in the

PowerShell console.

Input Parameters


ServerIPAddress SIP Y The IP address of the Baseboard

Management Controller (BMC) of the current blade server. The BMC runs independent of the



PCIDeviceNo The PCI device Number for the dedicated FC card


SaveConfig Save the config

Output Items

Remove-LparDedicatedFCPort sends a collection of the output object to the

pipeline. The output object type is result record, with the properties listed in

the table below.



Message The console displays an error message when the command fails.

Result "Completed"

"Failed"


In the following example, the Add-LparDedicatedFCPort cmdlet returns


Command

Remove-LparDedicatedFCPort -ServerIPAddress xx.xx.xx.xx –lparno 10 –PCIDeviceNo 5

Output

Set-LPARBootOrder

Set-LparBootOrder acquires information about the boot order of the specified


Syntax

Set-LparBootOrder [–ServerIPAddress] <IPAddress> [–LparNo] <Int> -DeviceIDList <List<string>> [-SaveConfig]

For more information, type Get-Help Set-LparBootOrder in the PowerShell

console.



Input Parameters


ServerIPAddress

SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs



DeviceIDL

ist

DIL Y The list of boot device identifier.

SaveConfig

SC Optional Save the config

Output Items

Set-lparBootOrder sends a collection of the output object to the pipeline. The

output object type is result record, with the properties listed in the table below.




Result "Completed"

"Failed"


In the following example, the get-LparBootOrder cmdlet returns boot order


Command

Set-LparBootOrder -ServerIPAddress xx.xx.xx.xx –lparno 10 – DeviceIDList 00:00:87:38:E9:05_0, EFI-SHELL

Get-LPARMemory

Get-LparMemory acquires information about memory of the specified logical

partition and displays the information in the PowerShell console.

Syntax

Get-LparMemory [–ServerIPAddress] <IPAddress> [–LparNo] <Int>

For more information, type Get-Help Get-LparMemory in the PowerShell

console.

Input Parameters


ServerIPAddress

SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The



Output Items

Get-LparMemory sends a collection of the output object to the pipeline. The

output object type is LPARMemory, which has the following properties:


ServerUniqueKey Unique ID among all of managed

chassis, servers (Blades/Racks/Generic

Computers), and switch modules,

including those from third-party vendors.



MemorySizeInMB Memory Size (unit:MB)

MemoryNodeNo Memory Node No. (i.e.,

node no

"Automatically"

"Automatically(Multiple)")


In the following example, the Get-LparMemory cmdlet returns memory

information for the specified logical partition.

Get-LparMemory -ServerIPAddress xx.xx.xx.xx –lparno 10



Set-LparMemory

Set-LparMemory acquires information about memory of the specified logical

partition and displays the information in the PowerShell console.

Syntax

Set-LparMemory [–ServerIPAddress] <IPAddress> [–LparNo] <Int>[-MemoryNodeNo <String>] [–MemorySizeInGB] <Int> [-SaveConfig]

For more information, type Get-Help Set-LparMemory in the PowerShell

console.

Input Parameters




LparNo LN Y The number of the logical partition number

MemorySizeInGB MS Y The size of memory.

SaveConfig SC N Save the config

Output Items

Set-LparMemory sends a collection of the output object to the pipeline. The

output object type is LPARMemory, which has the following properties:



(Blades/Racks/Generic Computers), and switch modules, including

those from third-party vendors.



MemorySizeInMB Memory Size (unit:MB)


MemoryNodeNo Memory Node No. (i.e.,

node no

"Automatically"

"Automatically(Multiple)")


In the following example, the Set-LparMemory cmdlet returns memory


Command

Set-LparMemory -ServerIPAddress xx.xx.xx.xx –lparno 10 –MemorySizeInGB 2



Get-LPARCPU

Get-LparCPU acquires information about CPUs of the specified logical partition


Syntax

Get-LparCPU [–ServerIPAddress] <IPAddress> [–LparNo] <Int>

For more information, type Get-Help Get-LparCPU in the PowerShell console.

Input Parameters




Output Items

Get-LparCPU cmdlet sends a collection of the output object to the pipeline. The

output object type is LPARCPU, which has the following properties:



(Blades/Racks/Generic Computers), and switch modules, including




LogicalCpuNo Logical CPU Number

AssignedPhysicalCpuNo Assigned Physical CPU Number (Integer or "Automatically")


In the following example, the Get-LparCPU cmdlet returns CPU information for

the specified LPAR.

Command

Get-LparCPU -ServerIPAddress xx.xx.xx.xx –lparno 10

Set-LPARCPU

Set-LparCPU sets the CPUs of the specified LPAR and displays the information

in the PowerShell console.

Syntax

Shared:

Set-LparCPU [–ServerIPAddress] <IPAddress> [–LparNo] <Int> [-LogicalCpuNo] <Int> [-CpuGroup <Int>] [-CpuAllocationRatio <Int>] [-CpuIdleDet] [-CpuPerformanceCapping] [-SaveConfig]

Dedicated:

Set-LparCPU [–ServerIPAddress] <IPAddress> [–LparNo] <Int> [-LogicalCpuNo] <Int> [-CpuGroup <Int>] [-LogicalCpuNoList <List<String>] [-CpuIdleDet] [-CpuPerformanceCapping] [-SaveConfig]

For more information, type Get-Help Set-LparCPU in the PowerShell console.

Input Parameters

Parameter Set: Shared




NumofLogicalCpu LCN Y The number of logical CPUs (For CB520H, you can set a value from 1 to 32. For CB520X, you

can set a value from 1 to 64.)

CpuGroup CG N CPU Group(default value: 0)

CpuAllocationRatio CAR N The ratio of all priority values of the virtualized CPUs

(default value: 100; possible value: 1-999)

CpuIdleDetection CID N CPU idle detection

(default value: true)




CpuPerformanceCapping CPC N CPU performance capping. With the processor capping function on, the shared mode LPAR does

not take on the unused (idle) capacity of

other LPARs even if the LPAR requires more performance than its allocation

rate (busy status). Because of the unused capacity, the LPAR's

processor-time never uses more processor-time the allocation rate, even if it

is busy.

Default value: true

SaveConfig SC N Save the config (default value:true)

Parameter Set: Dedicated






NumofLogicalCpu LCN Y The number of logical CPUs

CpuGroup CG N CPU Group(default value: 0)

LogicalCpuNoList LCNL N Define the relation of logical CPU and physical CPU

CpuIdleDet CID N CPU idle detection

(default value: true)

SaveConfig SC N Save the config(default value:true)

Output Items

Set-LparCPU sends a collection of the output object to the pipeline. The output

object type is result record, with the properties listed in the table below.





Result "Completed"

"Failed"


In the following example, the Set-LparCPU cmdlet returns CPU information for

the specified LPAR.

Command

Shared:

Set-LparCPU -ServerIPAddress xx.xx.xx.xx –lparno 10 –LogicalCpuNo 10

Get-ServerLparPhysicalCPU

Get-ServerLparPhysicalCPU acquires information about all available physical

CPUs for logical partition on the specified server and displays the information in the PowerShell console.

Syntax

Get-ServerLparPhysicalCPU [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-ServerLparPhysicalCPU in the

PowerShell console.

Input Parameters



current blade server. The BMC runs independent of the blade processor and of


Output Items

Get-ServerLparPhysicalCPU sends a collection of the output object to the

pipeline. The output object type is ServerLparPhysicalCPU, which has the

following properties:





ServerUniqueKey Unique ID among all of managed chassis, servers (Blades/Racks/Generic


ServerBladeNo Server blade number

CpuNo CPU number

SocketNo Socket number

CoreNo Assigned Physical CPU number (Integer or "Automatically")

ThreadNo The thread number

CoreStatus The status of the core. It has the following values:

"High"

"MXX" (ex. M01)

"Low"

"Failure"

"Error"

"Offline"

CpuStatus The status of CPU

CpuGroupNo The CPU Group number

CpuAllocation The ratio between the priority values for each virtualized CPU.

(Default Value: 100; Possible Values: 1 - 999)

NumaNodeNo A NUMA node number that the physical CPU belongs to. If NUMA node is not supported, the value is empty string.


In the following example, the Get-ServerLparPhysicalCPU cmdlet returns all

available physical CPUs for logical partition on the specified blade.

Command

Get-ServerLparPhysicalCPU -ServerIPAddress xx.xx.xx.xx

Get-ServerLparCPUGroup

Get-ServerLparCPUGroup acquires information about all available CPU groups

for logical partition on the specified server and displays the information in the

PowerShell console.

Syntax

Get-ServerLparCPUGroup [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-ServerLparCPUGroup in the

PowerShell console.

Input Parameters


ServerIPAddress SIP Y The IP address of the Baseboard Management Controller (BMC) of the current blade server. The BMC runs independent of

the blade processor and of failures associated with it.

Common Parameters

Get-ServerLparCPUGroup supports the following common parameters:

Verbose

Debug

ErrorAction

ErrorVariable

WarningAction

WarningVariable

OutBuffer

OutVariable


PowerShell console.

Output Items

Get-ServerLparCPUGroup sends a collection of the output object to the

pipeline. The output object type is ServerLparCPUGroup, which has the following properties:






(Blades/Racks/Generic Computers), and switch modules, including those from third-party vendors.

GroupNo Group Number

GroupName Group Name

NumOfSharedCores Shared Cores

NumOfDedicatedCores Dedicated Cores

NumOfThreads Number of Threads


In the following example, the Get-ServerLparCPUGroup cmdlet returns all

available CPU groups for LPAR on the specified blade.

Command

Get-ServerLparCPUGroup -ServerIPAddress xx.xx.xx.xx

Get-ServerBootOrder

Get-ServerBootOrder acquires information about the boot order of the

specified server and displays the information in the PowerShell console.

Syntax

Get-ServerBootOrder [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-ServerBootOrder in the PowerShell

console.

Input Parameters

Parameter Alias Y/N Description Accept wildcard

characters?


Controller (BMC) of the current blade server. The BMC runs independent of the


No

Common Parameters

Get-ServerBootOrder supports the following common parameters:

Verbose

Debug

ErrorAction

ErrorVariable

WarningAction

WarningVariable

OutBuffer

OutVariable


PowerShell console.

Output Items

Get-ServerBootOrder sends a collection of the output object to the pipeline.

The output object type is ServerBootOrder, which has the following properties:


ServerUniqueKey Unique key among all of managed chassis, servers (Blades/Racks/Generic Computers), and switch modules, including





CurrentBootOrderList A list of current devices to boot. Each device is separated by

comma. Each server may have a different boot device. Common boot devise are CD/DVD ROM, PXE

Network, or Hard Disk 1.

PossibleBootDeviceList A list of possible devices to boot. Common boot devise are CD/DVD

ROM, PXE Network, or Hard Disk 1.


In the following example, the Get-ServerBootOrder cmdlet returns the

cuurent bootorder and available boot devices of the specified blade.

Command

Get-ServerBootOrder -ServerIPAddress xx.xx.xx.xx

Set-ServerBootOrder

Set-ServerBootOrder acquires information about the boot order of the

specified server and displays the information in the PowerShell console.

Syntax

Set-ServerBootOrder [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Set-ServerBootOrder in the PowerShell

console.

Input Parameters


characters?


Controller (BMC) of the current blade server. The


No


characters?

BootOrderList BOL Y The list of devices to boot. Each device is separated by

comma. Each server may have a different boot device.

Common boot devise are CD/DVD ROM, PXE Network, or Hard Disk 1.

No

Output Items

Set-ServerBootOrder sends a collection of the output object to the pipeline.

cmdlet sends a collection of the output object to the pipeline. The output object type is result record, with the properties listed in the table below.





Result "Completed"

"Failed"


In the following example, the Set-ServerBootOrder cmdlet sets the bootorder

on the specified blade.

Command

Set-ServerBootOrder -ServerIPAddress xx.xx.xx.xx –BootOrderList "CD/DVD Rom","Hard Disk 0","PXE Network"

Get-QuantaCPU

Get-QuantaCPU acquires CPU information for the specified Quanta server and


Syntax

Get-QuantaCPU [-ServerIPAddress] <IPAddress>



For more information, type Get-Help Get-QuantaCPU in the PowerShell

console.

Input Parameters


characters?

ServerIPAddress -SIP Required The BMC IP address of a quanta server Named.

The parameter name must be specified in the command with the input

parameter value.

No

Output Items

Get-QuantaCPU sends a collection of the output object to the pipeline. The

output object type is QuantaCPUInfo, which has the following properties:


LocationName The location of the processor (i.e., CPU0)

Frequency The frequency of the processor (i.e., 2400 MHz)

ModelName The model name of the processor (i.e., Haswell)

ManufacturerName The manufacturer name of the processor(i.e., Intel)

ProcessorIndex The index (from 1) of the

processor.

Status The status of the processor slot(processorNotPresent, processorPresent)


In the following example, the Get-QuantaCPU cmdlet returns CPU information

for the specified Quanta server.

Command

Get-QuantaCPU -ServerIPAddress 172.17.59.59

Get-QuantaMemory

Get-QuantaMemory acquires the memory information about the specified

Quanta server and displays the information in the PowerShell console.

Syntax

Get-QuantaMemory [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-QuantaMemory in the PowerShell

console.

Input Parameters


characters?

ServerIPAddress SIP Required The BMC IP address of a

quanta server

No

Output Items

Get-QuantaMemory sends a collection of the output object to the pipeline. The

output object type is QuantaMemoryInfo, which has the following properties:


MemoryIndex The index (from 1) of the memory slot

Frequency The frequency of the memory device (i.e., 1866 MHz)

ModelName The model name of the memory device (i.e., DDR-4 RAM-DDR4 normal Voltage (1.2V))

MemorySize The size of the memory device (i.e., 16384 MB)

LocationName The location name of the memory device (DIMM A1).

Status The status of the memory device (memoryNotPresent, memoryPresent)


In the following example, the Get-QuantaMemory cmdlet returns memory

information for the specified Quanta server.



Command

Get-QuantaMemory -ServerIPAddress 172.17.59.59

Get-QuantaFan

Get-QuantaFan acquires the memory information about the specified Quanta

server and displays the information in the PowerShell console.

Syntax

Get-QuantaFan [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-QunataFan in the PowerShell

console.

Input Parameters


characters?

ServerIPAddress SIP Required The BMC IP address of a Quanta server

No

Output Items

Get-QuantaFan sends a collection of the output object to the pipeline. The

output object type is QuantaFanInfo, which has the following properties:


FanIndex The index (from 1) of the Fan device

Status The status of the fan device(other, unknown, ok, nonCriticalUpper, criticalUpper,

nonRecoverableUpper, nonCriticalLower, criticalLower,

nonRecoverableLower, failed)

LocationName The location name of the fan device (i.e., Fan_SYS0_1).

Reading The rotation speed of the fan device (i.e., 3900).

If this value cannot be determined

by software, then a value of -99 will be returned.


UpperNonRecoverableThreshold It defines the Upper NonRecoverable

Threshold for fan sensor. If this

value cannot be determined by software, then a value of -99 will

be returned.

UpperCriticalThreshold It defines the Upper Critical Threshold for fan sensor. If this value cannot be determined by

software, then a value of -99 will be returned.

UpperNonCriticalThreshold It defines the Upper NonCritical Threshold for fan sensor. If this


be returned.

LowerNonCriticalThreshold It defines the Lower NonCritical Threshold for fan sensor. If this value cannot be determined by


LowerCriticalThreshold It defines the Lower Critical Threshold for fan sensor. If this


be returned.

LowerNonRecoverableThreshold It defines the Lower NonRecoverable

Threshold for fan sensor. If this value cannot be determined by



In the following example, the Get-QuantaFan cmdlet returns memory


Command

Get-QuantaFan –ServerIPAddress 172.17.59.59


Get-QuantaSystemStatus acquires the system status information about the

specified Quanta server and displays the information in the PowerShell console.



Syntax

Get-QuantaSystemStatus [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get in the PowerShell console.

Input Parameters


ServerIPAddress SIP Required The BMC IP address of a quanta server

Output Items

Get-QuantaSystemStatus sends a collection of the output object to the

pipeline. The output object type is QuantaSystemStatusInfo, which has the following properties:


VoltageStatusOverall Voltage Status Overall (other, unknown, ok, noncritical, critical, nonRecoverable)

FanStatusOverall Fan Status Overall (other, unknown, ok, noncritical, critical, nonRecoverable)

TemperatureStatusOverall Temperature Status Overall (other, unknown, ok, noncritical, critical,

nonRecoverable)

PowerSupplyRedundancy Power Supply Redundancy Status (other,full,lost)

PowerSupply0Status Power Supply 0 Status (AllDeasserted,

PresenceDetected,

PowerSupplyFailureDetected,

PredictiveFailure,

PowerSupplyInputLost_ACDC)

PowerSupply1Status Power Supply 1 Status (AllDeasserted,

PresenceDetected,

PowerSupplyFailureDetected,

PredictiveFailure,

PowerSupplyInputLost_ACDC)


Get-QuantaSystemStatus returns system status information for the specified

Quanta server.

Command

Get-QuantaSystemStatus -ServerIPAddress 172.17.59.59

Get-QuantaServer

Get-QuantaServer acquires the SNMP agent information about the specified

Quanta server and displays the information in the PowerShell console.

Syntax

Get-QuantaServer [–ServerIPAddress] <IPAddress>

For more information, type Get-Help Get-QuantaServer in the PowerShell

console.

Input Parameters


ServerIPAddress -SIP Y The BMC IP address of a Quanta server

Output Items

Get-QuantaServer sends a collection of the output object to the pipeline. The

output object type is QuantaServer, which has the following properties:


AgentBMCVersion BMC version number

AgentServerIdentify Server Identify (off,on,blinking)

AgentChassisStatus Chassis status (powerIsOFF,powerIsON,powerOverLoad,interlock,p

owerFault,powerControlFault)

AgentMIBVersion The version number for this MIB supported by the BMC.

AgentSystemBIOSVersion

System BIOS version

AgentBMCIP BMC IP address

AgentBMCMAC BMC MAC address




In the following example, the Get-QuantaServer cmdlet returns SNMP agent


Command

Get-QuantaServer -ServerIPAddress 172.17.59.59

Set-QuantaBootOrder

Set-QuantaBootOrder sets the boot order on the Quanta server.

Syntax

Set-QuantaBootOrder -BootOption <QuantaBootOptionEnum> -ServerIP <string> [-UserID <string>] [-Password <string>] [<CommonParameters>]

For more information, type Get-Help Set-QuantaBootOrder in the PowerShell

console.

Input Parameters


ServerIP -SIP Y The BMC IP address of a Quanta server

UserID -U Y IPMI User ID for access of the Quanta server

Password -P Y IPMI password for access to the quanta server

BootOption -bo Y Boot Option for Quanta Server

Output Items

Set-QuantaBootOrder shows.


In the following example, the Set-QuantaBootOrder cmdlet returns result


Command

Set-QuantaBootOrder

Logging and Troubleshooting 159


Logging and Troubleshooting

This chapter includes the following sections:

Logging

Log Files

Log Setting

Log Rotation

Troubleshooting

Error Messages

160 Logging and Troubleshooting


Logging

The Hitachi Server Adapter for Microsoft Windows PowerShell® writes to the

logs as shown below:

Table 4 Log Output of Each Module

# Program Log file Event Log Other output

1 HiServerPowerShell.dll hipowershell_server.log

No -

2 Installer - No Message dialog

The log levels defined in the Windows registry are shown below:

Table 5 Log Level

# Log level ValueX1 Output to log fileX2

Output to event

log

Description

1 STAT 0x00000000 X - Writes operational status to the log file.

2 INFO 0x00000001 X - Enables informational logging that provides

information about the operations. Informational logging option is usually

enabled specifically for troubleshooting, because it

creates a large log file and can slow down performance.

3 WARNING 0x00000000 X - The program can continue its process, but alerts you.

4 ERROR 0x00000000 X - An error occurs, and the program stops processing.

5 PARAM 0x00000080 X - Writes parameter values of the invoked methods to the log file.

6 All 0xFFFFFFFF X - Writes all log level statements to the log file.

Log Files

Log files are created in the log subdirectory of the installation directory of the

Hitachi Server Adapter for Microsoft Windows PowerShell® at <System Drive>\Users\<user>\AppData\Local\Hitachi\ HiServerPowerShell\log.

When the log file exceeds 10MB (1MB=1024byte), it is renamed as

<logfilename>.bak, and a new log file is created. When the older file

<logfilename>.bak already exists, it is overwritten.

Log file has the following format:

One log item per line.

In each log item, the following columns are connected with a blank:

Table 6. Log Item Fields

# Format Description of the Variables

1 [process ID] process ID: Process ID of the Hitachi SCOM connector Windows service.

2 [Date-Time] Date: MM/DD/YY format,

MM: month, DD: date, YY: year

Time: hh:mm:ss

hh: hour(01-24), mm: minutes, ss: seconds

Each value is 2-digits (spaces filled with 0).

3 [Module] Module : Class name

When the name is less than 7 characters, blanks

are filled in to the right.

4 Level Level : Log level.

5 Message Code Status

message

S240####

Error message

E240####

Warning message

W240####

Info message I240####

Debug message

--------

XX where #### = four hex digit Message ID

6 {Class::Method(Serial)}:Message

Class: Class name

Method: Method name

Serial: Serial number of the storage when the S-

VOL resides

Message: Message strings



Log Setting

The log levels can be set by the variable DebugLevel in

HiServerPowerShell.config configuration file.

The DebugLevel can have one of these values: MINIMAL, NORMAL, or VERBOSE.

Log Rotation

Multiple log generation and rotation of the adapter log files create multiple Hitachi Storage Integration Pack logs.

The log generation and rotation of the adapter log files allows you to:

Log the multiple processes to the same file.

Determine the maximum number of consecutive files by using a user-specified parameter or a system default.

Rotate the current or active log file by incrementing the log file name, appending consecutive numbers that starts from zero to a user-specified limit or a system default.

Log the entries that are written to a temporary file when the log file is locked at the time of the rotation. The backup file is created and rotation stops. After the log file is unlocked, rotation continues, but

the temporary files are not deleted.

Specify a maximum log file size in HiLogger.Config by creating a key call [MaxFileSize] in a separate line. The minimum value is 5MB, and the maximum value is 100MB.

o If [MaxFileSize] is not specified in HiLogger.Config, the default value is

10MB.

o If [MaxFileSize] is out of range, the value is the default of 10MB.

Specify a maximum backup log file in HiLogger.Config by creating a key call [MaxBackupIndex] in a separate line. MaxBackupIndex minimum value is 1, and the maximum value is 255.

If [MaxBackupIndex] is not specified in HiLogger.Config, the default

value is 5.

If [MaxBackupIndex] value is out of range, it defaults to 5.

Troubleshooting

Symptom Recommended Action

A cmdlet fails to run.

Each cmdlet has exception handling and error codes. Check for exceptions and error codes in the

output messages. Refer the log file for the detailed information.

Chassis and/or server cannot be registered

through the PowerShell cmdlet.

Ensure that the HCSM server is accessible from the Windows machine where the Hitachi Computer

System Manager Web Service is configured and running. Verify this by navigating to:

http://<HCSM IP address>:<port>/ 22015/ComputeSystemsManager/api

AddChassis and/or AddServer cmdlets fail to

connect to the HCSM server. They display ”invalid

username/password.”

Ensure that the credentials supplied are correct.

A HCSM server call failed for the operation.

Do the following:

Check the HiServer.log for the cause of the error, as described in the SECTION NAME.

Change the log level to VERBOSE and retry the operation.

The Add-BladeChassis and/or AddServer cmdlets fail to connect to the HCSM server. They

display Invalid protocol when using the

HTTPS protocol to

communicate with a HCSM server that has a

self-signed SSL certification.

When you use Internet

Explorer to access the HCSM web page by HTTPS on the same

machine, Internet Explorer displays

Certificate Error.

Gain trust in the self-signed SSL certification by executing the following steps:

1. Use Internet Explorer to browse the HCSM webpage whose certificate you want to trust. For example:

https://<HCSMIPaddress>:22016/ComputeSystemsManager/index.jsp)

2. When the message There is a problem with this website's security certificate

appears, choose "Continue to this website (not recommended)."

3. Click Certificate Error at the right of the address bar and select View Certificates.

4. Click Install Certificate. Go to the wizard, and

click Next.

5. On the following page, select Place all certificates in the following store.

6. Click Browse, select Trusted Root Certification

Authorities, and click OK.

7. Back in the wizard, click Next, and then click



Symptom Recommended Action

Finish.

8. If a Security Warning message appears,

click Yes.

9. Shut down all running instances of Internet Explorer, and then restart Internet Explorer.

The HCSM's SSL certificate should now be

trustworthy.

Invalid port Check the HCSM port number.

Invalid IP or port Check the HCSM IP address and port number.

This LPAR is already deactivated. Please activate it and then try

again.

Activate the logical partition before running this workflow.

This LPAR is already activated. Please deactivate it and then try

again.

Deactivate the logical partition before running this workflow.

Power must be on for this operation.

Shut off the server power before running this workflow.

Error Messages

E280B101

Error Message ID E280B101

Error Message Text The version of cmdlet cannot be retrieved.

Explanation

Recommended Action

Please re-install the Adapter or contact technical support.

E280B102


Error Message Text This cmdlet does not support pipeline input.

Explanation

Recommended Action

Please change the pipeline input.

E280B103


Error Message Text Invalid HCSM username, password, or protocol.

Explanation

Recommended Action

Please check username, password, or protocol.

E280B104


Error Message Text Invalid HCSM IP or port.

Explanation

Recommended Action

Please check HCSM IP and port.

E280B105


Error Message Text Error while adding the chassis.

Explanation

Recommended Action

Please check HCSM server status. Ensure the chassis has been discovered and is managed by HCSM.

E280B106


Error Message Text Error while retrieving the chassis.

Explanation

Recommended Action

Please check the HCSM server status and the LAN environment.

E280B107


Error Message Text Error while retrieving the fan.

Explanation

Recommended Action

Please check HCSM server status and the LAN environment.

E280B108


Error Message Text Error while retrieving the FC switch.

Explanation

Recommended Action


E280B109




Error Message Text Error while retrieving the LAN switch.

Explanation

Recommended Action


E280B110


Error Message Text Error while retrieving the management module.

Explanation

Recommended Action


E280B111


Error Message Text Error while retrieving the logic partition information.

Explanation

Recommended Action


E280B112


Error Message Text Error while adding the server.

Explanation

Recommended Action


E280B113


Error Message Text Error while retrieving the power supply.

Explanation

Recommended Action


E280B114


Error Message Text Invalid user ID.

Explanation

Recommended

Action

Please check user ID.

E280B115


Error Message Text Error while setting the LID on on the chassis.

Explanation

Recommended Action


E280B116


Error Message Text Error while setting the LID off on the chassis.

Explanation

Recommended Action


E280B117


Error Message Text Error while setting the LID on the server.

Explanation

Recommended Action


E280B118


Error Message Text Error while setting the LID off on the server.

Explanation

Recommended Action


E280B119


Error Message Text Error while setting the power on for the server.

Explanation

Recommended

Action

Please check HCSM server status and the LAN

environment.

E280B120


Error Message Text Error while setting the power off for the server.

Explanation

Recommended Action

Please check HCSM server statusand the LAN environment.



E280B121


Error Message Text Error while setting the power reset for the server.

Explanation

Recommended Action


E280B122


Error Message Text Error while retrieving the server.

Explanation

Recommended Action


E280B123


Error Message Text Error while retrieving the server HBA port.

Explanation

Recommended Action


E280B124


Error Message Text Error while retrieving the server NIC port.

Explanation

Recommended Action


E280B125


Error Message Text Error while removing the server.

Explanation

Recommended

Action

Please check HCSM server status and the LAN

environment.

E280B126


Error Message Text Error while removing the chassis.

Explanation

Recommended Please check the HCSM server status and the LAN

Action environment.

E280B127


Error Message Text Invalid file path.

Explanation

Recommended Action

Please check the file path.

E280B128


Error Message Text Error while disabling the forcepxe on the server.

Explanation

Recommended Action


E280B129


Error Message Text Error while enabling the forcepxe for the server.

Explanation

Recommended Action


E280B130


Error Message Text Error while retrieving the server EFI settings.

Explanation

Recommended Action


E280B131


Error Message Text Error while retrieving the last set of server MAC addresses.

Explanation

Recommended Action


E280B132


Error Message Text Error while retrieving the last set of server WWN.



Explanation

Recommended Action


E280B133


Error Message Text Error while resetting the server MAC addresses.

Explanation

Recommended Action


E280B134


Error Message Text Error while resetting the server WWN.

Explanation

Recommended Action


E280B135


Error Message Text Error while setting the server MAC addresses.

Explanation

Recommended Action


E280B136


Error Message Text Error while setting the server WWN.

Explanation

Recommended Action


E280B137


Error Message Text Error while registering the server to WDS.

Explanation

Recommended Action

Please check WDS server configuration and LAN environment.

E280B138


Error Message Text Invalid input parameter.

Explanation

Recommended Action

Please check the input parameter.

E280B139


Error Message Text Invalid operation while resetting the server power.

Explanation

Recommended Action

Please check if the server is powered off.

E280B140


Error Message Text Error message of invalid operation from the HCSM server.

Explanation

Recommended Action

Please check HCSM logs.

E280B141


Error Message Text Error message of invalid operation from the HCSM server.

Explanation

Recommended

Action


E280B142


Error Message Text Error message of invalid operation from the HCSM

server.

Explanation

Recommended Action


E280B143


Error Message Text An activated Lpar cannot be operated. Please deactivate it first and then try again.



Explanation

Recommended Action

Please deactivate this Lpar.

E280B144


Error Message Text A deactivated Lpar cannot be operated. Please activate it first and then try again.

Explanation

Recommended Action

Please activate this Lpar.

E280B145


Error Message Text An existing virtual NIC port cannot be operated. Please activate it first and then try again.

Explanation

Recommended Action

Please remove this virtual NIC port.

E280B146


Error Message Text An existing virtual FC port cannot be operated. Please activate it first and then try again.

Explanation

Recommended Action

Please remove this virtual FC port.

E280B147


Error Message Text This Lpar is invalid. Please check your input and then try again.

Explanation

Recommended Action

Please check the Lpar.

E280B148

Error Message ID 0XB148

Error Message Text ERROR_ADD_LparSHAREDFCPORT_CMDLET_1

Explanation Error while adding the shared FC port to the Lpar.

Recommended Action

Check the HCSM logs.

E280B149


Error Message Text ERROR_ADD_LparVIRTUALNICPORT_CMDLET_1

Explanation Error while adding the virtual NIC port to the Lpar.

Recommended Action


E280B14A

Error Message ID 0XB14A

Error Message Text ERROR_ADD_QUICKLpar_CMDLET_1

Explanation Error while adding the quick Lpars to the server.

Recommended Action


E280B14B

Error Message ID 0XB14B

Error Message Text ERROR_GET_LparSHAREDFCPORT_CMDLET_1

Explanation Error while getting the shared FC port information from the Lpar.

Recommended Action


E280B14C

Error Message ID 0XB14C

Error Message Text ERROR_GET_LparVIRTUALNICPORT_CMDLET_1

Explanation Error while getting the virtual NIC port on the Lpar

Recommended Action


E280B14D

Error Message ID 0XB14D

Error Message Text ERROR_GET_SERVER_LparFCPORT_CMDLET_1

Explanation Error while getting all FC ports for all Lpars from this server.

Recommended Action


E280B14E

Error Message ID 0XB14E



Error Message Text ERROR_GET_SERVER_LparNICPORT_CMDLET_1

Explanation Error while getting the available NIC port for Lpar on the server.

Recommended Action


E280B14F

Error Message ID 0XB14F

Error Message Text ERROR_REMOVE_Lpar_CMDLET_1

Explanation Error while removing the Lpar from the server.

Recommended Action


E280B150


Error Message Text ERROR_REMOVE_LparSHAREDFCPORT_CMDLET_1

Explanation Error while removing the shared FC port from the Lpar.

Recommended

Action


E280B151


Error Message Text ERROR_REMOVE_LparVIRTUALNICPORT_CMDLET_1

Explanation Error while removing the virtual NIC port from the Lpar.

Recommended Action


E280B152


Error Message Text ERROR_SET_LparACTIVATE_CMDLET_1

Explanation Error while setting the Lpar activation.

Recommended

Action


E280B153


Error Message Text ERROR_SET_LparDEACTIVATE_CMDLET_1

Explanation Error while setting the Lpar deactivation.

Recommended Action


E280B154


Error Message Text ERROR_SET_LparREACTIVATE_CMDLET_1

Explanation Error while setting the Lpar reactivation.

Recommended Action


E280B155


Error Message Text INVALID_Lpar_SHAREDFC_VFCID

Explanation Omva;od VFC Id. Please try again.

Recommended Action


E280B156


Error Message Text INVALID_Lpar_SHAREDFC_SLOTNO

Explanation Invalid slot No. Please try again.

Recommended Action


E280B157


Error Message Text INVALID_Lpar_SHAREDFC_PORTNO

Explanation Invalid port No. Please try again.

Recommended

Action


E280B158


Error Message Text Invalid status of Lpar Manager. Please enable and

turn on Lpar Manager and try again.

Explanation The Lpar Manager status is invalid.

Recommended Action

Check Lpar Manager.

E280B159


Error Message Text Error while getting the physical Cpus for Lpar.




Recommended Action

Check Lpar Manager.

E280B15A


Error Message Text Error while getting the cpu group for Lpar.


Recommended Action

Check Lpar Manager.

E280B15B


Error Message Text Error while getting the logical CPUs on the Lpar.


Recommended Action

Check Lpar Manager.

E280B15C

Error Message ID 0XB15C

Error Message Text Error while getting the memory settings on the Lpar.


Recommended Action

Check Lpar Manager.

E280B15D

Error Message ID 0XB15D

Error Message Text Error while getting the boot order settings on the Lpar.


Recommended Action

Check Lpar Manager.

E280B15E

Error Message ID 0XB15E

Error Message Text Error while getting the boot order settings on the server.


Recommended Check Lpar Manager.

Action

E280B160


Error Message Text Error while setting the CPUs on the Lpar.


Recommended Action

Check Lpar Manager.

E280B161


Error Message Text Error while setting the memory on the Lpar.


Recommended Action

Check Lpar Manager.

E280B162


Error Message Text Error while setting the boot order on the Lpar.


Recommended Action

Check Lpar Manager.

E280B164


Error Message Text Error while adding the dedicated FC on the Lpar.


Recommended Action

Check Lpar Manager

E280B165


Error Message Text Error while removing the dedicated FC on the Lpar.


Recommended Action

Check Lpar Manager.

E280B166


Error Message Text Error while getting the dedicated FC on the Lpar.




Recommended Action

Check Lpar Manager.

E280B167


Error Message Text Error while setting the boot order on the server.


Recommended Action

Check Lpar Manager.

E280B168


Error Message Text Invalid Lpar boot device identifier. Please check your input again and if that is correct then your requested hardware is not available at this time.


Recommended Action

Check Lpar Manager.

E280B169


Error Message Text Power must be off for this operation. Please shutdown this server.


Recommended Action

Check Lpar Manager.

E280B170


Error Message Text Please check your input again and if that is correct then your requested hardware is not available at this time.


Recommended

Action

Check Lpar Manager.

E280B171


Error Message Text Invalid operation. This function is not available

now for this server product model.


Recommended Action

Check Lpar Manager.

E280B172


Error Message Text Invalid SSL cert.


Recommended Action

Check Lpar Manager.

E280B173


Error Message Text Error while getting the dedicated NICs on the Lpar.


Recommended Action

Check Lpar Manager.

E280B174


Error Message Text Error while adding the dedicated NIC on the Lpar.


Recommended Action

Check Lpar Manager.

E280B175


Error Message Text Error while removing the dedicated NIC on the Lpar.


Recommended Action

Check Lpar Manager.

E280B176


Error Message Text Error while updating the server firmware on the Lpar.


Recommended Action

Check Lpar Manager.

E280B177




Error Message Text Error while updating the IO card firmware on the Lpar.


Recommended Action

Check Lpar Manager.

E280B178


Error Message Text Error while updating the IO card firmware on the Lpar.


Recommended Action

Check Lpar Manager.

E280B179


Error Message Text Error while getting the IO card firmware on the Lpar.


Recommended Action

Check Lpar Manager.

E280B180


Error Message Text Unable to connect to HCSM. Please check this computer’s network and proxy settings, and try again.


Recommended

Action

Check Lpar Manager.

E280B181


Error Message Text Invalid IP or port IPMI. Please check your input

again and if that is correct, then this server is not available at this time.


Recommended Action

Check Lpar Manager.

E280B182


Error Message Text Invalid IP or port for SNMP. Please check your input again and if that is correct then this server is

not available at this time.


Recommended Action

Check Lpar Manager.

E280B183


Error Message Text This Quanta server has been powered on. Please power it off and try the cmdlet again.


Recommended Action

Check Lpar Manager.

E280B184


Error Message Text This Quanta server has been powered off. Please power it on and try the cmdlet again.


Recommended

Action

Check Lpar Manager.

E280B185


Error Message Text Error while getting the CPU information of the

server.


Recommended Action

Check Lpar Manager.

E280B186


Error Message Text Error while getting the fan information of the server.


Recommended Action

Check Lpar Manager.



E280B187


Error Message Text Error while getting the memory information of the server.


Recommended Action

Check Lpar Manager.

E280B188


Error Message Text Error while getting the information of the server.


Recommended Action

Check Lpar Manager.

E280B189


Error Message Text Error while getting the system status of the server.


Recommended Action

Check Lpar Manager.

E280B18A


Error Message Text Error while setting the power on operation on the server.


Recommended

Action

Check Lpar Manager.

E280B18B


Error Message Text Error while setting the power off operation on the

server.


Recommended Action

Check Lpar Manager.

E390B1BC

Error Message ID 0XB1BC

Error Message Text Error while setting the power cycle operation on the server.


E280B301


Error Message Text Error while getting the Lpar information from the server.

Explanation

Recommended Action

Please check the HCSM log.

E280B302


Error Message Text Error while activating the Lpar.

Explanation

Recommended Action


E280B303


Error Message Text Error while reactivating the Lpar.

Explanation

Recommended Action


E280B304


Error Message Text Error while deactivating the Lpar.

Explanation

Recommended Action


E280B305


Error Message Text Error while getting the Lpar NIC information from the server.

Explanation

Recommended Action




E280B306


Error Message Text Error while getting the Lpar FC information from the server.

Explanation

Recommended Action


E280B307


Error Message Text Error while adding the virtual NIC to the Lpar.

Explanation

Recommended Action


E280B308


Error Message Text Error while adding the virtual FC to the Lpar.

Explanation

Recommended Action


E280B309


Error Message Text Error while removing the virtual NIC from the Lpar.

Explanation

Recommended Action


E280B30A

Error Message ID E280B30A

Error Message Text Error while removing the virtual FC from the Lpar.

Explanation

Recommended Action


E280B30B

Error Message ID E280B30B

Error Message Text Error while adding the quick Lpars to the server.

Explanation

Recommended Action


E280B30C

Error Message ID E280B30C

Error Message Text Error while removing the Lpar from the server.

Explanation

Recommended Action


E280B30D

Error Message ID E280B30D

Error Message Text Error while getting the virtual NIC information from the Lpar.

Explanation

Recommended Action


E280B30E

Error Message ID E280B30E

Error Message Text Error while getting the virtual FC information from the Lpar.

Explanation

Recommended

Action


Glossary 187


Glossary

This glossary defines the special terms, acronyms, and abbreviations used in this document. Click the desired letter below to display the glossary entries that start with that letter.

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

MK-92ADPTR061-03

A

Administrator Role

Using the configuration GUI with administrative access to the array.

AMS

Hitachi Adaptable Modular Storage

AMS1000

AMS1000 stands for the Adaptable Modular Storage 1000 series.

AMS2000 Family

AMS2000 Family stands for the Adaptable Modular Storage 2000 series.

B

C

CCI

Command control interface

CLPR

Cache logical partition

CM

Command device

CPU

Central Processing unit

CTL

Subsystem controller

CTL0

Controller 0

CTL1

Controller 1

CU

Control unit

CV

Custom-sized volume

Glossary 189


Cyl

Cylinder

Controller

The component in a storage system that manages all storage functions. It is analogous to a computer and contains a processors, I/O devices, RAM, power supplies, cooling fans, and other sub-components as

needed to support the operation of the storage system.

Controller IP Address (AMS series only)

An Internet Protocol (IP) address is a numerical label that is uniquely assigned to a controller of Hitachi subsystem.

Controller Port

COW

Copy-on-write Snapshot

copy-on-write

Point-in-time snapshot copy of any data volume within a storage

system. Copy-on-write snapshots only store changed data blocks, therefore the amount of storage capacity required for each copy is

substantially smaller than the source volume.

D

Data Services

Data services consist of data moving, data replication, data archiving and any other functions where data is involved.

Datastore

DKS

Disk controller

DMLU

Differential management logical unit

DNS

Domain name server

DiskShadow (Windows 2008 and later)

DiskShadow.exe is a tool that exposes the functionality offered by the

Volume Shadow Copy Service (VSS).

Device Manager

MK-92ADPTR061-03

By providing a single console for managing complex storage environments, Hitachi Device Manager software unifies and simplifies

storage management and gives you full control of your storage. Featuring both an intuitive graphical user interface (GUI) and a

complete command line interface (CLI), Device Manager allows you to centrally manage single or multiple Hitachi storage systems.

E

ESX Host

ESX Host(s) (xxx.xxx.xxx.xxx)

EMT64T

Extended Memory 64 Technology

EV

Enterprise Vault

F

FC

Fiber channel

FTP

File Transfer Protocol

H

Hi-Star

Hierarchical Star Network

Hitachi Content Platform (HCP)

An open highly scalable, intelligent archive that reserves and protects data.

Hitachi Dynamic Provisioning (HDP)

Advanced thin-provisioning software product that provides Virtual

Storage Capacity to simplify administration and addition of storage, eliminate application service interruptions, and reduce costs.

HCP

Hitachi Content Platform

HCP System

Glossary 191


Fully Qualified Name for HCP Server.

HDP

Hitachi dynamic provisioning pool

HDP Pool

Consists of one or more dedicated RAID groups. Up to 50 DP pools in

the AMS 2100, and 64 DP pools in the AMS2300/2500 are allowed. Each pool requires a unique pool ID.

HDP Optimization

An HDP pool can be optimized by rebalancing each HDP-VOL’s allocated

pool capacity evenly across each of the RAID groups. This is particularly effective after adding a RAID group to the HDP pool.

HDP Pool Capacity

Amount of total capacity assigned to a given HDP pool.

HDP Pool Capacity Threshold

Initial warning levels of high pool utilizations upon early (default 40%)

and depletion (50%) conditions.

HDP Pool Consumed Capacity

Amount of pool capacity already consumed.

HDP RAID Group

One or more physical RAID Groups that belong to the same HDP pool.

HDP-VOL

A virtual LU that consumes and maps storage space for areas of the LU

that have had data written to them. In HDP, it is required to associate the HDP-VOL with a HDP pool. The HDP-VOL needs to specify a HDP pool ID, HDP-VOL logical capacity, and HDP-VOL number. Many HDP-

VOLs can be defined for on HDP pool. A given HDP-VOL cannot be defined to multiple DP pools.

HDvM

Hitachi HiCommand Device Manager

Hitachi Tiered Provisioning

New to VSP arrays, allows automated provisioning of HDP pools and

volumes based on device performance characteristics.

Host Group

A group of hosts of the same operating system platform.

MK-92ADPTR061-03

HTTP

HyperText Transfer Protocol

HUS

Hitachi Unified System

I

IBM

International Business MAChines Corporation

IP

Internet Protocol

IP Address

An Internet Protocol (IP) address is a numerical label that is uniquely assigned to a device.

IETF

Internet Engineering Task Force

J

JRE

Java Runtime Environment

JVM

Java Virtual MAChine

L

LDEV

Logical device

Logical Volume (LV)

LU

Logical unit (LU): A logical volume that is configured for use by open-systems hosts (for example, OPEN-V).

LUN

Logical unit number

LU Path

Glossary 193


Logical unit (LU) path: The path between and open-systems host and a logical unit.

LU Size

Logical unit (LU) size: The size of the logical unit.

LVI

Logical volume image

M

Management

Management includes discovery, initialization, configuration, provisioning, health and performance monitoring, alarms and alerts, and other system management functions.

MP

Management pack

N

Namespace

Logical grouping of the objects within HCP repository.

O

OS

Operating system

Over Provisioning Threshold

Threshold value for DP pool over-provision warning (default 100%) and

limit (default 130%).

P

Parity Group

A parity group, also called an array group, is a group of hard disk drives (HDDs) that form the basic unit of storage for RAID subsystems. All

HDDs in a parity group must have the same physical capacity.

PG

Parity group

P-Vol

MK-92ADPTR061-03

Primary volume

Q

Quick Resynch

A resynchronizing operation wherein the pair status becomes Paired Internally Synchronizing.

Quick Split

Splitting a pair whose status is Synchronizing or Paired Internally Synchronizing.

R

RAID

Redundant array of inexpensive disks

RAID Group

A redundant array of inexpensive drives (RAID) that have the same

capacity and are treated as one group for data storage and recovery. A RAID group contains both user data and parity information, which allows the user data to be accessed in the event that one or more of the drives

within the RAID group are not available. The RAID level of a RAID group determines the number of data drives and parity drives and how the

data is striped across the drives. For RAID1, user data is duplicated within the RAID group, so there is no parity data for RAID1 RAID

groups.

A RAID group can also be called an array group or a parity group.

RAM

Random access memory

Raw Capacity

RCU

Remote control unit

RG

RAID group

RFC

Request for comment

Rijndel

Glossary 195


A cryptography algorithm that comprises the advanced encryption standard that consists of three block cipher AES-128, AES-192 and AES-

256.

RMI

Remote method invocation

S

SAN

Storage area network

SAS

Serial-attached SCSI

SATA

Serial Advanced Technology Attachment

SCSI

Small computer system interface

SI

ShadowImage in-system replication

SIM

Service information message

SMS

Hitachi Simple Modular Storage

SNMP

Simple Network Management Protocol

SN

Serial number

SNM2

Storage Navigator Modular 2 (for DF arrays only)

SPARC

Scalable processor architecture

SSL

Secure docket layer

Storage

MK-92ADPTR061-03

Storage array or device

Storage includes both block and file storage and a form factor that

scales from a single node appliance to large scalable multi-node configurations.

Storage Serial No.

Storage Type

S-VOL

Secondary volume

SVP

Service processor

T

Tenant

HCP administrative entity to manage and own namespaces.

TCP/IP

Transmission Control Protocol/Internet Protocol

Total Capacity

The aggregate amount of storage space in a data storage system.

TransID

U

UDP

User Datagram Protocol

URL

Uniform resource locator

USP

Universal Storage Platform

User Account

Uniquely identify a user for authentication and authorization to the

subsystem. A user uses his user account to authenticate to the subsystem. The subsystem uses the user account to determine the access rights for the login user.

V

Glossary 197


Vshadow (Windows 2003)

A command-line tool that you can use to create and manage volume

shadow copies.

VSP

Virtual Storage Platform

VSS Hardware Provider

A hardware-based provider service that intercepts and processes

requests for creating point-in-time copies of data through the Microsoft Volume Shadow Copy Service (VSS).

VSS

Volume Shadow Copy Service

V-VOL

Virtual volume

VOL

Volume

Volume Group

W

WMS

Hitachi Workgroup Modular Storage

WWW

A World Wide Name (WWN) is a unique identifier that identifies a particular Fiber Channel, Advanced Technology Attachment (ATA) or

Serial Attached SCSI (SAS) target. Each WWN is an 8 byte number derived from an IEEE OUI and vendor-supplied information.

MK-92ADPTR061-03

Hitachi Data Systems

Corporate Headquarters

2845 Lafayette Street

Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 www.hds.com [email protected]

Asia Pacific and Americas

2845 Lafayette Street Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 [email protected]

Europe Headquarters

Sefton Park Stoke Poges

Buckinghamshire SL2 4HD United Kingdom Phone: + 44 (0)1753 618000 [email protected]

http://www.hds.com/




Hitachi Server Adapter for Microsoft Windows PowerShell … · MK-92ADPTR061-03 Hitachi Server...

Documents

Transcript of Hitachi Server Adapter for Microsoft Windows PowerShell … · MK-92ADPTR061-03 Hitachi Server...