Hi Jaime,

I tried with Oxygen but installation of plugin did not happen correctly .  I 
have copied the error below in the link

opendaylight-user@root>feature:install odl-sfc-vpp-renderer odl-sfc-scf-vpp

http://paste.openstack.org/show/721100/

curl -X PUT \
  http://localhost:8181/restconf/config/service-node:service-nodes \
  -H 'authorization: Basic YWRtaW46YWRtaW4=' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: 2ce00447-48ad-7962-30f1-c00e662d0c8a' \
  -d '{
    *******************************

{
    "errors": {
        "error": [
            {
                "error-type": "protocol",
                "error-tag": "unknown-element",
                "error-message": "The module named 'service-node' does not 
exist."
            }
        ]
    }
}



Thanks
Om Prakash

-----Original Message-----
From: Jaime Caamaño Ruiz [mailto:[email protected]] 
Sent: Wednesday, May 16, 2018 5:21 AM
To: PRAKASH, OM <[email protected]>; [email protected]
Cc: SINGH, ABHIJEET K <[email protected]>; FREEMAN, BRIAN D <[email protected]>
Subject: Re: [sfc-dev] Sfc104 demo issue

Hi,

1)

Yes, the port is hardcoded to 7777. Could you please rise a bug for this?

2)

Multiple model revisions shouldn't be a problem. Indeed there is two of them, 
and SFC uses the old one. Are you installing the same set of features as the 
sfc-104 demo? I notice you are using Carbon, which is rather old now. I tested 
this on Oxygen, could you use that?

BR
Jaime.



-----Original Message-----
From: " PRAKASH, OM " <[email protected]>
To: [email protected] <[email protected]>, jc 
[email protected]
Cc: ABHIJEET K SINGH <[email protected]>, BRIAN D FREEMAN <[email protected]>
Subject: Re: [sfc-dev] Sfc104 demo issue
Date: Mon, 14 May 2018 21:11:39 +0000

Hi,
 
I was trying to set up SFC demo with VPP and found out couple of serious issue 
. Do we need to raise bug for this against ODL-SFC ?
 
1)       The mount configuration through SFC contains netconf port
7777. But  Correct port should be 2831. Because of this  Classifier and SFF 
were not getting mounted.
 
{
    "topology": [
        {
            "topology-id": "topology-netconf",
            "node": [
                {
                    "node-id": "CLASSIFIER2",
                    "netconf-node-topology:password": "admin",
                    "netconf-node-topology:username": "admin",
                    "netconf-node-topology:port": 7777,
                    "netconf-node-topology:tcp-only": true,
                    "netconf-node-topology:host": "192.168.60.60"
                },
                {
                    "node-id": "CLASSIFIER1",
                    "netconf-node-topology:password": "admin",
                    "netconf-node-topology:username": "admin",
                    "netconf-node-topology:port": 7777,
                    "netconf-node-topology:tcp-only": true,
                    "netconf-node-topology:host": "192.168.60.10"
                },
                {
                    "node-id": "SFF1",
                    "netconf-node-topology:password": "admin",
                    "netconf-node-topology:username": "admin",
                    "netconf-node-topology:port": 7777,
                    "netconf-node-topology:tcp-only": true,
                    "netconf-node-topology:host": "192.168.60.20"
                },
                {
                    "node-id": "SFF2",
                    "netconf-node-topology:password": "admin",
                    "netconf-node-topology:username": "admin",
                    "netconf-node-topology:port": 7777,
                    "netconf-node-topology:tcp-only": true,
                    "netconf-node-topology:host": "192.168.60.50"
                },
                {
                    "node-id": "controller-config",
                    "netconf-node-topology:password": "admin",
                    "netconf-node-topology:username": "admin",
                    "netconf-node-topology:port": 1830,
                    "netconf-node-topology:tcp-only": false,
                    "netconf-node-topology:reconnect-on-changed-
schema": true,
                    "netconf-node-topology:host": "127.0.0.1"
                }
            ]
        }
    ]
}
 
2)       The second issue is that the v3po yang file is not correct.
Each yang file contains multiple revision number and because of this there is 
issue comng up
 
 
ubuntu@host:~/distribution-karaf-0.6.4-Carbon/cache/schema$ ls -ltr
v3po*
-rw-rw-r-- 1 ubuntu ubuntu 19279 May 14 16:35 [email protected]
-rw-rw-r-- 1 ubuntu ubuntu  1630 May 14 16:35 [email protected] ang
-rw-rw-r-- 1 ubuntu ubuntu 19255 May 14 16:48 [email protected]
 
 
  2018-05-14 16:59:14,398 | ERROR | on-dispatcher-99 |
DataTreeChangeListenerActor      | 197 -
org.opendaylight.controller.sal-clustering-commons - 1.5.4.Carbon |
member-1-shard-default-operational: Error notifying listener org.openda 
ylight.controller.md.sal.binding.impl.BindingDOMDataTreeChangeListenerA
dapter@799fba49
java.lang.NullPointerException: Cannot find 
(urn:opendaylight:params:xml:ns:yang:v3po?revision=2016-12-14)vpp node in 
schema context. Instance identifier has to start from root
        at
com.google.common.base.Preconditions.checkNotNull(Preconditions.java:25
0)[65:com.google.guava:18.0.0]
   
               from      [email protected]
                              module v3po {
  yang-version 1;
  namespace "urn:opendaylight:params:xml:ns:yang:v3po";
  prefix "v3po";
 
  revision "2016-12-14" {
    description
      "This revision adds the following new features:
       - ingress/egress ACLs support
       - moved ACL definitions to vpp-acl module
       - updated l2 container constraint (permit IP address on BVI
interface)
       - added PID of vpp process to vpp-state
       - added support for Loopback interfaces
       - added support for port mirroring";
  }
 
  revision "2015-01-05" {
    description "Initial revision of v3po model";
  }
 
 
From [email protected]
 
revision "2017-06-07" {
    description "Eliminated config leafrefs in operational tree";
  }
 
  revision "2017-03-15" {
    description
      "Revision changes:
       - acl and ietf-acl moved to vpp-interface-acl
       - vpp-state and rpc moved to vpp-management
       - bridge domains moved to standalone container";
  }
 
  revision "2016-12-14" {
    description
      "This revision adds the following new features:
       - ingress/egress ACLs support
       - moved ACL definitions to vpp-acl module
       - updated l2 container constraint (permit IP address on BVI
interface)
       - added PID of vpp process to vpp-state
       - added support for Loopback interfaces
       - added support for port mirroring";
  }
 
  revision "2015-01-05" {
    description "Initial revision of v3po model";
  }
 
 
Thanks
Om Prakash

 
_______________________________________________
sfc-dev mailing list
[email protected]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opendaylight.org_mailman_listinfo_sfc-2Ddev&d=DwICaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=nGABpS95qb7WLoWMNmdaQg&m=r-oEnY2Ahzx8cNLEkBydboV1bSwIJfkxXRtSsRmD6kI&s=D8ZKWS1zK_OhyLCB7JArKhnJCUAFRIQ4kPhIiw2JMP4&e=
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to