oh, maybe you are not using a branch/release that has the feature
yet. what version of ODL are you using?
JamO
On 5/1/18 2:14 PM, Konstantin Agouros wrote:
Hi,
I am afraid not. I tried with this result:
opendaylight-user@root>feature:install odl-infrautils-diagstatus
Error executing command: No matching features for
odl-infrautils-diagstatus/0.0.0
Regard,
Konstantin
Am 01.05.2018 um 22:52 schrieb Jamo Luhrsen <[email protected]>:
Konstantin,
did you install the feature odl-infrautils-diagstatus?
after that it should look like this:
opendaylight-user@root>showSvcStatus
Timestamp: Tue May 01 16:27:35 UTC 2018
Node IP Address: 127.0.0.1
System is operational: true
System ready state: ACTIVE
OPENFLOW : OPERATIONAL
IFM : OPERATIONAL
ITM : OPERATIONAL
DATASTORE : OPERATIONAL
hopendaylight-user@root>
Thanks,
JamO
On 4/30/18 1:35 AM, Konstantin Agouros wrote:
Hi,
well I changed the setting for sync back to false and then it was working.
Can You clarify on the showSvsStatus command? Typing show and then ‚tab‘ gives
me
opendaylight-user@root>show
show show-bgp show-cache
show-session-stats show-state show-time-counters
showStats showTransportType showcache
Regards,
Konstantin
Am 28.04.2018 um 20:24 schrieb Dayavanti Gopal Kamath
<[email protected]>:
Konstantin,
it will help if you can check and inform also on whether the flows are proper
after your restart, all bundles etc are up and operational, ( I think the karaf
cli command to check this is ' showSvcStatus ' ), and whether dataplane works
as expected. For the exceptions, the team would need detailed config as well as
karaf logs to analyze,
Thanks,
daya
-----Original Message-----
From: Konstantin Agouros [mailto:[email protected]]
Sent: Thursday, April 26, 2018 7:27 PM
To: Gobinath . <[email protected]>
Cc: Dayavanti Gopal Kamath <[email protected]>; odl netvirt dev
<[email protected]>; [email protected]
Subject: Re: [netvirt-dev] Proper way to shutdown and restart everything?
So I set the to true and then started odl again.
How I am seeing regular Exceptions:
2018-04-26 15:54:46,011 | ERROR | pool-40-thread-1 | DOMNotificationRouterEvent
| 209 - org.opendaylight.controller.sal-broker-impl - 1.6.2 | Delivery of
notification
org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@653dfe2e
caused an error in listener
org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter@781f345e
java.lang.NullPointerException
at
org.opendaylight.genius.arputil.internal.ArpUtilImpl.getInterfaceName(ArpUtilImpl.java:438)
at
org.opendaylight.genius.arputil.internal.ArpUtilImpl.onPacketReceived(ArpUtilImpl.java:389)
at
org.opendaylight.yangtools.yang.binding.util.NotificationListenerInvoker.invokeNotification(NotificationListenerInvoker.java:117)
at
org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter.onNotification(BindingDOMNotificationListenerAdapter.java:44)
at
org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouterEvent.deliverNotification(DOMNotificationRouterEvent.java:51)
at
org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter.lambda$static$0(DOMNotificationRouter.java:65)
at
com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129)[73:com.lmax.disruptor:3.3.6]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_161]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_161]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_161]
How do I proceed?
Regards,
Konstantin
Am 25.04.2018 um 11:28 schrieb Gobinath . <[email protected]>:
Hi Konstantin,
To enable the feature "bundle based resync" , uncomment and change the value to
"true" in the below file.
Filename: etc/org.opendaylight.openflowplugin.cfg
#
# To Enable bundle based reconciliation change the configuration value to true.
# By default it will be false which means bundle based reconciliation
will be disabled # and normal reconciliation will be enabled.
# NOTE: This option will be effective only if disable_reconciliation=false.
# bundle-based-reconciliation-enabled=false
Note: Bundle reconciliation will be supported from OVS2.6 and above.
Please check
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/docs-rtd-verify-fluorine/273/html/submodules/openflowplugin/docs/specs/bundle-reconciliation.html
in case of any queries.
Thanks and Regards,
Gobinath
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Konstantin Agouros
Sent: Wednesday, April 25, 2018 2:36 PM
To: Dayavanti Gopal Kamath <[email protected]>
Cc: odl netvirt dev <[email protected]>;
[email protected]
Subject: Re: [netvirt-dev] Proper way to shutdown and restart everything?
Hi,
can You tell me how to enable this feature? This sound like what I was looking
for.
Regards,
Konstantin
Am 25.04.2018 um 10:19 schrieb Dayavanti Gopal Kamath
<[email protected]>:
Hi konstantin,
There is a non-default re-sync functionality available in the
openflow plugin. If you use this, you should be in a position to restart the
controller, or a compute in any order (at least from a netvirt and related
features perspective) Tunnel deletes are not well handled today, I,e if you
remove a switch, and delete a tep in the controller, the system goes out of
sync, we are adding an ovsdb re-sync feature in fluorine mainly for this
usecase, but if you are not changing config, it should not block you currently.
I would suggest you enable the resync, and report any issues found to the group.
Thanks,
daya
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Konstantin Agouros
Sent: Wednesday, April 25, 2018 2:05 AM
To: odl netvirt dev <[email protected]>
Subject: [netvirt-dev] Proper way to shutdown and restart everything?
Hi,
I am under the impression that the whole system is not resilient to a proper
shutdown/restart of the whole ensemble. So is the proper way to first shutdown
the compute nodes and then ODL or the other way around?
Also: Should the tunnels-ports on the compute nodes be left as be or deleted
before starting again? At the moment I get an inconsistent state, where VMs on
some compute nodes have network and others not.
Thanks,
Konstantin
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet:
[email protected] Altersheimerstr. 1, 81545 Muenchen, Germany. Tel
+49
89 69370185
--------------------------------------------------------------------
--
------ "There is no 'dead' in team!" - Sameen Shaw
_______________________________________________
netvirt-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet:
[email protected] Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49
89 69370185
----------------------------------------------------------------------
------ "There is no 'dead' in team!" - Sameen Shaw
_______________________________________________
netvirt-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: [email protected]
Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"There is no 'dead' in team!" - Sameen Shaw
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: [email protected]
Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"There is no 'dead' in team!" - Sameen Shaw
_______________________________________________
netvirt-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
--
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: [email protected]
Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"There is no 'dead' in team!" - Sameen Shaw
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
