Hello It never hurts to try but it may not work. Some of this config ends up both in ODL & neutron databases and it may not be updated correctly. So you may need to stop neutron & ODL, reset both of it's databases and restart them.
You may reference ODL docs [1] on how to do that. Refer to "Ensuring OpenStack network state is clean", "Ensure Neutron is stopped", "Reset Neutron’s database", "Restart neutron-server"...Make sure you start ODL with 'clean' argument to clean it up too. [1] http://docs.opendaylight.org/projects/netvirt/en/stable-oxygen/openstack-guide/openstack-with-netvirt.html#installing-opendaylight-on-an-existing-openstack BR Jaime. -----Original Message----- From: om prakash <[email protected]> To: [email protected] Cc: ABHIJEET K SINGH <[email protected]>, BRIAN D FREEMAN <[email protected]> , OM PRAKASH <[email protected]>, [email protected] <netv [email protected]>, [email protected] <sfc-de [email protected]>, Sam Hague <[email protected]> Subject: Re: [sfc-dev] Opendaylight support for networking-sfc Date: Thu, 31 May 2018 11:07:26 -0400 Hi Jaime, is it possible to set up these parameter and then restart the ODL ? will it work ? Or these parameter needs to be set before 1st start of ODL ? On Thu, May 31, 2018 at 6:39 AM, Jaime Caamaño Ruiz <[email protected]> wrote: > Getting there. > > Let's review the configuration, some of which is specific to getting > SFC integration. > > In opendaylight/datastore/initial/config/genius-itm-config.xml make > sure that > > <def-tz-enabled>true</def-tz-enabled> > <def-tz-tunnel-type>vxlan</def-tz-tunnel-type> > <gpe-extension-enabled>true</gpe-extension-enabled> > > Also, the following parameters need to be set in OVS > > ovs-vsctl set O . other_config:local_ip=<node-ip> > ovs-vsctl set O . external_ids:of-tunnel=true > > These need to be set before running ODL. I am unsure how that would > be > done appropriately when deploying with devstack but my guess is that > these kind of things are being set from devstack/entry_points. > > Also, after this, make sure you have basic VM networking before > attempting SFC. > > BR > Jaime. > > -----Original Message----- > From: " PRAKASH, OM " <[email protected]> > To: Sam Hague <[email protected]>, [email protected] > Cc: ABHIJEET K SINGH <[email protected]>, BRIAN D FREEMAN <[email protected] > m> > , om prakash <[email protected]>, [email protected] > <n > [email protected]>, [email protected] > <sfc > [email protected]> > Subject: RE: [sfc-dev] Opendaylight support for networking- > Date: Wed, 30 May 2018 23:47:29 +0000 > > Hi Jaime/Sam, > > Finally I made a very good progress. Now SFC request is going to ODL > from Openstack . I see port-pair-create, port-pair-group-create, > flow- > classifier-create and port-chain-create request went to ODL. > > But there is exception coming in ODL . Any configuration I need to > add > to ODL for this ? can you please let me know ? > > Log I have put here . http://paste.openstack.org/show/722386/ > > > 2018-05-30T18:09:43,137 | ERROR | opendaylight-cluster-data- > notification-dispatcher-651 | InterfaceManagerRpcService | 255 > - > org.opendaylight.genius.interfacemanager-impl - 0.4.0 | RPC > getEndpointIpForDpn() failed; input = GetEndpointIpForDpnInput > [_dpid=4658453923909, augmentation=[]] > java.lang.NullPointerException: null > at > org.opendaylight.genius.interfacemanager.rpcservice.InterfaceManagerS > er > viceImpl.getEndpointIpForDpn(InterfaceManagerServiceImpl.java:141) > ~[255:org.opendaylight.genius.interfacemanager-impl:0.4.0] > at > org.opendaylight.genius.interfacemanager.rpcservice.InterfaceManagerR > pc > Service.lambda$getEndpointIpForDpn$0(InterfaceManagerRpcService.java: > 57 > ) ~[255:org.opendaylight.genius.interfacemanager-impl:0.4.0] > at > org.opendaylight.genius.infra.FutureRpcResults$FutureRpcResultBuilder > .b > uild(FutureRpcResults.java:210) > [261:org.opendaylight.genius.mdsalutil- > api:0.4.0] > at > org.opendaylight.genius.interfacemanager.rpcservice.InterfaceManagerR > pc > Service.getEndpointIpForDpn(InterfaceManagerRpcService.java:57) > [255:org.opendaylight.genius.interfacemanager-impl:0.4.0] > at > org.opendaylight.yangtools.yang.binding.util.RpcMethodInvokerWithInpu > t. > invokeOn(RpcMethodInvokerWithInput.java:32) > [328:org.opendaylight.mdsal.yang-binding:0.12.0] > at > org.opendaylight.yangtools.yang.binding.util.AbstractMappedRpcInvoker > .i > nvokeRpc(AbstractMappedRpcInvoker.java:53) > [328:org.opendaylight.mdsal.yang-binding:0.12.0] > at > org.opendaylight.controller.md.sal.binding.impl.BindingDOMRpcImplemen > ta > tionAdapter.invoke(BindingDOMRpcImplementationAdapter.java:83) > [218:org.opendaylight.controller.sal-binding-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.binding.impl.BindingDOMRpcImplemen > ta > tionAdapter.invokeRpc(BindingDOMRpcImplementationAdapter.java:70) > [218:org.opendaylight.controller.sal-binding-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.dom.broker.impl.GlobalDOMRpcRoutin > gT > ableEntry.invokeRpc(GlobalDOMRpcRoutingTableEntry.java:41) > [221:org.opendaylight.controller.sal-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRoutingTable > .i > nvokeRpc(DOMRpcRoutingTable.java:178) > [221:org.opendaylight.controller.sal-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRouter.invok > eR > pc(DOMRpcRouter.java:102) [221:org.opendaylight.controller.sal- > broker- > impl:1.7.0] > at > Proxybc94a1f1_a049_4699_ad3d_356171ed883e.invokeRpc(Unknown > Source) [?:?] > at > Proxyaca2580b_6c17_4724_9b69_fdc56325b228.invokeRpc(Unknown > Source) [?:?] > at > org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter.inv > ok > e0(RpcServiceAdapter.java:65) [218:org.opendaylight.controller.sal- > binding-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter.acc > es > s$000(RpcServiceAdapter.java:43) > [218:org.opendaylight.controller.sal- > binding-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter$Rpc > In > vocationStrategy.invoke(RpcServiceAdapter.java:156) > [218:org.opendaylight.controller.sal-binding-broker-impl:1.7.0] > at > org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter.inv > ok > e(RpcServiceAdapter.java:96) [218:org.opendaylight.controller.sal- > binding-broker-impl:1.7.0] > at com.sun.proxy.$Proxy128.getEndpointIpForDpn(Unknown > Source) > [254:org.opendaylight.genius.interfacemanager-api:0.4.0] > at > org.opendaylight.sfc.genius.util.SfcGeniusRpcClient.getDpnIpFromGeniu > sR > PC(SfcGeniusRpcClient.java:242) > [414:org.opendaylight.sfc.genius:0.7.0] > at > org.opendaylight.sfc.ofrenderer.processors.SfcRspProcessorLogicalSff. > co > nfigureSffTransportEgressFlow(SfcRspProcessorLogicalSff.java:272) > [416:org.opendaylight.sfc.openflow-renderer:0.7.0] > at > org.opendaylight.sfc.ofrenderer.processors.SfcOfRspProcessor.configur > eT > ransportEgressFlows(SfcOfRspProcessor.java:475) > [416:org.opendaylight.sfc.openflow-renderer:0.7.0] > : > > > Thanks > Om Prakash > > > -----Original Message----- > From: Jaime Caamaño Ruiz [mailto:[email protected]] > Sent: Wednesday, May 30, 2018 7:15 AM > To: PRAKASH, OM <[email protected]>; Sam Hague <[email protected]> > Cc: SINGH, ABHIJEET K <[email protected]>; FREEMAN, BRIAN D <bf1936@att. > co > m>; om prakash <[email protected]>; [email protected] > g; > [email protected] > Subject: Re: [sfc-dev] Opendaylight support for networking-sfc > > I suggest that you check the status of nova compute service > > openstack compute service list > > If compute service is up and healthy, check the nova compute logs for > any possible error there. > > sudo journalctl -u devstack@n-cpu > > BR > Jaime. > > _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
