Home » HP Manuals » Storage Devices » HP XP1024 » Manual Viewer

HP XP1024 Migration User Guide for the HP Command View XP Portfolio and HP XP - Page 22

Migration procedures

Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

Migration procedures Use the following procedures to migrate to Command View AE and Remote Web Console environments in various arrangements. See "Migration planning" on page 12 to select your preferred scenario. Scenario 1: Migrate to Command View AE with Remote Web Console This migration involves transitioning array management from Command View to Command View AE with Remote Web Console. This is the preferred option for complete functionality. Environment This environment offers array management with Command View AE and Remote Web Console. Requirement(s) • Upgrade to firmware that supports the standalone Remote Web Console for XP12000/XP10000/XP1024/XP128 • Install Command View AE. See the basic installation requirements in the HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide. • You might require the XP512/XP48 Remote Control for access to provisioning features in Command View XP (for example, LUN management, LUN security, LUSE, and CVS), although Command View AE also supports those features. Use Remote Web Console with Command View to manage Auto LUN, Cache LUN, BC/CA, and other low-usage, complex features on the XP512/XP48. • Purchase a Command View AE capacity license for existing arrays • Use Remote Web Console for optional low-level configuration management for arrays • Migrate existing CLI scripts (see "CLI migration" on page 31) • Manage licensing through Remote Web Console Procedure Uninstall Command View before installing Command View AE or Remote Web Console. To uninstall Command View, follow the instructions in the HP StorageWorks Command View XP Installation Guide. Accessing new features after migration • To access Remote Web Console, launch your browser and type the SVP IP address as the URL. NOTE: See the HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the HP StorageWorks Remote Web Console User Guide for the XP1024/XP128 for additional information. • To access Command View AE, launch your browser and type the following: ://: (default is 23015)/DeviceManager/Login. For example, http://12.12.12.12:23015/DeviceManager/Login • To access the firmware license feature, click Install in the left pane of the Remote Web Console window. License Key is the default pane. • To access the user administration feature, click the Option icon in the upper right side of the Remote Web Console window. The User Entry tab is the default pane. NOTE: For information about integrating with other applications, see "Application-related migrations" on page 28. Scenario 2: Migrate to standalone Remote Web Console This migration involves transitioning array management from Command View to the standalone Remote Web Console. 22 Migration

Section	Page
Contents	3
Intended audience	7
Prerequisites	7
Related documentation	7
Document conventions and symbols	8
Table 1 Document conventions	8
HP technical support	8
HP-authorized reseller	9
Helpful Web sites	9
Migration	11
Migration overview	11
Migration planning	12
Recommended configurations	12
Option 1	12
Option 2	12
Table 2 Configuration options	12
Comparing Command View AE and Command View	13
Table 3 Comparison of Command View AE and Command View (continued)	13
HP StorageWorks XP Remote Web Console	15
Figure 1 HP StorageWorks XP Remote Web Console	15
Remote Web Console environments	16
Table 4 Remote Web Console Environments	16
New Remote Web Console features	16
Remote Web Console options	16
User Administration	16
User group permissions and mapping	17
Table 5 Command VIew user groups permissions	17
XP10000/XP12000	17
Table 6 Remote Web Console mapping to Command View users (XP10000/XP12000)	17
Table 7 Remote Web Console and Command View default users (XP10000/XP12000)	17
XP1024/XP128	18
Table 8 Remote Web Console mapping to Command View users (XP1024/XP128)	18
Table 9 Remote Web Console and Command View default users (XP1024/XP128)	18
Using Remote Web Console without updated firmware	18
Accessing Remote Web Console	19
User sessions: Logging in	19
Other comparisons between Remote Web Console and the Command View portfolio	19
Installation scenarios	20
Table 10 Installation scenarios	20
Migration procedures	22
Scenario 1: Migrate to Command View AE with Remote Web Console	22
Environment	22
Requirement(s)	22
Procedure	22
Accessing new features after migration	22
Scenario 2: Migrate to standalone Remote Web Console	22
Environment	23
Requirement(s)	23
Procedure	23
Accessing new features after migration:	23
Scenario 3: Migrate from Command View to Remote Web Console with Command View	23
Environment	24
Requirement(s)	24
Procedure	24
Accessing new features after migration	24
Negating migration changes	24
Scenario 4: Command View AE and Command View installed on the same management server	24
Environment	25
Requirements	25
Table 11 Application environments	25
Procedure	26
Confirm migration	26
Accessing new features after migration	26
Negating migration changes	26
Scenario 5: Command View AE and Command View installed on different management servers	26
Environment	26
Requirement(s)	26
Procedure	27
Confirm migration	27
CLI Client Migration	27
Procedure	27
Accessing new feature after migration	27
Confirm migration	27
Negating migration changes	27
Command View CLI migration	27
Application-related migrations	28
Supported migration applications	28
Table 12 Applications supported for integration	28
Fast Recovery Solution (FRS)	28
Standalone Hitachi software	28
OpenView Storage Area Manager (Storage Area Manager)	28
Path Connectivity-related migrations	28
Major Path Connectivity features not found in Command View AE	29
Command View AE host: additional features	29
Replacing missing features after migration to Command View AE	29
HP System Insight Manager 5.x	29
HP Storage Essentials Enterprise Edition	29
Performance Advisor (PA) and Application Policy Manager (APM)	29
Impact of this migration	30
Requirements	30
Procedure	30
Confirm migration	30
Negating migration changes	30
Third-party products	30
Miscellaneous migration information	30
Command View license entitlement migration	30
Migration of audit logs	30
CLI migration	31
CLI migration overview	31
CLI Migration Tool overview	31
CLI Migration Tool requirements	31
CLI Migration Tool limitations	31
Supported target environments	31
Supported commands	32
Translating batch files	32
Using the CLI Migration Tool	32
CLI Migration Tool procedure	32
Invoking the CLI Migration Data Collection Tool	33
Invoking the CLI Migration Tool	33
Format of input file	33
Format of property file <arrayserialNo>.properties: optional parameter	33
XP128/XP1024/XP12000/XP10000	34
XP512/XP48	34
Format of output file <inputFileName_out.bat> or <inputFileName_out.sh>	35
Working with the CLI Migration Tool files	36
Table 13 CLI Migration Tool files	36
Setting up the CLI Migration Tool	36
Execution of the CLI Migration Tool	36
Configuration files	37
CLI Migration Data Collection Tool (cmdct)	37
XP512/XP48:	37
XP128/XP1024/XP12000/XP10000:	37
Mapping Command View CLI commands to Command View AE CLI commands	38
Table 14 Manual CLI command mapping	38
Comparing component display names and component IDs	58
Port name versus port ID	58
XP12000	58
Table 15 XP12000 port names and port IDs	58
XP1024	61
Table 16 XP1024 port names and port IDs	61
XP128	62
Table 17 XP128 port names and port IDs	62
XP512	63
Table 18 XP512 port names and port IDs	63
XP48	64
Table 19 XP48 port names and port IDs	64
XP10000	64
Table 20 XP10000 port names and port IDs	64
Port fibre address values	65
Table 21 Command parameter usage	65
Table 22 Fibre Addresses/Arbitrated Loop IDs (all array types)	65
Fibre topology	66
Table 23 Port fibre topology values	66
Host mode values	66
XP48/XP512	67
Table 24 XP48/XP512 port host mode values	67
XP128/XP1024	67
Table 25 XP128/XP1024 port host mode values	67
XP12000	67
Table 26 XP12000/XP10000 port host mode values	67
Object Id representation in Command View AE CLI	68
LUN group object ID	68
WWN group object ID	68
Path object ID	68
Host group object ID	68
Logical Unit object ID	68
WWN value representation in Command View AE CLI	68
Error codes	69
CLI Migration Tool error/completion messages	69
CLI Migration Tool error codes	70
Command View CLI Data Collection Tool error/completion messages (“cmdct”):	72
Sample commands for CLI migration	73
Sample Command View CLI commands versus Command View AE CLI commands	73
EXPAND LUN	73
Command View CLI	73
XP48/XP512 arrays:	73
XP128/XP1024/XP12000/XP10000 arrays:	73
Command View AE CLI	73
XP48/XP512 arrays	73
XP128/XP1024/XP12000/XP10000 arrays	73
Sample Command View CLI versus Command View AE CLI output	73
Command View CLI	73
1) list device	73
2) list array_config	74
3) list port -l	74
4) list port -hostgrp -l	74
5) cat Test.sh	75
Command View AE CLI	75
1) Hdvmcli GetStorageArray <equivalent to list device>	75
2) Hdvmcli GetStorageArray serialnum=10227 model=XP12000 <equivalent to list array_config for 10227>	75
3) Hdvmcli GetStorageArray subtarget=Port portsubinfo=HostStorageDomain serialnum=10227 model=XP12000 <equivalent to list port -l and list port -hostgrp -l for 10227>	76
4) $ pwd	77
5) fi	77
Sample executions of the CLI Migration Tool (XP128/XP1024/XP10000/XP12000)	79
Sample execution of the CLI Migration Data Collection Tool	79
Sample execution of the CLI Migration Tool	79
Sample execution of the CLI Migration Data Collection Tool (XP48/XP512)	80
Sample execution of the CLI Migration Tool	81
FAQ	83
Does “cmt” communicate with the Command View server?	83
Does “cmt” communicate with the Command View AE server and submit translated commands?	83
Does “cmt” communicate with the array SVP?	83
Does “cmdct” communicate with the Command View server?	83
Does “cmdct” communicate with Command View AE to collect data?	83
Does “cmdct” communicate with the array SVP?	83
How do I find out if data collection from the array is required?	83
What will happen if data collection was needed before command file migration but was not done because the array was unavailable or due to some other reason?	83
Can the same property file serve as input for multiple command file migrations?	84
Can the property file that is generated by cmdct be manually repaired/edited?	84
The host screen for my host does not show some LUNs assigned for that host	84
Glossary	87
Index	89
A	89
B	89
C	89
D	89
E	89
F	89
H	89
I	89
L	90
M	90
O	90
P	90
R	90
S	90
T	90
U	90

Match case Limit results 1 per page

Migration

Migration procedures

Use the following procedures to migrate to Command View AE and Remote Web Console environments in

various arrangements. See ”

Migration planning

” on page 12 to select your preferred scenario.

Scenario 1: Migrate to Command View AE with Remote Web Console

This migration involves transitioning array management from Command View to Command View AE with

Remote Web Console. This is the preferred option for complete functionality.

Environment

This environment offers array management with Command View AE and Remote Web Console.

Requirement(s)

•

Upgrade to firmware that supports the standalone Remote Web Console for

XP12000/XP10000/XP1024/XP128

•

Install Command View AE. See the basic installation requirements in the

HP StorageWorks Command

View XP Advanced Edition Device Manager Server Installation and Configuration Guide.

•

You might require the XP512/XP48 Remote Control for access to provisioning features in Command

View XP (for example, LUN management, LUN security, LUSE, and CVS), although Command View AE

also supports those features. Use Remote Web Console with Command View to manage Auto LUN,

Cache LUN, BC/CA, and other low-usage, complex features on the XP512/XP48.

•

Purchase a Command View AE capacity license for existing arrays

•

Use Remote Web Console for optional low-level configuration management for arrays

•

Migrate existing CLI scripts (see ”

CLI migration

” on page 31)

•

Manage licensing through Remote Web Console

Procedure

Uninstall Command View before installing Command View AE or Remote Web Console. To uninstall

Command View, follow the instructions in the

HP StorageWorks Command View XP Installation Guide.

Accessing new features after migration

•

To access Remote Web Console, launch your browser and type the SVP IP address as the URL.

NOTE:

See the

HP StorageWorks Remote Web Console User Guide for the XP12000/XP10000 or the

HP StorageWorks Remote Web Console User Guide for the XP1024/XP128

for additional information.

•

To access Command View AE, launch your browser and type the following:

http or https

>://<

DNS name or IP address of management server

>:<

install

port>

(default is 23015)/

DeviceManager/Login

For example,

http://12.12.12.12:23015/DeviceManager/Login

•

To access the firmware license feature, click

Install

in the left pane of the Remote Web Console window.

License Key is the default pane.

•

To access the user administration feature, click the

Option

icon in the upper right side of the Remote

Web Console window. The

User Entry

tab is the default pane.

NOTE:

For information about integrating with other applications, see ”

Application-related migrations

” on

page 28.

Scenario 2: Migrate to standalone Remote Web Console

This migration involves transitioning array management from Command View to the standalone Remote

Web Console.