NOC Console Lab · Connectivity Triage

Trace From the Source

Diagnose a reported outage remotely — find the hop where the path breaks, then decide who owns the fix.

secure shell local · NOC-ADMIN-02

noc-admin@NOC-ADMIN-02:~$

Ticket #NT-4471

Priya Raman in the Maple Wing reports she can’t load an off-campus supplier site. Before walking across campus, confirm from her workstation (MAPLE-WS14, 10.40.12.83) how far traffic gets toward the provider’s edge router at 203.0.113.254.

You’re signed in at the NOC on NOC-ADMIN-02. Open a remote shell to her workstation, run the path trace from there, then read where replies stop.

Tasks

Open a remote shell from NOC-ADMIN-02 to the workstation — ssh tech@10.40.12.83
On the workstation, trace the path to the provider edge — tracert 203.0.113.254
In the output, click the first hop that stops responding

Questions

1. What is the IP of the last hop that replies before the timeouts begin?

2. The hops inside your network reply; replies stop just past the provider edge. Where is the fault most likely located?

Priya’s workstation network adapter

The campus gateway / local LAN

Beyond your network, at or past the provider — escalate to the ISP

The DNS resolver configuration

3. Why run the trace from MAPLE-WS14 instead of from NOC-ADMIN-02?

The command runs faster on the user’s machine

The path from the affected host can differ; tracing elsewhere may miss a host- or path-specific fault

NOC-ADMIN-02 is not allowed to run trace tools

It hides the trace from the provider

Submit

Callsign (no real names — pseudonym only)

0 / 6

N10-007 · 5.2 N10-007 · 3.4 APNET · 4.4.C APNET · 1.1.A