<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Yavuz Selim Aktürk on Medium]]></title>
        <description><![CDATA[Stories by Yavuz Selim Aktürk on Medium]]></description>
        <link>https://medium.com/@ysakturk?source=rss-b19d1bde6728------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pLquVZhgZYB5VpKKZgwEeg.jpeg</url>
            <title>Stories by Yavuz Selim Aktürk on Medium</title>
            <link>https://medium.com/@ysakturk?source=rss-b19d1bde6728------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:07:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ysakturk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Single Source of Accuracy for Field and Operations Teams: Effective Racking]]></title>
            <link>https://medium.com/@ysakturk/the-single-source-of-accuracy-for-field-and-operations-teams-effective-racking-14e7659f8b7a?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/14e7659f8b7a</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 18:18:39 GMT</pubDate>
            <atom:updated>2026-08-12T18:18:39.959Z</atom:updated>
            <content:encoded><![CDATA[<p>In network planning and operation processes, physical cabinet layout and its documentation using the correct tools (especially MS Visio/rack diagram methods) are critical for the sustainability of a system. As seen in the image you shared, a modular rack/cabinet matrix designed as CABINET-A, CABINET-B, CABINET-C, and CABINET-D is a great example that simplifies operational processes.</p><p>The Importance of Cabinet Planning and Topology Documentation in Data Centers</p><p>The success of a network architecture is not limited to logical routing or protocol configurations. The level of organization, scalability, and documentation of the physical infrastructure directly determines the response speed of the operations team in the event of outages, hardware failures, or capacity increases.</p><p>A detailed rack diagram and topology study, as shown in the image, provides the following fundamental principles in modern network planning:</p><ol><li>Rack Unit (RU) Hierarchy and Product Placement</li></ol><p>The placement of devices within the rack should not be haphazard, but based on specific standards:</p><p>Placement of Heavy and Chassis Devices:</p><p>Heavy chassis-type switches/routers and large load balancers (e.g., the F5 VIPRION 44xx Chassis or Cisco ASR/Catalyst series shown in the image) are placed in the lowest U-levels (1U – 10U) of the rack. This both reduces the risk of tipping by maintaining the center of gravity of the rack and facilitates assembly/maintenance.</p><p>Middle Layer (Compute &amp; Security):</p><p>Server blocks (Dell PowerEdge, Cisco UCS, etc.) and firewalls (Cisco ASA, Fortigate, etc.) are located in the middle layers (10U – 30U).</p><p>Top Layer and Ports (ToR / Patch Panels):</p><p>Fiber/copper patch panels (fiber patch panel, cable organizer) are generally located at the top of the cabinet (38U – 42U) to ensure an organized distribution of fiber and copper terminations. Top-of-Rack (ToR) switches can also be moved to higher levels for easier access.</p><p>2. Power (PDU) and Cabling Architecture</p><p>PDU (Power Distribution Unit) Placement: As shown in the image, power distribution units (PDUs) are placed within the cabinet at specific U-shaped values ​​or vertically on the rear/side profiles. Devices with dual power supplies (redundant PSUs) (such as Cisco Nexus, Huawei, Fortinet, etc.) require each power input to be connected to different PDUs or different phases to ensure power continuity.</p><p>Cable Organizers: Placing a 1U/2U cable organizer between each switch or patch panel block prevents cable clutter (spaghetti wiring) and does not obstruct airflow.</p><p>3. Operational Benefits of Using MS Visio and Vector Diagrams</p><p>These diagrams, prepared in MS Visio or PDF format during the planning phase, serve as a “Single Source of Truth” for field and operations teams:</p><p>Clear U-Rank Tracking (RU Tracking): Each device is clearly labeled with arrows indicating exactly which U-range it occupies (e.g., VIPRION Chassis between U1-U6, Cisco Nexus between U21-U22).</p><p>Capacity Planning: Empty spaces, such as CABINET-D in the image, or empty spaces in the upper parts of CABINET-C (U28-U42), provide clear reservation space for future projects and equipment additions.</p><p>Convenience for Field Teams: When field technicians are sent to remotely managed data centers or data centers in different locations, the instruction “Cisco ASA located in U35 in CABINET-A” enables error-free physical intervention.</p><p>💡Summary and Best Practice Recommendations</p><ol><li>Labeling Standards: Device names shown in the diagram, physical labels on the devices, and hostnames must be exactly the same.</li></ol><p>2. Hot/Cold Aisle Design: The air intake and exhaust directions of the devices must be considered in the cabinet layout.</p><p>3. Dynamic Documentation: Every physical change made in the field (the location of a patch cable or the addition of a new 1U device) must be immediately recorded in the Visio/Cabinet plan file.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14e7659f8b7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Unmissable Opportunity: Cisco SDSI (300–745) Training]]></title>
            <link>https://medium.com/@ysakturk/an-unmissable-opportunity-cisco-sdsi-300-745-training-5c47d8ecc685?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c47d8ecc685</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 09:48:09 GMT</pubDate>
            <atom:updated>2026-06-08T09:48:09.574Z</atom:updated>
            <content:encoded><![CDATA[<p>For Turkish: <a href="https://ysakturk.com/blog-ve-anketler/f/ka%C3%A7%C4%B1r%C4%B1lmayacak-f%C4%B1rsat-cisco-sdsi-300-745-e%C4%9Fitimi">https://ysakturk.com/blog-ve-anketler/f/ka%C3%A7%C4%B1r%C4%B1lmayacak-f%C4%B1rsat-cisco-sdsi-300-745-e%C4%9Fitimi</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8q4854AyGnqZzruMpR7OA.png" /></figure><p>Unmissable Opportunity: Cisco SDSI (300–745) Training Free for a Limited Time! (Includes 41 CE Credits) Cisco has once again released a free CE Credit training program. This program offers the chance to earn a total of 41 credits. All you have to do is log in to <a href="http://www.u.cisco.com/">www.u.cisco.com</a> with your Cisco account information and complete these two trainings under the “Learning Paths” tab…</p><p>I have great news for those who want to take their careers in cybersecurity and network infrastructure design to the next level. Cisco’s Designing Cisco Security Infrastructure (SDSI) training package, one of its most prestigious specialization and certification preparation pathways, is completely FREE until July 13, 2026. Furthermore, this training provides a full 41 Continuing Education (CE) credits for professionals who want to recertify their existing Cisco certifications.</p><p>Key Details About the Training<br>Exam Preparation: This learning path ensures you are fully prepared for the current 300–745 SDSI v1.0 exam.<br>Titles to be Earned: Upon successful completion of the exam, you will be eligible to receive the Cisco Certified Specialist — Designing Cisco Security Infrastructure certification and will also have completed the concentration exam requirement for CCNP Security certification.<br>Content Intensity: This rich resource, totaling 41 hours and 2 minutes, consists of 23 different courses and 12 assessment tests.<br>Level: Intermediate<br>Current Status: Updated according to the February 2026 curriculum.</p><p>🛠️ What Will You Learn in This Training?<br>The SDSI learning path covers the most critical foundations of modern cybersecurity, such as secure infrastructures, applications, risk management, incident analysis, artificial intelligence (AI), automation, and DevSecOps. The core competencies you will gain upon completion of this training include:</p><p>Infrastructure Security Concepts: Analyzing fundamental concepts for designing, establishing, and maintaining secure architectural designs.<br>Layered Defense: Properly implementing security layers and core technologies to build strong and resilient defense mechanisms.<br>Regulation and Compliance: Integrating cybersecurity design principles and legal frameworks into infrastructure to comply with business and legal requirements.<br>Advanced Threat Management: Deploying and managing detection, response, and access control tools to protect networks, endpoints, and cloud environments.<br>Artificial Intelligence and Automation: Optimizing security strategies against evolving threats, modern enterprise needs, and technological advancements.</p><p>When is the Deadline?<br>To take advantage of this opportunity for free, you need to complete the training by July 13, 2026 (3:00 PM Pacific Time / 6:00 PM Eastern Time).</p><p>I strongly recommend that you utilize this time to both take a giant step towards CCNP Security and expand your cybersecurity architecture vision with AI and DevSecOps integrations.</p><p>Stay tuned to my blog to not miss out on such unmissable opportunities and technical reviews from the world of network management and cybersecurity!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c47d8ecc685" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cisco (200–301 CCNA) v2.0 (New Curriculum Announcement)]]></title>
            <link>https://medium.com/@ysakturk/cisco-200-301-ccna-v2-0-new-curriculum-announcement-fa4ffab62b23?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa4ffab62b23</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Fri, 05 Jun 2026 07:48:51 GMT</pubDate>
            <atom:updated>2026-06-05T07:48:51.182Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HeH1-mGOkgg28I5ACN6gKA.png" /></figure><p>Türkçe içerik için: <a href="https://ysakturk.com/blog-ve-anketler/f/cisco-200-301-ccna-v20-yeni-m%C3%BCfredat-duyurusu">https://ysakturk.com/blog-ve-anketler/f/cisco-200-301-ccna-v20-yeni-m%C3%BCfredat-duyurusu</a></p><p>Cisco has announced a significant content update for CCNA 200–301 v2.0. The deadline for the current v1.1 exam is February 2, 2027, while the first exam date for v2.0 appears to be February 3, 2027. The exam code remains 200–301 CCNA, and the duration remains 120 minutes.</p><p>The biggest change: CCNA is becoming more focused on “operations and troubleshooting.” The old v1.1 blueprint covered these six topics:</p><p>Network Fundamentals: 20%</p><p>Network Access: 20%</p><p>IP Connectivity: 25%</p><p>IP Services: 10%</p><p>Security Fundamentals: 15%</p><p>Automation and Programmability: 10%</p><p>The new v2.0 version has been reduced to 5 sections:</p><p>Network Infrastructure and Connectivity: 25%</p><p>Switching and Network Access: 25%</p><p>IP Routing: 20%</p><p>Network Services and Security: 20%</p><p>AI, Network Operations and Management: 10%</p><p>Cisco’s v2.0 announcement states that the exam now verifies knowledge of IP routing, switching/network access, services/security, infrastructure/connectivity, AI, and network operations/management; it also mentions that evaluating agentic AI and digital network assistant outputs may be included in the exam scope.</p><p>1) Network Fundamentals has become Network Infrastructure and Connectivity. This section has moved away from a more theoretical “what is a network?” approach and focused more on connectivity and troubleshooting. New topics clearly include:</p><p>Copper/fiber cable problems: collision, error, duplex mismatch, speed mismatch, distance, signal level, pinout, cable type.</p><p>Troubleshooting IPv4 addressing/subnetting errors.</p><p>Troubleshooting IPv6 addressing, prefix sizing, EUI-64, etc.</p><p>Wired/wireless client connectivity troubleshooting.</p><p>DHCPv4 client/server/relay troubleshooting.</p><p>Hypervisor, VM, and container concepts.</p><p>In short, v2.0 goes beyond just “IPv4 subnetting knowledge”; it includes a more field-oriented approach, such as why a client with an incorrect IP address cannot access the network, whether the DHCP relay is working, or whether there is a fiber signal/cable problem.</p><p>2) The switching side has grown and become more practical. Switching and Network Access now account for 25%. Here, classic CCNA topics like VLAN, trunk, SVI, LACP/EtherChannel continue, but with more configuration, validation, and troubleshooting language. Specifically, the new blueprint includes:</p><p>Switch-to-switch and switch-to-router connection configuration.</p><p>L2/L3 interface, 802.1Q trunk, LACP port-channel/EtherChannel, SVI.</p><p>Edge host connections: PC, printer, IoT, AP, IP phone, virtual host, network appliance.</p><p>Network documentation validation with CDP/LLDP.</p><p>L2/L3 troubleshooting with show, show logs, ping, extended ping, traceroute, and packet capture outputs.</p><p>Rapid PVST+, root bridge, root port, PortFast, root guard, loop guard, BPDU guard.</p><p>In short, in CCNA v2.0, “reading output and finding the problem” is as important as “knowing the command” on the switch side.</p><p>3) IP Connectivity became IP Routing, reducing the percentage from 25% to 20%. Routing is still very important, but its weighting has decreased slightly: 25% → 20%. The scope includes:</p><p>Routing table interpretation: next-hop, prefix/mask, administrative distance, metric, default route.</p><p>IPv4/IPv6 static route troubleshooting.</p><p>Default route, network route, host route, floating static.</p><p>Single-area OSPFv2 and OSPFv3 configuration.</p><p>OSPF neighbor adjacency, point-to-point, broadcast, DR/BDR, router-id.</p><p>HSRP and VRRP operational status interpretation.</p><p>Notably: OSPF is present, but it doesn’t go as far as CCNP; authentication is excluded. Static routing and routing table reading are handled more with a troubleshooting approach.</p><p>4) IP Services + Security Fundamentals merged. In the old v1.1, IP Services were 10% and Security Fundamentals were 15%. In the new v2.0, these are combined under Network Services and Security, totaling 20%. New scope includes:</p><p>TACACS+/RADIUS as a local username and AAA client.</p><p>Secure file transfer with SFTP/SCP.</p><p>NAT/PAT configuration.</p><p>DNS record troubleshooting: A, AAAA, CNAME, MX, NS, PTR.</p><p>IPsec remote access and site-to-site VPN concepts.</p><p>IPv4 ACLs: standard, extended, numbered, named.</p><p>L2 security: DHCP snooping, Dynamic ARP Inspection, storm control, RA guard, port security.</p><p>There’s a nice change in this section: security is no longer a separate “final section,” but integrated with operational services. For example, DNS, NAT, AAA, ACLs, and L2 security are considered together.</p><p>5) The Automation section has changed: AI + Network Operations have been added. In the old v1.1, Automation and Programmability accounted for 10%. In the new v2.0, this has been replaced by AI, Network Operations, and Management, each accounting for 10%. New topics include:</p><p>The role of Agentic AI within network operations.</p><p>Choosing the right prompt for a Generative AI system.</p><p>Evaluating components within a prompt such as data classification, output format, persona, and instructions.</p><p>Device-based, cloud-based, controller-based, automation-based, and infrastructure-as-code management approaches.</p><p>The function of SNMP within network operations.</p><p>Executing commands with configuration management mechanisms like Ansible.</p><p>Interpreting syslog message content, severity level, and facility.</p><p>This is important: CCNA is no longer asking superficially “What is AI?”, but rather focusing on whether you can use AI output in network operations, validate the recommendation, and interpret operational tools like syslog/SNMP/Ansible.</p><p>From my perspective as an IP/MPLS operations expert, the new CCNA makes more sense. Previously, some topics seemed like rote memorization; now, the focus is more on skills like AAA, ACL, DHCP snooping, DAI, port security, and RA guard, which are more naturally integrated with network services. Topics like Ansible, SNMP, syslog, AI assistant recommendations, and prompt selection are now expected even from entry-level network engineers.</p><p>What should someone currently studying for CCNA do? If you’re taking the exam before February 3, 2027, it makes sense to continue with v1.1, as the final exam date for v1.1 is February 2, 2027. Someone just starting out but planning to take the exam in 2027 should prepare according to the v2.0 blueprint.</p><p>In my opinion, the priority of the course should be:</p><p>Subnetting, routing table, static route, OSPF.</p><p>VLAN, trunk, SVI, EtherChannel, STP.</p><p>DHCP, DNS, NAT, ACL, AAA.</p><p>Interface/cable/client connectivity troubleshooting.</p><p>Syslog, SNMP, Ansible fundamentals.</p><p>AI/prompt/agent AI concepts.</p><p>In short: CCNA v2.0 has become less rote memorization and more of a real network operation and troubleshooting exam.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa4ffab62b23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ITU GSR-26 ANKARA]]></title>
            <link>https://medium.com/@ysakturk/itu-gsr-26-ankara-3e0487689d82?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e0487689d82</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Sat, 09 May 2026 19:38:53 GMT</pubDate>
            <atom:updated>2026-05-09T19:38:53.378Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.youtube.com/watch?v=kOsQHxjSwB8">https://www.youtube.com/watch?v=kOsQHxjSwB8</a></p><p><a href="https://ysakturk.com/blog-ve-anketler/f/itu-gsr-26-ankara">https://ysakturk.com/blog-ve-anketler/f/itu-gsr-26-ankara</a></p><p>Uluslararası Telekomünikasyon Birliği (<strong>ITU</strong> — International Telecommunication Union), bilgi ve iletişim teknolojileri (BİT) alanında Birleşmiş Milletler’in uzmanlaşmış bir ihtisas kuruluşudur. 1865 yılında kurulan ITU, dünyanın en eski uluslararası kuruluşlarından biri olma özelliğini taşır. Cenevre merkezli bu organizasyon, küresel iletişim ağlarının ve hizmetlerinin geliştirilmesi, standartlaştırılması ve koordine edilmesi için temel bir platform görevi görür.</p><h3>ITU’nun Temel Görev Alanları</h3><p>ITU faaliyetlerini üç ana sektör üzerinden yürütür:</p><h3>1. Radyokomünikasyon (ITU-R)</h3><p>Küresel radyo frekans spektrumunun ve uydu yörüngelerinin yönetimini sağlar. Bu sayede kablosuz teknolojilerin (radyo, televizyon, uydu, Wi-Fi, 4G/5G vb.) birbirine karışmadan çalışması mümkün olur.</p><h3>2. Standardizasyon (ITU-T)</h3><p>Teknik standartların belirlendiği alandır. İnternet protokollerinden ses ve video kodlama standartlarına (örneğin JPEG veya H.264 gibi) kadar pek çok teknolojik altyapı burada kararlaştırılır. Bu sayede farklı ülkelerde üretilen cihazlar birbiriyle uyumlu çalışabilir.</p><h3>3. Kalkınma (ITU-D)</h3><p>Dijital uçurumu kapatmayı hedefler. Gelişmekte olan ülkelerde BİT altyapısının yaygınlaştırılması, siber güvenliğin artırılması ve dijital okuryazarlığın desteklenmesi için projeler üretir.</p><h3>ITU Neden Önemlidir?</h3><ul><li><strong>Küresel Bağlantı:</strong> Telefonunuzla dünyanın öbür ucundaki birini arayabiliyorsanız veya internete kesintisiz erişebiliyorsanız, bu büyük ölçüde ITU’nun belirlediği standartlar ve frekans düzenlemeleri sayesindedir.</li><li><strong>Hükümet ve Özel Sektör İş Birliği:</strong> Diğer birçok BM kuruluşunun aksine ITU, hem devletleri hem de özel sektör temsilcilerini (teknoloji devleri, operatörler, üniversiteler) bir araya getiren hibrit bir yapıya sahiptir.</li><li><strong>Geleceğin Teknolojileri:</strong> Yapay zeka, 6G, akıllı şehirler ve nesnelerin interneti (IoT) gibi geleceğe yön veren alanlarda global yol haritalarını belirler.</li></ul><p><strong>Not:</strong> Türkiye, ITU’nun kurucu üyelerinden biridir ve birliğin karar alma süreçlerinde (Konsey üyeliği gibi) aktif olarak rol almaktadır.</p><p>Küresel Düzenleyiciler Sempozyumu (<strong>GSR</strong>), Uluslararası Telekomünikasyon Birliği (ITU) tarafından her yıl düzenlenen, dünyanın en prestijli telekomünikasyon ve dijital düzenleme etkinliğidir. <strong>GSR-26</strong>, dünya genelindeki bilgi ve iletişim teknolojileri (BİT) düzenleyicilerini, bakanları ve sektör liderlerini bir araya getirerek dijital geleceğin kurallarını belirlemeyi amaçlar.</p><h3>GSR’ın Temel Amacı Nedir?</h3><p>Bu sempozyumun ana amacı, hızla değişen teknoloji dünyasında yasal boşlukları doldurmak ve ülkeler arasında uyumlu bir düzenleme çerçevesi oluşturmaktır. Temel odak noktaları şunlardır:</p><ul><li><strong>Deneyim Paylaşımı:</strong> Farklı ülkelerdeki düzenleyici kurumların (Türkiye’deki BTK gibi) karşılaştıkları sorunları ve çözüm yöntemlerini birbirleriyle paylaşması sağlanır.</li><li><strong>En İyi Uygulama Esasları (Best Practice Guidelines):</strong> Her yıl sempozyum sonunda, dijital dönüşüm için yol gösterici olan ve üye ülkeler tarafından kabul edilen bir rehber yayımlanır.</li><li><strong>Dijital Uçurumu Kapatmak:</strong> İnternet erişimi kısıtlı olan bölgeler için yatırım modelleri ve teşvik edici düzenlemeler geliştirilir.</li></ul><h3>GSR-26&#39;da Öne Çıkan Konular Neler Olabilir?</h3><p>2026 yılındaki sempozyumun, gelişen teknolojilerin etkisiyle şu kritik başlıklara odaklanması beklenmektedir:</p><h3>1. Yapay Zeka ve Etik Düzenlemeler</h3><p>Üretken yapay zekanın (GenAI) hızla yayılmasıyla birlikte, verilerin korunması, etik standartlar ve algoritmik hesap verebilirlik konularında küresel standartlar tartışılacaktır.</p><h3>2. 5G ve 6G Yol Haritası</h3><p>Yüksek hızlı bağlantı altyapılarının dünya geneline yayılması ve 6G teknolojisi için gerekli spektrum yönetimi politikaları ele alınacaktır.</p><h3>3. Uzay ve Uydu İletişimi</h3><p>Alçak yörünge uydularının (LEO) artan sayısı nedeniyle, uzay tabanlı internet hizmetlerinin nasıl düzenleneceği ve bu teknolojilerin kırsal alanlara nasıl ulaştırılacağı önemli bir gündem maddesidir.</p><h3>4. Siber Güvenlik ve Dayanıklılık</h3><p>Dijital altyapıların saldırılara karşı korunması ve ülkeler arası siber güvenlik iş birliği protokollerinin güçlendirilmesi üzerinde durulacaktır.</p><h3>Kimler Katılır?</h3><p>GSR, sadece hükümet temsilcilerine açık bir etkinlik değildir; kapsayıcı bir yapıya sahiptir:</p><ul><li><strong>Ulusal Düzenleyici Kurumlar:</strong> Telekomünikasyon ve bilişim otoritelerinin başkanları.</li><li><strong>Bakanlıklar:</strong> Haberleşme ve teknoloji bakanları.</li><li><strong>Sektör Devleri:</strong> Operatörler, ekipman üreticileri ve büyük teknoloji şirketleri.</li><li><strong>Akademisyenler ve STK’lar:</strong> Dijital haklar ve teknoloji politikaları üzerine çalışan uzmanlar.</li></ul><p><strong>Özetle GSR-26</strong>, dijital dünyayı yönetenlerin “ortak dili” konuştuğu ve geleceğin bağlantılı dünyasının anayasasını tasarladığı en üst düzey platformdur.</p><p>Dijital geleceğin en kritik, en önemli platformlardan biri olan “Uluslararası Telekomünikasyon Birliği (ITU) Küresel Düzenleyiciler Sempozyumu — ITU Global Symposium for Regulators (GSR-26) etkinliği, Mayıs 2026 da Ankara’ da Bilgi Teknolojileri ve İletişim Kurumu’ nun ev sahipliğinde gerçekleştirilecektir. Organizasyonun detayları ve katılım süreçleri hakkında resmi bilgilere aşağıdaki bağlantılar üzerinden ulaşabilirsiniz:</p><p>ITU Link: <a href="https://www.itu.int/itu-d/meetings/gsr-26/">https://www.itu.int/itu-d/meetings/gsr-26/</a></p><p>GSR Link: <a href="https://www.gsr26.tr/">https://www.gsr26.tr/</a></p><p>Tanıtım Videosu: <a href="https://www.youtube.com/watch?v=kOsQHxjSwB8">https://www.youtube.com/watch?v=kOsQHxjSwB8</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e0487689d82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Firewall Admin / Network Admin]]></title>
            <link>https://medium.com/@ysakturk/firewall-admin-network-admin-0d8dfd297a06?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d8dfd297a06</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Thu, 16 Apr 2026 07:06:01 GMT</pubDate>
            <atom:updated>2026-04-16T07:06:01.418Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Pr2KVMEVy_l5bISiuWmmA.png" /></figure><p>Why do firewall administrators and network administrators sometimes disagree? This classic conflict is actually a natural clash stemming from both groups striving to do their jobs very well. Network administrators want traffic to flow, while firewall administrators want to control (and stop) traffic if necessary. Here are the fundamental reasons for this never-ending “cold war” between these two teams:</p><ol><li>Availability vs. Security (Speed ​​vs. Obstacle)<br>Network Administrator: Prioritizes connectivity and performance. Wants the packet to reach point B from point A with the lowest possible latency. Sees every new rule as a potential source of slowdown or disruption.<br>Firewall Administrator: Prioritizes security and isolation. For them, every open port is a risk, every uncontrolled traffic is a threat. Operates on the principle of “Close everything first, then only open what’s necessary” (Default Deny).</li></ol><p>2. The “Firewall is Always to Blame” Bias<br>When an application fails to work on the network or packet loss occurs, the blame usually falls first on the firewall team. The network administrator says: “The ping goes through, but the application doesn’t open, it must be the firewall dropping it.”<br>The firewall administrator says: “I checked the logs, there isn’t even a single incoming packet; the problem is in your routing settings.” This cycle leads to significant time loss and mutual blame between teams. 3. Change Management and Speed<br>Defining a VLAN or opening a port on the network side is usually a quick process.<br>Writing a rule on the firewall side requires security policy compliance checks, logging analysis, and risk assessment. While the network team thinks, “It’s just opening a port,” the security team considers the myriad threats behind that port.</p><p>3. Difference in Technical Perspective<br>The network engineer focuses on OSI Layers 2 and 3: MAC addresses, IPs, routing tables, and bandwidth are their world.<br>The firewall engineer focuses on OSI Layers 4 and 7: They deal with ports, protocols, application signatures, and data content. Although they are looking at the same cable, they speak different languages.</p><p>How to Find Common Ground?<br>The way to end this conflict is usually through visibility:<br>Centralized Logging: Transparent log systems visible to both sides provide a quick answer to the question “where did the packet fall?”.<br>Automation: Automating standard rule creation processes reduces human-factor disputes.<br>Clear Topology: An up-to-date network diagram immediately reveals whether the problem is physical or rule-related. In short; one is the engineer building the road, the other is the passport control officer on the road. As long as both are doing their jobs, this sweet but fierce competition will continue.</p><p>Actually, my advice is that there shouldn’t be such a distinction. Every firewall administrator should have network knowledge, and every network administrator should have firewall knowledge. Although it is necessary to specialize in one area, it is important to have knowledge and ideas about other areas as well. This is crucial for a collaborative project in the future, ensuring mutual harmony, avoiding blame, and a productive working process.</p><p>If I were to ask you whether you think this dispute is more of a communication problem than a technical one, what would your comments be?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d8dfd297a06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Network Engineer’s Visio Proficiency (Ağ Mühendisinin Visio Yetkinliği)]]></title>
            <link>https://medium.com/@ysakturk/network-engineers-visio-proficiency-a%C4%9F-m%C3%BChendisinin-visio-yetkinli%C4%9Fi-d3879b0d96fd?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3879b0d96fd</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 12:41:22 GMT</pubDate>
            <atom:updated>2026-04-01T12:41:22.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q57hmT6hCFkBue4UxtqDIg.jpeg" /></figure><p><strong>For Turkish: </strong><a href="https://ysakturk.com/blog-ve-anketler/f/a%C4%9F-m%C3%BChendisinin-visio-yetkinli%C4%9Fi"><strong>https://ysakturk.com/blog-ve-anketler/f/a%C4%9F-m%C3%BChendisinin-visio-yetkinli%C4%9Fi</strong></a></p><p>Hello everyone. In this article, I will discuss some important points. In this industry, there are many friends, colleagues, mentors, and a generation following in our footsteps. It’s crucial that those who lead the way set an example for those who follow…</p><p>Let’s not forget that we also have many competitors in the market. Everyone now knows about STP or ACL, or OSPF/BGP/IS-IS in some way, or even if they don’t, they can easily learn about them through readily available resources.</p><p>Those of us working in networking know that our field consists of many sub-branches: Wireless Network, Wired Network, GSM, Transmission, etc. Of course, these areas can also be further divided into operations, planning, or installation. My idea is to specialize in one of these three, but gain experience in each. But most importantly, as a respected older colleague always told us, is troubleshooting… Of course, to do that, you need to know things, and to know things, you need to read a lot… Reading? Yes, reading… By the way, that colleague was and still is a very right person. You can’t succeed without reading, folks.</p><p>I’ve shared an image here. Although it’s not very clear due to the camera, the title is “Internetworking with TCP/IP Principles, Protocols, and Architectures,” and the author is Douglas E. Comer.</p><p>That famous yellow book… Most of my colleagues know this book. It’s an old book, but especially in my circle, everyone knows it. :)</p><p>Although I started with a different introduction under the title “Visio,” I’ll gradually connect the topic…</p><p>The setup, operation, and planning I mentioned above… If we simplify this a bit and consider planning and setup as one, then setup and operation… One team installs and activates, while the other resolves the troubleshooting issues of previously activated systems. Don’t you think these two teams are interconnected? Shouldn’t they be synchronized and constantly exchanging information? Don’t you think the installation team should share everything clearly, understandably, and concisely when handing over the project to the operations team? What could they share? Planning processes, inventory information of installed devices, topology information (both logical and physical), IP/VLAN information, topology and cabinet design information if it’s a data center structure, access information, contact information for those experiencing problems, etc.</p><p>In my early years in the industry, while working on projects, I encountered situations where the setup process was completed without any information being shared, or where the setup remained only in the mind of the colleague who did the work, and they never formalized it. These were difficult processes… Why? Because setting up a system is easy, yes, since the entire design is up to you, you can route things wherever you want, etc., but understanding an existing, established system is far from easy. A small, momentary mistake can cause the entire system to collapse.</p><p>One day, while I was working on various projects as a Junior, I met a Principal-level colleague and had the opportunity to work with him for a while. His style was very interesting. Before each project, he would do thorough preparations, draw topologies, create and disassemble, and work with screens that had some really strange shapes. After that, I naturally became interested and did some research, and I learned that there was an application called Visio. While I was trying to create things with the existing Shapes in it, I learned one day that most manufacturers were already sharing data in a way that allowed them to transfer most of their IT products to this environment. Oh my God, I said… :) and I started…</p><p>The first project involved 10 switches. Then 15, 50, 100… and suddenly almost 2000 switches in a hub and spoke (Datacenter — Branch Office) configuration. Because only one type of product was used, there was a lot of cable clutter, but it resulted in a useful document. Those who came after me might have thanked me for it…</p><p>Then came other projects… Small/medium-sized datacenter architectures, edge location deployments, etc. At one point, purely out of curiosity, I even extracted the topologies of previously installed systems and transferred them to the Visio environment. Of course, there are many projects, but since they all contain private data, I can’t share them all. But I will share a randomly prepared cabinet visualization with you…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUQlyYbSXYOD4j6HVRCmtg.png" /></figure><p>Some of you might be wondering what’s in the image below… What isn’t there, folks? Palo Alto firewalls, Huawei switches or access controllers, HP or Extreme switches, H3C, Fortigate, Cisco Nexus or ASRs… Mikrotik, Mikrotik…</p><p>Each product family has visuals available online in Visio format. Don’t use PNG images, I advise against it, they distort when zoomed in… (I’ve tried it many times in the beginning…)</p><p>There are cabinets, folks. You can cover the empty U-shaped areas with covers… I chose two 42U cabinets…</p><p>You can design the cabinet layout for an entire datacenter like this, folks. Sometimes it takes time, but let’s just say you’re happy when it’s finished.</p><p>Our operations colleague, or perhaps another person X, who has this image, could simply review this image or documents without ever going to the data center. They wouldn’t need to go there anymore. This is already there. Actually, that place is also here…</p><p>I’ll end my remarks here. For questions and comments, please contact me via <a href="http://www.ysakturk.com/">www.ysakturk.com</a>.</p><p>Thank you.</p><p>Yavuz Selim Aktürk — Network Specialist</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3879b0d96fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ROUTING INFORMATION PROTOCOL]]></title>
            <link>https://medium.com/@ysakturk/routing-information-protocol-83d367596ccd?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/83d367596ccd</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 09:45:17 GMT</pubDate>
            <atom:updated>2026-03-30T09:45:17.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01dzq91GeCd3ln0hrAwucg.png" /></figure><p>ROUTING INFORMATION PROTOCOL</p><p>RIP is a protocol that works with the distance vector algorithm and uses the Bellman-Ford algorithm to calculate routing. RIP is listed as Administrative Distance (AD) 120 in the router’s device table. A router using the RIP protocol only considers the number of devices it passes through, i.e., the Hop Count, when choosing the best path, and the maximum hop count is 15. This means that a router can pass through a maximum of 15 routers. If this number is exceeded, i.e., when the 16th hop is reached, a Destination Unreachable warning is received.</p><p>Routers defined with RIP transmit the networks defined within them to neighboring routers every 30 seconds. It is important to note that the interface to which a network defined with RIP is connected is also selected as the interface to which routing updates will be sent.</p><p>RIP is divided into two versions: version 1 and version 2.</p><p>RIP Version 1<br>- Works with classful logic.<br>- Does not carry subnet mask information during update operations.<br>- Announces updates via the 255.255.255.255 broadcast.<br>- Supports Split Horizon and Split Horizon with poison reverse features.<br>- No authentication is required when using RIPv1.</p><p>RIP Version 2</p><ul><li>It is a classless protocol.<br>- Carries subnet mask information during update operations. Subnetting can be done on the network.<br>- Announces periodic updates via the 224.0.0.9 multicast broadcast.<br>- Supports VLSM (Variable Length Subnet Mask).<br>- A router using RIPv1 accepts RIPv2 updates. However, a router using RIPv2 only accepts RIPv2 updates. — Auto Summarization is available and is enabled by default.</li></ul><p>What is Auto Summarization? If subnetting has been performed on a network structure, the undivided network information is transmitted to the routers as summary information, ignoring the subnetting, and functions as if it were classfull. If this command is disabled, RIPv2 shares subnet mask information for all subnets with other routers.</p><p>Split Horizon<br>If a router learns its directly connected network from another router, it discards the learned information. It also ensures that when the router detects any changes on the network, it broadcasts these changes from interfaces other than the one it learned about. Thus, routers only broadcast changes in one direction. When Split Horizon is disabled, routers will update all networks in their routing tables and all networks they have learned about from any of their interfaces.</p><p>Route Poisoning<br>This is a type of routing where the hop count value is set to 16 in the router’s routing table, ensuring that the destination address is unreachable among the routers.</p><p>Triggered Updates<br>These are updates sent by routers when a change occurs in the routing table. As soon as the topology changes, the router detects this and informs its neighboring routers of the change without waiting for the periodic update period. Triggered updates work in conjunction with route poisoning.</p><p>Update Timer<br>The default timing for routing information exchanged by routers running RIP is 30 seconds. Routers periodically change their routing tables using the Update Timer.</p><p>Invalid Timer<br>If no update arrives within 180 seconds, the destination router considers it invalid. In this scenario, the destination router’s signal skip counts as 16 for this router.</p><p>Hold Down Timer<br>This is the time the router waits for the neighboring router to respond. If the router fails to respond within a certain time, it is declared dead. The default is 180 seconds.</p><p>Flush Time<br>The default is 60 seconds. This timer starts after the route is declared invalid and will end after 60 seconds, so the total time will be 180 + 60 = 240 seconds.</p><p>Note that all these times can be adjusted. To change the timers, use this command:<br>R1(config-router)# timers basic<br>R1(config-router)# timers basic 20 80 80 90</p><p>IGRP (INTERIOR GATEWAY ROUTING PROTOCOL)<br>IGRP is a “Distance Vector Protocol” developed by Cisco. Because it was developed by Cisco, devices using this protocol must be Cisco devices. Essentially, it was developed to address some shortcomings in RIPv1 and to provide Cisco with its own protocol. Like RIP, IGRP is a classful protocol.</p><p>The maximum possible “hop count” in IGRP is 255, a significant improvement over RIP, which only has a hop count of 15. However, hop count is not the only metric used for routing. Unlike RIP, IGRP also uses line latency, bandwidth, reliability, and load status as metrics.</p><p>IGRP features are as follows:</p><p>Update Timer: Ensures that update packets are sent to neighboring routers every 90 seconds via the broadcast address 255.255.255.255.<br>Invalid Timer: For a router that does not receive update packets every 90 seconds, this period is 270 seconds. In other words, if no update information is received during this time, the routing is considered invalid.<br>Holddown Timer: After the 270-second Invalid Timer period, the routing information on the router continues to be held for an additional 280 seconds.<br>Flush Timer: After a total of 90 + 270 + 280 = 640 seconds, the relevant routing information is deleted from the routing table.</p><p>NOTE: The biggest difference between RIP and IGRP is the Autonomous System (AS) number. In IGRP, only routers with the same AS number can communicate.</p><p>EIGRP (Enhanced Interior Gateway Routing Protocol)<br>Developed by Cisco and used by them for a long time before being made available to other companies, it is a dynamic routing protocol that performs routing by calculating metrics such as bandwidth, delay, load, and reliability.</p><p>When the protocol runs, routers establish neighbor relationships by sending “Hello” packets from their interfaces (ports) and create neighbor tables. A hello packet is sent to a neighboring router every 5 seconds, and if no response is received within 15 seconds, the neighbor relationship is deleted. The established neighbor relationships are confirmed with “Acknowledgement” packets. A query packet checks for any changes in the network, and new tables are created based on the incoming reply packet. All these processes are carried out using RTP (Reliable Transport Protocol).</p><p>When creating the routing table, one primary route and one backup route are written. This allows for a quick switch to the backup route if there is a problem with the primary route. Additionally, when switching to a backup route, another backup route is calculated.</p><p>The metric calculation typically includes 5 parameters (K1: bandwidth, K2: load, K3: delay, K4: reliability, K5: MTU (Maximum Transmission Unit)).</p><p>Generally, K1 (Bandwidth) and K3 (delay) parameters are used. These parameters are defined by default in the metric calculation. Activating other parameters is not recommended unless absolutely necessary, because if the metric values ​​are not the same, adjacency may not be established between routers.</p><p>Metric Calculation (When BW and Delay are Included)</p><p>Metric = (Bandwidth + Delay) * 256</p><p>In EIGRP, routers do not establish neighboring relationships if the metric values ​​are not the same. Therefore, it is recommended not to deviate from the default settings.</p><p>Bandwidth: The lowest bandwidth between interfaces traversed from the source interface to the destination interface. (This refers to the bandwidth of the interfaces, not the network bandwidth.)</p><p>Delay: The sum of all delays across all interfaces traversed until reaching the destination network.</p><p>The `show ip protocols` command can be used to see which values ​​are taken into account in the metric calculation.</p><p>For Turkish document and video: <a href="https://ysakturk.com/rip-ve-eigrp">https://ysakturk.com/rip-ve-eigrp</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83d367596ccd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSPF (Open Shortest Path First)]]></title>
            <link>https://medium.com/@ysakturk/ospf-open-shortest-path-first-f42d1df1574d?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/f42d1df1574d</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Tue, 10 Mar 2026 11:04:36 GMT</pubDate>
            <atom:updated>2026-03-10T11:04:36.225Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_d5OVmiyJ2Zc3rHXKO25A.png" /></figure><p>For Turkish: <a href="https://ysakturk.com/ospf">https://ysakturk.com/ospf</a></p><p>OSPF, like IS-IS, is a link-state, or Interior Gateway Protocol. In this protocol, routers create a map of the entire topology and store it in the LSDB. SPF, like IS-IS, calculates the shortest path.</p><p>Both IS-IS and OSPF have the link-state term we mentioned. There’s also the distance-vector, which is used in other dynamic routing protocols. What do these do?</p><p>Distance Vector (like RIP): Works with the logic of “I will travel this many hops (steps) in this network.” Link State: Works with a logic that spreads information like “these are my links, these are the costs.”</p><p>In OSPF, routers:</p><p>Perform neighbor discovery.<br>Establish neighbor relationships after discovery.<br>Create an LSDB database and store all information there.</p><p>SPF runs and calculates the path.</p><p>Write the best routes to the routing table after the relevant calculations.</p><p>OSPF:</p><p>It is an open standard, meaning it operates on a multivendor model.<br>It has fast convergence capabilities (much faster than RIP).<br>It supports classless architecture, i.e., CIDR and VLSM.<br>It operates on an area model.<br>It has route summarization and filtering features (especially on the ABR and ASBR side).<br>It supports authentication.</p><p>OSPF is divided into two versions: v2 and v3. v2 is used for IPv4 and is covered by the RFC 2328 standard. v3 is used for IPv6. In v3, neighbor relationships can be established with link-local addresses.</p><p>What are OSPF Terms?<br>There are several important terms we need to know in OSPF. These are as follows:</p><p>1. Router ID</p><p>OSPF routers have a 32-bit ID that identifies them. (It appears in IPv4 format.) The loopback address can be defined as a router ID. It can be defined manually, but if no definition is made, the device automatically selects the IP address with the highest value as the router ID.<br>It must be unique within the OSPF domain.<br>Router IDs must absolutely not conflict. This prevents the formation of neighbors.</p><p>2. Area</p><p>The OSPF topology is divided into areas. Area0 is the backbone area. Other areas must also be directly or indirectly connected to the backbone area. The reason for the area logic is to reduce the LSDB database space on the devices, reduce the SPF load, and limit the LSA flood area.</p><p>3. LSDB (Link State Database)</p><p>This is the database area where routers store OSPF-related data. All routers within the same area must have the same LSDB. The routing table is created as a result of SPF, while the LSDB contains topology information.</p><p>Besides the terms mentioned above, there are OSPF packet types. There are a total of 5 basic packet types within OSPF. These might come to mind when you say “OSPF Type”:</p><p>1. Hello Packet</p><p>This packet type is used for neighbor discovery and maintaining existing neighbor relationships. It contains information such as Router ID, Area ID, Hello/Dead Time, network mask, authentication, DR/BDR, and neighbor list. The Hello packet checks if there are neighbors, if the parameters are compatible, or if the neighbor relationship continues.</p><p>2. DBD/DD (Database Description)</p><p>Carries LSDB summary headers. It carries information about which LSA types are available. It proceeds with the Master/Slave sequence number.</p><p>3. LSR (Link State Request)</p><p>This packet requests that a specific LSA type is missing.</p><p>4. LSU (Link State Update)</p><p>Carries LSA data. May contain information on multiple LSA types.</p><p>5. LSAck (Link State Acknowledgment)</p><p>Checkes and confirms LSAs received from the other side. Ensures flooding reliability.</p><p>Important 2 Notes…!</p><p>OSPF Neighbor: Means two routers that have recognized each other at the hello level.<br>OSPF Adjacency: Means two routers that have established a full relationship sufficient for LSDB synchronization.</p><p>In other words, not every neighbor has to be an adjacency. We need to pay attention to this, especially in broadcast networks, due to the DR/BDR logic.</p><p>Let’s examine OSPF Neighbor States…</p><p>Down: No hello packets have been received, i.e., the initial state.<br>Attempt (Especially NBMA): An attempt is made to send a unicast hello packet to the neighboring router. This occurs in NBMA networks. (Used during the Frame Relay era.)<br>Init: A hello packet is received from the neighboring router, but our router ID is not in the neighbor list in the other router’s hello packet. This means there is one-way communication.<br>2-Way: We see our router ID in the other side’s hello packet (two-way communication is established). In Broadcast/NBMA network structures, some neighbors may remain in this neighbor state because full ajdacency is only established with DR/BDR.<br>ExStart: DBD exchange begins. Master/Slave is determined. Sequence is initiated. (We may encounter the ExStart state due to MTU mismatch.)<br>Exchange: DBD packets are exchanged. LSA headers are compared.<br>Loading: Missing LSA packets are requested again with the help of LSR. They are obtained with LSU. Full: LSDB synchronization is achieved. Neighborhood is fully established.</p><p>OSPF Network Types (this section describes DR/BDR and hello timer behavior)<br>Broadcast (Ethernet)<br>Used for communication. (224.0.0.5 and 224.0.0.6)<br>DR/BDR selection is made.<br>Default hello/dead time is usually 10/40 seconds.<br>Non-Broadcast (NBMA)<br>In NBMA mode, OSPF cannot use Multicast (224.0.0.5). Therefore, you need to manually define the IP addresses of neighbors on the router.<br>The NBMA network type tries to behave like Ethernet. Therefore, a DR (Designated Router) and BDR (Backup Designated Router) selection is made.<br>Hello/dead time is 30/120 seconds.<br>Point-to-Point<br>This is the simplest and most efficient operating mode where two routers are directly connected to each other.</p><p>There is no DR/BDR selection.<br>In P2P mode, neighbors are found automatically. (224.0.0.5)<br>Hello/Dead is 10/40 seconds.<br>Point-to-Multipoint<br>Preferred in hub and spoke configurations.<br>No DR/BDR selection.<br>P2MP usually sends Hello packets over 224.0.0.5 (Multicast).<br>Hello/Dead is 30/120 seconds.<br>Point-to-Multipoint Non-Broadcast<br>As the name suggests, it has all the features of Point-to-Multipoint (P2MP) mode, but with one major difference: it is customized for environments without Multicast/Broadcast capability. Unlike standard P2MP, this mode cannot automatically send Hello packets (multicast).<br>No DR/BDR selection.<br>Routers cannot automatically find each other; you need to define each neighbor based on IP address using the neighbor command.<br>Hello/Dead is 30/120 seconds.</p><p>DR/BDR<br>In Broadcast/NBMA segments, if everyone establishes full adjacency with everyone else, scaling becomes poor.</p><p>For example, if there are 10 routers: The number of full mesh adjacencies increases significantly, and LSU flooding becomes complex. Therefore:</p><p>A DR (designated router) is selected.<br>A BDR (backup router) is selected.<br>The remaining routers become DROTHER.</p><p>DROTHER generally establishes full adjacency with DR/BDR and remains in a 2-way type configuration.</p><p>When selecting DR/BDR, some criteria must be considered. One of these is the OSPF interface priority value. The router with a higher value becomes the DR. If this value is equal in both routers, the DR with the higher Route ID is selected. Devices with a priority value of 0 are not included in the DR/BDR selection. After the DR selection is made, if a new router with a higher priority is added to the topology, the DR may not change automatically. The change may occur via reset/neighbor flap.</p><p>How to Calculate OSPF Metric (Cost)<br>OSPF metric = Cost. The most basic principle: The lower the cost, the more preferable the path.</p><p>Classic cost formula</p><p>Generally: Cost = Reference Bandwidth / Interface Bandwidth. For example, if the reference bandwidth is 100 Mbps:</p><p>10 Mbps =&gt; cost 10<br>100 Mbps =&gt; cost 1<br>1 Gbps =&gt; still 1 (problem!)</p><p>If the default reference bandwidth remains outdated, all 1G/10G/100G links may appear to have a cost of 1. This results in suboptimal routing. Therefore, the reference bandwidth is increased (vendor syntax is changed).</p><p>A manual cost value can also be given.</p><p>Interface-based IP OSPF cost X (depending on the vendor)<br>Frequently used for traffic engineering/design</p><p>OSPF Area Structure and Router Roles<br>Internal Router<br>This is a router where all interfaces are located within the same area.</p><p>Backbone Router<br>A router with at least one interface located within Area 0.</p><p>ABR (Area Border Router)<br>A router connected to multiple areas. (Usually one end is connected to Area 0, i.e., the backbone.) ABR carries routes between areas. It generates Type 3/4 summary LSAs. It can perform summarization.</p><p>ASBR (Autonomous System Boundary Router)<br>A router that takes a route prefix from a different location outside of OSPF and redistributes it within OSPF. For example, taking a network prefix like BGP/Static/Connected and including it in OSPF. A router can be both ABR and ASBR at the same time.</p><p>OSPF LSA TYPES<br>LSA = Link State Advertisement… LSAs are packets that carry OSPF topology information.</p><p>Type 1 — Router LSA<br>In OSPF, a Type 1 Router LSA is a basic information card created by each router in an OSPF area to describe itself and the connections it is directly connected to. A router announces “Who am I and which IPs are on which interfaces?” to the entire area with this LSA. It is only broadcast within the area where it was generated. It does not pass to other areas via an ABR (Area Border Router). If there are 10 routers in an OSPF structure, there are exactly 10 Type 1 LSAs in the LSDB (Link State Database) table of that area. These LSAs combine to form the skeleton of the area’s physical topology.</p><p>Type 2 — Network LSA<br>OSPF Type 2 Network LSA is an information packet generated by the DR (Designated Router) that manages traffic in Broadcast and NBMA networks. Type 1 LSAs identify routers, while Type 2 LSAs collectively declare who is connected to that network segment (e.g., a switch). They are only generated by Designated Routers (DRs). If a network doesn’t have a DR option (like Point-to-Point), there is no Type 2 LSA. It remains only within the Area (zone) where it was generated. It cannot cross the Area Border Router (ABR). Routers in an OSPF area first look at Type 1 LSAs to answer the question “Which router am I connected to?” when calculating the route. If they are connected via a “Transit Network,” they immediately check the relevant Type 2 LSA to learn the details of that network (who is there, what is the mask?). When these two LSA types are combined, a complete map of the area is created.</p><p>Type 3 — Summary LSA (Inter Area)<br>OSPF Type 3 Summary LSA is a packet used to transfer network information from one OSPF area to another. It is only generated by an Area Border Router (ABR). It spreads across areas. For example, it carries information from a network in Area 1 to Area 0, and from there to Area 2. It includes the IP address, subnet mask, and cost of reaching a specific network (subnet). The announced destination’s Network ID is the Network Address. All Type 3 LSAs must pass through Area 0 (Backbone). Summary information originating from Area 1 must first pass through Area 0 to reach Area 2. As a Network Engineer, when you type the `show ip ospf database` command, you will see the routers in your own area under Router Link States (Type 1), and the networks coming from other areas under Summary Net Link States (Type 3).</p><p>Type 4 — ASBR Summary LSA<br>OSPF Type 4 ASBR Summary LSA is a routing packet that describes the exact location of the ASBR (Autonomous System Boundary Router), which is the gateway for routes coming from the outside world (BGP, EIGRP, Static, etc.), in an OSPF area. While Type 5 LSAs (External Routes) are propagated throughout the network, Type 4 LSAs whisper to other areas how to reach the router that owns these routes. It is only generated by the ABR (Area Border Router). An ASBR cannot send a Type 1 LSA outside its own area. Routers in other areas would not know how to reach the Router ID (ASBR) that “advertises” an external route arriving with a Type 5. The ABR fills this gap with Type 4. If Type 4 LSA is not used, routers in other areas will see external routes (Type 5) but cannot add them to the routing table because they cannot resolve the “Forwarding Address” information. In other words, Type 4 ensures the validation of the “delivery address” of external routes.</p><p>Type 5 — AS External LSA<br>OSPF Type 5 AS External LSA represents network information coming entirely from outside the OSPF network (from another routing protocol or static routes). It is generated only by the ASBR (Autonomous System Boundary Router). It is propagated throughout the entire OSPF autonomous system (AS). Unlike Types 1, 2, and 3, this LSA penetrates area boundaries. Type 5 LSAs cannot enter special areas configured as “Stub” or “NSSA” (Not-So-Stubby Area). Two different cost calculation methods are used when external routes are transferred (redistributed) to OSPF: External Type 2 (E2) — Default: Cost is fixed. The cost defined in the ASBR (default 20) remains the same across the entire network. Internal routers do not add their own internal costs to this. External Type 1 (E1): The cost is variable. The initial cost given by the ASBR is added to the cost of each OSPF link the packet passes through. It is usually used to choose the best path when there is more than one ASBR.</p><p>We can summarize the mechanism here as follows:</p><p>Type 5: Says, “There is a network outside called 192.168.50.0/24, and I own it (ASBR).”<br>Type 4: (For routers in other areas) Says, “The ASBR that sent that Type 5 is located over there; you need to go through me to reach it.”</p><p>Type 6 — Group Membership LSA<br>OSPF Type 6 — Group Membership LSA is a special type of LSA that is part of the classic OSPF (IPv4) protocol but is almost never used in standard routing operations. It determines which routers or network segments multicast traffic will be forwarded to. In modern networks, PIM (Protocol Independent Multicast) is generally used to manage multicast traffic. MOSPF has lost its popularity because it creates performance issues in large-scale networks, and Type 6 LSAs have become “obsolete” information.</p><p>Type 7 — NSSA External LSA<br>OSPF Type 7 NSSA External LSA is a packet used within NSSA (Not-So-Stubby Area), which is a special area type of OSPF that we call “closed to the outside world but not really.” Normally, “Stub” areas do not accept external routes (Type 5). However, sometimes a router in these end areas needs to have a connection to the outside world (e.g., an internet exit or a static route). This is where Type 7 LSAs come in. They only propagate within the NSSA domain. They can never leave the domain (Area 0 or other areas) in this form.</p><p>You want to reduce the load on devices by making an area a “stub,” but you need to redistribute the outside world (EIGRP, BGP, Static) to OSPF via a router in that area.</p><p>Rule: Type 5 LSAs are forbidden from entering or being generated in stub areas.</p><p>Solution: The external route travels within the NSSA as a Type 7, “disguised.”</p><p>Since Type 7 LSAs cannot leave the NSSA, this information needs to reach the entire OSPF network. The ABR (Area Border Router) takes on this task: it receives the Type 7 LSA in the NSSA domain, converts it into a standard Type 5 External LSA, and distributes it to the entire OSPF autonomous system via the backbone (Area 0).</p><p>A Type 7 LSA is like a “passport.” When a route from the outside world enters the NSSA area, it receives this passport. When it reaches the Area Border (ABR), the passport is replaced with Type 5, a “universal identifier,” and becomes recognizable throughout the OSPF world.</p><p>Type 8 — External Attributes LSA<br>OSPF Type 8 — External Attributes LSA is an LSA type designed to carry BGP (Border Gateway Protocol) information over OSPF, but it is almost never used today.</p><p>Type 9/10/11 — Opaque LSA<br>Used for OSPF extensions (TE, GR, etc.)</p><p>Type 9: Link-local scope<br>Type 10: Area-local scope<br>Type 11: AS-wide scope<br>In Summary…<br>Type 1,2: Within the area</p><p>Type 3,4: Between areas via ABR<br>Type 5: OSPF domain-wide (excluding stub)<br>Type 7: Within the NSSA<br>Type 9/10/11: According to their scope</p><p>Normal Area<br>In the OSPF world, a Normal Area is the standard area type where no restrictions are applied and all OSPF features work perfectly. Unless you specifically configure an area as a “Stub” or “NSSA,” it is considered a Normal Area by default. It accepts all types of LSAs and allows them to be generated internally. Types 1, 2, 3, 4, and 5 LSAs all roam freely in this area.</p><p>Stub Area<br>An OSPF Stub Area is a “restricted” area type designed to lighten the processor and memory load on routers in an area. These areas do not accept external routes (BGP, EIGRP, Static, etc.) and what are called Type 5 LSAs. Instead, they use a single Default Route (0.0.0.0/0) to exit to the outside world. A router that redistributes routes from the outside world to OSPF cannot exist within a Stub area. As a Network Engineer, you would choose Stub configuration, especially in branch offices with low-end or older routers, for the following advantages:</p><p>1. Reduced LSDB Size: Instead of thousands of external routes, only a single default route is maintained.</p><p>2. Memory Savings: Fewer LSAs mean less RAM usage.</p><p>3. Route flapping (fluctuations) from the outside world (such as the internet) does not trigger SPF calculations on routers within the Stub domain.</p><p>Totally Stubby Area<br>OSPF Totally Stubby Area is the most restrictive area type developed by Cisco, taking the “Stub Area” concept a step further. In this area type, not only external routes (Type 5) but even summary routes from other OSPF areas (Type 3) are blocked. For routers in this area, the world consists only of their own area; there is only one gateway (Default Route) for everything else.</p><p>As a Network Engineer, you would generally prefer this structure in the following scenarios:</p><p>Endpoint Branches: If the router in the branch office has very low hardware specifications and is connected to the center via a single line (Hub-and-Spoke).<br>Stability: No matter how much “flap” (line interruption) occurs in the rest of the network (other areas or the outside world), the routers in Totally Stubby don’t even notice it. SPF calculations remain minimal.<br>Simple Management: The routing table remains clean; only local networks and a single default route are visible.</p><p>NSSA<br>OSPF NSSA (Not-So-Stubby Area) is a hybrid area type that carries the restrictions of “stub” areas but allows you to host an ASBR (Area Border Router). Normally, route redistribution from the outside world (BGP, Static, EIGRP, etc.) is prohibited in stub areas. NSSA is designed to circumvent this restriction.</p><p>Type 5 LSA is Prohibited: Like a standard stub area, it does not allow Type 5 LSAs from the outside world to enter.<br>Can Host ASBR: A ​​router within the NSSA can forward routes received from the outside world to the OSPF.<br>Uses Type 7 LSA: External routes are announced as Type 7 within the NSSA to avoid restrictions.<br>Translation: The ABR (Area Border Router) receives these Type 7 LSAs, converts them to Type 5, and forwards them to other OSPF areas (such as Area 0).</p><p>Totally NSSA<br>OSPF Totally NSSA (Totally Not-So-Stubby Area) is a hybrid area type where Cisco combines “Totally Stubby” logic with NSSA. This mode is one of the most advanced and restrictive structures among OSPF area types. OSPF Totally NSSA (Totally Not-So-Stubby Area) is a hybrid area type where Cisco combines “Totally Stubby” logic with NSSA. This mode is one of the most advanced and restrictive structures among OSPF area types.</p><p>In short: It is a combination of NSSA’s ability to generate external routes and Totally Stubby’s digest route blocking feature.</p><p>Maximum Isolation: Neither external routes (Type 5) nor digest routes from other areas (Type 3) can enter.<br>ASBR Capability: A router within the area can transmit routes received from the outside world (Static, BGP, etc.) to OSPF as Type 7 LSA.<br>Automatic Default Route: The ABR (Area Border Router) automatically advertises a default route (0.0.0.0/0) internally. This allows routers inside to access both other areas and the outside world through this single gateway. LSA Conversion: Type 7 LSAs from an ASBR within the area are converted to Type 5 by the ABR and sent to the Backbone (Area 0).</p><p>Intra-Area: Specifies routes learned from within the same area. Indicated as O in the routing table.</p><p>Inter-Area: Specifies routes coming from the ABR. Indicated as O IA in the routing table.</p><p>External: Specifies redistributed routes. Indicated as O E1 or O E2 in the routing table.</p><p>If the same prefix is ​​attempted to be learned from different sources, the longest prefix match, administrative distance, and metric values ​​are considered when making a choice.</p><p>For OSPF neighboring, the following values ​​must match:</p><p>Area ID<br>Hello/Dead timer<br>Authentication<br>Stub/NSSA flag (area type compatibility)<br>Network type (in most cases)<br>MTU (especially problematic in ExStart/Exchange)<br>Subnet/mask (especially in broadcast segments)<br>Router ID must be unique</p><p>In OSPFv2, an authentication method can be used to maintain neighboring setup. Authentication methods can include simple password, MD5, and HMAC/SHA. If there is an authentication mismatch, neighboring cannot be established.</p><p>OSPFv2 has two multicast addresses: 224.0.0.5 and 224.0.0.6. The 224.0.0.5 address is listened to by all OSPF routers. Since every device included in OSPF listens to this address, general announcements are made here. Hello packets are sent to establish neighboring and indicate that the line is “alive”. The 224.0.0.6 address is listened to only by the DR (Designated Router) and BDR (Backup Designated Router). Only the selected leader (DR) and vice-leader (BDR) of that network listen to it. Other routers (DROther) do not consider packets arriving at this address.</p><p>OSPF Virtual Link: This is a “tunnel” mechanism used to virtually connect an area that is not directly connected to Area 0 (Backbone) to the Backbone by passing through another area. According to OSPF’s fundamental rule, all areas (Area 1, 2, 10, etc.) must be physically connected to Area 0 hierarchically. However, when this connection is broken due to network expansions, mergers, or unplanned growth, Virtual Link comes into play. The following rules are crucial when configuring Virtual Link:</p><p>Transit Area: There must be an intermediate area (Transit Area) through which the virtual tunnel will pass. This area must be a Normal area (except Area 0).<br>Stub Restriction: The transit area absolutely cannot be a Stub Area. This is because Virtual Link requires the passage of packets such as Type 5 LSA, and Stub areas do not allow this.<br>Router ID: Configuration is done via the Router ID of the routers at both ends, not via IP addresses.<br>Cost: The cost of the virtual link is equal to the cost of the shortest path through the transit area.</p><p>OSPF Summarization: This is the process of grouping and declaring numerous specific subnets in the routing table under a single large network address. Its purpose is to reduce CPU and RAM usage by routers, minimize LSA traffic on the network, and prevent a link flapping from affecting the entire network. If you are a network engineer managing a large-scale network, you will see the following benefits of summarizing:</p><p>Smaller Routing Tables: Instead of 100 /24 subnets, a single /16 route is maintained. This increases routing (lookup) speed.<br>Fault Isolation (LSA Throttling): When a specific link in one area drops, routers in other areas don’t rerun the SPF algorithm because the summary route is still active. The network becomes much more stable.<br>Bandwidth Savings: Control traffic decreases because fewer LSA packets are sent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f42d1df1574d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IS-IS Protocol]]></title>
            <link>https://medium.com/@ysakturk/is-is-protocol-27e706a43878?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/27e706a43878</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Mon, 09 Mar 2026 09:38:21 GMT</pubDate>
            <atom:updated>2026-03-09T09:38:21.861Z</atom:updated>
            <content:encoded><![CDATA[<p>For Turkish: Click the link: <a href="https://ysakturk.com/isis">https://ysakturk.com/isis</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YAFvdRZm6mT8viVR2tHuwg.png" /></figure><p>IS-IS (Intermediate System to Intermediate System)<br>IS-IS is essentially a link-state, or Interior Gateway Protocol (IGP), similar to OSPF. A link-state allows routers within an Autonomous System to calculate and use the shortest path when distributing topology information to each other. To summarize the basic terms:</p><p>- IGP: Works within the same AS (Autonomous System) as OSPF.</p><p>- Link State: Each router learns the topology of its network as a database.</p><p>- SPF: The shortest paths are calculated from these databases.</p><p>IS-IS was originally designed for OSI CLNS, not IP. IP support was added later. Therefore, some terms differ from OSPF.</p><p>So why is ISIS preferred over static routing? While static routing provides plug-and-play ease in small and simple structures, it becomes unmanageable as the network grows and becomes more complex. Writing static routes for each prefix within each router is both very difficult and unmanageable. Dynamic routing protocols are preferred instead.</p><p>Why ISIS? It has a highly scalable and stable structure. It’s also IP-independent, meaning it scales beyond Layer 2. It’s very common in structures like MPLS or Segment Routing, and operators love using ISIS :)</p><p>The ISIS working principle is briefly as follows:</p><p>The router activates ISIS on its interface.<br>Hello packets are shared with neighbors.<br>Necessary adjacency is established.<br>Each router publishes its link information as an LSP (Link State PDU).<br>All routers create an LSDB (Link State Database).<br>SPF runs (for route calculation).<br>Necessary routes are written to the RIB/FIB tables.</p><p>One of the most critical aspects of ISIS is Levels. The Level structure essentially provides scalability by dividing a network into manageable parts. If an ISP network had thousands of routers, all in a single area, even the slightest link drop would force all routers to run the SPF algorithm simultaneously, causing CPU usage to skyrocket. What are these levels?</p><p>IS-IS Level-1<br>This level is used for routing within the same area. In L1, the router only knows the topology within its own area.</p><p>IS-IS Level-2<br>Used for backbone routing between areas. Routers in L2 connect to each other to form a backbone area.</p><p>IS-IS Level-1–2<br>Both L1 and L2 work. L1 establishes neighboring relationships within its own area. L2 establishes neighboring relationships on the backbone side. Areas behave like borders.</p><p>In OSPF, everyone worked with the logic of being connected to backbone area 0. In IS-IS, the backbone logic is provided by the L2 domain.</p><p>In IS-IS, the Network Entity Title, which we call NET, is used to identify the router. For a NET, Area ID, System ID, and NSEL are generally used. For example:</p><p>For the address 49.0001.0000.0000.0001.00, the 49.001 part is the area ID, the 0000.0000.0001 part is the system ID, and the 00 part is the NSEL. The system ID is usually 6 bytes. Within the same domain, the system ID must be unique.</p><p>In OSPF, the Router ID is very important. In IS-IS, the ID/NET is very critical. If we ask what the biggest difference between OSPF and IS-IS is; OSPF works IP-dependently, but IS-IS works IP-independently and uses NET IDs.</p><p>What are the IS-IS Package Types (PDU)?</p><p>IIH (IS-IS Hello)<br>Used for establishing neighborly relationships. It comes in LAN IIH and P2P IIH. LAN IIH is used in broadcast-enabled networks (e.g., Ethernet LAN). P2P IIH is used to establish and maintain a neighborly relationship between two directly connected routers. The biggest difference from LAN IIH is that it assumes only two devices are present in the environment.</p><p>LSP (Link State PDU)<br>Carries the topology information of the router. It contains Router ID/System ID, neighboring information, metrics, prefixes, and various feature information. It’s similar to the LSA logic in OSPF, but in IS-IS, the fundamental object is the LSP.</p><p>In short, the LSP is like an ID card and contains all the information.</p><p>CSNP (Complete Sequence Number PDU)<br>Carries the LSDB summary collectively. It’s like an inventory list or database summary. Its main function is to ensure that the map information, which we call LSDB, of all routers in the network is completely identical, i.e., synchronized.</p><p>PSNP (Partial Sequence Number PDU)<br>It is the missing part completion or confirmation mechanism of the IS-IS protocol. It only covers certain LSPs. It works as broadcast or P2P depending on the network type.</p><p>How is neighboring established? To establish neighboring, certain conditions must be met. These are:</p><p>Being on the same level (L1/L2 compatibility)<br>Area compatibility (for L1)<br>Compatibility of Hello parameters/timer values<br>If using authentication, the correct password must be entered by both parties<br>MTU and CLNS availability<br>The IS-IS protocol must be active on the same link</p><p>Now, we mentioned P2P and Broadcast types. What is the difference between them? In a point-to-point structure, neighboring is established directly, and devices are directly connected to each other. In a broadcast structure, a DIS is selected (similar to the DR7BDR selection in OSPF).</p><p>What is DIS? It stands for Designated Intermediate System. In broadcast network structures, IS-IS selects a DIS. The role of DIS:</p><p>To manage some LSP flooding/synchronization processes<br>To generate pseudo-LSPs (to represent the LAN topology)</p><p>A pseudo-LSP is a special type of LSP used in broadcast networks in the IS-IS protocol, broadcast in the name of a virtual router that does not physically exist. Imagine 10 people in a meeting room (LAN). Instead of everyone saying “hello” and exchanging business cards (Full Mesh), one person in the room (DIS) writes everyone’s name on a piece of paper and hangs it on the wall (Pseudonode LSP).</p><p>The difference from OSPF DR is that IS-IS does not have BDR. DIS selection is done with different criteria (priority + SNPA/MAC, etc.). DIS preemption behavior may differ from OSPF.</p><p>In IS-IS, each router stores the following information:</p><p>LSDB (Link State Database): Topology information<br>SPF Tree: Shortest path information<br>Routing Table (RIB): Prefix-based route information</p><p>SPF is triggered when a new LSP arrives, when the LSP changes, when the relevant link or ports are up/down, when the metric value changes, and when the prefix advertisement changes. SPF timers are used in large-scale networks to prevent CPU usage from peaking.</p><p>IS-IS and IPv4/IPv6<br>The beauty of IS-IS is that it is not dependent on IP addresses as the carrier protocol. IP information is added using TLVs.</p><p>IPv4 Reachability TLV<br>IPv6 Reachability TLV<br>IPv6 Interface Address TLV</p><p>This allows both IPv4 and IPv6 to be carried within a single IS-IS process. This is very useful in dual-stack networks.</p><p>TLV Logic<br>TLV is essentially the heart of IS-IS.</p><p>T: Type<br>L: Length<br>V: Value<br>This structure makes it very easy to add new features to the protocol. Examples of use cases: IP Prefixes, Router Capability, TE Metric/Bandwidth, Segment Routing SIDs, Authentication, IPv6 Reachability…</p><p>This flexibility is the biggest reason why IS-IS has a long lifespan in operator networks.</p><p>IS-IS Route Types<br>This varies depending on the vendor CLI, but routes appear as follows: L1 route, L2 route, or L1L2 learned behavior.</p><p>Within the same area, traffic appears as L1. In different area structures, the L2 router sends the packet to the L1/L2 router. The packet is carried on the L2 backbone and lands at L1 in the destination area.</p><p>Authentication<br>Auth can be used for neighbor and LSP security in IS-IS:</p><p>Interface hello authentication<br>Area/domain LSP authentication<br>MD5/HMAC based methods (depending on vendor/version support)</p><p>This makes it difficult for rogue routers to establish adjacency/issue fake LSPs.</p><p>IS-IS and MPLS<br>IS-IS is particularly common in the following scenarios:</p><p>MPLS core<br>Traffic Engineering (TE)<br>Segment Routing (SR-MPLS / SRv6 in some architectures)<br>Fast convergence needs<br>Large backbones</p><p>Because IS-IS’s TLV structure makes it easy to declare new capabilities.</p><p>OSPF and IS-IS<br>IS-IS</p><p>Very mature usage among operators<br>Flexible TLV structure<br>Layer-2 operation is an advantage in some design/debug scenarios<br>Good scalability perception in large topologies<br>OSPF</p><p>More widespread knowledge base on the enterprise side<br>Much documentation/training material<br>Configuration and conceptual learning is more familiar for some teams</p><p>I want to talk about some common IS-IS failure points…</p><p>1. Adjacency is not appearing… What should I check?</p><p>Is IS-IS enabled under Interface?<br>Level compatibility (L1/L2)?<br>NET/area compatibility (especially L1)<br>Authentication mismatch?<br>CLNS MTU/encapsulation issue?<br>Is it a passive interface?<br>Are the Hellos going back and forth?</p><p>2. Adjacency exists but no route…</p><p>Is the prefix being advertised? Is there interface/passive/prefix suppression?<br>Is the level wrong? (prefix is ​​in L1, you are looking at L2)<br>Is route policy/filter blocking?<br>Is the overload bit set?<br>Metric too high/blackhole policy?</p><p>3. LSDB sync problem…</p><p>CSNP/PSNP exchange check<br>LSP lifetime / checksum / sequence issue<br>High CPU → SPF latency<br>Flapping link → continuous LSP churn</p><p>4. Traffic is suboptimal…</p><p>Metric plan is corrupted<br>ECMP behavior<br>L1→L2 transition point incorrect choice<br>Differences between wide metric and TE metric<br>SR/TE policy effect</p><p>Important operational information:</p><p>1. Overload Bit: If a router sets an overload bit, it generally indicates that it does not want to be used as a transit route (e.g., to prevent traffic from entering the database before it is fully loaded during boot).</p><p>Use Cases:</p><p>The router is newly started, BGP/IGP is not yet fully stable.<br>You don’t want to miss transit traffic during maintenance.<br>If accidentally left open:</p><p>The router may be accessible, but transit traffic may not pass as expected.</p><p>2. IS-IS Timers and Convergence</p><p>Main factors affecting convergence speed:</p><p>Hello interval / holdtime<br>SPF timers (throttle)<br>LSP generation timers<br>BFD integration (very critical if vendor-supported)<br>Interface physical detect time</p><p>So it’s not just about “Is IS-IS fast?”, but timer tuning + physical layer + BFD are considered together.</p><p>Simple Topology Example (Logic)</p><p>Let’s say:</p><p>Area 49.0001<br>R1 (L1)<br>R2 (L1/L2)<br>Area 49.0002<br>R3 (L1/L2)<br>R4 (L1)<br>R2 and R3 are connected via the L2 backbone</p><p>Traffic: R1 → R4</p><p>R1 sees that the R4 prefix is ​​not in its own area<br>It sends traffic to R2, which is the L1/L2 border<br>R2 → R3 via L2<br>R3 → reaches R4 via L1 in its own area<br>This structure is similar to OSPF ABR/backbone, but it is not exactly the same mechanically.</p><p>Configuration logic (vendor independent, conceptual)</p><p>Generally, there are 3 steps:</p><p>Create IS-IS process/domain<br>Define NET<br>Enable IS-IS on interfaces<br>(Optional) Set level, metric, auth, wide metric, passive, timers, BFD</p><p>Example Logically:</p><p>router isis X<br>net …<br>interface …<br>ip router isis X / isis enable (varies depending on the vendor)</p><p>Critical outputs viewed on the IS-IS show/debug side:</p><p>Vendor varies, but generally these types of commands are used:</p><p>show isis neighbors → neighbor status<br>show isis interface → interface levels/timers<br>show isis database → LSP/LSDB<br>show isis route → routes originating from IS-IS<br>show clns neighbors (on some platforms)<br>show isis spf-log → SPF trigger history<br>show isis hostname → system-id ↔ hostname match</p><p>In short, IS-IS:</p><p>It is a link-state IGP<br>It works with L1/L2 hierarchy<br>It uses NET/System ID<br>It has IIH, LSP, CSNP, PSNP PDUs<br>It calculates the shortest path with SPF<br>It is very flexible thanks to its TLV structure<br>Application video coming soon</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27e706a43878" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yeni Cisco CE Egitim Programi]]></title>
            <link>https://medium.com/@ysakturk/yeni-cisco-ce-egitim-programi-07fa57454c07?source=rss-b19d1bde6728------2</link>
            <guid isPermaLink="false">https://medium.com/p/07fa57454c07</guid>
            <dc:creator><![CDATA[Yavuz Selim Aktürk]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 06:56:38 GMT</pubDate>
            <atom:updated>2026-03-02T06:56:38.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*KxjDDu3c6lEZfCODX9JZDA.png" /></figure><p>Cisco, daha önce olduğu gibi yine ücretsiz iki adet CE Credit eğitim programı yayınladı. Bu iki program ile birlikte toplamda 16 adet kredi toplama şansı doğuyor. Tek yapmanız gereken: <a href="http://www.u.cisco.com/">www.u.cisco.com</a> adresine Cisco account bilgileriniz ile giriş yapıp “ <strong>Learning Paths</strong> “ sekmesi altından bu iki eğitimi tamamlamak…</p><p><strong>1.Eğitim: Cisco AI Technical Practitioner (AITECH)</strong> <em>— Cisco Yapay Zeka Teknik Uzmanı (AITECH) Öğrenim Yolu, geleneksel bilgi tabanlı işlerden yapay zeka ile desteklenen inovasyon odaklı rollere geçiş yapmak isteyen teknik profesyoneller için tasarlanmıştır. Bu kapsamlı program, öğrenenleri en yeni yapay zeka araçları ve metodolojilerini kullanarak teknik çözümler tasarlama, görevleri otomatikleştirme ve teknik ekipleri yönetme becerileriyle donatır. Yapay zeka destekli kod üretimi ve veri analizinden gelişmiş model özelleştirmesine ve iş akışı otomasyonuna kadar, bu Öğrenim Yolu BT ve ağ mühendislerini, veri analistlerini, AIOPs uzmanlarını, çözüm mimarlarını, teknik liderleri, yöneticileri ve iş süreç analistlerini kuruluşlarında yapay zekanın tüm potansiyelini kullanmaya hazırlar. (https://u.cisco.com/paths/cisco-ai-technical-practitioner-20806 adresinden alıntı yapılmıştır)</em></p><p><strong>2. Cisco AI Business Practitioner (AIBIZ) </strong><em>— Cisco Yapay Zeka İş Uygulayıcısı (AIBIZ) Öğrenme Yolu, yapay zeka okuryazarlığı açığını kapatmanıza yardımcı olur. Üretkenlik, içerik oluşturma, analiz ve liderlik için Üretken Yapay Zekayı kullanmak üzere pratik, uygulamalı beceriler kazanırken, yapay zekayı stratejik ve sorumlu bir şekilde nasıl benimseyeceğinizi öğreneceksiniz. Temel kavramlar ve uygulamalı araç kullanımıyla başlayacak, ardından pazarlama, müşteri desteği ve veri analizi alanlarında hızlı mühendislik, stratejik değerlendirme ve gerçek dünya uygulamalarına geçeceksiniz. Yolculuk, uygulama yol haritaları tasarlamanızı, değişimi yönetmenizi ve yapay zeka benimsenmesi için ikna edici iş gerekçeleri oluşturmanızı sağlayacak liderlik eğitimiyle doruğa ulaşır. Bu Öğrenme Yolu, Üretken Yapay Zekanın potansiyelinden yararlanmaya ve sorumlu, stratejik entegrasyon için eleştirel düşünme becerileri geliştirmeye hazır iş profesyonelleri, yöneticiler ve liderler için idealdir. (https://u.cisco.com/paths/cisco-ai-business-practitioner-20706 adresinden alıntı yapılmıştır)</em></p><p>Eğitimleri tamamladıktan sonra kredi bilgilerinizi <a href="http://www.ce.cisco.com/">www.ce.cisco.com</a> adresinden kontrol edebilirsiniz.</p><p><strong>Son tarih iki eğitim için de 26 Mart 2026. Fırsatları kaçırmayın…</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07fa57454c07" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>