I'd suggest that you don't skip to zaku but skip to destiny instead. If you still have this problem in destiny, can you please tell us about your setup? Like switch types (ProCurve?), whether you are using FlowVisor, etc.?
-- Murphy On Jan 14, 2012, at 7:31 AM, Theophlius Benson wrote: > I'm making the switch from NOX 0.8.0~full~beta (nox_core) to NOX > 0.9.0(zaku)~full~beta > > I go zaku from git and have made no modifications. I'm testing out the > routing module and noticed that the discovery module is print out some weird > errors and it is unable to discover any links . Note, when I do switch to > the old version .. these links are discovered and routing module works > appropriately. The errors are below. Did the format of the dpid change > between versions? In the past version the switches had this DPID > 002347cc4400 but now they have 06d6002347cc4400 > > 00623|openflow-event|DBG:received packet-in event from 06d6002347cc4400 > (len:128) > 00624|discovery|DBG:Recieved LLDP packet from unconnected switch > 00625|openflow-event|DBG:received packet-in event from 06d6002347cc4400 > (len:34) > 00626|discovery|DBG:Recieved LLDP packet from unconnected switch > 00627|openflow-event|DBG:received packet-in event from 06d6002347cc4400 > (len:34) > 00628|discovery|DBG:Recieved LLDP packet from unconnected switch > > > > > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
