Wired Intelligent Edge

 View Only
last person joined: yesterday 

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
Back to discussions
Expand all | Collapse all

VOICE VLAN - device-identity and device-profile association

This thread has been viewed 22 times

  • 1.  VOICE VLAN - device-identity and device-profile association

    Posted Jul 06, 2022 02:05 PM
    Good morning. I've configured the voice VLAN on several 2930f switches and created a device-identity, device-profile and associated the identity to the profile and enabled it. The issue is when I connect the new YEALINK SIP-T54W phone the device doesn't become part of the VLAN 100 (voice).

    device-identity name "YEALINK SIP-T54W"
    lldp oui 805e0c sub-type 1
    exit
    device-profile name "Yealink Desk Phone"
    tagged-vlan 100
    allow-jumbo-frames
    exit
    device-profile device-type "YEALINK SIP-T54W"
    associate "Yealink Desk Phone"
    enable
    exit

    We are using a CISCO Meraki for the VLAN 100 DHCP.

    Thank in advance,
    jw


  • 2.  RE: VOICE VLAN - device-identity and device-profile association

    Posted Jul 07, 2022 02:56 AM
    Please check the output of "show device-profile status" to check if device profile is applied and if so, is the phone sending tagged DHCP packet ? capture the packets and verify it.

    ------------------------------
    Shobana
    Aruba
    ------------------------------

    Original Message


  • 3.  RE: VOICE VLAN - device-identity and device-profile association

    Posted Jul 07, 2022 08:55 AM

    Thank you. I found the answer using Wireshark and using the Sys-Name.

     

    Much appreciated.

     

     

     

     

    James Walz

    Network Administrator

     

    Office:  

    717‑632‑8240, 3131

    Mobile: 

    (717) 873-5031

    jwalz@conewago.com

    www.conewago.com

     

     

     




    Original Message


  • 4.  RE: VOICE VLAN - device-identity and device-profile association

    Posted Jul 08, 2022 07:56 AM
    I've used Wireshark and captured the packets. I see its being assigned to VLAN 100 Voice tagged and not being assigned an IP address in the vlan.

    Thanought?
    Original Message


  • 5.  RE: VOICE VLAN - device-identity and device-profile association

    EMPLOYEE
    Posted Jul 07, 2022 05:51 AM

    You need to check if your YEALINK SIP-T54W phone is really sending an Organizationally Specific TLV which you configured to match on using the following command: "lldp oui 805e0c sub-type 1".

    There are not much devices that send those TLVs. So best to check if you mirror the port to a PC and capture the LLDP traffic using Wireshark.

    If your phone is not sending this YEALINK specific TLV there may be other solutions to fit your needs like:

    • - Match on LLDP  System Name (type 5)
      - Match on LLDP System Description (type 6)
      -       Match on LLDP-MED existence (lldp oui 0012bb sub-type 1)


    Original Message


  • 6.  RE: VOICE VLAN - device-identity and device-profile association

    Posted Jul 07, 2022 08:54 AM

    Thank you for your reply. I think I've got it now using the Sys-name.

     

    Much appreciated.

     

     

     

     

    James Walz

    Network Administrator

     

    Office:  

    717‑632‑8240, 3131

    Mobile: 

    (717) 873-5031

    jwalz@conewago.com

    www.conewago.com

     

     

     




    Original Message


  • 7.  RE: VOICE VLAN - device-identity and device-profile association

    Posted Jul 07, 2022 10:49 AM
    I changed the device-identity to use the Sys-name type 5, and the device does show up when I use show device-profile status. But the device(s) are not being added to the VLAN 100. I can manually tag each port and each are assigned an IP in the VLAN 10 range I set.

    Any ideas?
    Than in advance, jw

    ------------------------------
    James Walz
    ------------------------------

    Original Message