[I was thinking someone closer to the deployments would answer this, but this question has been outstanding for a few days, so let me give it a try] \ Hi Tim,
There was a previous bad interaction between the HP firmware and Nox. The crux of the problem was that HP firmware uses all 8 bytes of the datapath id and nox only considers 6 bytes, so Nox believed that two switches with the same DPID were connecting to it (because the DPIDs only differ in the two bytes that nox does not consider). The short story was there was a verison of the HP firmware that worked around this problem, but I can't seem to pull up that version information right now. Hopefully someone else on the list can provide this. - Rob . On Fri, Jun 25, 2010 at 10:48 AM, <tim.upthegr...@gatech.edu> wrote: > Hi all, > > I am not sure if this is an issue with my configuration, HP, or nox, but here > is the issue... when I run multiple openflow instances in an HP switch, the > two instances seem to fight over the same dpid in nox. > > First, enable only one instance... > > 00033|openflow|DBG:Passive tcp interface bound to port 6633 > 00034|nox|INFO:nox bootstrap complete > 00035|openflow|DBG:Passive tcp interface received connection > 00036|openflow|DBG:stream: negotiated OpenFlow version 0x97 (we support > versions 0x97 to 0x97 inclusive, peer no later than version 0x97) > 00037|nox|DBG:Success sending in 'sending switch config' > 00038|nox|DBG:Success sending in 'receiving features reply' > 00039|nox|DBG:Success receiving in 'receiving features reply' > 00040|nox|DBG:Success sending in 'receiving ofmp capability reply' > 00041|nox|DBG:Success receiving in 'receiving ofmp capability reply' > 00042|nox|DBG:Datapath f500019bbb30d00 sent error in response to capability > reply, assuming no management support > 00043|nox|DBG:No switch auth module registered, auto-approving switch > 00044|nox|DBG:Registering switch with DPID = 19bbb30d00 > 00045|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00046|switch|DBG:learned that 00:0a:41:ad:c1:81 is on datapath 0019bbb30d00 > port 18 > 00047|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00048|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00049|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00050|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00051|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > > > Enable the second instance on the HP switch.... > > > 00052|openflow|DBG:Passive tcp interface received connection > 00053|openflow|DBG:stream: negotiated OpenFlow version 0x97 (we support > versions 0x97 to 0x97 inclusive, peer no later than version 0x97) > 00054|nox|DBG:Success sending in 'sending switch config' > 00055|nox|DBG:Success sending in 'receiving features reply' > 00056|nox|DBG:Success receiving in 'receiving features reply' > 00057|nox|DBG:Success sending in 'receiving ofmp capability reply' > 00058|nox|DBG:Success receiving in 'receiving ofmp capability reply' > 00059|nox|DBG:Datapath f510019bbb30d00 sent error in response to capability > reply, assuming no management support > 00060|nox|DBG:No switch auth module registered, auto-approving switch > 00061|nox|DBG:Registering switch with DPID = 19bbb30d00 > 00062|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00063|openflow|DBG:Passive tcp interface received connection > 00064|openflow|DBG:stream: negotiated OpenFlow version 0x97 (we support > versions 0x97 to 0x97 inclusive, peer no later than version 0x97) > 00065|nox|DBG:Success sending in 'sending switch config' > 00066|nox|DBG:Success sending in 'receiving features reply' > 00067|nox|DBG:Success receiving in 'receiving features reply' > 00068|nox|DBG:Success sending in 'receiving ofmp capability reply' > 00069|nox|DBG:Success receiving in 'receiving ofmp capability reply' > 00070|nox|DBG:Datapath f500019bbb30d00 sent error in response to capability > reply, assuming no management support > 00071|nox|DBG:No switch auth module registered, auto-approving switch > 00072|nox|DBG:Registering switch with DPID = 19bbb30d00 > 00073|openflow|DBG:Passive tcp interface received connection > 00074|openflow|DBG:stream: negotiated OpenFlow version 0x97 (we support > versions 0x97 to 0x97 inclusive, peer no later than version 0x97) > 00075|nox|DBG:Success sending in 'sending switch config' > 00076|nox|DBG:Success sending in 'receiving features reply' > 00077|nox|DBG:Success receiving in 'receiving features reply' > 00078|nox|DBG:Success sending in 'receiving ofmp capability reply' > 00079|nox|DBG:Success receiving in 'receiving ofmp capability reply' > 00080|nox|DBG:Datapath f510019bbb30d00 sent error in response to capability > reply, assuming no management support > 00081|nox|DBG:No switch auth module registered, auto-approving switch > 00082|nox|DBG:Registering switch with DPID = 19bbb30d00 > 00083|openflow-event|DBG:received packet-in event from 0019bbb30d00 (len:64) > 00084|openflow|DBG:Passive tcp interface received connection > 00085|openflow|DBG:stream: negotiated OpenFlow version 0x97 (we support > versions 0x97 to 0x97 inclusive, peer no later than version 0x97) > 00086|nox|DBG:Success sending in 'sending switch config' > 00087|nox|DBG:Success sending in 'receiving features reply' > 00088|nox|DBG:Success receiving in 'receiving features reply' > 00089|nox|DBG:Success sending in 'receiving ofmp capability reply' > 00090|nox|DBG:Success receiving in 'receiving ofmp capability reply' > 00091|nox|DBG:Datapath f500019bbb30d00 sent error in response to capability > reply, assuming no management support > 00092|nox|DBG:No switch auth module registered, auto-approving switch > 00093|nox|DBG:Registering switch with DPID = 19bbb30d00 > ....... > > As you can see, the two instances with datapath f5 0 0019bbb30d00 and f5 1 > 0019bbb30d00 are both recognized, but nox seems to repeatedly register them, > flipping between the two. Has anyone else seen this problem? > > When connecting the switch directly to nox, I can still ping hosts connected > to the HP switch with some slowdown, but when running the network with > flowvisor, the reliability is not so good. > > > Version info: > > NOX 0.8.0~full~beta (nox_core), compiled Mar 19 2010 02:22:28 > Compiled with OpenFlow 0x97 (exp) > > Image stamp: /sw/code/build/btm(jeant_openflow) > Aug 31 2009 15:45:23 > K.14.41hpl > 70 > > Thanks in advance! > > Tim Upthegrove > Georgia Institute of Technology > College of Computing > (406)-437-1493 > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
