정보와 지식의 올바른 공유 - http://infoages.com

HPE Oneview - Lifecycle (Release and End of Support(EOS))

HPE OneView 5.4 and 6.0 are milestone releases and must be updated to before updating to a subsequent release. A milestone release is a release with enhanced update architecture which will deliver faster and more reliable updates. Milestone releases are expected two to three releases apart.

** EOS = End of Support (EOS) defines the last day where a patch may be available for a release.

NOTE. For a version that is in the "End of Support" phase, HPE Pointnext will continue to take calls from the users with active support contracts, but there will be no new fixes provided for this release.

참조문서:

Notice: HPE OneView - Product Lifecycle and Additional Resources
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00117617en_us

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c05148671

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00111768en_us

a00114638en_us: End-of-Support (EOS) for HPE OneView 5.0
a00078123en_us: End-of-Support (EOS) for HPE Synergy Composer (HPE OneView) / HPE Synergy Image Streamer 4.00 

연관문서:
HPE OneView Global Dashboard - Product Lifecycle and Additional Resources
https://support.hpe.com/hpesc/public/docDisplay?docId=a00029022en_us&docLocale=en_US

HPE OneView Partner Integration Lifecycle
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00054225en_us

Test System:

DL380 Gen9+VMware ESXi 6.5 u2

Test device - 331x NIC.

HPE Broadcom NX1 Online Firmware Upgrade Utility for VMware
1.28.6 (19 Apr 2021)
https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_648f0b90d7c2438b82851940e2#tab2

[root@DL380G9P5U25:/tmp/CP045013] ls
CP045013.vmexe          CP045013.vmfile         CP045013_BUILD_13.data  payload.json
CP045013.vmexe64        CP045013.xml            CP045013_VMw.zip

[root@DL380G9P5U25:/tmp/CP045013] pwd
/tmp/CP045013
[root@DL380G9P5U25:/tmp/CP045013] esxcli software vib install -d /tmp/CP045013/CP045013_VMw.zip
Installation Result
   Message: Operation finished successfully.
   Reboot Required: false
   VIBs Installed: HPE_bootbank_CP045013_1.28.6.13-7.0.0.15843807
   VIBs Removed:
   VIBs Skipped:
[root@DL380G9P5U25:/tmp/CP045013]

> 압축 해제 (아직 미설치...)

[root@DL380G9P5U25:/opt/Smart_Component/CP045013] pwd
/opt/Smart_Component/CP045013

[root@DL380G9P5U25:/opt/Smart_Component/CP045013] ls
CP045013.vmcfg          ESXi_6.5                Execute_Component       hpsetup                 nic_fw
CP045013.xml            ESXi_6.7                determine_which_OS.sh   libbrcm_bmapi.so.6      release.txt
CP045013_BUILD_13.data  ESXi_7.0                flash.so                libbrcm_hpfwupg.so

[root@DL380G9P5U25:/opt/Smart_Component/CP045013] ./hpsetup

===============================================================
HPE Broadcom NX1 Online Firmware Upgrade Utility for VMware
Version: 1.28.6

Performing Discovery operation......Please be patient..

Selecting HPE Ethernet 1Gb 4-port 331i Adapter MAC: 3cA82A21436C
*** WARNING *** - Installed nvm is the same version as selected nvm.
Update nvm 20.18.31 to 20.18.31 y/n/q (n):n
> 요 단계가 실제 설치 단계

다른 방법으로는, CP045013.vmexe 파일에 실행 권한을 주고, 설치.

[root@DL380G9P5U25:/tmp/CP045013] chmod +x CP045013.vmexe

[root@DL380G9P5U25:/tmp/CP045013] ls
CP045013.vmexe          CP045013.vmfile         CP045013_BUILD_13.data  payload.json
CP045013.vmexe64        CP045013.xml            CP045013_VMw.zip

[root@DL380G9P5U25:/tmp/CP045013] ./CP045013.vmexe
OS Version found  [6.5.0]

===============================================================
HPE Broadcom NX1 Online Firmware Upgrade Utility for VMware
Version: 1.28.6

Performing Discovery operation......Please be patient..

Selecting HPE Ethernet 1Gb 4-port 331i Adapter MAC: 3cA82A21436C
Update nvm 20.16.31 to 20.18.31 y/n/q (y):y


Firmware update in progress......It will take a while....Please be patient..

Please reboot for the firmware flash to complete.

[root@DL380G9P5U25:/tmp/CP045013]

증상: IML: Smart Storage Battery pre-failure (Battery 1)

Q. SSB의 pre-failure를 감지 및 표시 할 수 있는 iLO의 버전은?
A. iLO 4: v2.55 / iLO 5: Any version

Q. SSB의 pre-failure 발생 시, backup power의 상태는 어떠한지?
A. 정상 동작 상태
   SSB pre-failure는 실시간 감시에 따른 검출 기능으로, 로그 발생 시점 기준으로 정상 동작 상태이나,

   SSB 상태가 장애로 분류(마크)되는 이전 상태로 교체가 필요한 상태
   HPE는 증상 발생 후 한 주 이내 교체를 권장.

Note. pre-failure는 SSB 내부에 2개 배터리 셀이 존재하며, 각 셀의 충전 레벨이 서로 달라지는 상태를 감지함


참고문서:
Notice: (Revision) HPE Smart Storage Battery – Battery Pre-Failure Capability Available With HPE Integrated Lights Out (iLO) 4 Firmware Version 2.55
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00026525en_us

Notice: (Revision) HPE Smart Storage Batteries - How To Determine If a 12W And 96W HPE Smart Storage Battery Needs To Be Replaced
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00069090en_us

RESTful API를 사용하는 경우,
GET https://<%_iLO_IP_Address%>/redfish/v1/chassis/1/power
e.g.) GET https://192.168.0.10/redfish/v1/chassis/1/power

Note. RESTful client의 credential 설정 필요.

RESTful Interface Tool을 사용하는 경우,
RESTful Interface Tool
https://buy.hpe.com/kr/ko/software/infrastructure-management-software/system-server-management-software/hpe-system-server-software-management-software/restful-interface-tool/p/7630408

1. ilorest를 통해 iLO 접속
   ilorest login <%_iLO_IP_Address%> --user <%Administrative_Account%> --password <%Password%> --selector=Power.
2. 정보 열람
   ilorest list
      or
   ilorest -d serverinfo --power

iLO의 Web UI를 통해서 변경하는 것도 가능하지만, 수량이 많거나 하는 경우, 작업이 번거로울 수 있음에...

iLO의 SNTP의 Timezone을 변경 및 저장하지 않고, 아래 방법으로 진행해볼 수 있다.

1. RESTful Interface Tool 설치

RESTful Interface Tool for Windows

1.1.0(17 Nov 2020)

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_b0ed9438eb1248fb919f39e084

RESTful Interface Tool for Linux
3.2.1(16 Apr 2021)
https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_db4070dcd8e4468fb67d5aefbc

2. 첨부 “ilotz.zip” 파일을 다운로드

/ilotz/

• Change_iloTZ.bat
• Change_iloTZ.sh

-------------------------------------------------------------

ilorest login --nologo %1 --user %2 --password %3 --selector=HPeiLODateTime.v2_0_0

ilorest --nologo rawpatch .\ilodatetime.json

ilorest --nologo iloreset --url=%1 -u %2 -p %3

ilorest --nologo logout

echo %1

-------------------------------------------------------------

• ilodatetime.json

-------------------------------------------------------------

{
         "/redfish/v1/Managers/1/DateTime/":{
                       "TimeZone": {
            "Index": 31
                       }
         }
}
-------------------------------------------------------------

Windows 기준:
3. RESTful Interface Tool console 실행 > 다운로드 받은 “ilotz” 디렉토리로 이동

4. 아래 문구의 명령 수행
C:> Change_iloTZ.bat <%iLO_IPAddress%> <%Administrative_Account%> <%Password%>

e.g.)

Note. Script에서 수행되는 명령:
-------------------------------------------------------------
<snip>
iLO에 로그인:
ilorest login --nologo %1 --user %2 --password %3 --selector=HPeiLODateTime.v2_0_0

Timezone 변환:
ilorest --nologo rawpatch .\ilodatetime.json

Reset iLO:
ilorest --nologo iloreset --url=%1 -u %2 -p %3

접속 종료:
ilorest --nologo logout

대상 서버 IP Address 출력:
echo %1
<snip>
-------------------------------------------------------------
{
    "TimeZone": {
        "Index": 31,
        "Name": "Osaka, Sapporo, Tokyo, Seoul, Yakutsk",
        "UtcOffset": "+09:00",
        "Value": "JST-9:00"
    }
}
-------------------------------------------------------------

연관문서:
Advisory: (Revision) HPE Integrated Lights-Out 4 (iLO 4) and iLO 5 - The BIOS Time Zone May be Incorrect on Servers Set with Propagate Network Time Protocol (NTP) to Host or Propagate NTP or Onboard Administrator (OA) Time to Host
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00062543en_us

.