Lab: 42 N W Troubleshooting ‐ use Network Path Analyzer - TanveeKhanDB/OCI GitHub Wiki
Network Path Analyzer:
It's an OCI-native diagnostic tool that simulates and validates the network path between a source and a destination — without sending any actual traffic. It checks every hop: routing tables, security lists, NSGs, gateways, and peering connections, and tells you exactly where traffic is allowed, blocked, or misconfigured.
A free, simulation-based diagnostic tool inside OCI Console that traces the logical path between a source and destination, inspecting every routing and security policy along the way — without sending any real traffic.
Think of it as a "virtual traceroute with policy intelligence" — it doesn't just tell you the path, it tells you why traffic fails at each layer. Key uses: connectivity troubleshooting between subnets, validating firewall rules before deployment, checking DRG/VPN/FastConnect paths, auditing security list gaps.
Benefits:
-
No actual traffic needed — purely simulated, zero risk
-
Pinpoints the exact hop and rule causing a block
-
Works across VCNs, peerings, DRG, and on-prem paths
-
Free, native tool — no agent or third-party needed
-
Saves hours vs manual rule-by-rule audit
Imp point:
- It is GUI version of Telenet.
- We not need to provide the port from source its manage by OS while its needed at destination side.
Steps to create Network Path Analyzer in OCI
OCI Console → Networking → Network Command Center → Network Path Analyzer
Server Details:
Note: We can see telnet is working fine between Jump Server from Public subnet and App Server from Private Subnet.
Getting Error: