Cisco Cisco UCS B440 M1 High-Performance Blade Server Guia De Resolução De Problemas

Página de 3
Contents
Introduction 
Prerequisites
Requirements
Required Log files
Analyzing logs for initial clues
Gather information about UCS setup
Suggestion for proactively monitoring FI
Related Information
Introduction 
The document provides steps to investigate Unified Computing System Fabric Interconnect ( FI )
 crash or unexpected reboot failure.
On a high-level, the following problems could result in reboot of FI
    Kernel space process crashed ( aka Kernel panic ) 
    Kernel ran out of memory ( Out of Memory - OOM killing a user process to reclaim memory
)  
    User space process crashed    ( ex. - netstack, fcoe_mgr , callhome etc ) 
    FI firmware issue ( rare scenario , example - 
 )  or hardware component failure
 ( like SSD used for storage )
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
Cisco Unified Computing System (UCS) Manager
Cisco Unified Computing System (UCS) Manager Command Line Interface (CLI)
Required Log files
When FI reboots unexpectedly, collect following logs and upload it to TAC Service Request. 
      UCSM techsupport log bundle 
      Check if core dump file is created around the time of reboot event.