Nokia SR OS#
vr-sros nodes launched with containerlab comes up pre-provisioned with SSH, SNMP, NETCONF and gNMI services enabled.
Managing vr-sros nodes#
Containers with SR OS inside will take ~3min to fully boot.
You can monitor the progress with
watch docker ps waiting till the status will change to
Nokia SR OS node launched with containerlab can be managed via the following interfaces:
to connect to a
bash shell of a running vr-sros container:
docker exec -it <container-name/id> bash
to connect to the SR OS CLI
NETCONF server is running over port 830
ssh root@<container-name> -p 830 -s netconf
using the best in class gnmic gNMI client as an example:
gnmic -a <container-name/node-mgmt-address> --insecure \ -u admin -p admin \ capabilities
serial port (console) is exposed over TCP port 5000:
# from container host telnet <node-name> 5000
telnet localhost 5000if telnet is not available on your container host.
Default user credentials:
vr-sros container uses the following mapping for its interfaces:
eth0- management interface connected to the containerlab management network
eth1- first data interface, mapped to first data port of SR OS line card
eth2+- second and subsequent data interface
Interfaces can be defined in a non-sequential way, for example:
links: # sr1 port 3 is connected to sr2 port 5 - endpoints: ["sr1:eth3", "sr2:eth5"]
When containerlab launches vr-sros node, it will assign IPv4/6 address to the
eth0 interface. These addresses can be used to reach management plane of the router.
eth1+ needs to be configured with IP addressing manually using CLI/management protocols.
Features and options#
Virtual SR OS simulator can be run in multiple HW variants as explained in the vSIM installation guide.
vr-sros container images come with pre-packaged SR OS variants as defined in the upstream repo as well as support custom variant definition. The pre-packaged variants are identified by the variant name and come up with cards and mda already configured. Custom variants, on the other hand, give users the full flexibility in emulated hardware configuration, but cards and MDAs would need to be configured manually.
To make vr-sros to boot in one of the packaged variants use its name like that:
topology: nodes: sros: kind: vr-sros image: vrnetlab/vr-sros:20.10.R1 type: sr-1s # if type omitted, the default sr-1 variant will be used license: license-sros20.txt
Custom variant can be defined as simple as that:
# for distributed chassis CPM and IOM are indicated with markers cp: and lc: # notice the delimiter string `___` that MUST be present between CPM and IOM portions # max_nics value is provided in `lc` part. # mem is provided in GB # quote the string value type: "cp: cpu=2 ram=4 chassis=ixr-e slot=A card=cpm-ixr-e ___ lc: cpu=2 ram=4 max_nics=34 chassis=ixr-e slot=1 card=imm24-sfp++8-sfp28+2-qsfp28 mda/1=m24-sfp++8-sfp28+2-qsfp28"
# an integrated custom type definition # note, no `cp:` marker is needed type: "cpu=2 ram=4 slot=A chassis=ixr-r6 card=cpiom-ixr-r6 mda/1=m6-10g-sfp++4-25g-sfp28"
vr-sros nodes come up with a basic "blank" configuration where only the card/mda are provisioned, as well as the management interfaces such as Netconf, SNMP, gNMI.
User defined config#
It is possible to make SR OS nodes to boot up with a user-defined startup config instead of a built-in one. With a
startup-config property of the node/kind a user sets the path to the config file that will be mounted to a container and used as a startup config:
name: sros_lab topology: nodes: sros: kind: vr-sros startup-config: myconfig.txt
With such topology file containerlab is instructed to take a file
myconfig.txt from the current working directory, copy it to the lab directory for that specific node under the
/tftpboot/config.txt name and mount that dir to the container. This will result in this config to act as a startup config for the node.
save command will perform a configuration save for
vr-sros nodes via Netconf. The configuration will be saved under
config.txt file and can be found at the node's directory inside the lab parent directory:
# assuming the lab name is "cert01" # and node name is "sr" cat clab-cert01/sr/tftpboot/config.txt
Path to a valid license must be provided for all vr-sros nodes with a
If your SR OS license file is issued for a specific UUID, you can define it with custom type definition:
# note, typically only the cp needs the UUID defined. type: "cp: uuid=00001234-5678-9abc-def1-000012345678 cpu=4 ram=6 slot=A chassis=SR-12 card=cpm5 ___ lc: cpu=4 ram=6 max_nics=36 slot=1 chassis=SR-12 card=iom3-xp-c mda/1=m10-1gb+1-10gb"
When a user starts a lab, containerlab creates a node directory for storing configuration artifacts. For
vr-sros kind containerlab creates
tftpboot directory where the license file will be copied.
The following labs feature vr-sros node: