-
Notifications
You must be signed in to change notification settings - Fork 243
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add vJunos-Router kind based on existing vJunos-switch implementation (…
…#2063) * Add vJunos-Router kind based on existing vJunos-switch implementation * Add/fix vJunos kind short names * Fix vJunos shortnames in schema, merge separate vJunosRouter into vJunosSwitch kind, minor doc fixes * Add note about vJunosEvolved being freely downloadable to docs * Re-add accidentally removed trailing whitespace/newlines to docs * Remove deprecated vr-prefixed short names * Change vJunos short names to long names in autocompletion generator
- Loading branch information
Showing
10 changed files
with
95 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,79 @@ | ||
--- | ||
search: | ||
boost: 4 | ||
--- | ||
# Juniper vJunos-router | ||
|
||
[Juniper vJunos-router](https://www.juniper.net/documentation/product/us/en/vjunos-router/) is a virtualized MX router, a single-VM version of the vMX that requires no feature licenses and is meant for lab/testing use. It is identified with `juniper_vjunosrouter` kind in the [topology file](../topo-def-file.md). It is built using [vrnetlab](../vrnetlab.md) project and essentially is a Qemu VM packaged in a docker container format. | ||
|
||
Juniper vJunos-router nodes launched with containerlab come up pre-provisioned with SSH, SNMP, NETCONF and gNMI services enabled. | ||
|
||
## How to obtain the image | ||
|
||
The qcow2 image can be freely downloaded from the [Juniper support portal](https://support.juniper.net/support/downloads/?p=vjunos-router) without a Juniper account and built with [vrnetlab](../vrnetlab.md). | ||
|
||
## Managing Juniper vJunos-router nodes | ||
|
||
!!!note | ||
Containers with vJunos-router inside can take up to ~5-10min to fully boot. | ||
You can monitor the progress with `docker logs -f <container-name>`. | ||
|
||
Juniper vJunos-router node launched with containerlab can be managed via the following interfaces: | ||
|
||
=== "bash" | ||
to connect to a `bash` shell of a running Juniper vJunos-router container: | ||
```bash | ||
docker exec -it <container-name/id> bash | ||
``` | ||
=== "CLI via SSH" | ||
to connect to the vJunos-router CLI | ||
```bash | ||
ssh admin@<container-name/id> | ||
``` | ||
=== "NETCONF" | ||
NETCONF server is running over port 830 | ||
```bash | ||
ssh admin@<container-name> -p 830 -s netconf | ||
``` | ||
|
||
!!!info | ||
Default user credentials: `admin:admin@123` | ||
|
||
## Interfaces mapping | ||
|
||
Juniper vJunos-router container can have up to 11 interfaces and uses the following mapping rules: | ||
|
||
* `eth0` - management interface connected to the containerlab management network | ||
* `eth1` - first data interface, mapped to a first data port of vJunos-router VM | ||
* `eth2+` - second and subsequent data interface | ||
|
||
When containerlab launches Juniper vJunos-router node, it will assign IPv4/6 address to the `eth0` interface. These addresses can be used to reach the management plane of the router. | ||
|
||
Data interfaces `eth1+` need to be configured with IP addressing manually using CLI/management protocols or via a startup-config text file. | ||
|
||
## Features and options | ||
|
||
### Node configuration | ||
|
||
Juniper vJunos-router nodes come up with a basic configuration supplied by a mountable configuration disk to the main VM image. Users, management interfaces, and protocols such as SSH and NETCONF are configured. | ||
|
||
#### Startup configuration | ||
|
||
It is possible to make vJunos-router nodes boot up with a user-defined startup-config instead of a built-in one. With a [`startup-config`](../nodes.md#startup-config) property of the node/kind user sets the path to the config file that will be mounted to a container and used as a startup-config: | ||
|
||
```yaml | ||
topology: | ||
nodes: | ||
node: | ||
kind: juniper_vjunosrouter | ||
startup-config: myconfig.txt | ||
``` | ||
|
||
With this knob containerlab is instructed to take a file `myconfig.txt` from the directory that hosts the topology file, and copy it to the lab directory for that specific node under the `/config/startup-config.cfg` name. Then the directory that hosts the startup-config dir is mounted to the container. This will result in this config being applied at startup by the node. | ||
|
||
Configuration is applied after the node is started, thus it can contain partial configuration snippets that you desire to add on top of the default config that a node boots up with. | ||
|
||
## Known issues and limitations | ||
|
||
* vJunos-router requires Linux kernel 4.17+ | ||
* To check the boot log, use `docker logs -f <node-name>`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters