Sure Thank you.
Just clarifying your other question.
How i check Port list on the Controller ?
i do a get_features from the controller again for the switche's dpid
after a flow space addition in the flowvisor
When you mean the flowvisor reconnects should i expect the controller to
report an existing connection flap for that dpid ( i.e Disconnected and
Reconnected )
If so i don't see that happening. the connection remains Stable
Thanks
Japson Jacob
On Sun, Oct 21, 2012 at 6:25 PM, Ali Al-Shabibi <ali.al-shab...@stanford.edu
> wrote:
> FlowVisor reconnects to the controller when the flowspace is changed which
> should trigger your controller to redo a features request negotiation which
> will update your switches port list.
>
> Can you verify that this is happening? I will check tomorrow on my side.
>
>
> Cheers.
>
> --
> Ali
>
> On Oct 22, 2012, at 12:08 AM, japson jacob <japson....@gmail.com> wrote:
>
> > Hello again
> > Just pasting the syslog after an add of new flowspace
> >
> >
> ********************************************************************************************************************************************
> >
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: INFO user fvadmin
> ADD for dpid=00:0a:6c:9c:ed:70:6a:c6 match=OFMatch[in_port=2] priority=10
> actions=Slice:sdn=4
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: INFO user fvadmin
> ADD for dpid=00:0a:6c:9c:ed:70:6a:c6 match=OFMatch[in_port=2] priority=10
> actions=Slice:sdn=4
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: INFO user fvadmin
> ADD for dpid=00:0a:6c:9c:ed:70:6a:c6 match=OFMatch[in_port=2] priority=10
> actions=Slice:sdn=4
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: INFO Signalling
> FlowSpace Update to all event handlers
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: INFO Signalling
> FlowSpace Update to all event handlers
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: INFO Signalling
> FlowSpace Update to all event handlers
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: ERROR FIXME: need
> to flush old flow entries
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: ERROR FIXME: need
> to flush old flow entries
> > Oct 21 17:58:41 sdn-vm4 -1>Oct 21 17:58:41 flowvisor: ERROR FIXME: need
> to flush old flow entries
> >
> >
> ********************************************************************************************************************************************
> >
> > Controller in Use is POX. I kind off verified the controller ( getting
> the port_list) by not going thru flowvisor and connecting it directly to
> agent
> > Just a Curious question , On adding a new port to flow_space do you
> expect anything from the Agent to update the controller or it is handled by
> the flowvisor itself.
> > Can you also help me to understand how the flowvisor updates the
> controller when a new port is added
> >
> > Thanks alot for your support thus far
> > Japson Jacob
> >
> >
> >
> > On Sun, Oct 21, 2012 at 5:29 PM, Ali Al-Shabibi <
> ali.al-shab...@stanford.edu> wrote:
> > [re-adding the list; please don't drop it]
> >
> > Hi again,
> >
> > How do you fetch the port list? Also, which controller are you using?
> Are you positive you a fetching a fresh port list?
> >
> > Flowvisor updates the portlist specifically when a change to the
> flowspace is made. Could you send me the flowvisor syslog output of the
> period during which you add the new port?
> >
> >
> >
> > Cheers.
> >
> > --
> > Ali
> >
> > On Oct 21, 2012, at 11:28 PM, Ali Al-Shabibi <
> ali.al-shab...@stanford.edu> wrote:
> >
> > > Hi again,
> > >
> > > How do you fetch the port list? Also, which controller are you using?
> Are you positive you a fetching a fresh port list?
> > >
> > > Flowvisor updates the portlist specifically when a change to the
> flowspace is made. Could you send me the flowvisor syslog output of the
> period during which you add the new port?
> > >
> > >
> > > Cheers.
> > >
> > > --
> > > Ali
> > >
> > > On Oct 21, 2012, at 11:00 PM, japson jacob <japson....@gmail.com>
> wrote:
> > >
> > >> Hello Ali
> > >> Attaching the current config
> > >>
> > >> Thanks
> > >> Japson Jacob
> > >>
> > >>
> > >> On Sun, Oct 21, 2012 at 4:54 PM, Ali Al-Shabibi <
> ali.al-shab...@stanford.edu> wrote:
> > >> Japson,
> > >>
> > >> The config you sent me was the default config. Could you run:
> > >>
> > >> $ fvctl dumpconfig config_new.json
> > >>
> > >> while flowvisor is running. That'll fetch the current config from the
> internal database.
> > >>
> > >>
> > >> Cheers.
> > >>
> > >> --
> > >> Ali
> > >>
> > >> On Oct 21, 2012, at 9:10 PM, japson jacob <japson....@gmail.com>
> wrote:
> > >>
> > >>> Hi Ali,
> > >>> Yes , I am Still using default CONFIG.JSON fine.
> > >>> Attaching a copyof it.
> > >>>
> > >>> It is a pure Openflow 1.0 OF_SWITCH. and Port 2 is part of Openflow
> Switch.
> > >>> From my Observation I dont see the Port getting added dynamically
> > >>> i.e after adding port_2 in flow visor if i unconfigure the of_switch
> and configure it back then ports are added to the controller.
> > >>>
> > >>> Thanks
> > >>> Japson Jacob
> > >>>
> > >>>
> > >>> On Sun, Oct 21, 2012 at 12:31 PM, Ali Al-Shabibi <
> ali.al-shab...@stanford.edu> wrote:
> > >>> Hi Japson,
> > >>>
> > >>> It look like from your initial email that you still have the default
> flowvisor config loaded. Am I correct? It would help if you could send me
> flowvisor's config.
> > >>>
> > >>> Also what kind of of_switch are you using and is port 2 actually
> part of the openflow ports and/or is that port actually up?
> > >>>
> > >>>
> > >>> Cheers.
> > >>>
> > >>> --
> > >>> Ali
> > >>>
> > >>> On Oct 20, 2012, at 6:28 AM, japson jacob <japson....@gmail.com>
> wrote:
> > >>>
> > >>>> Being a newbie to flowvisor another basic Question
> > >>>>
> > >>>> The topology remains the same as below
> > >>>>
> > >>>> of_switch <-----> flowvisor <------>controller
> > >>>>
> > >>>> Now i create a flowspace for of_switch for eg
> > >>>> fvctl addFlowSpace 00:0a:6c:9c:ed:70:6a:c6 10 in_port=1 Slice:sdn=4
> > >>>>
> > >>>> When i try to add another port to the slice using
> > >>>> fvctl addFlowSpace 00:0a:6c:9c:ed:70:6a:c6 10 in_port=2 Slice:sdn=4
> > >>>>
> > >>>> When i try to do a port_list for this switch from controller I
> don't see the new port added
> > >>>> Can anyone please help me out here
> > >>>>
> > >>>> Thanks
> > >>>> Japson Jacob
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Sat, Oct 20, 2012 at 12:13 AM, Sumanth MS <
> sumanth.sathyanaray...@gmail.com> wrote:
> > >>>> Hey Japson,
> > >>>>
> > >>>> We are working on improving the logging messages and these types of
> messages would be fixed in the upcoming releases!
> > >>>> If the Flowvisor is working properly and rest everything is fine,
> there should be no problem with these log messages.
> > >>>> Please bear it for some time!
> > >>>>
> > >>>> Thanks & Best Regards
> > >>>> Sumanth
> > >>>>
> > >>>> On Fri, Oct 19, 2012 at 7:11 PM, japson jacob <japson....@gmail.com>
> wrote:
> > >>>> Hello
> > >>>> I have successfully hooked up my openflow switch to flowvisor and
> then onto Controller.
> > >>>> But in flowvisor log message i keep getting following message
> > >>>>
> > >>>>
> > >>>> Oct 19 22:05:45 sdn-vm4 -1>Oct 19 22:05:45 flowvisor: INFO trying
> to reconnect to localhost:54322
> > >>>> Oct 19 22:05:45 sdn-vm4 -1>Oct 19 22:05:45 flowvisor: INFO trying
> to reconnect to localhost:54322
> > >>>> Oct 19 22:05:45 sdn-vm4 -1>Oct 19 22:05:45 flowvisor: INFO trying
> to reconnect to localhost:54322
> > >>>>
> > >>>>
> > >>>> So far Flowvisor seems to be stable. Any help on how to remove this
> message ? Anything wrong about it
> > >>>>
> > >>>> Thanks
> > >>>> Japson Jacob
> > >>>>
> > >>>> _______________________________________________
> > >>>> openflow-discuss mailing list
> > >>>> 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
> > >>>
> > >>>
> > >>> <config.JSON.txt>
> > >>
> > >>
> > >> <config_new.json.txt>
> > >
> >
> >
>
>
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
