Posted on July 6, 2015 2:25 pm
 |  Asked by Ramesh
Print Friendly, PDF & Email

I have a running Openstack Instance which is integrated through CVX and Arista L2 switch (7050SX) for Layer-2 VLAN integration and Also the L3 router functionality integrated with same Arista switch for L3 gateway.

Currently while I am creating networks in Openstack as VLAN type are getting created in Arista switch – Working fine.

Also while I create L3 gateway, the same is getting created in Arista Switch – Working fine.


Now, next I need to have vxlan as network type in Openstack. But it is trying to push same commands and trying to create VLAN in Arista switch using vlan commands.

Can the VLAN and VXLAN network type co-exist in Openstack when it is integrated with Arista?


Posted by Alexis Dacquay
Answered on July 14, 2015 1:02 pm

Hi Ramesh,

Yes you could have VXLAN and VLAN both created on the Arista EOS by Openstack

Which version of Arista EOS and what release of Openstack are you using ? I would recommend a recent EOS version (for example 4.15.1F) and the Kilo release.


In Arista CLI, for VNI-VLAN binding, look at :

        region TEST networks map vlan 100-200 vni 100100-100200


Posted by Ramesh
Answered on July 14, 2015 1:20 pm


Thanks for the reply. I am using  4.15.0FXA version.

But, I’m not looking for a VLAN to VXLAN mapping in the Arista switch. I expect the Openstack to provision VXLAN network in Arista like it provisioning VLAN. This VLAN and VNI mapping only help me between arista to forward VTEP across different TOR switches.



Posted by Philippe Bureau
Answered on July 14, 2015 1:22 pm


Vxlan over L3 fabric requires vxlan controller service to distribute the mac addresses to the hardware Vteps. To enable vxlan controller service on cvx:


(config‐cvx)#service vxlan

(config‐cvx‐vxlan)#no shutdown

On the switches, a vxlan interface needs to be created and the vxlan controller client needs to

be enabled. This can be done by the following commands:

(config)#interface Vxlan 1

(config‐if‐Vx1)#vxlan controller‐client


Posted by Fred
Answered on July 14, 2015 7:04 pm

As of right now you cannot easily mix VLAN and VXLAN ML2 type drivers and have them interoperate (they would not be aware of each other).  The Arista type driver only configures VLANs, and can be used to create a VXLAN overlay between ToR switches as per Alexis’s post.  However, prior to Kilo Neutron did not have a mechanism for configuring an L2 Gateway, and could only configure software VTEPs.  Kilo introduced the L2 Gateway service (co-chaired by Arista) that allows Neutron to configure hardware VTEPs.  We are active in the L2 Gateway project, but do not yet have released code.  Please contact your account team for more details if you need this support.


Posted by Ramesh
Answered on July 15, 2015 7:28 am

Thanks for that answers Fred and Philippe..

My objective was, Let OSP (Openstack) uses Arista to create VLANs, but the vxlan should exists as transport type but locally. THis is happening, but OSP is pushing the configuration into Arista even for vxlan as command ”interface vlan 100100 (vnid)” and this was failing in configured in Arista.

But now things looks ok, since Arita filed a fix in the fix and thats available now.

This will avoid OSP to push the vxlan into Arita switch, but the vlan still will get configured in Arista. The vxlan will be local to OpenstackPlatform.

More details are here.

We are testing this in the lab and will update.

Thanks a lot.


Post your Answer

You must be logged in to post an answer.