I believe you're basically asking the switch to route (or at least switch) between the management port and the dataplane. The short answer is that the switch won't do this and it's not planned to be supported.
You probably want "physical in-band management" where the Pronto switch is managed by a connection accessed through a data plane port. This feature is not yet fully supported on the Pronto platforms, although some people are working with it now. Note that although physically on a dataplane port, the connection may still be logically separated from the OpenFlow controlled traffic. If you take this approach (of physical in-band) would you expect to be able to dedicate a VLAN to management (including the controller traffic)? The alternative is to have OpenFlow controlling the traffic to the controller, something that has enough pitfalls that no one has really gotten it to work reliably. -Dan On Wednesday, May 9, 2012 at 1:17 PM, Heming Wen wrote: > Greetings, > > We are currently setting up a basic Openflow Wireless testbed with three PC > Engine AP and a Pronto 3290 switch in our labs. We have a few questions > regarding the connection between the elements: > > 1) There are three controller path setups possible: L3 inband, tunneling and > L2 inband. If we want to setup a small demo (n-casting for instance), is > there a preference for a particular configuration? > > 2) How must the Openflow controller connected to the network in order to > control the AP? Right now, the openflow controller is connected to the > special ethernet port of the Pronto switch (in order to control the switch). > The default pyswitch controller can detect the Indigo/Pronto switch. However, > the AP is connected to the switching plane of the Pronto switch. Is there a > way to access the switching plane ports from the control port or must the > controller be connected in a different fashion? Right now, pinging doesn't > work between the switching plane and the control plane. > > Thank you for your help, > > Heming > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > (mailto:openflow-discuss@lists.stanford.edu) > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
