Original Message:
Sent: Feb 17, 2025 11:56 AM
From: Herman Robers
Subject: Mitel not getting IP's when rebooting in iniatial setup (CPPM and AOS-CX)
Maybe run a port-mirror and see what is is happening on the interface and if the traffic is tagged or untagged and to get a clue where the mismatch is.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Feb 17, 2025 08:28 AM
From: AP615
Subject: Mitel not getting IP's when rebooting in iniatial setup (CPPM and AOS-CX)
I had a similar issue and the problem was the phones were sticking on their current configuration which was originally a tagged vlan.
Phones also stuck on "discovering"
After I cleared the phone configs - like a factory reset of sorts on the phone they worked fine.
I was moving away from tagged vlan to untagged at the time, but the tagged vlan config appeared to be "sticky" on the phones themselves.
Original Message:
Sent: Feb 14, 2025 10:56 AM
From: dvcm
Subject: Mitel not getting IP's when rebooting in iniatial setup (CPPM and AOS-CX)
Hi @HR-abaef5
I've checked with Wireshark to confirm, but no EAPOL has ever been sent and 802.1x is not enabled on the phone.
output:
6200# sh port-acc clients interface 1/1/5 detail
Port Access Client Status Details:
RADIUS overridden user roles are suffixed with '*'
Client 00:08:5d:b4:95:b0, 00085db495b0
======================================
Session Details
---------------
Port : 1/1/5
Session Time : 326925s
IPv4 Address :
IPv6 Address :
Device Type :
VLAN Details
------------
VLAN Group Name :
VLANs Assigned : 1720
Access : 1720
Native Untagged :
Allowed Trunk :
Authentication Details
----------------------
Status : mac-auth Authenticated
Auth Precedence : mac-auth - Authenticated, dot1x - Not attempted
Auth History : mac-auth - Authenticated, 326925s ago
MACsec Details
--------------
MKA Session Status :
MACsec Status :
Authorization Details
----------------------
Role : DUR_CL_TEL_1x20_Untag-3148-8
Status : Applied
Role Information:
Name : DUR_CL_TEL_1x20_Untag-3148-8
Type : clearpass
Status: Completed
----------------------------------------------
Reauthentication Period : 4294967295 secs
Client Inactivity Timeout : None
Access VLAN Name : CL-TEL
Policy : AllowAll_DUR_CL_TEL_1x20_Untag-3148-8
Access Policy Details:
Policy Name : AllowAll_DUR_CL_TEL_1x20_Untag-3148-8
Policy Type : Downloaded
Policy Status : Applied
Base Policy : N/A
ACL Names : N/A
SEQUENCE CLASS TYPE ACTION
----------- ---------------------------- ---- ----------------------------------
10 AllTraffic_DUR_CL_TEL_1x2... ipv4 permit
Class Details:
class ip AllTraffic_DUR_CL_TEL_1x20_Untag-3148-8
10 match any any any
Original Message:
Sent: Feb 14, 2025 04:01 AM
From: Herman Robers
Subject: Mitel not getting IP's when rebooting in iniatial setup (CPPM and AOS-CX)
Could it be that your phones (after fully provisioned, upgraded to latest version) attempt 802.1X authentication but fail as they have not been configured correctly, or that ClearPass is not configured to handle 802.1X for those phones (client root CA imported, trusted for EAP)?
It would help to see the show the 'show port-access clients 1/1/1 detail' (assuming phone connected on interface 1/1/1) when the issue happens to see the mac/802.1X status.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.