<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cisco on ittechnetworkk</title>
    <link>https://ittechnetworkk.co.uk/tags/cisco/</link>
    <description>Recent content in Cisco on ittechnetworkk</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 08 Apr 2026 10:00:00 +0200</lastBuildDate>
    <atom:link href="https://ittechnetworkk.co.uk/tags/cisco/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>vPC on Cisco Nexus 9000</title>
      <link>https://ittechnetworkk.co.uk/posts/vpc-nexus-9k/</link>
      <pubDate>Wed, 08 Apr 2026 10:00:00 +0200</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/vpc-nexus-9k/</guid>
      <description>&lt;h2 id=&#34;what-is-vpc&#34;&gt;What is vPC?&lt;/h2&gt;&#xA;&lt;p&gt;Virtual Port Channel (vPC) lets two Nexus switches appear as a single logical switch to downstream devices. Connected hosts or switches see one port-channel spanning both peers — if one peer fails, traffic continues through the other with no STP reconvergence.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Key components:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;vPC Peer Link&lt;/strong&gt; — carries BPDUs, HSRP, control traffic, and orphan port traffic between the two peers. Always a port-channel with at least two 10G/40G/100G members&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;vPC Peer Keepalive&lt;/strong&gt; — a lightweight heartbeat (UDP 3200) used only to detect a dual-active (split-brain) scenario. Runs over a dedicated port-channel in a separate VRF — keeping it off the management plane for security and redundancy&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;vPC Member Ports&lt;/strong&gt; — port-channels on each peer that share a common &lt;code&gt;vpc&lt;/code&gt; ID, forming a single logical channel to the downstream device&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;vPC Domain&lt;/strong&gt; — the logical grouping that binds the two peers together&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;topology&#34;&gt;Topology&lt;/h2&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;            ┌──────────┐       ┌──────────┐&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;            │  NEXUS-1 │       │  NEXUS-2 │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;            │ (vPC Pri)│       │ (vPC Sec)│&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;            └──┬──┬──┬─┘       └─┬──┬──┬──┘&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │  │  │           │  │  │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;    Keepalive──│──│──│───────────│──│──│──Keepalive&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;   (Po20/VRF)  │  │  │           │  │  │ (Po20/VRF)&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │  │  └───────────┘  │  │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │  │   Peer Link     │  │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │  │  (Po10: 2x40G)  │  │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │  │                 │  │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │  └────────┬────────┘  │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │      vPC Member       │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │     (Po100: 2x10G)    │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │           │           │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │      ┌────┴────┐      │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               │      │ SERVER  │      │&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;               └──────┤ / ToR   ├──────┘&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;                      └─────────┘&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;&#xA;&lt;h2 id=&#34;addressing-reference&#34;&gt;Addressing Reference&lt;/h2&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Device&lt;/th&gt;&#xA;          &lt;th&gt;Interface&lt;/th&gt;&#xA;          &lt;th&gt;IP Address&lt;/th&gt;&#xA;          &lt;th&gt;Purpose&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;NEXUS-1&lt;/td&gt;&#xA;          &lt;td&gt;Po20 (VRF VPC-KA)&lt;/td&gt;&#xA;          &lt;td&gt;10.10.10.1/30&lt;/td&gt;&#xA;          &lt;td&gt;Peer Keepalive&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;NEXUS-2&lt;/td&gt;&#xA;          &lt;td&gt;Po20 (VRF VPC-KA)&lt;/td&gt;&#xA;          &lt;td&gt;10.10.10.2/30&lt;/td&gt;&#xA;          &lt;td&gt;Peer Keepalive&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;NEXUS-1&lt;/td&gt;&#xA;          &lt;td&gt;Vlan100&lt;/td&gt;&#xA;          &lt;td&gt;172.16.100.2/24&lt;/td&gt;&#xA;          &lt;td&gt;HSRP VIP gateway&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;NEXUS-2&lt;/td&gt;&#xA;          &lt;td&gt;Vlan100&lt;/td&gt;&#xA;          &lt;td&gt;172.16.100.3/24&lt;/td&gt;&#xA;          &lt;td&gt;HSRP VIP gateway&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;HSRP VIP&lt;/td&gt;&#xA;          &lt;td&gt;—&lt;/td&gt;&#xA;          &lt;td&gt;172.16.100.1/24&lt;/td&gt;&#xA;          &lt;td&gt;Default gateway&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;configuration&#34;&gt;Configuration&lt;/h2&gt;&#xA;&lt;p&gt;We&amp;rsquo;ll build this in order — each step depends on the previous one.&lt;/p&gt;</description>
    </item>
    <item>
      <title>MPLS L3VPN Lab</title>
      <link>https://ittechnetworkk.co.uk/posts/mpls-l3vpn-small-lab/</link>
      <pubDate>Wed, 01 Apr 2026 12:48:42 +0200</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/mpls-l3vpn-small-lab/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;This lab builds a full MPLS L3VPN service across an ISP core (AS 35500) with OSPF Area 0 as the IGP, LDP for label distribution, and MP-BGP (VPNv4) for customer route exchange. Two VPNs — &lt;strong&gt;RED&lt;/strong&gt; (AS 25942) and &lt;strong&gt;BLUE&lt;/strong&gt; (AS 48273) — carry overlapping address space through the same physical infrastructure, demonstrating VRF isolation.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Key design choices:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;P1 and P4&lt;/strong&gt; act as BGP Route Reflectors — PEs only peer with these two, no full-mesh iBGP required&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;&lt;code&gt;as-override&lt;/code&gt;&lt;/strong&gt; on all PE-CE peerings since both RED CEs share an AS and both BLUE CEs share an AS&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;OSPF point-to-point&lt;/strong&gt; network type on all /30 core links (skips DR/BDR election)&lt;/li&gt;&#xA;&lt;li&gt;All BGP loopback peerings use &lt;strong&gt;update-source Loopback0&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Here is the topology:&lt;/p&gt;</description>
    </item>
    <item>
      <title>DMVPN Phase 3 Dual Hub with IPSec Lab</title>
      <link>https://ittechnetworkk.co.uk/posts/dmvpn-phase3-ipsec1-ospf/</link>
      <pubDate>Wed, 01 Apr 2026 08:00:00 +0000</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/dmvpn-phase3-ipsec1-ospf/</guid>
      <description>&lt;p&gt;Hi everyone, in this lab I&amp;rsquo;ll walk you through how to configure a Dual Hub DMVPN Phase3 - IPSec topology.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OSPF Route Filtering</title>
      <link>https://ittechnetworkk.co.uk/posts/ospf-route-filtering/</link>
      <pubDate>Mon, 16 Feb 2026 11:22:31 +0100</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/ospf-route-filtering/</guid>
      <description>&lt;p&gt;Hi everyone, in this article I will walk you through how to configure OSPF Route Filtering through a lab in the exhibit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cisco Device Syslog Integration with Wazuh SIEM</title>
      <link>https://ittechnetworkk.co.uk/posts/cisco-wazuh-integration/</link>
      <pubDate>Sat, 19 Jul 2025 14:50:44 +0200</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/cisco-wazuh-integration/</guid>
      <description>&lt;p&gt;Hi everyone, in this article I will guide you through how to integrate Cisco devices (switches and routers) with the Wazuh SIEM tool for centralized logging and monitoring.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Network Time Protocol (NTP)</title>
      <link>https://ittechnetworkk.co.uk/posts/ntp/</link>
      <pubDate>Tue, 13 May 2025 21:23:07 +0200</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/ntp/</guid>
      <description>&lt;p&gt;In modern networks, accurate time synchronization is crucial for tasks such as logging, authentication, and system coordination. Network Time Protocol (NTP) is a widely used protocol that allows devices on a network to synchronize their clocks with a reliable time source. This guide will walk you through the configuration of NTP on Cisco devices, including manual time setup, using a device as an NTP server, authentication, and debugging.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic Trunking Protocol (DTP)</title>
      <link>https://ittechnetworkk.co.uk/posts/dynamic-trunking-protocol/</link>
      <pubDate>Wed, 02 Apr 2025 22:02:02 +0200</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/dynamic-trunking-protocol/</guid>
      <description>&lt;p&gt;Hi everyone, in this article, I will explain what DTP is and how it works.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GRE Over IPSEC LAB</title>
      <link>https://ittechnetworkk.co.uk/posts/gre-over-ipsec-lab/</link>
      <pubDate>Fri, 21 Feb 2025 22:19:46 +0100</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/gre-over-ipsec-lab/</guid>
      <description>&lt;p&gt;Hello everyone, in this LAB I will configure GRE over IPSec Tunnels with following topology.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GRE LAB</title>
      <link>https://ittechnetworkk.co.uk/posts/gre-lab/</link>
      <pubDate>Fri, 21 Feb 2025 22:18:30 +0100</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/gre-lab/</guid>
      <description>&lt;p&gt;Hello everyone, in this LAB I will configure GRE Tunnels.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VRF-Lite Configuration</title>
      <link>https://ittechnetworkk.co.uk/posts/vrf-lite-lab/</link>
      <pubDate>Fri, 21 Feb 2025 02:36:28 +0100</pubDate>
      <guid>https://ittechnetworkk.co.uk/posts/vrf-lite-lab/</guid>
      <description>&lt;p&gt;Hello everyone, in this LAB I will configure GRE Tunnels with following topology.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
