Daftar Pertemuan
Troubleshooting Tools
Team Roles
Pertemuan 13: Capstone Troubleshooting
Persiapan Ujian Akhir Semester
Pertemuan ini merupakan persiapan komprehensif untuk Ujian Akhir Semester. Fokus pada kemampuan troubleshooting jaringan enterprise yang terintegrasi.
Tujuan Pembelajaran
Mahasiswa mampu mendiagnosis dan memecahkan masalah kompleks pada jaringan enterprise yang terintegrasi (VLAN, Routing, WAN, Security) menggunakan metodologi troubleshooting yang sistematis dalam lingkungan team-based.
Metodologi Troubleshooting Enterprise Network
1. Systematic Troubleshooting Approach
Pendekatan terstruktur untuk troubleshooting jaringan enterprise yang kompleks:
Problem Identification
Identifikasi scope dan impact masalah
Information Gathering
Kumpulkan data dengan systematic commands
Hypothesis Formation
Buat dugaan berdasarkan evidence
Targeted Testing
Test hypothesis dengan focused commands
Solution Implementation
Implementasi fix yang tepat
Verification & Documentation
Konfirmasi dan dokumentasi solusi
2. Layer-by-Layer Troubleshooting Strategy
| OSI Layer | Common Issues | Diagnosis Commands | Solution Approach |
|---|---|---|---|
| Physical (1) | Kabel rusak, port down, power issues | show interfaces, show ip interface brief |
Ganti kabel, reset port, cek power |
| Data Link (2) | VLAN mismatch, STP loops, Duplex issues | show vlan, show spanning-tree, show interfaces |
Fix VLAN config, STP tuning, set duplex |
| Network (3) | IP conflicts, Routing issues, ACL blocking | show ip route, show ip ospf neighbor, show access-lists |
Fix IP scheme, routing config, ACL rules |
| Transport (4) | Port blocking, Session issues | telnet, traceroute, show tcp brief |
Open ports, check session state |
| Application (5-7) | Service down, DNS issues, Authentication | ping, nslookup, debug ppp authentication |
Restart services, fix DNS, check auth |
3. Divide and Conquer Strategy
- By Location: HQ, Branch, Remote sites
- By Technology: Switching, Routing, Security
- By Department: Admin, Sales, IT networks
- By Protocol: VLAN, OSPF, PPP, NAT
- Role Assignment: Layer experts dengan spesialisasi
- Communication: Regular sync-up meetings
- Documentation: Shared troubleshooting log
- Peer Review: Cross-verification solutions
Capstone Troubleshooting Challenge
Informasi Capstone Challenge
Durasi: 170 menit
Topik: Integrated Enterprise Troubleshooting
Format: Team-based (4-5 orang)
Bobot: 10% (Tugas 2)
Tujuan: Diagnosis multi-layer issues
Tools: Pre-configured problematic network
Deliverables: Troubleshooting report + Fixed network
Penilaian: Methodology & completeness
Enterprise Network Topology dengan Multiple Issues
Keterangan Topologi Enterprise:
- 3 Sites: Headquarters, Branch Office, Remote Site
- Multiple Technologies: VLAN, OSPF Multi-Area, PPP CHAP, NAT, ACL, VTP, STP
- Pre-configured Issues: Network sengaja dikonfigurasi dengan multiple errors
- Integration Points: Semua technologies terintegrasi dan saling dependent
Daftar Hidden Issues (Disembunyikan Instruktur)
Multiple Pre-configured Issues:
- VLAN database mismatch antar switch
- Trunk configuration errors
- STP loops dan root bridge issues
- VTP domain dan password mismatch
- Native VLAN不一致
- OSPF area assignment errors
- Missing network statements
- IP addressing conflicts
- Route redistribution problems
- Default route missing
- PPP CHAP authentication failure
- ACL blocking legitimate traffic
- NAT translation not working
- Port forwarding misconfiguration
- Service access restrictions
Troubleshooting Methodology Phase
Initial Connectivity Testing:
ping 192.168.10.1 ! Gateway local
ping 192.168.20.1 ! Gateway remote same area
ping 192.168.30.1 ! Gateway remote different area
ping 192.168.20.10 ! PC di remote same area
ping 192.168.30.10 ! PC di remote different area
! Document semua gejala dalam tabel
Baseline Network Status:
show ip interface brief
show interfaces status
show cdp neighbors
! VLAN dan Trunking status
show vlan brief
show interfaces trunk
show vtp status
Layer 2 Troubleshooting:
show vlan brief ! Pada semua switch
show vtp status
! Trunk configuration
show interfaces trunk
show interfaces fa0/24 switchport
! STP status
show spanning-tree
show spanning-tree root
show spanning-tree inconsistentports
Layer 3 Troubleshooting:
show ip route
show ip route ospf
show ip ospf neighbor
show ip ospf interface brief
! OSPF specific troubleshooting
show ip ospf database
debug ip ospf events ! Jika diperlukan
show running-config | section router ospf
WAN dan Security Troubleshooting:
show interfaces serial 0/0/0
debug ppp authentication
show running-config interface serial 0/0/0
! ACL dan NAT verification
show access-lists
show ip nat translations
show ip nat statistics
show running-config | include access-list
show running-config | include nat
Service Access Testing:
ping [destination] ! ICMP test
telnet [ip] [port] ! TCP service test
ftp [ip] ! FTP service test
http://[ip] ! Web service test
traceroute [destination] ! Path verification
Comprehensive Testing:
! Dari semua PCs test ke semua destinations
ping [all-devices]
traceroute [across-network]
! Service accessibility test
! Semua services harus accessible sesuai policy
show tech-support ! Comprehensive status
Documentation dan Reporting:
show running-config
copy running-config startup-config
! Screenshot semua verification commands
! Document semua fixes dalam troubleshooting log
Troubleshooting Challenge Scenarios
Symptoms: PC1 bisa ping PC2 tapi tidak bisa ping PC3 (beda VLAN, beda switch)
Expected Issues: VLAN mismatch, Trunk configuration, OSPF routing
Diagnosis Steps:
- Verifikasi VLAN assignment pada kedua switch
- Check trunk configuration antara switch-switch dan switch-router
- Verifikasi OSPF neighbor adjacency antara router
- Check network statements di OSPF configuration
- Verifikasi IP addressing dan subnet masks
Key Diagnosis Commands:
show vlan briefshow interfaces trunkshow ip ospf neighborshow ip route ospfshow running-config vlan
Symptoms: Router tidak belajar route dari router lain, OSPF adjacency stuck di INIT/2WAY
Expected Issues: Area mismatch, Network statements, Authentication, Timer mismatch
Diagnosis Steps:
- Verifikasi OSPF neighbor adjacency status dan state
- Check network statements dan wildcard masks
- Periksa area assignment consistency
- Verifikasi interface OSPF status dan timers
- Check untuk authentication mismatch
Key Diagnosis Commands:
show ip ospf neighborshow ip ospf interfacedebug ip ospf adjshow running-config | section ospfshow ip protocols
Symptoms: Branch dan Remote sites tidak bisa terkoneksi, PPP session tidak establish
Expected Issues: CHAP authentication failure, ACL blocking, NAT misconfiguration
Diagnosis Steps:
- Check PPP encapsulation dan authentication configuration
- Verifikasi CHAP username/password consistency
- Check applied ACLs pada WAN interfaces
- Verifikasi NAT configuration dan translations
- Test service access melalui NAT
Key Diagnosis Commands:
show interfaces serialdebug ppp authenticationshow access-listsshow ip nat translationsshow running-config interface
Troubleshooting Log Template
Capstone Troubleshooting Report - Kelompok [X]
Executive Summary
Tim Members: [Nama anggota kelompok]
Total Issues Identified: [Jumlah]
Time to Resolution: [Waktu] menit
Overall Network Status: [Fully Operational/Partially Fixed]
Methodology & Approach
Troubleshooting Strategy: [Bottom-up/Top-down/Divide-and-conquer]
Team Roles Assignment:
- Layer 2 Expert: [Nama] - VLAN, STP, Trunking
- Layer 3 Expert: [Nama] - OSPF, Routing, IP
- Security Expert: [Nama] - ACL, NAT, PPP
- Documentation: [Nama] - Logs, Screenshots
### Issue 1: [Nama Masalah - e.g., "Inter-VLAN Routing Failure"]
Documentation Best Practices:
- Gunakan timestamp untuk setiap entry troubleshooting
- Document before/after configuration screenshots
- Sertakan output verification commands
- Catat waktu yang dibutuhkan untuk setiap issue resolution
- Include team collaboration notes
Success Metrics & Evaluation
| Evaluation Criteria | Weight | Excellent (90-100%) | Good (70-89%) | Needs Improvement (<70%) |
|---|---|---|---|---|
| Issue Identification | 40% | Semua issues teridentifikasi dengan akurat | Major issues teridentifikasi, beberapa minor terlewat | Banyak issues tidak teridentifikasi |
| Troubleshooting Methodology | 30% | Systematic approach, logical sequence | Mostly systematic, beberapa inconsistencies | Random approach, tidak terstruktur |
| Solution Accuracy | 20% | Semua solutions correct dan optimal | Major solutions correct, beberapa suboptimal | Banyak incorrect solutions |
| Documentation & Teamwork | 10% | Excellent documentation, great teamwork | Adequate documentation, good collaboration | Poor documentation, minimal teamwork |
Advanced Troubleshooting Tips
- Start with Basics: Selalu check physical connectivity pertama
- Use Systematic Approach: Layer 1 → Layer 2 → Layer 3 → Application
- Document Everything: Keep timestamped notes dan screenshots
- Work as Team: Assign specific roles dan regular sync-ups
- Test Incrementally: Verify setelah setiap major change
- Multiple Changes: Jangan buat multiple changes simultaneously
- Skipping Documentation: Sulit revert changes tanpa documentation
- Ignoring Basics: Seringkali issue sederhana yang terlewat
- Poor Communication: Team members bekerja overlap atau conflict
- Panic Mode: Tetap calm dan systematic under pressure
Time Management Strategy (170 menit):
Information gathering
Baseline testing
Layer 2 & 3 diagnosis
Targeted fixes
Security & services
Complex issues
Final verification
Documentation
Deliverables Requirements
Yang Harus Dikumpulkan (Kelompok)
1. Troubleshooting Report Document
Format: PDF document
Content: Complete troubleshooting log dengan semua sections
2. Fixed Packet Tracer File
Format: .pkt file
Content: Network dengan semua issues fixed
3. Verification Screenshots
Format: Image files atau embedded dalam PDF
Content: Screenshot semua verification commands
4. Peer Evaluation
Format: Confidential form
Content: Team member contribution assessment