Which change can correct inband access to the WLC?
A.
change the switch FastEthernetO/1 duplex setting
B.
change the switch FastEthernetO/1 speed setting
C.
enable the switch FastEthernetO/1 spanning-tree port-fast trunk
D.
change the switch FastEthernetO/1 trunk encapsulation
E.
change the WLC management interface to use DHCP
F.
change the WLC management interface VLAN
G.
change the WLC configuration of NTP
H.
browse to WLC via http://10.10.10.10
Explanation:
All of the other ports in the network are using the default VLAN (VLAN 1) but port 0/1, which
connects to the WLC, is configured as a trunk, so VLAN 1 is not operationsl.
BUT….. what about the rule for ports connecting to WLC? according to that rule the switch port has to be in trunk mode….
Even, if the port is in trunk mode, by default VLAN 1 is allowed….Why do you think this port has to be configured as an access port?
Normally in WLC the management traffic should be untagged, so value ZERO should be used for VLAN…. and in this case they show ONE for that vlan. Don´t yo think this is the problem? For me F is the correct option
Narvez,
you are right by default trunk should allow all the vlans. but in this case vlan 1 is not trunked over the controller interface and hence the undet show vlan, vlan 1 is missing from the trunk.
I assume the option D not neccasarly suggest to change the vlan as access but it is suggesting to add the vlans over the interface trunks. It is more a switching question than a wireless question. And again F might be true if the vlans are being trunked and still no IP reachability on WLC.
I agree with Omar Narvaez.
Someone can help us?
Best regards
Look at the wlc’s management VLAN Identifier. It is set to 1, this means it will tag the management Vlan. Now look at the the switch’s trunk settings, it has a native Vlan of 1, meaning it will NOT tag the native Vlan 1. The management interface of the WLC needs to be set to an untagged Vlan for APs to connect per Cisco practice, therefore the management Vlan of the wlc needs to be set to 0. F is the correct answer in my opinion.
It does not show up on the show clan br command because it is a trunk. You have to use the show trunk command for that.
I do not see any “switcport trunk native vlan” configured on fa0/1 so by default native vlan should be vlan1 on fa0/1. It lets all untagged traffic to pass through vlan1. The explanation says “port 0/1, which
connects to the WLC, is configured as a trunk, so VLAN 1 is not operationsl”. Why would setting port 0/1 a trunk makes vlan1 not operational?
In contradiction with all example files I could get my hands on, I will go with TC for F. His logic does make sense, and I have verified indeed vlan1 will not show on trunk interfaces with ‘show vlan brief’.