vr-xrv nodes launched with containerlab come up pre-provisioned with SSH, SNMP, NETCONF and gNMI (if available) services enabled.
XRv image is discontinued by Cisco and supreceded by XRv 9000 image. It was added to containerlab because the image is lightweight, compared to XRv9k. If recent features are needed, use vr-xrv9k kind.
Managing vr-xrv nodes#
Containers with XRv inside will take ~5min to fully boot.
You can monitor the progress with
docker logs -f <container-name>.
Cisco XRv node launched with containerlab can be managed via the following interfaces:
to connect to a
bash shell of a running vr-xrv container:
docker exec -it <container-name/id> bash
to connect to the XRv CLI
ssh [email protected]<container-name/id>
NETCONF server is running over port 830
ssh [email protected]<container-name> -p 830 -s netconf
Default user credentials:
vr-xrv container can have up to 90 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 XRv line card
eth2+- second and subsequent data interface
When containerlab launches vr-xrv 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#
vr-xrv nodes come up with a basic configuration where only the control plane and line cards are provisioned, as well as the
clab user and management interfaces such as NETCONF, SNMP, gNMI.
The following labs feature vr-xrv node:
Known issues and limitations#
- LACP and BPDU packets are not propagated to/from vrnetlab based routers launched with containerlab.