Channels

Top 100 Trending New

Categories

Crypto Gaming News Entertainment Music Sports Tech Gambling Bots and mini apps Finance Business Education Lifestyle Health Travel Auto Fashion Jobs Dating Deals and shopping

Stickers

Stickers Emoji Themes Wallpapers

Bots Gifts Tools

Theme

CurrencyUSD

$US DollarUSD ₽Russian RubleRUB €EuroEUR ₴Ukrainian HryvniaUAH ₸Kazakhstani TengeKZT ₺Turkish LiraTRY złPolish ZlotyPLN ₪Israeli New ShekelILS AEDUnited Arab Emirates DirhamAED R$Brazilian RealBRL RpIndonesian RupiahIDR RMMalaysian RinggitMYR ¥Japanese YenJPY ₩South Korean WonKRW CN¥Chinese YuanCNY

Português (Brasil)

Bahasa Indonesia

Беларуская

Українська

Channels Categories Stickers Bots Gifts Tools

Premium Wiki Glossary Legal

Notifications Settings Log in

Every one please bring laptop — Security vibes — TG.ME

Security vibes@secvibes · 384 subscribers Open in TelegramOpen

Every one please bring laptop

t.me/secvibes/376

August 30, 2024 399

More from this channel

https://meet.google.com/ubj-hbpz-eed 729·Sep 11 I am on the way to class 827·Sep 4 Ticket 5: Unequal Load Balancing Not Working Symptom: Unequal load balancing is not functioning between R1 and R2. Troubleshooting Steps: Check the variance setting in the EIGRP configuration. Command: show running-config | section router eigrp Verify the metric of the routes in the routing table. Command: show ip route eigrp Solution: Adjust the variance to allow EIGRP to consider multiple paths. Command: plaintext Copy code R1(config)# router eigrp 10 R1(config-router)# variance 2 Ticket 6: Missing EIGRP Routes on R3 Symptom: R3 is missing EIGRP routes from R1. Troubleshooting Steps: Verify the EIGRP process and neighbors. Command: show ip eigrp neighbors Check for ACLs that may be blocking EIGRP traffic. Command: show access-lists Solution: Modify or remove the ACL to allow EIGRP traffic. Command: plaintext Copy code R3(config)# no access-list <number> Ticket 7: EIGRP Convergence Issues Symptom: Slow EIGRP convergence between all routers. Troubleshooting Steps: Verify hello and hold timers. Command: show ip eigrp interfaces detail Check for routing loops or high CPU usage. Command: show processes cpu Solution: Adjust the hello and hold timers for faster convergence. Command: plaintext Copy code R1(config)# interface Serial0/0 R1(config-if)# ip hello-interval eigrp 10 5 R1(config-if)# ip hold-time eigrp 10 15 Ticket 8: Route Redistribution Issue Symptom: Redistribution between OSPF and EIGRP on R2 is not working. Troubleshooting Steps: Check the redistribution command. Command: show running-config | section router ospf Verify if the correct metric is applied. Command: show ip route Solution: Correct the redistribution metric and route-map configuration. Command: plaintext Copy code R2(config)# router ospf 1 R2(config-router)# redistribute eigrp 10 subnets metric-type 1 Ticket 9: EIGRP Stub Router Configuration Symptom: R3 is not receiving the desired routes due to its stub configuration. Troubleshooting Steps: Check the stub configuration on R3. Command: show running-config | section router eigrp Verify if other routers are aware of R3’s stub status. Command: show ip eigrp neighbors Solution: Modify R3’s stub configuration to allow specific route types, such as connected and static routes, to be advertised. Command: plaintext Copy code R3(config)# router eigrp 10 R3(config-router)# no eigrp stub R3(config-router)# eigrp stub connected static This command removes the existing stub configuration and reconfigures it to allow connected and static routes to be advertised. Ticket 10: High CPU Utilization on R1 Symptom: R1 is experiencing high CPU utilization due to EIGRP. Troubleshooting Steps: Check CPU processes. Command: show processes cpu sorted Verify if EIGRP is causing the high utilization. Command: show ip eigrp traffic Solution: Optimize EIGRP settings by adjusting the hold-time and hello-interval on R1 or limiting the number of queries. You can also reduce the frequency of EIGRP updates by configuring ip bandwidth-percent eigrp. Command: plaintext Copy code R1(config)# interface Serial0/0 R1(config-if)# ip bandwidth-percent eigrp 10 50 R1(config-if)# ip hello-interval eigrp 10 5 R1(config-if)# ip hold-time eigrp 10 15 This command limits the EIGRP traffic to 50% of the interface bandwidth and adjusts the hello and hold timers to reduce the CPU load. 848·Sep 2 Complex EIGRP Tickets with Solutions Ticket 1: EIGRP Neighbor Issue Between R1 and R2 Symptom: R1 and R2 are not forming an EIGRP neighbor relationship. Troubleshooting Steps: Verify EIGRP process ID on both routers. Command: show ip protocols Check if interfaces are up. Command: show ip interface brief Ensure the correct interfaces are included in the EIGRP process. Command: show running-config | section router eigrp Verify there is no passive-interface misconfiguration. Command: show ip eigrp neighbors Solution: Correct the passive-interface configuration on R1. Command: plaintext Copy code R1(config)# router eigrp 10 R1(config-router)# no passive-interface Serial0/0 Ticket 2: R3 Not Receiving Routes from R2 Symptom: R3 is not receiving routes from R2. Troubleshooting Steps: Check if R3 is configured as an EIGRP stub. Command: show running-config | section router eigrp Verify if R3 is receiving any EIGRP updates. Command: show ip eigrp neighbors Check the ip address configuration on R2 and R3. Command: show ip interface brief Solution: Modify the stub configuration on R3. Command: plaintext Copy code R3(config)# router eigrp 10 R3(config-router)# no eigrp stub connected Ticket 3: EIGRP Metric Misconfiguration Symptom: EIGRP routes on R4 are not showing the correct metric. Troubleshooting Steps: Check the bandwidth and delay settings on the interface. Command: show interfaces Verify the EIGRP K-values are consistent across all routers. Command: show ip protocols Solution: Adjust the bandwidth and delay on R4's interface. Command: plaintext Copy code R4(config)# interface Serial0/0 R4(config-if)# bandwidth 1000 R4(config-if)# delay 1000 Ticket 4: Flapping EIGRP Neighbor Relationship Symptom: The EIGRP neighbor relationship between R2 and R4 is flapping. Troubleshooting Steps: Check for physical layer issues. Command: show interfaces Analyze logs for EIGRP errors. Command: show log Verify the stability of the interface. Command: show interfaces Solution: Replace the faulty cable or fix the interface configuration on R2 or R4. Command: plaintext Copy code R2(config)# interface Serial0/1 R2(config-if)# no shutdown 606·Sep 2 Ticket 10: High CPU Utilization on R1Symptom: R1 is experiencing high CPU utilization due to EIGRP. 446·Aug 30

An open web layer over public Telegram — search, stats and channel reading right in your browser, no account, no install.

Not affiliated with Telegram FZ-LLC; all data comes from public sources.

Catalog

Top channels Categories Countries Search

Content

Stickers Emoji Gifts Themes Wallpapers

Help

Tools Wiki Glossary Blockchain Safety Premium Advertisers Advertising

© 2026 TG.ME · G.Media network· Updated 10/08/2026 · v0.2.0 · bde7f05

Privacy Terms DMCA & complaints Report a violation

Similar channels

Information Security Library - UAEU1.1K subscribers

Cyber Security career development2.3K subscribers

Cyber SIRT & Threat Hunting3.8K subscribers

F5 | PALOALTO | CHECKPOINT | SOPHOS | FORTIGATE | Zscaler | Cisco2.2K subscribers

Web Security | Bug hunting7.4K subscribers

AI Prompts | ChatGPT | Google Gemini | Claude59.4K subscribers

Daily Security4K subscribers

ArashDeljoo4.2K subscribers