TroubleshootingPrompt
Network Device Error Explainer
Paste any syslog message or error output from your network device and get a plain-English explanation, severity assessment, root cause, and remediation steps. Supports Cisco IOS/IOS-XE/IOS-XR/NX-OS, Juniper Junos, Arista EOS, Palo Alto PAN-OS, and Fortinet FortiOS.
27 copies
ChatGPTClaudeGemini
Customize variables
The specific vendor, OS, and platform (e.g. Cisco IOS-XE Catalyst 9300, Juniper Junos MX204, Arista EOS 7050X, Palo Alto PAN-OS PA-440, Fortinet FortiOS FortiGate 100F)
Paste the exact syslog line(s) or error message from the device
Any recent changes, events, or additional context
Tips for better results
- ·Include the full syslog line including timestamp, facility, and severity — do not truncate it
- ·If you have multiple related errors, paste them all together
- ·Mention the OS version if you know it — some errors behave differently across versions
- ·For Cisco IOS XR: include the node location (e.g. 0/RP0/CPU0) if present in the syslog
- ·For Juniper: include the routing-engine (RE0/RE1) and daemon name from the syslog
- ·For Palo Alto: include the log type (threat, traffic, system, config) for better analysis
- ·For FortiOS: include the VDOM name if multi-VDOM is enabled
Prompt preview
○ DEVICE_TYPE○ ERROR_MESSAGE○ CONTEXT
You are a senior network engineer with deep expertise in troubleshooting across multiple vendors: Cisco IOS/IOS-XE/IOS-XR/NX-OS, Juniper Junos, Arista EOS, Palo Alto PAN-OS, and Fortinet FortiOS. Device: [Vendor / OS / Platform] Error / syslog output: ``` [Error message or syslog output] ``` Context: [Context (optional)] Please provide: 1. **Plain English explanation** — what this error means in simple terms, no jargon 2. **Severity** — is this critical, warning, or informational? Will it affect traffic? 3. **Root cause** — the most likely reasons this is happening on [Vendor / OS / Platform] 4. **Immediate diagnostic commands** — exact CLI commands to run right now to confirm the cause (use the correct syntax for [Vendor / OS / Platform]) 5. **Fix** — the exact CLI commands or steps to resolve it (correct syntax for [Vendor / OS / Platform]) 6. **Prevention** — how to prevent this from happening again If multiple error messages are present, address each one and note if they are related. Always use the correct vendor-specific CLI syntax and terminology for [Vendor / OS / Platform].
Tags
syslogerrorstroubleshootingmulti-vendorciscojuniperaristapaloaltofortinet