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
Copy file name to clipboardExpand all lines: docs/manual/kinds/ipinfusion-ocnos.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ search:
4
4
---
5
5
# IPInfusion OcNOS
6
6
7
-
IPInfusion OcNOS virtualized router is identified with `ipinfusion_ocnos` kind in the [topology file](../topo-def-file.md). It is built using either [boxen](https://github.com/carlmontanari/boxen) project or [hellt/vrnetlab](https://github.com/hellt/vrnetlab/tree/master/ocnos) and essentially is a Qemu VM packaged in a docker container format.
7
+
IPInfusion OcNOS virtualized router is identified with `ipinfusion_ocnos` kind in the [topology file](../topo-def-file.md). It is built using [hellt/vrnetlab](https://github.com/hellt/vrnetlab/tree/master/ocnos) and essentially is a Qemu VM packaged in a docker container format.
8
8
9
9
ipinfusion_ocnos nodes launched with containerlab come up pre-provisioned with SSH, and NETCONF services enabled.
10
10
@@ -36,7 +36,7 @@ IPInfusion OcNOS node launched with containerlab can be managed via the followin
0 commit comments