Quantcast
Channel: CCNA Training
Viewing all articles
Browse latest Browse all 515

VLAN & Trunking Questions

$
0
0

Note: If you are not sure about Virtual Local Area Network (VLAN), please read our Virtual Local Area Network VLAN Tutorial.

Quick summary about VLAN:

Be default all access ports belong to VLAN 1. If we want to assign a new VLAN, we have to use the command “switchport access vlan <vlan-id>” under interface mode.

VLAN Benefits:

– Logically group devices by department/function, not location so it provides more efficient use of bandwidth
– Separate broadcast domains, thus reducing their sizes and help mitigate broadcast storms
– Provide additional security because it separates sensitive data traffic from other traffic

The following commands are used to a create a VLAN (for example VLAN 10) and assign it to an interface (for example fa0/1) on a switch:

Switch(config)#vlan 10 //Create VLAN 10 first
Switch(config)#interface fa0/1
Switch(config-if)#switchport access vlan 10 //assign Fa0/1 interface to VLAN 10

To verify a VLAN or check which ports belong to which VLAN, use the “show vlan” command (or “show vlan id <vlan-id>” for a specific VLAN)

Question 1

Explanation

From the output we see the native VLAN of Switch1 on Gi0/1 interface is VLAN 1 while that of Switch2 is VLAN 99 so there would be a native VLAN mismatch.

Question 2

Explanation

Maybe this question is missing the “SW2 is set to Dynamic Auto” part so we assume this part to find out the best answer. Dynamic Desirable + Dynamic Desirable/Dynamic Auto/Trunk will form a trunk link.

Question 3

Explanation

The trunk still forms with mismatched native VLANs and the traffic can actually flow between mismatched switches. But it is absolutely necessary that the native VLANs on both ends of a trunk link match; otherwise a native VLAN mismatch occurs, causing the two VLANs to effectively merge. For example with the above configuration, SW1 would send untagged frames for VLAN 999. SW2 receives them but would think they are for VLAN 99 so we can say these two VLANs are merged.

Question 4

Question 5

Explanation

For 802.1q encapsulation, the native VLAN must matched at both side; otherwise the link will not work. In this case the native VLAN of S1 is 1 while the native VLAN of S2 is 2. Therefore when a frame from VLAN 1 is sent from S1 to S2, it will be untagged before leaving S1. When S2 receives this untagged frame, it  believes this frame was sent from the native VLAN. But the native VLAN on S2 is VLAN 2, not VLAN 1. Therefore only hosts on VLAN2 of S2 will receive this frame.

Question 6

Question 7

Explanation

From the configuration of SW1, we see it is using Port Aggregation Protocol (PAgP) with “auto” mode so the other end (SW2) must also runs PAgP with “desirable” mode to actively sending request to form an Etherchannel.

Question 8

Question 9

Question 10


Viewing all articles
Browse latest Browse all 515

Trending Articles