Network Management

 View Only

  • 1.  Voice VLAN in 2930f stack

    Posted Aug 14, 2025 02:16 PM

    Hello team!!!

    We have an stack with 3 switches Aruba 2930f

    Currently we have the VLAN 20 created and it is configured in some ports.  This stack is in production

    Now we need to change this VLAN 20 to Voice VLAN.

    As I see in another post, in an answer of Parnasus, this is the procedure:

    config
    vlan 20
    voice
    exit
    write memory
    exit

    Does this have any consideration to take care about?

    Anything could stop working after execute these commands?

    Thanks in advance.

    Regards,

    Damián



    -------------------------------------------


  • 2.  RE: Voice VLAN in 2930f stack

    Posted Aug 14, 2025 02:44 PM
    Hi! AFAIK it should be basically that simple (despite you can do more complex configurations): VLAN 20 should then be set tagged on VoIP ports (so ports are "Voice VLAN 20" tagged).





  • 3.  RE: Voice VLAN in 2930f stack

    Posted Aug 14, 2025 03:06 PM

    Hello Again Parnassus!!

    Thanks for your answer!!

    We have an Avaya IP Office 500, which will be connected to one port.  This device is not tagging packets, so I think this will need to have the VLAN 20 as untagged.

    Is this a problem?

    IP phones are not connected to this stack.

    Thanks in advance.

    Regards,

    Damián

    -------------------------------------------

    Original Message


  • 4.  RE: Voice VLAN in 2930f stack

    Posted Aug 15, 2025 03:41 AM
    Hi! besides your current network configuration (e.g. topology and VLAN tagging), generally VoIP phones should be connected to Switch ports dedicated to edge devices where (considering a data/voice shared scenario) such of a port is untagged member of a "data" VLAN (untagged = native) and, concurrently, is also a tagged member of a "voice" VLAN (so this VLAN is added to the port resulting in a interface operating in "trunk mode" compared to a port operating in "access mode"). VoIP traffic between phones is generally peer to peer (not passing through the IP PBX, your Avaya IPO 500) and flows into the "voice" VLAN (or be routed between different "voice" VLANs if VoIP phones are in different ones). That's to say that the IP PBX could stay connected to a switch on the "voice" VLAN even if its LAN interface is VLAN tagging unaware (and indeed is connected as if it was a normal PC) and connected to a Switch port which is simply "voice" VLAN untagged (so its native VLAN id = "voice" VLAN Id).

    But this in theory...real case scenarios may vastly vary due to issues related to IP Routing, DHCP for VoIP Phones...and so on.



    Original Message


  • 5.  RE: Voice VLAN in 2930f stack

    Posted Aug 15, 2025 08:54 AM

    Hi!!

    Thanks for your answer!

    So, do you recommend to configure only the voice VLAN as tagged even when there is no another VLAN in the port where is the IP PBX connected?

    Regards,

    Damián

    -------------------------------------------

    Original Message


  • 6.  RE: Voice VLAN in 2930f stack

    Posted Aug 15, 2025 11:04 AM
    Hi, no...I eventually suggest you what is a typical scenario (but, again, YMMV): leave the Avaya IPO 500 LAN interface as is (if it can't be set in another way), untagged member of the "voice" VLAN...and set interfaces where VoIP phones are connected as untagged member of a desired VLAN (the native VLAN you eventually need there) and tagged member of the "voice" VLAN. This in the case of a shared approach where the same access port could eventually be use to connect a PC (which, as written, is generally VLAN unaware).



    Original Message


Related Content