<html><head></head><body><div class="gmail_quote">On July 3, 2019 4:59:56 PM PDT, "Heim, Dennis" <Dennis.Heim@wwt.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Is there a module that exists for that? <br><br>Sent from my iPhone<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Jul 3, 2019, at 7:58 PM, Ben Pfaff <blp@ovn.org> wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">On Wed, Jul 03, 2019 at 09:25:24PM +0000, Heim, Dennis wrote:<br>My topology is I have VLANs (10,11,12, 15) configured as access ports on the OvS. I also have a VLAN trunk terminating on my Cisco CSR1K. I have layer 3 interfaces on the CSR1Kv. When the OvS is standalone it works without a problem. However, when I connect it to the ONOS controller, pings do not reach the CSR1K. With some testing, it appears when connected to the controller, it is not sending the vlan tags. If I go to the CSR1Kv and configure VLAN10 as the native vlan, then VLAN 10 can ping the interface.<br><br>Is there something that has to be done when connected to a controller to get it to VLAN tag the traffic?<br></blockquote><br>If ONOS is controlling OVS, then it needs to implement the VLAN support<br>itself.<br></blockquote></pre></blockquote></div><br clear="all">I don't know.</body></html>