[Server] Dell PowerEdge R740 message “Lifecycle controller is in Recovery Mode"

Solution:

step01. SSH iDRAC IP ,
(註) ID / Password : root / 目前不若之前用calvin 已改採用像HP iLO面板前都有出專屬預設密碼。

step02.
racadm set LifecycleController.LCAttributes.LifecycleControllerState 0 // Disabled
racadm set LifecycleController.LCAttributes.LifecycleControllerState 1 // Enabled
(註) first disabled then enabled it LCC

Finish.

[Storage] IBM DS-series use console connect

一般 IBM DS-series (LSI) storage 後面console port 大多是原廠才能知道如何連接,原廠手冊也不會有記載連接方式。

找尋一些文章用本篇來記錄一下。。

它的console類似早期鍵盤/滑鼠PS2母頭對應著RS-232

step01. use putty

step02. putty setup
baud rate [ 2400 ~ 9600 ] 、[19200]、[38200]、[57600]
data bit :8
Stop bit : 1
Flow control: XON/XOFF

step03.按下 Ctrl + Break 觸發它一下
出現了 “Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate
Do NOT press S – INSTEAD Press ESC
=> you’ll be asked username & password (shellUsr etc)

ESC。輸入連接密碼,default值 > infinitiy2llojp ; Dell 同款DS 密碼為 DF4m/2>

PS:若知道IP也可以試著 telnet DS A/B IP-address // 適用 IBM DS3524 / DS3512 機種

-> loadDebug
value = 1 = 0x1
-> setSAPassword_MT “"
ReturnCode = 0x1
value = 1 = 0x1
-> unld “Debug"
value = 0 = 0x0
-> exit


step04.
VxWorks login: shellUsr
Password: wy3oo&w4

** 常用指令集 **
-> netCfgShow // 查看控制器 A/B IP address
-> netCfgSet // 設定控制器 A/B IP address

** Factory default **
-> sysWipe
-> sysReboot

** Clear password **
-> loadDebug
-> setSAPassword_MT “"
-> unld “ffs:Debug"

** collect log **
-> excLogShow
-> hwLogShow

[若有 Lock down現象]
controller both type as below command
-> lemClearLockdown // 下完沒用可再試 sysReboot 重啟檢查
-> clearHardwareLockdown 
-> psvClearSodRebootLoopCounter
-> eelClearParityErrorControllerFailure
-> eelClearProcessorMemoryError 

拔出controller-A ,在 controller-B as below command,then insert controller-A
-> loadDebug 
-> cmgrSetAltToFailed 
-> cmgrSetAltToOptimal

(註)
default IP
controller-A 192.168.128.101
controller-B 192.168.128.102


Reference :
1. Martin Chang的部落格 – IBM DS 控制器串口命令文档 dell也一样
2. TechDocs – How to Connect to the DS4000 system using Hyperterm

[VMware] Backup / Restore vCenter Server 6.x vPostgres database

[ Windows ]

~備份(Backup)~

step01.
cd %VMWARE_CIS_HOME%\bin

cd C:\"Program Files"\VMware\"vCenter Server"\bin

step02. 需先停止 vmware-vpxdvmware-vdcs 服務
~6.7 and 6.5 (Windows)~
service-control –stop vpxd
service-control –stop content-library

~ 6.0 (Windows)~
service-control –stop vpxd
service-control –stop vdcs

step03.
下載KB Attachments , 載點
備份批次檔 > backup_win.py
還原批次檔 > restore_win.py

step04.
建立C槽底下一個目錄 tmp
C:\tmp將批次檔放置這兒

step05.
(Caution) 在執行批次檔請勿任意停止將會影響 PostgreSQL Database不一致。
找出  %VMWARE_CFG_DIR%\vmware-vpx\ 底下 vcdb.properties 記錄下 DB帳號 vc 的密碼

step06. 備份 (Backup)
cd %VMWARE_CIS_HOME%\Python\
python.exe c:\tmp\backup_win.py -p “oMfcT=7C?5L&Wh@2″ -f c:\tmp\backup_VCDB.bak
** 成功就會如下訊息**
Backup completed successfully.

step07. 最後別忘了啟動這二支 vmware-vpxdvmware-vdcs 服務
~6.7 and 6.5 (Windows)~
service-control –start vpxd
service-control –start content-library

~ 6.0 (Windows)~
service-control –start vpxd
service-control –start vdcs


~還原(Restore)~

step01.
請以 administrator 權限身份登入

step02.需先停止 vmware-vpxdvmware-vdcs 服務
~6.7 and 6.5 (Windows)~
service-control –stop vpxd
service-control –stop content-library

~ 6.0 (Windows)~
service-control –stop vpxd
service-control –stop vdcs

step03.
(Caution) 在執行批次檔請勿任意停止將會影響 PostgreSQL Database不一致。
找出  %VMWARE_CFG_DIR%\vmware-vpx\ 底下 vcdb.properties 記錄下 DB帳號 vc 的密碼

step04. 還原 (Restore)
cd %VMWARE_CIS_HOME%\Python\
python.exe c:\tmp\restore_win.py -p “oMfcT=7C?5L&Wh@2″ -f c:\tmp\backup_VCDB.bak
** 成功就會如下訊息**
Backup completed successfully.

step05. 最後別忘了啟動這二支 vmware-vpxdvmware-vdcs 服務
~6.7 and 6.5 (Windows)~
service-control –start vpxd
service-control –start content-library

~ 6.0 (Windows)~
service-control –start vpxd
service-control –start vdcs





[ Linux (Appliance) ]
與 Windows 差異是多了change mode
chmod 700 /tmp/backup_lin.py
chmod 700 /tmp/restore_lin.py


Reference :
1. Back up and restore vCenter Server Appliance/vCenter Server 6.x vPostgres database (2091961)

[VMware] vRealize Operations Manager 6.3 ~ 7.5 Enable SSH service

vRealize Operations Manager 6.x 基本上OS底層是 SUSE Linux Enterprise 11。所以尚未像 vCenter Appliance 是以 VMware Photon OS ;所以不是用VMware式的按下 ALT + F2 進入啟用SSH。

step01. open vROM console

step02. ALT + F1

step03. 預設帳號 ‘ root ‘ ,密碼 ‘空白 (blank)’ 按下後立即輸設定新密碼。

step04. # service sshd start

step05. # chkconfig sshd on

step06. use like ‘putty’ testing

Reference :

VMware KB – Enabling SSH access in vRealize Operations Manager 6.x and later (210051

vGyan.in : vRealize Part 7 – Enable SSH on vROPS

[HPE] ProLiant DL380p Gen8 iLO4 GUI show “Embedded Flash/SD-CARD: Failed restart.."

客戶反應iLO4反應有點怪怪,雖作過拔除電源斷電一分鐘但狀況依舊。且感覺它都時常會有 hang state ,用 ping iLO4卻是有回應不掉封包。在 iLO4 登入畫面會常顯示 “iLO Self-Test report a problem with :Embedded Flash/SD-CARD: Failed restart..view details on Diagnostics page. " 及 “Connection with iLO cannot be established. If you recently made changes to the network configurations,you may need to refresh this page to re-negotiate an SSL connection."

HPE原廠建議solution as below list

step01.
upgrade iLO4 to 2.44 or newer (因 2.44才支援能格式化 SD-Flash media {NAND} )

step02.
NAND Format Methods

* From the iLO 4 GUI (requires iLO 4 firmware version 2.61 or newer)
* From the Onboard Administrator (for servers in HPE BladeSystem c3000/c7000 Enclosures only)
* From Windows OS (using the HPQLOCFG.exe utility)
* From Windows PowerShell (using HPE iLO cmdlets for PowerShell)
* From Linux or VMware (using the hponcfg utility)

而我選擇用下載 HPQLOCFG.exe utility from “Software – Lights-Out Management v5.0.0" 需安裝在本機電腦上唷。

step03. 編輯腳本 force_format.xml (可隨意命名只要在用 hpqlocfg.exe 指定對的.xml名稱即可)

<RIBCL VERSION="2.0″>
<LOGIN USER_LOGIN="iLO4最高權限帳號" PASSWORD="iLO密碼">
<RIB_INFO MODE="write">
<FORCE_FORMAT VALUE="all" />
</RIB_INFO>
</LOGIN>
</RIBCL>

step04.
在格代化前 (1.升級iLO4 v2.53以上 , 2.重開iLO ,3.接上電源不開機狀態下作格式化)

“c:\Program Files (x86)\Hewlett-Packard\HP Lights-Out Configuration Utility\HPQLOCFG.exe" -f force_format.xml -s iLO的IP -u iLO最高權限 -p iLO密碼

**若成功在命令提示列會看到 “Forcing a format of the partition after the iLO reset“字樣,且在iLO4 event log “Embedded Flash/SD-CARD: One or more storage devices have been formatted."
最後有格式化成功查看 iLO4 > Information > System Information > Firmware > Intelligent Provisioning (版本會變成 N/A 狀態)

step05. 下載 " HP Intelligent Provisioning Recovery Media " 或"多版本 HPE IPRM
(PS: 對應版本如下
Gen8 servers supports Intelligent Provisioning 1.x
Gen9 servers supports Intelligent Provisioning 2.x
Gen10 servers supports Intelligent Provisioning 3.x
)

step06. 開機按下 F11 Boot menu

step07.進入後選第一個 “Intelligent Provisioning Recovery Media"
會陸續看到三步驟
> Verifying system settings This may take up to 30 seconds
> Running flash process Please wait until process is complete.
> Update Complate – you must reboot to apply your changes.

step08. 再把iLO4 restart ( Information > Diagnostics > reset )

step09. 再查看 iLO health 已不是 degrade ,其二. Intelligent Provisioning firmware有版本出現不在是 N/A state .

Done.

(若以上幫不了你則請更換主機板吧…..God bless you …..)

Reference:
1. HPE ProLiant Gen8 Servers – How to Reinstall or Upgrade Intelligent Provisioning

2. HPE Document ID: c04996097 ,v10 – Advisory: (Revision) HPE Integrated Lights-Out 4 (iLO 4) – HPE Active Health System (AHS) Logs and HPE OneView Profiles May Be Unavailable Causing iLO Self-Test Error 8192, Embedded Media Manager and Other Errors

3. HPE Document ID: a00048622en_us ,v5 – Advisory: (Revision) HPE Integrated Lights-Out 4 (iLO 4) – How to Format the NAND Used to Store AHS logs, OneView Profiles, and Intelligent Provisioning

4. HPE Document ID: a00047494en_us ,v1 – Notice: HPE Integrated Lights Out (iLO) 4 – RESTful Command to Allow an Auxiliary Power-Cycle Is Available in Firmware Version 2.55 (and Later)

5. 狸貓先生愛廢話講堂 – HPE Server 動手做 – ProLiant Gen9 的 Embedded Flash 故障造成 Intelligent Provisioning 無法啟動問題

[Windows]狂Ping指令,類Cisco Fast Ping 效果

下載PSTool工具 https://bit.ly/2Kys8

指令 > psping.exe -t -i 0 192.168.1.1

psping 64.exe -t -i 0 192.168.1.1
(註) 參數一定要如上不可隨便變動。否則僅是預設 ping 四次唷!


指令解釋:

– i > Usage for ICMP ping.
-t >Usage for TCP ping.
– l > Usage for latency test.
– b > Usage for bandwidth test.
-nobanner > Do not display the startup banner and copyright message.

[VMware] ESXi 6.5.x migrate VM but available hosts missing one host ?

因客戶機器有些異動後幫他上線後,客戶要將原本上面機器搬回該機,卻發現可用主機居然莫名看不到?換成vSphere Web Client (Flash)也是如此。

查了KB看來僅會發生在 ESXi 6.5系列。

Workaround:

step01. vSphere Web client 在要搬移機器 > Launch Remote console,立即關閉該VM console.

step02. 再作一次搬移動作.

Reference:
1.vMotion not showing all available hosts in the Cluster in vSphere 6.5 (57230)
2. Troubleshooting the migration compatibility error: The VMotion interface is not configured (or is misconfigured) on the destination host (1003827)
3. Understanding and troubleshooting vMotion (1003734)

[Nutanix] WinSCP connect CVM use SFTP protocol

自 AOS 5.5 開始預設 SFTP Port 2222 是關閉。

step01. @CVM$ allssh modify_firewall -f -o open -i eth0 -p 2222 -a // 開啟防火牆

step02. use WinSCP > SFTP > IP ,Port 2222 // 帳/密 admin / prism-password

(補充)
* Linux / Mac *
$ sftp -P 2222 admin@cluster-vip:/container-name 連線
$ put test.vmdk

[Nutanix] AHV decrease CVM memory

有時在用Nutanix CE版本資源總是很缺乏,一個節點用大家常用 16GB (16384 MB) 時,CVM就佔用 12GB 將近就75%記憶體資源都它在用..Orz

因此,當你這環境還想在每一台都建一台VM,那就只有新增AHV memory 或降低 CVM memory.我是沒什麼資源只能選後者。

Resolution:

step01. @cvm$ cluster stop

step02. @cvm$ sudo shutdown -P now
Or
@ahv# virsh shutdown cvm-name

step03. @ahv# virsh list –all | grep -i cvm

step04. @ahv# virsh dumpxml {cvm-name} | egrep -i “cpu|memory" // 10G ,10485760 KiB

step05. @ahv# virsh setmaxmem {cvm-name} –config –size 10GiB
@avh# virsh setmem {cvm-name} –config –size 10GiB

step06. @ahv# virsh dumpxml {cvm-name} | egrep -i “cpu|memory" // 再確認一次是否更改 10G OK.

step07. @ahv# virsh start {cvm-name}

step08. @cvm$ cluster status

step09. @cvm$ cluster start

Reference:
1. AHV 5.0 – Changing CVM Memory Configuration (AHV)