Amp's CCIE Quest On a quest for the digits…


 Powered by Max Banner Ads 
8Jan/093

1.01 VLAN

I. Implement and Troubleshoot Campus Infrastructure and Services

  • VLAN

What is a VLAN?

The actual name is short for Virtual LAN. In simple terms a VLAN is a switched network that is segmented, in a logical sense, by function, department, or application. The VLAN is also independent of the actual physical LAN. Meaning all of the users on the VLAN do not have to be on the same physical LAN, but they do have to be in the same IP subnet. As an example, CompanyA can have their Marketing Department physically located on 3 different floors in the building, but from a switch standpoint they are all together.

If the Marketing and HR departments wanted to communicate with each other then traffic between their respective VLANs would need to be routed via Switch Virtual Interface or (SVI). Creating  SVI seems to be pretty simple and straight forward, you give the interface a L3 address. One thing to keep in mind about a SVI is that it does not become active until it is associated with a physical port.

There are two types of VLAN ports that are of importance here; Access and Voice.

The Voice VLAN basically allows an access port to carry IP voice traffic from an IP phone. The Voice VLAN config is not supported on trunk ports. How is this done? An 802.1Q header is added to the Ethernet frame indicating the VLAN ID. The switch checks to see if the VLAN ID in the header matches what is configured on the interface, if so, the traffic is permitted.

Here's an example of how to configure:

Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface gigabitethernet1/0/1.640
Switch(config-if)# mls qos trust cos
Switch(config-if)# switchport voice vlan 640
Switch(config-if)# ip address 10.10.10.122 255.255.255.0
Switch(config-if)# end

The Voice VLAN will not show as UP until "voice vlan" has been assigned to the interfaces that the IP Phones are connected to.

Let me also note that I may be asked or told in the lab  to ensure that my switch ports bypass the blocking, listening, and learning states which means that I will have to configure "spantree portfast" on the interface.

I am sure that I may have left something important out regarding VLAN, if so just drop me a quick reminder. Afterall, this is supposed to be a learning process right? ;-D

Comments (3) Trackbacks (0)
  1. hy, We are both almost in the starting of our preps… and our ccvp timings was also similar… i will be also blogging about it…http://bravingallodds.blogspot.com/.

    what about ur written preps?? i haven seen any thing about it in ur site.. i am following mark lewis advice…http://www.networkworld.com/community/node/24374 .. and have started with the call manager fundamentals… also i have send email to james(blindhog.net) asking him for his tips..

    good luck to both of us…. i am currently a faculty in a training institute in my city… i teach ccvp… so thats good for my ccie preps also… i get free and full access to racks at my place… i will make it a more complete ccie rack after my written.

  2. Hello JoelJose420,
    Mind if I call you Joel? Well anyway, thanks for checking out my blog. I decided not to blog about my written prep, I chose to focus more on my lab prep. James and Josh over at blindhog are both great to deal with. We all stand to learn a lot from them. You are ahead of the game with having full access to racks at your place. Best wishes with your studies.

  3. no problemo.. i haven quite set the destination pattern for Joel. but then i guess i am still more human than cisco(the human network)…. so ok… u can call me Joel… hehe

    i believe u haven taken the written yet… and you are preparing for the lab… but then again… what happens to the written??… i have decided to pass the written and then get onto the lab…..coz its always good to begin with theory… and to have a sound theoretical background…. dont get me wrong… i have my share of difficulties with it(check my blog out)…but i am still going strong… ;)


Leave a comment

You must be logged in to post a comment.

No trackbacks yet.


 Powered by Max Banner Ads