Re: [nox-dev] [openflow-discuss] discovery errors using nox destiny as a learning switch with flowvisor 0.6.4 and HP switches in VLAN aggregation mode

2010-11-12 Thread kk yap
It is not clear to me what this patch is. From what I understand, it is because some switches does not completely strip VLAN tags. Is that what this is? Can't really comment on anything I do not understand, beyond I am unclear on what this is. As for patches, I am particularly touchy on

Re: [nox-dev] [openflow-discuss] discovery errors using nox destiny as a learning switch with flowvisor 0.6.4 and HP switches in VLAN aggregation mode

2010-11-12 Thread Christopher J. Tengi
KK, Here is what I have seen with my particular switch configuration. For the Asterix demo, a tunnel machine was set up with one interface connected to the Princeton campus network and another interface connected to an HP 5406zl OpenFlow switch. The OpenFlow switch port was manually

Re: [nox-dev] [openflow-discuss] discovery errors using nox destiny as a learning switch with flowvisor 0.6.4 and HP switches in VLAN aggregation mode

2010-11-12 Thread kk yap
Hi, I must say this patch sits very much on the gray zone. I personally think we can take it in as long as it does not affect other switch implementation. Of course, I am assuming discovery will not use VLAN tag for other purposes here. I am happy to push this as long as I can have someone

Re: [nox-dev] [openflow-discuss] discovery errors using nox destiny as a learning switch with flowvisor 0.6.4 and HP switches in VLAN aggregation mode

2010-11-12 Thread Srini Seetharaman
Hi KK/Chris This patch by itself won't work because it doesn't keep track of VLAN IDs to reuse in the packet_out for the LLDP. Let me rewrite one for that and send you after testing it in our HP network in Flashlab. Srini. On Fri, Nov 12, 2010 at 1:48 PM, kk yap yap...@stanford.edu wrote: Hi,