| Asset ID: |
1-71-1437473.1 |
| Update Date: | 2015-05-26 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1437473.1
:
Pillar Axiom: Lun Migration Guidelines
| Related Items |
- Pillar Axiom 600 Storage System
- Pillar Axiom 500 Storage System
- Pillar Axiom 300 Storage System
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
|
In this Document
Applies to:
Pillar Axiom 500 Storage System - Version Not Applicable and later Pillar Axiom 600 Storage System - Version All Versions and later Pillar Axiom 300 Storage System - Version Not Applicable and later Information in this document applies to any platform.
Goal
Guidelines for Lun Migration
Solution
In order to do LUN Quality of Service migrations, please adhere to the following:
- Do not attempt more than ONE migration at a time as this will reduce performance during the migration process.
- Once the migration is done (the task MonitorBackgroundLUNMigrationTask is complete and the Axiom logged the following event "Modify LUN by administrator succeeded", check the System Capacity to make sure it is "ZERO" before starting the next migration.
==> For R4, run pdscli command to check for the UnpreparedSystemCapacity
example:
pdscli sub -u administrator -H <ip address> GetStorageConfig
==> For R5, run pcli command to check for the PhysicalUnavailableCapacity
example:
- pcli sub -H <ip address> -u administrator GetStorageDetails
or axiomcli:
- axiomcli login -u administrator -p <administrator password> -axiom <ip address>
axiomcli storage_domain -list -details
==> R4 command
C:\Alice\CLI folder\krusty_040615>pdscli sub -u administrator -p XXXXX -H <IP address> GetStorageConfig
Header
ProtocolVersion: 0.1
SessionKey: 7c8b76f43e2a319c7097c00d11ebe2fb
Time: 2015-01-29T12:58:41-08:00
ClientData: pdscli
RequestStatus: Succeeded
Error List
GetStorageConfigResponse
TotalSystemCapacity: 10870
UsedSystemCapacity: 486
FreeSystemCapacity: 10384
UnpreparedSystemCapacity: 0
CommittedSystemCapacity: 1366
StorageClassUsage[1]
StorageClass: MultiLevelCellSolidStateDrives
TotalSystemCapacity: 0
UsedSystemCapacity: 0
FreeSystemCapacity: 0
UnpreparedSystemCapacity: 0
PotentialUsageList
PotentialUsage[1]
Redundancy: Standard
LargestVolumeCapacity: 0
PotentialUsage[2]
Redundancy: Double
LargestVolumeCapacity: 0
StorageClassUsage[2]
StorageClass: SataHardDiskDrives
TotalSystemCapacity: 10870
UsedSystemCapacity: 486
FreeSystemCapacity: 10384
UnpreparedSystemCapacity: 0 => this is unprepared capacity for the SATA class
PotentialUsageList
PotentialUsage[1]
Redundancy: Standard
LargestVolumeCapacity: 8653
PotentialUsage[2]
Redundancy: Double
LargestVolumeCapacity: 4326
StorageClassUsage[3]
StorageClass: FibreChannelHardDiskDrives
TotalSystemCapacity: 0
UsedSystemCapacity: 0
FreeSystemCapacity: 0
UnpreparedSystemCapacity: 0 => this is unprepared capacity for the FC class
PotentialUsageList
PotentialUsage[1]
Redundancy: Standard
LargestVolumeCapacity: 0
PotentialUsage[2]
Redundancy: Double
LargestVolumeCapacity: 0
StorageClassUsage[4]
StorageClass: SingleLevelCellSolidStateDrives
TotalSystemCapacity: 0
UsedSystemCapacity: 0
FreeSystemCapacity: 0
UnpreparedSystemCapacity: 0
PotentialUsageList
PotentialUsage[1]
Redundancy: Standard
LargestVolumeCapacity: 0
PotentialUsage[2]
Redundancy: Double
LargestVolumeCapacity: 0
===> R5 command:
C:\Alice\CLI folder\frankie_us_oracle_com>pcli sub -H frankie.us.oracle.com -u administrator GetStorageDetails
Password:
Message
Response
CorrelationID: 1432310902
BeginStreamResponse
TaskGuid: 4130303133373842A13F14B1717D38ED
TaskFqn: /GetStorageDetails/138450/administrator
Message
Response
CorrelationID: 1432310902
GetStorageDetailsResponse
StorageDetailsInformation
SystemCapacitySummary
PhysicalFreeCapacity: 8507
PhysicalFreeCapacityInBytes: 9135036825600
PhysicalUsedCapacity: 132
PhysicalUsedCapacityInBytes: 142694940672
PhysicalTotalCapacity: 8643
PhysicalTotalCapacityInBytes: 9280369459200
PhysicalAllocatedCapacity: 135
PhysicalAllocatedCapacityInBytes: 145332633600
PhysicalUnavailableCapacity: 0 ==> this is unprepared capacity for the system
PhysicalUnavailableCapacityInBytes: 0
PhysicalMaximumCommittedCapacity: 964
PhysicalMaximumCommittedCapacityInBytes: 1035825315840
StorageClassDetails[0]
StorageClass: FC_ROTATING_MEDIA
CapacitySummary
PhysicalFreeCapacity: 3070
PhysicalFreeCapacityInBytes: 3296628572160
PhysicalUsedCapacity: 0
PhysicalUsedCapacityInBytes: 0
PhysicalTotalCapacity: 3070
PhysicalTotalCapacityInBytes: 3296628572160
PhysicalAllocatedCapacity: 0
PhysicalAllocatedCapacityInBytes: 0
PhysicalUnavailableCapacity: 0 ==> this is unprepared capacity for the FC class
PhysicalUnavailableCapacityInBytes: 0
PhysicalMaximumCommittedCapacity: 0
PhysicalMaximumCommittedCapacityInBytes: 0
StorageClassDetails[1]
StorageClass: SATA_ROTATING_MEDIA
CapacitySummary
PhysicalFreeCapacity: 5437
PhysicalFreeCapacityInBytes: 5838408253440
PhysicalUsedCapacity: 132
PhysicalUsedCapacityInBytes: 142694940672
PhysicalTotalCapacity: 5572
PhysicalTotalCapacityInBytes: 5983740887040
PhysicalAllocatedCapacity: 135
PhysicalAllocatedCapacityInBytes: 145332633600
PhysicalUnavailableCapacity: 0 ==> this is unprepared capacity for SATA class
PhysicalUnavailableCapacityInBytes: 0
PhysicalMaximumCommittedCapacity: 964
PhysicalMaximumCommittedCapacityInBytes: 1035825315840
StorageDomainDetails[0]
StorageDomainIdentity
Id: 4130303133373842A214000000000000
Fqn: /default
StorageClassDetails[0]
StorageClass: SATA_ROTATING_MEDIA
CapacitySummary
PhysicalFreeCapacity: 5437
PhysicalFreeCapacityInBytes: 5838408253440
PhysicalUsedCapacity: 132
PhysicalUsedCapacityInBytes: 142694940672
PhysicalTotalCapacity: 5572
PhysicalTotalCapacityInBytes: 5983740887040
PhysicalAllocatedCapacity: 135
PhysicalAllocatedCapacityInBytes: 145332633600
PhysicalUnavailableCapacity: 0
PhysicalUnavailableCapacityInBytes: 0
PhysicalMaximumCommittedCapacity: 964
PhysicalMaximumCommittedCapacityInBytes: 1035825315840
StorageDomainDetails[1]
StorageDomainIdentity
Id: 4130303133373842A1140343C7DC9383
Fqn: /Test_domain
StorageClassDetails[0]
StorageClass: FC_ROTATING_MEDIA
CapacitySummary
PhysicalFreeCapacity: 3070
PhysicalFreeCapacityInBytes: 3296628572160
PhysicalUsedCapacity: 0
PhysicalUsedCapacityInBytes: 0
PhysicalTotalCapacity: 3070
PhysicalTotalCapacityInBytes: 3296628572160
PhysicalAllocatedCapacity: 0
PhysicalAllocatedCapacityInBytes: 0
PhysicalUnavailableCapacity: 0
PhysicalUnavailableCapacityInBytes: 0
PhysicalMaximumCommittedCapacity: 0
PhysicalMaximumCommittedCapacityInBytes: 0
Message
Response
CorrelationID: 1432310902
EndStreamResponse
TaskGuid: 4130303133373842A13F14B1717D38ED
TaskFqn: /GetStorageDetails/138450/administrator
- Run command storage_allocation to see the new LUN distribution across the bricks.
Use the axiomcli script to view what Bricks each LUN is allocated on. Log into the Axiom GUI as administrator and click "Support" tab -> under "Utilities Download" click "Command Line Interface" select "Download CLI for <host> ".
Use either of the storage_allocation commands below:
Below is an example of running axiomcli in R4
C:\Alice\CLI folder\krusty_040615>axiomcli.exe axiom_login -u administrator -p <password> <IP address>
Login Succeeded
*****************************************************
** **
** This is a company computer system with access **
** restricted to those with proper authorization. **
** Authorized parties are restricted to those **
** functions which have been assigned to perform **
** work related duties. Any unauthorized access **
** will be investigated and prosecuted to the **
** full extent of the law. If you are not an **
** authorized user, disconnect now. **
** **
*****************************************************
C:\Alice\CLI folder\krusty_040615>axiomcli storage_allocation -list -details -extents
The Axiom is now collecting system configuration information.
This may take several minutes to complete.
Name: test
Type : Filesystem
Priority : Archive
Redundancy : 1
AccessBias : Sequential
I/OBias : Read
NumberExtents : 4
AllocatedOnBricks
FQN: /Brick001, CU : 1
FQN: /Brick002, CU : 1
FQN: /Brick004, CU : 1
FQN: /Brick005, CU : 1
Extents
Brick CU Extent Start End Capacity
StripeChild StripeChildOffset
/Brick001 1 797 0xb29c380000 0xb2ddd80000 0x41a000
00 2 0x0
/Brick002 1 796 0xb2ee400000 0xb32fe00000 0x41a000
00 1 0x0
/Brick004 1 798 0xb29c380000 0xb2ddd80000 0x41a000
00 3 0x0
/Brick005 1 795 0x11b43a00000 0x11b85400000 0x41a000
00 0 0x0
Name: skip_test
Type : Filesystem
Priority : Archive
Redundancy : 1
AccessBias : Sequential
I/OBias : Read
NumberExtents : 4
AllocatedOnBricks
FQN: /Brick001, CU : 1
FQN: /Brick003, CU : 1
FQN: /Brick004, CU : 1
FQN: /Brick005, CU : 1
Extents
Brick CU Extent Start End Capacity
StripeChild StripeChildOffset
/Brick001 1 600 0xb936100000 0xb977b00000 0x41a000
00 2 0x0
/Brick003 1 598 0x12271200000 0x122b2c00000 0x41a000
00 0 0x0
/Brick004 1 601 0xb936100000 0xb977b00000 0x41a000
00 3 0x0
/Brick005 1 599 0x12271200000 0x122b2c00000 0x41a000
00 1 0x0
-
-----------------------------------------------------------------------------------------------------------------------------------------
Examples of running axiomcli in R5:
C:\Alice\CLI folder\esaxiom_050417>axiomcli login -u administrator -p pillar <ip address> The current userid on this client has not yet logged out from 10.133.112.85. Co ntinuing with this login request will logout the existing session, and all subse quent commands from this userid will use the new login information. Proceed with login (y/N)? y Login Successful C:\Alice\CLI folder\esaxiom_050417>axiomcli storage_allocation -list -lun -csv storage_allocation_lun.csv -o text Command Succeeded Opem the storage_allocation_lun.csv and you will see the following information.
| Name |
Type |
Priority |
Redundancy |
AccessBias |
IOBias |
SourceName |
SourceId |
SourceVlunHandle |
SourceVlunGUID |
BrickFriendlyName |
BrickWWN |
BrickLUN |
|
| Test1 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-001 |
0x200c000b083a542f |
2 |
|
| Test1 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-001 |
0x200c000b083a542f |
3 |
|
| Test1 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-002 |
0x200c000b083a54b6 |
2 |
|
| Test1 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-002 |
0x200c000b083a54b6 |
3 |
|
| Test2 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-001 |
0x200c000b083a542f |
2 |
|
| Test2 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-001 |
0x200c000b083a542f |
3 |
|
| Test2 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-002 |
0x200c000b083a54b6 |
2 |
|
| Test2 |
SAN LUN |
Archive |
Standard |
Mixed |
Mixed |
|
|
|
|
BRICK-002 |
0x200c000b083a54b6 |
3 |
|
Both commands will list all the LUNs and which Bricks they are allocated on. The extents will be listed as they are laid out on the bricks.
Action Plan:
-------------
- Identify the LUN(s) that you want to migrate.
- Once identified, open the LUN properties and click the Quality of Service tab to view the current settings.
- Change Priority vs. other Volumes of the LUN from its current setting to the desired band. (For example, changing from 'archive' to 'medium')
NOTE: Prior to selecting OK to execute this task, ensure that the 'Temporary' box is NOT checked follwed by OK to execute the migration process.
- The LUN status will change to 'Configuring' for about 30 seconds and then a MonitorBackgroundLUN MigrationTask will appear in the background. This is the period of time in which performance will be affected.
- Once the first migration is complete, run the scripts GetStorageConfig (R4) and GetStorageDetails (R5) and Storage_allocation (in step2 and step3). Ensure the output of UnpreparedSystemCapacity is zero and make sure that the LUN is in the new band and on different bricks.
- Once confirmed that the LUN is in the right band, change the QoS back to the LUN's original setting. To keep the LUN in a different band, make the appropriate modifications. If not, make sure the 'Temporary' box is not checked and Click OK.
- Wait until the migration back to the original setting is complete, ensure the output of UnpreparedSystemCapacity is zero and check storage_allocation for the new distribution.
- Once complete, begin processing the next LUN and follow steps: 2-8 until all LUNs have completed migration.
Attachments
This solution has no attachment
|
