Device Support Considerations
|
Ticket # |
Description |
|---|---|
| 548902 | Management of wired ports on Aerohive AP-150W controlled by AerohiveNG is currently unsupported. |
| 679230 | Aruba 9012-US currently not supported. If required, contact sales or support to submit a New Feature Request (NFR). |
| 829009 | The Allowed VLAN list is not properly managed on Aruba CX switches. When FortiNAC performs a VLAN change, only the new VLAN is set. The previously configured Allowed VLAN is not removed. This causes the Allowed VLANs list to grow over time. |
| 836831 | Layer 2 polling HPE Walljacks fails if special characters are found in the devices mac-address table. |
| 842181 | FortiNAC does not support the custom RADIUS attribute Fortinet-Host-Port-AVPair action=bounce-port for Change of Authorization (CoA) with FortiSwitches. |
| 843509 | FortiNAC is unable to communicate with Dell x1026 switches. |
| 845035 | Palo Alto VPN integration does not support syslog notifications from Palo Alto devices running v9+. |
| 846782 | FortiNAC is unable to read roles and potentially other data from Aruba IAPs due to a # symbol automatically added to the wireless network name. |
|
7680531 |
Ubiquiti Gen2 Unifi switches (example: USW-16-POE) are currently not supported. If required, contact sales or support to submit a New Feature Request (NFR). |
|
860546 |
L3 Polling currently not supported on Extreme Wireless Controllers |
| At this time, integration with Juniper MAG6610 VPN Gateway is not supported. This includes Pulse Connect Secure ASA. | |
| At this time, integration with Cisco 1852i Controller is not supported due to the device's limited CLI and SNMP capability. For details, see related KB article 189545. | |
| At this time, Fortinet does not support wired port management for the Cisco 702W. The access point does not provide the management capabilities required. | |
| At this time, Fortinet is not able to support the Linksys LAPN600 Wireless-N600 Dual Band Access Point. | |
| Ports on Avaya Networks 4850GTS-PWR+ switches sometimes show "Not Connected" even though the port is active. This is due to multiple ports on the switch using the same MAC Address. This prevents NAC from correctly discerning which are "Connected" versus "Not Connected". There is no workaround. | |
| Device models for Avaya 4800 switches (and potentially other related models) only support SSH. Device models for Avaya Ethernet Routing Switches only support Telnet. Contact Support if the alternate protocol is required. |