1 / 22

Module 13 Troubleshooting

Module 13 Troubleshooting. <Place supporting graphic here>. Module Objectives:. Troubleshooting considering for the PS-M4110 Log file analysis: M1000 Hardware Log CMC Logs Storage Array Status Log Storage Event Log Troubleshooting a DCB configuration issue.

shay
Download Presentation

Module 13 Troubleshooting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Module 13 Troubleshooting <Place supporting graphic here>

  2. Module Objectives: • Troubleshooting considering for the PS-M4110 • Log file analysis: • M1000 Hardware Log • CMC Logs • Storage Array Status Log • Storage Event Log • Troubleshooting a DCB configuration issue. • Perform a Virtually Reseat a Module

  3. Troubleshooting

  4. PS-M4110 Troubleshooting Considerations • CMC Firmware must be at 4.11 A01 or higher • Additional CMC virtual serial port option (racadm connect server-number) • CMC status will indicated warning and critical conditions • CMC information and debug logs • Network configuration issues • Fabric Mismatch health conditions: • The fabric is populated with IOMs which do not support 10Gb KR. • The fabric is not populated with any IOMs. • A combination of 1 and 2. • This condition will be reset when the above fabric conditions are rectified. This condition can also be seen if the fabric IOMs are physically moved/removed to create any one of the above 3 conditions.

  5. Racadm Commands • CMC firmware version 4.11 help -- list racadm subcommand description help <subcommand> -- display usage summary for a subcommand ? -- list racadm subcommand description ? <subcommand> -- display usage summary for a subcommand arp -- display the networking arp table chassisaction -- execute chassis or switch power-up/down/cycle or KVM powercycle closessn -- close a session clrraclog -- clear the CMC log clrsel -- clear the System Event Log (SEL) cmcchangeover -- changes the redundant state of the CMC from active to standby and vice versa config -- modify CMC configuration properties connect -- connect to switch or blade serial console deploy -- deploy blade by specifying required properties feature -- display features active on the chassis / feature deactivation featurecard -- feature card status and list the available features fwupdate -- update the firmware on a CMC, server, IOM inf, or KVM getassettag -- display asset tag getchassisname -- get the chassisname getconfig -- display CMC configuration properties getdcinfo -- display general I/O module and DC configuration information getfanreqinfo -- display fan request information for Servers and Switches getflexaddr -- display Flexaddress enablement status for all slots and fabrics. getioinfo -- display general IO information getkvminfo -- display the KVM module information

  6. Logs • M1000e Hardware Log • CMC Log

  7. Logs • Storage Event Log

  8. Logs • PS-M4110 Event Log

  9. Error Example • Array displaying and error • Click the slot icon for error details

  10. Error Example • Click the Storage Event Log

  11. Error Example • Review the event in the Storage Log • The array is configured for DCB and the switch is not configured for DCB

  12. Error Example- Solution • Turn off DCB on the MXL Switch • FTOS>enable • FTOS#configure • FTOS(conf)#no dcbenable • FTOS(conf)#no dcbstack-unitallpfc-bufferingpfc-ports 56 pfc-queues 2 • FTOS(conf)#exit • FTOS#copyrunning-configstartup-config • FTOS# reload

  13. Error Example • Array error cleared

  14. Virtual Reseat • Virtual reseat the array • Shutdown the member before issuing a virtual reseat command

  15. Virtual Reseat • Virtual reseat the array using the CMC interface

  16. Thermal Shutdown • Thermal shutdown recovery requires virtual reseat of the Blade Array slot or M1000e power cycle to restart. • 35C maximum operating temp.

  17. Switch • Click on the switch to launch the switch GUI

  18. Switch • Click Launch I/O Module GUI

  19. Switch • Login to the switch GUI to manage the switch

  20. PS-M4110 Considerations 4G of Memory • System will ship with 4096MB of Memory – for future use. • 2G actually in use until PS firmware 7.0. Storage Enclosure Processor (SEP) • Updated on each CM separately; only Active CM is used • Updated at Boot, if needed. Cache to Flash • Memory is no longer battery-backed; no more 72 hour limit • Super Cap. provides several seconds of power to copy RAM contents to Flash • Triggered by Power Loss or Controller Eject • “Battery” terminology retained in messages/log entries Crash Dumps to Disk • System crashdump to flash will be stored to reserved disk area • Occurs automatically and will be enabled by default • Includes system crashdumps retrieved from the secondary controller • Can retain multiple crash dumps

  21. Module Summary • Now that you have completed this module you should be able to: • List 5 things to consider checking as you start troubleshooting the PS-M4110 • Check the following logs: • M1000 Hardware Log • CMC Logs • Storage Array Status Log • Storage Event Log • Describe the process for troubleshooting a DCB configuration issue. • Virtually reseat a Module

  22. Questions?

More Related