ここ最近Unity VSAを色々いじくり回してるんだけど、実は古い方のUnity VSAに問題が起きていて、プール一覧が全く表示できずに居る。実は検証の状況が変わり、ファイルシステムやLUNを削除した結果、全く使われてないプールが2つほどあるんだけど、GUI上からこれらを削除できずに居るという話で。やりたいこととしては
- 使われなくなったプールを削除したい
- 削除したぶんを活用してCIFS用のプールを増やしたい
- 増やしたCIFS用プールの領域を使ってファイルサーバとして使ってるファイルシステムの容量を拡張したい
というところ。
というわけで、仕方なくCLIを使ってこれらを実現することにしたのですよ。
- まず、UEMCLIをダウンロードする。(ダウンロードはEMCアカウントが必要ですよ)
- UEMCLIをインストールする。
- インストール中、SSLを使うかどうかについて設定確認を求められるが、SSLを使う場合、証明書の組み込み等が必要になる。バッチスクリプト等の実行で恒久的に動かす場合、Low(SSL使わない)にしたほうが良い場合もあるので、業務用途に使う場合はちょっと考えたほうがいいかも。
- コマンドプロンプトでUEMCLIを実行する
取り敢えず、使われない2つのプールを削除するために、プール一覧を出力する。
C:\WINDOWS\system32>uemcli -d 192.168.100.219 -u local/admin -p ******** /stor/config/pool show -detail
Storage system address: 192.168.100.219
Storage system port: 443
HTTPS connection1: ID = pool_1
Name = NFS_Pool
Description =
Total space = 125627793408 (117.0G)
Current allocation = 58518929408 (54.5G)
Remaining space = 67108864000 (62.5G)
Subscription = 588481527808 (548.0G)
Subscription percent = 468%
Alert threshold = 70%
Drives = 1 x 120.0G Virtual
Number of drives = 1
RAID level =
Stripe length =
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = “The component is operating normally. No action is required.”
Protection size used = 71008256 (67.7M)
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%2: ID = pool_2
Name = LABO_Pool
Description =
Total space = 104152956928 (97.0G)
Current allocation = 38923141120 (36.2G)
Remaining space = 65229815808 (60.7G)
Subscription = 534723796992 (498.0G)
Subscription percent = 513%
Alert threshold = 70%
Drives = 1 x 100.0G Virtual
Number of drives = 1
RAID level =
Stripe length =
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = “The component is operating normally. No action is required.”
Protection size used = 368640 (360.0K)
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%3: ID = pool_3
Name = CIFS_Pool
Description =
Total space = 2618051002368 (2.3T)
Current allocation = 2288949133312 (2.0T)
Remaining space = 329101869056 (306.5G)
Subscription = 11534735024128 (10.4T)
Subscription percent = 440%
Alert threshold = 70%
Drives = 1 x 50.0G Virtual; 1 x 800.0G Virtual; 1 x 800.0G Virtual; 1 x 800.0G Virtual
Number of drives = 4
RAID level =
Stripe length =
Rebalancing = no
Rebalancing progress =
Health state = OK_BUT (7)
Health details = “This storage pool has exceeded the system capacity threshold. To allocate more storage space, add additional disks to your system. (https://192.168.100.219/help/webhelp/en_US/index.htm?#unity_c_storage_pool_at_or_near_full_capacity.html)”
Protection size used = 2210963456 (2.0G)
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%4: ID = pool_4
Name = Replica_Pool
Description =
Total space = 267361714176 (249.0G)
Current allocation = 0
Remaining space = 267361714176 (249.0G)
Subscription = 0
Subscription percent = 0%
Alert threshold = 70%
Drives = 1 x 250.0G Virtual
Number of drives = 1
RAID level =
Stripe length =
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = “The component is operating normally. No action is required.”
Protection size used = 0
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%5: ID = pool_7
Name = ESXi_Pool
Description =
Total space = 321048805376 (299.0G)
Current allocation = 0
Remaining space = 321048805376 (299.0G)
Subscription = 0
Subscription percent = 0%
Alert threshold = 70%
Drives = 1 x 300.0G Virtual
Number of drives = 1
RAID level =
Stripe length =
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = “The component is operating normally. No action is required.”
Protection size used = 0
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%6: ID = pool_8
Name = VDP_Pool
Description =
Total space = 814970044416 (759.0G)
Current allocation = 0
Remaining space = 814970044416 (759.0G)
Subscription = 0
Subscription percent = 0%
Alert threshold = 70%
Drives = 1 x 760.0G Virtual
Number of drives = 1
RAID level =
Stripe length =
Rebalancing = no
Rebalancing progress =
Health state = OK (5)
Health details = “The component is operating normally. No action is required.”
Protection size used = 0
Auto-delete state = Idle
Auto-delete paused = no
Auto-delete pool full threshold enabled = yes
Auto-delete pool full high water mark = 95%
Auto-delete pool full low water mark = 85%
Auto-delete snapshot space used threshold enabled = no
Auto-delete snapshot space used high water mark = 25%
Auto-delete snapshot space used low water mark = 20%
あ、いらないプールは実際には3つほどあったのか。取り敢えずこれらを削除することにする。
C:\WINDOWS\system32>uemcli -d 192.168.100.219 -u local/admin -p ******** /stor/config/pool -id pool_8 delete
Storage system address: 192.168.100.219
Storage system port: 443
HTTPS connectionOperation completed successfully.
C:\WINDOWS\system32>uemcli -d 192.168.100.219 -u local/admin -p ******** /stor/config/pool -id pool_7 delete
Storage system address: 192.168.100.219
Storage system port: 443
HTTPS connectionOperation completed successfully.
C:\WINDOWS\system32>uemcli -d 192.168.100.219 -u local/admin -p ******** /stor/config/pool -id pool_4 delete
Storage system address: 192.168.100.219
Storage system port: 443
HTTPS connectionOperation completed successfully.
これでプールを削除できた。どのプールにもバインドされてないディスクはVMware上の「設定の編集」で仮想ディスクを削除することにより、ディスクを外すことが可能となる。
ディスク外した後、必要容量を持ったディスクを再度作成し、装填する。その後、該当ディスクのTier設定を行い、プールに組み込めるようにする。搭載した仮想ディスクは、Tier設定をしないとプールに組み込めないので注意が必要である。
C:\WINDOWS\system32>uemcli -d 192.168.100.219 -u local/admin -p ******** /env/disk -id vdisk_14 set -tier performance
Storage system address: 192.168.100.219
Storage system port: 443
HTTPS connectionID = vdisk_14
Operation completed successfully.
Tier設定後、既存プールにディスクを組み込んで、プール容量を拡張する。
C:\WINDOWS\system32>uemcli -d 192.168.100.219 -u local/admin -p ******** /stor/config/pool -id pool_3 extend -disk vdisk_14
Storage system address: 192.168.100.219
Storage system port: 443
HTTPS connectionOperation completed successfully.
容量は以下のようになりまして。
拡張前:Total space = 2618051002368 (2.3T)
拡張後:Total space = 2938562936832 (2.6T)
300GBほど容量拡張ができました。あとはGUIでファイルシステムの容量を300GB広げればOK。というわけで、無事に容量追加できました。よかったよかった。
なお、ファイルシステムは筐体間レプリケーションをしてるわけですが、相手方に対するファイルシステムの拡張は、レプリケーションをSyncさせた時点で自動的に相手方に対して反映されます。このあたりはVNXと同様の動きをしてくれるようですな。
No responses yet