This
- To troubleshoot high utilization on a NetApp volume.
- To troubleshoot Disk I/O on a VMware Virtual Machine.
- To verify the boot-up configuration for UCS service profiles.
Use the following menu options to navigate the SL1 user interface:
- To view a pop-out list of menu options, click the menu icon (
). - To view a page containing all of the menu options, click the Advanced menu icon (
).
Troubleshooting High Utilization on a NetApp Volume
Suppose that in the Event Console page, an event states that a NetApp volume is over 97% full.
To see which systems use this volume:
- In the classic user interface, select the graph icon (
) in the Name column of the event to drill-down in to detailed information about the volume. - Select the tab. The Device View page displays the volume's relationships to other IT infrastructure components. Mousing over a device displays information about that device.
- Double-clicking on a device opens the topology view for that device. In this example, double-clicking on the VMware datastore related to the volume shows the relationships between the datastore and VMware Virtual Machines.
- From here, you can look at and drill-down to each virtual machine to see which virtual machine is consuming the most storage.
Verifying Boot-Up Configuration for UCS Service Profiles
This example shows how relationship information can be used to show potential flaws in architecture.
In the case of FlexPod:
- A UCS Service Profile has a 1-to-1 relationship with an ESXi host.
- A VMware datastore has a 1-to-1 relationship with a NetApp LUN.
Suppose that over time, all service profiles were booting from the same NetApp LUN. Suppose that LUN has an issue that caused your entire Virtualization environment to be unavailable. Although the verification process performed by the NetApp system would make this case unlikely, a best practice boot-up design is important for performance and should be validated.