![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2087334.1 : SPARC T5-2: prtdiag -v : ILOM environmental and firmware information is missing
In this Document
Created from <SR 3-10591922731> Applies to:SPARC T5-2 - Version All Versions and laterInformation in this document applies to any platform. Symptoms
=========================== Environmental Status ============================ < Sensor Data removed > ============================ FW Version ============================ ====================== System PROM revisions ======================= Chassis Serial Number
CauseFor the SPARC T5-2 pci root complex pci_1 [/pci@340] contains the ILOM communication port, system software like the Oracle Hardware Management Pack [OHMP ] services rely on this port to communicate with the ILOM. ILOM disk monitoring services also rely on this port to get the status of internal disk and RAID LUNs. Because of the unique root complex naming convention of the SPARC T5-2, LDOM assignment of root complex pci_1 [instead of pci_0] to alternate service or Non Primary Root domains [NPRD] may occur [not recommended]. On Solaris 11.2 SRU 8.0.4 [and above] prtdiag was modified to use EoUSB [ Ethernet over USB] for displaying ILOM information like Environmental Status,FW version and System Prom revisions. When the EoUSB port is not present in the primary domain, the prtdiag utility will proceed to complete the command without displaying this section of the output [same behavior with guest domain]. SolutionThe solution is to prevent root complex pci_1 [/pci@340/] which contains the ILOM communication port from getting assigned to a non primary root domain [NPRD] during LDOM/OVM initial configuration. Engineering did not enforce this restriction in the SPARC T4/T5 family of servers but have been enforced this restriction on SPARC T7/M7 systems and above. The workaround for this issue is as follows: STEP 1.] login to ILOM and disable the interconnect, then power cycle the platform set /SP/network/interconnect hostmanaged=false STEP 2.] log into solaris primary domain and make ilomconfig unusable by changing the permission of ilomconfig to 444 [ read only ] From Solaris the following should ensure that ds_snmp is used not EthUSB. STEP 2.1] # svcadm disable picl
by doing STEP 2.2 this should force ilomconfig not to execute and force prtdiag to use ds_snmp root@solaris:~# cd /usr/lib
root@solaris:/usr/lib# ls -l ilom* lrwxrwxrwx 1 root root 18 May 27 16:05 ilomconfig.builtin -> ../sbin/ilomconfig root@solaris:/usr/lib# /usr/sbin/ilomconfig list -bash: /usr/sbin/ilomconfig: Permission denied root@solaris:/usr/lib# ilomconfig list interconnect -bash: /usr/sbin/ilomconfig: Permission denied root@solaris:/usr/lib#
References<BUG:16456326> - PRTDIAG INTERMITTENTLY DOES NOT LIST MEMORY CONFIGURATION INFO<BUG:21037455> - T5-2 PRTDIAG -V INFOR MISSING AFTER UPGRADED INTO ENTIRE@0.5.11-0.175.2.8.0 <NOTE:1948940.1> - On SPARC T5-2, removing bus with usbecm device (pci_1 / pci@340) from primary/control domain can impact FMA and ldmd processing Attachments This solution has no attachment |
||||||||||||||||||
|