hc2vpp@lists.fd.io | [honeycomb-dev] Netconf issue with Honeycomb

Home Messages Hashtags Subgroups

Date Date 1 - 6 of 6

[honeycomb-dev] Netconf issue with Honeycomb

Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...>

#371

Hi,

It looks like you are using SFC version which is not compatible with Honeycomb.

HC exposes v3po@2017-06-07 since 17.07 or 17.10.

I think SFC needs update…

Regards,

Marek

Show quoted text

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of op317q@...
Sent: 15 maja 2018 07:16
To: honeycomb-dev@...
Subject: [honeycomb-dev] Netconf issue with Honeycomb

Hi,
I find below netconf issue with Honeycomd. I am not sure if this is SFC issue or honeycomb. The V3po yang file has 2 version in the cache.. SFC is using the old version.

next keepalive in 60 SECONDS
2018-05-14 23:17:52,983 | TRACE | oupCloseable-3-1 | WriteCandidateTx                 | 315 - org.opendaylight.netconf.sal-netconf-connector - 1.6.2 | Lock candidate successful
2018-05-14 23:17:52,986 | ERROR | n-dispatcher-225 | DataTreeChangeListenerActor      | 262 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-default-config: Error notifying listener org.opendaylight.sfc.scfvpprenderer.listeners.SfcScfVppDataListener@34847f1b
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:876)[56:com.google.guava:22.0.0]
        at org.opendaylight.yangtools.yang.data.impl.schema.ImmutableNodes.fromInstanceId(ImmutableNodes.java:134)[113:org.opendaylight.yangtools.yang-data-impl:1.2.2]
        at org.opendaylight.netconf.sal.connect.netconf.util.NetconfMessageTransformUtil.createEditConfigAnyxml(NetconfMessageTransformUtil.java:316)[315:org.opendaylight.netconf.sal-netconf-connector:1.6.2]
        at org.opendaylight.netconf.sal.connect.netconf.util.NetconfRpcStructureTransformer.createEditConfigStructure(NetconfRpcStructureTransformer.java:41)[315:org.opendaylight.netconf.sal-netconf-connector:1.6.2]
        at org.opendaylight.netconf.sal.connect.netconf.util.NetconfBaseOps.createEditConfigStrcture(NetconfBaseOps.java:291)[315:org.opendaylight.netconf.sal-netconf-connector:1.6.2]
        at org.opendaylight.netconf.sal.connect.netconf.sal.tx.AbstractWriteTx.put(AbstractWriteTx.java:106)[315:org.opendaylight.netconf.sal-netconf-connector:1.6.2]
        at org.opendaylight.controller.md.sal.binding.impl.AbstractWriteTransaction.put(AbstractWriteTransaction.java:46)[256:org.opendaylight.controller.sal-binding-broker-impl:1.6.2]
        at org.opendaylight.controller.md.sal.binding.impl.BindingDOMWriteTransactionAdapter.put(BindingDOMWriteTransactionAdapter.java:40)[256:org.opendaylight.controller.sal-binding-broker-impl:1.6.2]
        at org.opendaylight.sfc.util.vpp.SfcVppUtils.addDummyBridgeDomain(SfcVppUtils.java:317)[325:org.opendaylight.sfc.vpp-utils:0.6.2]
        at org.opendaylight.sfc.scfvpprenderer.processors.VppClassifierProcessor.configureVxlanGpeClassifier(VppClassifierProcessor.java:439)[323:org.opendaylight.sfc.scf-vpp:0.6.2]
        at org.opendaylight.sfc.scfvpprenderer.processors.VppClassifierProcessor.addScf(VppClassifierProcessor.java:604)[323:org.opendaylight.sfc.scf-vpp:0.6.2]
        at org.opendaylight.sfc.scfvpprenderer.listeners.SfcScfVppDataListener.add(SfcScfVppDataListener.java:64)[323:org.opendaylight.sfc.scf-vpp:0.6.2]
        at org.opendaylight.sfc.scfvpprenderer.listeners.SfcScfVppDataListener.add(SfcScfVppDataListener.java:30)[323:org.opendaylight.sfc.scf-vpp:0.6.2]
        at org.opendaylight.sfc.provider.listeners.AbstractDataTreeChangeListener.onDataTreeChanged(AbstractDataTreeChangeListener.java:43)[322:org.opendaylight.sfc.provider:0.6.2]
        at org.opendaylight.controller.md.sal.binding.impl.BindingDOMDataTreeChangeListenerAdapter.onDataTreeChanged(BindingDOMDataTreeChangeListenerAdapter.java:41)[256:org.opendaylight.controller.sal-binding-broker-impl:1.6.2]
        at org.opendaylight.controller.cluster.datastore.DataTreeChangeListenerActor.dataChanged(DataTreeChangeListenerActor.java:67)[269:org.opendaylight.controller.sal-distributed-datastore:1.6.2]
        at org.opendaylight.controller.cluster.datastore.DataTreeChangeListenerActor.handleReceive(DataTreeChangeListenerActor.java:41)[269:org.opendaylight.controller.sal-distributed-datastore:1.6.2]
        at org.opendaylight.controller.cluster.common.actor.AbstractUntypedActor.onReceive(AbstractUntypedActor.java:38)[262:org.opendaylight.controller.sal-clustering-commons:1.6.2]
        at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:165)[143:com.typesafe.akka.actor:2.4.18]

PRAKASH, OM <op317q@...>

#372

One more issue I see with SFC . it tries to connect to VPP using 7777 port. It should be 2831 correct ?

{

"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"

}

]

}

]

}

Thanks

Om Prakash

Show quoted text

From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) [mailto:mgradzki@...]
Sent: Tuesday, May 15, 2018 2:00 AM
To: PRAKASH, OM <op317q@...>; honeycomb-dev@...; hc2vpp@...
Subject: RE: [honeycomb-dev] Netconf issue with Honeycomb

Hi,

It looks like you are using SFC version which is not compatible with Honeycomb.

HC exposes v3po@2017-06-07 since 17.07 or 17.10.

I think SFC needs update…

Regards,

Marek

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of op317q@...
Sent: 15 maja 2018 07:16
To: honeycomb-dev@...
Subject: [honeycomb-dev] Netconf issue with Honeycomb

Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...>

#374

Config looks fine for me.

Notice “netconf-node-topology:tcp-only": true

By default HC provides Netconf over TCP (port 7777)

and SSH (port 2831).

You can configure them using netconf.json.

Regards,

Marek

Show quoted text

From: PRAKASH, OM [mailto:op317q@...]
Sent: 15 maja 2018 15:36
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; honeycomb-dev@...; hc2vpp@...
Subject: RE: [honeycomb-dev] Netconf issue with Honeycomb

One more issue I see with SFC . it tries to connect to VPP using 7777 port. It should be 2831 correct ?

{

"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"

}

]

}

]

}

Thanks

Om Prakash

Hi,

It looks like you are using SFC version which is not compatible with Honeycomb.

HC exposes v3po@2017-06-07 since 17.07 or 17.10.

I think SFC needs update…

Regards,

Marek

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of op317q@...
Sent: 15 maja 2018 07:16
To: honeycomb-dev@...
Subject: [honeycomb-dev] Netconf issue with Honeycomb

Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...>

#375

One more info.

Here is how default netconf.json looks like:

https://git.fd.io/honeycomb/tree/infra/northbound/netconf/src/main/resources/honeycomb-minimal-resources/config/netconf.json

{

"netconf-netty-threads": 2,

"netconf-tcp-enabled": "true",

"netconf-tcp-binding-address": "127.0.0.1",

"netconf-tcp-binding-port": 7777,

"netconf-ssh-enabled": "true",

"netconf-ssh-binding-address": "0.0.0.0",

"netconf-ssh-binding-port": 2831,

"netconf-notification-stream-name": "honeycomb"

}

Notice TCP is by default bound to 127.0.0.1, so it won’t be available from outside.

You can change it to 0.0.0.0 to bind to all available IPs or select specific one.

Regards,

Marek

Show quoted text

From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
Sent: 15 maja 2018 17:28
To: 'PRAKASH, OM' <op317q@...>; honeycomb-dev@...; hc2vpp@...
Subject: RE: [honeycomb-dev] Netconf issue with Honeycomb

Config looks fine for me.

Notice “netconf-node-topology:tcp-only": true

By default HC provides Netconf over TCP (port 7777)

and SSH (port 2831).

You can configure them using netconf.json.

Regards,

Marek

One more issue I see with SFC . it tries to connect to VPP using 7777 port. It should be 2831 correct ?

{

"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"

}

]

}

]

}

Thanks

Om Prakash

Hi,

It looks like you are using SFC version which is not compatible with Honeycomb.

HC exposes v3po@2017-06-07 since 17.07 or 17.10.

I think SFC needs update…

Regards,

Marek

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of op317q@...
Sent: 15 maja 2018 07:16
To: honeycomb-dev@...
Subject: [honeycomb-dev] Netconf issue with Honeycomb

Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...>

#376

Hi,

there was infra maintenance yesterday (see csit-dev or discuss mailing lists).

Are you still experiencing these issues?

Regards,

Marek

Show quoted text

From: PRAKASH, OM [mailto:op317q@...]
Sent: 15 maja 2018 21:31
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; honeycomb-dev@...; hc2vpp@...
Subject: RE: [honeycomb-dev] Netconf issue with Honeycomb

Err:8 https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main ./ Packages

404 Not Found

Ign:9 https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main ./ Translation-en_US

Ign:10 https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main ./ Translation-en

Reading package lists... Done

E: Failed to fetch https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main/./Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

root@sff1:~#

this is I am getting from the URL

404 - The generator for generated path /Packages with key PackagesContentGenerator not found in M2Repository(id=fd.io.stable.1804.ubuntu.xenial.main)

The generator for generated path /Packages with key PackagesContentGenerator not found in M2Repository(id=fd.io.stable.1804.ubuntu.xenial.main)

Thanks

Om Prakash

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco)
Sent: Tuesday, May 15, 2018 11:31 AM
To: PRAKASH, OM <op317q@...>; honeycomb-dev@...; hc2vpp@...
Subject: Re: [honeycomb-dev] Netconf issue with Honeycomb

One more info.

Here is how default netconf.json looks like:

https://git.fd.io/honeycomb/tree/infra/northbound/netconf/src/main/resources/honeycomb-minimal-resources/config/netconf.json

{

"netconf-netty-threads": 2,

"netconf-tcp-enabled": "true",

"netconf-tcp-binding-address": "127.0.0.1",

"netconf-tcp-binding-port": 7777,

"netconf-ssh-enabled": "true",

"netconf-ssh-binding-address": "0.0.0.0",

"netconf-ssh-binding-port": 2831,

"netconf-notification-stream-name": "honeycomb"

}

Notice TCP is by default bound to 127.0.0.1, so it won’t be available from outside.

You can change it to 0.0.0.0 to bind to all available IPs or select specific one.

Regards,

Marek

Config looks fine for me.

Notice “netconf-node-topology:tcp-only": true

By default HC provides Netconf over TCP (port 7777)

and SSH (port 2831).

You can configure them using netconf.json.

Regards,

Marek

One more issue I see with SFC . it tries to connect to VPP using 7777 port. It should be 2831 correct ?

{

"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"

}

]

}

]

}

Thanks

Om Prakash

Hi,

It looks like you are using SFC version which is not compatible with Honeycomb.

HC exposes v3po@2017-06-07 since 17.07 or 17.10.

I think SFC needs update…

Regards,

Marek

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of op317q@...
Sent: 15 maja 2018 07:16
To: honeycomb-dev@...
Subject: [honeycomb-dev] Netconf issue with Honeycomb

PRAKASH, OM <op317q@...>

#381

Err:8 https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main ./ Packages

404 Not Found

Ign:9 https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main ./ Translation-en_US

Ign:10 https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main ./ Translation-en

Reading package lists... Done

E: Failed to fetch https://nexus.fd.io/content/repositories/fd.io.stable.1804.ubuntu.xenial.main/./Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

root@sff1:~#

this is I am getting from the URL

404 - The generator for generated path /Packages with key PackagesContentGenerator not found in M2Repository(id=fd.io.stable.1804.ubuntu.xenial.main)

The generator for generated path /Packages with key PackagesContentGenerator not found in M2Repository(id=fd.io.stable.1804.ubuntu.xenial.main)

Thanks

Om Prakash

Show quoted text

One more info.

Here is how default netconf.json looks like:

https://git.fd.io/honeycomb/tree/infra/northbound/netconf/src/main/resources/honeycomb-minimal-resources/config/netconf.json

{

"netconf-netty-threads": 2,

"netconf-tcp-enabled": "true",

"netconf-tcp-binding-address": "127.0.0.1",

"netconf-tcp-binding-port": 7777,

"netconf-ssh-enabled": "true",

"netconf-ssh-binding-address": "0.0.0.0",

"netconf-ssh-binding-port": 2831,

"netconf-notification-stream-name": "honeycomb"

}

Notice TCP is by default bound to 127.0.0.1, so it won’t be available from outside.

You can change it to 0.0.0.0 to bind to all available IPs or select specific one.

Regards,

Marek

Config looks fine for me.

Notice “netconf-node-topology:tcp-only": true

By default HC provides Netconf over TCP (port 7777)

and SSH (port 2831).

You can configure them using netconf.json.

Regards,

Marek

One more issue I see with SFC . it tries to connect to VPP using 7777 port. It should be 2831 correct ?

{

"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"

}

]

}

]

}

Thanks

Om Prakash

Hi,

It looks like you are using SFC version which is not compatible with Honeycomb.

HC exposes v3po@2017-06-07 since 17.07 or 17.10.

I think SFC needs update…

Regards,

Marek

From: honeycomb-dev@... [mailto:honeycomb-dev@...] On Behalf Of op317q@...
Sent: 15 maja 2018 07:16
To: honeycomb-dev@...
Subject: [honeycomb-dev] Netconf issue with Honeycomb

1 - 6 of 6

Previous Topic Next Topic

Home Hashtags Subgroups Terms