ipinfusion_ocnos nodes launched with containerlab come up pre-provisioned with SSH, and NETCONF services enabled.
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:
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
NETCONF server is running over port 830
ssh ocnos@<container-name> -p 830 -s netconf
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.