|
Objective 1.3 - Troubleshoot Virtual infrastructure Storage Components |
|
|
|
Written by Matthijs van den Berg
|
|
Tuesday, 06 January 2009 13:24 |
KNOWLEDGE
- Identify storage related events and log entries
- Analyze storage events to determine related issues
SKILLS AND ABILITIES
- Verify storage configuration using CLI, VI client and server log entries
- Troubleshoot storage connection issues using CLI , VI Client and logs
- Rescan events
VI Client: Use the VI Client to connect to the Virtual Infrastructure Click “Events” from the top icon bar Look for rescan events in the log and possible for subsequent errors CLI: Log in to the service console Execute the esxcfg-rescan command The results of the scan are displayed on the screen Log: All storage related events are logged in the vmkernel log files in the /var/log directory. Older logfiles are provided with an trailing number. All warnings from the vmkernel log file are in the vmkwarnings logfile.
- Failover events
Failover events can be identified by looking at the preferred path and the active path. VI Client: Use the VI Client to connect to the Virtual Infrastructure Click “Events” from the top icon bar Or Use the VI Client to connect to the Virtual Infrastructure Select an ESX host from the Inventory Choose “Configuration”, “Storage” Select a storage volume, click “Properties” Click “Manage paths” and check if the active path is the preferred path. CLI: Log in to the service console Execute the “esxcfg-rescan command The results of the scan are displayed on the screen and it shows whether the preferred path is the active path. Or Failover attempts are logged . Log: All storage related events are logged in the vmkernel log files in the /var/log directory. Older logfiles are provided with an trailing number .
- Interpret log entries for configuration validation and predictive analysis
- Troubleshoot file system errors using logs and CLI
TOOLS
- VI client
- CLI
- vm-support script
- esxcfg-*
- vmkfstools
|