Hi everyone,
While browsing the ODL SFC code I see that VppNodeListener requires vpp nodes
to be netconf capable in order to be manageable and stored in the internal
hashmaps.
public void onDataTreeChanged(@Nonnull
Collection<DataTreeModification<Node>> changes) {
printTraceStart(LOG);
for (DataTreeModification<Node> modification : changes) {
DataObjectModification<Node> rootNode = modification.getRootNode();
switch (rootNode.getModificationType()) {
case WRITE:
case SUBTREE_MODIFIED:
if (rootNode.getDataAfter() != null) {
Node node = rootNode.getDataAfter();
if (nodeManager.isCapableNetconfDevice(node)) {
nodeManager.updateNode(node);
}
break;
However, after registering VPP nodes I can only see this in network topology:
{
"network-topology": {
"topology": [
{
"topology-id": "topology-netconf",
"node": [
{
"node-id": "controller",
"netconf-node-topology:host": "192.168.255.100",
"netconf-node-topology:port": 2831,
"netconf-node-topology:username": "admin",
"netconf-node-topology:password": "admin",
"netconf-node-topology:tcp-only": false,
"netconf-node-topology:keepalive-delay": 0
},
As you can see there are not netconf capabilities shown, thus when using
vpp-renderer in sfc it cannot find any node and it fails.
Do you know what is required in order to have vpp nodes registered with netconf
capabalities? (honeycomb seems to be running and working).
Thank you very much,
Best Regards,
MA.
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
