Reset Search
 

 

Article

NEAP phone does not get authenticated

« Go Back

Information

 
TitleNEAP phone does not get authenticated
Symptoms
IP phones configured for Non-EAPoL authentication are not allowed on a port.
Environment
ERS 3500, 3600
ERS 4800
ERS 4900, 5900

All supported software versions.
Cause
The IP phone was statically configured to send tagged traffic with certain VID. The port that the IP phone was connected to, was not a member of this VLAN, hence the MAC learning could not take place (incoming packets would be dropped due to 'unregistered frame filter'). Since the MAC address of the IP phone was never learned, NEAP process could not start.
Resolution
Either one of the two options will fix the issue:

1. Configure the IP phone to start untagged (allowing the MAC address to be learned), and assign VLAN/tagging to the phone dynamically (LLDP, DHCP option...).
2. Use EAPoL authentication (any EAP method the phone allows) instead of NEAP. EAPoL packets are not caught by the 'unregistered frame filter'.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255