View Only
last person joined: 19 hours ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  VOIP without LLDP-MED and with trunk port

    This message was posted by a user wishing to remain anonymous
    Posted 11-27-2023 10:17
    This message was posted by a user wishing to remain anonymous

    Hello Community,

    I am facing issues configuring VOIP.

    We are following the config from 


    But it is showing as not supported as below:

    Kindly advise how can I troubleshoot this.

    As per the Product feature, the link there sends me to the same doc:


    The device that needs to be configured is an EX4100-24p and running Junos 22.3R1.12


    Grateful if you could advise how to fix this or can I ignore the warning message?

    Kind regards,

  • 2.  RE: VOIP without LLDP-MED and with trunk port

    Posted 11-28-2023 02:06


    I believe the EX4100s run ELS JunOS Code. The native-vlan-id configuration has moved to the interface level of the hirachy.

    [edit interfaces]
    user@host# set interface-name native-vlan-id number

    Please refer to: https://www.juniper.net/documentation/us/en/software/junos/multicast-l2/topics/topic-map/layer-2-understanding.html

    And... https://apps.juniper.net/feature-explorer/parent-feature-info.html?pFKey=1370&pFName=Enhanced%20Layer%202%20Software%20(ELS)


  • 3.  RE: VOIP without LLDP-MED and with trunk port

    Posted 11-28-2023 13:19

    Maybe this is not useful and you have decided against the easy way for some reason, but why is it that you want the phones "without LLDP-MED"?

    Even though the doc you referenced shows explicit trunk setup, we find it much more convenient to use the

    "set switch-options voip interface access-ports vlan <voice-vlan-name"

    command, which essentially is a shortcut to make each access port a trunk port with its configured access vlan native, and the voice vlan tagged. 

    We also use:

    set protocols lldp-med interface all

    which means that lldp-med tells the phones the voice-vlan ID.

    So without dot1x, the phone joins the tagged voice-vlan, and any device plugged into the phone joins the port's statically configured VLAN. This setup also works works with our standard dot1x MAC auth, so that the phone is allowed on our voice-vlan, and when a device plugged into the phone's 2nd port, that device's MAC goes off to RADIUS and VLAN name is returned for it.

    (Again, sorry if you have specific detailed reasons for not using the above, but wanted to mention the basic options.)

    Steve Bohrer