FCSS_LED_AR-7.6 · Question #7
Refer to the exhibits. FortiGate is configured with an SSID named Corp in which dynamic VLAN assignment is enabled, and also configured with a RADIUS server to send IETF 64, IETF 65, and IETF 81…
The correct answer is A. The administrator must define the corresponding VLANs that are sent by the RADIUS server. Even though the RADIUS server is correctly sending VLAN assignment attributes (IETF 64, 65, and 81), FortiGate will only apply them if the corresponding VLAN interfaces are already defined on the FortiLink. Since the required VLANs are not preconfigured on FortiGate, dynamic…
Question
Refer to the exhibits. FortiGate is configured with an SSID named Corp in which dynamic VLAN assignment is enabled, and also configured with a RADIUS server to send IETF 64, IETF 65, and IETF 81 VSAs to manage VLAN allocation. The RADIUS server has been confirmed to be sending all the required information to FortiGate. However, FortiGate is not assigning the correct VLANs to wireless clients. Based on the information provided, what is causing the issue?
Exhibits
Options
- AThe administrator must define the corresponding VLANs that are sent by the RADIUS server.
- BWireless clients bust be assigned an IP address from the 10.0.3.0/24 subnet.
- CThe administrator must configure a firewall policy to allow wireless clients to communicate with
- DThe RADUIS server must send the framed-ip attribute to assign wireless clients an IP address.
How the community answered
(54 responses)- A61% (33)
- B6% (3)
- C22% (12)
- D11% (6)
Explanation
Even though the RADIUS server is correctly sending VLAN assignment attributes (IETF 64, 65, and 81), FortiGate will only apply them if the corresponding VLAN interfaces are already defined on the FortiLink. Since the required VLANs are not preconfigured on FortiGate, dynamic VLAN assignment cannot take effect for wireless clients.
Topics
Community Discussion
No community discussion yet for this question.