Deploy and Manage vJunos-router on KVM

# ip link add ge-000 type bridge

# ip link add ge-001 type bridge

In this case, the instance will have ge-0/0/0 and ge-0/0/1 configured.

ip link set ge-000 up

ip link set ge-001 up

# cd /root

# cp vjunos-router-23.2R1.14.qcow2 vjunos-rtr1-live.qcow2

Make a distinct copy for each vJunos-router that you plan to deploy. This ensures that you do not make any permanent changes on the original image. The live image must also be writable by the user deploying vJunos-router—typically the root user.

The following stanza specifies the number of cores provided to vJunos-router. The minimum needed cores are four and are sufficient for lab use cases.

<cpu>
    <arch>x86_64</arch>
    <model>IvyBridge</model>
    <topology cores="4" sockets="1" threads="1"/>
    <model fallback="allow">qemu64</model>
    <feature name="vmx" policy="require"/>
</cpu>

The default number of cores needed is four and is sufficient for most applications. This is the minimum CPU supported for vJunos-router. You can leave the CPU model as IvyBridge. Later generation Intel CPUs will also work with this setting.

<disk device="disk" type="file">
    <driver cache="writeback" name="qemu" type="qcow2"/>
    <source file="/root/vjunos-rtr1-live.qcow2"/>   
    <target dev="vda" bus="virtio"/>
</disk>

You must provide each vJunos VM on the host with its own uniquely named QCOW2 image. This is required for libvirt and QEMU-KVM.

# ./make-config.sh <juniper.conf> <config.qcow2>

The vJunos-router accepts an initial configuration by connecting a second disk to the VM instance that contains the configuration. Use the provided script make-config.sh to create the disk image.

The XML file references this configuration drive as shown below:

<disk device="disk" type="file">
    <driver cache="writeback" name="qemu" type="qcow2"/>
    <source file="/root/config.qcow2"/>
    <target dev="vdb" bus=”virtio”/>
</disk>

The eth0 in the stanza below refers to the host server interface that provides connectivity to the external world and this must match the name of the interface on your host server.

<interface type='direct'> 
    <source dev='eth0' mode='bridge'/>
    <model type='virtio'/>
    <alias name='net0'/>
    <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>

This example allows you to connect to the VCP “fxp0” that is the management port from outside the host server on which vJunos-router resides.

You need to have a routable IP address configured for fxp0, either through a DHCP server or using standard CLI configuration.

The eth0 in the stanza below refers to the host server interface which provides connectivity to the external world and should match the name of this interface on your host server.

If you are not using Dynamic Host Configuration Protocol (DHCP), then, after the vJunos-router is up and running, telnet to its console and configure the IP address for “fxp0” using CLI configuration as shown below:

Run this configuration in the CLI on the vJunos-router once the VM is up.

# set interfaces fxp0 unit 0 family inet address 10.92.249.111/23

# set system services ssh root-login allow command.

<interface type="bridge">
    <source bridge="ge-000"/>
    <model type="virtio"/>
    <mtu size='9600'/>
    <alias name="net1"/>
    <address bus="0x00" domain="0x0000" function="0x0" slot="0x08" type="pci"/>
</interface>
<interface type="bridge">
    <source bridge="ge-001"/>
    <model type="virtio"/>
    <mtu size='9600'/>
    <alias name="net2"/>
    <address bus="0x00" domain="0x0000" function="0x0" slot="0x09" type="pci"/>
</interface>

The port names are specified in the following stanza. The convention for the vJunos-router is to use ge-0xy where "xy" specifies the actual port number. In the following example, ge-000 and ge-001 are the port numbers. These port numbers will map to the Junos ge-0/0/0 and ge-0/0/1 interfaces respectively. As mentioned earlier, you need to create a Linux bridge for each port that you specify in the XML file.

In the following example, the unique serial console port number is "8610".

<serial type="tcp">
    <source host="127.0.0.1" mode="bind" service="8610"/>
    <protocol type="telnet"/>
    <target port="0"/>
    <alias name="serial0"/>
</serial>

The following smbios stanza informs the vJunos-router that it is a virtual Junos router. So, do not modify this smbios stanza.

<ns0:commandline>
    <ns0:arg value="-smbios"/>
    <ns0:arg value="type=1,product=VM-VMX, family=lab"/>
</ns0:commandline>

Some examples of valid values are given below. Uncomment the specified lines.

#       user = "qemu"   # A user named "qemu"
#       user = "+0"     # Super user (uid=0)
#       user = "100"    # A user named "100" or a user with uid=100#user = "root" <<< uncomment  this line
# 
#group = "root" <<< uncomment  this line 

# virsh create vjunos-rtr1.xml

The term "rtr1" is used to indicate that this is the first vJunos-router VM that is being installed. Subsequent VMs can be named vjunos-rtr2, and vjunos-rtr3 and so on.

When you execute this step, a shutdown signal sent to the vJunos-router instance allows it to shutdown gracefully.

You can find the port to connect to the serial console of the VCP from the XML file. Also, you can login to the serial console of the VCP through the telnet localhost <portnum> where portnum is specified in the XML configuration file:

If you have not supplied any initial Junos configuration in the steps above, then the vJunos-router will, by default, attempt to DHCP for the initial network setup.

If you don't have a DHCP server that can supply the Junos OS configuration, you can get repeated messages as shown below:

"Auto Image Upgrade"

You can disable these messages as follows:

[edit]]
user@host# set system  root-authentication plain-text-password
New password: <type password here>
Retype new password: <retype password here>
root# delete chassis auto-image-upgrade 
[edit]
root# commit 
commit complete