{"id":105,"date":"2026-09-03T12:43:51","date_gmt":"2026-09-03T12:43:51","guid":{"rendered":"https:\/\/wordpress.sarservice.site\/?p=105"},"modified":"2026-09-03T12:44:01","modified_gmt":"2026-09-03T12:44:01","slug":"how-to-configure-vlan-on-two-cisco-switches-with-four-pcs","status":"publish","type":"post","link":"https:\/\/wordpress.sarservice.site\/index.php\/2026\/09\/03\/how-to-configure-vlan-on-two-cisco-switches-with-four-pcs\/","title":{"rendered":"How to Configure VLAN on Two Cisco Switches with Four PCs"},"content":{"rendered":"\n

Absolutely. Here is a WordPress-ready blog post<\/strong> for a beginner-friendly Cisco VLAN lab using 2 switches and 4 PCs<\/strong>.<\/p>\n\n\n\n

How to Configure VLAN on Two Cisco Switches with Four PCs<\/h1>\n\n\n\n

Introduction<\/h2>\n\n\n\n

VLAN (Virtual Local Area Network) is used to logically divide a physical network into multiple separate networks. VLANs help improve network security, management, and traffic control<\/strong>.<\/p>\n\n\n\n

In this tutorial, we will configure VLANs using:<\/p>\n\n\n\n

    \n
  • 2 Cisco switches<\/strong><\/li>\n\n\n\n
  • 4 PCs<\/strong><\/li>\n\n\n\n
  • VLAN 10 \u2013 SALES<\/strong><\/li>\n\n\n\n
  • VLAN 20 \u2013 IT<\/strong><\/li>\n\n\n\n
  • A trunk link<\/strong> between the two switches<\/li>\n<\/ul>\n\n\n\n

    The lab can be created easily in Cisco Packet Tracer<\/strong>.<\/p>\n\n\n\n

    \"Image\"\/<\/figure>\n\n\n\n
    \"Image\"\/<\/figure>\n\n\n\n
    \"Image\"\/<\/figure>\n\n\n\n
    \"Image\"\/<\/figure>\n\n\n\n
    \n\n\n\n

    1. Network Topology<\/h2>\n\n\n\n

    We will create the following topology:<\/p>\n\n\n\n

                 Trunk Link\n        Fa0\/24 -------- Fa0\/24\n       +--------+      +--------+\n       | Switch1|------| Switch2|\n       +--------+      +--------+\n        |      |        |      |\n       PC1    PC2      PC3    PC4<\/code><\/pre>\n\n\n\n
    VLAN Design<\/h3>\n\n\n\n
    Device<\/th>Port<\/th>VLAN<\/th>IP Address<\/th><\/tr><\/thead>
    PC1<\/td>SW1 Fa0\/1<\/td>VLAN 10<\/td>192.168.10.2<\/td><\/tr>
    PC2<\/td>SW1 Fa0\/2<\/td>VLAN 20<\/td>192.168.20.2<\/td><\/tr>
    PC3<\/td>SW2 Fa0\/1<\/td>VLAN 10<\/td>192.168.10.3<\/td><\/tr>
    PC4<\/td>SW2 Fa0\/2<\/td>VLAN 20<\/td>192.168.20.3<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    We will use:<\/p>\n\n\n\n
      \n
    • VLAN 10 = SALES<\/strong><\/li>\n\n\n\n
    • VLAN 20 = IT<\/strong><\/li>\n\n\n\n
    • Switch-to-switch connection = Trunk<\/strong><\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n
      2. Connect the Devices<\/h1>\n\n\n\n
      In Cisco Packet Tracer, add:<\/p>\n\n\n\n
        \n
      • 2 \u00d7 Cisco 2960 switches<\/li>\n\n\n\n
      • 4 \u00d7 PCs<\/li>\n<\/ul>\n\n\n\n
        Connect:<\/p>\n\n\n\n
        PC1 \u2192 Switch1 Fa0\/1\nPC2 \u2192 Switch1 Fa0\/2\n\nPC3 \u2192 Switch2 Fa0\/1\nPC4 \u2192 Switch2 Fa0\/2\n\nSwitch1 Fa0\/24 \u2192 Switch2 Fa0\/24<\/code><\/pre>\n\n\n\n
        For the connections, you can use Copper Straight-Through<\/strong> cables.<\/p>\n\n\n\n
        \n\n\n\n
        3. Configure Switch 1<\/h1>\n\n\n\n
        Open Switch1 \u2192 CLI<\/strong>.<\/p>\n\n\n\n
        Enter:<\/p>\n\n\n\n
        enable\nconfigure terminal\n\nhostname SW1<\/code><\/pre>\n\n\n\n
        Create VLAN 10<\/h2>\n\n\n\n
        vlan 10\nname SALES\nexit<\/code><\/pre>\n\n\n\n
        Create VLAN 20<\/h2>\n\n\n\n
        vlan 20\nname IT\nexit<\/code><\/pre>\n\n\n\n
        Now configure the PC ports.<\/p>\n\n\n\n
        PC1 \u2013 VLAN 10<\/h3>\n\n\n\n
        interface fastethernet 0\/1\nswitchport mode access\nswitchport access vlan 10\nexit<\/code><\/pre>\n\n\n\n
        PC2 \u2013 VLAN 20<\/h3>\n\n\n\n
        interface fastethernet 0\/2\nswitchport mode access\nswitchport access vlan 20\nexit<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        4. Configure Trunk Port on Switch 1<\/h1>\n\n\n\n
        The connection between the two switches must carry traffic from both VLAN 10 and VLAN 20<\/strong>.<\/p>\n\n\n\n
        Configure Fa0\/24 as a trunk:<\/p>\n\n\n\n
        interface fastethernet 0\/24\nswitchport mode trunk\nexit<\/code><\/pre>\n\n\n\n
        Save the configuration:<\/p>\n\n\n\n
        end\nwrite memory<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        5. Configure Switch 2<\/h1>\n\n\n\n
        Open Switch2 \u2192 CLI<\/strong>.<\/p>\n\n\n\n
        enable\nconfigure terminal\n\nhostname SW2<\/code><\/pre>\n\n\n\n
        Create VLAN 10:<\/p>\n\n\n\n
        vlan 10\nname SALES\nexit<\/code><\/pre>\n\n\n\n
        Create VLAN 20:<\/p>\n\n\n\n
        vlan 20\nname IT\nexit<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        Configure PC3 \u2013 VLAN 10<\/h2>\n\n\n\n
        interface fastethernet 0\/1\nswitchport mode access\nswitchport access vlan 10\nexit<\/code><\/pre>\n\n\n\n
        Configure PC4 \u2013 VLAN 20<\/h2>\n\n\n\n
        interface fastethernet 0\/2\nswitchport mode access\nswitchport access vlan 20\nexit<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        6. Configure Trunk on Switch 2<\/h1>\n\n\n\n
        Configure Fa0\/24:<\/p>\n\n\n\n
        interface fastethernet 0\/24\nswitchport mode trunk\nexit<\/code><\/pre>\n\n\n\n
        Save:<\/p>\n\n\n\n
        end\nwrite memory<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        7. Configure IP Addresses on PCs<\/h1>\n\n\n\n
        Now configure the IP addresses.<\/p>\n\n\n\n
        PC1<\/h3>\n\n\n\n
        Go to:<\/p>\n\n\n\n
        PC1 \u2192 Desktop \u2192 IP Configuration<\/strong><\/p>\n\n\n\n
        Enter:<\/p>\n\n\n\n
        IP Address:      192.168.10.2\nSubnet Mask:     255.255.255.0<\/code><\/pre>\n\n\n\n
        PC2<\/h3>\n\n\n\n
        IP Address:      192.168.20.2\nSubnet Mask:     255.255.255.0<\/code><\/pre>\n\n\n\n
        PC3<\/h3>\n\n\n\n
        IP Address:      192.168.10.3\nSubnet Mask:     255.255.255.0<\/code><\/pre>\n\n\n\n
        PC4<\/h3>\n\n\n\n
        IP Address:      192.168.20.3\nSubnet Mask:     255.255.255.0<\/code><\/pre>\n\n\n\n
        A default gateway is not required<\/strong> for this basic Layer-2 VLAN lab because we are not configuring routing between VLANs.<\/p>\n\n\n\n
        \n\n\n\n
        8. Understanding How This Works<\/h1>\n\n\n\n
        The important concept is that the same VLAN exists on both switches<\/strong>.<\/p>\n\n\n\n
        VLAN 10 \u2013 SALES\n\nPC1\n192.168.10.2\n     |\n     | VLAN 10\n     |\n   SW1\n     |\n     | TRUNK\n     |\n   SW2\n     |\n     | VLAN 10\n     |\nPC3\n192.168.10.3<\/code><\/pre>\n\n\n\n
        Therefore:<\/p>\n\n\n\n
        PC1 can communicate with PC3.<\/strong><\/p>\n\n\n\n
        Similarly:<\/p>\n\n\n\n
        VLAN 20 \u2013 IT\n\nPC2\n192.168.20.2\n     |\n   SW1\n     |\n     | TRUNK\n     |\n   SW2\n     |\nPC4\n192.168.20.3<\/code><\/pre>\n\n\n\n
        Therefore:<\/p>\n\n\n\n
        PC2 can communicate with PC4.<\/strong><\/p>\n\n\n\n
        \n\n\n\n
        9. Test the VLAN Configuration<\/h1>\n\n\n\n
        Open PC1 \u2192 Desktop \u2192 Command Prompt<\/strong>.<\/p>\n\n\n\n
        Run:<\/p>\n\n\n\n
        ping 192.168.10.3<\/code><\/pre>\n\n\n\n
        You should receive replies:<\/p>\n\n\n\n
        Reply from 192.168.10.3\nReply from 192.168.10.3\nReply from 192.168.10.3<\/code><\/pre>\n\n\n\n
        This confirms that PC1 and PC3 are communicating through VLAN 10<\/strong> across the trunk.<\/p>\n\n\n\n
        Now test PC2:<\/p>\n\n\n\n
        ping 192.168.20.3<\/code><\/pre>\n\n\n\n
        PC2 should successfully communicate with PC4 through VLAN 20<\/strong>.<\/p>\n\n\n\n
        \n\n\n\n
        10. Test VLAN Isolation<\/h1>\n\n\n\n
        Now try:<\/p>\n\n\n\n
        From PC1<\/h3>\n\n\n\n
        ping 192.168.20.2<\/code><\/pre>\n\n\n\n
        This should fail<\/strong>.<\/p>\n\n\n\n
        Why?<\/p>\n\n\n\n
        PC1 is in:<\/p>\n\n\n\n
        VLAN 10<\/code><\/pre>\n\n\n\n
        while PC2 is in:<\/p>\n\n\n\n
        VLAN 20<\/code><\/pre>\n\n\n\n
        A normal Layer-2 switch does not route traffic between different VLANs.<\/p>\n\n\n\n
        \n\n\n\n
        11. Verify VLANs on the Switch<\/h1>\n\n\n\n
        On SW1 and SW2, run:<\/p>\n\n\n\n
        show vlan brief<\/code><\/pre>\n\n\n\n
        You should see something similar to:<\/p>\n\n\n\n
        VLAN Name                             Status    Ports\n---- -------------------------------- --------- ----------------\n1    default                          active    ...\n10   SALES                            active    Fa0\/1\n20   IT                               active    Fa0\/2<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        12. Verify the Trunk<\/h1>\n\n\n\n
        Run:<\/p>\n\n\n\n
        show interfaces trunk<\/code><\/pre>\n\n\n\n
        You should see Fa0\/24<\/strong> operating as a trunk.<\/p>\n\n\n\n
        For example:<\/p>\n\n\n\n
        Port        Mode         Encapsulation  Status\nFa0\/24      on           802.1q         trunking<\/code><\/pre>\n\n\n\n
        The trunk allows multiple VLANs to travel between the switches.<\/p>\n\n\n\n
        \n\n\n\n
        13. Complete Configuration<\/h1>\n\n\n\n
        Switch 1<\/h2>\n\n\n\n
        enable\nconfigure terminal\n\nhostname SW1\n\nvlan 10\nname SALES\nexit\n\nvlan 20\nname IT\nexit\n\ninterface fastethernet 0\/1\nswitchport mode access\nswitchport access vlan 10\nexit\n\ninterface fastethernet 0\/2\nswitchport mode access\nswitchport access vlan 20\nexit\n\ninterface fastethernet 0\/24\nswitchport mode trunk\nexit\n\nend\nwrite memory<\/code><\/pre>\n\n\n\n
        Switch 2<\/h2>\n\n\n\n
        enable\nconfigure terminal\n\nhostname SW2\n\nvlan 10\nname SALES\nexit\n\nvlan 20\nname IT\nexit\n\ninterface fastethernet 0\/1\nswitchport mode access\nswitchport access vlan 10\nexit\n\ninterface fastethernet 0\/2\nswitchport mode access\nswitchport access vlan 20\nexit\n\ninterface fastethernet 0\/24\nswitchport mode trunk\nexit\n\nend\nwrite memory<\/code><\/pre>\n\n\n\n
        \n\n\n\n
        14. Final Network Diagram<\/h1>\n\n\n\n
                            TRUNK\n              Fa0\/24 \u2194 Fa0\/24\n             +----------------+\n             |                |\n        +---------+      +---------+\n        |   SW1   |      |   SW2   |\n        +---------+      +---------+\n          |      |         |      |\n        Fa0\/1  Fa0\/2     Fa0\/1  Fa0\/2\n          |      |         |      |\n         PC1    PC2       PC3    PC4\n          |      |         |      |\n       VLAN 10 VLAN 20  VLAN 10 VLAN 20<\/code><\/pre>\n\n\n\n
        Expected Results<\/h3>\n\n\n\n
        Test<\/th>Result<\/th><\/tr><\/thead>
        PC1 \u2192 PC3<\/td>\u2705 Works<\/td><\/tr>
        PC2 \u2192 PC4<\/td>\u2705 Works<\/td><\/tr>
        PC1 \u2192 PC2<\/td>\u274c Does not work<\/td><\/tr>
        PC1 \u2192 PC4<\/td>\u274c Does not work<\/td><\/tr>
        PC3 \u2192 PC4<\/td>\u274c Does not work<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n
        Conclusion<\/h2>\n\n\n\n
        In this lab, we configured VLAN 10 and VLAN 20 on two Cisco switches<\/strong> and connected the switches using a trunk link<\/strong>.<\/p>\n\n\n\n
        The important commands to remember are:<\/p>\n\n\n\n
        vlan 10<\/code><\/pre>\n\n\n\n
        switchport mode access\nswitchport access vlan 10<\/code><\/pre>\n\n\n\n
        and for the connection between switches:<\/p>\n\n\n\n
        switchport mode trunk<\/code><\/pre>\n\n\n\n
        This is a basic but important Cisco networking lab for understanding VLANs, access ports, trunk ports, and VLAN isolation<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"
        Absolutely. Here is a WordPress-ready blog post for a beginner-friendly Cisco VLAN lab using 2 switches and 4 PCs. How to Configure VLAN on Two Cisco Switches with Four PCs … Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":106,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-105","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sarservice","entry"],"_links":{"self":[{"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/posts\/105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/comments?post=105"}],"version-history":[{"count":1,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/posts\/105\/revisions"}],"predecessor-version":[{"id":107,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/posts\/105\/revisions\/107"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/media\/106"}],"wp:attachment":[{"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/media?parent=105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/categories?post=105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.sarservice.site\/index.php\/wp-json\/wp\/v2\/tags?post=105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}