Juniper NETWORKS 408-745-2000

vJunos Router Deployment

408-745-2000-vJunos-Router-Deployment-PRODUCT....png" alt="Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-PRODUCT..." width="864" height="574" srcset="https://manuals.plus /wp-content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-PRODUCT....png 864w, https://manuals.plus/wp- content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-PRODUCT...-550x365.png 550w, https://manuals.plus/wp- content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-PRODUCT...-768x510.png 768w" sizes="(max-width: 864px) 100vw, 864px" />

Specifications

• Product : vJunos-router Deployment Guide for KVM
• Publisher : Juniper Networks, Inc.
• Published Date : 2024-02-05
• Hardware and Software Compatibility: Linux Host Servers with KVM hypervisor (Ubuntu 18.04, 20.04, 22.04 or Debian 11 Bullseye)

Product Information
The vJunos-router is a virtual router solution that allows users to run Junos software for testing network configurations and protocols. It can be installed on an industry-standard x86 server running a Linux KVM hypervisor.

Product Usage Instructions

Install and Deploy vJunos-router on KVM

1. Prepare the Linux Host Servers to Install vJunos-router:
   • Ensure the host server meets the minimum hardware and software requirements.
   • Install the vJunos-router software components on the server.
2. Deploy and Manage vJunos-router on KVM:
   • Set up the vJunos-router deployment on the host server.
   • Verify the vJunos-router virtual machine (VM) status.
   • Configure vJunos-router settings including active ports, interface naming, and media MTU.
   • Connect to vJunos-router for further configuration.

Troubleshoot vJunos-router on KVM

1. Verify That the VM is Running:
   • Check the status of the vJunos-router VM.
2. Verify CPU Information:
   • Monitor and verify CPU usage information.
3. View Log Files:
   • Check log files for any error or warning messages.
4. Collect Core Dumps:
   • If needed, collect core dumps for troubleshooting purposes.

Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA

• 408-745-2000
• www.juniper.net

Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. vJunos-router Deployment Guide for KVM

Copyright © 2024 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA.

About This Guide

• Use this guide to install the virtual Junos-router (vJunos-router).
• The vJunos-router is a virtual version of the Junos-based MX routing platform. It represents a Juniper router running Junos® operating system (Junos OS) in the kernel-based virtual machine (KVM) environment. The vJunos-router is based on Juniper
• Networks® vMX Virtual Router (vMX) nested architecture.
• This guide also includes basic vJunos-router configuration and management procedures.
• After installing and configuring the vJunos-router as covered in this guide, refer to Junos OS documentation for information about additional software configuration.

RELATED DOCUMENTATION: Junos OS for MX Series Documentation

vJunos-router Overview

SUMMARY
This topic provides an overview, key features supported, benefits, and limitations of the vJunos-router.

Overview

• The vJunos-router is a virtual version of a Juniper router that runs the Junos OS. You can install a vJunos-router as a virtual machine (VM) on an x86 server.
• You can configure and manage the vJunos-router in the same way as you manage a physical router.
• The vJunos-router is a single virtual machine (VM) that you can use only in labs and not in the production environment. The vJunos-router is built using vMX as a reference Juniper router and supports a single Routing Engine and single Flexible PIC Concentrator (FPC).
• The vJunos-router supports a bandwidth of up to 100 Mbps aggregated over all the interfaces.

NOTE: You don’t have to purchase a bandwidth license for using the vJunos-router. Ignore the license check messages.

Instead of using hardware routers, you can use the vJunos-router to start the Junos software for testing the network configurations and protocols.

vJunos-router Installation Overview

• You can install the software components of the vJunos-router on an industry-standard x86 server running a Linux KVM hypervisor (Ubuntu 18.04, 20.04, 22.04 or Debian 11 Bullseye).
• On servers running the KVM hypervisor, you can also run applicable third-party software. You can install multiple vJunos-router instances on a single server.

Key Features Supported
This topic provides you the list and details of the key features that are supported and validated on vJunos-router. For details on configuration of these features, see the feature guides at: User Guides.

The vJunos-router supports the following key features:

• Supports up to 96 router interfaces.
• Feature consistency with the physical MX Series platforms.
• Virtual route reflection
• Virtual broadband network gateway (BNG) capabilities, including:
• L2TP network server/Layer 2 Tunneling Protocol (LNS/L2TP)
• Point-to-Point Protocol over Ethernet (PPPoE)
• Dynamic Host Configuration Protocol (DHCPv4/DHCPv6)
• Pseudowire Headend Termination (PWHT) support
• Static and dynamic (RADIUS) subscriber interface support

Benefits and Uses
The benefits and use cases of the vJunos-router on standard x86 servers are as follows:

• Reduced capital expenditure (CapEx) on lab —The vJunos-router is available for free to build test labs reducing costs associated with physical routers.
• Reduced deployment time —You can use the vJunos-router to build and to test topologies virtually without building expensive physical labs. Virtual labs can be built instantly. As a result, you can reduce costs and delays associated with deployments on the physical hardware.
• Eliminate need and time for lab hardware —The vJunos-router helps you eliminate waiting time for lab hardware to arrive after procurement. vJunos-router is available for free and can be downloaded instantly.
• Education and training— Allows you to build labs for learning and education services for your employees.
• Proof of concept and validation testin g—You can validate various data center switching topologies, pre-build configuration examples, and get automation ready.

Limitations
The vJunos-router has the following limitations:

• Has a single Routing Engine and single FPC architecture.
• In-service software upgrade (ISSU) is not supported.
• Attachment or detachment of interfaces when it is running is not supported.
• SR-IOV for the vJunos-router use cases and throughput is not supported.
• Due to its nested architecture, the vJunos-router cannot be used in any deployments that launch the instances from within a VM.
• Supports a maximum bandwidth of 100 Mbps over all the interfaces.
• You cannot upgrade the Junos OS on a running system. Instead, you must deploy a new instance with the new software.

RELATED DOCUMENTATION: Minimum Hardware and Software Requirements for vJunos-router on KVM | 8

vJunos-router Architecture

The vJunos-router is a single, nested VM solution in which the virtual forwarding plane (VFP) and the Packet Forwarding Engine (PFE) reside in the outer VM. When you start the vJunos-router, the VFP starts a nested VM that runs the Junos Virtual Control Plane (VCP) image. KVM hypervisor is used to deploy VCP. The term “nested” refers to the VCP VM being nested within the VFP VM, as shown in vJunos-router Architecture on page 5 .
The vJunos-router can support up to 100 Mbps of throughput using four cores and 5GB of memory. Any additional cores and memory configured gets allocated to the VCP. VFP does not need additional memory apart from the minimum footprint supported. The 4 cores and 5GB memory is sufficient for lab use cases.

408-745-2000-vJunos-Router-Deployment-FIG-1.png" alt=" Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG- (1)" width="654" height="585" srcset="https://manuals.plus/wp- content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG-1.png 654w, https://manuals.plus/wp-content/uploads/2024/08 /Juniper-NETWORKS-408-745-2000-vJunos- Router-Deployment-FIG-1-550x492.png 550w" sizes="(max-width: 654px) 100vw, 654px" />

The vJunos-router architecture is organized in layers:

• The vJunos-router is at the top layer.
• The KVM hypervisor and the related system software described in the software requirements section are in the middle layer.
• The x86 server is in the physical layer at the bottom.

Understanding this architecture can help you plan your vJunos-router configuration.

After you create the vJunos-router instance, you can use the Junos OS CLI to configure the vJunos-router interfaces in the VCP. The vJunos-router supports Gigabit Ethernet interfaces only.

Hardware and Software Requirements for vJunos-router on KVM

Minimum Hardware and Software Requirements for vJunos-router on KVM | 8

Minimum Hardware and Software Requirements for vJunos-router on KVM
This topic provides you the list of hardware and software requirements to start a vJunos-router instance. Minimum Hardware Requirements for vJunos- router on page 8 lists the hardware requirements for vJunos-router.

Table 1: Minimum Hardware Requirements for vJunos-router

100 Mbps) use cases, any Intel x86 processor with VT-x capability.

Intel Ivy Bridge processors or later.

Example of Ivy Bridge processor: Intel Xeon E5-2667 v2 @ 3.30 GHz 25 MB cache

Number of cores| A minimum of four cores are required. The software allocates three cores to the VFP and one core to the VCP, which is sufficient for most use cases.

Any additional cores will be provided to VCP as three cores is sufficient to support the data plane needs of VFP.

Memory| A minimum of 5GB memory is required. Approximately 3GB memory will be allocated to VFP and 2 GB to the VCP. If more than 6 GB of total memory is provided, then VFP memory is capped at 4GB, and the additional memory is allocated to VCP.
Other requirements| •   Intel VT-x capability.

•   Hyperthreading (recommended)

•   AES-NI

Table 2: Software Requirements for Ubuntu

Operating system

NOTE : Only English localization is supported.

| •   Ubuntu 22.04 LTS

•   Ubuntu 20.04 LTS

•   Ubuntu 18.04 LTS

•   Debian 11 Bullseye

Virtualization| •   QEMU-KVM

The default version for each Ubuntu or Debian version is sufficient. The apt- get install qemu-kvm installs this default version.

Required packages

NOTE : Use the apt-get install pkg name or sudo apt-get install <pkg- name> commands to install a package.

| •   qemu-kvm virt-manager

•   libvirt-daemon-system

•   virtinst libvirt-clients bridge-utils

Supported Deployment Environments| QEMU-KVM using libvirt

Also, the EVE-NG bare metal deployment is supported.

Note: vJunos-router is not supported on EVE-NG or any other deployments that launch vJunos from within a VM due to the constraints of deeply nested virtualization.

vJunos-router Images| The images can be accessed from the lab download area of juniper.net at: Test Drive Juniper

Install and Deploy vJunos-router on KVM

Install vJunos-router on KVM
SUMMARY
Read this topic to understand how to install the vJunos-router in the KVM environment.

Prepare the Linux Host Servers to Install vJunos-router
This section applies to both Ubuntu and Debian host servers.

1. Install the standard package versions for your Ubuntu or Debian host server to ensure that the servers meet the minimum hardware and software requirements.
2. Verify that Intel VT-x technology is enabled. Run the lscpu command on your host server.

The Virtualization field in the output of the lscpu command displays VT-x, if VT-x is enabled. If VT-x is not enabled, then see your server documentation to learn how to enable it in BIOS.

Deploy and Manage vJunos-router on KVM

SUMMARY
Read this topic to understand how to deploy and manage the vJunos-router instance after you install it.

This topic describes:

• How to bring up the vJunos-router on the KVM servers using libvirt.
• How to choose the amount of CPU and memory, set up the required bridges for connectivity, and configure the serial port.
• How to use relevant XML file sections for the configurations and selections listed earlier.

NOTE : Download the sample XML file and the vJunos-router image from the Juniper website.

Set Up the vJunos-router Deployment on the Host Server

This topic describes how to set up the vJunos-router deployment on the host server.

NOTE : This topic highlights only a few sections of the XML file that are used to deploy vJunos-router through libvirt.

The entire XML file vjunos-router.xml is available for download along with the VM image and associated documentation on the vJunos Lab Software Downloads page.

Install the packages mentioned in the Minimum Software Requirements section, if the packages are not already installed. See “Minimum Hardware and Software Requirements for vJunos-router on KVM” on page 8

1. Download the VM image, script, and the xml files from the vJunos Lab Software Downloads page.

2. Create a Linux bridge for each Gigabit Ethernet interface of the vJunos-router that you plan to use. # 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.

3. Bring up each Linux Bridge.

   • ip link set ge-000 up
   • ip link set ge-001 up

4. Make a live disk copy of the provided QCOW2 vJunos image.

   • 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.

5. Specify the number of cores provided to vJunos-router by modifying the following stanza.
   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. 408-745-2000-vJunos-Router-Deployment-FIG-2.png" alt=" Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG- (2)" width="880" height="285" srcset="https://manuals.plus/wp- content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG-2.png 880w, https://manuals.plus/wp-content/uploads/2024/08 /Juniper-NETWORKS-408-745-2000-vJunos- Router-Deployment-FIG-2-550x178.png 550w, https://manuals.plus/wp- content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG-2-768x249.png 768w" sizes="(max-width: 880px) 100vw, 880px" />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.

6. Increase the memory if needed by modifying the below stanza. 408-745-2000-vJunos-Router-Deployment-FIG-3.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (3)" width="858" height="259" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-3.png 858w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-3-550x166.png 550w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-3-768x232.png 768w" sizes="(max-width: 858px) 100vw, 858px" />The following example shows the default memory required by the vJunos-router. The default memory is sufficient for most applications. You can increase the value if needed. It also shows the name of the specific vJunos-router being spawned, which is vjunos-rtr1 in this case.

7. Specify the name and location of your vJunos-router image by modifying the XML file as shown in the following example. 408-745-2000-vJunos-Router-Deployment-FIG-4.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (4)" width="840" height="226" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-4.png 840w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-4-550x148.png 550w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-4-768x207.png 768w" sizes="(max-width: 840px) 100vw, 840px" />You must provide each vJunos VM on the host with its own uniquely named QCOW2 image. This is required for libvirt and QEMU-KVM.

8. Create the configuration disk image.

   • ./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: 408-745-2000-vJunos-Router-Deployment-FIG-5.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (5)" width="765" height="228" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-5.png 765w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-5-550x164.png 550w" sizes="(max-width: 765px) 100vw, 765px" /> NOTE : If you do not prefer initial configuration, then remove the above stanza from the XML file.

9. Set up the management Ethernet port. 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. 408-745-2000-vJunos-Router-Deployment-FIG-6.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (6)" width="811" height="251" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-6.png 811w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-6-550x170.png 550w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-6-768x238.png 768w" sizes="(max-width: 811px) 100vw, 811px" />

   • 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:
     NOTE : The configurations below are just examples or sample configuration snippets. You might also have to set up a static route configuration.

   • 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 routing-options static route 0.0.0.0/0 next-hop 10.92.249.254

10. Enable SSH to the VCP management port.

    set system services ssh root-login allow command.

11. Create a Linux bridge for each port that you specify in the XML file. 408-745-2000-vJunos-Router-Deployment-FIG-7.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (7)" width="885" height="502" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-7.png 885w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-7-550x312.png 550w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-7-768x436.png 768w" sizes="(max-width: 885px) 100vw, 885px" />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.

12. Provide a unique serial console port number for each vJunos-router on your host server. In the followAing example, the unique serial console port number is “8610”. 408-745-2000-vJunos-Router-Deployment-FIG-8.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (8)" width="685" height="257" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-8.png 685w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-8-550x206.png 550w" sizes="(max-width: 685px) 100vw, 685px" />The following smbios stanza informs the vJunos-router that it is a virtual Junos router. So, do not modify this smbios stanza. 408-745-2000-vJunos-Router-Deployment-FIG-9.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (9)" width="754" height="196" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-9.png 754w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-9-550x143.png 550w" sizes="(max-width: 754px) 100vw, 754px" />

13. Check /etc/libvirt/qemu.conf and uncomment the following XML lines if these lines were commented out. Some examples of valid values are given below. Uncomment the specified lines. 408-745-2000-vJunos-Router-Deployment-FIG-10.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (10)" width="895" height="252" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-10.png 895w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-10-550x155.png 550w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-10-768x216.png 768w" sizes="(max-width: 895px) 100vw, 895px" />

14. Restart libvirtd and create the vJunos-router VM again.

    systemctl restart libvirtd

15. Create vjunos-rtr1 VM using the vjunos-rtr1.xml file.

    • 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.
    • As result, the VM is created and the following message is displayed: Domain vjunos-rtr1 created from vjunos-rtr1.xml

16. Shut down the vJunos-router deployed on the Host Server safely (if needed). Use the # virsh shutdown vjunos-rtr1 command to shutdown vJunos-router.

    • When you execute this step, a shutdown signal sent to the vJunos-router instance allows it to shutdown gracefully.
    • The following message is displayed.
    • Domain ‘vjunos-rtr1’ is being shutdown
    • NOTE : Do not use the “virsh destroy” command as this command can corrupt the vJunos-router VM disk.
    • If your VM stops booting after using the “virsh destroy” command, then, create a live QCOW2 disk copy of the provided original QCOW2 image.

Verify the vJunos-router VM
This topic describes how to verify whether the vJunos-router is up and running.

1. Verify if the vJunos-router is up and running. # virsh list 408-745-2000-vJunos-Router-Deployment-FIG-11.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (11)" width="625" height="190" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-11.png 625w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-11-550x167.png 550w" sizes="(max-width: 625px) 100vw, 625px" />

2. Connect to the serial console of the VCP. 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 where portnum is specified in the XML configuration file: NOTE : The telnet port number needs to be unique for each vJunos-router VM residing on the host server. 408-745-2000-vJunos-Router-Deployment-FIG-12.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (12)" width="659" height="222" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-12.png 659w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-12-550x185.png 550w" sizes="(max-width: 659px) 100vw, 659px" />

3. Disable auto image upgrade.

   • 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:

     Retype new password: root# delete chassis auto-image-upgrade

   • [edit]
     root# commit
     commit complete

4. Verify if the ge interfaces specified in your vJunos-router xml file are up and available. Use the show interfaces terse command. For example, if the vJunos-router XML definition file specifies two virtual NICs connected to “ge-000” and “ge-001”, then ge-0/0/0 and ge-0/0/1 interfaces should be in the link “up” state when you verify using the show interface output command as shown below. 408-745-2000-vJunos-Router-Deployment-FIG-13.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (13)" width="741" height="118" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-13.png 741w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-13-550x88.png 550w" sizes="(max-width: 741px) 100vw, 741px" /> 408-745-2000-vJunos-Router-Deployment-FIG-14.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (14)" width="519" height="539" />

5. Verify that a vnet interface under each corresponding “ge” bridge is configured. Use the brctl command on the host server, after you start the vJunos-router as shown below: 408-745-2000-vJunos-Router-Deployment-FIG-15.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (15)" width="623" height="263" srcset="https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-15.png 623w, https://manuals.plus/wp-content/uploads/2024/08/Juniper-NETWORKS-[408-745-2000](https://phone.gd/phone/408-745-2000)-vJunos-Router-Deployment-FIG-15-550x232.png 550w" sizes="(max-width: 623px) 100vw, 623px" />

Configure vJunos-router on KVM

SUMMARY
Read this topic to understand how to configure the vJunos-router in the KVM environment.

Connect to vJunos-router

•  Telnet to the serial console number specified in the XML file to connect to vJunos-router. See details provided in “Deploy and Manage vJunos-router on KVM” on page 11 .
• When you connect through the console, use Ctrl + ] to get to the telnet prompt and then enter quit to exit back to the main host.

For example:

408-745-2000-vJunos-Router-Deployment-FIG-16.png" alt=" Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG- (16)" width="473" height="461" />

Configure Active Ports

• This section describes how to configure the number of active ports. You can specify the number of active ports for the vJunos-router to match the number of NICs added to the VFP VM. The default number of ports is 10, but you can specify any value in the range of 1 through 96.
• Run the user@host# set chassis fpc 0 pic 0 number-of-ports 96 command to specify the number of active ports. Configure the number of ports at the [edit chassis fpc 0 pic 0] hierarchy level.

Interface Naming

• The vJunos-router supports only Gigabit Ethernet (ge) interfaces.
• You cannot change the interface names to 10-Gigabit Ethernet (xe) or 100-Gigabit Ethernet (et). If you attempt to change the interface names, then these interfaces will still show as “ge” when you run the show configuration or show interfaces terse commands.

Configure the Media MTU

•  You can configure the media maximum transmission unit (MTU) in the range 256 through 9192. MTU values outside the above mentioned range are rejected.
• You must configure the MTU by including the MTU statement at the [edit interface interface-name] hierarchy level.
• Configure the MTU. 408-745-2000-vJunos-Router-Deployment-FIG-17.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (17)" width="470" height="108" />
  • NOTE : The maximum supported MTU value is 9192 bytes.
• For example: 408-745-2000-vJunos-Router-Deployment-FIG-18.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (18)" width="491" height="108" />

Troubleshoot

Verify That the VM is Running

• Verify whether the vJunos-router is running after you install it. 408-745-2000-vJunos-Router-Deployment-FIG-19.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (19)" width="361" height="65" />The virsh list command displays the name and state of the virtual machine (VM). The state can be: running, idle, paused, shutdown, crashed, or dying. 408-745-2000-vJunos-Router-Deployment-FIG-20.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (20)" width="534" height="187" />
• You can stop and start the VMs with the following virsh commands:
  • virsh shutdown—Shutdown the vJunos-router.
  • virsh start—Start an inactive VM that you defined previously.

NOTE : Do not use the “virsh destroy” command as that can corrupt the vJunos-router VM disk.

If your VM stops and does not boot after using the virsh destroy command, then create a live QCOW2 disk copy of the original QCOW2 image provided.

Verify CPU Information

• Use the lscpu command on the host server to display CPU information.
• The output displays information such as the total number of CPUs, the number of cores per socket, and the number of CPU sockets.
• For example, the following codeblock shows the information for an Ubuntu 20.04 LTS host server supporting a total of 32 CPUs.

408-745-2000-vJunos-Router-Deployment-FIG-21.png" alt=" Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG- (21)" width="748" height="831" srcset="https://manuals.plus /wp-content/uploads/2024/08/Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG-21.png 748w, https://manuals.plus/wp-content/uploads/2024/08 /Juniper-NETWORKS-408-745-2000-vJunos- Router-Deployment-FIG-21-495x550.png 495w" sizes="(max-width: 748px) 100vw, 748px" /> 408-745-2000-vJunos-Router-Deployment-FIG-22.png" alt=" Juniper- NETWORKS-408-745-2000-vJunos-Router- Deployment-FIG- (22)" width="485" height="87" />

View Log Files

• View the system logs using the show log command on the vJunos-router instance. 408-745-2000-vJunos-Router-Deployment-FIG-23.png" alt=" Juniper-NETWORKS-408-745-2000-vJunos-Router-Deployment-FIG- (23)" width="416" height="78" />
• The root > show log ? command displays the list of log files available for viewing.
• For example, to view the chassis daemon (chassisd) logs run the root > show log chassisd command.

Collect Core Dumps
Use the show system core-dumps command to view the collected core file. You can transfer these core dumps to an external server for analysis through the fxp0 management interface on the vJunos-router.

FAQ

Q: What are the key features of vJunos-router on KVM?
A: The key features include running Junos software for network testing, support for multiple instances on a single server, and compatibility with Linux KVM hypervisors.

Q: Is a bandwidth license required for using vJunos-router?
A: No, a bandwidth license is not required for using vJunos-router. License check messages can be ignored.

References

• Downloads
• MX960 Documentation | Juniper Networks

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>