Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
rzanella
New Contributor III

Fortinac delay to switch to VLAN isolation

Hi,

I'm configuring my first Fortinac.

I have a problem whit switching vlan. When I plug on switch an pc  Fortinac receive snpm trap but the switch to isolation vlan is done after 40/50 seconds about.
So pc get IP of production and after switching VLAN it don't get a IP of isolation subnet until I do ipconfig /renew.


here what I see on switch:
Aug 28 15:06:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
Aug 28 15:06:59: %SYS-5-CONFIG_I: Configured from console by admin on vty1...

 

Could you help me?

 

Thanks in advance

2 Solutions
ebilcari
Staff
Staff

This looks like an integration with a Cisco switch, is it properly modeled in FNAC, are the credentials validated for both SNMP and CLI?

It is preferred to use SNMP MAC traps instead of link status traps. In case of link status traps a L2 polling is triggered and it will add some delay.

Is the end host connected directly or through an IP Phone?

- Emirjon
If you have found a solution, please like and accept it to make it easily accessible for others.

View solution in original post

AEK

The community must be RW, otherwise it doesn't accept up/down requests from NAC.

AEK

View solution in original post

AEK
10 REPLIES 10
rzanella
New Contributor III

Solved. Thanks to  AEK and ebilcari.

Here what I do on switch.

on interfaces add:

snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree portfast edge 

 

SNMP configuration:

snmp-server community ForNacTrap RW 50

snmp-server enable traps mac-notification change move threshold

 

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors