A network administrator is addressing an issue where remote branch office routers intermittently drop OSPF neighbor adjacencies with the central core router following a WAN circuit bandwidth upgrade. Place the administrator's troubleshooting actions in the correct sequential order according to the CompTIA troubleshooting methodology, from the initial step to the final step.
- 1Interview branch office users regarding disconnect timestamps and inspect central core router syslog files to gather OSPF MTU mismatch error messages.
- 2Consider recent WAN environment changes and hypothesize that the service provider altered interface MTU limits, causing large OSPF Database Description (DBD) packets to be dropped.
- 3Execute ICMP ping tests with the Don't Fragment (DF) flag set and maximum payload size across the WAN link to confirm packet drops occur above the standard MTU threshold.
- 4Draft a formal change request to adjust router IP MTU settings and assess potential routing table re-convergence impacts prior to execution.
- 5Confirm OSPF adjacencies maintain a stable FULL state for 24 hours post-change and configure automated monitoring alerts for MTU mismatch drops.
- 6Record the root cause, exact terminal commands executed, and verified baseline configurations within the organization's centralized knowledge management system.
Cevap
The correct sequence follows the CompTIA 6-step troubleshooting methodology: 1. Identify the problem (gathering symptoms through user interviews and log inspection), 2. Establish a theory of probable cause (hypothesizing WAN provider MTU mismatch), 3. Test the theory to determine the cause (executing ping tests with the DF bit set), 4. Establish a plan of action to resolve the problem and identify potential effects (drafting a change request and evaluating routing impacts), 5. Verify full system functionality and implement preventive measures (confirming stable OSPF FULL state and adding automated alerts), 6. Document findings, actions, and outcomes (recording resolution details in the central repository).
The correct order follows CompTIA's official 6-step sequence: 1. Identify the problem by gathering information from users and logs, 2. Establish a theory of probable cause by considering recent changes, 3. Test the theory using targeted diagnostic tools (DF-bit pings), 4. Establish a plan of action and identify potential effects before applying changes, 5. Verify full system functionality and implement preventive measures, and 6. Document findings, actions, and outcomes as the final administrative step.
Adım Adım Çözüm
Anahtar Kavram
CompTIA Troubleshooting Methodology Sequence
Tahmini Süre:2m 0s