VLAN 3 is not yet configured on your switch. What happens if you set the switchport access vlan 3
command in interface configuration mode?
A.
The command is rejected.
B.
The port turns amber.
C.
The command is accepted and the respective VLAN is added to vlan.dat.
D.
The command is accepted and you must configure the VLAN manually.
Correct answer is D. After setting a switchport access to some non-existing VLAN (lets say 360), you can immediately #show vlan and won’t see the vlan listed yet. Even after writing that config, you can still do a #show vlan id 360 and get a “VLAN id 360 not found in current VLAN Database” error. You will need to manually configure the VLAN to append it to vlan.dat.
0
0
I try to do this commands on Packet Tracer Student 6.2.0.0052 (IOS 12.2):
>enable
#configure terminal
#interface fa0/3
#switchport access vlan 3
— I get the message “Access VLAN does not exist. Creating vlan 3”
#do show vlan
— The result of the “show vlan” command is: vlan 3 is active then attributed to fa0/3. (it’s maybe like up/down status)
#do show interface vlan 3
I get the message “Interface Vlan3 does not exist”
#interface vlan 3
— I get the message “Interface vlan3, changed state to up” (it’s like up/up status)
I can’t do the “more vlan.dat” command on packet tracer to see if the vlan 3 is present on this file…
If anyone have a real switch to do this command ?
0
0