Skip to content

IPInfusion OcNOS#

IPInfusion OcNOS virtualized router is identified with ipinfusion_ocnos kind in the topology file. It is built using srl-labs/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.

Note

OcNOS 7.0.0-262 (OcNOS-SP-PLUS-x86-7.0.0-262-GA.qcow2) builds and boots with make docker-image without modification. Older images such as 6.0.2 needed a GRUB change for the serial console, as shown here.

Getting the image#

The OcNOS VM image for KVM is a free download from IP Infusion (registration required): OcNOS-SP VM for KVM. The VM includes a 365-day license and is licensed for non-production evaluation only (OcNOS EULA). Decompress the image with xz -d, then copy the .qcow2 file into the ipinfusion/ocnos directory of srl-labs/vrnetlab and run make docker-image.

Managing ipinfusion_ocnos nodes#

Note

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:

to connect to a bash shell of a running ipinfusion_ocnos container: 

docker exec -it <container-name/id> bash

to connect to the OcNOS CLI 

ssh ocnos@<container-name/id>

NETCONF server is running over port 830 

ssh ocnos@<container-name> -p 830 -s netconf

Info

Default user credentials: admin:admin@123

Interfaces mapping#

ipinfusion_ocnos container can have up to 63 interfaces (eth management + 62 additional data interfaces defined in the topology file) 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.

Data interfaces eth1+ need to be configured with IP addressing manually using CLI/management protocols.