A network engineer is responding to a critical datastore access failure across a virtualized server cluster immediately following scheduled network switch maintenance. Place the following troubleshooting steps in the correct chronological sequence according to the official CompTIA troubleshooting methodology.
- 1Gather hypervisor storage event logs and interview host administrators regarding the specific symptoms observed during maintenance.
- 2Hypothesize that the dedicated iSCSI traffic VLAN was inadvertently omitted from the switch trunk port configuration.
- 3Inspect the running configuration of the storage switch to verify whether the iSCSI VLAN ID is active on the trunk link.
- 4Formulate a change plan to re-add the missing iSCSI VLAN to the trunk port profile and apply the configuration fix.
- 5Run storage I/O performance tests across all hypervisor nodes to confirm datastore access and configure automated switch configuration logging.
- 6Log the root cause, configuration fix, and updated maintenance checklist in the IT service management system.
Answer
The correct sequence follows the official 6-step CompTIA Troubleshooting Methodology: 1. Identify the problem (gather hypervisor logs and interview admins) -> 2. Establish a theory of probable cause (hypothesize missing iSCSI VLAN) -> 3. Test the theory to determine cause (inspect switch running configuration) -> 4. Establish a plan of action and implement the solution (formulate change plan and apply fix) -> 5. Verify full system functionality and implement preventive measures (run I/O performance tests and configure logging) -> 6. Document findings, actions, and outcomes (log incident root cause and resolution in ticketing system).
The correct order strictly adheres to the standard 6-step CompTIA troubleshooting methodology: 1. Identify problem -> 2. Establish theory -> 3. Test theory -> 4. Plan of action & implement -> 5. Verify system functionality & preventive measures -> 6. Document findings.
Step-by-Step Solution
Key Concept
CompTIA 6-Step Network Troubleshooting Methodology
Estimated Time:2m 0s