Description | This article describes the issue when Dynamic assigned VLAN is not working with Ivanti as a Radius server |
Scope |
FortiSwitch is not assigning the port user connected to the correct VLAN ID although the configuration is correct and Ivanti logs show that the user is authenticated successfully and assigned to the correct VLAN. |
Solution |
Once the 802.1x is successfully configured, test with the user.
FortiSwitch # diagnose switch 802-1x status. port16: Mode: port-based (mac-by-pass disable) Link: Link up Port State: authorized: ( ) Dynamic Authorized Vlan : 0 EAP pass-through : Enable EAP auto-untagged-vlans : Enable Quarantine VLAN (4093) detection : Enable Native Vlan : 1 Allowed Vlan list: 1 Untagged Vlan list: Guest VLAN : Auth-Fail Vlan : AuthServer-Timeout Vlan :
Sessions info: xx:xx:xx:xx:xx:xx Type=802.1x,PEAP,state=AUTHENTICATED,etime=0,eap_cnt=12 params:reAuth=3600
In addition to the FortiSwitch output, when checking Packet Capture logs taken from FortiGate, it is possible to see that Ivanti is sending VLAN ID information as '<vlan-id>\000' or '<vlan-name>\000'. The sample is below.
Resolution:
Result.
FortiSwitch # diagnose switch 802-1x status port16: Mode: port-based (mac-by-pass disable) Link: Link up Port State: authorized: ( ) Dynamic Authorized Vlan : 201 EAP pass-through : Enable EAP auto-untagged-vlans : Enable Quarantine VLAN (4093) detection : Enable Native Vlan : 201 Allowed Vlan list: 201 Untagged Vlan list: Guest VLAN : Auth-Fail Vlan : AuthServer-Timeout Vlan : Sessions info: xx:xx:xx:xx:xx:xx Type=802.1x,PEAP,state=AUTHENTICATED,etime=0,eap_cnt=12 params:reAuth=3600
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.