<p dir="ltr">Spanning tree is off by default too on mlx code, so you shouldn't be seeing those regardless on the new vlan.</p>
<p dir="ltr">Mike </p>
<div class="gmail_quote">On Jun 24, 2016 6:09 PM, "i3D.net - Martijn Schmidt" <<a href="mailto:martijnschmidt@i3d.net">martijnschmidt@i3d.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Gerald,<br>
<br>
There are more BPDU types than just spanning-tree.. :-) You should apply<br>
"no fdp enable" and "no spanning-tree" on the physical interface ethe<br>
1/2, as well as "no ip redirect" and "ipv6 nd suppress-ra" on the VE's<br>
which are facing that interface. This should be enough to make the MLXe<br>
shut up if "route-only" is also enabled on a global level (though it<br>
should be ok with an interface-level "route-only" setting too).<br>
<br>
Best regards,<br>
Martijn Schmidt<br>
<br>
On 06/24/2016 11:59 PM, Gerald wrote:<br>
> Oh, maybe the trick is disabling STP an the port too:<br>
><br>
> !<br>
> vlan 666 name dummy-layer3-vlan<br>
> untag eth 1/2<br>
> spanning-tree ethernet 1/2 disable<br>
> !<br>
><br>
> Am 24.06.2016 um 23:54 schrieb Gerald:<br>
>> All right, I've tested this and now the MLX seems to generate VLAN666<br>
>> BPDUs by itself on this port. At least I can see that the "BPDU Config<br>
>> tx" counter is still rising.<br>
>><br>
>> So I can stop flooding VLAN1 BPDUs from other ports but now we have new<br>
>> VLAN666 BPDUs on that port transmitted.<br>
>><br>
>> From one hell to the other... which one is better :-/<br>
>><br>
>><br>
>> Gerald<br>
>><br>
>> Am 24.06.2016 um 23:35 schrieb Clement Cavadore:<br>
>>> Yes thats it ;)<br>
>>><br>
>>> Le 24 juin 2016 23:30:02 GMT+02:00, Gerald <<a href="mailto:gerald@ax.tc">gerald@ax.tc</a>> a écrit :<br>
>>>> Oops, need sleep ;-)<br>
>>>><br>
>>>> !<br>
>>>> int eth 1/2<br>
>>>> enable<br>
>>>> route-only<br>
>>>> ip addres <a href="http://10.0.0.1/24" rel="noreferrer" target="_blank">10.0.0.1/24</a><br>
>>>> !<br>
>>>> vlan 666 name dummy-layer3-vlan<br>
>>>> untag eth 1/2<br>
>>>> !<br>
>>>><br>
>>>> Am 24.06.2016 um 23:27 schrieb Gerald:<br>
>>>>> Thx Clement for this advice, did you mean something like this:<br>
>>>>><br>
>>>>> !<br>
>>>>> int eth 1/2<br>
>>>>> enable<br>
>>>>> route-only<br>
>>>>> ip addres <a href="http://10.0.0.1/14" rel="noreferrer" target="_blank">10.0.0.1/14</a><br>
>>>>> !<br>
>>>>> vlan 666 name dummy-layer3-vlan<br>
>>>>> untag eth 2/12<br>
>>>>> !<br>
>>>>><br>
>>>>><br>
>>>>> Gerald<br>
>>>>><br>
>>>>> Am 24.06.2016 um 21:59 schrieb Clement Cavadore:<br>
>>>>>> You should create some "dummy" vlans on route-only ports, to avoid<br>
>>>> that.<br>
>>>>>> No problem having untagged vlan on any port with IP/routing<br>
>>>> configuration. You even ca do this without any disturbance.<br>
>>>>>> Le 24 juin 2016 21:53:08 GMT+02:00, Gerald <<a href="mailto:gerald@ax.tc">gerald@ax.tc</a>> a écrit :<br>
>>>>>>> The MLX got a reboot some weeks ago, this seems not to help. I'am<br>
>>>>>>> afraid<br>
>>>>>>> of your (1) note... :-(.<br>
>>>>>>><br>
>>>>>>> Gerald<br>
>>>>>>><br>
>>>>>>> Am 24.06.2016 um 21:27 schrieb Steven Raymond:<br>
>>>>>>>>> On Jun 24, 2016, at 1:19 PM, Gerald <<a href="mailto:gerald@ax.tc">gerald@ax.tc</a>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> Is there a way to stop this? I would have my "route-only" ports<br>
>>>>>>> Layer2<br>
>>>>>>>>> free and not disturb other Layer2 systems behind.<br>
>>>>>>>> Old old notes I found said basically 1) “bpdus are sent even with<br>
>>>>>>> route-only”, and 2) "you should reboot after applying route-only".<br>
>>>>>>>> Both of which may not helpful to you.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>> _______________________________________________<br>
>>>>>>> foundry-nsp mailing list<br>
>>>>>>> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
>>>>>>> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> _______________________________________________<br>
> foundry-nsp mailing list<br>
> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></blockquote></div>