FYI, this problem was tracked down to a config problem, not a flowvisor or
nox bug ;-)
- Rob
.
On Sat, Oct 16, 2010 at 1:51 AM, Niky Riga nr...@bbn.com wrote:
Hi KK,
Attached are nox's log files.
* pathlet.out : the log file when I run the pathlet controller on the slice
* pyswitch.out :
What about having a tcpdump of the control traffic between NOX to/from
FV, and FV to/from switch? Each disconnection will have a new
connection following it, then you will see the hellos, feature
requests and replies, etc.
I would like to see the NOX's log too. NOX typically does not kill a
KK: I've looked through the tcpdumps and the sequence is:
HELLO
HELLO
FEATURE_REQUEST
FEATURE_REPLY
VENDOR MSG
ERROR (vendor unsupported)
PACKET_IN (lldp)
and then disconnect
- Rob
.
On Fri, Oct 15, 2010 at 9:07 PM, kk yap yap...@stanford.edu wrote:
What about having a tcpdump of
Two of the switches are local to stanford and NECs:
necsw2 (00:00:00:12:e2:78:31:f5)
necsw(00:00:00:12:e2:78:67:65)
necsw is the main connection point to the other flowvisors, so it would
receive packet_in's from the other flowvisor.
- Rob
.
On Fri, Oct 15, 2010 at 9:15 PM, kk yap
Sorry... the ... meant more packet_in's.
- Rob
.
On Fri, Oct 15, 2010 at 9:15 PM, kk yap yap...@stanford.edu wrote:
ERROR (vendor unsupported)
PACKET_IN (lldp)
and then disconnect
Can I know the model of the switch, and what ... means? The front
part looks correct at a glance.
Can someone send the pcap file on the list, so that people can
actually start doing real investigation here? If it is too big, send
to Nick Bastin? (Sorry, Nick...)
I would still like to see the NOX's output.
Regards
KK
On 15 October 2010 21:36, Rob Sherwood rob.sherw...@stanford.edu wrote:
I've put the pcapfile on yuba:~capveg/nineveh-fv.tcpdump (for those who have
access... it's a 2MB file).
It's a trace of both to the FV on nineveh:6633 (from the FV on openflow5)
and to the controller on nineveh:1734. If you just filter on port 1734 you
get just the controller traffic.
- Rob
.
