Cisco CCNA Tutorial: Configure Basic VLAN


With multiple hosts and servers on layer 2 switches, there are several issues arises that should be dealt by network administrators. One major problem is its broadcast can flood to all ports resulting to the consumption of unnecessary bandwidth. And, security vulnerability, since all devices attached to layer 2 devices can forward and receive frames to and from every other devices on that same switch.

One solution for this is through configuration of VLAN or Virtual Local Area Network. According to Cisco, “A VLAN is a logical broadcast domain that can span multiple physical LAN segments. It allows an administrator to group together stations by logical function, by project teams, or by applications, without regard to physical location of the users.”

There are 2 ways to configure a VLAN

1. Static VLAN which requires administrator to interactively assign each switch port to a specific VLAN

2. Dynamic VLAN which requires VLAN management policy server (VMPS) to scan for a match address from the database and temporarily assign the port used by the device  to the appropriate VLAN.

Through VLAN, we can group packets according to its vlan id as it goes in and out to switches. We can configure this using manageable switches.

Watch for the complete VLAN configuration

You can follow by downloading the preconfigured packet tracer activity file in this exercise.

Private VLAN Configuration

Steps to Configure Private VLAN

1. Create VLAN ID and VLAN NAME

(config)#vlan <vlan id>
(config-vlan)#name <vlan name>

Specify the appropriate VLAN id for the assigned VLAN. In this activity, VLAN 10 for students, 20 for Instructors and 30 for admins. Assign a name which makes VLAN ID identifiable such as Students, Instructors, Administrators.

2. Assign ports to VLAN

By default, all ports are assigned as members of VLAN 1. There are two ways to add ports to VLAN. We can add ports individually or adding ports in range.

Assigning ports individually to VLAN

(config)#interface fa#/#
(config-if)#switchport access vlan <vlan id>

Assigning port range to VLAN

(config)#interface range fa#/start_of_range - end_of_range
(config-if)#switchport access vlan <vlan id>

In this activity, we will assign port ranges to specific VLAN groups. Interface range fa0/1-9 specifies ports 1-9 to be assigned for VLAN 10. Switchport mode access specifies port access function. Switchport access vlan 10 specifies the range of ports to be a member of VLAN 10. Do this to all switches that has VLAN groups.

3. Configure VLAN trunk port

This is configuration is required for multiple vlan frames to travel using a single port or link. Trunk port is necessary to forward frames from one device going to another. In this activity, we will enable fa0/24 of 3 floor switches to act as truck port in order to receive and forward vlan frames to main switch. To configure port for trunking, interface fa0/24 where fa0/24 is the specific port for trunking. Issue the command switchport mode trunk, this will change the port mode to accept multiple vlan frames. Supply the command switchport trunk allowed vlan all to allow all vlans to communicate with each other. 

(config)#interface <interface id> 
(config-if)#switchport mode trunk 
(config)#switchport trunk native vlan <vlan id> 
(config-if)#switchport trunk allowed vlan add <vlan list>

specify all necessary commands and save your vlan configuration.

4. Verify VLAN settings

You can view the configuration and effectivity of the configuration using the command

show interfaces {interface id | vlan <vlan id> | switchport}



  1. Dear John,
    I have created VLANs followed by your video .You created 3 VLANs and you enable fe0/1,fe0/2,fe0/3 as a trunk port on the main switch .You enable fe0/24 of each switch as a trunk port.But you haven’t run Vtp mode server or vtp mode client command on either switch .Is this possible to communicate between hosts from one Vlan to another without making a switch a server ?I have implemented the same topology as you do , i am able to ping to and to but is not communicating with or to .Is this the policy of Vlan that hosts in that particular vlan can communicate with the hosts with the same subnet ? Is this related to unauthorised access? But in your video all host are able to communicate with each other or in your topology as well .Why all the hosts are not communicating with each other?Please help me

    • VTP is used for managing multiple switches with vlans. in this activity, with 3 switches, I did not use vtp to simplify things out. If you want to ping .1 with .11 or .2 with .12, simply add them to the same vlan group. In the video, after vlan, .1 and .11 are not communicating nor .2 and .12.

      sorry for the late reply. I was quite busy for a while. hope this helps.

Leave a Reply