Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
So why did the ping fail? Well we didn't load the reactive forwarding application. Indeed, if you list the loaded applications you will see the following:
Code Block |
---|
onos> feature:list
110 | Active | 80 | 1.0.0.SNAPSHOT | onos-rest
116 | Active | 80 | 1.0.0.SNAPSHOT | onos-of-api
117 | Active | 80 | 1.0.0.SNAPSHOT | onos-of-ctl
118 | Active | 80 | 1.0.0.SNAPSHOT | onos-lldp-provider
119 | Active | 80 | 1.0.0.SNAPSHOT | onos-host-provider
120 | Active | 80 | 1.0.0.SNAPSHOT | onos-of-provider-device
121 | Active | 80 | 1.0.0.SNAPSHOT | onos-of-provider-packet
122 | Active | 80 | 1.0.0.SNAPSHOT | onos-of-provider-flow
136 | Active | 80 | 1.0.0.SNAPSHOT | onos-cli
137 | Active | 80 | 8.1.15.v20140411 | Jetty :: Websocket
138 | Active | 80 | 1.0.0.SNAPSHOT | onos-gui
151 | Active | 80 | 1.0.0.SNAPSHOT | onos-core-net
152 | Active | 80 | 1.0.0.SNAPSHOT | onos-core-trivial |
...