📝 Section Review: Logging & Troubleshooting
اہم نکاتKey TakeawaysKey Takeaways
- صحیح level پر log کریں: locally warnings، syslog کو notifications — debugging صرف active troubleshooting میں۔Sahi level par log karo: locally warnings, syslog ko notifications — debugging sirf active troubleshooting mein.Log at the right level: warnings locally, notifications to syslog — debugging only when actively troubleshooting.
- ہر log message میں severity اور event ID ہوتی ہے (جیسے %ASA-4-106023) — ID exact cause pinpoint کرتی ہے۔Har log message mein severity aur event ID hoti hai (jaise %ASA-4-106023) — ID exact cause pinpoint karti hai.Every log message carries a severity and event ID (e.g. %ASA-4-106023) — the ID pinpoints the exact cause.
- Packet-tracer سب سے تیز diagnostic ہے: یہ exact phase دکھاتا ہے جہاں packet drop ہوتا ہے۔Packet-tracer sab se tez diagnostic hai: ye exact phase dikhata hai jahan packet drop hota hai.Packet-tracer is the fastest diagnostic: it shows the exact phase where a packet is dropped.
- ASDM Monitoring same data کے لیے visual packet-tracer، threat graphs اور log views دیتا ہے۔ASDM Monitoring same data ke liye visual packet-tracer, threat graphs aur log views deta hai.ASDM Monitoring gives visual packet-tracer, threat graphs, and log views for the same data.
- Real captures (`capture ...`) simulation کو complement کرتے ہیں — یہ دکھاتے ہیں wire پر اصل میں کیا گزرا۔Real captures (`capture ...`) simulation ko complement karte hain — ye dikhate hain wire par asal mein kya guzra.Real captures (`capture ...`) complement simulation — they show what actually crossed the wire.
خود جانچ (مشق)Self-Check (Practice)Self-Check (Practice)
یہ مشقی سوالات ہیں، امتحانی سوالات نہیں۔These are practice questions, not exam questions.These are practice questions, not exam questions.
❓ ASA logging levels اور sensible production choices؟ASA logging levels aur sensible production choices?ASA logging levels and sensible production choices?
0 emergencies سے 7 debugging تک۔ Locally warnings (4) پر log کریں؛ notifications (5) اور above syslog کو بھیجیں۔ Debugging (7) صرف live troubleshooting میں تھوڑی دیر — یہ log flood کر دیتا ہے۔0 emergencies se 7 debugging tak. Locally warnings (4) par log karo; notifications (5) aur above syslog ko bhejo. Debugging (7) sirf live troubleshooting mein thodi der — ye log flood kar deta hai.0 emergencies to 7 debugging. Log locally at warnings (4); send notifications (5) and above to syslog. Debugging (7) only briefly during live troubleshooting — it floods the log.
❓ Packet-tracer کیسے use کرتے ہیں؟Packet-tracer kaise use karte ho?How do you use packet-tracer?
`packet-tracer input <in-if> <proto> <src-ip> <src-port> <dst-ip> <dst-port> [detailed]` — یہ simulated packet کو ACL، NAT اور routing phases سے گزارتا ہے اور آخر میں ALLOW یا DROP reason کے ساتھ بتاتا ہے۔`packet-tracer input <in-if> <proto> <src-ip> <src-port> <dst-ip> <dst-port> [detailed]` — ye simulated packet ko ACL, NAT aur routing phases se guzarta hai aur aakhir mein ALLOW ya DROP reason ke sath batata hai.`packet-tracer input <in-if> <proto> <src-ip> <src-port> <dst-ip> <dst-port> [detailed]` — it walks a simulated packet through ACL, NAT, and routing phases and ends with ALLOW or DROP plus the reason.
❓ ایک flow drop ہو رہا ہے — اپنا troubleshooting method بتائیں۔Ek flow drop ho raha hai — apna troubleshooting method batao.A flow is dropped — describe your troubleshooting method.
Packet-tracer dropping phase کا نام بتاتا ہے؛ پھر اس feature کے counters/config check کریں (`show access-list` hits، `show nat`/`show xlate`، `show route`)، اور exact event ID کے لیے `show logging`۔ ایک وقت میں ایک layer fix کریں اور دوبارہ trace کریں۔Packet-tracer dropping phase ka naam batata hai; phir us feature ke counters/config check karo (`show access-list` hits, `show nat`/`show xlate`, `show route`), aur exact event ID ke liye `show logging`. Ek waqt mein ek layer fix karo aur dobara trace karo.packet-tracer names the dropping phase; then check that feature's counters/config (`show access-list` hits, `show nat`/`show xlate`, `show route`), and `show logging` for the exact event ID. Fix one layer at a time and re-trace.