IPInfusion OcNOS virtualized router is identified with
ipinfusion_ocnos kind in the topology file. It is built using either boxen project or hellt/vrnetlab and essentially is a Qemu VM packaged in a docker container format.
ipinfusion_ocnos nodes launched with containerlab come up pre-provisioned with SSH, and NETCONF services enabled.
OcNOS VM disk images need to be altered to support telnet serial access and ethX interfaces name style. This can be done by modifying the grub config file, as shown here.
Managing ipinfusion_ocnos nodes#
Containers with OcNOS inside will take ~3min to fully boot.
You can monitor the progress with
docker logs -f <container-name> and
docker exec -it <container-name> tail -f /console.log.
IPInfusion OcNOS node launched with containerlab can be managed via the following interfaces:
Default user credentials:
ipinfusion_ocnos container can have up to 144 interfaces and uses the following mapping rules:
eth0- management interface connected to the containerlab management network
eth1- first data interface, mapped to first data port of OcNOS line card
eth2+- second and subsequent data interface
When containerlab launches ipinfusion_ocnos node, it will assign IPv4 address to the
eth0 interface. This address can be used to reach management plane of the router.
eth1+ need to be configured with IP addressing manually using CLI/management protocols.