Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2301982.1
Update Date:2017-09-06
Keywords:

Solution Type  Technical Instruction Sure

Solution  2301982.1 :   NPE: DIED TOTAL_DEATHS: Errors Detected In IB Switch Logs  


Related Items
  • Sun Datacenter InfiniBand Switch 36
  •  
  • Exalogic Elastic Cloud X4-2 Eighth Rack
  •  
  • Sun Network QDR InfiniBand Gateway Switch
  •  
Related Categories
  • PLA-Support>Sun Systems>SAND>Network>SN-SND: Sun Network Infiniband
  •  




In this Document
Goal
Solution
References


Created from <SR 3-15539560685>

Applies to:

Exalogic Elastic Cloud X4-2 Eighth Rack - Version X4 and later
Sun Datacenter InfiniBand Switch 36 - Version All Versions to All Versions [Release All Releases]
Sun Network QDR InfiniBand Gateway Switch - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

Logging the following in the messages:

Aug 14 08:31:44 eldv01gw01 logger: luproxy DIED TOTAL_DEATHS:2
Aug 14 08:31:45 eldv01gw01 logger: RESTART RESULTS-
Aug 14 08:31:45 eldv01gw01 logger: luproxy DIED REASON: NO_PS
 

Solution

This is a restart of the ILOM deamons and this might happen due to daemon startup timing order, customers could see such log messages but they are safe to ignore unless it constantly logs such occurrences and finally stops restarting those dead daemons.

Unless there are lots of such reports and you are not able to login to the spsh shell (either from root login or directly using ilom-admin or ilom-operator) these are safe to ignore.
 

References

<BUG:25965070> - GW STAYS IN BOOT IN PROGRESS TOO LONG WHEN AN ETHERNET PORT IS DOWN

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback