Wired Intelligent Edge

 View Only
  • 1.  VLAN tagging for voice is not working

    Posted Jul 05, 2023 12:34 PM

    Hello,

    From last 2 days I am facing issue with VLAN tagging for voice vlan in Aruba the same setting is working on other site switch but in this switch i tried many time but the result is still Zero

    1) I have IP-Phone and Computer connect to IP-Phone our requirment is to put IP-phone in other subnet and Computer connected to IP phone must be in other network

    = to achive this we have done SVI on HP router and on Aruba Switch Tagging vlann (this is for trunk port)

    =Aruba switch port 48(trunk port config)

    vlan tagged 5, 15, 25, 25

    untagged 1

    = access port config 

    ethernet 21

    tagged vlan 35 voice

    untagged vlan 25

    --problem (even after tagging my IP-phone is not getting IP from vlan 35 network it is still getting IP from Vlan 25 network)

    --Addtional info 

    IP-phone we have already enable vlan tag id 35 (this similar settting working on other site)

    Switch Os version is  16YA .006

    J9782A



  • 2.  RE: VLAN tagging for voice is not working

    Posted Jul 06, 2023 07:56 AM

    If your phone receives an IP from VLAN 25, it's most likely that the phone does not use the tagged vlan 35. Depending on the phone, it will learn that through LLDP, DHCP, static configuration or through your PBX. Do you have LLDP enabled on your switch? Many phones learn (or can learn) the voice VLAN id through LLDP.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    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.
    ------------------------------



  • 3.  RE: VLAN tagging for voice is not working

    Posted Jul 06, 2023 11:01 AM

    1) Phone model is Astra

    2) Phone Model is Mitel

    in Astra Phone we are facing issue but in mitel it is working fine 

    LLDP is enable on port 

    Astra Phone we have also enable LLDP and Vlantagging 




  • 4.  RE: VLAN tagging for voice is not working

    Posted Jul 07, 2023 05:49 AM

    Because it works fine with Mitel but not with Astra, it may be good to work with Astra support. If you want to do some research yourself, you may configure a port mirror for the port that the phone is connected, and see what switch and phone are doing/sending, and if it's tagged or untagged, but based on the limited information it's hard to assist in this forum.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    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.
    ------------------------------



  • 5.  RE: VLAN tagging for voice is not working

    Posted Jul 11, 2023 11:55 AM
    Edited by wdubose Jul 11, 2023 12:19 PM

    We have Aruba 6200f VRF switch stacks at the access layer.  This is how I successfully have my IP phones configured:

    my VOICE VLAN is 46

    my DATA VLAN is 35

    I specify whatever my data VLAN is (35 in this example) as the native VLAN for the interface that the phone and PC are connected to.  I then specify both the voice and data VLANs as trunks for that same interface.

    int 1/1/x

    vlan trunk native 35 

    vlan trunk allowed 35,46

    On our old HP switches and Aruba OS 2930f switches, you are allowed to specify both trunk (tagged) and access (untagged) on the same interface.  The same result as above is accomplished with the following:

    int 1/1/x

    untagged 35

    tagged 46