Thanks, Natasha. So the registration is optional and this does not explain why I can't see flows sent from the switch to NOX and flow entries sent back. Correct?
Gershon Schatzberg From: Natasha Gude [mailto:[email protected]] Sent: Thursday, February 11, 2010 4:22 PM To: Gershon Schatzberg Cc: nox-dev Subject: Re: [nox-dev] meaning of debug message: switch xxx isn't registered Hi Gershon, These messages just signal that nox hasn't been informed of the existence of these switches and their ports, and thus cannot tag them with a specific id. If an application wanted to, it could "register" switches and locations with the authenticator using the update_switch/location methods - tying a switch datapathid or location datapathid+port number to an opaque integer identifier respectively. Natasha On Thu, Feb 11, 2010 at 4:02 PM, Gershon Schatzberg <[email protected]> wrote: I am getting the following output on NOX 0.6 when connecting a HW switch (20 ports) running the reference design: ----------------------------- 00065|openflow|DBG:Passive tcp interface received connection 00066|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00067|nox|DBG:Success sending in 'sending switch config' 00068|nox|DBG:Success sending in 'receiving features reply' 00069|nox|DBG:Success receiving in 'receiving features reply' 00070|nox|DBG:Success sending in 'receiving ofmp capability reply' 00071|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00072|nox|DBG:Datapath 002320a19545 sent error in response to capability reply, assuming no management support 00073|nox|DBG:No switch auth module registered, auto-approving switch 00074|nox|DBG:Registering switch with DPID = 2320a19545 00075|authenticator|DBG:Received dp 2320a19545 join. 00076|authenticator|DBG:Switch 2320a19545 isn't registered 00077|authenticator|DBG:Location 2320a19545:1 isn't registered 00078|authenticator|DBG:Location 2320a19545:2 isn't registered 00079|authenticator|DBG:Location 2320a19545:3 isn't registered 00080|authenticator|DBG:Location 2320a19545:4 isn't registered 00081|authenticator|DBG:Location 2320a19545:5 isn't registered 00082|authenticator|DBG:Location 2320a19545:6 isn't registered 00083|authenticator|DBG:Location 2320a19545:7 isn't registered 00084|authenticator|DBG:Location 2320a19545:8 isn't registered 00085|authenticator|DBG:Location 2320a19545:9 isn't registered 00086|authenticator|DBG:Location 2320a19545:10 isn't registered 00087|authenticator|DBG:Location 2320a19545:11 isn't registered 00088|authenticator|DBG:Location 2320a19545:12 isn't registered 00089|authenticator|DBG:Location 2320a19545:13 isn't registered 00090|authenticator|DBG:Location 2320a19545:14 isn't registered 00091|authenticator|DBG:Location 2320a19545:15 isn't registered 00092|authenticator|DBG:Location 2320a19545:16 isn't registered 00093|authenticator|DBG:Location 2320a19545:17 isn't registered 00094|authenticator|DBG:Location 2320a19545:18 isn't registered 00095|authenticator|DBG:Location 2320a19545:19 isn't registered 00096|authenticator|DBG:Location 2320a19545:20 isn't registered 00097|authenticator|DBG:Location 2320a19545:65534 isn't registered 00098|openflow|DBG:stream: idle 15 seconds, sending inactivity probe 00099|openflow|DBG:stream: message received, entering CONNECTED ------------------------------------ What do these debug messages indicate? Gershon Schatzberg _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
