<?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 Edgar C Francis on Medium]]></title>
        <description><![CDATA[Stories by Edgar C Francis on Medium]]></description>
        <link>https://medium.com/@edgarcf?source=rss-563571c76227------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DkAm4B1hjRjZkQw-Z-uQaw.jpeg</url>
            <title>Stories by Edgar C Francis on Medium</title>
            <link>https://medium.com/@edgarcf?source=rss-563571c76227------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:31:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edgarcf/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[What is FLEXVPN? How to configure FLEXVPN?]]></title>
            <link>https://edgarcf.medium.com/what-is-flexvpn-how-to-configure-flexvpn-92a394bfdda0?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/92a394bfdda0</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[vpn-service]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[computer-science]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Thu, 29 Aug 2024 07:31:30 GMT</pubDate>
            <atom:updated>2024-08-29T07:31:30.490Z</atom:updated>
            <content:encoded><![CDATA[<p>https://mpls.internetworks.in/2024/04/what-is-flexvpn-how-to-configure-flexvpn.html</p><p><strong>FlexVPN </strong>is a versatile VPN framework by Cisco that simplifies the configuration and deployment of various types of VPNs because Cisco supports various types of VPNs and many of them require different configurations to show verification commands. FlexVPN is designed to support site-to-site, hub-and-spoke, remote access, and other VPN configurations but The only VPN type that FlexVPN doesn’t cover is GETVPN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*LrQChdKdqxn1MB0G-fpUTA.png" /></figure><p>Here are some key points about FlexVPN:</p><p><strong>Based on IKEv2</strong>: FlexVPN utilizes the Internet Key Exchange version 2 (IKEv2) protocol for all its VPN types, which offers improved security and features over IKEv1.</p><p><strong>Smart Defaults:</strong> It employs smart defaults based on best practices, minimizing the required configuration efforts.</p><p><strong>Unified Solution:</strong> FlexVPN is a unified solution that covers all VPN types except Group Encrypted Transport VPN (GETVPN), making it easier to manage and operate.</p><p><strong>Supports Various Authentication Methods:</strong> It supports certificates, pre-shared keys (PSKs), and Extensible Authentication Protocol (EAP) authentication methods.</p><p><strong>Deployment Flexibility:</strong> FlexVPN can be deployed over public internet or private MPLS VPN networks and is designed for both site-to-site and remote access VPNs.</p><p><strong>Failover Redundancy:</strong> It offers different redundancy models, including dynamic routing protocols over VPN tunnels and IKEv2-based server clustering.</p><p><strong>Smart default </strong>is a pre-defined value this feature helps us to minimize the configuration and make it easy to configure VPN. For example, when we configure IPsec VPN with IKEv2, we have to configure the following items</p><ul><li>IKEv2 proposal</li><li>IKEv2 policy</li><li>IKEv2 profile</li><li>IKEv2 keyring</li><li>IPsec transform-set</li><li>IPsec profile</li></ul><p>These items we have to configure for IPsec VPN with IKEv2. But with smart default, we use pre-defined values and we have to configure only two items:</p><ul><li>IKEv2 profile</li><li>IKEv2 policy</li></ul><p>We do not have to configure the proposal, policy, transform-set, and IPsec profile.</p><p>Let’s see the configuration for a better understanding:</p><p>Topology: In this topology, we have a head office router-1 and branch sites a,b,c,d, and e routers. head office router is a hub router and the rest of the routers are spokes and router 2 acts as an internet. our task is to configure the IPsec VPN tunnel and all the data will be encrypted.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92a394bfdda0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to configure IPsec on the GRE Dynamic Virtual-Template interface?]]></title>
            <link>https://edgarcf.medium.com/how-to-configure-ipsec-on-the-gre-dynamic-virtual-template-interface-c50734836a28?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/c50734836a28</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[gre]]></category>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[cisco]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Thu, 29 Aug 2024 06:06:12 GMT</pubDate>
            <atom:updated>2024-08-29T06:06:12.349Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://mpls.internetworks.in/2024/04/how-to-configure-ipsec-on-gre-dynamic.html">How to configure IPsec on GRE Dynamic Virtual-Template interface?</a></p><p>Generic Routing Encapsulation (GRE) is a network tunneling protocol developed by Cisco Systems that can encapsulate a wide variety of network layer protocols inside virtual point-to-point links or point-to-multipoint links over an Internet Protocol network. GRE tunnels also allow unicast, multicast, and broadcast traffic between routers but there is a problem with GRE tunnels it is clear text and GRE needs to provide better-grade protection. However, we can encrypt the complete GRE tunnel with IPsec security which provides good-grade security. we already configure IPsec with GRE click here. but in this blog, we will configure an IPsec with a Dynamic Virtual-Template interface.</p><p>VTI does the same job that GRE with IPsec does. They both encrypt the tunnel with IPsec. VTI removed the additional 4 bytes GRE header, thus reducing the bandwidth for sending encrypted data. VTI allows the configuration of ACL, NAT, and QoS. remember the default mode for a tunnel is GRE you have to define the mode IPsec IPv4 to configure the SVTI tunnel.</p><p>let’s see the configuration- in this topology, we have head office router 1 and branch routers 3 and 4. Router 2 is acting as an internet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c50734836a28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Cisco Management VLAN? How to configure VLAN management? | CCNA Security]]></title>
            <link>https://edgarcf.medium.com/what-is-cisco-management-vlan-how-to-configure-vlan-management-ccna-security-d9d789e85d2e?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9d789e85d2e</guid>
            <category><![CDATA[ccna]]></category>
            <category><![CDATA[ccna-security]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 08:00:33 GMT</pubDate>
            <atom:updated>2024-07-01T08:00:33.346Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Management VLAN?</h3><p>Management VLAN is a VLAN that is used for Managing and monitoring network devices like routers, switches, and other devices from a remote location by using protocols such as telnet, SSH, SNMP,syslog, etc. The purpose of the management VLAN is to configure designated the VLAN for configuration purposes. Cisco recommends not to use VLAN 1 and not to use any VLAN that carries user data traffic as management VLAN. Normally the Management VLAN is VLAN1, but you can use any VLAN as a management VLAN. Once you configure the Management VLAN for administration, the data plane traffic and management traffic will be isolated this reduces the interference, and also with this VLAN security will be enhanced for management traffic.</p><h3><strong>Let’s see the configuration for better understanding.</strong></h3><p><a href="https://www.internetworks.in/2024/06/what-is-cisco-management-vlan-how-to.html">https://www.internetworks.in/2024/06/what-is-cisco-management-vlan-how-to.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HiKTTtrSZO5P02F5CVYpsg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9d789e85d2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is DMVPN (Dynamic Multipoint VPN), NHRP, mGRE, and How to configure DMVPN Phase 1?]]></title>
            <link>https://edgarcf.medium.com/what-is-dmvpn-dynamic-multipoint-vpn-nhrp-mgre-and-how-to-configure-dmvpn-phase-1-abff7917acc4?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/abff7917acc4</guid>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sat, 23 Mar 2024 08:12:19 GMT</pubDate>
            <atom:updated>2024-03-23T08:12:19.486Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is DMVPN (Dynamic Multipoint VPN), NHRP, mGRE, and How to configure DMVPN Phase 1?</strong></p><p><a href="https://mpls.internetworks.in/2021/02/what-is-dmvpn-dynamic-multipoint-vpn.html">What is DMVPN (Dynamic Multipoint VPN), NHRP, mGRE and How to configure DMVPN Phase 1?</a></p><h3>DMVPN (Dynamic Multipoint VPN) Introduced by Cisco in late 2000 is a routing technology you can use to build a VPN network with multiple sites (spokes) without having to statically configure all devices. It’s a “hub and spoke” network, where the spokes will, can communicate with each other directly without having to go through the hub. Encryption is supported through IPsec which makes DMVPN a popular choice for connecting different sites using regular Internet connections. It’s a great backup or alternative to private networks like MPLS VPN.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/0*iw3_JORNh41_XESi.png" /></figure><p>This technology has been developed to address the need for automatically created VPN tunnels when dynamic IP addresses on the spokes are in use. This pure hub-and-spoke topology where all branches may communicate with each other securely through the hub.</p><p>There are four topics you need to know.</p><p>Multipoint GRE (mGRE)</p><p>NHRP (Next Hop Resolution Protocol)</p><p>Routing (RIP, EIGRP, OSPF, BGP, etc.)</p><p>IPsec (not required but recommended)</p><h3>Multipoint GRE (mGRE)</h3><p>Our regular GRE tunnels are point-to-point and don’t scale well. It becomes messy quickly so much point-to-point tunnels. but When we use GRE Multipoint, there will be only one tunnel interface on each router. mGRE interfaces do not have a tunnel destination. It keeps costs low, minimizing configuration complexity, and increasing flexibility. Multipoint GRE(Mgre) Uses tunnel source and tunnel mode (mgre). the Tunnel can have many endpoints by using a single tunnel interface. The endpoint can be configured as GRE or MGRE and Mapping is done by NHRP Protocol.</p><h3>NHRP (Next Hop Resolution Protocol)</h3><p>We want something which can help our router to figure out what the public IP address is of the other router, we do this with the help of a protocol called NHRP (Next Hop Resolution Protocol). Next hop resolution protocol (NHRP) Maps the tunnel IP with NBMA address (public IP ) (static or dynamic). NHRP Provides layer 2 address resolution protocol and caching services similar to ARP and inverse ARP. All it does is build a dynamic database store on the hub with information about spokes IP addresses.</p><h3>How NHRP works:</h3><ul><li>One router will be the NHRP server next-hop server (NHS).</li><li>All other routers will be the NHRP client’s next-hop client (NHC).</li><li>NHRP clients register themselves with the NHRP server and report their public IP address NHC sends a query to the NHS if they want to communicate with another NHC.</li><li>The NHRP server keeps track of all public IP addresses in its cache, NHS acts as a mapping agent and stores all registered mappings NHS reply to queries made by NHC.</li><li>When one router wants to tunnel something to another router, it will request the NHRP server for the public IP address of the other router.</li></ul><p>DMVPN has different three versions. we call phases.</p><p>Phase 1</p><p>Phase 2</p><p>Phase 3</p><p>DMVPN phase 1</p><p>Phase 1</p><p>before we started I want to let you know Phase 1 is Not used nowadays, In phase 1 we use NHRP so that spokes can register themselves with the hub (NHRP needed for spokes to register with hub). The hub is the only router that is using a multipoint GRE (mGRE) interface, all spokes will be using regular point-to-point GRE tunnel interfaces.No spokes hub and spokes topology were dynamic IP address on the spokes may be used. All your traffic goes through the hub. This means that there will be no direct spoke-to-spoke communication; all traffic has to go through the hub.</p><p>So our traffic has to go through the hub, our routing configuration will be quite simple. Spoke routers only need a summary or default route to the hub to reach other spoke routers.</p><p><em>DMVPN Phase 2 and 3 we will talk about in the next chapter.</em></p><p>let’s see the configuration:</p><p>Topology:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*3-K6i0HZ_d_hmpqn.png" /></figure><p>Goal:</p><ul><li>configure the topology as per the diagram</li><li>assign the IP addresses to their port as per the topology</li><li>configure static routing on router 2</li><li>configure default routing on router 1 3 4</li><li>configure DMVPN Phase 1 on router 1, 3 and 4</li><li>configure router 1 Hub and router 3 and 4 should be spokes routers</li><li>configure tunnel interfaces 192.168.1.0/24</li><li>configure NHRP using Stating mapping.</li></ul><p>R1(config)#interface serial 4/0</p><p>R1(config-if)#ip address 1.1.1.1 255.0.0.0</p><p>R1(config-if)#no shutdown</p><p>R1(config-if)#ip address 10.1.1.1 255.0.0.0</p><p>R1(config-if)#no shutdown</p><p>R1(config-if)#no keepalive</p><p>R1(config-if)#exit</p><p>R2(config)#interface serial 4/0</p><p>R2(config-if)#ip address 1.1.1.2 255.0.0.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#interface serial 4/1</p><p>R2(config-if)#ip address 3.3.3.1 255.0.0.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#interface serial 4/2</p><p>R2(config-if)#ip address 4.4.4.1 255.0.0.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#interface fastethernet 0/0</p><p>R2(config-if)#ip address 20.1.1.1 255.0.0.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#no keepalive</p><p>R2(config-if)#exit</p><p>R3(config)#interface serial 4/1</p><p>R3(config-if)#ip address 3.3.3.2 255.0.0.0</p><p>R3(config-if)#no shutdown</p><p>R3(config-if)#interface fastethernet 0/0</p><p>R3(config-if)#ip address 30.1.1.1 255.0.0.0</p><p>R3(config-if)#no shutdown</p><p>R3(config-if)#no keepalive</p><p>R3(config-if)#exit</p><p>R4(config)#interface serial 4/2</p><p>R4(config-if)#ip address 4.4.4.2 255.0.0.0</p><p>R4(config-if)#no shutdown</p><p>R4(config-if)#interface fastethernet 0/0</p><p>R4(config-if)#ip address 40.1.1.1 255.0.0.0</p><p>R4(config-if)#no shutdown</p><p>R4(config-if)#no keepalive</p><p>R4(config-if)#exit</p><p>R1#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 10.1.1.1 YES manual up up</p><p>Serial4/0 1.1.1.1 YES manual up up</p><p>R2#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 20.1.1.1 YES manual up up</p><p>Serial4/0 1.1.1.2 YES manual up up</p><p>Serial4/1 3.3.3.1 YES manual up up</p><p>Serial4/2 4.4.4.1 YES manual up up</p><p>R3#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 30.1.1.1 YES manual up up</p><p>Serial4/1 3.3.3.2 YES manual up up</p><p>R4#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 40.1.1.1 YES manual up up</p><p>Serial4/2 4.4.4.2 YES manual up up</p><p>R1(config)#ip route 0.0.0.0 0.0.0.0 serial 4/0</p><p>R1(config)#exit</p><p>R2(config)#ip route 1.0.0.0 255.0.0.0 serial 4/0</p><p>R2(config)#ip route 10.0.0.0 255.0.0.0 serial 4/0</p><p>R2(config)#ip route 30.0.0.0 255.0.0.0 serial 4/1</p><p>R2(config)#ip route 3.0.0.0 255.0.0.0 serial 4/1</p><p>R2(config)#ip route 4.0.0.0 255.0.0.0 serial 4/2</p><p>R2(config)#ip route 40.0.0.0 255.0.0.0 serial 4/2</p><p>R2(config)#exit</p><p>R3(config)#ip route 0.0.0.0 0.0.0.0 serial 4/1</p><p>R3(config)#exit</p><p>R4(config)#ip route 0.0.0.0 0.0.0.0 serial 4/2</p><p>R4(config)#exit</p><p>R1#show ip route static</p><p>Gateway of last resort is 0.0.0.0 to network 0.0.0.0</p><p><strong>S* 0.0.0.0/0 is directly connected, Serial4/0</strong></p><p>R2#show ip route static</p><p>Gateway of last resort is not set</p><p><strong>S 10.0.0.0/8 is directly connected, Serial4/0</strong></p><p><strong>S 30.0.0.0/8 is directly connected, Serial4/1</strong></p><p><strong>S 40.0.0.0/8 is directly connected, Serial4/2</strong></p><p>R3#show ip route static</p><p>Gateway of last resort is 0.0.0.0 to network 0.0.0.0</p><p><strong>S* 0.0.0.0/0 is directly connected, Serial4/1</strong></p><p>R4#show ip route static</p><p>Gateway of last resort is 0.0.0.0 to network 0.0.0.0</p><p><strong>S* 0.0.0.0/0 is directly connected, Serial4/2</strong></p><p><strong>R1(config)#interface tunnel 999</strong></p><p><strong>R1(config-if)#ip address 192.168.1.1 255.255.255.0</strong></p><p><strong>R1(config-if)#tunnel source 1.1.1.1</strong></p><p><strong>R1(config-if)#tunnel mode GRE multipoint</strong></p><p><strong>R1(config-if)#ip NHRP network-id 01</strong></p><p><strong>R1(config-if)#ip NHRP map 192.168.1.2 3.3.3.2</strong></p><p><strong>R1(config-if)#ip NHRP map 192.168.1.3 4.4.4.2</strong></p><p><strong>R1(config-if)#exit</strong></p><p>R3(config)#interface tunnel 999</p><p>R3(config-if)#ip address 192.168.1.2 255.255.255.0</p><p>R3(config-if)#tunnel source 3.3.3.2</p><p>R3(config-if)#tunnel destination 1.1.1.1</p><p>R3(config-if)#ip NHRP network-id 02</p><p>R3(config-if)#ip NHRP map 192.168.1.1 1.1.1.1</p><p>R3(config-if)#exit</p><p><strong>R4(config)#interface tunnel 999</strong></p><p><strong>R4(config-if)#ip address 192.168.1.3 255.255.255.0</strong></p><p><strong>R4(config-if)#tunnel source 4.4.4.2</strong></p><p><strong>R4(config-if)#tunnel destination 1.1.1.1</strong></p><p><strong>R4(config-if)#ip NHRP network-id 03</strong></p><p><strong>R4(config-if)#ip NHRP map 192.168.1.1 1.1.1.1</strong></p><p><strong>R4(config-if)#exit</strong></p><p><strong>R4(config)#end</strong></p><p>R1#show ip nhrp</p><p>192.168.1.2/32 via 192.168.1.2</p><p>Tunnel999 created 00:44:20, never expire</p><p>Type: static, Flags: used</p><p>NBMA address: 3.3.3.2</p><p>192.168.1.3/32 via 192.168.1.3</p><p>Tunnel999 created 00:44:04, never expire</p><p>Type: static, Flags: used</p><p>NBMA address: 4.4.4.2</p><p><strong>R3#show ip NHRP</strong></p><p><strong>192.168.1.1/32 via 192.168.1.1</strong></p><p><strong>Tunnel999 created 00:29:11, never expire</strong></p><p><strong>Type: static, Flags:</strong></p><p><strong>NBMA address: 1.1.1.1</strong></p><p><strong>R4#show ip NHRP</strong></p><p><strong>192.168.1.1/32 via 192.168.1.1</strong></p><p><strong>Tunnel999 created 00:23:36, never expire</strong></p><p><strong>Type: static, Flags:</strong></p><p><strong>NBMA address: 1.1.1.1</strong></p><p>R4#traceroute 192.168.1.1</p><p>Type escape sequence to abort.</p><p>Tracing the route to 192.168.1.1</p><p>VRF info: (vrf in name/id, vrf out name/id)</p><p>1 192.168.1.1 1616 msec 92 msec 36 msec</p><p>R4#traceroute 192.168.1.2</p><p>Type escape sequence to abort.</p><p>Tracing the route to 192.168.1.2</p><p>VRF info: (vrf in name/id, vrf out name/id)</p><p>1 192.168.1.1 12 msec 48 msec 40 msec</p><p>2 192.168.1.2 700 msec 328 msec 84 msec</p><p>R3#traceroute 192.168.1.1</p><p>Type escape sequence to abort.</p><p>Tracing the route to 192.168.1.1</p><p>VRF info: (vrf in name/id, vrf out name/id)</p><p>1 192.168.1.1 80 msec 72 msec 72 msec</p><p>R3#traceroute 192.168.1.3</p><p>Type escape sequence to abort.</p><p>Tracing the route to 192.168.1.3</p><p>VRF info: (vrf in name/id, vrf out name/id)</p><p>1 192.168.1.1 72 msec 56 msec 96 msec</p><p>2 192.168.1.3 240 msec 188 msec 188 msec</p><p>R1#traceroute 192.168.1.2</p><p>Type escape sequence to abort.</p><p>Tracing the route to 192.168.1.2</p><p>VRF info: (vrf in name/id, vrf out name/id)</p><p>1 192.168.1.2 8 msec 72 msec 96 msec</p><p>R1#traceroute 192.168.1.3</p><p>Type escape sequence to abort.</p><p>Tracing the route to 192.168.1.3</p><p>VRF info: (vrf in name/id, vrf out name/id)</p><p>1 192.168.1.3 72 msec 100 msec 100 msec</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abff7917acc4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Network Tunneling and how to configure Generic Routing Encapsulation (GRE) Tunnels?]]></title>
            <link>https://edgarcf.medium.com/what-is-network-tunneling-and-how-to-configure-generic-routing-encapsulation-gre-tunnels-1c49abda41d1?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c49abda41d1</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[ccna]]></category>
            <category><![CDATA[ccnp]]></category>
            <category><![CDATA[ccie]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sat, 23 Mar 2024 06:07:28 GMT</pubDate>
            <atom:updated>2024-03-23T06:07:28.558Z</atom:updated>
            <content:encoded><![CDATA[<h3>ccnaWhat is Network Tunneling and how to configure Generic Routing Encapsulation (GRE) Tunnels?</h3><p><a href="https://mpls.internetworks.in/2021/02/what-is-network-tunneling-and-how-to.html">What is Network Tunneling and how to configure Generic Routing Encapsulation (GRE) Tunnels?</a></p><p><strong>Generic Routing Encapsulation (GRE) is a network tunneling protocol developed by Cisco Systems that can encapsulate a wide variety of network layer protocols inside virtual point-to-point links or point-to-multipoint links over an Internet Protocol network.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/0*0-EDFYp52yA7lbdM.png" /></figure><p><strong>When do we use the GRE?</strong></p><p>GRE is used when packets need to be sent from one network to another over the internet.</p><p><strong>Generic Routing Encapsulation (GRE) has some disadvantages</strong>:-</p><p>GRE tunnel is an encapsulation protocol and does not perform any encryption.</p><p>When we create a GRE point-to-point tunnel without any encryption is extremely risky as sensitive data can easily be extracted from the tunnel and misused by others. ( <strong><em>That’s why we used IPSec to add an encryption layer and secure the GRE tunnel with the help of IPSec we get army-level encryption</em></strong>).</p><p>Classic GRE tunnel is a point-to-point, Manual tunnel, Not scalable, Static IP on all endpoints</p><p>GRE tunnel uses a ‘tunnel’ interface a logical interface configured on the router with an IP address where packets are encapsulated and decapsulated as they enter or exit the GRE tunnel.</p><p>All tunnel interfaces of participated routers must always be configured with an IP address that is not used anywhere else in the network.Each tunnel interface is assigned an IP address within the same network as other Tunnel interfaces. Before you configure you must adjust (MTU) maximum transfer unit and MSS maximum segment size.</p><p>Let’s see the configuration:-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*SQDbe8G-KNWGJ4V1Jgufyw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c49abda41d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Classification and marking? What is IP Precedence and DSCP Values? What are AF and EF?]]></title>
            <link>https://edgarcf.medium.com/what-is-classification-and-marking-what-is-ip-precedence-and-dscp-values-what-are-af-and-ef-710b6274516c?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/710b6274516c</guid>
            <category><![CDATA[ccna]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[ccnp]]></category>
            <category><![CDATA[cisco]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 12:16:53 GMT</pubDate>
            <atom:updated>2023-12-03T12:16:53.880Z</atom:updated>
            <content:encoded><![CDATA[<h3>Classification and Marking</h3><p>Classification and marking is the process of identifying the priority of each packet. This is the first step of QoS control and should be done near the source hosts. classification is the process of identifying and categorizing traffic into classes, typically based upon incoming interface IP precedence DSCP Source or Destination address application classification is the most fundamental QoS building block. Without classification, all packets are treated the same.</p><p><a href="https://qos.internetworks.in/2021/10/what-is-classification-and-marking-what.html">https://qos.internetworks.in/2021/10/what-is-classification-and-marking-what.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/0*jH68elc-floccWB7.png" /></figure><p>The table lists the criteria of classification</p><h3>Marking</h3><p>marking is the QoS feature component that colors a packet so it can be identified and distinguished from other packets in QoS treatment. commonly used markers:</p><p>link-layer: COS (ISL,802.1Q), MPLS EXP bits, frame relay</p><p>network layer:DSCP, IP precedence</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/0*zxdyN3xBc3XycK8q.png" /></figure><p><strong>Layer 2 and Layer 3 Header Marking</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*lOzIT5mGX6rSyVVD.png" /></figure><h3>let’s take a look at Layer 3 IPv4 packet ToS Byte.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/0*mdSidF-wIyZYFS7d.png" /></figure><p>In the starting, the ToS byte defines like this ☝.</p><ul><li>The starting 3 bits are used to define IP precedence. The higher the value means the higher the priority of IP Packets.</li><li>Rests of the bits are called the Type of Service. ToS bits are used to assign delay, throughput, and reliability.</li></ul><p><strong>let’s see the picture for better understanding.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*x7z6gD31gdQu3qMq.jpg" /></figure><p>But the “type of service” bits which are a specified delay, throughput, and reliability have never been really been used. Only the IP precedence bits are used to assign a priority to the IP packets. do not confuse by the name ToS. 0–7 is called ToS byte and 4–7 bits is called ToS bits (Type of Service). look at the picture below👇. however, ToS bits (Type of Service) have never been used only the IP Precedence is in use for prioritizing the IP packets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/0*EIIcPSYn7A7hV6CG.png" /></figure><p><strong>Let’s talks about what we actually using nowadays?</strong></p><p>DS field (Differentiated Services) now we called ToS byte to DS field the name is changed.</p><p><strong>DSCP (DiffServ Code Point)</strong> provides a 6-bit field for QoS marking in which color code (CS) is also called DSCP value. CS or DSCP 6 bits among which 3 bits are the same as IP precedence, and the other 3 bits are ToS fields. Thus, the DSCP value range is 0 to 63. The graph below shows the DSCP and IP precedence bits:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*j6r5wQzKDXMX42yq.jpg" /></figure><p>DSCP value is also known as Per-Hop Behavior PHB is that packets that are marked with a certain codepoint will receive a certain QoS treatment (for example queuing, policing, or shaping). The default Per-Hop Behavior PHB means that we have a packet that is marked with a DSCP value of 000000. This packet should be treated as “best-effort”.</p><p>.</p><p><strong>Now there are three types of defined PHBs:</strong></p><p><strong>Best-Effort (BE or DSCP 0)</strong> is the packet that is marked with a DSCP value of 000000. This packet should be treated as “best-effort”.</p><p><strong>Assured Forwarding (AF)</strong> Assured forwarding allows you to provide assurance of delivery as long as the traffic does not exceed some subscribed rate.</p><p><strong>Expedited Forwarding (EF)</strong>.is that any traffic class with EF’s related DSCP is given highest priority</p><p>let’s see CS, AF, EF, and Best effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/0*YfhHqMPjCwPd3Vum.jpg" /></figure><p>The first bits are called CS higher number means high priority (same as IP Precedence) and the rest of the 3 bits are called AF higher number means high drop probability assured forwarding bits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/170/0*ATV0u0CKBMo1W-KC.jpg" /></figure><p>What are CS and AF?</p><p>CS 1 + AF 1 = 001 0100</p><p>CS 2 + AF 2 = 010 1000</p><p>CS 3 + AF 3 = 011 0110</p><p>How this works?</p><p>let’s take an example we have FastEthernet 0/0 and the queue is full and the router wants drop packets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*wjnwqnDdKbHfbvRG.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=710b6274516c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is NBAR (network- based application recognition), classification QOS How to configure NBAR?]]></title>
            <link>https://edgarcf.medium.com/what-is-nbar-network-based-application-recognition-classification-qos-how-to-configure-nbar-1b1e0f633139?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b1e0f633139</guid>
            <category><![CDATA[ccie]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[ccna]]></category>
            <category><![CDATA[ccnp]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 11:11:48 GMT</pubDate>
            <atom:updated>2023-12-03T11:11:48.543Z</atom:updated>
            <content:encoded><![CDATA[<p>When we implement <a href="https://www.blogger.com/blog/post/edit/8044180635915599428/4647352564377947787#">Quality of Service (QoS</a>) the first step is classification, by default our router does not care about what kind of IP packets it is. Our router just looks at the routing table to find the correct destination IP address and forwards.</p><p>When we configure QoS technologies like queuing, policing, or shaping before doing first we have to identify what kind of traffic is running on our routers so we can figure out what kind of application it belongs to. This is classification.</p><p><a href="https://www.blogger.com/blog/post/edit/8044180635915599428/4647352564377947787#">What is Quality of Service (QOS)?</a></p><p><a href="https://www.blogger.com/blog/post/edit/8044180635915599428/4647352564377947787#">What is Modular Quality of service CLI (MQC)?</a></p><p><a href="https://www.blogger.com/blog/post/edit/8044180635915599428/4647352564377947787#">What is Classification and marking? What are IP Precedence and DSCP Values? What is AF and EF?</a></p><p>Once we identify our traffic (classify). Now we can mark and apply QoS policy to it.</p><p>There are a few methods on IOS routers for classification:</p><p><strong>Header inspection</strong> It is a simple classification method and it works really good but has some disadvantages. Let’s say we configure our router all the applications run TCP and its destination is HTTP port 80. Anyhow some other applications are also using TCP port 80. The router is going to perform the same action on both.</p><p><strong>Payload inspection </strong>This is reliable and it will do deep packet inspection. This method will look at the content of the payload and recognize the application. On our Cisco IOS, this is done with the help of NBAR (network-based application recognition)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*UqnIPCM9H_FZlCWA.png" /></figure><p>NBAR router inspects incoming IP packets and matches them with attributes and signatures in the (packet description language module) PDLM. NBAR is commonly used to block websites and it’s very popular for classification</p><p>NBAR classification modern client-server and web-based applications. Perform identification of applications and protocols (layers 4–7) NBAR Performs protocol discovery and provides traffic statistics. NBAR enables downstream action based on QoS policies via (RED), class-based queuing, and policing. New applications are easily supported by loading a PDLM.</p><p>NBAR can classify applications that use Statically assigned TCP and UDP port numbers. Non-UDP and non-TCP IP protocols. Dynamically assigned TCP and UDP port numbers negotiated during connection establishing (requires stateful inspection)</p><p><strong><em>NBAR2 is the next generation of NBAR, enhancing the application recognition engine to support more than 1000 applications. NBAR2 functionality requires an advanced license</em></strong></p><p><strong>Packet description language module</strong></p><p>PDLMs allow NBAR to recognize new protocol-matching text patterns in data packets without requiring a new Cisco IOS software image or a router reload. An external PDLM can be loaded at run time to extend the NBAR list of recognized protocols. PDLMs can also be used to enhance an existing protocol recognition capability. PDLMs must be produced by Cisco engineers.</p><p><strong>NBAR Protocol Discovery</strong></p><p>Analyze application traffic patterns in real time and discover which traffic is running on the network. Provides bidirectional, per-interface, and per-protocol statistics. Important monitoring tool supported by Cisco QoS management tools Generates real-time application statistics Provides traffic distribution information at key network locations.</p><p>let’s see the configuration: — <a href="https://qos.internetworks.in/2021/10/what-is-of-nbar-network-based.html">https://qos.internetworks.in/2021/10/what-is-of-nbar-network-based.html</a></p><p>Topology:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*GGkd2y-1Imm8Nn9m" /></figure><ul><li>configure the topology as per our diagram</li><li>assign the IP address to their respective interfaces</li><li>configure EIGRP AS65100</li><li>configure outbound MQC</li><li>configure IP precedence of 1 to ICMP packets, IP precedence of 2 HTTP packets and configure DSCP EF TO VoIP.</li></ul><p>R1(config)#interface serial 4/0</p><p>R1(config-if)#ip address 192.168.10.1 255.255.255.0</p><p>R1(config-if)#no shutdown</p><p>R1(config-if)#exit</p><p>R1(config)#interface fastEthernet 0/0</p><p>R1(config-if)#ip address 10.1.1.1 255.0.0.0</p><p>R1(config-if)#no keepalive</p><p>R1(config-if)#no shutdown</p><p>R1(config-if)#exit</p><p>R1#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 10.1.1.1 YES manual up up</p><p>Serial4/0 192.168.10.1 YES manual up up</p><p>R2(config)#interface serial 4/0</p><p>R2(config-if)#ip address 192.168.10.2 255.255.255.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#exit</p><p>R2(config)#interface fastEthernet 0/0</p><p>R2(config-if)#ip address 20.1.1.1 255.0.0.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#no keepalive</p><p>R2(config-if)#exit</p><p>R2#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 20.1.1.1 YES manual up up</p><p>Serial4/0 192.168.10.2 YES manual up up</p><p>R1(config)#router eigrp 65100</p><p>R1(config-router)#network 192.168.10.0</p><p>R1(config-router)#network 10.0.0.0</p><p>R1(config-router)#no auto-summary</p><p>R1(config-router)#exit</p><p>R2(config)#router eigrp 65100</p><p>R2(config-router)#network 192.168.10.0</p><p>R2(config-router)#network 192.168.10.0</p><p>R2(config-router)#network 20.1.1.1</p><p>R2(config-router)#no auto-summary</p><p>R2(config-router)#exit</p><p>*Oct 11 18:22:53.123: %DUAL-5-NBRCHANGE: EIGRP-IPv4 65100: Neighbor 192.168.10.1 (Serial4/0) is up: new adjacency</p><p>R1#show ip route eigrp</p><p>Codes: L — local, C — connected, S — static, R — RIP, M — mobile, B — BGP</p><p>D — EIGRP, EX — EIGRP external, O — OSPF, IA — OSPF inter area</p><p>N1 — OSPF NSSA external type 1, N2 — OSPF NSSA external type 2</p><p>E1 — OSPF external type 1, E2 — OSPF external type 2</p><p>i — IS-IS, su — IS-IS summary, L1 — IS-IS level-1, L2 — IS-IS level-2</p><p>ia — IS-IS inter area, * — candidate default, U — per-user static route</p><p>o — ODR, P — periodic downloaded static route, H — NHRP, l — LISP</p><p>+ — replicated route, % — next hop override</p><p>Gateway of last resort is not set</p><p><strong>D 20.0.0.0/8 [90/2172416] via 192.168.10.2, 00:00:21, Serial4/0</strong></p><p>R1#show ip eigrp neighbors</p><p>EIGRP-IPv4 Neighbors for AS(65100)</p><p>H Address Interface Hold Uptime SRTT RTO Q Seq</p><p>(sec) (ms) Cnt Num</p><p><strong>0 192.168.10.2 Se4/0 13 00:00:31 54 324 0 4</strong></p><p>R2#show ip route eigrp</p><p>Codes: L — local, C — connected, S — static, R — RIP, M — mobile, B — BGP</p><p>D — EIGRP, EX — EIGRP external, O — OSPF, IA — OSPF inter area</p><p>N1 — OSPF NSSA external type 1, N2 — OSPF NSSA external type 2</p><p>E1 — OSPF external type 1, E2 — OSPF external type 2</p><p>i — IS-IS, su — IS-IS summary, L1 — IS-IS level-1, L2 — IS-IS level-2</p><p>ia — IS-IS inter area, * — candidate default, U — per-user static route</p><p>o — ODR, P — periodic downloaded static route, H — NHRP, l — LISP</p><p>+ — replicated route, % — next hop override</p><p>Gateway of last resort is not set</p><p>D 10.0.0.0/8 [90/2172416] via 192.168.10.1, 00:00:42, Serial4/0</p><p>R2#show ip eigrp neighbors</p><p>EIGRP-IPv4 Neighbors for AS(65100)</p><p>H Address Interface Hold Uptime SRTT RTO Q Seq</p><p>(sec) (ms) Cnt Num</p><p>0 192.168.10.1 Se4/0 11 00:00:46 44 264 0 3</p><p>R1(config)#class-map HTTP</p><p>R1(config-cmap)#match protocol http</p><p>R1(config-cmap)#exit</p><p>R1(config)#class-map VoIP</p><p>R1(config-cmap)#match access-group name VOICE</p><p>R1(config-cmap)#exit</p><p>R1(config)#class-map ICMP</p><p>R1(config-cmap)#match protocol icmp</p><p>R1(config-cmap)#exit</p><p>R1(config)#ip access-list extended VOICE</p><p>R1(config-ext-nacl)#permit udp any any range 16380 32760</p><p>R1(config-ext-nacl)#exit</p><p>R1(config)#policy-map INTERNETWORKS</p><p>R1(config-pmap)#class ICMP</p><p>R1(config-pmap-c)#set ip precedence 1</p><p>R1(config-pmap-c)#exit</p><p>R1(config-pmap)#class HTTP</p><p>R1(config-pmap-c)#set ip precedence 2</p><p>R1(config-pmap-c)#exit</p><p>R1(config-pmap)#class VoIP</p><p>R1(config-pmap-c)#set ip dscp ef</p><p>R1(config-pmap-c)#exit</p><p>R1(config-pmap)#exit</p><p>R1(config)#exit</p><p>R1#show run policy-map</p><p>Building configuration…</p><p>Current configuration : 132 bytes</p><p>!</p><p>policy-map <strong>INTERNETWORKS</strong></p><p><strong>class ICMP</strong></p><p><strong>set ip precedence 1</strong></p><p><strong>class HTTP</strong></p><p><strong>set ip precedence 2</strong></p><p><strong>class VoIP</strong></p><p><strong>set ip dscp ef</strong></p><p>!</p><p>end</p><p>R1#show run class-map</p><p>Building configuration…</p><p>Current configuration : 156 bytes</p><p>!</p><p><strong>class-map match-all ICMP</strong></p><p><strong>match protocol icmp</strong></p><p><strong>class-map match-all HTTP</strong></p><p><strong>match protocol http</strong></p><p><strong>class-map match-all VoIP</strong></p><p><strong>match access-group name VOICE</strong></p><p>end</p><p>R1(config)#interface serial 4/0</p><p>R1(config-if)#service-policy output INTERNETWORKS</p><p>R1(config-if)#EXIT</p><p>R1(config)#END</p><p>R1#show policy-map interface serial 4/0</p><p>Serial4/0</p><p>Service-policy output: INTERNETWORKS</p><p>Class-map:<strong> ICMP (match-all)</strong></p><p><strong>0 packets, 0 bytes</strong></p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol <strong>icmp</strong></p><p><strong>QoS Set</strong></p><p><strong>precedence </strong>1</p><p>Packets marked 0</p><p>Class-map: HTTP (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol http</p><p>QoS Set</p><p>precedence 2</p><p>Packets marked 0</p><p>Class-map: VoIP (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group name VOICE</p><p>QoS Set</p><p>dscp ef</p><p>Packets marked 0</p><p>Class-map: class-default (match-any)</p><p>7 packets, 368 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>R1#ping 20.1.1.1 source 10.1.1.1<strong> repeat 16</strong></p><p>Type escape sequence to abort.</p><p>Sending 16, 100-byte ICMP Echos to 20.1.1.1, timeout is 2 seconds:</p><p>Packet sent with a source address of 10.1.1.1</p><p>!!!!!!!!!!!!!!!!</p><p>Success rate is 100 percent (16/16), round-trip min/avg/max = 32/46/52 ms</p><p>R1#show policy-map interface serial 4/0</p><p>Serial4/0</p><p>Service-policy output: INTERNETWORKS</p><p>Class-map: ICMP (match-all)</p><p><strong>16 packets,</strong> 1664 bytes</p><p>5 minute offered rate 1000 bps, drop rate 0000 bps</p><p>Match: protocol icmp</p><p>QoS Set</p><p>precedence 1</p><p>Packets marked 16</p><p>Class-map: HTTP (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol http</p><p>QoS Set</p><p>precedence 2</p><p>Packets marked 0</p><p>Class-map: VoIP (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group name VOICE</p><p>QoS Set</p><p>dscp ef</p><p>Packets marked 0</p><p>Class-map: class-default (match-any)</p><p>20 packets, 1313 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>R1#ping 20.1.1.1 source 10.1.1.1 <strong>repeat 4</strong></p><p>Type escape sequence to abort.</p><p>Sending 4, 100-byte ICMP Echos to 20.1.1.1, timeout is 2 seconds:</p><p>Packet sent with a source address of 10.1.1.1</p><p>!!!!</p><p>Success rate is 100 percent (4/4), round-trip min/avg/max = 44/49/52 ms</p><p>R1#show policy-map interface serial 4/0</p><p>Serial4/0</p><p>Service-policy output: INTERNETWORKS</p><p>Class-map: <strong>ICMP (match-all)</strong></p><p><strong>20 packets</strong>, 2080 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol icmp</p><p>QoS Set</p><p>precedence 1</p><p>Packets marked 20</p><p>Class-map: HTTP (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol http</p><p>QoS Set</p><p>precedence 2</p><p>Packets marked 0</p><p>Class-map: VoIP (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group name VOICE</p><p>QoS Set</p><p>dscp ef</p><p>Packets marked 0</p><p>Class-map: class-default (match-any)</p><p>26 packets, 1617 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b1e0f633139" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the queue? How do software and hardware queues work? Congestion management using Queuing.]]></title>
            <link>https://edgarcf.medium.com/what-is-the-queue-how-do-software-and-hardware-queues-work-congestion-management-using-queuing-dedfdd8ffae7?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/dedfdd8ffae7</guid>
            <category><![CDATA[qos]]></category>
            <category><![CDATA[ccie]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[ccna]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 08:51:50 GMT</pubDate>
            <atom:updated>2023-12-03T08:51:50.705Z</atom:updated>
            <content:encoded><![CDATA[<p>Routers use a queue to store traffic until it can be processed or serialized. switches and router interfaces have ingress (inbound) queues and egress (outbound) queues. An ingress (inbound) queue stores packets until the switch or router CPU can forward the data to the appropriate interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/0*297mvpuMUT6ry87l" /></figure><p>Cisco routers can be configured to perform well queuing for packets that are waiting to exit an interface. Queues are buffers in devices that hold data to be processed. Queues provide bandwidth reservation and prioritization of traffic as it enters or leaves a network device. If the queues are not emptied, they overflow and drop traffic.</p><p>We have two types of queues and fancy queueing QoS tools like <strong>CBWFQ</strong> &amp; <strong>LLQ</strong>.</p><p><strong>Hardware queue</strong></p><p><strong>Software queue </strong><a href="https://qos.internetworks.in/2021/10/what-is-queue-how-software-and-hardware.html">https://qos.internetworks.in/2021/10/what-is-queue-how-software-and-hardware.html</a></p><p><strong>Hardware queues provide the following features:</strong></p><ul><li>When an interface finish sending a packet, the next packet from the hardware queue can be encoded and sent out the interface, without ensuring a software interrupt to the CPU — ensuring full use of interface bandwidth.</li><li>Always use FIFO logic first in first out.</li><li>Cannot be affected by IOS queuing tools.</li><li>IOS automatically shrinks the length of the hardware queue to a smaller length than the default when a queuing tool is present.</li><li>Short hardware queue length means packets are more likely to be in the controllable software queues, giving the software queuing more control of the traffic leaving the interface.</li><li>The only function of a hardware queue that can be manipulated is the length of the queue.</li></ul><p><strong>Congestion management using Queuing</strong></p><p>Congestion can occur at any point in the network where there are points of speed mismatches or aggregation, Speed mismatches are the most typical cause of congestion. when the packets traveling from LAN to WAN. Generally, a full hardware queue indicates interface congestion, and software queuing is used to manage it. The software queuing system can be selected and configured depending on the platform and cisco IOS version. Queuing manages congestion to provide bandwidth and delay guarantees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/0*TkWFq8gSNXqtgPfi" /></figure><p>Creation of queues. Assignment of packets to those queues based on the classification of the packets, and scheduling of the packets in a queue for transmission. Allow us to control congestion by determining the order in which packets are sent out an interface based on priorities assigned to those packets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dedfdd8ffae7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are LLQ (Low Latency Queuing) and CBWFQ (Class-Based Weighted Fair Queuing)?]]></title>
            <link>https://edgarcf.medium.com/what-are-llq-low-latency-queuing-and-cbwfq-class-based-weighted-fair-queuing-8b50b0d934dc?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b50b0d934dc</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[ccnp]]></category>
            <category><![CDATA[ccna]]></category>
            <category><![CDATA[ccie]]></category>
            <category><![CDATA[cisco]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 07:46:53 GMT</pubDate>
            <atom:updated>2023-12-03T07:46:53.924Z</atom:updated>
            <content:encoded><![CDATA[<h3>What are LLQ (Low Latency Queuing) and CBWFQ (Class-Based Weighted Fair Queuing)? How to configure LLQ and CBWFQ?</h3><h3>LLQ (Low Latency Queuing)</h3><h3>CBWFQ (Class-Based Weighted Fair Queuing)</h3><p>Cisco created CBWFQ and LLQ using some of the best concepts from legacy queuing methods. PQ and CQ as well as WFQ while adding several features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*V8-PRSriWl6nmwIr" /></figure><p>LLQ low-latency queuing is developed by Cisco and it provides strict priority queuing to CBWFQ (class-based weighted fair queueing. Low-latency queuing provides delay-sensitive data like VoIP traffic to be given more preferential treatment over other traffic by letting the data be dequeued and sent first.</p><p>CBWFQ (Class-Based Weighted Fair Queuing) it’s a scheduling mechanism that allows a minimum bandwidth guarantee when the network congestion occurs on an interface.</p><p>CBWFQ is used to provide traffic classes during times of network congestion at an interface. Each of the CBWFQ queues is assigned a weight, and the packets are treated from the queues based upon the weight of the queue.CBWFQ and LLQ both support 64 queues/classes and also have one special queue called the class-default queue. LLQ and CBWFQ are both tools that use MQC and NBAR for configuration. there is one drawback in CBWFQ is VoIP traffic suffers an unacceptable delay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*i3eiWYBNvizYvCc1" /></figure><p>Advantage of LLQ</p><p>LLQ provides all the benefits of CBWFQ (Class-Based Weighted Fair Queuing), including the capability of the user to queue and guarantees each queue an appropriate amount of bandwidth and to apply WRED to each of the queues (except to the strict-priority queue).</p><p>LLQ combines priority queuing and CBWFQ and provides Strict priority queueing for sensitive traffic like VoIP and video. LLQ also reduces latency/jitter for communications.</p><p>let’s see the configuration for a better understanding of LLQ and CBWFQ.</p><p>Topology:- <a href="https://qos.internetworks.in/2021/10/what-is-llq-low-latency-queuing-and.html">https://qos.internetworks.in/2021/10/what-is-llq-low-latency-queuing-and.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*NzVxzyqD9MHMoMeV" /></figure><p>Goal:-</p><ul><li>configure the topology as per the diagram above.</li><li>configure IP addresses to their ports</li><li>configure EIGRP AS 65120 and advertise directly connected interfaces.</li><li>configure CBWFQ tool on router 1</li><li>configure ICMP bandwidth 18 percent, FTP bandwidth 28 and HTTP bandwidth 38.</li><li>configure LLQ tool on router 3</li><li>configure VoIP priority 192, ICMP bandwidth 120, HTTP priority 10 and FTP priority 15.</li><li>The rest of the traffic use WFQ.</li></ul><p>R1(config)#interface serial 4/0</p><p>R1(config-if)#ip address 192.168.10.1 255.255.255.0</p><p>R1(config-if)#no shutdown</p><p>R1(config-if)#exit</p><p>R1(config)#interface fastEthernet 0/0</p><p>R1(config-if)#ip address 10.1.1.1 255.255.255.0</p><p>R1(config-if)#no shutdown</p><p>R1(config-if)#no keepalive</p><p>R1(config-if)#exit</p><p>R2(config)#interface serial 4/0</p><p>R2(config-if)#ip address 192.168.10.2 255.255.255.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#exit</p><p>R2(config)#interface fastEthernet 0/0</p><p>R2(config-if)#ip address 20.1.1.1 255.255.255.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#no keepalive</p><p>R2(config-if)#exit</p><p>R2(config)#interface serial 4/1</p><p>R2(config-if)#ip address 23.1.1.1 255.255.255.0</p><p>R2(config-if)#no shutdown</p><p>R2(config-if)#exit</p><p>R3(config)#interface serial 4/1</p><p>R3(config-if)#ip address 23.1.1.2 255.255.255.0</p><p>R3(config-if)#no shutdown</p><p>R3(config-if)#exit</p><p>R3(config)#interface fastEthernet 0/0</p><p>R3(config-if)#ip address 30.1.1.1 255.255.255.0</p><p>R3(config-if)#no keepalive</p><p>R3(config-if)#no shutdown</p><p>R3(config-if)#exit</p><p>R1(config)#router eigrp 65120</p><p>R1(config-router)#network 192.168.10.0</p><p>R1(config-router)#network 10.0.0.0</p><p>R1(config-router)#no auto-summary</p><p>R1(config-router)#exit</p><p>R2(config)#router eigrp 65120</p><p>R2(config-router)#network 192.168.10.0</p><p>R2(config-router)#network 192.168.10.0</p><p>R2(config-router)#network 20.0.0.0</p><p>R2(config-router)#network 23.1.1.0</p><p>R2(config-router)#no auto-summary</p><p>R2(config-router)#exit</p><p>R3(config)#router eigrp 65120</p><p>R3(config-router)#network 23.1.1.0</p><p>R3(config-router)#network 30.0.0.0</p><p>R3(config-router)#no auto-summary</p><p>R3(config-router)#exit</p><p>R1(config)#<strong>class-map ICMP-TRAFFIC</strong></p><p>R1(config-cmap)#<strong>match protocol icmp</strong></p><p>R1(config-cmap)#<strong>class-map HTTP-TRAFFIC</strong></p><p>R1(config-cmap)#<strong>match protocol http</strong></p><p>R1(config-cmap)#<strong>class-map FTP-TRAFFIC</strong></p><p>R1(config-cmap)#<strong>match protocol ftp</strong></p><p>R1(config-cmap)#<strong>exit</strong></p><p>R1(config)#<strong>policy-map CBWFQ-QUEUE</strong></p><p>R1(config-pmap)#<strong>class ICMP-TRAFFIC</strong></p><p>R1(config-pmap-c)#<strong>bandwidth percent 18</strong></p><p>R1(config-pmap-c)#<strong>class HTTP-TRAFFIC</strong></p><p>R1(config-pmap-c)#<strong>bandwidth percent 38</strong></p><p>R1(config-pmap-c)#<strong>exit</strong></p><p>R1(config-pmap)#<strong>policy-map CBWFQ-QUEUE</strong></p><p>R1(config-pmap)#<strong>class FTP-TRAFFIC</strong></p><p>R1(config-pmap-c)#<strong>bandwidth percent 28</strong></p><p>R1(config-pmap-c)#<strong>exit</strong></p><p>R1(config-pmap)#<strong>class class-default</strong></p><p>R1(config-pmap-c)#exit</p><p>R1(config-pmap)#exit</p><p>R1(config)#interface serial 4/0</p><p>R1(config-if)#<strong>service-policy output CBWFQ-QUEUE</strong></p><p>R1(config-if)#END</p><p>R1#show policy-map interface serial 4/0</p><p>Serial4/0</p><p>Service-policy output: CBWFQ-QUEUE</p><p>Class-map: ICMP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol icmp</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>bandwidth 18% (277 kbps)</p><p>Class-map: HTTP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol http</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>bandwidth 38% (586 kbps)</p><p>Class-map: FTP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol ftp</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>bandwidth 28% (432 kbps)</p><p>Class-map: class-default (match-any)</p><p>2 packets, 48 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 2/48</p><p>R1#show run policy-map</p><p>Building configuration…</p><p>Current configuration : 185 bytes</p><p>!</p><p>policy-map CBWFQ-QUEUE</p><p><strong>class ICMP-TRAFFIC</strong></p><p><strong>bandwidth percent 18</strong></p><p><strong>class HTTP-TRAFFIC</strong></p><p><strong>bandwidth percent 38</strong></p><p><strong>class FTP-TRAFFIC</strong></p><p><strong>bandwidth percent 28</strong></p><p><strong>class class-default</strong></p><p>!</p><p>end</p><p>R1#show run class-map</p><p>Building configuration…</p><p>Current configuration : 168 bytes</p><p>!</p><p><strong>class-map match-all FTP-TRAFFIC</strong></p><p><strong>match protocol ftp</strong></p><p><strong>class-map match-all ICMP-TRAFFIC</strong></p><p><strong>match protocol icmp</strong></p><p><strong>class-map match-all HTTP-TRAFFIC</strong></p><p><strong>match protocol http</strong></p><p><strong>end</strong></p><p><strong>FROM ROUTER 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*DrfEwoyXRBcV8dtn" /></figure><p><strong>FROM ROUTER 1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*S85S3AgfNBlN_pwa" /></figure><ul><li>configure LLQ tool on router 3</li></ul><p>R3(config)#<strong>ip access-list extended VoIP</strong></p><p>R3(config-ext-nacl)#<strong>permit udp any any range 16380 32770</strong></p><p>R3(config-ext-nacl)#exit</p><p>R3(config)#class-map <strong>ICMP-TRAFFIC</strong></p><p>R3(config-cmap)#<strong>match protocol icmp</strong></p><p>R3(config-cmap)#exit</p><p>R3(config)#class-map <strong>HTTP-TRAFFIC</strong></p><p>R3(config-cmap)#match protocol <strong>http</strong></p><p>R3(config-cmap)#exit</p><p>R3(config)#class-map <strong>FTP-TRAFFIC</strong></p><p>R3(config-cmap)#match protocol<strong> ftp</strong></p><p>R3(config-cmap)#exit</p><p>R3(config)#class-map <strong>VoIP-TRAFFIC</strong></p><p>R3(config-cmap)#match access-group name <strong>VoIP</strong></p><p>R3(config-cmap)#EXIT</p><p>R3(config)#policy-map <strong>LLQ</strong></p><p>R3(config-pmap)#class <strong>VoIP-TRAFFIC</strong></p><p>R3(config-pmap-c)#<strong>priority 190</strong></p><p>R3(config-pmap-c)#exit</p><p>R3(config-pmap)#class <strong>ICMP-TRAFFIC</strong></p><p>R3(config-pmap-c)#<strong>bandwidth 120</strong></p><p>R3(config-pmap-c)#exit</p><p>R3(config-pmap)#class <strong>HTTP-TRAFFIC</strong></p><p>R3(config-pmap-c)#<strong>priority 10</strong></p><p>R3(config-pmap-c)#exit</p><p>R3(config-pmap)#class <strong>FTP-TRAFFIC</strong></p><p>R3(config-pmap-c)#<strong>priority 15</strong></p><p>R3(config-pmap-c)#exit</p><p>R3(config-pmap)#class class-default</p><p>R3(config-pmap-c)#fair-queue</p><p>R3(config-pmap-c)#exit</p><p>R3(config-pmap)#exit</p><p>R3(config)#interface serial 4/1</p><p>R3(config-if)#service-policy output <strong>LLQ</strong></p><p>R3(config-if)#EXIT</p><p>R3(config)#END</p><p>R3#show policy-map interface serial 4/1</p><p>Serial4/1</p><p>Service-policy output: LLQ</p><p>queue stats for all priority classes:</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>Class-map: VoIP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group name V<strong>oIP</strong></p><p><strong>Priority: 190 kbps, burst bytes 4750, b/w exceed drops: 0</strong></p><p>Class-map: ICMP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: <strong>protocol icmp</strong></p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p><strong>bandwidth 120 kbps</strong></p><p>Class-map: HTTP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol http</p><p>Priority: 10 kbps, burst bytes 1500, b/w exceed drops: 0</p><p>Class-map: FTP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol ftp</p><p>Priority: 15 kbps, burst bytes 1500, b/w exceed drops: 0</p><p>Class-map: class-default (match-any)</p><p>5 packets, 280 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops/flowdrops) 0/0/0/0</p><p>(pkts output/bytes output) 5/280</p><p>Fair-queue: per-flow queue limit 16 packets</p><p>R3#show policy-map</p><p>Policy Map LLQ</p><p>Class VoIP-TRAFFIC</p><p>priority 190 (kbps)</p><p>Class ICMP-TRAFFIC</p><p>bandwidth 120 (kbps)</p><p>Class HTTP-TRAFFIC</p><p>priority 10 (kbps)</p><p>Class FTP-TRAFFIC</p><p>priority 15 (kbps)</p><p>Class class-default</p><p>fair-queue</p><p>R3#show run class-map</p><p>Building configuration…</p><p>Current configuration : 231 bytes</p><p>!</p><p>class-map match-all FTP-TRAFFIC</p><p>match protocol ftp</p><p>class-map match-all VoIP-TRAFFIC</p><p>match access-group name VoIP</p><p>class-map match-all ICMP-TRAFFIC</p><p>match protocol icmp</p><p>class-map match-all HTTP-TRAFFIC</p><p>match protocol http</p><p>end</p><p>R3#show run policy-map</p><p>Building configuration…</p><p>Current configuration : 197 bytes</p><p>!</p><p>policy-map LLQ</p><p>class VoIP-TRAFFIC</p><p>priority 190</p><p>class ICMP-TRAFFIC</p><p>bandwidth 120</p><p>class HTTP-TRAFFIC</p><p>priority 10</p><p>class FTP-TRAFFIC</p><p>priority 15</p><p>class class-default</p><p>fair-queue</p><p>!</p><p>end</p><p>R3#ping 10.1.1.1 source 30.1.1.1 repeat 11</p><p>Type escape sequence to abort.</p><p>Sending 11, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:</p><p>Packet sent with a source address of 30.1.1.1</p><p>!!!!!!!!!!!</p><p>Success rate is 100 percent (11/11), round-trip min/avg/max = 40/48/56 ms</p><p>R3#show policy-map interface serial 4/1</p><p>Serial4/1</p><p>Service-policy output: LLQ</p><p>queue stats for all priority classes:</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>Class-map: VoIP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group name VoIP</p><p>Priority: 190 kbps, burst bytes 4750, b/w exceed drops: 0</p><p>Class-map: ICMP-TRAFFIC (match-all)</p><p>16 packets, 1664 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol icmp</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 16/1664</p><p>bandwidth 120 kbps</p><p>Class-map: HTTP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol http</p><p>Priority: 10 kbps, burst bytes 1500, b/w exceed drops: 0</p><p>Class-map: FTP-TRAFFIC (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: protocol ftp</p><p>Priority: 15 kbps, burst bytes 1500, b/w exceed drops: 0</p><p>Class-map: class-default (match-any)</p><p>420 packets, 28159 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops/flowdrops) 0/0/0/0</p><p>(pkts output/bytes output) 420/28159</p><p>Fair-queue: per-flow queue limit 16 packets</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b50b0d934dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Modular Quality of Service CLI (MQC)?]]></title>
            <link>https://edgarcf.medium.com/what-is-modular-quality-of-service-cli-mqc-a3e6d8896bfe?source=rss-563571c76227------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3e6d8896bfe</guid>
            <category><![CDATA[ccnp]]></category>
            <category><![CDATA[ccie]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[ccna]]></category>
            <dc:creator><![CDATA[Edgar C Francis]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 07:21:10 GMT</pubDate>
            <atom:updated>2023-12-03T07:21:10.405Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.blogger.com/blog/post/edit/8044180635915599428/2640322190570442916#">Internetworks</a></p><p>The modular Quality of Service CLI (MQC) helps by defining a common set of configuration commands to configure many QOS features in a router or switch. <a href="https://qos.internetworks.in/2020/03/what-is-modular-quality-of-service-cli_21.html">https://qos.internetworks.in/2020/03/what-is-modular-quality-of-service-cli_21.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/0*COJPK5Rwh2CdnY41.jpg" /></figure><p>MQC separates the classification function of a QOS tool from the action (PHB) that the QOS tool wants to perform. To do so, there are three major commands with MQC, with several subordinate commands:</p><p>Class maps</p><p>What traffic do we care about?</p><p>Each class is identified using a class map</p><p>A traffic class contains three major elements:</p><p>- A case-sensitive name</p><p>- A series of match command</p><p>- An instruction on how to evaluate the match command if more than one match command exists in the traffic class</p><p>Class maps can operate in two modes:</p><p>- Match all: all conditions have to succeed.</p><p>- Match any: at least one condition must succeed.</p><p>- The default mode is match all.</p><p>R1(config-cmap)#</p><p>Policy maps</p><p>What will be done to this traffic?</p><p>Define a traffic policy, which configures the QOS features associated with traffic class previously identified using a class map.</p><p>A traffic policy contains three major elements:</p><p>- A case-sensitive name</p><p>- A traffic class</p><p>- The QOS policy associate with that traffic class</p><p>Up to 256 traffic classes can be associated with a single traffic policy.</p><p>Multiple policy maps can be nested to influence the sequence of QOS actions.</p><p>Service policy</p><p>Where will this policy be implemented?</p><p>Attaches a traffic policy configured with a policy map an interface.</p><p>Service polices can be applied to an interface for inbound or outbound packets.</p><p>R1(config-pmap-c)#</p><p>Service policy</p><p>Where will this policy be implemented?</p><p>Attaches a traffic policy configured with a policy map an interface.</p><p>Service polices can be applied to an interface for inbound or outbound packets.</p><p>\</p><p>let see the configuration:</p><p>Topology:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*nEt4nNihK8Yl1dXh.png" /></figure><p>TASK:</p><ul><li>configure the topology as per the diagram</li><li>Assign IP addresses as per the diagram</li><li>configure OSPF and advertise all the directly connected interfaces</li><li>configure MQC policy on router 1 serial 3/2</li><li>traffic flows for ICMP between Router 1 and Router 3 serial 3/2 network (10.1.1.1 to 30.1.1.1) should be guaranteed 130 kbps.assign 70 kbps to HTTP traffic.</li></ul><p>R1#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 10.1.1.1 YES manual up up</p><p>Serial3/0 1.1.1.1 YES manual up up</p><p>Serial3/2 3.3.3.2 YES manual up up</p><p>R2#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 20.1.1.1 YES manual up up</p><p>Serial3/0 1.1.1.2 YES manual up up</p><p>Serial3/1 2.2.2.1 YES manual up up</p><p>R3#show ip interface brief</p><p>Interface IP-Address OK? Method Status Protocol</p><p>FastEthernet0/0 30.1.1.1 YES manual up up</p><p>Serial3/1 2.2.2.2 YES manual up up</p><p>Serial3/2 3.3.3.1 YES manual up up</p><p>R1(config)#router ospf 1</p><p>R1(config-router)#network 10.0.0.0 0.255.255.255 area 0</p><p>R1(config-router)#network 1.0.0.0 0.255.255.255 area 0</p><p>R1(config-router)#network 3.0.0.0 0.255.255.255 area 0</p><p>R1(config-router)#exit</p><p>*Jan 5 23:40:32.179: %OSPF-5-ADJCHG: Process 1, Nbr 20.1.1.1 on Serial3/0 from LOADING to FULL, Loading Done</p><p>R2(config)#router ospf 1</p><p>R2(config-router)#network 20.0.0.0 0.255.255.255 area 0</p><p>R2(config-router)#network 2.0.0.0 0.255.255.255 area 0</p><p>R2(config-router)#network 1.0.0.0 0.255.255.255 area 0</p><p>R2(config-router)#exit</p><p>*Jan 5 23:40:31.891: %OSPF-5-ADJCHG: Process 1, Nbr 10.1.1.1 on Serial3/0 from LOADING to FULL, Loading Done</p><p>*Jan 5 23:41:07.539: %OSPF-5-ADJCHG: Process 1, Nbr 30.1.1.1 on Serial3/1 from LOADING to FULL, Loading Done</p><p>R3(config)#router ospf 1</p><p>R3(config-router)#network 30.0.0.0 0.255.255.255 area 0</p><p>R3(config-router)#network 3.0.0.0 0.255.255.255 area 0</p><p>R3(config-router)#network 2.0.0.0 0.255.255.255 area 0</p><p>R3(config-router)#exit</p><p>*Jan 5 23:41:07.835: %OSPF-5-ADJCHG: Process 1, Nbr 20.1.1.1 on Serial3/1 from LOADING to FULL, Loading Done</p><p>*Jan 6 00:21:31.051: %OSPF-5-ADJCHG: Process 1, Nbr 10.1.1.1 on Serial3/2 from LOADING to FULL, Loading Done</p><p>R1#show ip pro</p><p>*** IP Routing is NSF aware ***</p><p>Routing Protocol is “ospf 1”</p><p>Outgoing update filter list for all interfaces is not set</p><p>Incoming update filter list for all interfaces is not set</p><p>Router ID 10.1.1.1</p><p>Number of areas in this router is 1. 1 normal 0 stub 0 nssa</p><p>Maximum path: 4</p><p>Routing for Networks:</p><p>1.0.0.0 0.255.255.255 area 0</p><p>3.0.0.0 0.255.255.255 area 0</p><p>10.0.0.0 0.255.255.255 area 0</p><p>Routing Information Sources:</p><p>Gateway Distance Last Update</p><p>20.1.1.1 110 00:01:29</p><p>30.1.1.1 110 00:00:43</p><p>Distance: (default is 110)</p><p>R1#show ip route ospf</p><p>Gateway of last resort is not set</p><p>O 2.0.0.0/8 [110/128] via 1.1.1.2, 00:01:40, Serial3/0</p><p>O 20.0.0.0/8 [110/65] via 1.1.1.2, 00:01:40, Serial3/0</p><p>· 30.0.0.0/8 [110/129] via 1.1.1.2, 00:00:55, Serial3/0</p><p>R2#show ip pro</p><p>*** IP Routing is NSF aware ***</p><p>Routing Protocol is “ospf 1”</p><p>Outgoing update filter list for all interfaces is not set</p><p>Incoming update filter list for all interfaces is not set</p><p>Router ID 20.1.1.1</p><p>Number of areas in this router is 1. 1 normal 0 stub 0 nssa</p><p>Maximum path: 4</p><p>Routing for Networks:</p><p>1.0.0.0 0.255.255.255 area 0</p><p>2.0.0.0 0.255.255.255 area 0</p><p>20.0.0.0 0.255.255.255 area 0</p><p>Routing Information Sources:</p><p>Gateway Distance Last Update</p><p>10.1.1.1 110 00:02:02</p><p>30.1.1.1 110 00:01:25</p><p>Distance: (default is 110)</p><p>R2#show ip route ospf</p><p>Gateway of last resort is not set</p><p>O 3.0.0.0/8 [110/128] via 1.1.1.1, 00:02:09, Serial3/0</p><p>O 10.0.0.0/8 [110/65] via 1.1.1.1, 00:02:09, Serial3/0</p><p>· 30.0.0.0/8 [110/65] via 2.2.2.2, 00:01:31, Serial3/1</p><p>R3#show ip pro</p><p>*** IP Routing is NSF aware ***</p><p>Routing Protocol is “ospf 1”</p><p>Outgoing update filter list for all interfaces is not set</p><p>Incoming update filter list for all interfaces is not set</p><p>Router ID 30.1.1.1</p><p>Number of areas in this router is 1. 1 normal 0 stub 0 nssa</p><p>Maximum path: 4</p><p>Routing for Networks:</p><p>2.0.0.0 0.255.255.255 area 0</p><p>3.0.0.0 0.255.255.255 area 0</p><p>30.0.0.0 0.255.255.255 area 0</p><p>Routing Information Sources:</p><p>Gateway Distance Last Update</p><p>10.1.1.1 110 00:12:40</p><p>20.1.1.1 110 00:14:46</p><p>Distance: (default is 110)</p><p>R3#show ip route ospf</p><p>Gateway of last resort is not set</p><p>O 1.0.0.0/8 [110/128] via 3.3.3.2, 00:12:45, Serial3/2</p><p>[110/128] via 2.2.2.1, 00:14:52, Serial3/1</p><p>O 10.0.0.0/8 [110/65] via 3.3.3.2, 00:12:45, Serial3/2</p><p>O 20.0.0.0/8 [110/65] via 2.2.2.1, 00:53:04, Serial3/1</p><p>R1(config)#access-list 111 permit icmp host 10.1.1.1 host 30.1.1.1 echo</p><p>R1(config)#access-list 111 permit icmp host 10.1.1.1 host 30.1.1.1 echo-reply</p><p>R1(config)#access-list 122 permit tcp any any eq www</p><p>R1(config)#class-map icmp_tr</p><p>R1(config-cmap)#match access-group 111</p><p>R1(config-cmap)#exit</p><p>R1(config)#class-map web_tr</p><p>R1(config-cmap)#match access-group 122</p><p>R1(config-cmap)#exit</p><p>R1#show run class-map</p><p>Building configuration…</p><p>Current configuration : 111 bytes</p><p>!</p><p>class-map match-all web_tr</p><p>match access-group 122</p><p>class-map match-all icmp_tr</p><p>match access-group 111</p><p>end</p><p>R1(config)#policy-map internetworks</p><p>R1(config-pmap)#class icmp_tr</p><p>R1(config-pmap-c)#bandwidth 130</p><p>R1(config-pmap-c)#exit</p><p>R1(config-pmap)#class web_tr</p><p>R1(config-pmap-c)#bandwidth 70</p><p>R1(config-pmap-c)#exit</p><p>R1(config-pmap)#class class-default</p><p>R1(config-pmap-c)#exit</p><p>R1#show run policy-map</p><p>Building configuration…</p><p>Current configuration : 116 bytes</p><p>!</p><p>policy-map internetworks</p><p>class icmp_tr</p><p>bandwidth 130</p><p>class web_tr</p><p>bandwidth 70</p><p>class class-default</p><p>!</p><p>end</p><p>R1(config)#interface serial 3/2</p><p>R1(config-if)#service-policy output internetworks</p><p>R1(config-if)#end</p><p>R1#show policy-map interface serial 3/2</p><p>Serial/2</p><p>Service-policy output: internetworks</p><p>Class-map: icmp_tr (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group 111</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>bandwidth 130 kbps</p><p>Class-map: web_tr (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group 122</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>bandwidth 70 kbps</p><p>Class-map: class-default (match-any)</p><p>5 packets, 288 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 5/288</p><p>R1#PING 30.1.1.1 SOURCE 10.1.1.1 REPEAT 100</p><p>Type escape sequence to abort.</p><p>Sending 100, 100-byte ICMP Echos to 30.1.1.1, timeout is 2 seconds:</p><p>Packet sent with a source address of 10.1.1.1</p><p>!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</p><p>!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!</p><p>Success rate is 100 percent (100/100), round-trip min/avg/max = 20/29/44 ms</p><p>R1#show policy-map interface serial 3/2</p><p>Serial3/2</p><p>Service-policy output: INTERNETWORKS</p><p>Class-map: ICMP_TR (match-all)</p><p>100 packets, 10400 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group 111</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 100/10400</p><p>bandwidth 130 kbps</p><p>Class-map: WEB_TR (match-all)</p><p>0 packets, 0 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: access-group 122</p><p>Queueing</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 0/0</p><p>bandwidth 70 kbps</p><p>Class-map: class-default (match-any)</p><p>15 packets, 1153 bytes</p><p>5 minute offered rate 0000 bps, drop rate 0000 bps</p><p>Match: any</p><p>queue limit 64 packets</p><p>(queue depth/total drops/no-buffer drops) 0/0/0</p><p>(pkts output/bytes output) 15/1153</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3e6d8896bfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>