At the moment, Voice will still only be available via 4.22.1F pre-releases, and commands/functionality/troubleshooting is subject to change as we approach GA. For now, the following is the information is what we currently have on Voice that we know has been tested:
switchport mode trunk phone
switchport phone trunk […]
switchport phone vlan
Fair enough. Device came with eos version 4.21.6F installed and therefore these interface level commands are not available. How can I get the 4.22 pre-release to test? Potential new customer here doing a testing/proof of concept. Unfortunately we only have a limited test window.
You can now download 4.22.1FX-Campus which will allow you to play around with supported Voice VLAN scenarios:
At the moment, we don’t support the LLDP MED TLV, but the good news is that LLDP-MED is not required for the switch to know it is connected to an IP phone. The basic LLDP “System Capabilities” TLV works.
We support learning the Voice VLAN via:
If you are configuring the CLI, you will be using trunking ports (not access ports – that won’t work) and have a couple of choices here as Roberto mentioned above.
Hope this helps!
Hi Cord and Saskia,
Let me rephrase my previous answer and expound a bit as I see how it can be misleading.
Arista has implemented a mechanism to support VoIP phones (including support for PC behind IP Phones) in a way that existing deployments of IP Phones can work with Arista POE switches without need to change anything in IP phone, AAA server, Call-Manager or other associated entities.
Traditionally, VLAN and QoS/DSCP setting to be used for voice traffic are conveyed to phone over LLDP using the MED extension to LLDP.
Arista's implementation doesn't use MED extension. Instead, the switch is able to add the VLAN and QoS/DSCP setting (or port set to trust QoS/DSCP setting from phone) once the device has been classified as a phone. The classification is done with attributes from LLDP which are then validated with commonly deployed AAA servers (ex. ISE).
Once the device has been authenticated Arista switches slap the VLAN and QoS to VoIP traffic at the ingress port of PoE switch to which phone is connected. We believe that this is a cleaner way of enforcing VLAN and/or QoS/DSCP parameters as the control is 100% in-network. With advances in Silicon technology and software maturity, this implementation provides a normalized and unambiguous way of ensuring that VLAN and/or QoS/DSCP are correctly set for voice traffic.
Arista's EOS supports power negotiation through the IEEE Std 802.3-2015 "Power-via-MDI" TLV.
The following configuration in Arista's PoE switches will allow for IP Phones to work without any changes to phone or other associated entities.
conf# interface eth X
The "phone plan Y" can be overridden by AAA assigned VLAN. If AAA server doesn't assign any VLAN then VLAN. Y will be used for VoIP traffic.
Let me know how this goes. Take a look at a tcpdump on the interface, review "show lldp neighbors detail" also let me know if you upgraded to the 4.22.1FX-Campus EOS version.
Unfortunately I don’t have anything to test it yet. Seems like the vmdk version doesn’t support this feature in my lab.
Yes, the parameters you’ve mentioned will work with IP Phones.
Switch configs provided by Sarah Howell is the right config. AAA is optional. If you don’t configure AAA-based AUTH and/or VLAN assignment the phone value Y mentioned above will the VLAN on which VoIP traffic will be mapped to.
PC traffic will be mapped to native VLAN.
As long as phone is enabled to do LLDP (which presumably is needed even in prior configs) we’re good.
Thanks for the concise answer. You guys are quick! Sarah’s config is now working for me. Thanks again.
Post your Answer
You must be logged in to post an answer.