Wired Intelligent Edge

last person joined: 15 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

DUR and role assignment with PC behind IPphone

This thread has been viewed 10 times
  • 1.  DUR and role assignment with PC behind IPphone

    EMPLOYEE
    Posted Sep 14, 2019 02:17 AM

    Hi all, a client has 2930F switches along with some Avaya IP phones. They are keen on CPPM and dynamic role assignment through it. Now since laptops/desktops are connected to 2930F through the IP phone inbuilt LAN port and not directly to 2930F, how will the role assignment work? authentication will be done for IP phones and users both so will the same switch port which is connected to IP phone and then to user have multiple role assignments simultaneously and how will the traffic flow?

    Please help. Thanks in advance



  • 2.  RE: DUR and role assignment with PC behind IPphone

    MVP GURU
    Posted Sep 15, 2019 04:51 AM

    Hi,

     

    depend of authentification method (by port or by client)

    if it is by port all traffic will be considered IP Phone (not recommended...)

    if it is by client (a address mac), it will be a first authentification for IP Phone and a second for laptop



  • 3.  RE: DUR and role assignment with PC behind IPphone

    EMPLOYEE
    Posted Sep 19, 2019 04:03 AM

    thanks for your reply. Yes we will do client authentication, for user we want to do 802.1x and for IP phones we will do MAC



  • 4.  RE: DUR and role assignment with PC behind IPphone

    MVP GURU
    Posted Sep 24, 2019 06:47 PM

    and ? don't work ?



  • 5.  RE: DUR and role assignment with PC behind IPphone

    EMPLOYEE
    Posted Sep 25, 2019 05:55 AM

    Hi mohanvnegi,

     

    DUR is based on "user-based authentication".

    So it means that you can assign different user-roles on a same port, in the limit of 32, as each user/device will be individually authenticated.

    Once authenticated, the match between the user and the Role/Network Profile, and so the VLAN, is made through its MAC Address.

     

    So, your implementation is totally supported :

    You can use 2 different user-roles, with 2 different profiles, assigned by 2 different authentication methods, without any issue.

    You can even assign your user to a tunnel if you want to use Dynamic Segmentation, and let your IP Phone forward on the legacy network.

     

    You can refer to the "Access Security Guide" if you need more informations regarding User-Based and Port-Based Authentication modes.

    You can also look at the "ClearPass Solutions Guide: Wired Policy Enforcement"  document.