Examkin

Question

Difficulty: HardUtilizing Command-Line Network Troubleshooting Utilities

A network administrator on a Linux workstation is troubleshooting an inability to reach a remote HTTPS service hosted at 10.20.30.50 on custom port 8443. Following a structured bottom-up OSI troubleshooting methodology, in what sequence should the administrator execute the following command-line diagnostics to systematically isolate the failure?

  1. 1Execute `ip addr show` to verify local host IP address assignment, netmask, and interface link state.
  2. 2Execute `ping -c 3 192.168.1.1` to test ICMP reachability to the local default gateway.
  3. 3Execute `traceroute -n 10.20.30.50` to identify the intermediate router hop where packet forwarding fails along the path.
  4. 4Execute `nc -zv 10.20.30.50 8443` to probe TCP port accessibility and verify transport layer listener availability.

Answer

The correct diagnostic sequence begins with verifying host interface configuration (`ip addr show`), testing local gateway reachability (`ping -c 3 192.168.1.1`), isolating intermediate path routing (`traceroute -n 10.20.30.50`), and finally checking specific TCP port socket accessibility (`nc -zv 10.20.30.50 8443`).
Adhering to a bottom-up troubleshooting methodology requires starting with local host interface verification (`ip addr show`), followed by testing default gateway reachability (`ping`), isolating multi-hop routing paths (`traceroute`), and concluding with transport layer port testing (`nc`).

Step-by-Step Solution

1
Inspect local network interface configuration using `ip addr show`.
Confirms physical/data link connection state and validates local IPv4 address configuration.
Troubleshooting must begin at the local host level (Layers 1 and 2) to ensure the network interface is up and bound to an IP address.
2
Test ICMP echo communication to the default gateway with `ping -c 3 192.168.1.1`.
Verifies ARP resolution and local segment Layer 3 forwarding capability.
If local gateway ping fails, off-subnet routing is impossible, making upstream path tracing unnecessary until local connectivity is restored.
3
Perform path discovery to the target IP address using `traceroute -n 10.20.30.50`.
Identifies the specific hop or WAN interface where packet transit terminates.
Layer 3 path reachability must be confirmed end-to-end before probing specific transport layer application ports.
4
Probe destination transport port using netcat (`nc -zv 10.20.30.50 8443`).
Determines if TCP port 8443 accepts connection attempts or if packets are filtered by security devices.
Transport layer port socket testing is the final step once underlying Layer 3 routing and path reachability are confirmed.

Key Concept

Bottom-up CLI Network Troubleshooting Methodology
Estimated Time:2m 0s
Rate this question

Topics

Utilizing Command-Line Network Troubleshooting Utilities

More questions from this topic