You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the ONOS version used in the NGSDN-Tutorial is version 2.2.2, and I was doing some testing in the most recent version (2.7.0), I encountered a series of issues during the configuration of In-Band Network Telemetry on a custom topology.
In this case, when using the provided version on the Docker Compose file, the org.onosproject.inbandtelemetry application shows the following web interface:
Here you can configure the collector IP and port. However, in the most recent version, which I've been developing some code during my past years, this is the following web interface:
Collector IP and port cannot be configured anymore on the web interface. Moreover, when setting up a custom topology with some docker containers, where network devices execute the stratum_bmv2 P4 software switch using the pipeline org.onosproject.pipelines.int, the following errors show up in the ONOS log when activating the org.onosproject.inbandtelemetry application:
Inspecting the history of commits related to the inbandtelemetry application on the ONOS repository, it seems that the application has been modified and now should be configured using netcfg, but I cannot understand how to do it properly.
Can anyone explain how the inbandtelemetry application should be configured to support INT telemetry headers on the packets?
Thank you for your time,
Pablo
The text was updated successfully, but these errors were encountered:
As the ONOS version used in the NGSDN-Tutorial is version 2.2.2, and I was doing some testing in the most recent version (2.7.0), I encountered a series of issues during the configuration of In-Band Network Telemetry on a custom topology.
In this case, when using the provided version on the Docker Compose file, the org.onosproject.inbandtelemetry application shows the following web interface:
Here you can configure the collector IP and port. However, in the most recent version, which I've been developing some code during my past years, this is the following web interface:
Collector IP and port cannot be configured anymore on the web interface. Moreover, when setting up a custom topology with some docker containers, where network devices execute the stratum_bmv2 P4 software switch using the pipeline org.onosproject.pipelines.int, the following errors show up in the ONOS log when activating the org.onosproject.inbandtelemetry application:
Inspecting the history of commits related to the inbandtelemetry application on the ONOS repository, it seems that the application has been modified and now should be configured using netcfg, but I cannot understand how to do it properly.
Can anyone explain how the inbandtelemetry application should be configured to support INT telemetry headers on the packets?
Thank you for your time,
Pablo
The text was updated successfully, but these errors were encountered: