RSE Lab Day
Welcome to your labs for Routing & Switching Essentials (RSE).
The primary purpose of lab days are for students to work on labs and build networking skills working directly with the hardware and software. Students are able to work on the curriculum, assessments, and any other course material to improve their awareness, learning, and understanding. Students are highly encouraged to work in teams, and share their learning.
Skills-based assessment(s) can also be practiced.
Make a goal to master the following labs!
The primary purpose of lab days are for students to work on labs and build networking skills working directly with the hardware and software. Students are able to work on the curriculum, assessments, and any other course material to improve their awareness, learning, and understanding. Students are highly encouraged to work in teams, and share their learning.
Skills-based assessment(s) can also be practiced.
Make a goal to master the following labs!
| ITN 0.0.0.1 Lab - Initializing and Reloading a Router and Switch | *2.1.1.6 Lab - Configuring Basic Switch Settings *2.2.4.11 Lab – Configuring Switch Security Features | *3.3.2.2 Lab – Implementing VLAN Security *3.2.2.5 Lab – Configuring VLANS and Trunking | *4.1.4.6 Lab – Configuring Basic Router Settings with IOS CLI | *5.1.3.7 Lab – Configuring 802.1Q Trunk-Based Inter-VLAN Routing | *8.2.4.5 Lab – Configuring Basic Single-Area OSPFv2 | *9.2.3.4 Configuring and Verifying VTY Restrictions | *10.1.2.5 Lab – Configure Basic DHCPv4 on a router | *11.2.2.6 Lab – Configure dynamic and static NAT |
DTP: How do I know the functionality of a switch port?
Dynamic Trunking Protocol
- Access
- Dynamic Auto
- Dynamic Desireable
- Trunk
Native VLAN Explained
Here is the scoop! Trunks ONLY CARRY TAGGED FRAMES, that's what trunks
were designed to do. the purpose of a trunk is to be able to TRANSFER DATA
FROM DIFFERENT VLANs. The reason the frames are tagged before they traverse
the trunk is so that when it gets to the other side of the trunk, the switch can
READ THE TAG AND DETERMINE WHICH VLAN THE FRAME BELONGS TO and then
forward it on to that VLAN.
Now the native VLAN. The purpose of the native VLAN is so that if untagged data finds its way traversing the trunk (usually because it entered the trunk somewhere in the middle, most likely from a connected hub so that the frame could not be tagged by the switch before entering the trunk), when that untagged frame gets to either end of the trunk, the switch then reads the frame sees that it is an untagged frame that ended up on the trunk and sends that untagged frame to the VLAN that has been assigned as the native VLAN.
Remember, TRUNKS ONLY CARRY TAGGED FRAMES, all untagged frames goes to the native vlan. So to answer your question, if VLAN1 hits the trunk, it too will be tagged, so that the switch on the other side of the trunk can determine which VLAN the frame belongs to and forward the frame to the appropriate VLAN.
For more discussion on this topic, take a look at https://learningnetwork.cisco.com/thread/2217.
Now the native VLAN. The purpose of the native VLAN is so that if untagged data finds its way traversing the trunk (usually because it entered the trunk somewhere in the middle, most likely from a connected hub so that the frame could not be tagged by the switch before entering the trunk), when that untagged frame gets to either end of the trunk, the switch then reads the frame sees that it is an untagged frame that ended up on the trunk and sends that untagged frame to the VLAN that has been assigned as the native VLAN.
Remember, TRUNKS ONLY CARRY TAGGED FRAMES, all untagged frames goes to the native vlan. So to answer your question, if VLAN1 hits the trunk, it too will be tagged, so that the switch on the other side of the trunk can determine which VLAN the frame belongs to and forward the frame to the appropriate VLAN.
For more discussion on this topic, take a look at https://learningnetwork.cisco.com/thread/2217.
Subscribe to:
Posts (Atom)