Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

devendra's profile - activity

2017-03-02 04:07:22 -0700 asked a question linux bridge not updating

We have integrated Openstack Kilo with ODL Lithium SR4. After integration all networking works good (VM has IP, connectivity etc) though we can’t see any linux bridges getting created when an instance is initiated. Isn’t the linux bridges supposed to implement the openstack security groups? How does ODL handle this?

2017-02-02 21:28:33 -0700 received badge  Popular Question (source)
2016-12-02 17:01:29 -0700 received badge  Notable Question (source)
2016-11-30 01:56:49 -0700 asked a question OVS port number changes on instance restart

Hi All,

I have a Kilo+Lithium SR4 setup.

One observation i have seen is whenever an instance (VM) reboots its port number on OVS changes. It seems like that whenever an instance goes down (while rebooting or shutdown) ODL removes the corresponding port from OVS. The next time when the instance comes-up OVS treats it as a new instance and allocates the next available port number.

Please note this behavior is not seen in pure Openstack (without ODL). The port number remains same even after instance reboot.

Can anyone highlight if this is side effect of any feature or a bug in ODL?

I am planning to put some OVS flows based on port number and they don't work after an instance reboot.

Response will be appreciated

2016-11-28 20:42:06 -0700 received badge  Popular Question (source)
2016-11-23 01:35:11 -0700 commented answer No flows in br-int

While integrating Openstack with ODL we do mention local ip ovs-vsctl set Open_vSwitch '_uuid' other_config={'local_ip'='<ip on="" which="" ovs="" runs="">'} Also we did face the same issue with Kilo + Berylium SR2

2016-11-20 21:53:23 -0700 commented question No flows in br-int

Found a workaround for this for the timebeing Restart ODL and u can see the flows back on OVS switches

2016-11-18 02:18:17 -0700 received badge  Editor (source)
2016-11-18 02:16:54 -0700 asked a question No flows in br-int

Hi, I have a 3 node Openstack Kilo + Opendaylight Lithium SR4 setup.

This is working all good for a day or 2 but after that connectivity is lost between instances and also to external world. On restarting the OpenvSwitch daemon i am not able to view any flows in br-int on network/compute node. Though OVS logs states some flow_mods happening but nothing is seen on dump-flows command

OVS Logs *2016-11-18T09:29:15.285Z|00113|connmgr|INFO|br-int: added primary controller "tcp:10.1.24.5:6653" 2016-11-18T09:29:15.285Z|00114|rconn|INFO|br-int<->tcp:10.1.24.5:6653: connecting... 2016-11-18T09:29:15.307Z|00115|rconn|INFO|br-int<->tcp:10.1.24.5:6653: connected 2016-11-18T09:29:15.319Z|00116|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.5.0 2016-11-18T09:29:24.802Z|00117|memory|INFO|118596 kB peak resident set size after 10.0 seconds 2016-11-18T09:29:24.802Z|00118|memory|INFO|handlers:8 ofconns:1 ports:41 revalidators:4 rules:18 udpif keys:8 2016-11-18T09:29:25.406Z|00119|connmgr|INFO|br-int<->tcp:10.1.24.5:6653: 1361 flowmods in the 9 s starting 10 s ago (1361 modifications) 2016-11-18T09:30:25.406Z|00120|connmgr|INFO|br-int<->tcp:10.1.24.5:6653: 1149 flowmods in the 9 s starting 59 s ago (1149 modifications)


The karaf logs has the error Tunnel end-point configuration missing. Please configure it in OpenVSwitch Table.

Karaf logs below 2016-11-18 04:29:14,622 | INFO | pool-43-thread-1 | SouthboundHandler | 285 - org.opendaylight.ovsdb.openstack.net-virt - 1.1.4.Lithium-SR4 | ovsdbUpdate: PORT - DELETE - <<node{getnodeid=uri [_value="ovsdb://uuid/158f8753-4893-4a3d-a75e-49ae6e97c042/bridge/br-int]," getterminationpoint="[TerminationPoint{getTpId=Uri" [_value="qr-58997f38-cd]," augmentations="{interface" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.ovsdbterminationpointaugmentation="OvsdbTerminationPointAugmentation{getInterfaceExternalIds=[InterfaceExternalIds{getExternalIdKey=attached-mac," getexternalidvalue="fa:16:3e:f9:7c:51," augmentations="{}}," interfaceexternalids{getexternalidkey="iface-status," getexternalidvalue="active," augmentations="{}}," interfaceexternalids{getexternalidkey="iface-id," getexternalidvalue="58997f38-cda5-4257-a80f-4c5fb01af515," augmentations="{}}]," getinterfacetype="class" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.interfacetypeinternal,="" getinterfaceuuid="Uuid" [_value="7ff4c13e-e7ab-473b-ae0e-8acc43cff100]," getname="qr-58997f38-cd," getofport="36," getportuuid="Uuid" [_value="404b5272-ff88-4b4a-bf1f-fd7879835ee9]}}}," terminationpoint{gettpid="Uri" [_value="br-int]," augmentations="{interface" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.ovsdbterminationpointaugmentation="OvsdbTerminationPointAugmentation{getInterfaceType=class" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.interfacetypeinternal,="" getinterfaceuuid="Uuid" [_value="fcffbb49-6d27-4783-901f-9aa5d84ef64e]," getname="br-int," getofport="65534," getportuuid="Uuid" [_value="d962a8e8-6c75-49ee-bb0d-773eaf1f1849]}}}," terminationpoint{gettpid="Uri" [_value="qr-7569c1a9-e9]," augmentations="{interface" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.ovsdbterminationpointaugmentation="OvsdbTerminationPointAugmentation{getInterfaceExternalIds=[InterfaceExternalIds{getExternalIdKey=attached-mac," getexternalidvalue="fa:16:3e:81:e7:1d," augmentations="{}}," interfaceexternalids{getexternalidkey="iface-status," getexternalidvalue="active," augmentations="{}}," interfaceexternalids{getexternalidkey="iface-id," getexternalidvalue="7569c1a9-e994-47c5-807d-a7ac95d814b6," augmentations="{}}]," getinterfacetype="class" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.interfacetypeinternal,="" getinterfaceuuid="Uuid" [_value="e2da5d83-d022-4488-822b-8996ce7a9c94]," getname="qr-7569c1a9-e9," getofport="38," getportuuid="Uuid" [_value="2da6f2dc-0e31-4599-bf92-445a796a1469]}}}," terminationpoint{gettpid="Uri" [_value="qr-6deec372-02]," augmentations="{interface" org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.ovsdb.rev150105.ovsdbterminationpointaugmentation="OvsdbTerminationPointAugmentation{getInterfaceExternalIds=[InterfaceExternalIds{getExternalIdKey=attached-mac," getexternalidvalue="fa:16:3e:0a ...

(more)
2016-06-06 03:50:02 -0700 asked a question Error while creating the rendered Service Path

Hi,

I have a Openstack (Kilo) and ODL (Lithium SR3) setup. I am trying to setup a basic SFC via OVS. The desired flow is if traffic flows from Node A to Node B it should go via Node C. Node C is a SF and an interface on OVS is acting like SFF.

While creating RSP i am getting this error:-

    ERROR | lt-dispatcher-44 | SfcL2RspProcessor                | 315 - org.opendaylight.sfc.ofl2 - 0.1.3.Lithium-SR3 | RuntimeException in processRenderedServicePath:
    java.lang.RuntimeException: processSffDpls srcSff is null [SFF1-6jun-dev]
            at org.opendaylight.sfc.l2renderer.SfcL2RspProcessor.processSffDpls(SfcL2RspProcessor.java:813)[315:org.opendaylight.sfc.ofl2:0.1.3.Lithium-SR3]
            at org.opendaylight.sfc.l2renderer.SfcL2RspProcessor.processRenderedServicePath(SfcL2RspProcessor.java:121)[315:org.opendaylight.sfc.ofl2:0.1.3.Lithium-SR3]
            at org.opendaylight.sfc.l2renderer.SfcL2RspDataListener.onDataChanged(SfcL2RspDataListener.java:61)[315:org.opendaylight.sfc.ofl2:0.1.3.Lithium-SR3]
            at org.opendaylight.controller.md.sal.binding.impl.AbstractForwardedDataBroker$TranslatingDataChangeInvoker.onDataChanged(AbstractForwardedDataBroker.java:143)[161:org.opendaylight.controller.sal-binding-broker-impl:1.2.3.Lithium-SR3]
            at org.opendaylight.controller.cluster.datastore.DataChangeListener.dataChanged(DataChangeListener.java:66)[183:org.opendaylight.controller.sal-distributed-datastore:1.2.3.Lithium-SR3]
            at org.opendaylight.controller.cluster.datastore.DataChangeListener.handleReceive(DataChangeListener.java:39)[183:org.opendaylight.controller.sal-distributed-datastore:1.2.3.Lithium-SR3]
            at org.opendaylight.controller.cluster.common.actor.AbstractUntypedActor.onReceive(AbstractUntypedActor.java:34)[175:org.opendaylight.controller.sal-clustering-commons:1.2.3.Lithium-SR3]
            at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:167)[168:com.typesafe.akka.actor:2.3.10]
            at akka.actor.Actor$class.aroundReceive(Actor.scala:467)[168:com.typesafe.akka.actor:2.3.10]
            at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:97)[168:com.typesafe.akka.actor:2.3.10]
            at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)[168:com.typesafe.akka.actor:2.3.10]
            at akka.actor.ActorCell.invoke(ActorCell.scala:487)[168:com.typesafe.akka.actor:2.3.10]
            at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:254)[168:com.typesafe.akka.actor:2.3.10]
            at akka.dispatch.Mailbox.run(Mailbox.scala:221)[168:com.typesafe.akka.actor:2.3.10]
            at akka.dispatch.Mailbox.exec(Mailbox.scala:231)[168:com.typesafe.akka.actor:2.3.10]
            at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)[165:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
            at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)[165:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
            at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)[165:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
            at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)[165:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]
            at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)[165:org.scala-lang.scala-library:2.10.4.v20140209-180020-VFINAL-b66a39653b]

Response is appreciated.

JSON

    SF
{
  "service-functions": {
    "service-function": [
      {
        "name": "SF1-6Jun-dev",
        "ip-mgmt-address": "10.0.21.4",
        "sf-data-plane-locator": [
          {
            "name": "sf1-dpl",
            "port": 6653,
            "ip": "192.168.60.5", -- IP of SF
            "transport": "service-locator:gre",
            "service-function-forwarder": "SFF1-6jun-dev"
          }
        ],
        "nsh-aware": true,
        "type": "service-function-type:dpi"
      }
    ]
  }
}

SFF
{
  "service-function-forwarders": {
    "service-function-forwarder": [
      {
        "name": "SFF1-6Jun-dev",
        "service-function-forwarder-ovs:ovs-bridge": {
          "bridge-name": "br-int" -- using default bridge
        },
        "service-function-dictionary": [
          {
            "name": "SF1-6Jun-dev",
            "sff-sf-data-plane-locator": {
              "port": 6653 ...
(more)
2016-06-06 02:19:38 -0700 asked a question warning while creating SFF

hi,

I have Openstack (Kilo) and ODL (Lithium) setup. While creating a SFF i am getting following WARNING, any pointers for possible cause will be helpful.

Thanks in advance!!!

SFF Json

    {
  "service-function-forwarders": {
    "service-function-forwarder": [
      {
        "name": "SFF1-6Jun-dev",
        "service-function-forwarder-ovs:ovs-bridge": {
          "bridge-name": "br-int"
        },
        "service-function-dictionary": [
          {
            "name": "SF1-6Jun-dev",
            "sff-sf-data-plane-locator": {
              "port": 6653,
              "ip": "192.168.60.5",
              "transport": "service-locator:gre",
              "service-function-forwarder-ovs:ovs-bridge": {}
            },
            "type": "service-function-type:dpi"
          }
        ],
        "sff-data-plane-locator": [
          {
            "name": "sff1-dpl",
            "data-plane-locator": {
              "port": 6653,
              "ip": "10.0.21.4",
              "transport": "service-locator:gre"
            },
            "service-function-forwarder-ovs:ovs-bridge": {}
          }
        ],
        "service-node": ""
      }
    ]
  }
}
2016-06-02 23:23:35 -0700 received badge  Organizer (source)
2016-06-02 23:14:37 -0700 asked a question Cannot determine DataPlaneLocator transport type, dataPlaneLocator.getTransport() is null

Hi All,

I have Openstack (Kilo) and ODL (Lithium) successfully integrated.

I am trying to create a SFF with one SF linked to it. While creating SFF i am getting the error 'Cannot determine DataPlaneLocator transport type, dataPlaneLocator.getTransport() is null' though i have mentioned the transport type as 'GRE'. When doing a get call via restconf i can see the transport type.

Please suggest if this warning can be neglected?

Error

2016-06-03 01:54:12,259 | WARN  | -dispatcher-7316 | SfcSffToOvsMappingAPI            | 314 - org.opendaylight.sfc.ovs - 0.1.3.Lithium-SR3 | Cannot determine DataPlaneLocator transport type, dataPlaneLocator.getTransport() is null.
2016-06-03 01:54:12,259 | WARN  | -dispatcher-7316 | SfcSffToOvsMappingAPI            | 314 - org.opendaylight.sfc.ovs - 0.1.3.Lithium-SR3 | Falling back to InterfaceTypeInternal

Get JSON Response

{
  "service-function-forwarders": {
    "service-function-forwarder": [
      {
        "name": "SFF1",
        "service-function-forwarder-ovs:ovs-bridge": {
          "bridge-name": "br-int"
        },
        "service-function-dictionary": [
          {
            "name": "SF1",
            "sff-sf-data-plane-locator": {
              "ip": <SF IP>,
              "transport": "service-locator:gre",
              "service-function-forwarder-ovs:ovs-bridge": {}
            },
            "type": "service-function-type:firewall"
          }
        ],
        "ip-mgmt-address": "<SFF Mgmt IP>",
        "sff-data-plane-locator": [
          {
            "name": "sff1-dpl",
            "data-plane-locator": {
              "ip": "<SFF IP>",
              "transport": "service-locator:gre"
            },
            "service-function-forwarder-ovs:ovs-bridge": {}
          }
        ],
        "service-node": ""
      }
    ]
  }
}