cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
402
Views
0
Helpful
1
Replies

Post compliance, endpoint again authenticates via MAB

dgaikwad
Level 5
Level 5

Hello Experts,
I am seeing this behavior with my test lab, when endpoint connects, it authenticates via dot1x, goes through posture, and reported as compliant. Its also gets the final access, which is a VLAN change to the production VLAN.
But, soon in a few seconds, the same endpoint again authenticates via MAB and gets access via MAB.
I am not sure how this happening and seems that this issue only happens when my endpoints is behind a IP phone (Avaya).

This keeps happening in a loop.
 I am using this following interface configuration:

interface FastEthernet0/1
 switchport access vlan 142
 switchport mode access
 switchport voice vlan 141
 no cdp enable
 authentication event fail action next-method
 authentication event server dead action authorize vlan 100
 authentication event server dead action authorize voice
 authentication event server alive action reinitialize
 authentication host-mode multi-host
 authentication order dot1x mab webauth
 authentication priority dot1x mab webauth
 authentication port-control auto
 authentication periodic
 authentication timer inactivity 15
 mab
 no snmp trap link-status
 dot1x pae authenticator
 dot1x timeout tx-period 15
 spanning-tree portfast edge
 spanning-tree bpduguard enable

Is there anything that I missing or have added extra for this interface configuration?

1 Accepted Solution

Accepted Solutions

Mike.Cifelli
VIP Alumni
VIP Alumni
Test by switching this:
#authentication host-mode multi-host
To this:
#authentication host-mode multi-domain
Multi-domain: Allows both a host and a voice device, such as an IP phone (Cisco or non-Cisco), to be authenticated on an 802.1X-authorized port independently.

View solution in original post

1 Reply 1

Mike.Cifelli
VIP Alumni
VIP Alumni
Test by switching this:
#authentication host-mode multi-host
To this:
#authentication host-mode multi-domain
Multi-domain: Allows both a host and a voice device, such as an IP phone (Cisco or non-Cisco), to be authenticated on an 802.1X-authorized port independently.