The service port can be used management purposes, primarily for out-of-band management. However, AP management traffic is not possible across the service port. In most cases, the service port is used as a "last resort" means of accessing the controller GUI for management purposes. For example, in the case where the system distribution ports on the controller are down or their communication to the wired network is otherwise degraded.

A dynamic interface with the Dynamic AP Management option enabled is used as the tunnel source for packets from the controller to the access point and as the destination for CAPWAP packets from the access point to the controller.

The virtual interface is used to support mobility management, Dynamic Host Configuration Protocol (DHCP) relay, and embedded Layer 3 security such as guest web authentication. It also maintains the DNS gateway host name used by Layer 3 security and mobility managers to verify the source of certificates when Layer 3 web authorization is enabled.

Reference:

https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/ports_and_interfaces.html

When a FlexConnect access point can reach the controller (referred to as the connected mode), the controller assists in client authentication. When a FlexConnect access point cannot access the controller, the access point enters the standalone mode and authenticates clients by itself.

Reference:

https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-2/configuration/guide/cg/cg_flexconnect.html

The Static Persistence (or "on" mode) bundles the links unconditionally and no negotiation protocol is used. In this mode, neither PAgP nor LACP packets are sent or received.

Lightweight AP cannot normally operate on its own. It is very dependent on a WLC somewhere in the network.

Click Add New WLAN. The Add New WLAN window appears.

In the General tab, perform the following:

a) The WLAN Id is automatically selected but you can change it.

b) Enter the Profile Name for the WLAN. (*) must be set

c) Enter the SSID. (*) must be set

d) Choose Admin State for the WLAN from the drop-down list. The default Admin State is Enabled.

e) Choose Radio Policy from the drop-down list. The default Radio Policy is ALL.

=> CD is correct ans.

(config)#lldp ?

holdtime => Specify the holdtime (in sec) to be sent in packets

reinit => Delay (in sec) for LLDP initialization on any interface

run => Enable LLDP

timer => Specify the rate at which LLDP packets are sent (in sec)

tlv-select => Selection of LLDP TLVs to send

The VTP mode of SW2 is transparent so it only forwards the VTP updates it receives to its trunk links without processing them.

Reference:

https://www.cisco.com/c/en/us/support/docs/lan-switching/vtp/10558-21.html

From the neighbor status, we notice the "Flags" are SP. "P" here means the neighbor is in Passive mode. In order to create an Etherchannel interface, the (local)

SW1 ports should be in Active mode. Moreover, the "Port State" in the exhibit is "0x3c" (which equals to "00111100"³ in binary format). Bit 3 is "1" which means the ports are synchronizing -> the ports are working so the local ports should be in Active mode.

Dynamic Auto — Makes the Ethernet port willing to convert the link to a trunk link. The port becomes a trunk port if the neighboring port is set to trunk or dynamic desirable mode. This is the default mode for some switchports.

Dynamic Desirable — Makes the port actively attempt to convert the link to a trunk link. The port becomes a trunk port if the neighboring Ethernet port is set to trunk, dynamic desirable or dynamic auto mode.